Introduction
Over the last several days, I built Sentinel AI, an autonomous investment committee powered by:
- MetaMask Smart Accounts
- ERC-7715 Advanced Permissions
- ERC-7710 Redelegation
- x402 Payments
- 1Shot Permissionless Relayer
- Venice AI
Unlike most hackathon feedback, this is not a project showcase.
This is builder feedback.
The goal is simple:
What worked exceptionally well?
What slowed development?
What can be improved for future builders?
After spending dozens of hours reading documentation, deploying contracts, debugging integrations, and connecting multiple systems together, I think I can provide feedback that is both practical and actionable.
What MetaMask Got Extremely Right
1. Smart Accounts Finally Make AI Agents Practical
The biggest takeaway from this hackathon is that Smart Accounts fundamentally change how AI systems can interact with crypto.
Before learning MetaMask Smart Accounts, my mental model was:
- User owns wallet
- User signs everything
- AI can only recommend
After implementing ERC-7715 and ERC-7710, the model became:
- User defines boundaries
- AI operates inside boundaries
- Blockchain enforces the rules
This is a massive shift.
It is probably the most important thing I learned during the entire hackathon.
The permission model feels genuinely future-proof.
2. Documentation Quality Was Surprisingly High
One thing I want to specifically praise is the quality of the MetaMask documentation.
Most Web3 documentation explains APIs.
MetaMask documentation explains concepts.
That difference matters.
The explanations around:
- Smart Accounts
- Delegation
- Redelegation
- Advanced Permissions
were much easier to understand than similar account abstraction documentation from other ecosystems.
This significantly reduced the learning curve.
Where MetaMask Documentation Can Improve
1. Missing End-to-End Examples
This was probably the single biggest friction point.
Most documentation pages explain individual concepts well.
However, real applications combine everything.
As a builder, I constantly wanted a single example showing:
User Connect Wallet
↓
Create Smart Account
↓
Grant ERC-7715 Permission
↓
Create Session Key
↓
Redelegate Permission
↓
Execute Transaction
↓
Revoke Permission
Currently, this flow exists across multiple documentation pages.
Future builders would benefit enormously from one complete reference implementation.
Suggested Improvement
Create a dedicated:
Full Lifecycle Smart Account Example
with frontend, backend, and smart contract code.
This would probably save builders several hours.
2. More Architecture Diagrams
The documentation is technically strong.
However, Smart Accounts are fundamentally visual systems.
When implementing redelegation, I found myself drawing diagrams manually.
For example:
User
↓
Smart Account
↓
Session Account
↓
Execution Agent
↓
1Shot Relayer
↓
Blockchain
I believe every major documentation section should include:
- Architecture diagram
- Sequence diagram
- Permission flow diagram
This would dramatically improve comprehension.
3. Better Error Troubleshooting
One challenge I encountered repeatedly:
I would receive an error.
The documentation explained how things work.
But not why they fail.
Examples:
- Invalid delegation
- Permission context mismatch
- Session account issues
- Smart account initialization failures
A dedicated troubleshooting database would be extremely valuable.
Something similar to:
Common Error
Cause
Solution
would save builders substantial time.
What 1Shot Did Extremely Well
1. The Relayer Is Genuinely Impressive
The 1Shot Permissionless Relayer was probably the smoothest integration in the entire stack.
The capability discovery endpoint was especially useful.
Instead of hardcoding assumptions, applications can dynamically determine:
- Supported chains
- Payment tokens
- Delegation targets
- Fee structures
This feels significantly more scalable than traditional approaches.
2. Gas Abstraction Feels Like Magic
One of the strongest moments in my build process was seeing transactions executed without worrying about native gas tokens.
This sounds simple.
But for user experience, it is transformative.
Most users do not care about gas.
They care about outcomes.
1Shot aligns perfectly with that reality.
Where 1Shot Can Improve
1. More Real-World Production Examples
Most builders are not creating simple token transfer demos.
They're creating:
- Agents
- DAOs
- Portfolio managers
- Automation systems
I would love to see:
Example Projects
- AI Agent + Relayer
- DAO Treasury + Relayer
- Smart Account + Relayer
- x402 + Relayer
These examples would accelerate adoption significantly.
2. Better Webhook Documentation
Webhooks are powerful.
However, they are also where many production systems break.
More examples covering:
- Retry logic
- Signature verification
- Event ordering
- Failure handling
would be extremely useful.
What Venice AI Did Well
1. The Idea Is Powerful
The most exciting aspect of Venice is not the model itself.
It is the philosophy.
Permissionless intelligence.
Permissionless payments.
Permissionless infrastructure.
That combination is incredibly powerful for agentic systems.
The vision aligns perfectly with where autonomous applications are heading.
Where Venice Can Improve
1. More Web3-Specific Agent Examples
Most AI providers show:
- Chatbots
- Assistants
- Content generation
Builders in this hackathon are building:
- Trading agents
- Governance agents
- Treasury agents
- Research agents
Dedicated examples would help developers understand best practices much faster.
Feedback for HackQuest
1. Excellent Track Design
The track structure was one of the strongest aspects of the hackathon.
Most hackathons reward feature accumulation.
This event rewarded architecture.
That encouraged builders to think deeply about systems rather than simply adding more buttons.
2. Better Resource Organization
As the event progressed, I found resources spread across:
- Documentation sites
- GitHub repositories
- Discord discussions
- HackQuest resources
A centralized builder portal would improve navigation significantly.
3. Weekly Technical Office Hours
This is probably my biggest recommendation.
Builders often spend:
- 30 minutes coding
- 5 hours debugging
A weekly technical office hour with ecosystem teams could dramatically improve builder velocity.
Even one session per week would create enormous value.
The Biggest Lesson From Building Sentinel AI
The biggest lesson wasn't about AI.
It wasn't about smart contracts.
It wasn't about relayers.
It was about permissions.
The future of Web3 is not giving software unlimited authority.
The future is programmable trust.
MetaMask Smart Accounts, ERC-7715, ERC-7710, x402, and 1Shot collectively point toward a future where autonomous agents can safely act on behalf of humans.
That future feels much closer after building Sentinel AI.
And for that reason alone, this hackathon was worth participating in.
Thank you to the MetaMask, Venice AI, 1Shot API, and HackQuest teams for creating an event that pushed builders to explore what autonomous onchain systems can become.
Top comments (0)