Norsh
HomeNTPNCLAPI
HomeNTPNCLAPI
  1. Norsh
  • 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. Norsh

API

This section is the official repository of public APIs for the Norsh ecosystem. All available endpoints are documented here with structure, parameters, and response formats. Users can explore, test, and integrate these APIs directly from this interface, using consistent models across environments.
The Norsh API follows the structural and encoding standards defined in:
NTP-4: Interchangeable Data Standard – Establishes JSON as the required format for all input/output structures.
NTP-2: Standards for Encoding, Time and Localization – Defines timestamp formatting, numeric conventions, and encoding behavior.
All communication must use UTF-8 encoded JSON, with exact field names, no dynamic keys, and standardized representations.

Rules and Behavior#

All endpoints are stateless and self-contained.
Responses include a timestamp in milliseconds since epoch (UTC).
Numeric formats follow the US pattern: 0.000,00 → 1,000.00.
Binary data must be encoded as Base64 or Hex—raw binary is prohibited.
No optional fields outside the defined schema are accepted.
These constraints apply across internal systems, smart elements, ledgers, and third-party integrations. Full compliance with NTP-2 and NTP-4 is required.
Modified at 2025-06-05 19:56:16
Previous
Cryptographic Identity
Next
Crypto
Built with