Trust Anchor
- IPNS ID
- Published
- Revision
Contacting the appliance…
This appliance
Enroll a public identity, then prove possession with a NOMOI mandate.
Progress refreshes while this screen is open. “Observed” means the publication is available. Successful operator sign-in permanently closes password setup.
Enrolled and published?
This appliance
Present a mandate, then sign a short-lived challenge — with a key in this browser, or in your own terminal. Your signing key stays on your computer.
An enrolled operator, or a newly created TA's designated administrator, also gets management access with their own sign-in mandate.
or sign in your own terminal
A challenge lasts at most a minute. Keep your terminal ready before requesting one, or keep keys in this browser.
The terminal route issues the same 30-second challenge for nomos sign.
Expired — request a new challenge.
or sign in your own terminal
nomos-login-mandate.pem next to where you run the command. Requires a CLI with --mandate-file support.This browser
This browser cannot run the key wallet. Use nomos id and nomos sign instead.
Signing keys, kept encrypted in this browser in the CLI’s own key-file format. Nothing here is sent to the appliance.
Keys are stored the way the CLI stores them: encrypted under your passphrase, in the same file format. Save each key file — clearing this site's data deletes the browser's copy. A saved key file works as ~/.config/nomos/ids/<name>, and CLI key files import here. Unlocked keys stay in memory only while this tab is open.
This browser
Mandates held here, by leaf CID, and the ones you issue. Nothing leaves this browser until you publish it.
This browser cannot run the key wallet. Use nomos issue and nomos verify instead.
Check this before you sign. It is decoded from the exact bytes that will be signed.
Mandate signed and kept in this browser. It is not published: hand the presentation to its subject, or publish it so verifiers can fetch it.
Publish this mandate and its chain to the appliance's IPFS node? Anyone can then fetch it by CID and see its scope, keys and validity; it cannot be withdrawn. Verifiers will no longer need its full chain shown to them.
Publish this mandate and its chain to the appliance's IPFS node? Anyone can then fetch it by CID and see its scope, keys and validity; it cannot be withdrawn. Verifiers will no longer need its full chain shown to them.
Remove this mandate from the browser? It stays valid wherever else it is held.
A backup holds every mandate here, for another browser or this one once its data is cleared. It holds no key.
This browser
Verify a mandate held in this browser, or one on another device by exchanging three QR codes: mandate → challenge → response.
Check anyone's mandate with a Trust Anchor's verifier, then have its holder prove they hold the key it delegates to: in this browser when it holds that key, or on their own device by QR code. Nothing here signs anyone in.
Check a stamp or crew membership with a verifier, and have its holder prove they hold the identity it was given to, on their own device by QR code. Nothing here signs anyone in.
Scanning checks it and challenges its holder straight away. Have them ready to scan back: the challenge lasts seconds, not minutes.
Expired — challenge the holder again.
Have the holder scan your challenge under Present my mandate, review and sign there, then scan their response. Your verifier checks it against the challenge retained here.
Have both devices ready before requesting a challenge: it lasts at most a minute.
Problems
You are the holder. Keep your key and passphrase on this device. The person verifying you scans and verifies on their separate device.
No mandates for your keys are stored here. Add your mandate on Mandates first.
No stamps for your identities are stored here. Collect one under My passport first.
A signature proves possession of the mandate’s key. Confirm who is asking and what they intend to verify before signing; a live challenge can be relayed.
This device signs for the mandate you chose, decoded here. The requesting verifier checks its authority.
The verifier’s screen counts down its challenge: sign before it runs out, or ask for a new one.
Have the verifier scan this QR code on their device. They check it against their original challenge.
Updating workspace…
Previously loaded information may be out of date.
your mandate
This Trust Anchor as a verifier resolves it now.
Trust Anchor
No audit events recorded for this TA.
Only reads recorded so far.
Nothing needs you right now.
No publications recorded for this TA.
A publication is complete once its state is observed. The last five are shown.
This session reads what the Trust Anchor publishes. Editing it takes an administration mandate.
your mandate
No Trust Anchors yet
Create one under New TA. Its namespace, state and provisioning progress appear here.
Nothing provisioning
Create a TA to follow its provisioning here.
your mandate
or anywhere
Read from IPFS, not from this appliance:
Suspended: its verifier is stopped and queued publications wait. Resume or delete it from the TA directory.
Open a saved draft or delete its editable copy. Deletion also closes it if open, discarding unsaved edits. Publishing a draft removes it too; its publication keeps the snapshot. Published policy and publication snapshots are retained.
No draft open
New drafts start from the published policy. Change roots, trusted namespaces and revocations, save, then publish one immutable revision.
You prepare it with your operator session. Saved drafts are available to this TA’s administrators by ID, and changes are recorded in both audit logs.
The root identities its published policy names, marked where one is registered as an operator on this appliance, then registered operators it does not name as roots.
No root identities or operators.
The bin removes an operator registration from this TA immediately after confirmation, including initial administrators and keys listed as roots. Published roots, saved drafts, queued publications and the self session remain independent. Use “Remove root from draft”, then save and publish, to withdraw root authority separately.
No known identities.
Known identities are kept on the appliance that manages a TA, and this one does not manage it. They are not published.
These are this TA's known identities: its administrators see them under Policy and issue mandates to them from Keys. A known identity grants nothing, so keeping the list grants nothing either. Both this TA's audit log and the operator's record each change.
No publications.
Publication jobs are run by the appliance that manages a TA, and this one does not manage it. What it published is under History.
No events to show.
The audit log is kept by the appliance that manages a TA, and this one does not manage it. What it published is under History.
Load more to reach the latest events.
Follows each state's previous CID back, as nomos ta audit does: from the TA's current state, resolved afresh, or from the state CID it was given.
your mandate
Publication may take time; a job is complete only when its state is observed.
Listed on the sign-in page
Listing only offers it for choosing. Anyone who knows this TA’s IPNS ID can still verify against it through the API.
Open a saved draft or delete its editable copy. Deletion also closes it if open, discarding unsaved edits. Publishing a draft removes it too; its publication keeps the snapshot. Published policy and publication snapshots are retained.
No draft open
New drafts start from the published policy. Change roots, trusted namespaces and revocations, save, then publish one immutable revision.
You prepare it with your operator session. Saved drafts are available to this TA’s administrators by ID, and changes are recorded in both audit logs.
An operator is a key this TA may name as a root. Registering one grants no authority until it is a root of a published policy. Removing a registration leaves published roots, saved drafts, queued publications and bootstrap enrollment unchanged. To withdraw root authority, edit and publish a policy draft.
The root identities the published policy names, marked where one is registered as an operator on this appliance, then registered operators it does not name as roots.
No root identities or operators yet.
A known identity names a public key for this TA, so that any of its administrators can issue a mandate to it without pasting the key. It grants nothing and cannot be a policy root — register it under Operators for that. The pencil beside one renames it, as does adding its key again; removing one does not revoke mandates already issued to it.
No known identities yet. Add the people and services you issue mandates to.
If sign-in or publication was interrupted, open it here to load its status and any saved draft. Unsaved edits stay in this browser tab during sign-in; reloading discards them.
Save your edits before opening another draft or publication.
Retrying.
Resolves this TA's IPNS name afresh and follows each state's previous CID back, as nomos ta audit does. It reads the published states themselves, so publications from the CLI appear too.
your mandate
Rechecks the login mandate with its TA verifier. A rejected chain and an unavailable verifier remain distinct; neither grants access.
No publications yet
Policy updates and their delivery status appear here.
A record of every action
Who changed what, with which mandate, and the result.
No loaded events match the filter.
Load more to reach the latest events.