velon (@velonsecure) header
velon (@velonsecure) profile picture

Permission infrastructure for Solana. Understand who can act, what they can do, and under which limits. Review changes. Verify revocations.

Joined October 2026
Photo by velon (@velonsecure)Photo by velon (@velonsecure)Photo by velon (@velonsecure)Photo by velon (@velonsecure)
You approve an app to spend some tokens. You use it. Close the tab. Move on. But that permission may still be there. Who can use it now? How much can they spend? How do you know when their access is gone? Those questions led us to build Velon.
1
1
1
18
Subscriptions showed us why this matters beyond a revoke button. The technical delegate can differ from the merchant allowed to collect. Several permissions can share one budget. Our recorded examples preserve those distinctions. Simple must still be truthful.
1
1
That’s Velon: making Solana permissions understandable, and their changes verifiable. We’re early. The public preview shows recorded evidence; the complete revoke loop is demonstrated locally. velon-eta.vercel.app What permission would you want explained first?