Crosslink: Incentivized Feature Net

[aquietinvestor]

@alphiz22

1. ZingoDelegator version — I was using `zingodelegator-0.0.1`, the only version available on the Play Store at the time. If this caused Orchard transactions to be unreadable by the scanner, that was a compatibility issue outside my control. Has this been confirmed with the Zingo team?

One thing to note is that all ZingoDelegator releases currently use the version number 0.0.1 and include a separate build number. The current release is 0.0.1 (build 37), as shown in the screenshot below. If you could let us know which build number you were using, that would be very helpful.

@alphiz22

2. Staking since block 131,000 — was this activity detected from my Mobile UFVK (ZingoDelegator) or my Desktop UFVK?

This activity was detected from your mobile wallet.

@alphiz22

3. Round 2 submission — do I need to re-submit my UFVKs, or will my Round 1 submissions carry over automatically?

Yes, you’ll need to re-submit your UFVKs for Round 2. Similar to Round 1, we’ll announce a claim period with a submission deadline. At that time, you’ll send us your UFVKs along with your mainnet Orchard address. If you stake using both the desktop and mobile wallets, you’ll need to submit the UFVK for each wallet.

@alphiz22

2. BFT finality and fork visibility — with BFT stalled network-wide, nodes silently ended up on different forks. A public status page showing live BFT health would help participants know whether their activity is on the canonical chain.

Cipherscan and ctaz have developed tools for this. Please see the following links:

CipherScan - Zcash Block Explorer

cTAZ

@alphiz22

Overall the experience was valuable. The community, ctaz.cash, and forum support were excellent throughout.

Thank you for the feedback! It’s helpful to hear your thoughts on where we can improve the user experience.