# Public Notes on ZSA Discussions ## 2/12/2021 - Arborist call - how many assets can you fit in a single transaction / circuit - probably around 10 could work - there is also transaction size limit on the number of actions - 2109 was the limit for Sapling outputs - https://zips.z.cash/protocol/protocol.pdf#orchardbalance - for issuance / minting: - how much state does the full node have to maintain? Would add - registry list as transparent UTXOs from TZE outputs - or state from a new transaction type / version - this yields a trade-off: how extensible are TZEs vs how much state must be maintained with new tx types? - Do we want to (eventually) allow minting privately? - In any case, if do TZE-based issuance, then think about extensibility: what if we want to change to registry-based in the future? - backwards compatibility - in order to use the Orchard-ZEC in the new ZSA-Orchard one can have either the type be all "0" or have a deafault note slot that does not have a type. - Most likely will not need a turnstile method
Last changed by  
 
QEDIT Research
380

Read more

Zcash zkAssets QEDIT Grant Proposal

Further notes for proposal talk about NFT and the need for privacy not necessarily ARBORIST CALL NOTES for when NU6? shared roadmap

12/8/2021
Zcash NU5 Final Audit Report - September 2021

![](https://i.imgur.com/PyNeb3o.png =250x100) [TOC] Overview This document presents the findings of the QEDIT team during the review of the Zcash NU5 protocol update. Specifically the review is focused on (1) the Halo 2 proving system with its latest PLONK-style arithmetization for representing constraint systems; (2) the Orchard protocol, which, even if based on Sapling, differs considerably from it; (3) the underlying primitives of Orchard, from hash functions and commitments to signature schemes; (4) the latest key structure and derivation system; (5) the underlying field and elliptic curve arithmetic and parameter generation; and (6) the actual circuit implementation that describes the Orchard Action statement. Note that we explicitly exclude any blockchain-related component not associated with orchard or its interface (consensus, network, block generation, etc.) For this review, we evaluated the specification of the protocol design for security and audited the implementation for vulnerabilities that could affect the system as a whole. This review spanned the period of ~5 months, intermitently, from April 21st until September 24th, 2021.

10/12/2021
QEDIT QAT Blockchain Demo for Assioma

![](https://i.imgur.com/PyNeb3o.png =400x150) In this document, we present the details of the QEDIT Asset Transfer (QAT) solution as per the scope defined in the pricing proposal with reference: 20210618-QAT01. This includes, a testing cloud environment where QAT has been deployed as a single node. The API keys to interact with the system and an example script to test the different modes of operation (issuance, transfer, etc.) The documentation for the API is can be found here. Access Details to QAT Demo Node We have prepared a test environment for Assioma, hosted on AWS (Frankfurt). In order to access it, you can either call the API locally, or use the Swagger GUI by following the steps below:

9/5/2021
Read more from QEDIT Research
Published on HackMD