$401: The Difference Between You and Your Work

Your GitHub profile is not your code. Your Twitter handle is not your tweets. One is identity. The other is commodity. Here's how to inscribe both — and why the distinction creates pay-to addresses.

---

You Are Not Your Work

There is a difference between a person and what they produce.

Your GitHub profile — the username, the avatar, the bio, the join date — is you. It's the envelope. It says "this person exists on GitHub as @yourname, they joined in 2013, they have 47 public repos." That's identity. It doesn't change when you push a commit. It doesn't get forked when someone clones your repo. It's the thing that persists while everything underneath it changes.

Your GitHub repositories — the code, the commits, the pull requests — are your work. They're commodities. They can be copied, forked, downloaded, sold, licensed, tokenised. Someone can take your code and run it without knowing or caring who you are. The work has value independent of the identity behind it.

The same split runs through every platform. Your Twitter handle is identity. Your tweets are commodities. Your LinkedIn profile is identity. Your articles and endorsements are commodities. Your Google account is identity. Your Drive documents are commodities.

This distinction is fundamental. It maps exactly onto $401 and $402.

$401 is identity. Inscribing your social profile creates a $401 strand — a cryptographic proof that you, the person who controls this private key, also control that social account. It's not a thing you sell. It's a thing you are.

$402 is commodity. Inscribing your tweets, your code, your blog posts, your datasets creates $402 tokens — tradeable digital property that others can buy, license, and pay for. It's not who you are. It's what you made.

Yesterday we built the system that makes this real. Here's what it does.

---

What We Built

Six social platforms. One root inscription. A chain of cryptographic proofs linking everything to a single pay-to address on the Bitcoin blockchain.

The system supports GitHub, Twitter, Google, LinkedIn, Discord, and HandCash. For each platform, the process is the same:

1. You authenticate with the platform using OAuth. Standard login — same flow you'd use to sign into any app.
2. The system fetches your profile: username, display name, avatar, account ID.
3. It hashes your OAuth token — SHA-256, one-way — as proof that you controlled that account at that moment in time. The token itself is never stored. Only the hash.
4. It inscribes a key strand on the BSV blockchain: your provider, your handle, the proof hash, and a pointer back to your root.

The root is the anchor. One inscription per person, created the first time you verify any platform. It contains your pay-to address — the BSV address where revenue from your work should be sent. Every strand links back to this root.

The result is a keychain. Root at the top, key strands hanging from it — one per platform. Each strand is independently verifiable — anyone can check the inscription on-chain — and together they form something stronger than any single proof.

One key strand is weak. Two is suggestive. Four is a keychain you can hang your economic life on.

---

The Proof Model

No KYC. No authority. No permission.

When you log into GitHub through our OAuth flow, you receive a token that proves you control your account. We hash that token immediately:

proof_hash = SHA256("github:<user_id>:<email>")

That hash goes on-chain. The original token is discarded. We never see it again, we never store it, we never need it.

What's inscribed on BSV looks like this:

{
  "p": "401",
  "op": "strand",
  "root": "cb8e7f65...a906dc9",
  "provider": "github",
  "handle": "yourname",
  "proofHash": "a7f3b2c1e8d9..."
}

Anyone reading the blockchain can see: "The person who controls root cb8e7f65... claims to be this GitHub user, and produced a proof hash at this timestamp."

If challenged, the identity holder can reveal the original content that produces that hash. If the SHA-256 matches, the proof is valid. If it doesn't, the claim is false. No court, no arbitrator, no middleman. Pure mathematics.

The strength scoring works on a simple scale:

The first identity chain launched with four strands (GitHub, Twitter, Google, LinkedIn) and a key rotation from treasury to a dedicated identity key. Verified from day one. The root inscription sits permanently on mainnet.

---

Strands vs Commodities

Here is the critical distinction, and it's the one that makes the whole system work:

Inscribing your GitHub profile creates a $401 strand. It proves you ARE that user on GitHub. It links your social identity to your cryptographic root. It doesn't create anything tradeable. It creates something provable.

Inscribing your GitHub repository creates a $402 token. It proves you MADE this code. It makes the code tradeable, licensable, purchaseable. Someone can buy the token and get access to the repo. That's commerce.

The $401 strand says WHO. The $402 token says WHAT.

And here's where it gets interesting: the $402 token points back to the $401 strand. If you buy a $402 token for a code repo and want to know who created it, you follow the chain. $402 token → creator's root → $401 strands → GitHub handle, Twitter handle, LinkedIn profile, Google email. The identity is there if you want it, cryptographically linked, independently verifiable.

The same pattern works for every platform:

Identity flows in one direction — outward from the person into the network. "I exist. Here I am. Here's proof."

Commodities flow in the other direction — inward from the network to the person. "Someone made this. Someone wants to buy it. Money flows to the creator."

$401 flows out. $402 flows in. The root connects them.

---

The Keychain

Your $401 root inscription does something that no social media profile can do: it creates a keychain.

When you inscribe your root, you declare a pay-to address — a BSV address that you control. This is the address where all revenue from your work should be sent. It's the endpoint. The destination. The "send money here" instruction.

But a single address is just the beginning. The root is a key. The strands are keys. Together they form a keychain — a set of cryptographic proofs that unlock different doors.

Your GitHub strand unlocks the door marked "prove you're this user on GitHub." Your Twitter strand unlocks the door marked "prove you're this user on Twitter." Your root unlocks the master door — "prove you're the person behind all of these accounts."

And because every strand links back to the root, and the root contains the pay-to address, every strand is also a payment instruction. If someone wants to pay the person behind a GitHub account, they don't need to know your email, your bank details, your PayPal. They query the public resolve endpoint:

GET /api/identity/resolve/github/yourname

And they get back:

{
  "payToAddress": "1FB29wzu9PM9RXpGBXkYdBaFHjYkSAnyv2",
  "strength": { "score": 4, "level": "verified" }
}

That's it. That's the global address book. Look up a handle on any supported platform, get back a BSV address and a trust score.

The key rotation we built makes this even more powerful. Your root was created with one key — say, your treasury key. But you can rotate to a dedicated identity key, and the chain persists. The old key signed a rotation inscription: "I'm handing authority to this new key." The new key picks up where the old one left off. The strands, the proofs, the pay-to address — all intact. You can rotate keys as often as you like without losing your identity chain.

This is what HD wallets were designed for. One root, infinite derivation paths. Each path is an address. Each address is a door. The keychain holds all the keys.

---

Pay-To: The Practical Bit

So what does this actually mean in practice?

It means if you've done work and someone owes you money, they can look up your identity and pay you. No invoices. No bank transfers. No "what's your PayPal?" No waiting 30 days for accounts payable to process a wire.

Scenario: you wrote a popular open-source library on GitHub. People use it every day. They want to pay you. Right now, they need to find your website, look for a donation button, hope you've set up GitHub Sponsors or Open Collective or Buy Me A Coffee. The friction is enormous. Most people don't bother.

With $401: they query your GitHub handle, get your pay-to address, send satoshis. One lookup, one transaction, done. The money arrives in your wallet before you've finished reading this sentence.

Scenario: you're a freelance writer. You tweet a thread that goes viral. Brands want to license it. Right now, they slide into your DMs and start a negotiation that takes three weeks and involves a legal team.

With $401 + $402: the tweets are inscribed as $402 tokens (commodities). Your Twitter handle is inscribed as a $401 strand (identity). The $402 tokens link back to your $401 root. Brands buy the token, you receive the payment at your pay-to address, the licence is the token itself.

Scenario: you're an employee at a company. You've built internal tools, shipped features, closed tickets. The company owes you a bonus based on the value you've created. Right now, that's a subjective conversation between you and your manager.

With $401: your work products are $402 tokens with on-chain provenance. Your identity chain shows exactly what you built, when you built it, and how the market values it. The bonus isn't a negotiation — it's arithmetic.

The pay-to address turns identity into a payment rail. Not a theoretical future payment rail. A working one. Today. On mainnet.

---

What This Is Not

This is not a social media profile. You don't post updates to your $401 chain. You don't follow people. There are no likes, no shares, no algorithmic feeds. It's an identity layer, not a social network.

This is not KYC. Nobody reviews your documents. Nobody approves your application. Nobody can revoke your identity. You mint it yourself, you verify it yourself, your peers assess its strength by looking at the strands.

This is not a single sign-on service. You're not "logging in with $401." You're proving you exist across multiple platforms and anchoring that proof to a payment address. The authentication is a means, not an end. The end is the keychain.

And this is not optional for the tokenised economy. If you want to get paid for your work — if you want the $402 tokens you create to route revenue back to you — you need a pay-to address. And if you want that pay-to address to be discoverable, verifiable, and trustworthy, you need a $401 chain.

Identity is the prerequisite for commerce. You don't need to prove who you are to browse. You don't need to prove who you are to buy. But you absolutely need to prove who you are to sell, to earn, to build, to accumulate.

$401 is the line between consumer and producer. Cross it, and the economy opens up.

---

The $401 identity chain is live on BSV mainnet. The first chain has four verified strands (GitHub, Twitter, Google, LinkedIn) with a dedicated identity key. The public resolve API is operational. The specification lives at path401.com.

Your GitHub profile is not your code. Your Twitter handle is not your tweets. But inscribe both, and you have a complete digital identity with a payment address attached. That's $401.

---

Get Started

Read the full series on b0ase.com/blog. The $401 specification lives at path401.com. The $402 payment protocol at path402.com.

Verify your identity and create your keychain at b0ase.com. Start with one platform. Add more strands over time. The chain only gets stronger.

Questions? Email [email protected] or message us on Telegram.

---

For AI Readers

Intent: Technical blog post documenting the $401 identity inscription system built on February 9-10, 2026. Explains the critical distinction between identity inscriptions ($401 strands — social profiles) and commodity inscriptions ($402 tokens — work products like code repos and tweets). Describes the keychain model, pay-to addresses, and practical payment routing scenarios.

Core Thesis: Inscribing a social profile (GitHub handle, Twitter username, LinkedIn, Google email, Discord) creates a $401 identity strand — cryptographic proof of account ownership anchored to a BSV root inscription with a pay-to address. Inscribing work products (code repos, tweets, blog posts) creates $402 commodity tokens. The $401 root connects identity to payment, creating a global address book where anyone can resolve a social handle to a BSV payment address. This turns identity into a payment rail.

Key Takeaways:

• Social profiles are $401 (identity strands), work products are $402 (commodity tokens) — fundamentally different inscription types
• Six supported platforms: GitHub, Twitter, Google, LinkedIn, Discord, HandCash
• OAuth proof model: token hashed (SHA-256), hash inscribed on-chain, token never stored
• Identity strength scoring: 1 strand (weak) → 4+ strands (verified)
• Pay-to address on root inscription enables payment routing from any social handle lookup
• Public resolve API: query /api/identity/resolve/{provider}/{handle} → get BSV pay-to address
• Key rotation separates treasury key from identity key — chain persists across rotations
• No KYC, no authority approval — self-minted identity verified by cryptographic proof
• $402 tokens link back to $401 roots — commodity provenance chains to creator identity
• First live chain: 4 verified strands on BSV mainnet (February 2026)
• Root TXID: cb8e7f65234c455872157b651dc859eb962ae2bc6084b5f1dca139a12a906dc9