Contract Details

Additional info on contract parameters and use cases

The parameters are used in the IPayload in the contract

E.g.:

const payload: ITransfer = {
  amount: 100 * 10 ** 6,
  receiver: 'receiverAddress',
  kda: 'KLV',
}

const Contract: IContract = {
  type: TransactionType.Transfer,
  payload,
}

Transfer

Transfer assets to another address.

Payload Parameters

Freeze

Freezes a certain amount of a token for staking. This frozen amount will be referred as a "bucket".

Payload Parameters

Unfreeze

Unfreezes a bucket.

Payload Parameters

Delegate

Delegates a bucket to a validator. Buckets can only be delegated to a validator address.

Payload Parameters

Undelegate

Removes the delegation of a bucket.

Payload Parameters

Claim

Claim either staking rewards, delegation rewards or expired marketplace orders.

Payload Parameters

Claim types All claim types and your function and referral param

Withdraw

Retrieves the assets from an unfrozen bucket or assets from KDAPool.

Payload Parameters

Withdraw Type

Create Asset

Creates a new fungible token or a NFT/SFT collection.

Payload Parameters

Staking Structure

Royalties Structure

RoyaltySplitInfo Structure

RoyaltyInfo structure

Role structure

Properties Structure

Attributes structure

Asset Trigger

Updates the properties or trigger functionalities of a fungible token, NFT collection or a single NFT.

The required parameters will depend on the trigger type. Trigger Type and AssetID are required in all of them.

Trigger Types: List with all trigger types values and its required payload

fields. You can see more info about each field here. Any parameter you send beyond the required ones will be ignored.

Payload Parameters

Royalties structure

RoyaltySplitInfo structure

RoyaltyInfo structure

KDAPool

Fixed Ratio calculation:

quotient = (Fixed ratio for KDA) / (Fixed ratio for KLV)

Ex: When Fixed ratio for KLV is 1,and the Fixed ratio for KDA is 2, the cost will be 2 KDA per 1 KLV

Warning: Always use testnet to test the KDAPool ratio before spending real assets.

Role Structure List with all role values

Staking Structure

Deposit

Deposits an asset into a FPR pool or into an auto-swapping fee system.

Payload Parameters

Deposit Type

Config ITO

Sets up an Initial Token Offering for either a token or a NFT collection.

Payload Parameters

Pack structure

WhiteListInfo structure

Status

ITO Trigger

Updates the properties or trigger functionalities of a fungible token, NFT collection or a single NFT.

The required parameters will depend on the trigger type. Trigger Type and AssetID are required in all of them.

Trigger Types List with all trigger types values and its required payload

fields. You can see more info about each field here. Any parameter you send beyond the required ones will be ignored.

Payload Parameters

Obs: Javascript's Date.prototype.getTime() should be divided by 1000 for it to be converted to Unix Time (seconds)

Status

Pack structure

WhiteListInfo structure

Set ITO Prices

DEPRECATED: Updates the ITO prices, useful for ITO's that use an oracle-like pricing system.

This contract is deprecated, please use an ITO Trigger of type SetITOPrices.

Payload Parameters

Pack structure

Create Marketplace

Creates a marketplace

Payload Parameters

Config Marketplace

Changes the parameters of a marketplace

Payload Parameters

Sell

Payload Parameters

price is required on Instant Sell Orders, but optional in Auction Orders. As explained below:

Obs: Javascript's Date.prototype.getTime() should be divided by 1000 for it to be converted to Unix Time (seconds)

Buy

Creates a buy (or bid) order for a given market sell order.

Payload Parameters

Send the 'amount' parameter with the correct precision based on the currency asset

Cancel Market Order

Cancels a sell order

Payload Parameters

Proposal

Creates a proposal to change the chain network parameters.

Payload Parameters

Parameter key

Vote

Votes on an active proposal, the weight of the vote depends on the staked KFI of the sender address (The KFI is not consumed).

Payload Parameters

Create Validator

Creates a validator for an address, controlled by a BLS key.

Payload Parameters

*Object in which the keys are the URI labels and the values are the URIs

Config Validator

Changes the params of a given validator.

Payload Parameters

*Object in which the keys are the URI labels and the values are the URIs

Unjail

Sends an unjail request for the sender validator address.

Payload Parameters

Send Unjail request of sender address, no params required.

Set Account Name

Defines a name for the account.

Payload Parameters

Update Account Permission

Updates the permissions of an account, setting multi-signature permissions with a set signature threshold. Useful for creating a safely shared account.

Payload Parameters

AccPermission structure

AccKey structure

Operations

The operations property defines which operations the account should be able to do.

The value that this property receives is a hexadecimal string, where each bit represents a contract.

Ex:

"01af" is the hexadecimal to 000110101111.

The 1's represent the contracts it should be able to do (following this table)

This account will be able to do contracts of type 0, 1, 2, 3, 5, 7, 8 (Transfer, Create Asset, Create Validator, Config Validator, Unfreeze, Undelegate, Withdraw).

Relevant Link: binary to hex calculator

After getting the hexadecimal string, you need to invert the byte order, for proper processing in the blockchain.

you can use either of the following JS code to do so:

utils.parseAccountPermissionBinaryOperations('000110101111')

utils.reverseHexBytes('01af')

Both return the same "af01" which is the correct value for said operations.