They land on as provisioned — issued, not yet on any account — with the whose and authority set in the single-key form, and a note saying they came in by paste so it is plain the details are still to fill in.
Keys you watch
current · due soon · overdue · unconfirmed — never proven, or overdue too long to count on
Accounts you look after
Paste anything with account ids in it — a list, a document, a hashscan page. Every 0.0.N is picked out, added for the network selected above, and looked up on that network's mirror node at once — its key structure, its last account update, and its balance. Look up asks again later. Then the rings: inner is what the chain requires, m of n; outer is one wedge per key, the key's own traffic light — green current, amber due, red overdue, grey never proven — and pale for a key we have no record of. A key that is a salted child of a master you hold is found from the master alone. Salted with something other than the account number? Write it as KSUB does — 0.0.28897(28) — and that salt is kept on the account and tried too; pasting an account again with brackets sets the salt on one already listed. Anything else on the line goes into those accounts' notes; a line with no accounts on it is a note for all of them.
current · check due · overdue · never proven · not on record
A group's colour is derived from its keys: the colour of the worst key its threshold has to count. Current keys alone meet it — green; it needs a due key — amber; an overdue one — red; a never-proven one — grey; it cannot be met with the keys on record — pale.
Fragments
A key built from parts — KSIGN assembles one from several fragments — leaves no trace of the parts on chain, so two keys that share a fragment look unrelated. This is the record of that: a name for each fragment, who holds it, notes. Never the fragment itself. Add fragments to a key on its card; the record is created as you do, on the network selected above — a fragment sits on one network and shows only there. Each fragment then shows every key built from it, and every account and token those keys reach — what is exposed if it is lost or taken.
Tokens you look after
Paste anything with token ids in it. Each is looked up on the network selected above: its name, symbol, treasury, and every key it has — admin, supply, freeze, wipe, KYC, pause, fee schedule, metadata — each a key tree drawn and matched to this ledger like an account's. Searching for an id that is not an account finds the token. The treasury is a link to the account.
current · check due · overdue · never proven · not on record — per key role; the token's own light is the worst of its keys on record
Files
Cluster
Start from one or more accounts. Forward: the keys that sit on them (directly or as salted children), the fragments those keys were built from, the tokens they are treasury of and those tokens' keys. Then backward: anything else those keys and fragments reach. If that finds more accounts, the set is not closed — a key or a fragment is shared with something outside it — and you can widen to the smallest closed set. A closed cluster is a natural unit to back up on its own, and to keep small.
Clusters on
Every account on this network, grouped into closed sets. Big ones are where a single key or fragment reaches a lot.
Search
A public key, any part of one (the last four characters are enough), an account id or just its number, or any word from a name, a note, a memo or a rotation reason. Both kinds, both networks. If what you type is a well-formed key, account or token that is not here yet, you are offered the chance to add it — an id is tried as an account, then as a token.
Activity
What you have been doing lately, newest first, each line linking to what it is about. This is a convenience — somewhere to pick up a session from — not an audit trail: nothing here is signed or verifiable, lines can be deleted, and it is deliberately left out of Back up, which carries current state only.
—
The ladder
Levels are qualifications, not vanity. Demotion happens on Unconfirmed, never on a single miss. Guardian and Steward need attested custody and recovery drills, which this device cannot measure alone.
About KPOP
The idea. A keyholder is never asked to sign a transaction. Every so often, inside a window they cannot predict, they prove one thing: can you still produce a signature with this key? Everything else — how much the key controls, whether a recovery could be satisfied today — is derived from those proofs.
Four states. Current, due soon, overdue, unconfirmed. Overdue is not lost. The app never records "key lost"; it records "possession not demonstrated within policy".
Policy. Set by the key's authority: how often, within what window, how fast, with what verification. Practice keys are weekly with a day to answer; critical keys weekly with an hour, on an attested device.
What it holds. Public keys, names, custody notes, receipts. No secrets, nothing that can sign. All of it in this browser; Back up hands it to you as one line.
What it does not do. Sign — that is KSIGN's, or a wallet's. Talk to a server — sharing is by paste. Issue notifications — a static page cannot; the window and the issue day are shown instead.
Online, when you ask. Look up accounts on a key asks the public Hedera mirror node which accounts use it. Nothing else ever leaves the device.
Versions. The footer shows the build running in this tab. KPOP keeps its own copy of itself so it opens with no network, which means a new deploy does not appear until that copy is replaced — when one is out, a banner offers it. If a browser ever gets stuck on an old build, Get a fresh copy below drops the cached copy and reloads. It does not touch your keys, names or receipts: those live in this browser's storage, which neither button goes near.
Tools alongside. kcrawl finds accounts connected to ones you already know — created by, sent to, received from, same key — one hop at a time, with counts before anything is added; paste its results into the Accounts tab. KBQR turns any text into a set of QR codes you can print or play as an animation, and reads them back — paste a Back up line into it for a paper copy. Both run entirely on the device.
Questions and what comes next. The FAQ covers why the challenge is what it is, the four states, the network rule, and — separately from rotation — the flows where custody itself moves: a leak and break-glass, an interim 1-of-1, a hand-over, a sale. It is the working notes for where KPOP goes.