Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt

Use this file to discover all available pages before exploring further.

The Cryptography endpoints manage the cryptographic keys that underpin Legal Identities, smart contracts, vault links, and other signing operations on the Neuron platform. Before you can apply for a Legal Identity or sign a contract, you must:
  1. Call Get algorithms to discover which algorithms are available on the broker.
  2. Call Create key to generate a key pair using one of those algorithms.
  3. Use the resulting keyId in identity applications, contract signing, and vault link creation.

Endpoints

EndpointDescription
Get algorithmsList all cryptographic algorithms supported by the broker, including security strength, PQC status, and a score for ordering.
Create keyCreate a new cryptographic key pair on the server, protected by a key password. Returns the key’s creation timestamp.
Get public keyRetrieve the server’s public key, or the public key of a specific account key. Use this to verify server-issued signatures.

Algorithm properties

Each algorithm returned by Get algorithms includes:
FieldDescription
localName / namespaceUnique algorithm identifier used in Create key.
securityStrengthSecurity strength in bits.
safeWhether the curve is considered safe per safecurves.cr.yp.to.
slowWhether the algorithm is computationally intensive.
pqcWhether the algorithm is Post-Quantum Cryptography (PQC).
scoreRelative score — use with securityStrength to rank algorithms.

Key storage and security

  • Keys are stored encrypted on the server, protected by the key password.
  • The key password is never stored — instead, a signature derived from it is used to reconstruct the encryption key.
  • All operations that use a key require keySignature (signed with the key password) and requestSignature (signed with the account password).
  • Reusing a nonce will result in an error.
  • Legal identities — keys are required to apply for and sign identity applications.
  • Contracts — keys are required to sign smart contracts.
  • Storage — keys are used to sign vault link creation requests.