Running the Node
For example, the following command will pull the Docker image, start the syncing process in the testnet (
aries) environment, and expose the node's GraphQL API at
docker run -p 4000:4000 freeverseio/livingassetsnode --network aries
On a Windows OS, the GraphQL API may be exposed at
One of the main command line options,
--network, allows to select one of the two main pre-configured environments:
--network mainnet: (default) the production environment, running on Polygon's mainnet.
--network aries: the testnet environment, running on Polygon's Mumbai testnet; used for developing projects before primetime.
As usual with Docker, you may find it useful to use volumes in order to have persistent data, and avoid re-syncing from scratch after the node is restarted, e.g. by prepending
docker run -v your_vol_name:/.livingassets.
The following command line parameters may be used to override the default values:
The URL of an EVM node that the Living Assets node will use to fetch the layer-1 data required to sync. By default, environments are set to use Polygon's public nodes. For increased speed and reliability, it is recommended to specify owned or hosted nodes.
Avoids pinning the content in the ipfs node.
The node's storage type, either
The number of blocks fetched from the layer-1 node in one batch. Default value: 10000. Several Polygon node hosting services allow fetching events in larger batches; using larger values shall speed up sync, and potentially reduce costs.
The number of blocks that must pass before a layer-1 TX is considered finalized by the Living Assets node. The default value (70 blocks) is set conservatively by considering previous Polygon re-orgs.
The local path where node's data is stored. Default value:
The URL inside the docker image used to expose the node's GraphQL API. Default value:
The Living Assets Ethereum-formatted contract address used for external JSON-RPC calls. Default values are set for each environment.
Activates debug logs.
The gas fee cap (Wei) for layer-1 TXs. Default: