InfStones Documentation

OKC Archive API

Below you will find the API documentation for the standard OKC Archive JSON-RPC calls that InfStones supports.

1 Overview

InfStones provides access to API endpoints for developers building on the OKC Archive chain. Developers can interact with on-chain data and send different types of transactions to the network by utilizing the API endpoints.
OKC Archive API follows a JSON-RPC standard. JSON-RPC is a stateless, lightweight, remote procedure call (RPC) protocol that is commonly used when interacting with OKC Archive chain.

2 Types of Requests in the OKC Archive API

2.1 Getting Blocks

Retrieves information from a particular block in the blockchain.

2.2 Reading Transactions

Retrieves information on the state data for addresses regardless of whether it is a user or a smart contract.

2.3 Writing Transactions

Allows developers to both send ETH from one address to another, write data on-chain, and interact with smart contracts.

2.4 Account Information

Returns information regarding an address's stored on-chain data.

2.5 EVM/Smart Contract Execution

Allows developers to read data from the blockchain which includes executing smart contracts. However, no data is published to the OKC Archive network.

2.6 Event Logs

Returns logs which are records that denote/provide context on specific events within a smart contract, like a token transfer or a change of ownership for example.

2.7 Chain Information

Returns information on the OKC Archive network and internal settings.

2.8 Filters

Allows developers to filter and query for specific OKC Archive logs.

2.9 Web3

Returns OKC Archive network web3 related operations