Fullnode Rest API

Use the Endless Fullnode REST API

If you wish to employ the Endless API, then this guide is for you. This guide will walk you through all you need to integrate the Endless blockchain into your platform with the Endless API.

Also see the System Integrators Guide for a thorough walkthrough of Endless integration.

Viewing current and historical state

Most integrations into the Endless blockchain benefit from a holistic and comprehensive overview of the current and historical state of the blockchain. Endless provides historical transactions, state, and events, all the result of transaction execution.

• Historical transactions specify the execution status, output, and tie to related events. Each transaction has a unique version number associated with it that dictates its global sequential ordering in the history of the blockchain ledger.

• The state is the representation of all transaction outputs up to a specific version. In other words, a state version is the accumulation of all transactions inclusive of that transaction version.

• As transactions execute, they may emit events. Events are hints about changes in on-chain data.

Ensure the fullnode you are communicating with is up-to-date.

The fullnode must reach the version containing your transaction to retrieve relevant data from it. There can be latency from the fullnodes retrieving state from validator fullnodes, which in turn rely upon validator nodes as the source of truth.

The storage service on a node employs two forms of pruning that erase data from nodes:

• state

• events, transactions, and everything else

While either of these may be disabled, storing the state versions is not particularly sustainable.

Events and transactions pruning can be disabled via setting the enable_ledger_pruner to false in storage_config.rs. This is default behavior in Mainnet. In the near future, Endless will provide indexers that mitigate the need to directly query from a node.

The REST API offers querying transactions and events in these ways:

• Transactions for an account
• Transactions by version
• Events by event handle

Reading state with the View function

View functions do not modify blockchain state when called from the API. A View can be used to read potentially complex on-chain state using Move. For example, you can evaluate the EDS changes due to the transactions of blocks. Here are related files:

• view_function.rs for an example
• related Move code
• specification.

The view function operates like the Endless Simulation API, though with no side effects and an accessible output path. View functions can be called via the /view endpoint. Calls to view functions require the module and function names along with input type parameters and values.

A function does not have to be immutable to be tagged as #[view], but if the function is mutable it will not result in state mutation when called from the API. If you want to tag a mutable function as #[view], consider making it private so that it cannot be maliciously called during runtime.

In order to use the View functions, you need to publish the module through the Endless CLI.

In the Endless CLI, a view function request would look like this:

endless move view --function-id devnet::message::get_message --profile devnet --args address:devnet
{
  "Result": [
    "View functions rock!"
  ]
}

In the TypeScript SDK, a view function request would look like this:

    const payload: InputViewFunctionData = {
      function: "0x1::primary_fungible_store::balance",
      functionArguments: [aliceAccountAddr, fungibleAssetMetadataAddress.toString()],
      typeArguments: ["0x1::fungible_asset::Metadata"],
    };

    const balance = (await view<[string]>({ endlessConfig, payload }))[0];;

    expect(balance[0]).toBe("100000000");

The view function returns a list of values as a vector. By default, the results are returned in JSON format; however, they can be optionally returned in Binary Canonical Serialization (BCS) encoded format.