#Verification

The previous pages covered the economic engine that funds the network and the symmetric decay model that carries the dead. Both rest on a single assumption: that the avatars on the network are real people, not synthetic identities a single attacker spun up by the thousand. Verification is the gate that keeps that assumption true.

Without verification, anyone could create a million temp avatars, have them vouch for each other, and flood the level system with phantom users that drain the surplus pool. The protocol prevents this by requiring every new avatar to collect three vouches from people who have already invested months of hosting, before the temp identity is allowed to become permanent.

#The Permanence Gate

Every new avatar starts as a temporary identity with a .temp.avtr domain and a 90-day countdown. During those 90 days you must collect three verifications from trusted members of the network. Succeed, and your avatar becomes permanent: the .temp prefix drops, your Network Estate begins accruing level progress, and your replicated copies stop being TTL-bound. Fail, and the avatar plus every copy of it is permanently deleted.

This gate is intentionally hard. Verification is the only barrier between a genuine new user and a flood of fake accounts, so the protocol holds it tight. Three real people who already invested months of hosting must vouch for you, by name, with their cryptographic signatures.

#Trusted Verifiers

A trusted verifier is not just any L1+ user. The minimum tier required scales with how mature the network is, because attack costs change as the network ages.

In Genesis mode, the network is too young for any L3 user to exist. L3 requires 27 months of hosting, so until the network itself has been running for 27 months, nobody can possibly hold L3 status. Genesis falls back to L2 as the floor. Once L3 users naturally appear, the protocol upgrades the requirement and the bar gets harder.

The protocol explicitly does not allow L1 users to verify others. L1 only requires 3 months of hosting, which an attacker can rent for around $100,000. They could spin up a fleet of fake L1 nodes, have them verify each other after 3 months, and the whole thing snowballs into a synthetic Network Estate. L2 raises the cost an order of magnitude, and L3 raises it again. At L3 the attack budget is high enough that even a state actor would think twice.

#The Pregnancy Metaphor

The trusted verifier tiers borrow from the most universal time-investment metaphor humans have, which is pregnancy. Three months is one trimester, nine months is one full pregnancy, and twenty-seven months is three pregnancies in a row.

The mature-mode trusted-verifier rule reads cleanly as one sentence: three verifications from L3 users who hosted three pregnancies. The metaphor is not random. It anchors the protocol to a unit of time that every culture intuitively understands as a real, biological commitment, which makes the verifier requirement memorable rather than arbitrary.

#Banked Verifications

You can verify with as many people as you want, at any time. There is no social restriction on how many vouches you can issue. But your active verifier weight, the count that determines your priority during crisis recovery, is capped by your level. Verifications beyond the cap sit "banked" and unlock automatically as you climb.

Picture a user who arrives on the network and verifies fifty friends in their first week.

By L4 their entire L1 social capital has fully unlocked. The banking mechanic rewards early enthusiasm without letting it skew the early network. A user who recruits a hundred friends in week one is not granted a hundred votes immediately; they receive their level's allotment, and the rest waits for them to earn the level that justifies the weight.

The same mechanic also works as a retention hook. A user who verified beyond their level's cap has banked value waiting for them at every future level, which gives a quiet ongoing reason to keep hosting.

#Revocation

Verification is one-way trust at the moment it is issued, but its persistence depends on the issuer's status. The rules differ for temp users and permanent users, for the same reason banks distinguish provisional credit from settled funds.

A temp user can issue verifications during their 90-day TTL, but if they fail to become permanent, every verification they issued is automatically revoked. This blocks an attack pattern where a swarm of fake temp avatars verify a target avatar, then disappear when their TTL expires, leaving the target permanently inflated by phantom trust.

Once an avatar reaches L1 and becomes permanent, all verifications it has issued become permanent too. The protocol does not revoke verifications between permanent users, even if the verifier later degrades or stops hosting. Permanence creates trust that does not unwind, because cascading revocations would let one falling avatar take down a chain of others.

#Crisis Recovery Priority

Verifications keep working long after the permanence gate. When the network drops below 50% health, circuit breakers fire and copies above the eternal floor are shed (covered in Protocol Economics). When health recovers, those copies need to be restored, and the protocol has to decide who gets restored first.

The answer is verification count. An estate with more active verifications gets restored before an estate with fewer, because more verifications mean more humans signed off on this avatar being a real person worth preserving. Verifier weight thus carries economic value across the full lifecycle: it gates entry at Temp, it tracks growth across levels through banking, and it determines recovery order after a crisis.

This means that even if every other dimension of your Network Estate is identical to another estate, the one with more active and banked verifications gets recovery priority. Hoarding verifiers is not antisocial. It is exactly what the protocol asks you to do, because every vouch is a signal to the network that a real human is willing to stake their own track record on this avatar being who they say they are.

#What Comes Next

Verification ties the social trust layer to the technical crisis-recovery layer. Combined with the level system from Protocol Economics and the symmetric decay model from Digital Permanence, it completes the picture of how Avatarnet keeps a million strangers honest without a central authority deciding who counts as real.

The next section, Reference, collects every term used so far for quick lookup.