---
# System prepended metadata

title: Project Orchid

---

# Project Orchid


## Morning
- If we have the Grab wallet at the merchant, we are forced to send out XSGD. We cannot send private and anonymous money. So we are trying to increase the anonymity set for the merchants' money sent.
- We thought about using Nightfall. If we only do a zkrollup for the smart contract for the voucher NFTs, then we only have privacy between users and the voucher smart contract and the users and the issuer. Also, the smart contract can't send money to merchants but we need an offline party to withdraw them.
- Also then, we could aggregate the values and send them. (Without a proof.)


## Afternoon
- We thought about adding verifiable credentials/ZKAPs to the existing protocol. We would need an off-chain prover. We basically separated the smart contract into an off-chain and on-chain component.
- See the diagrams.
- We have different zk components. ZKAPS, Circuit for the aggregation, and possibly Nightfall (if the airdrop is not off-chain).
- It would not be too much to develop since the components are already written for ZKAPs and one could use circom/Zokrates.
- We also thought about Aztec. 



## drawings

- phase 1: https://docs.google.com/drawings/d/116Td0lMfQvYd636agk3raPZzettBF4GJGsMJ4WnSh-Q/edit
- nightfall: https://docs.google.com/drawings/d/1l7y6n1aqyHwZPHfShuEe5_YYWStx_Rm0PRW2wgqQhwE/edit
- tokens+snarks: https://docs.google.com/drawings/d/1xJqFnpwahZsdRLI0pGZQtJzreQ3epJ8YQCV5FD6TsNQ/edit

## Meeting on Thursday
- For MAS the goal is Would do this for different blockchain/ledgers -- would be generic
- How integrated should our work be with StraitsX component
- Vincent will work on the specification and publish to the public
- PBM specification learned from the FinTech festival and will be updated
- Solution should not be highly customized!
- Talk to the other use cases -- how this would be independent
- iterative process to define scope
- write down some points to go forward

# Summary 
We suggest a ....
To understand the requirements of the CBDC, we need to refine 

# Meeting 02/03/22
- 