{"signature": "0x40ddc870287bff39fc7ac8a7aa6cf3395efd032b494aedb5fcf1c92a63890d6f40f6dd59aff769e8aadb44ef76ed5bd43ec0983d0bdafefd83f217403fbcc1311b", "application": {"round": "0x3aa3c6cc0004b7366a12b8e4262015af525531a9", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "fnfIB2A+1BfkL8PRjAE3hU8dign+bZaqzJvOmVN3aKxNsMck1WaOX/R327L9Ka/9", "encryptedSymmetricKey": "e17285961bbcde1bcc6518dd414755e107320e66bd5c696c46d39e6ebe950a83f44daa6f65985b80e172cf4a274dc4014a72d961db38bd0fd0767cb49cef2a86589c37b5495c8038ea6f9f535f46224d302b609b9eb01e6adb2d23f7235567ad7ee88357ebff6626a4295a24c94da454f15ced1fe361c274fddedf4c9bb88b5700000000000000208be64e6248569a71b0d7b1a35a0da8fa0afe221089d565cdbdb1549dfabe9158b051ae0ea3c6306a5969feb696878c94"}}, {"type": "number", "answer": "2", "hidden": false, "question": "Team Size", "questionId": 1}, {"type": "short-answer", "answer": "@BingbongChef", "hidden": true, "question": "Telegram Handle", "questionId": 2}], "project": {"id": "0x718952dc57ba781233da544d115b8ae6ede3c7e59f06a6059c9c94bd3fe8c8e2", "title": "Eire Swap", "logoImg": "bafkreihqfrw5b6knnr5vgcsvvpwvgcrjpi2rlrrnthopbompivcz73nvx4", "metaPtr": {"pointer": "bafkreigb2abznv2pvicm5sgxed3xlbfxxjyqojpyyzm4jsznj3vltcr2cu", "protocol": "undefined"}, "website": "https://ethereum-dub-2024-frontend.vercel.app/", "bannerImg": "bafkreibwwtlmieovpzwg2bsugunysalap5fdrp7hzso4bbi656hbiqah2q", "createdAt": 1718051872295, "userGithub": "mcgraneder", "credentials": {}, "description": "Concept\nEireSwap will be a Uniswap like Dex, but where users have their own built-in smart wallet. The wallet utilises account abstraction primitives as well as cryptographic protocols, for example Schnorr Proof Of Knowledge, to take advantage of zero-knowledge (ZK) proofs in smart contracts. This facilitates extension of modern Automated Market Maker (AMM) protocols as utilised by Uniswap or Pancakeswap, so that users can get the advantages resulting for AA, like batching transactions and custom fee tokens. In this way, the typical swap flow seen in today's AMMs can be optimised into a one-signature flow. This is in addition to enabling one-signature cross chain trades secured by our ZK protocol. \n\nOne-signature flow\nThe main idea is to create a wallet contract that a user can own which will have a deterministic address: a smart wallet. This smart wallet acts a vessel, the means to execute their swap transactions through a relayer. Since a user's wallet contract’s address is deterministic, they can use it on any chain to execute any transaction they want on these chains in one flow.  We also extend this to allow a user to create a unique private/public key pair for their wallet contract. With this, the wallet can implement its own ECDSA signature (for on-chain SC signing) and ZK proof algorithms. The private key is derived in secret off-chain and the public key is used as the salt in the deterministic CREATE2 smart contract address. Thus the user’s Externally Owned Account (EOA), smart contract wallet, and smart contract public key are all intrinsically linked.\n\nCurrently AMM swap flows require an approval, the swap transaction (tx) itself, as well as the restriction of paying gas tokens in native currency. If we abstract this tx flow to a user’s smart wallet we can essentially batch all of these transactions together and execute them in one flow. This has another benefit of giving the user the option to pay the gas fees in a custom gas token such as USDT.  In this case, this is all one transaction from the user’s perspective. In the contracts, the mechanism includes the payment as an additional transaction after the swap that sends USDT from the users EOA account to the relayer, and the relayer pays the native gas for the user within the transaction.\n\nCross Chain swaps A unique feature that this design makes possible is the ability for the user to also execute cross chain swaps in a one-signature flow. This works in a two step process under the hood. There is both an origin chain transaction and a destination chain transaction; both are executed for the user by the relayer as components of a one-signature transaction flow. As an example, let us imagine the user has USDT on Ethereum Mainnet and wants to swap it for WBNB on Binance’s BNB chain.  Furthermore, let us assume that the relayer has access to USDT liquidity on both chains.\nIn this cross chain flow, the user will build a batched transaction where they send USDT to the relayer’s smart wallet on Ethereum Mainnet. After this is done, the relayer will run a verification protocol. The verification will assert that the contract states are correct, meaning that the user’s USDT balance has gone down by the amount they want to swap (plus fee) and that the relayer's balance has gone up by the swap amount (plus fee). Upon successful completion of this verification, the relayer will execute the destination chain transaction themselves and send the end WBNB from the relayer’s smart wallet to the user’s smart wallet address on BNB.\n\nIn this flow the relayer can be considered the source of liquidity on all chains that cross chain swaps go through. USDT will be a gateway asset that will be the used for liquidity on all supported chains. The net relayer’s balance of USDT on all chains remains constant here, but in a particular swap across two chains, the funds that the relayer uses on the destination chain’s tx will be balanced out by the funds they gain from the user on the origin chain.", "lastUpdated": 0, "projectGithub": "mcgraneder/ethereum-dub-2024", "projectTwitter": "BingbongCh82440"}, "recipient": "0xaB53512726f66EAEf2830a1BAA6aa69FE3A66914"}}