generated: '2026-07-17'
method: searched
source: https://docs.alpenlabs.io/build-alpen-apps/rpc-endpoints
summary: >-
  Cross-cutting standards Alpen's developer surface conforms to, asserted from the public
  RPC-endpoints and getting-started documentation. Alpen is not a REST/OpenAPI provider;
  its interface is JSON-RPC 2.0 in the Ethereum tradition. No published compliance
  program (SOC 2 / ISO 27001 / PCI / HIPAA) — security posture is covered by third-party
  audits (see security/alpen-labs-vulnerability-disclosure.yml), not a Compliance pointer.
standards:
- id: json-rpc-2.0
  conforms: true
  evidence: developer interface is a JSON-RPC endpoint (rpc.testnet.alpenlabs.io)
- id: ethereum-json-rpc
  conforms: true
  evidence: full node exposes standard eth_* Ethereum-compatible RPC methods
- id: evm
  conforms: true
  evidence: EVM-compatible validity rollup; deploys standard Solidity contracts; chain ID 8150
- id: erc-4337-account-abstraction
  conforms: true
  evidence: bundler exposes eth_sendUserOperation, eth_estimateUserOperationGas, eth_getUserOperationByHash, eth_getUserOperationReceipt, eth_supportedEntryPoints
- id: eip-7769
  conforms: true
  evidence: ERC-4337 bundler RPC follows the EIP-7769 specification
- id: ethereum-prague-spec
  conforms: true
  evidence: testnet regenesis implemented the Prague execution-layer spec
- id: bip39
  conforms: true
  evidence: alpen CLI wallet exports/recovers a BIP39 mnemonic
- id: rfc9116-security-txt
  conforms: true
  evidence: /.well-known/security.txt published (RFC 9116)
- id: rest-openapi
  conforms: false
  evidence: no REST/OpenAPI surface; interface is JSON-RPC only
- id: oauth2
  conforms: false
  evidence: public RPC endpoints require no OAuth