Is the Testnet Broken?

The testnet seems to be froze at block 33271. Is it expected to work at this time with zcash v1.0.5?
I was mining a few blocks a couple weeks ago...

This also appears to not work...
https://explorer.testnet.z.cash/

After several days leaving a node on the testnet....it finally woke up and started mining a couple more blocks. Now it is hashing again. Interesting, just thought I would report I do have one active full node working again on the testnet.

1 Like

Thanks for confirming it works again for you. Also, the testnet explorer linked above shows new blocks.

Is "explorer.testnet.z.cash" running an outdated node and left on chain fork?
It doesn't appear to be in sync with the testnet anymore...

There was some message before

"errors": "Action required: testnet will upgrade at block 53127. Upgrade to Zcash 1.0.7 to avoid being left on a chain fork.

zcash-cli getchaintips

[
  {
    "height": 54278,
    "hash": "002e756629a7bd7366dcf652ca24b005cc4bab4ef7fc81b1bb688b879cd2d95d",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 53875,
    "hash": "00f21de9df29f1137635fb966cc160bce41c00e4175402034dd26ed90b28d28d",
    "branchlen": 1,
    "status": "valid-headers"
  },
  {
    "height": 53140,
    "hash": "00275f71021b0f0071af997d0db779fcbd6c5127c2334c77d48376a0ee8e08a3",
    "branchlen": 14,
    "status": "invalid"
  }
]

zcash-cli getinfo

{
  "version": 1000751,
  "protocolversion": 170002,
  "walletversion": 60000,
  "balance": 4340.00000000,
  "blocks": 54279,
  "timeoffset": -37,
  "connections": 1,
  "proxy": "",
  "difficulty": 25.62447165952985,
  "testnet": true,
  "keypoololdest": 1490107710,
  "keypoolsize": 101,
  "paytxfee": 0.00000000,
  "relayfee": 0.00000100,
  "errors": "WARNING: abnormally high number of blocks generated, 140 blocks received in the last 4 hours (96 expected)"
}

zcash-cli getpeerinfo

[
  {
    "id": 147,
    "addr": "198.199.112.230:51526",
    "addrlocal": "xxx.xxx.xxx.xxx:18233",
    "services": "0000000000000001",
    "lastsend": 1490148132,
    "lastrecv": 1490148132,
    "bytessent": 800189,
    "bytesrecv": 915211,
    "conntime": 1490096032,
    "timeoffset": -14,
    "pingtime": 0.019414,
    "version": 170002,
    "subver": "/MagicBean:1.0.7/",
    "inbound": true,
    "startingheight": 53890,
    "banscore": 0,
    "synced_headers": 54283,
    "synced_blocks": 54283,
    "inflight": [
    ],
    "whitelisted": false
  }
]

Curiosity kills the cat...thank you for any information...

Just wanted to report that I noticed, the testnet block explorer's zcash node must have been updated because it's working again and showing the latest mined testnet blocks :slight_smile:

A recent block I mined with my custom coinbase hex :slight_smile:
https://explorer.testnet.z.cash/tx/8dc4ce09e74a0df5fbc07ff6f42b94fafaadb2a3bd4d1ecc95fa6b61e793299d

1 Like

Hi @hellcat are you still on the testnet?

I have been able to mine successfully there, and my coins eventually mature, but I cannot seem to send them to a zaddress, e.g.:

zcach-cli sendtoaddress "ztmDbXP67jDTdhZwhvdxbKhXsUvVe3SpNAUHGeKZVrw6pBRcZytmw6NsXrnMumKPDRLPWWkdmf7uSQxjJV7Gr2hMv3ZK3Xj" 0.1
error code: -5
error message:
Invalid Zcash address

According to my client, though, the above address is valid.

Have you encountered this before? Is my understanding correct that I must first send the mined coins to a zaddr before I can send them to a taddr?

You can not use "senttoaddress" or "sendmany" when sending to private zaddr.

Please see Zcash Payment API docs.

You must use "z_sendmany" to shield mined coins to a zaddr before payments can be sent.

Enjoy!

... aha! Thanks a lot.

Hi Hellcat,

Do you have a set of examples of using the json-rpc protocol via curl (beyond the examples provided by "zcash-cli help")? I am spending a lot of time using trial and error to figure out where to put brackets ([ and ]) vs braces ({ and }). Do you know how to format the fee in the json-rpc?

All the best,
ezaron