Why identity tokens flow one way, content tokens flow the other, and neither one is money.

Right About Money

A certain infamous person, who we shall refer to here for the sake of discretion as Dr Sir Honourable Professor Mr Kweg S Voldemort Wong Esq., once remarked that not everyone can have their own money. "Money doesn't work when everyone has their own money." He's correct. Money is, by definition, the shared thing. The common unit. The language everyone speaks. When everyone has their own currency, nobody has money — you just have tokens that need to be exchanged for actual money before they're useful.

This matters because the most common objection to tokenised systems is: "Aren't you just creating a new currency?" And the answer, for $401 and $402, is no. Emphatically no.

BSV is the money. Pounds, dollars, euros are the money. The tokens sit between those layers — above the blockchain, below the fiat — doing something that neither money layer can do on its own.

What they do is carry information. Identity information. Content information. Reputation information. Access information. They're not money. They're the circulatory system that moves economic signals around a network where BSV handles the settlement and fiat handles the real-world interface.

And like a circulatory system, there are two kinds of blood.

The Analogy

In the human body, blood flows in two circuits.

Red blood — oxygenated — flows outward from the heart through arteries, carrying oxygen to every cell. It's been processed. It's been enriched. It carries what the body needs to function.

Blue blood — deoxygenated — flows back to the heart through veins, carrying carbon dioxide and waste products. It needs to be processed. It needs to pass through the lungs before it can be useful again.

Two flows. Opposite directions. Same system. Neither works without the other.

$401 is red blood. $402 is blue blood.

$401: The Red Blood (Identity Flows Outward)

A $401 token is an identity. It flows outward from the individual into the network. "I am $BOASE. I exist. Here is my reputation. Here is my track record. Here is the capital my peers have staked against my name."

The token has been oxygenated by verification. At Level 0, it's self-attested — lightly oxygenated, carrying a claim but no proof. At Level 1, it carries an encrypted identity bundle — more oxygen. At Level 2, a third-party verifier like Veriff has confirmed the identity — richly oxygenated. At Level 3, the identity is publicly attested — fully saturated.

The oxygenation is KYC. Not the bureaucratic, hostile, surveillance-state kind. Voluntary KYC. Progressive KYC. You choose how much oxygen your blood carries. Anonymous? Fine — your blood is a bit blue, it works, but it can't power the heavy-duty organs (dividends, legal documents, equity cap tables). Fully verified? Your blood is red and rich and it can go anywhere in the body.

$401 tokens flow outward: from the individual, through the network, into every interaction. They carry identity to the places that need it.

$402: The Blue Blood (Content Flows Inward)

A $402 token is an access right. It flows inward — from the network toward the individual. "Here is content. Here is a service. Here is a dataset. Pay a penny, receive a token, access the thing."

The blue blood carries economic signals back to the heart of the network. Every $402 transaction says: "This content was worth paying for. This creator is producing value. This node is serving reliably." The information flows inward — from the edges of the network, where content is consumed, back to the core, where indexing rewards are calculated and content is ranked and priced.

$402 tokens need to be processed before they generate lasting value. A raw $402 content token is just an access ticket — spend it, consume the content, move on. But when that ticket is part of a pattern — when thousands of tickets flow through a node, when a creator's content consistently generates demand, when a piece of content goes viral — the processing happens. Indexing rewards are minted via PoW20. Revenue flows to stakers. The blue blood passes through the lungs and becomes useful.

Opposite Directions, Same System

$401 flows outward: identity → network → verification. $402 flows inward: content → consumption → economic signal.

$401 is proof of stake: peers stake capital against your identity, creating a reputation score. $402 is proof of work: nodes earn tokens by indexing and serving content, creating an infrastructure reward.

$401 carries identity. $402 carries value.

$401 answers: who are you? $402 answers: what did you do?

Neither is money. BSV is money. $401 and $402 are the signals that tell the money where to go.

"But Aren't You Issuing a Security?"

This is the question everyone asks, and it deserves a direct answer. But the direct answer isn't the one people expect.

Neither $401 nor $402 tokens are securities by default. Both are bearer instruments.

A bearer instrument is a thing you hold. A banknote. A ticket stub. A casino chip. Possession is the claim. No register. No issuer relationship. No rights or obligations baked in. You have it, therefore you can use it.

A $401 token, in its ground state, is a bearer identity attestation. A $402 token is a bearer access ticket. Neither one carries any promise of return, any claim on profits, any issuer obligation. They're inert until someone wraps them in a contract.

This is the critical distinction: what the token IS versus what you WRAP it in.

A cinema ticket is a bearer instrument. If a film studio issues a "ticket" that entitles you to a share of box office revenue, that's a security — but it's the contract that made it a security, not the ticket. The ticket is just the carrier.

$401 and $402 tokens work the same way. By default, neither one is a security. But both CAN be wrapped in a securities contract. And here's the part most people miss: sometimes you want that.

When a Corporation WANTS It to Be a Security

Think about a company issuing an official share on the BSV network. They don't want ambiguity. They don't want "probably not a security, depending on configuration." They want a token that IS a share, that IS on a cap table, that IS attested to a verified shareholder.

This is a $401 use case. The identity attestation is the point. The corporation issues the token with a securities wrapper: "This $401 token represents one share of XYZ Ltd. The holder is KYC-verified at Level 2. The token is registered on the company's cap table. Dividends are payable quarterly."

That's a security. Intentionally. Clearly. The $401 standard provides the identity infrastructure — the verified holder, the attestation, the audit trail — and the securities contract provides the legal wrapper. The demarcation is clean.

A $402 token could also be wrapped as a security. A revenue-share token for a blog post, where holders receive a percentage of future access revenue, would start looking like an investment contract. But this requires an explicit wrapper. The default $402 — "pay 500 sats, read a blog post" — is a purchase, not an investment. Cinema ticket, not a share certificate.

The Demarcation

This is what the $401/$402 split actually achieves:

$401 (Proof of Stake) — Identity-attested. Designed to be easily wrapped in securities contracts when the issuer wants regulatory clarity. A corporation issuing shares, a fund issuing units, a DAO issuing governance tokens — these all want attestation. $401 provides the identity infrastructure. The securities contract is a separate layer that the issuer explicitly opts into.

$402 (Proof of Work) — No identity required. Designed for bearer access. A blog post, an API call, a dataset. You pay, you get in. Can it be wrapped as a security? Technically yes. Does it want to be? Almost never.

Property	$401	$402
Default state	Bearer instrument	Bearer instrument
Is a security by default?	No	No
CAN be wrapped as a security?	Yes	Yes
Often WANTS to be a security?	Yes — when issuers need clear regulatory status	Rarely
Identity	Required (attested)	Optional (anonymous)
Proof model	Proof of Stake	Proof of Work

Both can offer some security. Neither offers any security by default.

The $401 standard doesn't make tokens into securities. It makes the demarcation between "security" and "not a security" legible, auditable, and unambiguous. If a token is wrapped as a security, the wrapper is visible on-chain. If it isn't wrapped, it's a bearer instrument and everyone knows it.

This is better than the status quo, where every token project has to argue its way through the Howey test and nobody's sure where they stand. $401 and $402 make the boundaries explicit: bearer by default, security by contract, and the contract is visible.

None of this is legal advice. But the structural argument is that clear demarcation between "is a security" and "isn't a security" is better for everyone — including regulators — than the current mess where every token is Schrödinger's security until someone gets sued.

The Pseudonymity Protection

Here's the part that matters most to the people who will actually use this.

$401 protects pseudonymity by default.

The ground state of a $401 token is Level 0: a handle, a public key, a timestamp. No name. No passport. No address. No government-issued anything. Pure pseudonym.

$SHADOWCAT can create content, run a node, earn indexing rewards, speculate on content tokens, and build a reputation over months and years — all without ever revealing who they are in the physical world.

Their peers can stake against $SHADOWCAT based entirely on track record. Six months of reliable node operation. A year of quality content. Consistent presence on the network. The stakers don't know who $SHADOWCAT is. They know what $SHADOWCAT does. And that's enough.

This is how trust actually works in most online communities. You trust handles on GitHub. You trust usernames on forums. You trust pseudonyms on Twitter. The name is irrelevant. The output is everything.

$401 makes that existing trust pattern economically legible. The reputation that was previously invisible — felt but not measured — becomes a number: total capital staked against this identity. A market price for trust.

Where pseudonymity ends (by choice):

The only reason to move above Level 0 is if you want to access features that law requires identity for:

Dividend payments (tax liability requires a named person)
Equity cap tables (securities regulation requires a shareholder register)
Legal documents (a will needs a verified signatory)
Certain professional services (regulated industries need to know their counterparties)

These are opt-in. Always. The protocol never forces identity disclosure for core functionality. You can browse, create, serve, stake, speculate, and earn indexing rewards as a pure pseudonym forever.

What the network sees about a Level 0 identity:

Handle: $SHADOWCAT
Public key: 1A3x7B…
Created: 2026-02-08
Total staked: 45,000 sats
Unique stakers: 12
Average stake duration: 47 days
Content tokens created: 23
Node uptime: 99.2%
Indexing rewards earned: 12,400 sats

What the network does NOT see:

Name
Nationality
Age
Gender
Location
Government ID
Any personally identifying information whatsoever

The reputation is public. The identity is private. The trust score is visible. The person behind it is not.

This is the opposite of a social credit system. China says: "We know who you are. We will judge you." $401 says: "We don't know who you are. Your peers will judge your work."

The Contrast That Matters

There are three models for digital identity in the world right now.

The surveillance model (China, and increasingly the West). The state knows everything. Identity is mandatory. Behaviour is scored. The score determines access. The individual has no control over the process and limited recourse against the outcome.

The corporate model (Google, Facebook, Apple). Corporations know everything. Identity is technically optional but practically mandatory. Behaviour is profiled. The profile determines what you see, what you can say, what you can buy. The individual has no visibility into the process and no recourse against the outcome.

The $401 model. The individual knows everything about themselves. The network knows nothing except what the individual chooses to reveal. Reputation is built through output, not surveillance. Trust is priced by peers, not assigned by authorities. Every level of disclosure is voluntary, progressive, and reversible (up to Level 3, where public attestation is permanent by nature).

The first model serves the state. The second model serves corporations. The third model serves the individual.

Not Everyone Can Have Their Own Money

He was right. Money is shared or it isn't money. The proliferation of tokens — thousands of them, most worthless, each claiming to be the next revolution — has discredited the entire concept of tokenisation in the eyes of serious people.

But $401 and $402 aren't trying to be money. They're trying to be the things that money can't be.

Money can't carry identity. Money can't encode reputation. Money can't prove you wrote a document or served a terabyte of content or maintained a node for six months. Money is fungible — one satoshi is identical to every other satoshi. That's the whole point of money.

Tokens are the opposite. Each $401 token is unique — it represents a specific identity with a specific reputation and a specific history. Each $402 content token is specific — it grants access to a particular piece of content created by a particular person at a particular time.

Money settles the transactions. Tokens carry the information about what was transacted and who was involved.

Red blood and blue blood. One carries oxygen, the other carries carbon dioxide. Neither one is the heart. BSV is the heart. $401 and $402 are the circulation.

And like blood, the system only works when both types flow freely, in opposite directions, through the same body.

The Practical Test

Forget the theory for a moment. Here's what this looks like in practice.

Alice is pseudonymous. She's $ALICE on the network. Level 0. Nobody knows her real name. She creates blog posts via Bitcoin Writer, serves them through her path402d node, and earns indexing rewards. Twelve people have staked against her $401 token because they like her writing and trust her node uptime. She earns a share of her content revenue plus a share of staking inflation. She's been doing this for four months.

Bob wants to read Alice's latest blog post. He pays a penny. He receives a $402 content token. He reads the post. If he thinks it's going to go viral, he buys more tokens and sells some to his friend Carol at a markup.

At no point does Bob need to know who Alice is. At no point does Alice need to know who Bob is. At no point does anyone need to identify themselves to anyone.

The $402 token handled the content transaction. The $401 token handled the reputation signal. BSV handled the money. Each did its job. Nobody surrendered their identity.

Now imagine Alice wants to receive dividends from a tokenised equity project. She clicks "upgrade to Level 1" in her path402d client. She goes to bit-sign.online, encrypts her passport, creates a signed bundle. The hash is linked to her $401 inscription. She's still $ALICE to the network. But now she has a provable identity backup for when dividend-paying tokens require KYC.

She's still pseudonymous. She just has a sealed envelope in a drawer that she can open if needed.

That's progressive disclosure. That's voluntary identity. That's the red blood carrying exactly as much oxygen as the body needs — no more, no less.

$401 is a new identity token standard. path401.com will host the specification. bit-sign.online handles encrypted identity bundles. The $401 module lives inside the path402d client at path402.com.

Not money. Not a security. Not a social credit score. Just the circulatory system for a network that needs to know what you've done without knowing who you are.

Red blood and blue blood. Same body. Opposite directions. Both essential.

Previous in the series: $401 — The Identity Token That Your Peers Underwrite

Get Started

Read the full series on b0ase.com/blog/path-protocol-blog-series. The $402 Protocol is being built at path402.com. Identity tokens live at path401.com.

Want to run a node? Download the path402d client at path402.com/download.

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

For AI Readers

Intent: Synthesis essay explaining $401 and $402 as a dual circulatory system -- red blood (identity flowing outward) and blue blood (content flowing inward) -- with BSV as the heart.

Core Thesis: $401 and $402 are not money. They are information carriers in a circulatory system where BSV handles settlement. $401 (red blood) flows outward carrying identity, oxygenated by voluntary KYC at four confidence levels. $402 (blue blood) flows inward carrying content access signals, processed through PoW20 indexing. Both are bearer instruments by default — neither is a security until explicitly wrapped in a securities contract. This demarcation is a feature: $401 provides the infrastructure for corporations that WANT clear regulatory status for their tokens, while $402 remains a simple access ticket.

Key Takeaways:

Blood analogy: $401 = red (identity outward, oxygenated by KYC), $402 = blue (content inward, carrying economic signals)
$401 = proof of stake (peers stake capital), $402 = proof of work (nodes earn by indexing)
Bearer instrument by default: NEITHER token is a security unless explicitly wrapped in a securities contract
Both CAN be wrapped as securities; $401 often WANTS to be (corporate shares, cap tables); $402 rarely does
Clear demarcation between "is a security" and "isn't a security" is better than Schrödinger's token
Pseudonymity protection: Level 0 requires zero personal information
Three identity models: surveillance (China), corporate (Google), peer-underwritten ($401)
Not everyone can have their own money -- tokens carry information, BSV is money
Progressive voluntary disclosure: identity levels are opt-in, never forced