OdyCust/ GUIDE
УКР

Sign Nodes

Pair the exact service identity before separately authorizing source access.

Step by step

  1. Open Settings → Sign Nodes. A configured candidate is operator-approved transport configuration, not a paired organization service or an online status.
  2. Choose the candidate, enter its name and create a pairing invitation. Complete normal platform confirmation. The original public operation ID and name survive a lost response; recover that invitation instead of guessing a new one.
  3. Choose Check service identity. The backend contacts its pinned service and saves the public proof. Compare the backend origin, receipt-key fingerprint and transport SPKI fingerprint with your expected operator configuration.
  4. Select the review checkbox and Confirm pairing before expiry. Proof alone is not pairing. An expired invitation cannot be extended: start a new invitation explicitly. Reading the original state does not repeat confirmation.
  5. After confirmation, review the saved result and choose Finish pairing review. Until then, reopening the page returns to the same invitation without repeating confirmation.
  6. Revocation requires the current revision, exact DELETE and platform confirmation. It retains keys/transcripts and cannot cancel or reassign an unknown signing operation. A new pairing after revocation requires another proof and review.
  7. Open Wallet sources and a ready address to create its separate signer association. Pairing this service never automatically associates every Wallet Node.
  8. Registered devices and their exact address associations are readable, without a TLS fingerprint. An already confirmed device association can be selected for a human HD wallet transfer under current permissions. Device pairing, proof submission, revocation and private key import are not controls in this interface; service import, standalone keys and automations keep their existing service transport.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.