Run a node
Sequentia Core is the full node and its desktop wallet. It downloads and checks every block itself, follows Bitcoin testnet4 to check each block’s anchor, and is the software block producers run. It is a fork of Elements 23.3.3, itself a fork of Bitcoin Core, so anyone who has run bitcoind will find it familiar.
This page is the overview. For screen-by-screen instructions use the tester guide; for everything an operator can configure, the operator manual.
Install
Download the current release for Linux (x86-64) or Windows (64-bit) from sequentiatestnet.com/download/core and check it against the published SHA256SUMS:
sha256sum -c SHA256SUMS --ignore-missingLinux
tar xzf sequentia-core-*-linux-x86_64.tar.gzcd sequentia-core-*/bin/sequentia-qt # desktop walletWindows. Run the installer, then open Sequentia Core from the Start menu.
The testnet is the default chain and the node configures itself for it: a peer to connect to, a Bitcoin testnet4 endpoint to check anchors against, the asset registry and the price server. No configuration file is needed to get started. The first start downloads the chain.
Run it headless
The same download carries the daemon and its command-line client:
bin/sequentiad -daemonbin/sequentia-cli getblockchaininfo # height and sync progressbin/sequentia-cli getanchorstatus # the tip's Bitcoin anchor, and whether it checksbin/sequentia-cli createwallet mywalletbin/sequentia-cli getnewaddressbin/sequentia-cli stopThe data directory is ~/.elements on Linux and %APPDATA%\Elements on Windows, and the configuration file in it is elements.conf.
Use your own Bitcoin node
A Sequentia node needs to see Bitcoin. Every block names a Bitcoin block, and the node must check that the block exists and is on Bitcoin’s best chain, and must notice when Bitcoin reorganises. See Bitcoin anchoring.
Out of the box, a testnet node uses a shared Bitcoin testnet4 endpoint so that it works immediately. To validate without trusting anyone, point it at your own Bitcoin node:
# elements.conf[test]validateanchor=1mainchainrpchost=127.0.0.1mainchainrpcport=48332mainchainrpccookiefile=/home/YOU/.bitcoin/testnet4/.cookieStart your Bitcoin node first and let it finish synchronising. A Sequentia node that cannot reach Bitcoin refuses to start, or asks whether to start anyway and shows a warning for the whole session.
Whitepaper 5.5Why the Bitcoin connection is not optional
A node that stops validating anchors can no longer discover that its own chain is built on a Bitcoin block that has been orphaned.
A node may delegate anchor validation to its peers, but it then relies on them to detect Bitcoin reorganisations and to judge whether blocks made under the escape rule were entitled to be produced. That is unsuitable for a node that produces blocks or from which others synchronise.
The cost is small: with no reorganisation, each poll of Bitcoin costs a single request, whether the chain is a day or ten years old.
Choose which fee assets you accept
Your node keeps a price list: the assets it accepts as fees, each with a rate. It decides which waiting transactions your node relays and, if you produce blocks, which you include. See The open fee market.
On the testnet a node reads the network’s price server by default. You can connect to a different one, run your own, or write the list by hand:
sequentia-cli getfeepriceserver # connected? to which?sequentia-cli setfeepriceserver "http://host:8089/feewhitelist" # connect to a price serversequentia-cli setfeepriceserver "" # disconnect and keep the current listsequentia-cli getfeeexchangerates # the list in forceThe desktop wallet offers the same from a dialog. A list written by hand ends the connection to the price server until you connect again.
What the desktop wallet does
- Send and receive bitcoin and any Sequentia asset, at the same
tb1address. - Pay fees in any accepted asset, shown in that asset’s own units.
- Issue assets and register their names: Issue an asset.
- Stake, delegate and run a pool from the Staking tab: Stake and pools.
- Confidential transfers, when you choose them.
Keep it healthy
| Check | Command |
|---|---|
| Is the chain advancing? | getblockchaininfo (a block is expected about every minute) |
| Is the anchor current and verified? | getanchorstatus |
| What is final? | getposfinality |
| Is the whole testnet healthy? | The status page |
Upgrades that change consensus rules are announced with a block height. Every node must be upgraded before that height, or it forks off. See Status and roadmap.
Other ways to run it
- A custom chain. Any other chain name builds a private network from configuration, with every consensus rule taken from the settings. This is the path for local development and tests.
- Mainnet parameters. They exist in the code with a placeholder genesis, and the node refuses to start on them. They become real only at launch.
Read further
- Tester guide: Sequentia Core
05-operating-sequentia.md: the full operator manualrunbook-windows-node.md