ISuperToken
Last updated
Was this helpful?
Last updated
Was this helpful?
This is the technical reference related to the interface for Super Tokens.
Super Token deployments work in a proxy pattern with the original implementation being comon between all super tokens for each chain. The implementation address for the SuperToken is different for each network and can be found in the SuperTokenFactory at the method getSuperTokenLogic
.
To get the addresses of all the SuperTokenFactory contracts, you can use the Tagomi Explorer, section Protocol.
In order to interact with any contract satistying the ISuperToken
interface, you can use the following ABI:
Initialize the contract
underlyingToken
contract IERC20
underlyingDecimals
uint8
n
string
s
string
Initialize the contract with an admin
underlyingToken
contract IERC20
underlyingDecimals
uint8
n
string
s
string
admin
address
Only the current admin can call this function if admin is address(0), it is implicitly the host address
newAdmin
address
New admin address
Changes the admin for the SuperToken
Returns the admin address for the SuperToken
Returns the name of the token.
Returns the symbol of the token, usually a shorter version of the name.
_Returns the number of decimals used to get its user representation. For example, if decimals
equals 2
, a balance of 505
tokens should be displayed to a user as 5,05
(505 / 10 ** 2
).
Tokens usually opt for a value of 18, imitating the relationship between Ether and Wei. This is the value ERC20 uses, unless setupDecimals is called.
SuperToken always uses 18 decimals.
This information is only used for display purposes: it in no way affects any of the arithmetic of the contract, including IBEP20-balanceOf and IBEP20-transfer.
See IBEP20-totalSupply.
Returns the amount of tokens owned by an account (owner
).
account
address
Moves amount
tokens from the caller's account to recipient
.
recipient
address
amount
uint256
[0]
bool
Returns Success a boolean value indicating whether the operation succeeded.
a BEP20 Transfer event.
Returns the remaining number of tokens that spender
will be allowed to spend on behalf of owner
through transferFrom. This is zero by default.
owner
address
spender
address
This value changes when approve or transferFrom are called.
Sets amount
as the allowance of spender
over the caller's tokens.
spender
address
amount
uint256
[0]
bool
Returns Success a boolean value indicating whether the operation succeeded.
Beware that changing an allowance with this method brings the risk that someone may use both the old and the new allowance by unfortunate transaction ordering. One possible solution to mitigate this race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards
an Approval event.
Moves amount
tokens from sender
to recipient
using the allowance mechanism. amount
is then deducted from the caller's allowance.
sender
address
recipient
address
amount
uint256
[0]
bool
Returns Success a boolean value indicating whether the operation succeeded.
a Transfer event.
_Atomically increases the allowance granted to spender
by the caller.
This is an alternative to approve
that can be used as a mitigation for problems described in IBEP20-approve._
spender
address
addedValue
uint256
an Approval event indicating the updated allowance.
@custom:requirements
`spender` cannot be the zero address.
_Atomically decreases the allowance granted to spender
by the caller.
This is an alternative to approve that can be used as a mitigation for problems described in IBEP20-approve._
spender
address
subtractedValue
uint256
an Approval event indicating the updated allowance.
@custom:requirements
`spender` cannot be the zero address.
`spender` must have allowance for the caller of at least `subtractedValue`.
Returns the smallest part of the token that is not divisible. This means all token operations (creation, movement and destruction) must have amounts that are a multiple of this number.
For super token contracts, this value is always 1
_Moves amount
tokens from the caller's account to recipient
.
recipient
address
amount
uint256
userData
bytes
a Sent event.
@custom:requirements
the caller must have at least `amount` tokens.
`recipient` cannot be the zero address.
if `recipient` is a contract, it must implement the IERC777Recipient interface.
_Destroys amount
tokens from the caller's account, reducing the total supply and transfers the underlying token to the caller's account.
If a send hook is registered for the caller, the corresponding function will be called with userData
and empty operatorData
. See IERC777Sender._
amount
uint256
userData
bytes
a Burned event.
@custom:requirements
the caller must have at least `amount` tokens.
_Returns true if an account is an operator of tokenHolder
. Operators can send and burn tokens on behalf of their owners. All accounts are their own operator.
See operatorSend and operatorBurn._
operator
address
tokenHolder
address
_Make an account an operator of the caller.
See isOperatorFor._
operator
address
an AuthorizedOperator event.
@custom:requirements
`operator` cannot be calling address.
_Revoke an account's operator status for the caller.
See isOperatorFor and defaultOperators._
operator
address
a RevokedOperator event.
@custom:requirements
`operator` cannot be calling address.
_Returns the list of default operators. These accounts are operators for all token holders, even if authorizeOperator was never called on them.
This list is immutable, but individual holders may revoke these via revokeOperator, in which case isOperatorFor will return false._
_Moves amount
tokens from sender
to recipient
. The caller must be an operator of sender
.
If send or receive hooks are registered for sender
and recipient
, the corresponding functions will be called with userData
and operatorData
. See IERC777Sender and IERC777Recipient._
sender
address
recipient
address
amount
uint256
userData
bytes
operatorData
bytes
a Sent event.
@custom:requirements
`sender` cannot be the zero address.
`sender` must have at least `amount` tokens.
the caller must be an operator for `sender`.
`recipient` cannot be the zero address.
if `recipient` is a contract, it must implement the IERC777Recipient interface.
_Destroys amount
tokens from account
, reducing the total supply. The caller must be an operator of account
.
If a send hook is registered for account
, the corresponding function will be called with userData
and operatorData
. See IERC777Sender._
account
address
amount
uint256
userData
bytes
operatorData
bytes
a Burned event.
@custom:requirements
`account` cannot be the zero address.
`account` must have at least `amount` tokens.
the caller must be an operator for `account`.
_Mint new tokens for the account If userData
is not empty, the tokensReceived
hook is invoked according to ERC777 semantics.
@custom:modifiers
onlySelf_
account
address
amount
uint256
userData
bytes
_Burn existing tokens for the account If userData
is not empty, the tokensToSend
hook is invoked according to ERC777 semantics.
@custom:modifiers
onlySelf_
account
address
amount
uint256
userData
bytes
_Transfer amount
tokens from the sender
to recipient
. If spender
isn't the same as sender
, checks if spender
has allowance to spend tokens of sender
.
@custom:modifiers
onlySelf_
sender
address
spender
address
recipient
address
amount
uint256
_Give spender
, amount
allowance to spend the tokens of account
.
@custom:modifiers
onlySelf_
account
address
spender
address
amount
uint256
Transfer all available balance from msg.sender
to recipient
recipient
address
Return the underlying token contract
tokenAddr
address
Underlying token address
Return the underlying token decimals
underlyingDecimals
uint8
Underlying token decimals
Return the underlying token conversion rate
amount
uint256
Number of tokens to be upgraded (in 18 decimals)
underlyingAmount
uint256
The underlying token amount after scaling
adjustedAmount
uint256
The super token amount after scaling
Upgrade ERC20 to SuperToken.
amount
uint256
Number of tokens to be upgraded (in 18 decimals)
It will use `transferFrom` to get tokens. Before calling this function you should `approve` this contract
Upgrade BEP20 to SuperToken and transfer immediately
to
address
The account to receive upgraded tokens
amount
uint256
Number of tokens to be upgraded (in 18 decimals)
userData
bytes
User data for the TokensRecipient callback
It will use `transferFrom` to get tokens. Before calling this function you should `approve` this contract
@custom:warning
there is potential of reentrancy IF the "to" account is a registered ERC777 recipient. @custom:requirements
if `userData` is NOT empty AND `to` is a contract, it MUST be a registered ERC777 recipient otherwise it reverts.
Downgrade SuperToken to ERC20. It will call transfer to send tokens
amount
uint256
Number of tokens to be downgraded
Downgrade SuperToken to BEP20 and transfer immediately
to
address
The account to receive downgraded tokens
amount
uint256
Number of tokens to be downgraded (in 18 decimals)
Perform BEP20 approve by host contract.
account
address
The account owner to be approved.
spender
address
The spender of account owner's funds.
amount
uint256
Number of tokens to be approved.
@custom:modifiers
onlyHost |
account
address
spender
address
addedValue
uint256
account
address
spender
address
subtractedValue
uint256
Perform ERC20 transferFrom by host contract.
account
address
The account to spend sender's funds.
spender
address
The account where the funds is sent from.
recipient
address
The recipient of the funds.
amount
uint256
Number of tokens to be transferred.
@custom:modifiers
onlyHost |
Perform ERC777 send by host contract.
spender
address
The account where the funds is sent from.
recipient
address
The recipient of the funds.
amount
uint256
Number of tokens to be transferred.
userData
bytes
Arbitrary user inputted data
@custom:modifiers
onlyHost |
Upgrade ERC20 to SuperToken by host contract.
account
address
The account to be changed.
amount
uint256
Number of tokens to be upgraded (in 18 decimals)
@custom:modifiers
onlyHost |
Downgrade ERC20 to SuperToken by host contract.
account
address
The account to be changed.
amount
uint256
Number of tokens to be downgraded (in 18 decimals)
@custom:modifiers
onlyHost |
oldAdmin
address
newAdmin
address
Token upgrade event
account
address
Account where tokens are upgraded to
amount
uint256
Amount of tokens upgraded (in 18 decimals)
Token downgrade event
account
address
Account whose tokens are downgraded
amount
uint256
Amount of tokens downgraded
Constant Outflow NFT proxy created event
constantOutflowNFT
contract IConstantOutflowNFT
constant outflow nft address
Constant Inflow NFT proxy created event
constantInflowNFT
contract IConstantInflowNFT
constant inflow nft address
Pool Admin NFT proxy created event
poolAdminNFT
contract IPoolAdminNFT
pool admin nft address
Pool Member NFT proxy created event
poolMemberNFT
contract IPoolMemberNFT
pool member nft address
Parameters
Parameters
Parameters
Note
Parameters
Parameters
Return Values
Emits
Parameters
Parameters
Return Values
Note
Emits
Parameters
Return Values
Emits
Parameters
Emits
Parameters
Emits
Note
If send or receive hooks are registered for the caller and recipient
, the corresponding functions will be called with userData
and empty operatorData
. See and ._
Parameters
Emits
Parameters
Emits
Parameters
Parameters
Emits
Parameters
Emits
Parameters
Emits
Parameters
Emits
Parameters
Parameters
Parameters
Parameters
Parameters
Return Values
Return Values
Parameters
Return Values
Parameters
Note
Parameters
Note
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters
Parameters