Norsh
HomeNTPNCLAPI
HomeNTPNCLAPI
  1. Usage Guide
  • Norsh
    • Usage Guide
      • Cryptographic Identity
    • API
      • Crypto
        • Generates a public and private key pair
        • Generates an address from a public key.
  • NTP - Norsh Technical Paper
    • LICENSE-NCL-11
    • Published
      • NTP-1: Norsh Technical Paper Specification
      • NTP-2: Standards for Encoding, Time and Localization
      • NTP-3: Cryptography and Hash Specification
      • NTP-4: Interchangeable Data Standard
      • NTP-5: Temporal Time-Step Model
      • NTP-6: Modular Prime Fragmentation
      • NTP-7: The End of Mining - PoW
      • NTP-8: The Fallacy of Stake - PoS
      • NTP-9: The Myth of Absolute Non-Censorship
      • NTP-10: Structural Failures of Decentralization
  • NCL - Norsh Commons License
    • NCL-0: Norsh Commons License
    • NCL-1: Attribution Requirement
    • NCL-2: Restricted Commercialization
    • NCL-4: Commercialization with Agreement or Royalties
    • NCL-8: Educational Use Permission
    • NCL-16: Complementary Use and Integration Permission
    • NCL-32: Pre-Approval for Application Publication
    • NCL-64: Restricted or Authorized Derivatives
    • NCL-128: Contribution Terms
  1. Usage Guide

Cryptographic Identity

In the Norsh ecosystem, your identity is created and validated through a pair of cryptographic keys. There are no usernames, passwords or conventional accounts. Instead, all authentication, ownership and communication are tied to a public key, and to a unique address derived from it.
If you lose your private key, your identity cannot be recovered.
If your private key is exposed, your identity can be stolen.
There is no fallback, no password reset, and no admin override.
Security begins at the key.
This process involves two fundamental steps.

Step 1 - Generate your key pair#

Use the endpoint: POST /v1/crypto/keys
You will receive:
A private key, which must be stored with absolute security
A public key, which can be shared and is used to generate your address
The private key is your only proof of control.
If it is lost or exposed, your identity, assets and permissions are irreversibly compromised.
Never share it, never transmit it, never expose it to client interfaces or third-party systems.
Your private key must be stored in a secure location, such as a hardware device, an encrypted file, or a certified key vault. Norsh does not store or recover any keys. Responsibility is entirely on the user or the application managing the keys.

Step 2 - Derive your address#

Use the endpoint: POST /v1/crypto/address
Provide your public key as input. You will receive a 64-character SHA3-256 address. This is your unique and permanent identifier across the Norsh network.
This address is your:
Wallet ID
Owner ID
Element controller
Sender and recipient in all transactions
Once generated, this address is used in all interactions with Norsh, including sending transactions, executing actions, authorizing elements, and receiving assets.

Ongoing usage#

From this point forward, the public key and the derived address are used in all systems. The private key is used to sign any request or transaction that requires proof of authority.
Every API that performs a sensitive operation expects the request to be signed using the private key, and verifiable using the public key. This guarantees that only the rightful holder of a key can perform operations under that identity.

Reference Standards#

This process is based on the technical rules defined in:
NTP-3: Cryptography and Hash Specification — which defines key generation, elliptic curve parameters, and hashing
NTP-2: Standards for Encoding, Time and Localization — which defines how keys, addresses and metadata must be formatted and encoded in the API responses
All keys are generated using ECDSA with curve secp256r1, and all addresses are derived using SHA3-256 from the raw bytes of the public key, as described in the specifications.
This cryptographic identity model is the foundation of all security, ownership and trust within the Norsh ecosystem. Its correct implementation and secure management are non-negotiable.
Modified at 2025-06-05 20:35:45
Next
API
Built with