#
Smart Contract configuration
The behaviour of DeBets Smart Contract depends on a few configuration settings whose value is decided by DeBets and might change in the future.
The following table lists the configuration settings and their meaning:
| setting | current value | read method | description |
|---|---|---|---|
| counter-close-timeout | one week | getCounterCloseTimeout | when one party requests to close a deposit this is the amount of time available for the other party to submit the closing information (see Closing of deposits) |
| minimum-deposit-duration | one week | getMinSessionDuration | this setting guarantees a minimum duration for player deposits even when they are in loss (see Closing of deposits) |
| fee | %1 | getFee | the fee applied by DeBets each time a loging deposit gets closed (see Smart Contract Fee) |
You can obtain the current value in the Smart Contract for each configuration setting at anytime. To do this, click on the contract address at the bottom of this page and then in the block explorer invoke the corresponding read method
In addition to the settings above the Smart Contract uses two more settings whose value depends on the cryptocurrency being used: the minimum-deposit-amount
and the minimum-balance.
The minimum-deposit-amount corresponds to the smallest amount that can be deposited when a player creates a new deposit. The following
table shows the value currently set in the Smart Contract for each cryptocurrency:
The minimum-balance corresponds to the value of the player balance in a deposit under which you are allowed to close a losing deposit even if the minimum deposit duration has not elapsed (see Closing of deposits).
You can obtain the current value in the Smart Contract for minimum-deposit-amount by calling the getMinDepositAmount read method and for
minimum-balance by calling getMinBalance read method in the block explorer (to open the block explorer page for DeBets Smart Contract use the links at the bottom of this page). Both these methods take as argument the address of the token contract which can be taken from the table below. When the cryptocurrency is the native coin of the blockchain instead of the token contract address you have to use the zero address as the argument.