Initialize EOSIO Side

Now we are going to start the interval that runs all of the bridge logic.
Locate the init action on your atomictokenpeg contract
sister_address and sister_msig_address will be the atomictokenpeg bridge contract (not the account) on the EVM side.
The token_contract will be your token contract name on the EOSIO side.
10000 is 1.0000 TKN for the min_transfer.
We do not allow the contract to issue tokens because we are assuming the original token contract exists on the Kylin side.
Login with blok's cleos option with your tokenpeg EOSIO account
Select the active permission level.
By clicking the Submit Transaction the cleos command will be autopopulated for you
If you use the command below, be sure to update the settings like account, addresses, token contract, etc.
1
# cleos -u https://kylin.eosn.io push transaction '{
2
  "delay_sec": 0,
3
  "max_cpu_usage_ms": 0,
4
  "actions": [
5
    {
6
      "account": "maticnftbrdg",
7
      "name": "init",
8
      "data": {
9
        "sister_address": "0x95f50751605101ca1A49fC27d79AB19F997D3e82",
10
        "sister_msig_address": "0x95f50751605101ca1A49fC27d79AB19F997D3e82",
11
        "sister_chain_name": "mumbai",
12
        "this_chain_name": "kylin",
13
        "processing_enabled": true,
14
        "token_contract": "bridgeassets",
15
        "transfers_enabled": true,
16
        "can_issue": false
17
      },
18
      "authorization": [
19
        {
20
          "actor": "maticnftbrdg",
21
          "permission": "active"
22
        }
23
      ]
24
    }
25
  ]
26
}'
Copied!
Now we're ready to test the bridge!

Verify Source Code

Test bridge

Last modified 9mo ago

Copy link