{"signature": "0x27b59b172e79ec6c4935e2aaccde03eaf46ca8e150f0dedc90b1bf555a0d9b3813ef3e53e8d0d60a256965b7007d2fdc02154089209a3c97f09a08a6002d81fb1b", "application": {"round": "0xe5B88c67fCd25f0a7BAD6cF7c5A5197e61BFd143", "answers": [{"type": "email", "answer": "valerio@turtleshell.xyz", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "@valerio_mnt", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "paragraph", "answer": "https://github.com/turtleshell-xyz", "hidden": false, "question": "Project GitHub Repo", "questionId": 2}, {"type": "link", "answer": "https://t.me/turtleshell_xyz", "hidden": false, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "paragraph", "answer": "Yes, we have participated in previous round. Here the link to our project: \n\nhttps://builder.gitcoin.co/#/chains/10/registry/0x/projects/0xbc0c38f75ec02f37af3c6cc5acef9951e0f69c0b49a26e9bf680b1fbcf4f76cb", "hidden": false, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds", "questionId": 4}, {"type": "paragraph", "answer": "**TurtleShell** is an open-source ecosystem of tools and frameworks designed to enhance security and operational transparency in Web3 development. Our core offerings include:\n\n- **Circuit Breaker SDK**: Built around the [EIP-7265 standard](https://eips.ethereum.org/EIPS/eip-7265) (co-authored by our team), this SDK enables Ethereum developers to integrate real-time security mechanisms like circuit breakers into smart contracts with minimal effort. It addresses the critical problem of **inaccessible smart contract defense mechanisms**, which leaves protocols vulnerable to exploits. By abstracting low-level complexity, the SDK allows developers to add safeguards against hacks (e.g., pausing suspicious token outflows) in minutes.\n\n- **Security Monitoring Dashboard**: A free, open-source React-based tool that provides protocols with real-time insights into contract health metrics (e.g., transaction volume anomalies, circuit breaker status). This solves two key inefficiencies: (1) the lack of **free, customizable security monitoring solutions** for Web3, and (2) the gap in **non-technical stakeholder visibility** into protocol safety.", "hidden": false, "question": "Provide a brief overview of your tool, library, or framework. What specific problem or inefficiency in the development process does it address?", "questionId": 5}, {"type": "paragraph", "answer": "### Reduced Barriers & Improved Efficiency\n- **Simplified Adoption**: The Circuit Breaker SDK reduces integration time for critical security features from days to hours. For example, developers can add a rate-limiting circuit breaker with <10 lines of code.\n- **Cross-Environment Support**: Optimized for both Hardhat (via [npm](https://www.npmjs.com/package/@markeljan/circuitbreaker)) and Foundry (used by 90% of adopters), ensuring compatibility with mainstream developer workflows.\n- **Metrics**:\n  - 300+ npm installs (Hardhat users).\n  - Estimated 15-20 weekly active developers (primarily Foundry users).\n  - 20% of production-ready projects adopt the dashboard for monitoring.\n\n### Enhanced Security\n- **Proven Effectiveness**: Case studies (e.g., [Curve Finance’s proposal](https://gov.curve.fi/t/proposal-improving-protocol-security-on-chain-realtime-hack-prevention/9441)) demonstrate how circuit breakers could have mitigated historical exploits like the $61M Curve pool hack.\n- **Non-Technical Empowerment**: The dashboard translates raw blockchain data into actionable insights (e.g., \"Token outflow spiked 400% in 1 hour\"), enabling protocol decision-makers to respond proactively.\n\n### Community Validation\n- Backed by ecosystem partners like **Arbitrum** (grant recipient) and featured in industry analyses ([CoinTelegraph](https://cointelegraph.com/learn/erc-7265-eth-token-standard-for-defi-security), [Unchained Podcast](https://www.youtube.com/watch?v=exyQFCKDOyM)).", "hidden": false, "question": "How does your project reduce development barriers, improve efficiency, or enhance the security of Web3 projects? Please provide specific examples or metrics if available.", "questionId": 6}, {"type": "paragraph", "answer": "  - 300+ npm installs (Hardhat users).\n  - Estimated 15-20 weekly active developers (primarily Foundry users).\n  - 20% of production-ready projects adopt the dashboard for monitoring.", "hidden": false, "question": "Describe the current usage and support for your tool within the developer community. This could include GitHub stars, downloads, or testimonials from developers.", "questionId": 7}, {"type": "paragraph", "answer": "### Development Roadmap\n1. **Q3 2024**: \n   - Launch \"FreezeAssetModule\" (alpha already live) for granular asset control.\n   - Add multi-chain dashboard support (starting with Arbitrum).\n2. **Q4 2024**: \n   - Integrate AI-driven anomaly detection for proactive threat alerts.\n   - Publish developer tutorials in partnership with Ethereum Foundation.\n3. **Q1 2025**: \n   - Conduct third-party security audits for new features.\n\n### Grant Allocation\n- **50%**: Retroactive rewards for open-source contributors (critical to maintaining momentum).\n- **30%**: Technical development (AI integration, multi-chain expansion).\n- **20%**: Security audits and educational content creation.\n\nBy funding these efforts, the grant will directly accelerate the adoption of EIP-7265, democratize access to security tooling, and strengthen the resilience of Web3 protocols.", "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 is a developer library for smart contract developers. This tool doesnt directly live onchain.", "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": 9}], "project": {"id": "0x5f35d5527cb492645559c5ff7bba6564228553f452f1c5a92036c4c6620bdbb9", "title": "TurtleShell", "logoImg": "bafkreidiygdq7eew5m7ndi5mrg46kk627zuo6nmya7f7dxtdbeug7fra4e", "metaPtr": {"pointer": "bafkreiccujkpc4offqfzlbargsvmwcolmdgwxghmeqqlf72umdr5faasl4", "protocol": "undefined"}, "website": "https://turtleshell.xyz/", "bannerImg": "bafkreiekfdnykpgabgifaoe7pj5dre7icuydojkz6h6xsgsxvrop4gmzuy", "createdAt": 1743006379055, "userGithub": "valeriofichera", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-26T16:28:00.486Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0xcb1688503ef5507d5c3e09fff53d559b9dee11440b1482c1f0d69204eedd6e274a75da3c0998ba5c751b854d3f780647b922855054c005a88456b6d52c2213c11b", "eip712Domain": {"types": {"Proof": [{"name": "@context", "type": "string"}, {"name": "created", "type": "string"}, {"name": "proofPurpose", "type": "string"}, {"name": "type", "type": "string"}, {"name": "verificationMethod", "type": "string"}], "@context": [{"name": "nullifiers", "type": "NullifiersContext"}, {"name": "provider", "type": "string"}], "Document": [{"name": "@context", "type": "string[]"}, {"name": "credentialSubject", "type": "CredentialSubject"}, {"name": "expirationDate", "type": "string"}, {"name": "issuanceDate", "type": "string"}, {"name": "issuer", "type": "string"}, {"name": "proof", "type": "Proof"}, {"name": "type", "type": "string[]"}], "EIP712Domain": [{"name": "name", "type": "string"}], "CredentialSubject": [{"name": "@context", "type": "@context"}, {"name": "nullifiers", "type": "string[]"}, {"name": "id", "type": "string"}, {"name": "provider", "type": "string"}], "NullifiersContext": [{"name": "@container", "type": "string"}, {"name": "@type", "type": "string"}]}, "domain": {"name": "VerifiableCredential"}, "primaryType": "Document"}, "proofPurpose": "assertionMethod", "verificationMethod": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb#controller"}, "issuer": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb", "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1"], "issuanceDate": "2025-03-26T16:28:00.486Z", "expirationDate": "2025-06-24T16:28:00.486Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD478230AC12b747d9796222B8Ac9989ABEDf5B00", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextGithubOrg#turtleshell-xyz#78494380", "nullifiers": ["v0.0.0:W0Z+Nts6fK2uuVA4hXF+d5uFtk3SA2aMxLcyJ0fMEMs="]}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-26T16:28:33.127Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0xc4cd55177cc40a2a7a0ebb9caf433c40a032d2a00393e22835b749035f1618c2738e47945e98e854f2c36a4d81d85f268f6e891ae8f557f6b1221fabf7d31e851b", "eip712Domain": {"types": {"Proof": [{"name": "@context", "type": "string"}, {"name": "created", "type": "string"}, {"name": "proofPurpose", "type": "string"}, {"name": "type", "type": "string"}, {"name": "verificationMethod", "type": "string"}], "@context": [{"name": "nullifiers", "type": "NullifiersContext"}, {"name": "provider", "type": "string"}], "Document": [{"name": "@context", "type": "string[]"}, {"name": "credentialSubject", "type": "CredentialSubject"}, {"name": "expirationDate", "type": "string"}, {"name": "issuanceDate", "type": "string"}, {"name": "issuer", "type": "string"}, {"name": "proof", "type": "Proof"}, {"name": "type", "type": "string[]"}], "EIP712Domain": [{"name": "name", "type": "string"}], "CredentialSubject": [{"name": "@context", "type": "@context"}, {"name": "nullifiers", "type": "string[]"}, {"name": "id", "type": "string"}, {"name": "provider", "type": "string"}], "NullifiersContext": [{"name": "@container", "type": "string"}, {"name": "@type", "type": "string"}]}, "domain": {"name": "VerifiableCredential"}, "primaryType": "Document"}, "proofPurpose": "assertionMethod", "verificationMethod": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb#controller"}, "issuer": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb", "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1"], "issuanceDate": "2025-03-26T16:28:33.126Z", "expirationDate": "2025-06-24T16:28:33.126Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xD478230AC12b747d9796222B8Ac9989ABEDf5B00", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextTwitter#TurtleShell_xyz", "nullifiers": ["v0.0.0:b3Zl5jcbQZSbLvx5k93v/eixhWV1UEIY4+onrjVbML4="]}}}, "description": "Imagine:\n\nOne day you wake up and your protocol got exploited …maybe you heard of ERC-7265 as attempt to end that quite real nightmare.\n\nWith TurtleShell we are aiming to give every Smart Contract holding Assets the necessary bolster to prevent unintended outflow.\n\non-chain realtime hack prevention\n\nwe are building on-chain firewalls\n\nWhat is an On-Chain Smart Contract Firewall?\n\nSmart contract hacks have been plaguing DeFi protocols, bridges, and more.\n\nToday, in order to defend themselves, protocols perform audits, open bug bounties, and implement monitoring.\n\nAll of these steps are absolutely crucial. Nevertheless, whenever a vulnerability is discovered by an attacker, most exploits can drain funds in a very short period of time, sometimes even within a single transaction. To prevent these hacks from happening, we need an on-chain tool.\n\nYou can think of the Smart Contract Firewall as an additional layer of security for DeFi protocols.\n\nOur Firewall is a set of Solidity Smart Contracts that allow you to:\n\nDefine critical parameters for your protocol (e.g., TVL) and track these parameters over time.\n\nDetect that a transaction (or multiple) is causing the protocol to operate outside its normal activity (e.g., unusual liquidity outflow, indicative of a potential hack happening).\n\nImplement a set of protective measures, including transaction blocking, protocol pausing, fund freezing, or controlled fund withdrawal, before the transaction is committed and funds exit the protocol.\n\nThe Firewall provides a way to detect abnormal changes in your protocol directly on-chain, that could be indicative of a hack. That means that you can act upon abnormal activity, whenever it occurs, directly on the blockchain.", "lastUpdated": 0, "projectGithub": "turtleshell-xyz", "projectTwitter": "turtleshell_xyz"}, "recipient": "0xD478230AC12b747d9796222B8Ac9989ABEDf5B00"}}