{"signature": "0x32539858bf2f9a3783afd3ef1da62ae7a5e526999e6c3241f7bb14abe80c1ab217d519115f5b1209ed3e3e934e387fcc0aed82415755b3be6743929be0b06be21b", "application": {"round": "0x145052e87140b7309f6ee18ba12fc187560d5d89", "answers": [{"type": "email", "answer": "contractlevel@proton.me", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "contract_level", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "short-answer", "answer": "https://github.com/contractlevel/compliance", "hidden": false, "question": "Project Github Repo", "questionId": 2}, {"type": "link", "answer": "", "hidden": false, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "paragraph", "answer": "no", "hidden": false, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile to prior rounds.", "questionId": 4}, {"type": "paragraph", "answer": "It enables traditional institutions to interact with publicly accessible smart contracts by enforcing the same regulatory standards they are used to.\nFor example, banks and traditional asset managers are unwilling to participate in DeFi protocols because any sanctioned/illicit actor can also participate. These traditional institutions must follow strict laws forbidding them from engaging with such actors. Contract Level Compliance gives them the assurance that non-compliant actors will never be present in onchain systems.", "hidden": false, "question": "How does your project contribute significantly to the Ethereum network's infrastructure? Please provide specific examples and metrics if available.", "questionId": 5}, {"type": "paragraph", "answer": "No user data other than a \"yes\" or \"no\" to the question \"Has this address completed KYC with a licensed entity?\" is revealed onchain. User privacy is paramount.\nAs well as this, automating the compliance procedure for transactions is something so far unseen in public smart contracts.", "hidden": false, "question": "Describe any pioneering development work in your project, particularly in enhancing privacy, interoperability, or user experience.", "questionId": 6}, {"type": "paragraph", "answer": "It addresses the problem of traditional institutions not touching public smart contracts due to regulatory concerns.\nThe only current alternatives provide compliance offchain, monitoring transactions AFTER they happen. Whereas the Contract Level approach ensures non-compliant transactions never execute in the first place.", "hidden": false, "question": "What specific problems or challenges in the Ethereum ecosystem does your project address? How does your solution improve upon existing alternatives?", "questionId": 7}, {"type": "paragraph", "answer": "The next step is integrating Concero V2 for fast, cost effective, and decentralized crosschain interactions. \nGrant funds will be used to pay for private security audits (at least 2 with independent, leading firms), followed by a competitive audit, and then establishing a bug bounty.", "hidden": false, "question": "Outline your project's roadmap and how the grant funds will be used to achieve your development goals.", "questionId": 8}, {"type": "paragraph", "answer": "This project contributes to the decentralization of Ethereum by enabling a much wider market to participate, who were previously unable to.", "hidden": false, "question": "How does your project contribute to the decentralization and security of the Ethereum network?", "questionId": 9}, {"type": "paragraph", "answer": "Not yet deployed.", "hidden": false, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 10}], "project": {"id": "0xe826b1a26848a3c370bf02021a95b6acf6786256f31238a1defe323bb50360af", "title": "Contract Level", "logoImg": "bafkreibkozijar67fd2mknpzyh6zemtep5zhpxbqzwcs4calvziwmkuoom", "metaPtr": {"pointer": "bafkreigzi35rm4rodj5wmkigmbmecyyqwwqla54ikpe3x433nqzaghbz6i", "protocol": "undefined"}, "website": "https://contractlevel.com", "bannerImg": "bafkreieqbiyqhhcrecd4fyl6ihwdlebuao5zv4p6sncf5mxsjpmrkpvony", "createdAt": 1742296190993, "userGithub": "contract-level", "credentials": {}, "description": "Contract Level Compliance (CLC) embeds regulatory compliance directly into smart contracts. It achieves this by using Chainlink to check if an onchain user has completed KYC (Know Your Customer) with a licensed entity, before executing custom smart contract logic on their behalf. This ensures only compliant users can participate in regulated smart contracts.\n\nNo user data is ever revealed onchain except for a \"yes\" or \"no\" to the question \"Has this user completed KYC with a licensed entity?\"\n\nThis approach differs from offchain compliance services which monitor transactions AFTER they happen. With Contract Level Compliance, non-compliant transactions are never given the opportunity to execute.\n\nGrant money is intended for security audits and establishing a bug bounty program.\n\nCLC aims to have a transformative impact by:\n\nUnlocking institutional engagement: By making smart contracts regulatory compliant, CLC enables traditional financial institutions to confidently adopt blockchain technology.\n\nDemocratizing access: It allows any KYC-verified individual to participate in regulated DeFi, broadening financial service opportunities.\n\nDriving adoption: With regulatory clarity increasing globally, CLC positions itself as a critical infrastructure component, supporting the future of compliant blockchain applications.\n\nFurther reading:\nWhitepaper: https://www.contractlevel.com/whitepaper.pdf\nIntroductory article: https://medium.com/@contractlevel/introducing-contract-level-compliance-91806137c88d", "lastUpdated": 0, "projectGithub": "contractlevel", "projectTwitter": "contractlevel"}, "recipient": "0xAE25a61c90C390c4a2bb832b2BeaD2f2Fb26A4C8"}}