0.2.0

• Rc/0.2.0 (#935)

0.2.0-rc.6

• merge dev to rc (#932)

0.2.0-rc.5

• Merge pull request #920 from zingolabs/dev
• Merge pull request #924 from zingolabs/fix/dockerignore-updates
• Update dockerignore to ignore testing dirs
• Merge pull request #821 from pacu/zebra-4-support
• Merge pull request #897 from zingolabs/rc/0.2.0
• Fix state_service_get_address_transactions_regtest test
• [#816] Updating to Zebra 4.1.0
• Merge branch 'dev' into rc/0.2.0
• Merge pull request #918 from idky137/fix_db_block_write
• Merge branch 'dev' into fix_db_block_write
• Merge pull request #917 from idky137/zainodb_module_refactor
• fixed db block write for zero value shielded txs
• moved dbv1 code into submodules
• Merge pull request #913 from idky137/fix_slow_get_block_range_init
• Merge branch 'dev' into fix_slow_get_block_range_init
• Merge pull request #915 from idky137/transparent_address_history_feature
• Merge branch 'dev' into transparent_address_history_feature
• Merge pull request #914 from idky137/remove_1_1_0_migration
• fixed slow get block range init time when db has not been validated
• feature gated DB transparent history capability + tests
• removed DB v1.0.0 -> v1.1.0 migration
• Merge pull request #911 from zingolabs/rpc_integration_testing
• Add triggering of zcash integration tests to PRs and merges to dev
• Merge pull request #901 from idky137/update_fix_addr_hist_records_by_addr_and_index_blocking
• Merge pull request #905 from idky137/update_db_max_map_size_default
• Merge pull request #902 from idky137/zebrad_state_service_testnet_config
• updated db max size (gb) default to fit mainnet cache
• undo stateservice spawn change
• updated testnet config for zebrad, fixed stateservive spawn
• removed commented out old code
• updated migration + db changelog
• updated fix_addr_hist_records_by_addr_and_index_blocking to take and reuse a lmdb ro txn, reducing tnx overhead
• updated addr_hist_records_by_addr_and_index_blocking

0.2.0-rc.4

• Merge pull request #898 from zingolabs/dev
• Merge pull request #895 from idky137/bug_fix_chain_index_status_shutdown_signals
• fixed chain_index shutdown
• Merge pull request #864 from idky137/fix_chain_index_start_sync_loop
• Merge pull request #884 from zingolabs/clippy_service
• add time based log to zainodb::sync_from_height to show zaino has not stalled
• tune and run cargo fmt
• set generated files to allow warnings
• ignore generated for fmt
• final fixes
• fixed mark addrhist record as unspent
• propagate errors from db env sync
• Merge remote-tracking branch 'idky137/fix_chain_index_start_sync_loop' into fix_chain_index_start_sync_loop
• added db sync before alidating new block to avoid data races
• added debug warning on partially written blocks
• added debug warning on partially written blocks
• updated db write_block, delete_block, validate_block and mark_addrhist_record_spend/unspent
• only every 100 blocks committed logged at info level
• improve SyncError
• nfs sync from fs tip if above prev nfs tip
• fixed chain_index::start_sync_loop

0.2.0-rc.3

• Merge pull request #881 from zingolabs/hotfix/version-bump
• fix(docker): move entrypoint.sh to / per Docker convention
• feat(zainod): print version on startup
• chore: bump version to 0.2.0

0.2.0-rc.2

• Merge pull request #871 from zingolabs/hotfix/dockerfile-entrypoint
• fix(docker): use /app/* symlinks for ergonomic mount paths
• fix(docker): handle read-only mounts gracefully + add permission tests
• fix(docker): use ENTRYPOINT/CMD split with privilege dropping

v0.1.2

v0.1.2 — “Zaino”

✨ What’s new

• Dual-node compatibility
  Works with both Zcashd (FetchService) and Zebrad (StateService) — just choose the backend in your config file.

• JSON-RPC server
  Enable/disable via the config file.

🐞 Known issues

• State-corruption during reorgs (temporary patch applied).
  A full fix is planned for v0.1.3 — see Issue #295 for details.

Milestone 1 Release

0.1.1 is the release for the grant: Build Zaino To Deprecate Zcashd and Decentralize Zcash, Milestone 1.

It should be noted that Zaino is currently still in development and is not currently recommended for Main-net usage.