• Home
  • Reference
  • Changelog

Changelog

Track what's new across the Shinzo developer platform: network releases, SDK changes, tooling updates and documentation improvements.

Sep 29, 2026

🐳 Upgrade

Generator client

Generator operators upgrading to v0.7.0-ethereum-mainnet need to reset their DefraDB database files while preserving their existing node identity. Do not delete the entire DefraDB store or keys directory. Your existing identity must be preserved to avoid generating a new peer ID and having to register the Generator again.

Before upgrading, keep the following unchanged:

  • Keys folder: The existing DefraDB identity key must remain in place. If the node cannot find its key, it creates a new identity and will need to register again.
  • Keyring secret: Keep the same DEFRADB_KEYRING_SECRET. A different secret prevents the Generator from reading its existing key.
  • Public IP: Keep the same registered public IP. The IP is part of the node’s on-chain registration. If the server is recreated and its IP is not reserved, the address may change.

Only remove the database files required for the reset. Never rm -rf the entire store. This is especially important for Generators started with docker run, where identity keys may live inside the data directory. Once the existing identity, keyring secret, and registered IP are preserved, start the Generator with the new image:

docker pull ghcr.io/shinzonetwork/shinzo-generator-client:v0.7.0-ethereum-mainnet

Host client

Host operators also need to reset their DefraDB database files while preserving the Host identity.

Keep the following unchanged:

  • Keys folder: Do not remove the Host’s existing identity keys.
  • Keyring secret: Keep the same keyring_secret configured in config.yaml.
  • Public IP: Keep the same registered public IP.

Never rm -rf the entire store. Hosts started with docker run may store their keys inside it. After resetting only the required database files, start the Host with the new image:

docker pull ghcr.io/shinzonetwork/shinzo-host-client:v0.7.0-ethereum-mainnet

💡 Improvements

  • Generator Generator now uses the new chain abstraction architecture, separating chain-specific logic and enabling support for additional chains. (PR #348)
  • Generator LinkStamper errors now stop processing instead of allowing corrupted records to be indexed. (PR #367)
  • Generator CID waits are now cancellable and document fields are read directly from DefraDB. (PR #371)
  • Generator In-flight indexing and signing operations now complete before DefraDB shuts down. (PR #390) (PR #391)
  • Generator DefraDB’s libp2p protocol now enforces resource limits, including a configurable memory budget. (PR #384)
  • Generator Generator version is now logged at startup, making the running version directly visible in logs. (PR #383)
  • Host Attestation records now include an indexed block number for more efficient block-based operations. (PR #386)
  • Host Pruning now operates by block height, improving how historical data is identified and removed. (PR #426)
  • Host Added resource limits to the DefraDB libp2p protocol to improve resource management and network stability. (PR #411)

⚠️ Notes for operators

  1. Memory

The default configuration assumes a 16 GB container with:

GOMEMLIMIT=14GiB

The DefraDB libp2p memory budget now defaults to 10 GiB. If you’re running a smaller container or machine, set DEFRADB_P2P_RESOURCE_MEMORY_MIB below your GOMEMLIMIT to keep the libp2p resource budget within the memory available to the process.

  1. Host pruning

max_blocks now represents the number of block heights retained. docs_per_block has been removed. If it is still present in your config.yaml, it has no effect and can be deleted. max_docs_per_cycle, which controls the number of documents deleted during each pruning cycle, now defaults to:

max_docs_per_cycle: 50000
  1. (optional) Host disk readahead

For Host operators, setting the data disk’s readahead to 16 KB can reduce disk reads from DefraDB’s memory-mapped files.

Identify the data disk:

lsblk

Then set its readahead:

echo 16 | sudo tee /sys/block/<disk>/queue/read_ahead_kb

This setting resets after a reboot.

Sep 16, 2026

🐳 Upgrade

Generator client

docker pull ghcr.io/shinzonetwork/shinzo-generator-client:v0.6.5.4-ethereum-mainnet

Host client

docker pull ghcr.io/shinzonetwork/shinzo-host-client:v0.6.5.4-ethereum-mainnet

💡 Improvements

  • Generator Improved indexing and pruning performance to reduce chain lag and help Generators stay closer to the chain tip. (PR #333) (PR #335)
  • Generator Secondary indexes are now rebuilt correctly after importing data, improving data consistency after restores or migrations. (PR #338)
  • Generator Chain configuration has been generalized to improve support for different chain configurations. (PR #329)
  • GeneratorHost Health checks now actively probe DefraDB, providing a more accurate indication of client health. (PR #364) (PR #382)
  • GeneratorHost Registration no longer suggests addresses that are unreachable by other network participants. (PR #366) (PR #367)
  • Host Improved pruning behavior with cleaner shutdown handling and bounded pruning cycles. (PR #357) (PR #360)
  • Host Added a warning state to Host metrics for better operational visibility. (PR #370)
  • Host Fixed registration to preserve the forwarded Host port correctly. (PR #383)

⚠️ Generator Upgrade Note

Generator operators upgrading to v0.6.5.4-ethereum-mainnet need to reset their DefraDB data.

Back up your node identity key before removing the existing DefraDB directory. If the key is not preserved, you will need to register the Generator again.

# Back up the identity key
cp shinzo-data/defradb/keys/node-identity-key ./path/to/new/location

# Reset DefraDB
rm -rf shinzo-data/defradb

# Recreate the keys directory
mkdir -p shinzo-data/defradb/keys

# Restore the identity key
cp ./path/to/new/location/node-identity-key shinzo-data/defradb/keys/

# Set the correct ownership to prevent identity and permission errors
sudo chown -R 1001:1001 ~/shinzo-data/defradb ~/shinzo-data/lens

Once the existing identity key has been restored, you can start the upgraded Generator without re-registering.

⚠️ Host Upgrade Note

# Reset DefraDB
rm -rf data/defradb

# Recreate the required data directories
sudo mkdir -p ~/data/defradb

# Set the correct ownership to prevent permission errors
sudo chown -R 1001:1001 ~/data/ ~/data/defradb ~/data/lens ~/data/keys

Aug 06, 2026

🐳 Upgrade

Generator client

docker pull ghcr.io/shinzonetwork/shinzo-generator-client:v0.6.5.3-ethereum-mainnet

Host client

docker pull ghcr.io/shinzonetwork/shinzo-host-client:v0.6.5.3-ethereum-mainnet

💡 Improvements

  • Generator Improved block signing performance by signing batched blocks directly from collected CIDs instead of performing a read-back query. (PR #308)
  • Generator Fixed a hardcoded Shinzo Hub URL used during testnet deployments. (PR #313)
  • Host History pruning is now enabled by default. (PR #326)
  • Host Fixed a hardcoded Shinzo Hub URL in the health server. (PR #351)
  • GeneratorHost Updated dependencies, including Go Ethereum, GitHub Actions, gRPC, and other internal libraries for improved stability and maintenance.

July 16, 2026

🐳 Upgrade

Generator client

docker pull ghcr.io/shinzonetwork/shinzo-generator-client:v0.6.5.2-ethereum-mainnet

Host client

docker pull ghcr.io/shinzonetwork/shinzo-host-client:v0.6.5.2-ethereum-mainnet

💡 Improvements

  • Generator Blocks are now signed only after all required block data has been received. (PR #293)
  • Generator Pruning now skips invalid or incomplete records instead of stopping the entire process. (PR #287)
  • HostGenerator Updated status pages to point to the correct hub. (PR #319) (PR #302)
  • Host Billing now validates against the pool included in each signed request. Queries without a pool are rejected. (PR #314)
  • Host Failed pruning jobs are now automatically retried instead of being discarded. (PR #316)
  • Host History pruning is now disabled by default. (PR #317)
  • Storage Improved pruning reliability when new data is written during concurrent writes.
  • Storage Large deletion operations are now processed in smaller batches for better stability.
  • Storage Deleting documents now also removes their associated index entries.
  • Storage Improved pruning performance by reducing unnecessary ownership scans.

July 08, 2026

🐳 Upgrade

Generator client

docker pull ghcr.io/shinzonetwork/shinzo-generator-client:ethereum-mainnet-latest

Host client

docker pull ghcr.io/shinzonetwork/shinzo-host-client:v0.6.5-ethereum-mainnet

✨ Highlights

  • Shinzō Testnet is now live.
  • Generator Generator Client is available for Shinzo Testnet deployments. Installation instructions: Generator Installation Guide
  • Host Host Client is available for Shinzo Testnet deployments. Installation instructions: Host Installation Guide