espressosystems / cape Goto Github PK
View Code? Open in Web Editor NEWConfigurable Asset Privacy for Ethereum
Home Page: https://cape.docs.espressosys.com/
License: GNU General Public License v3.0
cape's People
Contributors
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
Stargazers
Watchers
Forkers
weikengchen gpalrepo leohchen dadybayo zerlo-radar crypto-forks 0xyvz greyreen mimoo cryptozenci anatolianteam nanne007 patogallaiovlabs certora 0xgoldencape's Issues
Batch verification logic
Define a limit of gas consumption for the CAPE contract
Developers' documentation
Check the gas price in USD for other EVM compatible projects
Do not rely on custom jellyfish branch for transcript tests
Plan for V1 (all components)
Gas optimizations for Records Merkle tree
Prepare for audit
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/42
- Go through all the TODOs in the code. Fix each of them or delete if not relevant anymore.
- Initial cleanup
- Check remaining TODOs related to CAPE contract code with @sveitser
- Review the code and check if it is readable. In particular review/add comments.
- Check that the README.md is up to date
Research "weierstrudel": EVM (huff) implementation of precompiles with lower gas fees
Revisit BN254 implementation
Define Integration tests for Deliverable 1 of Version 1
Update the rust specification (workflow) based on conversation about race conditions for relayers
Avoid typechain error: TypeError: Cannot read property 'outDir' of undefined
Plan for the whole project
Add clippy check into CI
Clean up and deduplicate type conversion functions between rust and solidity
Add arbitrum version of Rescue contract
- Arbitrum version of Rescue contract
- Document how to run tests against arbitrum dev net
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/107
Documentation for users
Optimize Rescue.sol
Solidity transcripts optimization, improvements
- Append point/Field Elems: serialize into bytes, then append
- little-endian vs big-endian in solidity
- overhead in ser/de serialize
- fields elems as u256, basic word in solidity
- Benchmark gas usage
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/122
Gas profiling tool
Evaluate alternatives for storing the owners' memo
For now we will reuse the system's code. Later we can have a look at more decentralized options such as:
- Whisper → Swarm?
- https://www.ethswarm.org
- libp2p
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/115
Define and configure an automated tool for documenting solidity code
Roadmap: Plonk verifier
Planning
TurboPlonk Verifier
- #70
- struct definition: Proofs, VerifyingKey #117, #151
- (among which fields like OpenKey and k_coset_repr can be shared across different vk)
- deseralizing proof into group and field elements
- Point & Field validity check #40, #64
- FS transcript
- basic append and get challenges API
- higher level append vk, evals API #171
- #181
- Algebraic operations
- #9
- #45
- #10 (single proof is just a special case)
Transaction Validity Verifier
References:
- Aztec's Plonk verifier
- Old gitlab issue
Measure gas for a function with view modifier
Design Generic ER20 token that emulates the freezing feature of AAP
Integration tests based on the smart contract
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/77
An effective way of documenting users' workflow could be by writing integration tests involving the AAPValidator and Wrapper smart contract. See Application UI Specification.
- Generate user keys
- Mint some units of an asset
- Transfer some units of an asset to another address and check balances
- Fail to transfer more units of an asset than an address owns
- Freeze an asset, fail a transfer, unfreeze, make the transfer successfully
- Build a transaction, but wait too long to submit it and observe the failure
- Fail a transfer because the relayer is unreachable
- Discover shenanigans, e.g. bogus ledger update
- Fail to submit a transaction that's already been submitted
- Submit several transactions all of which transfer a single asset and observe that only one succeeds
- Get the list of default asset types and whatever metadata comes with them
- Flip a bit in a transaction and observe failure to validate
- Wrap and unwrap some ERC-20 tokens
- Confirm that transaction history agrees with tests performed
- Demonstrate tracing
- Do something with owner memos
Full validator in Solidity
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/36
- #3
- nullifiers merkle tree
Analyze the problem of upgrading the code / data
Aggregated Polynomial Commitment Scheme
Owner's memo store
Decide the scope of the Relayer and who will work on it
Use solpp in order to see how much gas we can save on the Rescue implementation.
Revisit the use of the Nullifiers Merkle Tree inside the contract
The initial analysis suggested that it is cheaper in terms of gas to use a hashmap rather than a sparse Merkle tree to handle the nullifiers.
After a deeper inspection, @tri-joe noticed that the analysis is a worst case analysis and that on average and in practice the size of a non-membership proof for nullifiers is smaller, which may make the authenticated data structure competitive again.
One clear advantage of using a hashmap is that its implementation is simpler, while in addition to potential gas peformance gain, the nullifiers merkle tree is also appealing for making the smart contract look more like an AAP validator.
For now we will keep the hash map but come back later to this ticket when all the logic of the smart contract is implemented.
More details can be found here.
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/99
Test script for CI
Evaluate Certora product for finding flaws in our smart contract code
Store owner memos in call data
Use Typescript instead of javascript
Benchmarks still fail on Arbitrum
Explore tools for interacting with eth blockchain
[Meta] Gas optimizations
Ethers-rs abigen does not support nested structs
Check KZG ceremony SRS readiness
Smart contract: Implement the main algorithm for validating blocks and updating the blockchain state.
Transaction prices are not reliable when running geth locally
Reduce CI build time
Skeleton implementation of the smart contract
Development enviornment doesn't work with nix >= 2.4 on M1 Macs
Support for the native aarch64-darwin architecture is still young but if a person installs nix on Mac OS today they will get version 2.4 and will run into a few incompatibilities. These currently cause the nix-shell evaluation to fail.
https://gitlab.com/translucence/cap-on-ethereum/cape/-/issues/116
Wrapping NFTs on CAPE
Solidity coding style
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.