GUARDIANVAULT

🎯 TAGLINE

"Secure family assets. Delegate with limits. Inherit with confidence."

Inheritance planning without private keys — powered by MetaMask Advanced Permissions

📋 PROJECT INFORMATION

🚨 THE PROBLEM

Current Inheritance Solutions Are Fundamentally Broken

The Core Challenge

"I want my family to inherit my crypto if something happens to me, but I don't want to give them my private keys, pay thousands in legal fees, or set up complex multisigs."

This is impossible with existing Web3 infrastructure — until now.

💡 OUR SOLUTION

GuardianVault: Permission-Based Inheritance System

GuardianVault uses MetaMask Advanced Permissions (ERC-7715) to create:

Key Innovation Matrix

HOW IT WORKS

Complete User Journey

🧠 How GuardianVault Works (Simple Explanation)

1. A user connects MetaMask and creates a GuardianVault

2. The user defines:

   • Beneficiaries (family members)

   • Token type (ERC-20 like USDC)

   • Maximum amount

   • Time window

   • Trigger condition (emergency / inactivity / verified event)

3. The user grants an Advanced Permission (ERC-7715) to an Executor Agent

4. (Optional) The Executor Agent re-delegates partial permission to a Verifier Agent (A2A flow)

5. Agents continuously monitor trigger sources

6. When the trigger occurs:

   • Permissions are validated

   • Verifier approval is requested (if enabled)

7. Funds are released automatically and securely

8. Every step is auditable, revocable, and transparent

✅ No private keys shared
✅ No custodial control
✅ Fully permission-based execution

🔐 MetaMask Advanced Permissions (ERC-7715)

GuardianVault deeply integrates MetaMask Advanced Permissions using the Smart Accounts Kit.

How we use Advanced Permissions:

• Grant agents limited ERC-20 spending authority

• Enforce:

  • Max spend amount

  • Time-bound validity

  • Contract-specific execution

• Support agent-to-agent (A2A) delegation

• Permissions are:

  • Revocable anytime

  • Visible in MetaMask

  • Non-custodial by design

This ensures agents can help — but never misuse funds.

Permission Scope Configuration

🤖 Agent-to-Agent (A2A) Security Flow

GuardianVault introduces a two-agent approval model:

• Executor Agent
  Executes fund transfers when conditions are met

• Verifier Agent (Optional)
  Receives a sub-delegated permission to approve or reject execution

This creates multi-party verification without multi-sig complexity, making inheritance safer and more human-friendly.

📊 Envio Indexing Integration

GuardianVault uses Envio to provide a real-time transparency layer.

What Envio indexes:

• Vault creation events

• Permission grants & revocations

• Agent delegation trees

• Fund release events

Why this matters:

• Families can see exactly what permissions exist

• Judges can verify Advanced Permissions in action

• Creates a live dashboard for auditability and trust

Envio turns GuardianVault from a black box into a fully observable system.

🎯 Why GuardianVault is Unique

• 🚫 Not another DCA or trading bot

• 👨‍👩‍👧‍👦 First family-focused crypto inheritance system

• 🛡️ Uses permissions instead of private keys

• 🔁 Introduces A2A permission re-delegation

• 🌍 Solves a real-world human problem, not just DeFi mechanics

📈 IMPACT & METRICS

Problem Scale

🙏 ACKNOWLEDGMENTS

Built during the MetaMask Advanced Permissions Dev Cook-Off using:

Special thanks to the MetaMask and Envio teams for their excellent documentation and support!