Zingo Labs Accelerates Zcashd Deprecation

[idky137]

I have opened this issue for this purpose (Enumerate the set of indices required by "full node" wallets and block explorers. · Issue #72 · zingolabs/zaino · GitHub). And will be reaching out to exchanges and other users of zcashd’s cli’wallet in the near future.

[zancas]

Hey folks! This is thrilling news. Look forward to hearing about our progress in 30 days!

[daira]

@zancas

Does anyone have an estimate for zcashd deprecation where the other components take less than 5 months?

To me the issue is not whether zcashd deprecation will be complete within 5 months (although I hope it will be); it’s whether we will need the indexer piece before 5 months. I think that other parts will get to the point that they are blocked on having the indexer, long before that.

@zancas

NU6

My impression is that NU6 needs more time in testnet, with concomitant attention from (I assume) ECC engineers.

NU6 will activate on time at the halving. zcashd 6.0.0 will be released this week (6.0.0-rc1 is already out; there’s just Make DEFAULT_BLOCK_UNPAID_ACTION_LIMIT zero by daira · Pull Request #6900 · zcash/zcash · GitHub and the final changes for activation which will go in the release PR).

[daira]

@ZcashFoundation

@zancas at the most recent meeting, the @ZcashGrants Committee voted to approve your revised proposal and has requested that you provide monthly updates via the forum in this thread. This approval is contingent on @daira & @pili confirming the amendments to this grant via this thread.

Is there any way to see the history of changes? (I strongly suggested moving the grants to GitHub; I gather that hasn’t been done yet.) I don’t see significant changes since the last time I reviewed, but it’s hard to tell if I have to just rely on memory.

[pili]

ZF Engineering team confirms that we are good with the grant in its current shape and we have 2 pieces of additional feedback:

1. We would request that all work be open source and licensed with an appropriate open source license. We notice the Zaino repo does not have a license yet.
2. It would be good to have a bit more detail within the grant itself on what each of the deliverables entails although we do see that the issues in the github repo provide more information.

[zancas]

I am in favor of using git to manage grants. I don’t know if/how to access edits in submittable, but I can look into it, if necessary.

[zancas]

I believe that the MIT license is acceptable to everyone?

We can add that to the repo, if there’s agreement.

We’re happy to copy details into the submittable grant form if that’s required.
Would 2 to 5 bullet points in a list be an acceptable format in the grant?

If that’s the ask then we can make a 1:1 map from tracking issue task to submitted-deliverable bullet point.

[dismad]

Good luck to you and your team

[daira]

I am good with the current grant with the software deliverables being under the MIT license.

[Edicksonjga]

Great and important news. We are one step closer to reaching new objectives, strengthening the network and leaving behind the obsolete.