NU6 Testnet activation height has been set

General
1

The ZIP editors / ECC&ZF engineers decided on a height for the NU6 testnet activation: 2976000, which should be reached around August 28, 21:00 UTC (this Wednesday).

If you run a Testnet node, you should update your zcashd or zebrad node with the versions that are about to be released (probably tomorrow). If you don’t update in time, you will need to update and re-sync your node.

Pinging people I think are running testnet nodes: @aarnott @Cacho

14 Likes
2

My testnet node is based on this docker image:

zfnd/zebra     latest          d3606083624e   7 weeks ago     207MB

Is that right? Note it’s 7 weeks old, but that’s apparently the latest available.

3

Yes, that’s Zebra 1.8, the latest release.

2 Likes
4

Yes, to be clear, we’re releasing an update soon (likely today) and you will need to update it. Thanks!

1 Like
5

Oh right, I see that in your original post now. Sorry I missed it.

FWIW, having only a day to upgrade seems like a very small window. I can make it work, but next time I suggest a larger one.

2 Likes
6

Yes, sorry about that. Our timeline was slipping and we had to get things going. For the mainnet activation there will be much more time to update. Thank you!

3 Likes
7

also @emersonian and @hanh (maybe?)

2 Likes
8

We are less than 24 hours away from the announced NU6 testnet activation yet no zcashd nor zebrad releases have happened, as Docker images or otherwise. When should operators expect a release?

A delay would make sense to be respectful to testnet node operators.

Edit: I missed the Zcashd release on Github, my mistake. (thanks @pacu ). Can we get a Docker Hub image published for Zcashd so that I do not have to fork?

2 Likes
9

5.10.0 in docker hub https://hub.docker.com/r/electriccoinco/zcashd/tags

Feedback noted. :pray:

10

We’re now at testnet block 2975627, a mere 373 blocks or ~7 hours away, and no zfnd/zebra docker image update is yet available.

1 Like
11

The Docker image is now available: https://hub.docker.com/r/zfnd/zebra/tags

2 Likes
12

The nodes backing testnet.zec.rocks are updated, as well as the Helm charts available at GitHub - emersonian/zcash-stack.

4 Likes
13

My mainnet and testnet zebrad nodes are now updated. Thanks.

4 Likes
14

A heads-up for those who are interested, NU6 activates on testnet in about 45 minutes. Anyone running zcashd 5.9.x or zebrad 1.8.x on testnet should shut down or upgrade their nodes in order to avoid following the wrong fork.

15

Apologies for the short notice; the zcashd release was delayed due to problems with testing backported security fixes; once zcashd was ready, we wanted to set the testnet activation height as soon as possible so as to give as much time as possible for remediation in case anything goes wrong with activation on testnet, so that we have as much time as possible to update for mainnet activation. We already had to shorten the normal 16-week EOS halt window in order to ensure that v5.10.0 nodes would halt before the halving.

2 Likes
16

NU6 has successfully activated on testnet:

2024-08-28T17:37:32.598260Z  INFO ProcessNewBlock: main: UpdateTip: new best hash=0017d56ed80077f45eb88f11d50f4306ee1fbf95892c9a9cb7a9538e72ceabc1 height=2976000 bits=527777933 log2_work=37.37135 tx=3522206 date=2024-08-28 17:37:30 progress=1.000000 cache=19.9MiB(101tx)
7 Likes
17

Congratulations on your new milestone! Where can I see the final list of what went into NU6?

UPD. Okay, I’ve familiarized myself here: arboretum-notes/AllArboristCallNotes/Arborist Call 84-Notes.md at main · ZcashCommunityGrants/arboretum-notes · GitHub

2 Likes
18

@cacho is having issues with the node backing mainnet explorer

19

Our internal testnet Zebra nodes and the Zebra node for exblo have been updated.

20

Hi,

ZCashd Mainnet is returning a different response than Zcashd testnet for getblockchaininfo. Mainnet is not returning chainValue and chainValueZat for transparent pool. This change was introduced after 5.10 update.
After reviewing the documentation it looks like chainValue/chainValueZat is optional in rpc. I´ll update the explorer code unless you have a different opinion.

Testnet Response

 "valuePools": [
            {
                "chainValue": 14330225.99333559,
                "chainValueZat": 1433022599333559,
                "id": "transparent",
                "monitored": true
            },

Mainnet response

 "valuePools": [
            {
                "id": "transparent",
                "monitored": false
            },
1 Like