docs: zeto change-log update #117
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| # Zeto Smart Contract Set | ||
|
|
||
| We're excited to introduce the Zeto Smart Contract Set, bringing comprehensive zero-knowledge token capabilities to the SettleMint platform. | ||
|
|
||
| ## Token Types | ||
|
|
||
| ### Fungible Tokens | ||
| 1. **Zeto_Anon** | ||
| - Basic anonymous transfers | ||
| - Privacy-preserving transactions | ||
| - Standard fungible features | ||
|
|
||
| 2. **Zeto_AnonEnc** | ||
| - Encrypted anonymous transfers | ||
| - Enhanced privacy features | ||
| - Encrypted transaction data | ||
|
|
||
| 3. **Zeto_AnonNullifier** | ||
| - Anonymous with nullifiers | ||
| - Prevents double-spending | ||
| - Transaction tracking without revealing details | ||
|
|
||
| 4. **Zeto_AnonNullifierKyc** | ||
| - KYC-enabled anonymous transfers | ||
| - Regulatory compliance features | ||
| - Identity verification while maintaining privacy | ||
|
|
||
| 5. **Zeto_AnonEncNullifier** | ||
| - Encrypted transfers with nullifiers | ||
| - Combined encryption and tracking | ||
| - Maximum privacy with spending controls | ||
|
Comment on lines
+28
to
+31
There was a problem hiding this comment. suggestion (typo): Use "KYC" instead of "Kyc" for consistency. It's generally recommended to use all caps for acronyms like KYC (Know Your Customer). Suggested implementation: |
||
|
|
||
| 6. **Zeto_AnonEncNullifierKyc** | ||
| - KYC-enabled encrypted transfers | ||
| - Full suite of privacy features | ||
| - Compliant with regulatory requirements | ||
|
Comment on lines
+33
to
+36
There was a problem hiding this comment. suggestion (typo): Use "KYC" instead of "Kyc" for consistency. It's generally recommended to use all caps for acronyms like KYC (Know Your Customer). Suggested implementation: |
||
|
|
||
| ### Non-Fungible Tokens | ||
| 1. **Zeto_NfAnon** | ||
| - Basic anonymous NFTs | ||
| - Private ownership | ||
| - Hidden transfer history | ||
|
|
||
| 2. **Zeto_NfAnonNullifier** | ||
| - NFTs with nullifiers | ||
| - Trackable unique assets | ||
| - Privacy-preserving ownership transfers | ||
|
|
||
| ## Zero-Knowledge DVP (Delivery vs Payment) | ||
| - Atomic swaps between any token types | ||
| - Private order matching | ||
| - Secure settlement verification | ||
|
|
||
| ## Testing, Deployment & Trusted Setup | ||
| - Fast test deployments with pre-configured environments | ||
| - Local development setup | ||
| - Production deployment helpers & MPC trusted setup guides | ||
|
|
||
| ## Subgraph Integration | ||
| Pre-configured subgraph templates for all contracts | ||
|
|
||
| ## Open Source Zeto Deployment | ||
| - Zeto smart contracts repository: [github.com/settlemint/solidity-zeto](https://github.com/settlemint/solidity-zeto) | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion (typo): Use "KYC" instead of "Kyc" for consistency.
It's generally recommended to use all caps for acronyms like KYC (Know Your Customer).
Suggested implementation:
Note: If this contract name is referenced elsewhere in the codebase (like in actual smart contract files, tests, or documentation), those references will also need to be updated to match this new capitalization.