poztter.com

poztter.com / your master zone

Your master zone.

The master zone is the most important part of your POZ record. It says which keys can change anything about you, including which other keys are allowed to do which things. Get this right once, and the rest is easy.

three things every master zone should have

  1. A daily-use survivorship group with one or two strong keys (a hardware token, your primary device).
  2. A recovery survivorship group that doesn't depend on the daily group. Family, an agency, your lawyer, a deposit box — the model can express many shapes.
  3. Sub-zone delegations for at least Identity and Service, with deny ≥ grant.
Genesis is forever. Your record's original_master_hash is computed from your genesis revision and never changes. Take time on the genesis. You can revise everything else later — but the genesis is what permanently identifies you.

practical patterns

solo, with recovery

The most common configuration. One primary key for everyday signing, plus a recovery group for if it's lost.

GroupKeySurvivorship value
1 (Primary)Hardware token100
2 (Recovery)Family member 140
2 (Recovery)Family member 240
2 (Recovery)Family member 340

solo, with agency

One primary key, plus a "user + agency" group for recovery. The agency can't act without you, and you can't be locked out by the agency.

GroupKeySurvivorship value
1 (Primary)Hardware token100
2 (User + agency)Recovery key (yours)50
2 (User + agency)Agency key50

two devices, no third party

Phone and laptop. Either alone is enough day-to-day; both together can authorize anything.

GroupKeySurvivorship value
1Phone100
2Laptop100
START how many daily devices? one two trusted recovery friends agency → TWO DEVICES phone 100 · laptop 100 → SOLO + FAMILY hw token 100 3 family × 40 recovery spacer → SOLO + AGENCY hw token 100 you 50 + agency 50 whichever pattern you pick, always configure ≥ 2 groups recovery is the difference between "setback" and "locked out forever"
fig 01 · short path from "how many devices" + "who do you trust" to a recommended pattern. Every leaf includes a recovery group — none rely on a single key.

things to avoid

editing your master zone

Modifications follow the draft / sign / apply workflow. Increment the serial, collect signatures from a satisfying group, compute the hash, save. The poz_cli tool walks you through this.

Read the master zone specification for the full data layout, and survivorship for the threshold rules.