{"signature": "0xba15bb419e4fb88af42e4316d2b1102bbfd5deea358119f96dbe7d271be2d431549f5121d5ddea5d69dc239ce462f5ea8e68b5fa13bc9fc26624fe8bb539c2081c", "application": {"round": "0xe5B88c67fCd25f0a7BAD6cF7c5A5197e61BFd143", "answers": [{"type": "email", "answer": "jacob.hanouna@particlecs.com", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "@BlueSpaceOut", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "paragraph", "answer": "https://github.com/PracticalParticle/particle-core", "hidden": false, "question": "Project GitHub Repo", "questionId": 2}, {"type": "link", "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 associated with previous rounds", "questionId": 4}, {"type": "paragraph", "answer": "The Guardian AA ecosystem tackles critical security and usability inefficiencies in Web3 development with a layered approach:\n\nFirst, the core MultiPhaseSecureOperation library serves as a foundational security design system. It provides a standardized, battle-tested framework for implementing multi-phase security, role-based access control, and time-delayed operations within smart contracts. This library eliminates the need for developers to reinvent complex security logic, significantly reducing the risk of vulnerabilities and streamlining the development process for secure decentralized applications.\n\nSecond, the Guardian AA framework provides secure and easily auditable smart contracts that leverage the MultiPhaseSecureOperation library and extend OpenZeppelin’s Ownable contract. These contracts offer account abstraction by replacing the traditional single-key vulnerability model with a multi-phase security architecture and implement distinct roles and a well-defined operation workflow to move past simple smart contract wallets. This promotes enhanced security, and clear separation of access privileges for different roles.\n\nFinally, SandBlox is a modern development platform designed to simplify and accelerate the creation of secure Web3 applications built on Guardian AA. SandBlox provides pre-built, encapsulated \"blox\" – reusable blockchain components powered by Guardian AA – that developers can quickly assemble and deploy, allowing them to focus on application logic rather than underlying security complexities. SandBlox streamlines development and reduces barriers to entry, further accelerating the creation of robust, user-friendly Web3 experiences.\n\nGuardian AA + Security Library:\nhttps://github.com/PracticalParticle/particle-core\n\nSandBlox:\nhttps://github.com/PracticalParticle/sand-blox\n", "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": "Guardian AA and SandBlox significantly reduce development barriers, improve efficiency, and enhance the security of Web3 projects:\n\nReduced Development Barriers: SandBlox provides pre-built, encapsulated \"blox\" – reusable blockchain components powered by Guardian AA – enabling developers to quickly assemble and deploy secure dApps without writing complex security logic from scratch. Example: Instead of building a secure vault system, a developer can use a pre-built \"vault blox\" within SandBlox, instantly providing secure asset storage and management.\n\nImproved Efficiency: Guardian AA streamlines development with its MultiPhaseSecureOperation library, offering a standardized security design system. This eliminates the need for developers to invent their own security patterns, saving time and reducing the risk of introducing vulnerabilities. Example: The two-phase operation workflow in Guardian AA provides a ready-made pattern for critical operations like ownership transfers, ensuring a consistent and secure approach.\n\nEnhanced Security: Guardian AA's core innovation is its multi-phase security architecture, which moves beyond the single-key vulnerability of traditional accounts. Role-based access control and time-delayed operations provide layers of protection against key compromise and unauthorized transactions. Example: The time-delayed security feature allows users to cancel unauthorized transactions during the waiting period, preventing asset loss even if a key is compromised.\n\nClear Separation of Responsibilities: Guardian AA allows users to define specific permissions with various roles to manage the account, preventing any single role from having complete control. Example: The recovery role is the only role that can initiate the ownership transfer process, providing a secure recovery mechanism for both lost and compromised keys while preventing unauthorized individuals from seizing control.\n\nThese features of Guardian AA and SandBlox, combined, empower developers to build more secure and robust Web3 applications with greater speed and efficiency.", "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": "As a newly launched open-source project on GitHub, Guardian AA and SandBlox are in the early stages of community adoption. We are actively engaging with developers, providing documentation and examples, and fostering a collaborative environment. While we don't yet have metrics like GitHub stars or download numbers to share, we're excited to build a strong and supportive community around our tools, focusing on real-world usage and developer feedback to drive future development. We believe the unique security features and development efficiencies offered by Guardian AA and SandBlox will resonate with developers seeking to build more secure and user-friendly Web3 applications.", "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": "Project Roadmap\n\nThe Guardian AA project has a multi-stage roadmap focused on continuous development, community engagement, and expansion:\n\nPhase 1: Core Protocol Development (Completed): Development of core account abstraction mechanisms, including role-based access control and time-delayed operations. Creation of proof-of-concept smart contracts. This has already been completed.\n\nPhase 2: SandBlox Alpha Release & Community Adoption (Ongoing): Launch of the developer-friendly open-source approach with the SandBlox application in Alpha. Focus on community engagement and adoption of security solutions.\n\nPhase 3: Core Contract Refinements & Security Audits (Next 6 Months): Focus on core contract refinements and implementing security audits for the core security protocol\n\nPhase 4: SandBlox Beta Release and General Availability of Guardian AA (Next 12 Months): Release SandBlox for beta testing and general availability of Guardian AA.\n\nPhase 5: Exploration of Additional Security and Compliance Solutions (Long-Term): Research and development into additional security and compliance solutions.\n\nUse of Grant Funds\n\nThe grant funds will be primarily used to achieve the goals of Phase 3: Core Contract Refinements & Security Audits. Specific allocations include:\n\nSecurity Audits: A significant portion of the funds will be allocated to engaging reputable security firms to conduct comprehensive audits of the Guardian AA core security protocol. This will help identify and address potential vulnerabilities, ensuring the security and reliability of the solution. Approximate allocation: 40% of grant funds.\n\nCore Contract Refinements: Funds will be used to improve and refine the core contracts of the Guardian AA based on community feedback and audit findings. This includes adding new features and optimizing performance. Approximate allocation: 30% of grant funds.\n\nDeveloper Documentation and Resources: A portion of the funds will be dedicated to creating comprehensive developer documentation, tutorials, and example code specifically focused on the Guardian AA contracts. This will lower the barrier to entry for developers and encourage wider adoption. Approximate allocation: 20% of grant funds.\n\nCommunity Engagement and Outreach: Funds will be used to support community engagement activities, such as hackathons, workshops, and online forums. This will help build a strong community around the Guardian AA project and encourage collaboration and innovation. Approximate allocation: 10% of grant funds.", "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": "Our core design empowers users with unparalleled flexibility and control by allowing them to deploy our contract infrastructure directly across the entire EVM ecosystem. This means users choose the EVM-compatible network that best suits their needs and deploy Guardian AA contracts directly from their own accounts. Because of this user-centric approach we currently don't maintain a centralized list of deployer addresses", "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": "0xf8e3771e90d1bdb333bd2c23db0feda10e046aa09ffc94ffd89ebcbe8089fb9f", "title": "Guardian Account Abstraction", "logoImg": "bafkreifzy4rmgexrs6brml2wlux7fq66y7pleo4z55yrap6j64ans6523y", "metaPtr": {"pointer": "bafkreiaub2kx545s43fjvb27ovaaqzqqzyula4fkyl4275rdynjzh4votm", "protocol": "undefined"}, "website": "https://aa.particlecs.com/", "bannerImg": "bafkreid5rynxdey2ige5znltvkxneysbq7sfmyd26a4g457abyxejpzs6q", "createdAt": 1742836646792, "userGithub": "JaCoderX", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-24T17:22:36.010Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0x66420676d8241e9a3baf9ca67aa9867c6dda71de9bb609c83f3efb5e31dbadb60e1236557caf80932bba6a3ab26226ce671cf8d8a898cb14ce5758619d5143501c", "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-24T17:22:36.010Z", "expirationDate": "2025-06-22T17:22:36.010Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xa8088ad31bcd1459D12Ae6355119d3F4bF37D751", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextGithubOrg#PracticalParticle#12550942", "nullifiers": ["v0.0.0:DsVJcSfuDl2zavRnXsBoa1wN4mXbDtrbtTuJrs7VfoE="]}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-24T17:15:51.445Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0x61a3d527c1eef81e6d640861186a3bd97dcb1d354cd8570e35242dc9c59fa9ac5b25c116755946e200a0cfaad23b941c4049b1afdbb190397b6cb6374ba7f9731c", "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-24T17:15:51.444Z", "expirationDate": "2025-06-22T17:15:51.444Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xa8088ad31bcd1459D12Ae6355119d3F4bF37D751", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextTwitter#Particle_CS", "nullifiers": ["v0.0.0:65dF/jYv+q+0Fe3PcowCZlSF+pRAnMyd8+m2OKQhUUo="]}}}, "description": "Guardian Account Abstraction is a blockchain security infrastructure protocol that aims to enhance the overall security and usability of smart contracts in the development of decentralized applications.\n\nThe protocol's key features include:\n\n- Multi-phase security architecture\n\n- Role-based access control\n\n- Time-delayed operations\n\n- Meta-transaction support\n\nGuardian AA aims to have the following impacts:\n\n- Improved security for digital assets by reducing the risk of private key compromise\n\n- Enhanced user experience for blockchain interactions\n\n- Greater flexibility in implementing custom security policies\n\n- Increased adoption of blockchain technology by making it more accessible and secure for everyday users\n\nBy providing a robust security framework, Guardian AA seeks to address critical challenges in blockchain security and contribute to the wider adoption of decentralized technologies.\n\nWe opened source the Guardian AA for the benefit of the EVM ecosystem as a whole. As we believe high level security should be available for all.\n\nGithub: \nhttps://github.com/PracticalParticle/particle-core\n\nFor easy accessibility for the  technology, we also create SandBlox - a platform for show casing real world applications called Blox. \n\nGive it a try\nhttps://sandblox.app/\n", "lastUpdated": 0, "projectGithub": "PracticalParticle", "projectTwitter": "Particle_CS"}, "recipient": "0x2d77a0DD2d87b6DEAA7041c2a2048cA85DCfD526"}}