5ire · Authentication Profile

5Ire Authentication

Authentication

5ire secures its APIs with none across 3 declared security schemes, as derived from its OpenAPI definitions.

blockchainlayer-1smart-contractsevmweb3substratejson-rpcsustainabilityesgproof-of-stakecryptocurrencydeveloper-tools

Methods: none Schemes: 3 OAuth flows: API key in:

Security Schemes

none none

Source

Authentication Profile

generated: '2026-08-02'
method: searched
source: >-
  https://docs.5ire.org/build-on-5irechain/evm-compatibility/, https://docs.5ire.org/wallets/metamask/,
  https://github.com/5ire-tech/5ireChain (README node flags), ethereum-lists/chains entries 995 and 997.
  Content verified via Internet Archive captures (2025-02 / 2025-03); live origin returned HTTP 530 on 2026-08-02.
docs: https://docs.5ire.org/build-on-5irechain/evm-compatibility/
summary:
  types:
    - none
  api_key_in: []
  oauth2_flows: []
  transport_auth: false
  request_auth: cryptographic-signature
  note: >-
    5ireChain exposes no HTTP-layer authentication. The public JSON-RPC endpoints accept anonymous requests with no
    API key, bearer token, basic credential, OAuth 2.0 flow, OpenID Connect issuer or mutual TLS. Authorization is
    not an API concern at all: read methods are unauthenticated by design, and any state-changing call is an
    ECDSA-signed transaction (secp256k1 on the EVM side, sr25519/ed25519 on the native Substrate side) whose
    authority comes from the signing key held in the caller's wallet, not from a credential presented to the
    endpoint. There are consequently no scopes, no token lifetimes and no scopes/ artifact for this provider.
schemes:
  - name: none
    type: none
    surface: 5ireChain Mainnet JSON-RPC (https://rpc.5ire.network)
    description: Public, unauthenticated Ethereum JSON-RPC 2.0. No credential is accepted or required.
    sources:
      - https://docs.5ire.org/build-on-5irechain/evm-compatibility/
  - name: none
    type: none
    surface: 5ireChain Thunder Testnet JSON-RPC (https://rpc.testnet.5ire.network)
    description: Public, unauthenticated Ethereum JSON-RPC 2.0.
    sources:
      - https://docs.5ire.org/wallets/metamask/
  - name: none
    type: none
    surface: 5ireChain Native Substrate RPC (WebSocket, port 9944)
    description: >-
      Public Substrate RPC. Self-hosted nodes gate exposure with node CLI flags (--rpc-external, --rpc-cors,
      --rpc-methods) rather than with credentials.
    sources:
      - https://github.com/5ire-tech/5ireChain
transaction_signing:
  evm:
    curve: secp256k1
    scheme: ECDSA
    chain_id_binding: EIP-155 (995 mainnet / 997 Thunder testnet)
    replay_protection: per-account nonce plus chain-ID binding
    wallets:
      - MetaMask
      - 5ire Wallet browser extension
    docs: https://docs.5ire.org/wallets/metamask/
  native:
    curves:
      - sr25519
      - ed25519
    scheme: Substrate SignedExtrinsic
    replay_protection: per-account nonce plus mortal era and genesis-hash binding
    wallets:
      - 5ire Wallet browser extension
    docs: https://docs.5ire.org/wallets/5ire-wallet-extension/
gaps:
  - No API-key or token issuance surface exists, so there is no key rotation, revocation or scope model to document.
  - No OpenAPI document is published, so no securitySchemes could be derived mechanically.
  - No /.well-known/openid-configuration or /.well-known/oauth-authorization-server was retrievable on any host.