Provenance · Authentication Profile

Provenance Authentication

Authentication

Provenance secures its APIs with none-for-reads and signature-based-for-writes across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyBlockchainFinancial ServicesTokenizationReal-World AssetsCosmos SDKgRPCWeb3DeFiDigital Assets
Methods: none-for-reads, signature-based-for-writes Schemes: 2 OAuth flows: API key in:

Security Schemes

PublicQuery none
TransactionSignature signature

Source

Authentication Profile

provenance-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: >-
  docs.provenance.io + Cosmos SDK transaction model (grpc/*.proto Msg services). No
  OpenAPI securitySchemes exist; the auth model is the Cosmos public-chain model.
summary:
  types: [none-for-reads, signature-based-for-writes]
  api_key_in: []
  oauth2_flows: []
schemes:
- name: PublicQuery
  type: none
  applies_to: All Query (read) operations over REST (api.provenance.io), gRPC, and RPC.
  note: Chain state is public; no credentials required to read.
- name: TransactionSignature
  type: signature
  algorithm: secp256k1
  applies_to: All Msg (write) operations that broadcast transactions.
  note: >-
    State-changing transactions are signed by the sending account's private key
    (secp256k1) and validated by consensus using the account's public key, sequence
    (nonce), and chain-id. Granular delegation is available via the Cosmos authz and
    feegrant modules and Provenance marker access grants.