metadata: {"signature": "0x2a85b25b19cb0d5687d5116563454c62dc95bae1892e5699925519f46c1d740b2711c63408fa9a2ccf71a32bbec8b827482f678cbf6890e889b419be4dbeb0351b", "application": {"round": "0x274554eb289004e15a7679123901b7f070dda0fa", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "O57cEX1QqYRCzYKG+1zwvclcQczAryC0YKkDfjD0c/8wFAr1XY5NfhcQqJkVKlEz", "encryptedSymmetricKey": "3bf16c8ad01d82a26c43f2f1c04232eccc16444dba2438099b3169b775b65f914ba88d70575e3e052cf5678a77d20913d4c18caabec85c9d3876affe7c46615e6534c010458fe2bd1769a607ac69becb6a7c277d5d717b6d36f39523449396b4318ebdc3eadc513c2341535f1abe169797605b4c011169ab656eca5d20ca13240000000000000020c4faaef92d59b86ba4cb55985ee53ddc49778500e7e7432553ae3e10b05bbe3fb81b934c204a8b447a7e1cb43b6d9486"}}, {"type": "short-answer", "answer": "nothing", "hidden": false, "question": "Previous project funding sources (VC, grants, token sales, etc)", "questionId": 1}, {"type": "number", "answer": "0", "hidden": false, "question": "Total prior funding for project in USD", "questionId": 2}, {"type": "number", "answer": "2", "hidden": false, "question": "Total team size", "questionId": 3}, {"type": "number", "answer": "3", "hidden": false, "question": "How old is the project? (Months)", "questionId": 4}, {"type": "address", "hidden": true, "question": "If you participated in past grant rounds using a different project payout wallet address, please share it here:", "questionId": 5, "encryptedAnswer": {"ciphertext": "SK01KSWtZsNVCyltI4oEdSY+40F/OtmPokjdpqc+7Js=", "encryptedSymmetricKey": "ffa3ddd77935e0726e37446c2ef0b4a7b30be70d9e3c4796b2f52897d1cb14b91cc78c90d6508895cc9a4b622b468f0511948e7bebf6ae471ea78c2cbab04cefb89bc5652d775fc57f3d50733e6671343f77ddc88bcb66eaf494579b2915b384bf6bf8ad86333c85c12fab6265e78c4c6b509457e9d9e93842039ff8529c437a00000000000000204607fc30f68ee13d59762df33c7e41082f0739e0321cb1cb7fdf5e50f2ef3bb7c15d7d3d33901bae797c5af86a46b9aa"}}, {"type": "paragraph", "hidden": false, "question": "Profiles or socials of other main team members publicly associated with project", "questionId": 6}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Have you read and confirmed your grant abides by the Program General Eligibility Policy? https://gitcoin.notion.site/Gitcoin-Grants-Beta-Round-Eligibility-b7fca9fd3c26450b89ded11caaa6497f", "questionId": 7}, {"type": "paragraph", "answer": "This project implements [the DECO paper from Cornell University](https://arxiv.org/abs/1909.00938) using our fork of [lurk-rs](https://lurk-lang.org), both of which is about zk tech. a limitation in the original paper is that prover can't efficiently prove a statement about JSON when there's collision of keys. The keys had to be globally unique. That is, `{\"x\": {\"a\": \"b\"}, \"y\": {\"c\": \"d\"}}` is fine but `{\"x\": {\"a\": \"b\"}, \"y\": {\"a\": \"d\"}}` is not. We are trying to mitigate this problem by utilizing recent advancement in IVC scheme such as Nova. We implement fully SNARKed JSON parser, combine it with the original DECO scheme. It allows the prover to prove that a certain URL e.g. 4horsemen.com/apocalypse has indeed returned a JSON that has a certain key-value pair e.g. `\"color\":\"black\"` deep inside a certain path e.g. `horsemens[2].horse.skin` All of our work funded by the grant will be made open source.", "hidden": true, "question": "How does your project fit into the ZK Tech round eligibility criteria? ", "questionId": 8}, {"type": "paragraph", "hidden": false, "question": "If you've participated in past grant rounds, please share any new updates or milestones from the prior months", "questionId": 9}, {"type": "paragraph", "hidden": false, "question": "Anything else you'd like to share about your project, previous work, or other project affiliations? Anything you'd like to add that has not been covered?", "questionId": 10}, {"type": "multiple-choice", "hidden": true, "question": "Does 50% of your team reflect the diversity of the community your project serves with a particular emphasis on including women, Black, Indigenous, and People of Color (BIPoC), individuals with disabilities, and members of the LGBTQ+ community?", "questionId": 11, "encryptedAnswer": {"ciphertext": "t585smBdE4b8/1SDunpRnMnjixp2qUv8lzq2e1Q6DoY=", "encryptedSymmetricKey": "db3e06ab0d1b8fa84b230e72fb1e1d7085c3e1f0c68c1f52cb32aedd746d75754fd6fe7a42ce5ae98541f25e26cc37194aed2f0bfc24a7beeb6664e2ea99dadb802228e7adbb4ca69e0575939e9cfdf5a724cc01e748035b524697fe119f4f879324fe449a90931dfc9011463ef310baa432d8a954d96b5015abc2365db7d1b3000000000000002092a335822f77f7de50c25ccded7fbb41f4bc0e81e81eb8da7a53d42ef8c0b748e8271011de305cfaa5bee649c6cfc08f"}}], "project": {"id": "1:0x03506eD3f57892C85DB20C36846e9c808aFe9ef4:453", "title": "chokepoint", "logoImg": "bafkreid6xbaom37fnurpouwz5wckdodnciv3bzeipph36uk27ay6lmzaau", "metaPtr": {"pointer": "bafkreie2f7wx6nno2hp3ncms52tifouflm33bv23uq7xqlpl3rjelldv5i", "protocol": "1"}, "website": "https://chokepoint.exchange", "bannerImg": "bafkreieku2kopspxqvlvr4hpj6tnrjegkxny5vaqcjoka6oca7xqhdztey", "createdAt": 1681761283669, "userGithub": "chokepoint-exchange", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..oYuLcJtipHxXldkjwplX8HNzFV0CROWF5MdkjCHIk2B9aBLCADi_UdxCAXepYyC2YbDU9N38HNO8nyPmWNwnAg", "type": "Ed25519Signature2018", "created": "2023-04-18T18:21:26.919Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-18T18:21:26.919Z", "expirationDate": "2023-07-17T18:21:26.919Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x134538aa584d2F087cea2385B4f738336319FD83", "hash": "v0.0.0:AGaX127h+4iymXe4L0GXaToTOJeX+aYo4mmSEwQ+/lw=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#chokepoint-dao#130933074"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..rW5RE67krytYJpIA5og3CtQ_0kOgreEE6zUmDasHh_josL4rNwMScNs3NyziQxR-lFf5KpFTgmHo5ff9RE1ECw", "type": "Ed25519Signature2018", "created": "2023-04-18T18:12:40.617Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-18T18:12:40.616Z", "expirationDate": "2023-07-17T18:12:40.616Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x134538aa584d2F087cea2385B4f738336319FD83", "hash": "v0.0.0:GEocmprcxL1sJ9No3kPlZfRcNLh4tPsytm7dVXZnma0=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#chokepoint_dao"}}}, "description": "# chokepoint.exchange\na trustless bridge between CBDC and ETH\n# What we're BUIDLing\n## Problem: anti-crypto government\nRecently, the law enforcements are tightening their attitude towards crypto industry. [FDIC has forcibly closed a crypto-friendly bank Signature Bank without telling them why.](https://decrypt.co/123346/signature-bank-shut-down-anti-crypto-barney-frank) [SEC has sent a wells notice for Coinbase without disclosing what\\'s wrong.](https://www.coinbase.com/blog/we-asked-the-sec-for-reasonable-crypto-rules-for-americans-we-got-legal) [Kraken was forced to shut down their staking service due to regulatory pressure.](https://www.theverge.com/2023/2/9/23593183/kraken-staking-sec-settlement-penalties-crypto-interest) [Elizabeth Warren blames crypto for the collapse of Sillicon Valley Bank somehow.](https://twitter.com/ewarren/status/1636488503197413377) It seems that FTX has damaged the sentiment towards crypto among the government insiders severely.\n## Consequence: incoming crackdown\nThe last straw that will break camel's back is for Gary Gensler to declare ETH a security as opposed to a commodity. The legal implication of this would be the biggest since the inception of Ethereum. [He has been talking about his intention to do so publicly for a while.](https://www.protocol.com/newsletters/protocol-fintech/gensler-ether-security) If it were to finally happen, every single exchange that lists ETH might be deemed as illegal. [The state of New York just sued Kucoin for this exact reason.](https://www.coindesk.com/policy/2023/03/09/new-york-attorney-general-sues-crypto-exchange-kucoin-alleges-ether-is-a-security/) [SEC just charged Bittrex saying premined coins are security.](https://www.sec.gov/news/press-release/2023-78) Don't ignore the canary in a coal mine. [The entire market will collapse unless we do something.](https://graymirror.substack.com/p/bitvana-or-the-bitcaust)\n## Solution: fiat dex\nTo save cypherpunks from the government overreach, we are developing chokepoint.exchange, the first trustless non-custodial NoKYC OTC DEX that supports fiat natively without relying on stablecoin which is a single point of failure SEC can easily crack down on. It utilizes the combination of transport layer security and zero knowledge proof outlined in [a paper from Cornell University](https://arxiv.org/abs/1909.00938) to prove on-chain that the buyer has sent the seller CBDC. CBDC transfers to buy ETH on chokepoint.exchange will look indistinguishable from ordinal individual-to-individual transfers, thus it is uncensorable by the government.\n# How we build it\nno CBDC wallet for consumers has been released yet, but we can assume that it will be accessible through the current internet stack, IP, TCP, HTTP, TLS... Thus verifying on-chain that CBDC transfer has happened could be reducible to verifying on-chain that a certain response has came back from a HTTP server the government operates. Turns out [this exact problem was nailed by a team from Cornell University in 2019](https://arxiv.org/abs/1909.00938), and subsequently [improved by a team from University of Lisbon in 2022](https://eprint.iacr.org/2022/1774.pdf).\n## 2023: libchokepoint\nWe aim to release an open source implementation of the paper by Rust and Lurk in 2023.  It enables the prover to prove to the verifier that the server has responded to the prover's HTTP request with a HTTP response encrypted with a TLS session key derived from the server's TLS certificate. The first release will prove about a whole response from the server, thus it is succinct but not zero knowledge, as it might leak the verifier some critical private information about the prover.\nThe second release will add zero knowledge property. Assuming the response is structured in JSON or XML, it will prove that a certain key in the response equals to a certain value, without disclosing any values of other keys.\n## 2024: chokepoint.exchange\n libchokepoint enables a buyer on chokepoint.exchange to prove to verifiers that he has sent the seller x amount of CBDC, without disclosing any other information. The slight problem here is that it implements an interactive protocol, thus smart contracts can't be a verifier. We mitigate this problem by utilizing EigenLayer restaking. Each restaked node will play the interactive game with buyers as a verifier, verify whether or not the the buyer has actually sent the seller CBDC, vote for the verification result on the chain. The restaked nodes who have voted for the majority will be paid transaction fees. Those who have voted against the majority will be slashed.", "lastUpdated": 0, "projectGithub": "chokepoint-dao", "projectTwitter": "chokepoint_dao"}, "recipient": "0x134538aa584d2F087cea2385B4f738336319FD83"}}