Implementing and interacting with a Stacks node and related software.
In order to efficiently and reliably query the Stacks blockchain state, running a follower node allows for direct access to the same data as hosted APIs with the added benefit of decentralized control.
The Stacks Node API provides both a self-contained Docker image and manual installation instructions for running a Stacks 2.0 blockchain and API instance.
The main elements of the API tech stack include:
- Stacks Blockchain API
- Stacks Blockchain Node
- Bitcoin Node
The Syvita Guild also created the repository below, which contains a quick start script that sets up each component based on their cloned versions using Docker.
The Stacks Explorer provides a web interface to interact with Stacks blockchain data, including accounts, transactions, contracts, and more.
Some examples include:
Stacking is the act of locking up STX for a set number of reward cycles and receiving a portion of the BTC spent by Stacks miners.
We call it "stacking" instead of "staking" because the protocol provides rewards of the base currency instead of the same currency.
A few high-level notes about the protocol:
- A STX holder must broadcast a signed message before the reward cycle begins that:
- Locks the associated Stacks tokens for a protocol-specified lockup period (reward cycles are 2,100 Stacks blocks in length, maximum of 12)
- Specifies the Bitcoin address to receive the funds
- Votes on a Stacks chain tip
- The required minimum for a reward slot is dynamic and can increase last minute. It only increases in steps of 10k STX
- It is possible that a reward slot receives 0 BTC because Stacks miners did not send any BTC when it was the slot's turn
- The more reward slots an address occupies, the closer the payouts will be to the average payout
- When the selected reward cycles are complete, the address must sit out for one cycle (a "cooldown period")
The PoX smart contract is the main tool and provides the functions to stack STX.