Seismic Systems · Authentication Profile

Seismic Systems Authentication

Authentication

Seismic's authentication model has two distinct layers. (1) The SRC20 Factory REST API is unauthenticated and read-only — it uses a public provider and holds no key. (2) On-chain interaction is authenticated cryptographically: writes are signed Seismic transactions (EIP-712 typed data, tx type 0x4A) and "signed reads" are authenticated eth_call requests that prove the caller's identity to the contract, with calldata encrypted to the node's TEE key via ECDH + AES-GCM. There is no OAuth, no API-key issuance, and no scopes surface.

Seismic Systems secures its APIs with none and wallet-signature across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyBlockchainPrivacyEncryptionStablecoinsFintechWeb3Smart ContractsEVMCryptographyDeveloper Tools
Methods: none, wallet-signature Schemes: 3 OAuth flows: API key in:

Security Schemes

rest-public none
seismic-signed-transaction wallet-signature
scheme: EIP-712 typed-data signature (Seismic tx type 0x4A)
seismic-signed-read wallet-signature
scheme: Authenticated eth_call (signed read)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://docs.seismic.systems/reference/seismic-transaction/signed-reads.md
docs:
  - https://docs.seismic.systems/reference/seismic-transaction.md
  - https://docs.seismic.systems/reference/seismic-transaction/signed-reads.md
  - https://docs.seismic.systems/getting-started/src20-factory/api.md
description: >-
  Seismic's authentication model has two distinct layers. (1) The SRC20 Factory
  REST API is unauthenticated and read-only — it uses a public provider and holds
  no key. (2) On-chain interaction is authenticated cryptographically: writes are
  signed Seismic transactions (EIP-712 typed data, tx type 0x4A) and "signed
  reads" are authenticated eth_call requests that prove the caller's identity to
  the contract, with calldata encrypted to the node's TEE key via ECDH + AES-GCM.
  There is no OAuth, no API-key issuance, and no scopes surface.
summary:
  types: [none, wallet-signature]
  rest_api_auth: none
  onchain_auth: [eip712-signed-transaction, signed-read, tee-ecdh-encryption]
  oauth2_flows: []
schemes:
  - name: rest-public
    layer: rest-api
    type: none
    applies_to: openapi/seismic-systems-src20-factory-openapi.yml
    detail: The SRC20 Factory REST API requires no credentials and can only read public state.
  - name: seismic-signed-transaction
    layer: on-chain
    type: wallet-signature
    scheme: EIP-712 typed-data signature (Seismic tx type 0x4A)
    detail: >-
      Shielded writes are signed with the developer's wallet key and submitted via
      eth_sendRawTransaction; calldata is AES-GCM encrypted to the node TEE public key
      obtained through seismic_getTeePublicKey and an ECDH key exchange.
  - name: seismic-signed-read
    layer: on-chain
    type: wallet-signature
    scheme: Authenticated eth_call (signed read)
    detail: >-
      Read calls that prove caller identity to the contract so a user can access their own
      shielded state (e.g. their SRC20 balance) without exposing it to others.