Overview

Message-Specific Methods

Obsidian provides a native message submission API alongside standard Ethereum RPC:

Method	Purpose
eth_sendMessageBlob	Submit a signed message
eth_getBlockMessages	Retrieve all messages from a block
eth_getMessagesByAddress	Query messages by sender
eth_getMessageByHash	Look up a message by its hash
eth_getMessageWork	Get VDF parameters for Standard Messages
eth_getMessageBufferStatus	Get lane buffer status

Applications can treat Obsidian as both an EVM execution environment and a data publication layer, using the appropriate pathway for each workload.

Standard Methods

All standard Ethereum methods work:

• eth_blockNumber

• eth_getBlockByNumber

• eth_getBalance

• eth_sendTransaction

• etc.

Authentication

No authentication required for read methods. Write methods require valid signatures.

Rate Limits

Tier	Requests/sec
Public	10
Registered	100
Archive node	Unlimited

Response Format

Standard JSON-RPC 2.0:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": { ... }
}

Errors:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32000,
    "message": "Invalid signature"
  }
}