Learn all about Blockdaemon NEAR Staking API.
The NEAR Staking API offers a comprehensive staking solution that eliminates the need for running NEAR nodes. You simply need to sign the transactions, adding minimal dependencies to your technology stack.
Our advanced bookkeeping and transaction lifecycle tracking enable your organization's various sub-teams to avoid conflicts when dealing with ongoing deactivation and withdrawal operations.
Supported Networks
The Blockdaemon Staking API supports the following NEAR networks:
- Mainnet
- Testnet
User Journey
In this section, we present a typical user journey when interacting with the NEAR Staking API:
- Staking
- Deactivating
- Withdrawal
1. Staking
Staking funds with the Blockdaemon staking pool is achieved through the Post Stake Intent endpoint. This endpoint returns an unsigned transaction that needs signing and broadcasting to the network by the account responsible for the delegated funds.
2. Deactivating your Stake
Before withdrawing staked tokens, they must undergo deactivation. The Post Deactivation Intent endpoint returns an unsigned transaction. Once signed and broadcast, it triggers the deactivation process. The process completes within 2 or 3 NEAR epochs (equivalent to 24-48 hours).
3. Withdrawing Funds
Upon the full deactivation of the stake, an unsigned withdrawal transaction can be generated using the Post Withdrawal Intent endpoint.