My first call with @joshs was Jul 18th and our engineer started some research since then.
We setup our Slack channel with @joshs and other engineers on July 23rd (sorry can’t provide a link as a proof). And we have technical discussion back-and-forth asynchronously based on our own research.
We had a more focused technical call with @joshs@daira@str4d and other folks from ECC team on Aug 5th.
And this is also the reason @daira@str4d is answering technical questions above (kudos to @daira@str4d and the whole ECC team which is super helpful).
With the early research and communication mentioned above, we are kind of confident that we can deliver this before the end of October. So we put this date in the application. But again, we will do our best and this is not a guarantee.
Also please kindly note that the final delivery date of this integration also depends on
when this grant is approved.
how long it takes for Zashi team to finish the integration on their end.
@Lixin at the most recent meeting, the @ZcashGrants Committee voted to conditionally approve this proposal with the stipulation that Least Authority review the SDK and address concerns before final payout. ZCG has requested that you provide monthly updates via the forum in this thread.
Hi @Lixin - Yes, Least Authority is a security auditing firm that is fulfilling a ZCG funded role as the Zcash Ecosystem Security Lead. See their monthly updates here.
@Liz315 can help facilitate with information about the auditing process and scoping that work. Least Authority is also available for consultation sessions related to your project if needed.
Hi @Lixin - Feel free to reach out with questions anytime. When convenient, it would be great for us to learn more about the scope and timeline so we can meet any necessary deadlines. You can send details to us or we can schedule a call to discuss it all.
Hey @Liz315 nice to e-mmet you here! And we are excited for our coming collaboration!
Do you mind joining our Slack channel with ECC team? So that they can be also synced with the collaboration between us and they may potentially have some comments too.
On the other hand, our dev set up a wallet with the command-line wallet provided by ECC team, with which we are going to make a demo for the integration to speed up the final integration with Zashi.
Currently, our dev is working on wallet address verification, which involves trying to generate a Zcash address using the same mnemonic in our codebase and checking if it matches the one generated by the software wallet.
Please kindly note that we received the confirmation email on Thursday and we only spent 2 days on the work mentioned above. Thanks!
You guys are awesome Lixin. So thankful to have folks like you in the hardware industry making an effort for this. Ledger has been a nightmare they are so slow and out of touch. It would be very impressive if we got shielded support on Keystone before Ledger…
If Keystone releases their shielded app before Ledger, I will buy at least 2 Keystone wallets. I already planned to buy a Ledger Flex or Stax, but I think Keystone 3 Pro is better suited for me.
TBH if we didn’t make it of shipping shielded address support before Ledger, I still suggest you can give Keystone a try. I don’t want to be heard so biased but the most common feedback we got from Ledger user is that “after using Keystone, you will never go back to Ledger” LOL.
Usually a co-branded version takes about 4-6 weeks for manufacturing and shipping. And we want to start pre-order when we are 100% sure about when we can finish the work we promised in the grant.
We set some deadlines for each milestone of the grant but TBH now we are not 100% sure we can deliver them on time as there are many dependencies. We will do our best.
love the idea of opening it to the community! zechub and free2z communities will be all over the promotional aspect of getting designs im sire. The x% to the foundation is my vote also, their mission has the most wide spread benefits.
Continuing from the previous week’s work, we have verified the feasibility of the address-generation algorithm on Keystone. Keystone can generate the same addresses as the CLI wallet shared by the Zashi team. We are using this CLI wallet to build a demo for the integration with the Zashi Wallet. With that being said, the POC of Milestone 2 (Keystone hardware wallet can generate both transparent and Orchard Shielded addresses) has been done (not tested nor audited yet).
We have read part of the source code related to sending transactions in the CLI Wallet. Currently, we are verifying the feasibility of signing transaction (Milestone 3) on Keystone. We have already extracted transaction information from the CLI Wallet. The next step is to modify or extract part of the signing library’s code to make it workable on the Keystone 3 Pro. This will allow us to sign transactions on the Keystone device and then transfer them back to the CLI Wallet for on-chain transactions.
Please kindly note that after some discussion with the Zashi team, the deliverable of Milestone 1 has been changed from “Review and finalize PCZT (similar to PSBT for Bitcoin) with Zashi/Zcash team.” to "POC of PCZT (similar to PSBT for Bitcoin) with Zashi/Zcash team."We are having this change because the discussion of PCZT will be through the whole process of our integration and we are modifying that with the Zashi team from time to time. So it’s inappropriate to “finalize” it in Milestone 1.And for Milestone 1 we are having 1-ish week delay. But the good news is that Milestone 1 is not blocking the following work and we are working on other deliverables and we are 100% on time.
