Fairness is a principle. This page explains how it is implemented, constrained, and hardened.
Scope & Status
Current stage: alpha (local-first)
Identity verifier seam exists; full live ICAO/NFC production verification is not yet deployed
Decentralized runtime direction is defined; full consensus layer is still being phased in
If wording conflicts with implementation, fairsharecoin/foundation is authoritative
Proof-of-Being
FairShareCoin starts from one rule: each verified living person is eligible for one base issuance unit (1 FSC).
This rule aims to remove mining races and reduce issuance privilege tied to hardware or early capital.
Identity Uniqueness & Privacy
The design target is uniqueness without exposing raw personal identity on-chain.
Identity proofs are transformed into deterministic, non-reversible identifiers for claim checks.
Current identity direction
Use ICAO-compliant ePassport verification path (NFC + certificate validation) when live
Derive deterministic identity identifier from stable fields
Exclude unstable attributes (e.g., nationality, expiry date, sex marker) from uniqueness basis
Use public namespace separator (“public pepper”) to prevent cross-system collisions
Renewal continuity model
Document renewal should not create duplicate issuance
New credential is re-evaluated under the same uniqueness logic
Recovery/continuity flow handles document lifecycle changes without re-minting base issuance
Future cryptographic privacy upgrades
Selective-disclosure and/or ZK-proof style verification for stronger privacy boundaries
Verifier abstraction to support future standards (including digital travel credential formats)
Node Roles (directional model)
Full Nodes: full validation + full ledger state
Transaction/Relay Nodes: transaction propagation and lightweight service roles
Light Clients: wallet-focused clients with minimal local requirements
Wallet Types
Verified wallet: eligible for base issuance under uniqueness rules
Anonymous wallets (optional): transactional/privacy utility; not for extra base issuance claims
Named/managed wallets (optional): usability layer for practical scenarios
Unit Scale
1 FSC is divided into 1012 picoFSC (12 decimals). Public UX can stay human-friendly (often nanoFSC),
while internal arithmetic maintains full precision.
Unit
Symbol
Value
Typical use
FairShareCoin
FSC
1
Base unit
Milli
mFSC
0.001
Larger everyday transfers
Micro
μFSC
0.000001
Service/task-level transfers
Nano
nFSC
0.000000001
Fine-grained visible UX unit
Pico
pFSC
0.000000000001
Internal precision
Unit–Time Bridge (conceptual framing)
Using an 80-year reference lifespan:
1 FSC ≈ 80 years
1 mFSC ≈ 29.2 days
1 μFSC ≈ 42.1 minutes
1 nFSC ≈ 2.52 seconds
1 pFSC ≈ 2.52 milliseconds
Per-second reference: 1 second ≈ 0.3969 nFSC.
Gold tracks scarcity in matter. Bitcoin tracks scarcity in energy. FSC explores scarcity anchored to personhood and time.
Abuse Resistance
Uniqueness checks to prevent duplicate base issuance claims
Rate limits and cooldowns at service/API level in current implementation
Separation between verified issuance rights and non-issuance wallet usage
Recovery & Continuity
Recovery is designed around identity continuity rather than fragile device custody alone.
Device loss should not imply permanent account loss when verified continuity can be re-established.
Supply Logic
Base issuance model: one unit per verified person
No mining-based inflation race by design direction
Circulating availability is shaped by user behavior (spend/save/hold), not fixed speculative schedules
Dormant Wallet Behavior
Dormant wallets represent inactive holders. They remain part of total system accounting,
but they do not actively transact while dormant.
Resilience & Anti-Fragility Direction
The goal is graceful behavior under adverse conditions: partial connectivity, infrastructure stress,
and uneven node availability. This is a design target and ongoing engineering track, not a finished claim.
Roadmap Direction
Verifier hardening and standards-aligned identity adapters
Decentralized runtime maturation
Higher privacy verification proofs
Ecosystem layers (apps, voting/governance tooling, group coordination primitives)