Reserved. Feedback strongly encouraged.
Thank you Cryptorex for your precisious describtion and your step up for VaultZ activation. I would strongly highlighten the pool Suprnova, because one of the many reason why we constructed a donation method VaultZ was caused by their careless attitude. I dont mean that, everybody should donate but there should be a midpath between huge taxes and lack of donation. VaultZ is our midpath and dont forget we could devote it or modify it by the time passes.
So Suprnova should definitelly update to our new node, and I really hope so they do it.
I would like to add to the exchange list: http://cratex.io our members new exchange and his pool which was among our first pools: http://pcmining.xyz
Im happily looking forward for the next meetup!
Thank you.
Thank you cryptorex for the new thread for VaultZ.
May I copy here as a reminder what I wrote on Nov 13 2017 on bitcointalk:
Take a developer fee for marketing and infrastructure of 500 BTCZ per block size reward, but do not destroy the factor 1000 in relation to BTC.
The halving will destroy the trust of ‘normal’ people in BTCZ as true BTC 2.0 as explained in post #1 of this thread.
Please could you explain exactly from the advantage site why halving helps?
BTC is mining until year 2040 to get all the 21 mio coins available. Shall BTCZ miners mining until year 2070 to get all available coins?
Halving destroys the reasonable factor 1000 to factor 500, this makes no sense IMHO.
Halving is a contradiction to the basic concept of BTCZ.
Good to see that we add now a small fee for community.
-swisstrader
If I understand correctly, the 5% will be taken directly from each new minned block (12500 -5% (665) = 11875 reward block)? And the change will be made in the BTCz Full node (https://github.com/btcz/bitcoinz).
So the payment gateways (btcz.in or pay.btcz.app) and other projects like TxtZ will also have to update the full node.
What will happen for those who do not update? it’s like a hard fork?
I guess, who do not update, will be excluded or can cause huge share errors/ malefuncion at mining (lower rates).
Yes it will be taken from block reward goes to a community or vaultZ address (we will discuss it).
It will be voted what region (eg. Marketing, development…) and what project will get parts for utilites to development (will be discussed).
Receiver should report every transaction or usement of the amount.
Yes - the change will be directly for each new mined block.
Yes - any service running fullnode will need to update. It is effectively a ‘hard fork’, in that those who do not update will be left behind.
We had a discussion on Nov 3rd 2018 to implement VaultZ. Details have been posted/updated on the chart in the original post.
In short we discussed the best approach to upgrading
- VaultZ or
- VaultZ + Sapling or
- VaultZ + Sapling + DynamicZ
As of now - option 1 is the best option as 2 and 3 contain features that are either too ‘new’ or require additional thought.
We’re moving along. 
I think everyone is aware of what is VaultZ,
but it’s not necessarily obvious about Sapling and DynamicZ.
So correct me if I’m wrong …
Sapling is an improvement of the zksnarks protocol,
which makes it possible to perform Z transactions faster and lighter (with less RAM, something like 30 Mb instead of 3 Gb). From this fact, Z transactions can be made from a mobil device.
But, what is DynamicZ (or Stealth-WerkZ)? Strategic partner with SAFEcoin and Safe Trade, auto-trading exchanges of BTCz to fiat (as explained on Project Announcement 06/27)?
Yep - I’d say that’s a well explained description of Sapling.
Regarding DynamicZ - It is a discussion that was introduced by Stealth-WerkZ, but beyond that I cannot say because we believe it is truly innovative. Further evaluation of the idea needs to be tested because it is something I don’t believe we’ve seen. We can’t say much about it yet.
Very nice update! I though we get a live meetup at oct.30th.
Couéd you update exchange list with Cratex.io made by our member PCmining.XYZ?! Pool list also.
Well the oct 30th date was a typo - it was kind of misleading. I meant to type Sept 30th which was the very first dev meeting we had about it.
But yes, a live stream will be in order I’m just waiting for some responses from some components listed and we’ll go live…I kind of miss that!
Thanks! Need to add cratex.io!
I shared the below on Discord yesterday. I’ve also updated the table in the OP. Choo choo!
We’ve successfully tested VaultZ with a test Community Fee address.
We’ve mined on testnet and the block reward is being split per VaultZ 5% - testing has only used one address but we’re working on how the structure should be - as in there will be over 30 addresses. It seems to be the practice to have many ‘fee’ addresses. The amount of addresses doesn’t change the percentage, they just spread the Community Fee over several addresses.
The test pool where blocks are currently being mined is here: http://149.28.202.159:8080/stats
The testnet explorer successfully shows the block reward seperated out of the 12,500 blockreward - here are details: http://testnet.explorer.btcz.life:3002/block/0003845af6bc49592dd5f01085f1d6573fb93465f5c31f2c570e6f8808f58bc6
Note the 11,875 / 625 BTCZ split (t2CihAq1hbJB49hxWPPifDD7jWRepFoAM2b is a testnet multisig address)
We were successful in spending from the multisig address as well to a shielded address details are here - http://testnet.explorer.btcz.life:3002/tx/8dc97e0ef2d31ef91dbeb525f4b3bac79517bd259130b747078ac9733d5fe6c0
I’ll update the forum later, but wanted to share here first. We are still going to do some more testing and figure out the next steps which are getting a codebase for our exchanges and pool configurations, etc. Stay tuned - VaultZ is moving along.
Excelente noticia🤩!!!
Update (and effort!) much appreciated!
Thank you everyone for the support. I’ve updated with a few extra details - nothing in too much detail, but we would like to communicate that our efforts are ongoing.
As you know, the proving method issue announced earlier this year has required us to pivot and update our core node to at least zcash 2.0.3. That many updates requires our test phase to be extended.
We’ve launched a testnet with a lot of changes and are working towards having a production release soon. Please stay tuned. Remember, this is a community effort. Thanks for your patience.
Team renuzit seems to be is making great progress with our major update to zcash core 2.0.3. This will address the proving method ‘vulnerability’, among other upgrades.
The latest progress is blocks are being successfully mined on testnet:
http://testnet.explorer.btcz.life:3002/
There are a few other things to tidy up, including VaultZ, then we can start scheduling further updates and announcements.
Please stay tuned.
Updated original post with March 17th 2019 notes.
Community, the upgraded node wallet packages for v2.0.3 - Sapling + VaultZ activation at block 328,500 to occur on or about April 6-7th 2019 are available.
Please upgrade when you can, as the activation is about 2 weeks away. Full node wallets should be re-indexed.
The below is available now: https://github.com/btcz/bitcoinz/releases/tag/2.0.3
- Debian Package x64
- Linux x64 binary
- Windows x64 binary
The Windows GUI Swing wallet v2.0.3 is also available now: https://github.com/btcz/bitcoinz-wallet/releases/tag/v2.0.3
If you use Coinomi or ZelCore there is nothing to do yet, as we need to notify them to upgrade, which we will be doing over the weekend.
If you use Android (Copay), we should have a new release by the time activation occurs.
We will be notifying pools and exchanges over the weekend as well.
Please stay tuned! This is definitely an exciting moment for everyone, there is still some more coordination and work involved leading upto the upgrade.