This post will outline the necessary steps required to execute the VaultZ proposal. It is meant to be an all encompassing detail focused publication of the efforts required, and to be undertaken by the team, to carry the VaultZ proposal from planning through execution, implementation, and monitoring phases.

Additionally, we will be required to update to at least Groth16 proving method, over the past weeks @renuzit has worked tirelessly to implement zcash core updates into BitcoinZ. Read further for more details.

For details on the VaultZ proposal please see:

VaultZ Proposal

Percentage for VaultZ

For details on the zkSNARKs Sprout vulnerability please see:

BitcoinZ Current zkSNARKs Proving Method

Meeting Type Date Discussion Preliminary Sept 30th, 2018 General discussion regarding efforts required for proposal implementation Plan / Identify Nov 3rd, 2018 Discuss beginning of testing phase and required components; as well as any obstacles and discoveries during self-testing / code review Notes: Created todo list Reached out to exchanges to determine support (pending responses) Discussed when sapling integration would make most sense Discussed ‘DynamicZ’ - a StealthWerkZ project Identified critical testing components: Testnet node, Explorer, Pools, Replay protection Re-introduce community fee code into core node Preliminary timeline for minimal functional testing: 2-4 weeks Update required to Groth16 zkSNARKs proving method at a minimum / Sapling codebase Execution March 1st, 2019 Begin deploying test environments for testing of block reward change; and any components required for minimal functionality Notes: COMPLETED : Sapling + VaultZ Master branch Github COMPLETED : Testnet Pool: http://testsnomp.btcz.rocks:8080/stats COMPLETED : Testnet Explorer: Iquidus / Insight COMPLETED : Re-introduce community fee code into core node Next steps: Wallet systems: Win Binaries, Copay, etc March 17th, 2019 1. shielded coinbase coins using z_shieldcoinbase" from multisig one - “t2FpKCWt95LAPVRed61YbBny9yz5nqexLGN” to a sapling z-address 2. sent from sapling z address to single wallet tmQaL15dnng34TNknZiedx9qjRpaHihJMT6 3. sent from t single wallet tmQaL15dnng34TNknZiedx9qjRpaHihJMT6 to sprout z-address 4. sent from sprout z-address to tmQaL15dnng34TNknZiedx9qjRpaHihJMT6 5. tried to send between Sapling -> Sprout and was denied, as it should be denied 6. Mined blocks and the 5% block reward split is being sent to community fee addresses as intended March 24th, 2019 COMPLETED: Production release: Activation on April 6/7th @ Block 328,500 BitcoinZ v2.0.3 (Sapling + VaultZ) - Debian, Linux x64, Windows CLI x64 BitcoinZ v2.0.3 Win GUI Wallet Notes: PENDING: Insight Explorer, CoPay Wallet, Web Wallet, Paper Wallet sites Notes: These systems will be ready by the activation height Partially moving to Implementation phase Implementation March 23rd, 2019 Network updates completed:

Iquidus Explorer

Seeder nodes

Windows GUI Swing wallet

Coinomi Wallet ZelCore Wallet CoPay

Insight

Web wallet

Pending network updates:

Paper Wallet Monitoring April 7th, 2019 Upgrade activated (VaultZ + Sapling) now active Execution plan completed April 7th, 2019 Execution plan completed and fully deployed. Thread will be locked.

Components Identified

During the preliminary meeting BTCZ devs identified the components below.

Coordination / with the listed components will be required at least 30 days before Implementation is foreseeable.

The message needing to be communicated to the components listed is simple: If you’re running a full node for any purpose, an update to latest node build from BTCZ Github is required when it is available.

NOTICE: This list is not considered exhaustive - If any component is missing/not listed please let us know by posting in this thread, tweeting us, getting us on Discord or email us at [email protected]

Exchanges

Pools

Equipool PCMining Axepool Geekhask Mineflow Pool.pink CryptoCommunity Miningspeed Zsolo Nibiru Pool Altpool 2Miners Coinblockers Supernova

Wallets

Co-pay - will update when Insight explorer / BWS updated Multi-asset wallets:

a. Coinomi - node update required

b. ZelCore - node-update required? Swing wallet - node re-packaging required CLI wallet - update node build required Web wallet - will update when Insight explorer is updated Offline wallets / paper wallet sites - no update required

Explorers

Iquidus - node update required Insight - node update required / many other updates

NOTICE: This list is not considered exhaustive - If any component is missing/not listed please let us know by posting in this thread, tweeting us, getting us on Discord or email us at [email protected]

Updated March 17th 2019