Arc Pass
Proof-Based Founder & Builder Identity
A credential layer for the Arc ecosystem where access is earned from verifiable building history, not from claiming a title.
Demo
Claiming a pass: username check, eligibility against real onchain activity, then the issued Founder Pass credential.
Problem
Every ecosystem directory is self-reported. Anyone can write "founder" or "senior engineer" in a bio, which means the signal is worth roughly nothing and everyone falls back on warm introductions anyway. The passes and NFTs that tried to fix this mostly just moved the same unverified claim on-chain.
Why I built it
Running founder introductions at Webcoin Labs, the bottleneck was never willingness — it was trust. I could vouch for people I had personally worked with and nobody else. Proof of building is the thing that scales past what one person can vouch for.
What I built
Two credentials built on evidence rather than assertion. Founder Pass is invite-based and carries founder identity, ecosystem access and a credibility layer that travels with you. Builder Pass is earned: it reads real ecosystem participation — contract activity, shipped projects, GitHub history — and resolves to a tier that reflects what you have actually built.
Credentials
Founder Pass
Invite-based founder identity and access.
- Founder identity and ecosystem access
- Startup credibility layer that travels between platforms
- Access to founder-only ecosystem benefits
- Gateway into investor and advisor introductions
Builder Pass
Earned from verifiable building history.
- Reads on-chain contract activity
- Checks shipped projects and ecosystem participation
- Verifies GitHub and public building proof
- Resolves to a tier that reflects real work
Builder Pass tiers
- BronzeVerified entry — first proven contributions
- SilverConsistent shipping across multiple projects
- GoldSustained ecosystem activity and depth
- PlatinumSignificant, sustained public building record
- DiamondTop-tier verified builder standing
What I did
- Product design and credential model
- Tier and verification logic
- Ecosystem integration with Webcoin Labs
- Go-to-market
Technology
- React
- Next.js
- Node.js
- PostgreSQL
- Arc
- Smart Contracts
Challenges
Making a credential that resists gaming without becoming impossible to earn. Weighted too far toward on-chain activity and it rewards whoever deploys the most throwaway contracts; weighted too far toward manual review and it does not scale past a few hundred people.
What I learned
The credential is only as valuable as what it unlocks. Building the verification was the easy half — the work that matters is making the pass actually gate something people want.