Sapphire Prix

Oasis Network RFP: Sapphire Confidential Fungible Token Standard

<!-- SC_OFF --><div class="md"><p>Oasis Network recently launched the <a href="https://docs.oasis.io/dapp/sapphire/">Sapphire Paratime</a>- the industries first and only confidential EVM. We just published an <a href="https://github.com/oasisprotocol/adrs/issues/8">RFP for Sapphire Confidential Token Standard</a>. Please feel free to contact me with any questions, or if you're interested in building on Sapphire.</p> <p>Motivation</p> <p>A <em>confidential fungible token</em> (CFT) that hides at least one of {sender, recipient,amount}<br/> can offer a more complete privacy solution to both dapps and users. A CFT standard will encourage interoperability among dapps, improved tooling for developers, and more convenience for end users.</p> <p>Example Use-Cases</p> <ul> <li>A Web3 gaming company wants to to offer in-game purchases, but doesn't want competitors to identify its most valuable customers.</li> <li>a DAO wants to purchase a physical good but wants to prevent other potential buyers from one upping their offer</li> <li>incentive-compatible (sealed-bid second-price) NFT auctions</li> <li>improved DeFi: MEV-resistent DEX, privacy for users of KYC'd lending protocols</li> </ul> <p>Requirements</p> <ul> <li>ERC-20 ABI compatible</li> <li>supports variants hiding any/all of {sender, recipient,amount}<br/> from entities who are not the sender or recipient</li> <li>variants able to be generated using a <a href="https://docs.openzeppelin.com/contracts/4.x/wizard">wizard</a></li> <li>conducive to side-channel resistant implementations</li> <li>minimal runtime overhead for ERC-20 methods when compiler optimizations are enabled</li> </ul> <p>Each variant (if multiple) can be in one ADR but have its own name, if desired (e.g., "ADR-18 Semi-Private").</p> <p>Desirable Features</p> <p>These features are highly useful, but may be added in future standards application or platform. If not solved in the proposal, these features must not be precluded by the proposal.</p> <ul> <li>receiver can be efficiently notified of an inbound transfer.</li> </ul> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/mentalgooseflesh"> /u/mentalgooseflesh </a> <br/> <span><a href="https://www.reddit.com/r/ethereum/comments/y47ml7/oasis_network_rfp_sapphire_confidential_fungible/">[link]</a></span>   <span><a href="https://www.reddit.com/r/ethereum/comments/y47ml7/oasis_network_rfp_sapphire_confidential_fungible/">[comments]</a></span>