Welcome to Hesskey
Sign in with your decentralized identity. No passwords, no email addresses. Just you and your phone.
Click Sign in in the top-right to begin.
Authenticated Verified --
Create the Hesskey Foundation
No Foundation exists on this chain yet. As the first registered user, you can create the Foundation and become its owner. This is a one-time action — once created, the Foundation owner controls governance.
This will submit create_foundation via the Hesskey app (pallet 13, call_index 12).
Cluster health
Live snapshot of the validator network — chain consensus, block production, IPFS, and bootnode reachability.
Cluster Map
Every validator in this Foundation cluster. Nodes you own carry a YOURS badge. Foundation slots show FOUNDATION; personal slots show PERSONAL.
Claim Foundation Node Slot
Submit via Hesskey app: pallet 12, call_index 2 (claim_foundation_node_slot).
Foundation Members
Add Member from Contacts
Pick a contact on the Hesskey app — the phone signs a
propose(AddFoundationMember(did)) extrinsic.
The proposal needs the current approval threshold to pass.
Maximum Members
Roles
Viewer & Auditor are read-only markers. Spender can transfer up to a daily limit. Proposer can submit proposals. Admin can grant roles and approve/reject proposals. The Foundation owner is always an implicit Admin.
Grant role
Daily limit is only used for the Spender role; leave blank for others.
Calls pallet 15, call_index 0 (grant_role) — phone signs.
Transfer
Moves HKEY out of the keyless treasury. Admin: unlimited. Spender: gated by daily limit.
Pallet 15, call_index 2 (treasury_transfer).
Proposals
Submit a proposal
Pallet 15, call_index 3 (submit_proposal). Admin approval required to execute.
Pending proposals
Every parameter change goes through the propose-and-approve flow. The current approval threshold is shown below and is itself foundation-tunable via meta-governance.
Recently executed proposals
Foundation Governance
Meta-governance
Blockchain Parameters
Any Foundation member can update economic parameters. Changes take effect immediately on-chain.
Reward Distribution
Fee Rates
Fee Split
Validator Lifecycle
Prune inactive nodes now
The inactivity sweep runs every 600 blocks (~1 hour). This button triggers it immediately. Validators at ≥ 90 % of the threshold are highlighted red in the activity table below — they'll be released on the next sweep.
Runtime Parameters (Owner Only)
Reward Period (live)
Period-based-rewards (spec 146+) pools per-block rewards and
distributes proportionally to each validator's healthy
intervals at period close. Foundation-tunable cadence via
set_epoch_length + the 9 new
SetSlotFulfilmentThreshold / SetPeerQuorumPct /
etc. governance variants.
—
—
—
—
—
—
Auto-refreshed every 30 s. Values come from
HesskeyRewards storage; settings without an
explicit governance write fall back to the runtime defaults
(80 / 50 / 50).
Off-chain heartbeat attestations (live)
Every validator's off-chain worker fires every
50 blocks. Each
submits a 4-byte vouches mask saying which peers it
could reach via HTTP probe. Bit i of the mask = "I vouch
for the DID at PeriodValidatorOrder[i]".
| # | DID | Submissions | Latest sample | Vouches (hex) | Vouched-for indices |
|---|---|---|---|---|---|
| no data yet | |||||
IPFS Storage (quota tiers + pin/unpin)
Pin / unpin CIDs against your own per-DID quota.
Pinning charges size_bytes against your
tier (node-owner / non-node / unregistered). Tier
limits are foundation-tunable via the proposal flow.
Per-DID quota tiers
—
non-node: —
unregistered: —
Pin a CID (charges your quota)
Unpin a CID
Pallet Controls
Pause or unpause pallets. Any Foundation member can toggle pallet status.
Governance Whitelist
Add or remove accounts from the governance whitelist (fee-exempt, etc.).
● Live · Org / Event / Ticket on-chain (pallet-object)
pallet-object is live on-chain: Org / Event / Ticket are
real, ownable objects with the live counts below. Person is the identity layer —
your eID-verified DID in pallet-did, the root every object hangs off; it is created by
registration and is never minted as an object (the anti-Sybil guarantee). Domain, Membership
and ConcertTicket are previewed — they arrive with pallet-object-types,
the Foundation-governed type registry.
Design spec ↗
All building blocks
Each binds a claim schema, a storage profile, a mint-fee and authorization.
| Building block | Built on | Mint fee | Storage | Objects |
|---|---|---|---|---|
| Person | — | free | creds RF3 | 12,480 |
| Domain | — | 0.20 | meta RF3 | 96 |
| Organisation | — | 0.05 | meta·docs RF3 | 342 |
| Event | — | 0.01 | meta RF3 | 5,233 |
| Membership | — | 0.005 | cred RF3 | 9,540 |
| Ticket | — | 0.002 | cred RF3 | 210,400 |
| ConcertTicket | ▸ Ticket | 0.002 | cred RF3 · media 10/14 | 88,900 |
Coming soon · preview with illustrative data
Live data arrives with pallet-storage-policy.
“Available” counts only proven capacity — providers passing
retrievability audits — never claimed disks.
Design spec ↗
Network storage
Whole-network proven capacity, durability and the lending market.
1,240 storage providers · 12 validators (decoupled) · 18 regions · 99.96% audit pass · RF≥3 auto-repair · quota 300 GB / 1 GB (Foundation-tunable).