DePool

This document contains instructions on how to deploy and configure a DePool smart contract, and run a validator node through it.

It is intended for the latest version of the DePool contract. For instructions on the archive versions of DePool refer to the relevant tags in the repository. Note that they are intended for reference only and should not be used on the network anymore.

Note: For RustCup use the DePool from RUSTCUP_DEPOOL_--_DO_NOT_DEPLOY_ON_MAINNET branch. Do not use it on any other network.

For detailed information on DePool specifications, please refer to the relevant document.

Answers to frequently asked questions can be found here.

Note: One node can be assigned to only one DePool contract.

Note: Validator contest winners are strongly recommended not to deploy DePool to the main net without previously testing their setup out on the devnet for a few days. Test tokens for staking on the devnet can be requested from community admins.

Prerequisites

TONOS-CLI of the latest version (0.3.0 or later) installed and configured.

tvm_linker utility.

Resources required to run a node available:

Procedure

To function correctly, the DePool contract requires an active validator node and a set of supporting smart contracts, that have to be deployed and configured alongside it:

The Validator Wallet, which should be a multisignature wallet with at least three custodians and reqConfirms > 1. Can be deployed to the basechain.
The DePool contract itself, deployed to the basechain. DePool contract deploys two proxy smart contracts to the masterchain, which will pass messages from the DePool to the Elector smart contract. Two proxies are required to support two staking rounds running in parallel, one for odd rounds, and one for even rounds.
Optionally, the DePool Helper contract, which is connected to the global Timer contract and ensures regular operation of the DePool. Also deployed to the basechain. Can be replaced with other methods of updating DePool state.

Important: the only contracts requiring masterchain in this setup are the two proxy contracts, which are deployed by DePool. Everything else is designed to function on the basechain, as the contracts are rather complex and consume a lot of gas.

Once all of these contracts are deployed and configured, the DePool is ready to receive stakes.

Follow the steps described below to complete this procedure.

1. Set Up Node and Deploy Validator Wallet

When using DePool you may set up the validator wallet on the basechain, as the DePool itself operates on the basechain and will pass your stakes to the masterchain Elector contract through its proxy contracts.

With that in mind, follow:

For C++ node - this procedure up to step 4.4 (the validator script in step 5 will be different)
For Rust node - this procedure up to step 6

and make sure to set up at least three custodians for your wallet.

Make sure that in the course of the procedure:

For C++ node:

validator wallet address was specified in the ~/ton-keys/$(hostname -s).addr file.
validator wallet keys were saved to the ~/ton-keys/msig.keys.json file.

For Rust node:

validator wallet address was specified in the /ton-node/configs/${VALIDATOR_NAME}.addr file.
validator wallet keys were saved to the /ton-node/configs/keys/msig.keys.json file.

The wallet address will also be needed on the following steps.

As always, also make sure to securely backup all of your seed phrases and/or wallet keys, generated during wallet and node setup. If you lose them, you will not be able to recover access to your funds.

Note: The validator wallet should have a small sum of tokens available at all times to reliably send election requests to DePool. Each election request costs ~ 1 Ton.

2. Prepare DePool and Supporting Smart Contracts

Obtain contract code from the repository.

Note: For RustCup use the DePool from RUSTCUP_DEPOOL_--_DO_NOT_DEPLOY_ON_MAINNET branch. Do not use it on any other network.

The files required for DePool deployment are comprised of three pairs of compiled contract .tvc files and their corresponding ABI files:

DePoolProxy.tvc

DePool.tvc and DePool.abi.json

DePoolHelper.tvc and DePoolHelper.abi.json

3. Generate Deployment Keys

Use TONOS-CLI to generate seed phrases for the contracts you will be deploying:

tonos-cli genphrase

Do not reuse wallet keys, or any other keys you may have used elsewhere already.

Securely backup these seed phrases and keep them secret, as without them, control over the DePool contract will be lost (for example, without its key, the DePool cannot be closed). If you suspect that your keys are compromised, close the DePool and deploy it anew with new keys and a new set of supporting contracts.

Generate key pair files from the seed phrases (this step is intended for the sake of convenience as nothing in the seed phrases indicates for what contract they are intended, and they are easy to mix up).

tonos-cli getkeypair depool.json "seed_phrase_for_depool"
tonos-cli getkeypair helper.json "seed_phrase_for_helper"

4. Calculate Contract Addresses

The smart contracts you will be deploying need to be configured to know the addresses of each other. Thus, first you have to calculate and save the addresses of every contract to be deployed.

4.1. Calculate DePool address

tonos-cli genaddr DePool.tvc DePool.abi.json --setkey depool.json --wc 0

Save the DePool address.

Put it into the following files in in your validator node setup:

~/ton-keys/depool.addr file - for C++ Node
/ton-node/configs/depool.addr - for Rust Node

It will be required for the validator script.

4.2. (Optional) Calculate DePool Helper address

tonos-cli genaddr DePoolHelper.tvc DePoolHelper.abi.json --setkey helper.json --wc 0

Save the DePool Helper address.

5. Send Coins to the Calculated Addresses

Send some coins to all addresses calculated on step 4 to initialize them with the following command:

tonos-cli call <wallet_address> submitTransaction '{"dest":"contract_address","value":*number*,"bounce":"false","allBalance":"false","payload":""}' --abi <MultisigWallet.abi.json> --sign <wallet_seed_or_keyfile>

Where

<wallet_address> - is the address of the wallet, from which you are making the transaction

<contract_address> - address of one of the contracts, calculated on step 4.

"value":*number* - the amount of coins to be transferred (in nanotokens).

"bounce":"false" - bounce flag set to false, to allow a transaction to an account that is not yet initialized.

<MultisigWallet.abi.json> - the ABI file of the contract, from which you are making the transaction (for validator wallets - usually SafeMultisigWallet.abi.json)

<wallet_seed_or_keyfile> - either the seed phrase in double quotes, or the path to the keyfile for the wallet, from which you are making the transaction

allBalance and payload values in this case remain default.

Example:

tonos-cli call 0:2bb4a0e8391e7ea8877f4825064924bd41ce110fce97e939d3323999e1efbb13 submitTransaction '{"dest":"0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace","value":200000000,"bounce":"false","allBalance":"false","payload":""}' --abi ./SafeMultisigWallet.abi.json --sign ./wallet.json

Confirm the transaction, if it is required.

Such a transaction should be repeated for every address calculated on step 4: the DePool contract itself and, optionally, the DePool Helper contract.

The recommended initial amounts are:

21 Tons to the DePool conrtact
5 Tons to the DePool Helper
10 Tons should be left on the validator wallet

For the duration of the DePool existence, balance on all DePool-related contracts should be maintained:

Proxies receive fees for their services automatically, but if they run out of funds for any reason, DePool might miss elections.

Helper, on the other hand, should be topped up regularly, depending on the set timer period. Without funds on the Helper contract, DePool will not be able to function regularly.

The DePool itself receives funds for its operations from validation rewards, but may also, if it stops receiving these rewards, run out of funds.

6. Deploy Contracts

6.1. Deploy DePool contract to the basechain

tonos-cli deploy DePool.tvc '{"minStake":*number*,"validatorAssurance":*number*,"proxyCode":"<ProxyContractCodeInBase64>","validatorWallet":"<validatorWalletAddress>","participantRewardFraction":*number*}' --abi DePool.abi.json --sign depool.json --wc 0

Where

"minStake":*number* – minimum stake (in nanotons) that DePool accepts from participants. It's recommended to set it not less than 10 tokens.

"validatorAssurance":*number* - minimal stake for validator. If validator has stake less than validatorAssurance, DePool won't be taking part in elections.

ProxyContractCodeInBase64 - code of the proxy contract. Can be obtained by calling tvm_linker:

tvm_linker decode --tvc DePoolProxy.tvc

<validatorWalletAddress> – validator wallet address from step 1.

"participantRewardFraction":*number* - percentage of the total DePool reward (in integers, up to 99 inclusive) that goes to Participants. It's recommended to set it at 95% or more.

Important: You will not be able to change all of these parameters, except participantRewardFraction, after the DePool is deployed. They will influence the appeal of your DePool to potential participants:

participantRewardFraction determines what percentage of their total reward all participants will receive (too small, and other DePools might draw them away, too big, and your validator wallet might not receive enough rewards, to support validation and staking); it can be adjusted at any time by the DePool owner, but only upwards - see how below.

validatorAssurance determines how much you take it upon yourself to invest in the DePool and lose in case of any validator node malfunction or misbehavior. If set too small, potential participants might decide you aren't risking enough and avoid your DePool in favor of others.

Example:

tonos-cli deploy DePool.tvc '{"minStake":10000000000,"validatorAssurance":100000000000000,"proxyCode":"te6ccgECIgEABdIAAib/APSkICLAAZL0oOGK7VNYMPShBwEBCvSkIPShAgIDzkAGAwIB1AUEADk7UTQ0//TP9MA0wf6QPhs+Gv4an/4Yfhm+GP4YoAA9PhCyMv/+EPPCz/4Rs8LAPhK+Ev4TF4gywfOzsntVIADTu/CC3SXgE7zRTfjAQaY/pn5mQwQh/////XUcjuDRTfbBKtFN/MBjvwQgCrqVAUNq//CW4ZGfCwGUAOeegZwD9AUaCIAAAAAAAAAAAAAAAAACHtMu6Z4sQ54Wf/CTni2S4/YBvL4HJeARvQIBIBAIAgFuDwkCASAOCgIBIA0LAZj6f40IYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABPhpIe1E0CDXScIBjhnT/9M/0wDTB/pA+Gz4a/hqf/hh+Gb4Y/hiDAG4joDi0wABn4ECANcYIPkBWPhC+RDyqN7TPwGOHvhDIbkgnzAg+COBA+iogggbd0Cgud6S+GPggDTyNNjTHyHBAyKCEP////28sZZbcfAB8AXgAfAB+EdukzDwBd4WALu0t7mSfCC3SXgE72mf6Lg0U32wSrRTfzAY78EIAq6lQFDav/wluGRnwsBlADnnoGcA/QFGgiAAAAAAAAAAAAAAAAAB8+0HGmeLEOeFn/wk54tkuP2AGEl4BG8//DPAAMe23RITPhBbpLwCd7TP9Mf0XBopvtglWim/mAx34IQBV1KgKG1f/hLcMjPhYDKAHPPQM4B+gKNBEAAAAAAAAAAAAAAAAABM+vBdM8WIs8LPyHPCx/4Sc8WyXH7AFuS8Ajef/hngAMe5zeipnwgt0l4BO9pn+mP6Lg0U32wSrRTfzAY78EIAq6lQFDav/wluGRnwsBlADnnoGcA/QFGgiAAAAAAAAAAAAAAAAABO2QLJmeLEWeFn5DnhY/8JOeLZLj9gC3JeARvP/wzwAgEgGxECASAYEgEPuotV8/+EFugTATKOgN74RvJzcfhm0fhJ+EvHBfLgZvAIf/hnFAFG7UTQINdJwgGOGdP/0z/TANMH+kD4bPhr+Gp/+GH4Zvhj+GIVAQaOgOIWAf70BXEhgED0DpPXCweRcOL4anIhgED0Do4kjQhgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAE3/hrcyGAQPQOjiSNCGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATf+GxwAYBA9A7yvdcL//hicPhjFwAMcPhmf/hhAgFqGhkA8bTYWbL8ILdJeATvaZ/9IGj8JPwl44L5cDN8E7eIODRTfbBKtFN/MBjvwQgdzWUAUFq/33lwM7g0U32wSrRTfzAY78EIAq6lQFDav5DkZ8LEZwD9AUaCIAAAAAAAAAAAAAAAAAEdldCSZ4sRZ4Wf5Lj9gC34BD/8M8AApbQlaov8ILdJeATvaPwk/CZjgvlwNHwTt4gQOUEIHc1lAFRan99HERA5QQgdzWUAVFqf0Nq/kHwmZGfChGcA/QFANeegZLh9gBhvGEl4BG8//DPAAgEgHRwAn7rbxCnvhBbpLwCd7R+EuCEDuaygAiwP+OLSTQ0wH6QDAxyM+HIM6NBAAAAAAAAAAAAAAAAArbxCnozxYizxYhzws/yXH7AN5bkvAI3n/4Z4AgEgIR4BCbhxdZGQHwH6+EFukvAJ3tM/0//TH9Mf1w3/ldTR0NP/3yDXS8ABAcAAsJPU0dDe1PpBldTR0PpA39H4SfhLxwXy4Gb4J28QcGim+2CVaKb+YDHfghA7msoAoLV/vvLgZ3BopvtglWim/mAx34IQBV1KgKG1fyHIz4WIzgH6AoBqz0DPg8ggAFLPkTnN0S4ozws/J88L/ybPCx8lzwsfJM8L/yPPFM3JcfsAXwfwCH/4ZwCC3HAi0NMD+kAw+GmpOADcIccAIJwwIdMfIcAAIJJsId7f3CHBAyKCEP////28sZZbcfAB8AXgAfAB+EdukzDwBd4=","validatorWallet":"0:0123012301230123012301230123012301230123012301230123012301230123","participantRewardFraction":95}' --abi DePool.abi.json --sign depool.json --wc 0

Note: For RustCup, make sure to get the proxy code from the contract file in the RUSTCUP_DEPOOL_--_DO_NOT_DEPLOY_ON_MAINNET branch. Do not use it on any other network.

At the time of deployment, the variable m_balanceThreshold is set as current DePool account balance - 5 tokens. DePool will replenish its balance from validation rewards to this value every round it receives rewards.

6.2. (Optional) Deploy DePool Helper contract to the basechain

tonos-cli deploy DePoolHelper.tvc '{"pool":"DePoolAddress"}' --abi DePoolHelper.abi.json --sign helper.json --wc 0

Where

<DePoolAddress> – address of the DePool contract from step 4.1.

Example:

tonos-cli deploy DePoolHelper.tvc '{"pool":"0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace"}' --abi DePoolHelper.abi.json --sign helper.json --wc 0

6.3. Deploy StEverVault strategy

To participate in StEver program need to deploy and add a special contract called StEverStrategy via StEverVaultStrategyFactory. Validator MultiSig wallet should have at least 23 ever.

First of all, need to clone StEver repo. Then in the stever repo folder

npm i

cross-env SEED="{{YOUR_SEED_PHRASE}}" npx locklift run --disable-build --network mainnet -s scripts/validator/1_create_and_add_strategy_to_dePool.ts

Then step by step need to fill the required fields

Example:

√ StEverStrategyFactory address ... 0:4b96a1a988e872ffe8c936dc4150b6373fb39488ff821956f65d2655bd81a096
√ Validator Multi Sig wallet address ... 0:5c1d243557a9c8b4a7f9ed8aa0b287cca08c967b6f474453802e4057de97c074
√ DePool address ... 0:fc351755ed420bc9c57958b381a64688200c8714525bcb76b1e93068604452ba

The result of this script will:

Step 1. Sending create strategy transaction
Step 1 success Transaction successfully sent, tx: 9999999999999999999999999999999999
Step 2. Waiting for strategy address
Step 2 success Strategy successfully created with address 0:581917c5e20abe39667845f8525cbbf6a1fc65b32161dbee96ef9c4b8eb8d921
Step 3. Add strategy to the DePool
Step 3 success Strategy added as allowed participant to the DePool, tx: 99999999999999999999999999
Summary
Strategy with address 0:581917c5e20abe39667845f8525cbbf6a1fc65b32161dbee96ef9c4b8eb8d921 created and added to the DePool

7. Configure DePool State Update method

There are three different methods of setting up regular state updates of the DePool contract available. You have to set up one of them to run regularly. The period for state updates should be chosen based on the duration of the validation cycle on the blockchain. At the very minimum DePool's state update function should be called four times during the validation cycle:

At least twice after the elections begin, so DePool gets ready to receive and forward validator's election request.
Once after the validation begins, to find out if it won elections or not.
Once after unfreeze, to process stakes and rewards and rotate the rounds.

In the current network configuration, 1 and 3 coincide, so DePool's state update should be called be called at least three times during the validation cycle - at least twice twice during elections and once during validation.

For Rust node you can use the provided ticktock script, which sends 5 ticktocks after the elections open.

State update through Multisig Contract

A Multisig wallet can be used instead of Helper to call DePool's ticktock function directly.

tonos-cli depool [--addr <depool_address>] ticktock [-w <msig_address>] [-s <path_to_keys_or_seed_phrase>]

Where

--addr <depool_address> - the address of the DePool

-w <msig_address> - the address of the multisig wallet used to call DePool

-s <path_to_keys_or_seed_phrase> - either the keyfile for the wallet, or the seed phrase in quotes

All these options can be skipped, if they were previously specified in the TONOS-CLI configuration file:

tonos-cli config --addr <address> --wallet <address> --keys <path_to_keys or seed_phrase>

1 token is always attached to this call. Change will be returned.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace ticktock -w 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e -s "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

State update through DePool Helper contract (temporarily unavailable)

If you have previously deployed DePool helper, you can set it up to regularly call the DePool state update ticktock function. To do it, DePool Helper contract needs to be connected to the global Timer contract. Use the following command:

tonos-cli call HelperAddress initTimer '{"timer":"TimerAddress","period":*number*}' --abi DePoolHelper.abi.json --sign helper.json

Where

<HelperAddress> – is the address of the Helper contract from step 4.2

<TimerAddress> - is the address of the global timer contract.

"period":*number* - is the period for regular DePool contract calls via ticktock messages (in seconds). This period should be chosen based on the duration of the validation cycle on the blockchain. At a minimum DePool Helper contract should be set to call the DePool contract once every step of the validation cycle.

Example:

tonos-cli call 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e initTimer '{"timer":"0:3a10ef5d6435e82eb243b41e620f6a7737a70694884aca1c52c99088efb7643d","period":3600}' --abi DePoolHelper.abi.json --sign helper.json

Timer contract and period may be changed at any time with this command.

Timer fees

Timer charges a fee for its services every time the Helper calls it.

The fees (in nanotons) are calculated according to the following formula:

fee = period * timerRate + fwdFee * 8 + epsilon

Where

timerRate = 400000 nanotons per second

fwdFee = 1000000 nanotons

epsilon = 1e9 nanotons

period = the period set in the DePool Helper contract (in seconds).

Thus, the longer the period set in the DePool Helper contract is, the higher a single timer fee will be.

To pay these fees reliably, sufficient positive balance (~100 Tons if the period is set to 1 hour) has to be maintained on the Helper. Without funds on the Helper contract, DePool will not be able to function regularly.

State update through external call of the DePool Helper Contract

DePool Helper can be called to send the ticktock message manually at any time with the following command:

tonos-cli call <HelperAddress> sendTicktock {} --abi DePoolHelper.abi.json --sign helper.json

Where

<HelperAddress> – is the address of the Helper contract from step 4.2.

If needed, it can be set up to run regularly (for example, with cron utility) to supplement or replace the timer.

Example:

@hourly        cd <tonos-cli-dir> && tonos-cli call <HelperAddress> sendTicktock {} --abi DePoolHelper.abi.json --sign helper.json

Where

<tonos-cli-dir> - directory with TONOS-CLI configuration file, DePoolHelper.abi.json file and helper.json keyfile containing DePool Helper keys.

<HelperAddress> – address of the Helper contract from step 4.2.

8. Make Stakes

DePool collects stakes from various participants to be pooled together and forwarded as one stake to the Elector on behalf of its validator node.

Collection is continuous. Stakes can be made at any time, and will be distributed to whichever round is currently in the pooling stage. Every time an election begins on the blockchain, the accumulated pool is locked and (if all conditions are met) staked in this election, and the pooling stage of the next round begins.

Note: This means, that a DePool stake for a specific election needs to be made before the election begins.

To participate in elections, DePool has to accumulate, through stakes belonging to the validator wallet and, optionally, from other wallets, a staking pool, validator's share of which is not less than validatorAssurance (see section 6.1 above).

TONOS-CLI allows to manage several types of stakes.

DePool fees

All staking commands are subject to an additional fee (by default 0.5 tons), that is partially spent to pay for DePool executing the command. The change is then returned to the sender. This value can be adjusted in TONOS-CLI config.

Additionally, when DePool receives the stake and rewards back from elector and processes the funds of participants, it uses the rewards to top up its balance:

first to m_balanceThreshold = DePool's balance at the time of deployment - 5 tons
then it takes retOrReinvFee*(N+1) tokens, where N is the number of participants.retOrReinvFee is set to 0,04 tons in the current version of DePool and can only be changed in contract code. It can be viewed through getDePoolInfo get-method.

These two fees cover DePool's operational expenses and are deducted only from validation rewards. If DePool doesn't receive rewards in a round, it will not be able to top up its balance.

Configure TONOS-CLI for DePool operations

For all commands listed below, the DePool address, the wallet making the stake, the amount of fee to pay for DePool's services and the path to the keyfile/seed phrase may be specified in the TONOS-CLI config file in advance:

tonos-cli config --addr <address> --wallet <address> --keys <path_to_keys or seed_phrase> --depool_fee <depool_fee>

Where

--addr <address> - the address of the DePool

--wallet <address> - the address of the wallet making the stake

<path_to_keys or seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes

--depool_fee <depool_fee> - value in tons, that is additionally attached to the message sent to the DePool to cover its fees. Change is returned to the sender. The default value, used if this option isn't configured, is 0.5 tons. It should be increased only if it proves insufficient and DePool begins to run out of gas on execution.

Example:

tonos-cli config --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --keys "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel" --depool_fee 0.8

In this case all commands allow to omit --addr, --wallet and --sign options.

Deposit stakes

1) Ordinary stake

Ordinary stake is the most basic type of stake. It and the rewards from it belong to the wallet that made it.

It is invested completely in the current pooling round, and can be reinvested every second round (as odd and even rounds are handled by DePool separately). Thus to participate in every DePool round, an ordinary stake should be invested in two consecutive rounds, so it can later be reinvested in odd and even rounds both.

Ordinary stake must exceed DePool minimum stake. Check DePool Info get-method to find out the minimum stake.

Use the following command to make an ordinary stake:

tonos-cli depool [--addr <depool_address>] stake ordinary [--wallet <msig_address>] --value <number> [--sign <key_file or seed_phrase>]

where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet making a stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

<key_file or seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake ordinary --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 100.5 --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

2) Vesting stake

A wallet can make a vesting stake and define a target participant address (beneficiary) who will own this stake, provided the beneficiary has previously indicated the donor as its vesting donor address. This condition prevents unauthorized vestings from blocking the beneficiary from receiving an expected vesting stake from a known address.

To receive a vesting stake beneficiary must:

already have an ordinary stake of any amount in the DePool (it can be made by the participant itself, or transferred from another participant)
set the donor address with the following command:

tonos-cli depool [--addr <depool_address>] donor vesting [--wallet <beneficiary_address>] --donor <donor_address> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<beneficiary_address> - address of the beneficiary wallet .

<donor_address> - address of the donor wallet.

<key_file or seed_phrase> - either the keyfile for the beneficiary wallet, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:3187b4d738d69776948ca8543cb7d250c042d7aad1e0aa244d247531590b9147 donor vesting --wallet 0:255a3ad9dfa8aa4f3481856aafc7d79f47d50205190bd56147138740e9b177f3 --donor 0:279afdbd7b2cbf9e65a5d204635a8630aec2baec60916ffdc9c79a09d2d2893d --sign "deal hazard oak major glory meat robust teach crush plastic point edge"

Not the whole stake is available to the beneficiary at once. Instead it is split into parts and the next part of stake becomes available to the beneficiary (is transformed into beneficiary's ordinary stake) at the end of the round that coincides with the end of the next withdrawal period. Rewards from vesting stake are always added to the beneficiary's ordinary stake. To withdraw these funds, beneficiary should use one of the withdrawal functions.

Please note, that the vesting stake is split into two equal parts by the DePool, to be used in both odd and even rounds, so to ensure DePool can participate in elections with just one vesting stake where validator wallet is beneficiary, the stake should exceed validatorAssurance*2. Similarly, to ensure any vesting stake is accepted, make sure it exceeds minStake *2.

Vesting for validator beneficiaries is subject to additional rules: At the end of every withdrawal period, the part of the vesting stake to be released is divided proportionally into 2 parts - for rounds in this period when DePool successfully completed validation and received a reward (without slashing) and for rounds when DePool missed elections or was slashed. The portion of the stake corresponding to the successful rounds is sent to the validator, while the portion corresponding to the failed rounds is returned to the vesting stake donor. For example, if there were 100 rounds within the withdrawal period, and DePool successfully completed 80 of them, missed elections in 5 more and was slashed in the remaining 15, the validator will receive 80% of the unlocked part of the vesting stake, and the stake donor will get back 20% of it.

Donor uses the following command to make a vesting stake:

tonos-cli depool [--addr <depool_address>] stake vesting [--wallet <msig_address>] --value <number> --total <days> --withdrawal <days> --beneficiary <address> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet making a stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

total <days> - total period, for which the stake is made.

withdrawal <days> - withdrawal period (each time a withdrawal period ends, a portion of the stake is released to the beneficiary).

There are limitations for period settings: withdrawalPeriod should be <= totalPeriod, totalPeriod cannot exceed 18 years or be <=0, totalPeriod should be exactly divisible by withdrawalPeriod.

beneficiary <address> - address of the wallet that will receive rewards from the stake and, in parts over time, the vesting stake itself. Cannot be the same as the wallet making the stake.

<key_file or seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake vesting --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 1000 --total 360 --withdrawal 30 --beneficiary 0:f22e02a1240dd4b5201f8740c38f2baf5afac3cedf8f97f3bd7cbaf23c7261e3 --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Note: Each participant can be the beneficiary of only one vesting stake. Once the current vesting stake expires, another can be made for the participant.

3) Lock stake

A wallet can make a lock stake, in which it locks its funds in DePool for a defined period, but rewards from this stake will be payed to another target participant (beneficiary). As with vesting, the beneficiary has to indicate the donor as its lock donor address before receiving a lock stake. This condition prevents unauthorized lock stakes from blocking the beneficiary from receiving an expected lock stake from a known address.

To receive a lock stake beneficiary must:

already have an ordinary stake of any amount in the DePool (it can be made by the participant itself, or transferred from another participant)
set the donor address with the following command:

tonos-cli depool [--addr <depool_address>] donor lock [--wallet <beneficiary_address>] --donor <donor_address> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<beneficiary_address> - address of the beneficiary wallet .

<donor_address> - address of the donor wallet.

<key_file or seed_phrase> - either the keyfile for the beneficiary wallet, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:3187b4d738d69776948ca8543cb7d250c042d7aad1e0aa244d247531590b9147 donor lock --wallet 0:255a3ad9dfa8aa4f3481856aafc7d79f47d50205190bd56147138740e9b177f3 --donor 0:279afdbd7b2cbf9e65a5d204635a8630aec2baec60916ffdc9c79a09d2d2893d --sign "deal hazard oak major glory meat robust teach crush plastic point edge"

Like vesting stake, lock stake can be configured to be unlocked in parts at the end of each round that coincides with the end of the next withdrawal period. At the end of each period a part of the Lock Stake is returned to the wallet which locked it. The rewards of a lock stake are always added to the ordinary stake of the beneficiary. To withdraw these funds, beneficiary should use one of the withdrawal functions.

Please note that the lock stake is split into two equal parts by the DePool, to be used in both odd and even rounds, so to ensure DePool can participate in elections with just one lock stake where validator wallet is beneficiary, the stake should equal validatorAssurance *2. Similarly, to ensure any vesting stake is accepted, make sure it exceeds minStake *2.

Donor uses the following command to make a lock stake:

tonos-cli depool [--addr <depool_address>] stake lock [--wallet <msig_address>] --value <number> --total <days> --withdrawal <days> --beneficiary <address> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet making a stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

total <days> - total period, for which the stake is made.

withdrawal <days> - withdrawal period (each time a withdrawal period ends, a portion of the stake is returned to the wallet that made the stake).

There are limitations for period settings: withdrawalPeriod should be <= totalPeriod, totalPeriod cannot exceed 18 years or be <=0, totalPeriod should be exactly divisible by withdrawalPeriod.

beneficiary <address> - address of the wallet that will receive rewards from the stake. Cannot be the same as the wallet making the stake.

key_file or seed_phrase - either the keyfile for the wallet making the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake lock --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 1000 --total 360 --withdrawal 30 --beneficiary 0:f22e02a1240dd4b5201f8740c38f2baf5afac3cedf8f97f3bd7cbaf23c7261e3 --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Note: Each participant can be the beneficiary of only one lock stake. Once the current lock stake expires, another can be made for the participant.

Remove stakes

This command removes an ordinary stake from a pooling round (while it has not been staked in the Elector yet):

tonos-cli depool [--addr <depool_address>] stake remove [--wallet <msig_address>] --value <number> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

<key_file or seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake remove --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 100 --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Transfer stakes

The following command assigns an existing ordinary stake or its part to another participant wallet. If the entirety of the stake is transferred, the transferring wallet is removed from the list of participants in the DePool. If the receiving wallet isn't listed among the participants, it will become a participant as the result of the command.

tonos-cli depool [--addr <depool_address>] stake transfer [--wallet <msig_address>] --value <number> --dest <address> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

dest <address> - address of the new owner of the stake.

<key_file or seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake transfer --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 1000 --dest 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Note: Stakes cannot be transferred from or to DePool's validator wallet, and between any wallets during round completion step (RoundStep = Completing = 8).

Withdraw Stakes

1) Withdraw entire stake

The following command allows to withdraw an ordinary stake to the wallet that owns it, as soon as the stake becomes available. Use withdraw on to receive the stake, once it's unlocked. If you then make another stake, and want to keep reinvesting it every round, run the command with withdraw off.

tonos-cli depool [--addr <depool_address>] withdraw on | off [--wallet <msig_address>] [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

<key_file or seed_phrase> - either the keyfile for the wallet that made the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace withdraw on --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

2) Withdraw part of the stake

The following command allows to withdraw part of an ordinary stake to the wallet that owns it, as soon as the stake becomes available. If, as result of this withdrawal, participant's ordinary stake becomes less than minStake, then participant's whole stake is sent to participant.

tonos-cli depool [--addr <depool_address>] stake withdrawPart [--wallet <msig_address>] --value <number> [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

all --value parameters must be defined in tons, like this: --value 10.5, which means the value is 10,5 tons.

<key_file or seed_phrase> - either the keyfile for the wallet that made the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace stake withdrawPart --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --value 1000 --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Reinvest Stakes

Ordinary stake reinvestment is controlled by the DePool reinvest flag. By default this flag is set to yes, and the the participant's available ordinary stake will be reinvested every round, no additional action required. It gets set to no when withdrawing the entire stake. After stake withdrawal it remains set to no. To re-enable ordinary stake reinvesting after withdrawing a stake, run the withdraw command with option off:

tonos-cli depool [--addr <depool_address>] withdraw off [--wallet <msig_address>] [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

<key_file or seed_phrase> - either the keyfile for the wallet that made the stake, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace withdraw off --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Note:

Withdrawing a part of the stake does not affect the reinvest flag.

Lock and vesting stakes are reinvested according to their initial settings for the full duration of the staking period. There is no way to change these settings once lock and vesting stakes are made.

9. Check Donors and Stakes in the DePool

After the stake is made, you can check its status in the DePool with the getParticipantInfo get-method:

tonos-cli run <depool_address> getParticipantInfo '{"addr":"<msig_address>"}' --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

Note: if you are expecting a lock or vesting stake, make sure the donor address is specified in your lockDonor or vestingDonor parameters.

10. Set Up Validator Script

Once the the validator has accumulated a stake sufficient to participate in elections, (at least validatorAssurance), this stake needs to be signed by the node. This should be done through a validator script.

The main function that the validator script should regularly perform is to send signed election requests to the DePool, which will forward the accumulated stake to the Elector contract on the validator's behalf. The Election request should be generated with the proxy address for the current round as the requesting validator wallet.

When participating in elections through a DePool contract, the validator script handles only the creation and sending of the node election request, as all activities regarding stakes and rewards are handled at the level of the DePool.

Note, that the validator wallet should have a small sum of tokens (~20 Tons) available at all times to reliably send election requests to DePool. Each election request costs ~ 1 Ton.

Note: Do not forget to confirm the election request transactions sent out by the script with the necessary amount of validator wallet custodians.

For C++ node

Working examples of such a script can be found here: for the main FreeTON network, and for the devnet.

Important: If you are setting up DePool validator script on top of a C++ node, that was previously functioning under a regular validator script, you should first disable the regular script (validator_msig.sh) and only set up the DePool validator script (validator_depool.sh) for the next elections. Two validator scripts should never run at the same time, as this creates unpredictable behavior.

It is recommended to run the script periodically, for example with cron utility. Example:

@hourly        script --return --quiet --append --command "cd /scripts/ && ./validator_depool.sh 2>&1" /var/ton-work/validator_depool.log

It is possible to configure the script to monitor the DePool status through the available get-methods, such as getParticipantInfo, getRounds, getDePoolInfo, getParticipants (see get-methods section for details) and through view DePool events command.

For Rust Node

For rustnet, the script is set up automatically during node deployment.

Important: If you are switching a rust validator node from direct staking to DePool, make sure to delete the current node build, set the DePool validator variable and rebuild it from scratch.

11. Maintain Positive Balance on DePool and Supplementary Contracts

DePool Balance

Normally the DePool receives sufficient funds for its operations from validation rewards. They go to DePool's own balance, which is completely separate from the staking pool and the funds on it are never staked.

However, a situation where the DePool spends its funds on regular operations, but does not receive enough rewards (for example, fails to participate in the elections or loses them), is possible.

DePool balance can be viewed or through getDePoolBalance get-method in TONOS-CLI (requires DePool.abi.json file):

tonos-cli run <depool_address> getDePoolBalance {} --abi DePool.abi.json

Additionally, DePool emits the TooLowDePoolBalance event when its balance drops too low to perform state update operations (below CRITICAL_THRESHOLD which equals 10 tons).

Replenish the balance to at least 20 tons from any multisignature wallet with the following command:

tonos-cli depool [--addr <depool_address>] replenish --value *number* [--wallet <msig_address>] [--sign <key_file or seed_phrase>]

Where

<depool_address> - address of the DePool contract.

all --value parameters must be defined in tons, like this: --value 150.5, which means the value is 150,5 tons.

<msig_address> - address of the wallet that made the stake.

<key_file or seed_phrase> - either the keyfile for the wallet, or the seed phrase in quotes.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace replenish --value 150 --wallet 0:1b91c010f35b1f5b42a05ad98eb2df80c302c37df69651e1f5ac9c69b7e90d4e --sign "dizzy modify exotic daring gloom rival pipe disagree again film neck fuel"

Note: These funds do not go towards any stake. They are transferred to the DePool contract itself and are spent on its operational expenses.

Proxy Balance

The balance of ~ 2 Tons on the proxies should be maintained for the full duration of DePool existence.

Generally proxies receive fees for their services automatically, but if they run out of funds for any reason, DePool might miss elections.

As the proxies are deployed by the DePool itself, you have to run the getDePoolInfo get-method to find out their addresses:

tonos-cli run <depool_address> getDePoolInfo {} --abi DePool.abi.json

The balance of the proxies can be viewed on the ton.live blockchain explorer by searching the proxy addresses, or through TONOS-CLI commands:

tonos-cli account <proxy0_address>
tonos-cli account <proxy1_address>

If necessary, it can be topped up with a transaction from any multisignature wallet:

tonos-cli call <wallet_address> submitTransaction '{"dest":"<proxy_address>","value":*number*,"bounce":"true","allBalance":"false","payload":""}' --abi <MultisigWallet.abi.json> --sign <wallet_seed_or_keyfile>

Where

<wallet_address> - is the address of the wallet, from which you are making the transaction

<proxy_address> - address of one of the proxies, calculated on step 4.

"value":*number* - the amount of coins to be transferred (in nanotokens).

<MultisigWallet.abi.json> - the ABI file of the contract, from which you are making the transaction (for validator wallets - usually SafeMultisigWallet.abi.json)

<wallet_seed_or_keyfile> - either the seed phrase in double quotes, or the path to the keyfile for the wallet, from which you are making the transaction

Note: If the proxy balance dips too low to operate and it fails to deliver messages between DePool and elector, DePool will emit one of the following events: ProxyHasRejectedTheStake (if proxy cannot pass the stake on to elector) or ProxyHasRejectedRecoverRequest (if proxy cannot retrieve stake from elector). To reestablish operations you need to top up the proxy balance, and then call the DePool ticktock function by any available means. These measures should be taken as soon as possible, however, as DePool risks missing elections if it cannot communicate with elector on time.

Withdrawing excess funds

If proxy accumulates excess funds over time, they can be withdrawn using a transaction from the validator wallet with a specific payload:

tonos-cli call <validator_wallet> submitTransaction '{"dest":"<proxy_address>","value": 500000000,"bounce": true,"allBalance": false, "payload": "te6ccgEBAQEABgAACFBK1Rc="}' --abi <MultisigWallet.abi.json> --sign <seed_phrase_or_key_file>

<validator_wallet> - address of the validator wallet.

<proxy_address> - address of the proxy contract.

<MultisigWallet.abi.json> - validator wallet ABI file (usually SafeMultisigWallet.abi.json).

<seed_phrase_or_key_file> - either the keyfile for the validator wallet, or the seed phrase in quotes.

payload contains the message calling the withdrawExcessTons() function of the proxy contract.

value, bounce, allBalance and payload values should not be modified. Change from the 0.5 tons not spent on the transaction will be returned.

Proxy will send all excess funds to the validator wallet, reserving only its minimal balance of 2 tons for itself.

Example:

tonos-cli call 0:303c1aa8110dc5c543687c6bba699add7a7faf2ed55737f494f78d1c51c6b8d4 submitTransaction '{"dest":"-1:d16999c37c82523d1931011471967ae9e06ee53c1cafcacc8f6d3bee34f15044","value": 500000000,"bounce": true,"allBalance": false, "payload": "te6ccgEBAQEABgAACFBK1Rc="}' --abi SafeMultisigWallet.abi.json --sign "kick jewel fiber because cushion brush elegant fox bus surround pigeon divide"

DePool Helper Balance

The balance of ~ 100 Tons on the helper contract should be maintained for the full duration of DePool existence.

The balance of the helper can be viewed on the ton.live blockchain explorer by searching the helper address, or through TONOS-CLI command:

tonos-cli account <helper_address>

Helper balance should be topped up regularly. Without funds on the Helper contract, DePool will not be able to function regularly.

To top up, send a transaction from any multisignature wallet:

tonos-cli call <wallet_address> submitTransaction '{"dest":"<helper_address>","value":*number*,"bounce":"true","allBalance":"false","payload":""}' --abi <MultisigWallet.abi.json> --sign <wallet_seed_or_keyfile>

Where

<wallet_address> - is the address of the wallet, from which you are making the transaction.

<helper_address> - address of the helper, calculated on step 4.

"value":*number* - the amount of coins to be transferred (in nanotokens).

<MultisigWallet.abi.json> - the ABI file of the contract, from which you are making the transaction (for validator wallets - usually SafeMultisigWallet.abi.json).

<wallet_seed_or_keyfile> - either the seed phrase in double quotes, or the path to the keyfile for the wallet, from which you are making the transaction.

Validator Wallet Balance

Validator wallet will receive a fraction of any DePool round rewards directly, so with a successful DePool setup, it should receive regular income.

In general, the validator wallet should have a small sum of tokens (~20 Tons) available at all times to reliably send election requests to DePool. Each election request costs ~ 1 Ton.

12. Check DePool Status in the Elections

Once everything has been configured properly, stakes made, and election request sent by the validator script, you can monitor the operation of the DePool and its validator node through various channels.

On ton.live

Nodes currently participating in an open election are displayed on ton.live in the Next validators section until election end.

When the elections end, the newly elected set of validators is posted on ton.live in the Next validators section.

When the new validator set becomes active, it is moved to the Current section. At that point you will be able to see new blocks signed by the validator node on its validator page.

To find the pages of your validator and DePool, you can search for the validator wallet or for the DePool address on ton.live. All validator-related pages are linked to each other.

Using DePool Events

TONOS-CLI supports DePool event monitoring.

To print out all events, or, optionally, all events since a specific time use the following command:

tonos-cli depool [--addr <depool_address>] events [--since <utime>]

Where

<depool_address> - address of the DePool contract.

<utime> - unixtime, since which the events are displayed. If -since is omitted, all DePool events are printed.

To wait for a new event use the following command.

tonos-cli depool [--addr <depool_address>] events --wait-one

Where

<depool_address> - address of the DePool contract.

TONOS-CLI waits until new event will be emitted and then prints it to the stdout.

Example:

tonos-cli depool --addr 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace events --wait-one

List of possible events:

DePoolClosed() - event emitted when DePool is closing.
RoundStakeIsAccepted(uint64 queryId, uint32 comment) - event emitted when Elector accepts the stake.
RoundStakeIsRejected(uint64 queryId, uint32 comment) - event emitted when Elector rejects the stake.
ProxyHasRejectedTheStake(uint64 queryId) - event is emitted if stake is returned by proxy because too low balance of proxy contract.
ProxyHasRejectedRecoverRequest(uint64 roundId) - event is emitted if stake cannot be returned from elector because too low balance of proxy contract.
RoundCompleted(TruncatedRound round) - event emitted when the round was completed.
StakeSigningRequested(uint32 electionId, address proxy) - event emitted when round switches from pooling to election indicating that DePool is waiting for signed election request from validator wallet.
TooLowDePoolBalance(uint replenishment) - event emitted when DePool's own balance becomes too low to perform state update operations (below CRITICAL_THRESHOLD which equals 10 tons). replenishment indicates the minimal value required to resume operations. It's recommended to replenish the balance to 20 tons or more if this event occurs.
RewardFractionsChanged(uint8 validator, uint8 participants) - event emitted when contract owner changes reward fractions. validator - validator's reward fraction. participants - participants' reward fraction.
InternalError(uint16 ec) - emitted whenever an internal error occurs. Contains error code.

Events command output example:

event ee4f1e53997f7c5cd3a03511f8ed8e5715ead58e9645b4c99f91b56f0a4bd07b
RoundStakeIsAccepted 1611665778 (2021-01-26 12:56:18.000)
{"queryId":"1611665701","comment":"0"}

event 14ed78bb338cc94b2e1165f71de732d092ff203941e027bfe2b5e20bdc0a90ee
StakeSigningRequested 1611665471 (2021-01-26 12:51:11.000)
{"electionId":"1611666134","proxy":"-1:1ef217ee3f9aa5cd2202919c97e1b61caddcb1a80f450d82990a06b918a75d82"}

event c884939b93dcf846ab43f1bbc36977fabe57bf376fa3638d95b2e7127ed4f0c2
RoundCompleted 1611665471 (2021-01-26 12:51:11.000)
{"round":{"id":"159","supposedElectedAt":"1611664334","unfreeze":"0","stakeHeldFor":"900","vsetHashInElectionPhase":"0xc09caf4efff6cabff6185754d2150bc11d94098f97ea146a617e9d0d90cecc76","step":"8","completionReason":"3","stake":"2525331200749","recoveredStake":"0","unused":"0","isValidatorStakeCompleted":false,"rewards":"0","participantQty":"1","validatorStake":"2525331200749","validatorRemainingStake":"0","handledStakesAndRewards":"0"}}

Using get-methods

DePool contract supports a number of get-methods, which can be used to monitor its status and the status of participants and stakes in the pool.

`getParticipantInfo(address addr)`

Returns information about a specific participant in all investment rounds.

tonos-cli run <depool_address> getParticipantInfo '{"addr":"<msig_address>"}' --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

<msig_address> - address of the wallet that made the stake.

Output example:

Result: {
  "total": "107043197878158",
  "withdrawValue": "0",
  "reinvest": true,
  "reward": "5837197878158",
  "stakes": {
    "160": "104517866677409",
    "161": "2525331200749"
  },
  "vestings": {},
  "locks":  {
    "160": {
      "lastWithdrawalTime": "1604655095",
      "owner": "0:6cde10682ab1f72f267ce4a47a439db6473be65ba87dc846556fbabdba8bfb78",
      "remainingAmount": "100000500000000",
      "withdrawalPeriod": "1728000",
      "withdrawalValue": "100000500000000"
    },
    "161": {
      "lastWithdrawalTime": "1604655095",
      "owner": "0:6cde10682ab1f72f267ce4a47a439db6473be65ba87dc846556fbabdba8bfb78",
      "remainingAmount": "100000500000000",
      "withdrawalPeriod": "1728000",
      "withdrawalValue": "100000500000000"
    },
  "vestingDonor": "0:6cde10682ab1f72f267ce4a47a439db6473be65ba87dc846556fbabdba8bfb78",
  "lockDonor": "0:6cde10682ab1f72f267ce4a47a439db6473be65ba87dc846556fbabdba8bfb78"
}

The participant parameters displayed by the get-method are the following:

total: participant's total stake (in nanotons).

withdrawValue: the value to be withdrawn when the funds become available.

reinvest: whether the ordinary stake of the participant should be continuously reinvested.

reward: The total rewards earned by participant in the current DePool (in nanotons).

stakes: the ordinary stakes in the current active rounds (in nanotons).

locks and vestings: participant's lock and vesting stake, each split into two neighboring rounds. There can be only one of each, split equally into two entries.

The parameters of the lock and vesting stakes are:

lastWithdrawalTime: last time a withdrawal period ended and a part of the stake was unlocked (in unixtime).
owner: the address that made the lock or vesting stake on behalf of the participant.
remainingAmount: the current amount staked in this round (in nanotons).
withdrawalPeriod: the period in seconds, after which the next part of the stake gets unlocked.
withdrawalValue: the value that is unlocked every withdrawal period (in nanotons).

lockDonor and vestingDonor are the addresses set by the participant to be their lock and vesting donors, respectively.

`getDePoolInfo()`

Returns DePool configuration parameters and constants (supplementary contract addresses, minimal stake settings and fees for various actions).

tonos-cli run <depool_address> getDePoolInfo {} --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

Output example:

Result: {
  "poolClosed": false,
  "minStake": "10000000000",
  "validatorAssurance": "100000000000000",
  "participantRewardFraction": "50",
  "validatorRewardFraction": "50",
  "balanceThreshold": "15858929993",
  "validatorWallet": "0:303c1aa8110dc5c543687c6bba699add7a7faf2ed55737f494f78d1c51c6b8d4",
  "proxies": [
    "-1:1ef217ee3f9aa5cd2202919c97e1b61caddcb1a80f450d82990a06b918a75d82",
    "-1:d16999c37c82523d1931011471967ae9e06ee53c1cafcacc8f6d3bee34f15044"
  ],
  "stakeFee": "500000000",
  "retOrReinvFee": "40000000",
  "proxyFee": "90000000"
}

The round parameters displayed by the get-method are the following:

poolClosed: whether DePool was closed.

minStake: the minimal stake the DePool accepts from participants (in nanotons). Set during deployment.

validatorAssurance: required validator stake (in nanotons). Also set during deployment.

participantRewardFraction: percentage of the reward that goes to all participants. Also set during deployment.

validatorRewardFraction: the fraction of the total reward that goes directly to validator. Equals 100% - participantRewardFraction.

validatorWallet: the address of the validator wallet. Also set during deployment.

proxies: the two proxies on the masterchain that DePool uses to communicate with elector. They are deployed by the DePool itself.

stakeFee: fee for staking operations (in nanotons).

retOrReinvFee: the fee deducted from every participant's stake and rewards during reward distribution at the end of the round (in nanotons).

proxyFee: the fee that proxies take for any messages passed through them (in nanotons).

`getRounds()`

Returns information about all rounds (step, total stake, stakeholder count, round id).

tonos-cli run <depool_address> getRounds {} --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

Output example:

Result: {
  "rounds": {
    "159": {
      "id": "159",
      "supposedElectedAt": "1611664334",
      "unfreeze": "0",
      "stakeHeldFor": "900",
      "vsetHashInElectionPhase": "0xc09caf4efff6cabff6185754d2150bc11d94098f97ea146a617e9d0d90cecc76",
      "step": "9",
      "completionReason": "3",
      "stake": "2525331200749",
      "recoveredStake": "0",
      "unused": "0",
      "isValidatorStakeCompleted": true,
      "rewards": "0",
      "participantQty": "0",
      "validatorStake": "2525331200749",
      "validatorRemainingStake": "0",
      "handledStakesAndRewards": "2525331200749"
    },
    "161": {
      "id": "161",
      "supposedElectedAt": "0",
      "unfreeze": "4294967295",
      "stakeHeldFor": "0",
      "vsetHashInElectionPhase": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "step": "1",
      "completionReason": "0",
      "stake": "2525331200749",
      "recoveredStake": "0",
      "unused": "0",
      "isValidatorStakeCompleted": false,
      "rewards": "0",
      "participantQty": "1",
      "validatorStake": "0",
      "validatorRemainingStake": "0",
      "handledStakesAndRewards": "0"
    },
    "160": {
      "id": "160",
      "supposedElectedAt": "1611666134",
      "unfreeze": "4294967295",
      "stakeHeldFor": "900",
      "vsetHashInElectionPhase": "0x7965b01da2b778404bd5b9e6dc5a5f6d1e4ce15a78284ebec78ed86a8852d5f9",
      "step": "6",
      "completionReason": "0",
      "stake": "205352016359392",
      "recoveredStake": "0",
      "unused": "0",
      "isValidatorStakeCompleted": false,
      "rewards": "0",
      "participantQty": "2",
      "validatorStake": "104517866677409",
      "validatorRemainingStake": "0",
      "handledStakesAndRewards": "0"
    },
    "162": {
      "id": "162",
      "supposedElectedAt": "0",
      "unfreeze": "4294967295",
      "stakeHeldFor": "0",
      "vsetHashInElectionPhase": "0x0000000000000000000000000000000000000000000000000000000000000000",
      "step": "0",
      "completionReason": "0",
      "stake": "0",
      "recoveredStake": "0",
      "unused": "0",
      "isValidatorStakeCompleted": false,
      "rewards": "0",
      "participantQty": "0",
      "validatorStake": "0",
      "validatorRemainingStake": "0",
      "handledStakesAndRewards": "0"
    }
  }

id: round ID. It's also displayed above each round. At DePool deployment, the first four rounds are created: 0, 1, 2 and 3. Whenever one round completes and is removed from the DePool, a new one is created, its ID incremented by 1: when 0 is removed, 4 is created, etc.

supposedElectedAt: the time the validator is scheduled to start validating, if elected (in unixtime). This value remains 0, until validator elections start and DePool enters waitingValidatorRequest step of the round. Then it is set to the time the election winners will start validating.

unfreeze: the time the stake will be unfrozen by elector (in unixtime). This value remains 4294967295 until validation ends.

stakeHeldFor: the period in seconds for which stake will remain frozen in elector after validation. It's set by the global configuration parameter p15 when validation completes.

vsetHashInElectionPhase: this is a system variable that holds the hash of validation set (global config parameter 34) when round was in election phase. Is set during election.

step: step the round is currently at. The possible steps are:

0 - PrePooling: step reserved for receiving half of vesting/lock stake from participants. Nothing else happens when round is in this step.
1 - Pooling: DePool receives stakes from participants. Half of vesting/lock stakes are invested into the round in the pooling step, the other into the round in the PrePooling step. This way, the other half of these stakes is always invested into the very next round.
2 - WaitingValidatorRequest: waiting for election request from validator. The elections have begun, it's no longer possible to invest stakes into this round. Once election request from validator is received, DePool can participate in elections.
3 - WaitingIfStakeAccepted: stake has been sent to elector. Waiting for answer from elector.
4 - WaitingValidationStart: elector has accepted round stake. Validator is candidate. Waiting for validation to start, to know if validator won elections.
5 - WaitingIfValidatorWinElections: DePool has tried to recover stake in validation period to know if validator won elections. Waiting for elector answer.
6 - WaitingUnfreeze: DePool received elector answer and waits for the end of unfreeze period. If at this step CompletionReason!=0, then validator did not win and DePool is waiting to return/reinvest funds after the next round. Else validator won elections.
7 - WaitingReward: Unfreeze period has been ended. Request to recover stake has been sent to elector. Waiting for answer from elector.
8 - Completing: Returning or reinvesting participant stakes because round is completed.
9 - Completed: All stakes of the round have been returned or reinvested. At the next round rotation the round will be deleted from the DePool.

completionReason: the code for the reason the round was completed. Remains "0", until round actually is completed. The possible reasons are:

0 - Round is not completed yet.
1 - Pool was closed by owner.
2 - The round was one of the first two rounds after deployment: 0 or 1. These first rounds are empty and are used only to launch the round rotation mechanism. They complete with this code without performing any additional actions.
3 - Validator stake is less than validatorAssurance.
4 - Stake is rejected by elector for some reason.
5 - Round is completed successfully. DePool won elections, its node performed validation and it received the reward from elector.
6 - DePool has participated in elections but lost the elections.
7 - Validator is blamed during investigation phase.
8 - Validator sent no request during election phase.

stake: the total stake in the current round, that is sent to elector (in nanotons).

recoveredStake: the total stake returned by elector (in nanotons).

unused: if the stake was cut off by the elector (this can happen if there is a significant number of election candidates with much smaller stakes), this value equals the amount cut off (in nanotons). This amount is not lost to participants - it simply isn't staked in this round and the rewards for the round will be proportionally smaller. If DePool did not receive a ticktock call during the validation period, this value will remain 0, even if some funds were cut off.

isValidatorStakeCompleted: indicates whether validator's stake has been processed during Completing round step. Whenever participants receive rewards, validator's stake should be processed first, as any losses the total stake sustains due to poor node rerformance are first deducted from validator's share of the pool.

rewards: the total rewards that are distributed among all participants in the current round (in nanotons). Is calculated when the stake is returned from elector.

participantQty: the quantity of participants in the round.

validatorStake: this value equals the final validator stake in the current round. It is set at the and of the Pooling step.

validatorRemainingStake: this value is used if validator got punished by elector for poor node performance and part of the DePool stake is lost. Then this value equals the remaining validator stake, if any (in nanotons).

handledStakesAndRewards: the total quantity of stakes and rewards that were processed by the DePool during Completing step (in nanotons).

`getParticipants()`

Returns list of all participants.

tonos-cli run <depool_address> getParticipants {} --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

Output example:

Result: {
  "participants": [
    "0:9fa316f41fe4e991865b80006c9d9916b2637146e9a6f346eeb25c035206c5b7",
    "0:a08bb1f6c64939bcbd3d950a44d88820f0102c550bfaf49f70f2d012eeec333a",
    "-1:68384476fce1d2649484912c08541a8037c36b606aca0f8cc04c043640e8dd98"
  ]
}

`getDePoolBalance()`

Returns DePool's own balance in nanotokens (without stakes).

tonos-cli run <depool_address> getDePoolBalance {} --abi DePool.abi.json

Where

<depool_address> - address of the DePool contract.

13. (Optional) Adjust validator and participant reward fraction

If you want to make your DePool more attractive to potential participants, you may increase the fraction of the total reward they receive.

DePool deployment keys are required for this action. Use the following command:

tonos-cli call <depool_address> setValidatorRewardFraction '{"fraction":<fraction_value>}' --abi DePool.abi.json --sign <depool_keyfile_or_seed_phrase>

Where

<depool_address> - address of the DePool.

<fraction_value> - new value of Validators reward fraction, which should be less than previous and should not be equal to 0.

<depool_keyfile_or_seed_phrase> - DePool deployment keyfile or its corresponding seed phrase.

Example:

tonos-cli call 0:53acdc8033cc0794125038a810d4b64e24e72add52ee866b82ade42d12cd9f02 setValidatorRewardFraction '{"fraction":29}' --abi DePool.abi.json --sign depool.keys.json

Current validator reward fraction value can be viewed with the getDePoolInfo get-method.

14. (Optional) Close DePool

The deployer of the DePool can close the DePool at any time. DePool deployment keys are required for this action:

tonos-cli call <depool_address> terminator {} --abi DePool.abi.json --sign <depool_keyfile_or_seed_phrase>

Where

<depool_address> - address of the DePool.

<depool_keyfile_or_seed_phrase> - DePool deployment keyfile or its corresponding seed phrase.

Example:

tonos-cli call 0:37fbcb6e3279cbf5f783d61c213ed20fee16e0b1b94a48372d20a2596b700ace terminator {} --abi DePool.abi.json --sign depool.json

When a DePool is closed, all the stakes invested in it are returned to their owners, as soon as they become available. dePoolClosed event is emitted. The closed DePool cannot be reactivated again.

To return all stakes currently locked in rounds to their owners, make sure DePool's state update function is called once the current and the next validation cycles complete.

Rewards Distribution

Every time DePool receives rewards for validation, DePool replenishes it's own balance and the rest is distributed according to the following rules:

validatorRewardFraction% of the reward, regardless of the validator’s share in the pool, goes directly to the validator wallet. This is the reward for maintaining the node and is intended to be used on operational expenses.
participantRewardFraction% of the reward is distributed among all participants (including the validator) proportionally to their share of the staking pool. By default these rewards are added to the ordinary stakes of all participants and reinvested with it. To withdraw this stake or any part of it to the participant wallet, use one of the withdrawal functions.

Troubleshooting

1. Wrong contract version

Issue: Wrong/outdated version of any contracts involved in DePool operations may cause various issues and hard-to-diagnose behavior.

To check contract versions, search for the addresses of DePool, DePool Helper and both proxies on ton.live and review Code hash (may be hidden under More details). Click on the value to copy it to clipboard.

It should match the following values:

DePool:

14e20e304f53e6da152eb95fffc993dbd28245a775d847eed043f7c78a503885

Proxies:

c05938cde3cee21141caacc9e88d3b8f2a4a4bc3968cb3d455d83cd0498d4375

DePool Helper:

f990434c02c2b532087782a2d615292c7c241ece4a9af33f8d090c535296401d

If only the Helper contract has wrong Code hash, deploying and configuring only a new Helper is enough.

If DePool or proxies have wrong Code hash, all contracts have to be redeployed, and the node reconfigured to work with the new DePool.

Note: For RustCup, contract code hash is different.

Initially the following contracts were used:

891d1afd26d99ee4f9def21fbd4bccffe25143e79729669573c7d792a646f4e9 for DePool

d938d7c19af7ba65342e6fc2f4c6827b7e16ce378722ce134bb461f9d62f6c76 for proxy

After the August 5 update the code hashes are as follows:

cef9fe9fed144e25e24aa671da1118244dfb2d1e316e9961522cd9b015bbba59 for DePool

b633f0b5bc420abd8cb74b03eb0960df2a91c6c123d5cb18ed7283bb26e491bd for proxy

2. DePool isn't emitting events

Issue: DePool seems to be set up correctly, but is not emitting expected events, for example stakeSigningRequested.

This can be caused by issues with the state update method.

Possible solutions:

Change the global timer and/or the timer call period (termporarily unavailable):
```
tonos-cli call <HelperAddress> initTimer '{"timer":"TimerAddress","period":*number*}' --abi DePoolHelper.abi.json --sign helper.json
```
Where

<HelperAddress> – is the address of the Helper contract from step 4.2

<TimerAddress> - is the address of the global timer contract.

"period":*number* - is the period for regular DePool contract calls via ticktock messages (in seconds).
Set up external ticktock function call through TONOS-CLI:
```
tonos-cli call <HelperAddress> sendTicktock {} --abi DePoolHelper.abi.json --sign helper.json
```
Where

<HelperAddress> – is the address of the Helper contract from step 4.2.

If necessary, run it regularly, e.g. with cron:
```
@hourly        cd <tonos-cli-dir> && tonos-cli call <HelperAddress> sendTicktock {} --abi DePoolHelper.abi.json --sign helper.json
```
Where

<tonos-cli-dir> - directory with TONOS-CLI configuration file, DePoolHelper.abi.json file and helper.json keyfile containing DePool Helper keys.

<HelperAddress> – is the address of the Helper contract from step 4.2.
Call DePool's ticktock function through multisig instead of Helper:
```
tonos-cli depool [--addr <depool_address>] ticktock [-w <msig_address>] [-s <path_to_keys_or_seed_phrase>]
```
Where

--addr <depool_address> - the address of the DePool

-w <msig_address> - the address of the multisig wallet used to call DePool

-s <path_to_keys_or_seed_phrase> - either the keyfile for the wallet making the stake, or the seed phrase in quotes

All these options can be skipped, if they were previously specified in the TONOS-CLI configuration file.

1 token is always attached to this call, change is returned to sender.

3. Validator script and election request issues

Issue: DePool isn't receiving election request from validator script and/or isn't passing it on to the Elector.

This can be caused by DePool setup errors, low balance on some of the contracts involved, or issues with the script or node setup.

Possible solutions and diagnostic methods:

If the DePool fails to accumulate a suitable stake, or malfunctions in any other manner, the election request will not pass through to the Elector. Always make sure that the full DePool setup procedure described in this document is completed, and that DePool contract itself operates correctly, i.e. enters waiting request step and emits stakeSigningRequested event, when encountering problems with election participation.
Check balance of all contracts and top up if any of them have run out of funds (see section 11 for details).

For C++ Node

Check that the DePool address is specified in the in the ~/ton-keys/depool.addr file in your validator node files and matches your current DePool address.
Check that the validator wallet address is specified in the ~/ton-keys/$(hostname -s).addr file according to the node setup procedure.
Check that the validator wallet keys are saved to the ~/ton-keys/msig.keys.json file according to the node setup procedure.
Check validator script output log (/var/ton-work/validator_depool.log file if script is set up according to the given example). They may help identify the cause of the issue.

Rerun the command to send election request manually. It can be found in the validator script output log (/var/ton-work/validator_depool.log file if set up according to the given example) and used as is.

Example:

tonos-cli call -1:fd05bd9be4e2d3ee7789d1fbc5811e0bd85cf1d14968028fd46a9e1c7b1066cc submitTransaction '{"dest":"0:10fdf438953430949ca33147f792b9fd9002e7979e50c94547c771c51fb643b9","value":"1000000000","bounce":true,"allBalance":false,"payload":"te6cckEBAgEAmQABqE5zdEsAAAAAXz7BoZOzdxrAyZXWwptpyrV5ZV1EkLrRdSsfm0KFiFpOuB4XXz7FVAADAACIUt3MiEtCLfPfKEWoVz2sTA9yS/Sl8N88ZkQ8CB1c3QEAgNnX/KhAEKVKe/MO4ArCIMLXM1kgYu34Ujp9dSq2lkSo8vfj0s+yySs6Ac2ufavtXO4DLZ1afugAVwUjvKvI3Agoizgf"}' --abi /validation/configs/SafeMultisigWallet.abi.json --sign /keys/msig.keys.json

Run validator script with verbose logs to get more diagnostic information:
```
bash -x ./validator_depool.sh
```

For Rust Node

Check that the DePool address is specified in the in the /ton-node/configs/depool.addr file in your validator node files and matches your current DePool address.
Check that the validator wallet address is specified in the /ton-node/configs/${VALIDATOR_NAME}.addr file
Check that the validator wallet keys are saved to the /ton-node/configs/keys/msig.keys.json file
Refer to this document for Rust node troubleshooting.

4. DePool function terminates with error in TONOS-CLI

In TONOS-CLI output it looks like this:

message: Contract execution was terminated with error
message_processing_state: null
data: {
  "account_address": "0:3187b4d738d69776948ca8543cb7d250c042d7aad1e0aa244d247531590b9147",
  "config_server": "net.ton.dev",
  "exit_code": 140,
  "function_name": "constructor",
  "original_error": {
    "code": 1006,
    "core_version": "0.27.0",
    "data": {
      "block_id": "20c8932bc6c7baa90c2d099595b432607355b79d95293061dc6feec392675975",
      "block_time": "Thu, 19 Nov 2020 13:24:37 +0300 (1605781477)",
      "expiration_time": "Thu, 19 Nov 2020 13:24:35 +0300 (1605781475)",
      "message_id": "eae70ebcf84fd9ebcffc544908ca637d9a46a8bdffdab24db6749d003608969e",
      "sending_time": "Thu, 19 Nov 2020 13:23:35 +0300 (1605781415)"
    },
    "message": "Message was not delivered within the specified timeout",
    "message_processing_state": null,
    "source": "node"
  },

The error code is indicated in the "exit_code" line.

Possible error codes and their meanings:

101 - message sender is not owner (message public key is wrong). Please check your key file or seed phrase.

108 - function cannot be called by external message.

113 - message sender is not validator wallet.

114 - DePool is closed.

116 - participant with such address does not exist.

129 - incorrectly defined stake parameters during DePool deployment (minStake < 1 token or minStake > validatorAssurance). Please check your parameters in deploy message.

130 - DePool deployment isn't signed with public key. Please check your key file or seed phrase.

133 - validator address passed to constructor is not of add_std type. Please check your parameters in deploy message.

138 - Incorrect participant reward fraction during DePool deployment (participantRewardFraction ≤ 0 or ≥ 100). Please check your parameters in deploy message.

141 - incorrectly specified proxy code during DePool deployment. Please check your parameters in deploy message.

142 - DePool is being deployed to the wrong shardchain (workchain id ≠ 0). Please check your parameters in deploy message.

143 - new validator reward fraction is greater than old.

144 - new validator reward fraction is zero.

146 - insufficient DePool balance.

147 - validator wallet address is zero.

149 - incorrectly specified minimal stake and validator assurance.

Incorrect DePool function call by another contract:

107 - message sender is not proxy contract.

120 - message sender is not DePool (this is not a self call).

125 - invalid confirmation from elector (invalid round step).

126 - invalid confirmation from elector (invalid query ID).

127 - invalid confirmation from elector (sender is not elector).

148 - message sender is not one of the proxies.

Name		Name	Last commit message	Last commit date
Latest commit History 7 Commits
.gitignore		.gitignore
ConfigParamsBase.abi.json		ConfigParamsBase.abi.json
ConfigParamsBase.base64		ConfigParamsBase.base64
ConfigParamsBase.code		ConfigParamsBase.code
ConfigParamsBase.tsol		ConfigParamsBase.tsol
ConfigParamsBase.tvc		ConfigParamsBase.tvc
DePool.abi.json		DePool.abi.json
DePool.base64		DePool.base64
DePool.code		DePool.code
DePool.tsol		DePool.tsol
DePool.tvc		DePool.tvc
DePoolHelper.abi.json		DePoolHelper.abi.json
DePoolHelper.base64		DePoolHelper.base64
DePoolHelper.code		DePoolHelper.code
DePoolHelper.tsol		DePoolHelper.tsol
DePoolHelper.tvc		DePoolHelper.tvc
DePoolLib.tsol		DePoolLib.tsol
DePoolProxy.abi.json		DePoolProxy.abi.json
DePoolProxy.base64		DePoolProxy.base64
DePoolProxy.code		DePoolProxy.code
DePoolProxy.tsol		DePoolProxy.tsol
DePoolProxy.tvc		DePoolProxy.tvc
DePoolRounds.abi.json		DePoolRounds.abi.json
DePoolRounds.base64		DePoolRounds.base64
DePoolRounds.code		DePoolRounds.code
DePoolRounds.tsol		DePoolRounds.tsol
DePoolRounds.tvc		DePoolRounds.tvc
IDePool.tsol		IDePool.tsol
IDePoolInfoGetter.abi.json		IDePoolInfoGetter.abi.json
IDePoolInfoGetter.base64		IDePoolInfoGetter.base64
IDePoolInfoGetter.code		IDePoolInfoGetter.code
IDePoolInfoGetter.tsol		IDePoolInfoGetter.tsol
IDePoolInfoGetter.tvc		IDePoolInfoGetter.tvc
IElector.tsol		IElector.tsol
IParticipant.abi.json		IParticipant.abi.json
IParticipant.base64		IParticipant.base64
IParticipant.code		IParticipant.code
IParticipant.tsol		IParticipant.tsol
IParticipant.tvc		IParticipant.tvc
IProxy.tsol		IProxy.tsol
Participant.abi.json		Participant.abi.json
Participant.base64		Participant.base64
Participant.code		Participant.code
Participant.tsol		Participant.tsol
Participant.tvc		Participant.tvc
ParticipantBase.abi.json		ParticipantBase.abi.json
ParticipantBase.base64		ParticipantBase.base64
ParticipantBase.code		ParticipantBase.code
ParticipantBase.tsol		ParticipantBase.tsol
ParticipantBase.tvc		ParticipantBase.tvc
ProxyBase.abi.json		ProxyBase.abi.json
ProxyBase.base64		ProxyBase.base64
ProxyBase.code		ProxyBase.code
ProxyBase.tsol		ProxyBase.tsol
ProxyBase.tvc		ProxyBase.tvc
README.md		README.md
ValidatorBase.tsol		ValidatorBase.tsol

broxus/stEver-depool-contracts

Folders and files

Latest commit

History

Repository files navigation

DePool

Table of Contents

Prerequisites

Procedure

1. Set Up Node and Deploy Validator Wallet

2. Prepare DePool and Supporting Smart Contracts

3. Generate Deployment Keys

4. Calculate Contract Addresses

4.1. Calculate DePool address

4.2. (Optional) Calculate DePool Helper address

5. Send Coins to the Calculated Addresses

6. Deploy Contracts

6.1. Deploy DePool contract to the basechain

6.2. (Optional) Deploy DePool Helper contract to the basechain

6.3. Deploy StEverVault strategy

7. Configure DePool State Update method

State update through Multisig Contract

State update through DePool Helper contract (temporarily unavailable)

State update through external call of the DePool Helper Contract

8. Make Stakes

DePool fees

Configure TONOS-CLI for DePool operations

Deposit stakes

1) Ordinary stake

2) Vesting stake

3) Lock stake

Remove stakes

Transfer stakes

Withdraw Stakes

1) Withdraw entire stake

2) Withdraw part of the stake

Reinvest Stakes

9. Check Donors and Stakes in the DePool

10. Set Up Validator Script

For C++ node

For Rust Node

11. Maintain Positive Balance on DePool and Supplementary Contracts

DePool Balance

Proxy Balance

Withdrawing excess funds

DePool Helper Balance

Validator Wallet Balance

12. Check DePool Status in the Elections

On ton.live

Using DePool Events

Using get-methods

getParticipantInfo(address addr)

getDePoolInfo()

getRounds()

getParticipants()

getDePoolBalance()

13. (Optional) Adjust validator and participant reward fraction

14. (Optional) Close DePool

Rewards Distribution

Troubleshooting

1. Wrong contract version

2. DePool isn't emitting events

3. Validator script and election request issues

For C++ Node

For Rust Node

4. DePool function terminates with error in TONOS-CLI

About

Topics

Resources

Stars

Watchers

Forks

Releases

`getParticipantInfo(address addr)`

`getDePoolInfo()`

`getRounds()`

`getParticipants()`

`getDePoolBalance()`