Object Endpoints

This section documents the endpoints used to query specific Object capabilities and state within the Brixs network.

Get Object Data

Retrieves the data, balance, and ownership status of a specific Brixs Object.

Method: brixs_getObject

Request Payload

Code

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "brixs_getObject",
  "params": ["0xabcd12347890ffff"]
}

Expected Response

Code

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "objectId": "0xabcd12347890ffff",
    "version": 5,
    "owner": "0x9999888877776666",
    "type": "0x2::coin::Coin<0x2::brx::BRX>",
    "lockedUntil": null
  }
}

Handling Object Mutations

Phase 1: Engine Initialization

The first phase requires a comprehensive setup of the execution environment. The Brixs Native EVM initializes the state and establishes secure connections with the P2P network. This ensures that when the DPoS Sequencer begins proposing blocks, there are no bottlenecks in transaction ingestion.