Skip to content

Commit

Permalink
Update README.md with asn details
Browse files Browse the repository at this point in the history
  • Loading branch information
Divide-By-0 authored Jun 8, 2024
1 parent 4edc719 commit f6aeae6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -348,7 +348,7 @@ Ads bring in surprisingly low revenue -- I hope that the bounty makes it worth y
- **Quantum Proof Keypairs on Ethereum with AA**: Implement ECDSA in a STARK and integrate into EIP 4337 like this [ethresearch post suggests](https://ethresear.ch/t/quantum-proof-keypairs-with-ecdsa-zk/14901), allowing anyone to move their money to a quantum-safe wallet with ECDSA, without having to switch keypair algorithms.
- **Recursive Verifier for Vole in the Head**: Thanks to Nanak for the idea. Holonym has a very fast [browser prover for circom](https://github.com/holonym-foundation/vole-zk-prover) based on the vole in the head paper, but proofs are 10mb. Write a recursive verifier for these proofs in groth16 so that you can aggregate them efficiently to post on-chain.
- **Circom -> Binius Compiler**: People are working on Binius VMs, but it would be great to automatically compile circom into a Binius circuit.
- **PDF/Document Parsing**: Inspired by Sachin and Richard. Build an ASN.1 parser in ZK and combine it with Reef to prove things about Docusigned signed PDFs. The easiest thing would be to diff a doc with a signature and a doc without one, and see if the diff is small enough to extract and prove. Would allow you to get contracts on-chain.
- **PDF/Document Parsing**: Inspired by discussions with Sofiane, Sachin, and Richard. Build an ASN.1 parser in ZK and combine it with ZK Regex to prove things about Docusigned signed PDFs or PDFs in email attachments. The easiest thing would be to diff a doc with a signature and a doc without one, and see if the diff is small enough to extract and prove. Would allow you to get contracts on-chain.
- **Truly random NFT drops** The problem is that you can predict randomness and mint the best NFTs by simulating the chain. Some solutions [exist](https://www.paradigm.xyz/2021/10/a-guide-to-designing-effective-nft-launches#phase-4-metadata-reveal). However, a better way to do this is, on mint, you generate a 24+ second (2+ block) VRF seeded by the previous blockhash. Minters pay gas upfront for anyone to send a second reveal transaction. MEV searchers calculate the VDF and send the result to the chain for that gas money + a small bonus, in return for updating the NFT values on chain first. More description at this hackmd: https://hackmd.io/xgR6mtWyQYC_SZYtZTdoDA .
- **Futarchy On-Chain**: Build the first prediction markets for governance, like [MerkleDao](http://www.ralphmerkle.com/papers/DAOdemocracyDraft.pdf)'s plan. Add features like also betting reputation points proportional to money, where higher reputation leads to higher investment limits, which will help institutional players to be long-term aligned with the project instead of financial manipulators. This will also help elect legislators who consistently have high reputation, meaning they accurately predict long term impact of legislation on people.
- **Anvil Tenderly Debugger**: Make it so that a failed transaction on Anvil replays that transaction on the forked chain from that block on Tenderly, and can show the simulated error in an easy-to-debug way.
Expand Down

0 comments on commit f6aeae6

Please sign in to comment.