Merge your GitHub, Figma, and onchain deploys into one verified contribution map.
Tunde applies to an accelerator with three links that nobody clicks. With Craft Graph he sends one page that shows signed proof of his commits, his contract deploys and his design files over five years, verified rather than claimed.
Let anyone who makes things show their whole craft in one look, verified rather than claimed, and owned by them.
Builders who design, code and ship contracts send reviewers three or four links, and most reviewers do not click them. Design work is nearly invisible, and a Basescan link proves a contract exists but not who made it. People need one page that shows the whole craft and proves it, without exposing private client work.
Talent profiles on someone else's platform score you by their rules and can change those rules tomorrow. When you own Craft Graph, the contribution map, the verifier page and the list of builders who trust it all live under your name and your wallet. Every profile that gets shared in an accelerator application or a hiring thread points back to your brand, and that is a record you keep.
10 paying Pro builders and 1 signed team plan within 60 days.
2 grant or retro funding applications submitted with usage data attached.
Contracts deployed and verified from your wallet, a public builder profile, and 30 days of real onchain activity.
Craft Graph or a new feature on it submitted to one hackathon, with a demo video.
Your own map live and used in at least 2 applications or pitches, saving an hour each.
Your class, team or community with 15 or more maps and a monthly showcase.
1 signed partnership with an ecosystem, program or platform that links to your maps.
A case study with real numbers and one interview or client call from it.
3 paid setups for clients at $500 or more each.
You do not need to write code to run it. The connectors for GitHub and contract deploys come set up, and your job is picking the community you serve, onboarding the first profiles and keeping the page looking sharp. If you want a new connector later, that is a custom order, not something you have to build.
Honest answer: for generic builder scores, they might not. Your opening is a specific community, such as a bootcamp cohort, a design guild or a chain's local builder group, that wants its own branded map and wants design work counted next to code. Go narrow first. A small group that loves it beats a broad group that ignores it.
Yes. It deploys from your wallet, the attestations anchor from contracts you control, and the domain and brand are yours. DEPLOYR builds and hands it over. If you stop paying for hosting you can export the profiles and the anchored proofs stay onchain.
The map only shows what it can check: commits signed to a linked GitHub account, contracts deployed from a linked wallet, and files from linked design accounts. It cannot prove someone did the thinking behind a commit, so say that plainly on your verifier page. Verified activity is still far stronger than three unclicked links.
Then you learn that fast and cheap. Start with ten builders who are about to apply for something, a grant, a job or an accelerator, because that is the moment a proof page matters. If ten people with a real deadline do not use it, change the community, not the product.
Put your name on a take onchain, mint a shareable badge, others co-sign.
Create an account and prove your transactions in your own browser. Client-side proving on Miden, nothing leaks.
Prove your trading discipline, not your profits: stops honored, sizing kept, tilt avoided.
Caregivers and parents prove unpaid care work, privately, for loans and jobs.
Recruiters pay a small USDC fee to request verified proofs from candidates, who get paid.
Mentees attest that you changed their path, building a lineage tree of who you lifted up.
Prove you are over 18, a resident, or a degree holder without showing a single document.
Timestamp every hour of deliberate practice and own the 10,000 hour proof.