Deploy eosio.assert on EOS Mainnet

Documentation of eosio.assert contract deployment.

You can find more details of eosio.assert here:

https://github.com/EOSIO/eosio.assert

Prerequisites

1. Build eosio.assert smart contract

Use eosio.cdt 1.6.1 to build eosio.assert smart contract, the build is in contracts/eosio.assert folder.

checksums:

openssl dgst -sha256 contracts/eosio.assert.wasm
SHA256(contracts/eosio.assert.wasm)= 2f1e6ca484eeb88d4c0102a90279dc320edf58e3853784101760530be77f60a2

openssl dgst -sha256 contracts/eosio.assert.abi
SHA256(contracts/eosio.assert.abi)= 92807134f93622ab1ffaf16ac1688658688394155f5838f61b648f28bd01769b

2. Prepare chain id, name and logo

You can find the logo of EOS Mainnet under public folder, the checksum is:

openssl dgst -sha256 public/EOS-Mainnet-logo-500x500.png
SHA256(public/EOS-Mainnet-logo-500x500.png)= 4f9a83541efaed8b78b9070f8066bce152651bc0cfc56f325dbca0a6dcd22561

Note: Recommended logo format is PNG and the size should less than 50000 bytes(due to a limit of EOS Authenticator App). There's a SVG version under public also in case of any future usage.

the chain id of EOS Mainnet is aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906, you can find it via api nodes, such as https://api.eoslaomao.com/v1/chain/get_info

STEP 1/3: Create account eosio.assert

Prepare create account multisig transaction and propose

create eosio.assert account :

cleos -u https://api.eoslaomao.com push action eosio newaccount '{"creator":"eosio","name":"eosio.assert","owner":{"threshold":1,"keys":[],"accounts":[{"permission":{"actor":"eosio","permission":"active"},"weight":1}],"waits":[]},"active":{"threshold":1,"keys":[],"accounts":[{"permission":{"actor":"eosio","permission":"active"},"weight":1}],"waits":[]}}' -p eosio -s -j -d > create_assert.json

delegate bandwidth to eosio.assert:

cleos -u https://api.eoslaomao.com system delegatebw eosio eosio.assert "1 EOS" "1 EOS" -p eosio -s -j -d >> create_assert.json

buyram for eosio.assert(at least 321kb ram needed, 40 EOS will get you around 350kb on EOS Mainnet):

cleos -u https://api.eoslaomao.com system buyram eosio eosio.assert "40 EOS" -p eosio -s -j -d >> create_assert.json

Merge actions in file create_assert.json, and change expire time in create_assert.json into future date, e.g. 10 days later, and set ref_block_num and ref_block_prefix to 0.

You will get a transaction like this:

{
  "expiration": "2019-06-15T11:36:47",
  "ref_block_num": 0,
  "ref_block_prefix": 0,
  "max_net_usage_words": 0,
  "max_cpu_usage_ms": 0,
  "delay_sec": 0,
  "context_free_actions": [],
  "actions": [{
      "account": "eosio",
      "name": "newaccount",
      "authorization": [{
          "actor": "eosio",
          "permission": "active"
        }
      ],
      "data": "0000000000ea305590afc2d800ea30550100000000010000000000ea30550000000080ab26a70100000100000000010000000000ea305500000000a8ed3232010000"
    },{
      "account": "eosio",
      "name": "delegatebw",
      "authorization": [{
          "actor": "eosio",
          "permission": "active"
        }
      ],
      "data": "0000000000ea305590afc2d800ea3055a08601000000000004454f5300000000a08601000000000004454f530000000000"
    },{
      "account": "eosio",
      "name": "buyram",
      "authorization": [{
          "actor": "eosio",
          "permission": "active"
        }
      ],
      "data": "0000000000ea305590afc2d800ea3055a08601000000000004454f5300000000"
    }
  ],
  "transaction_extensions": [],
  "signatures": [],
  "context_free_data": []
}

We have proposed this transaction on EOS Mainnet : https://www.eosx.io/tools/msig/proposal?proposer=eoslaomaocom&name=createassert And it has been approved by more than 15 Block Producers and executed successfully.

The actual transaction data used in EOS Mainnet proposal is create_assert.json.

STEP 2/3: Deploy eosio.assert contract

Note: before deployment, make sure eosio.assert has enough CPU/NET and RAM resource.

cleos -u https://api.eoslaomao.com set contract eosio.assert contracts/eosio.assert/ -p eosio.assert -s -j -d > deploy_assert.json

Update expiration to a future time, set ref_block_num and ref_block_prefix to 0, and propose it.

We have proposed this transaction on EOS Mainnet : https://www.eosx.io/tools/msig/proposal?proposer=eoslaomaocom&name=deployassert We have included top 35 Block Producers on EOS Mainnet in this proposal, please review&verify.

The actual transaction data used in EOS Mainnet proposal is deploy_assert.json.

cleos -u https://api.eoslaomao.com multisig review eoslaomaocom deployassert

STEP 3/3: Setup EOS Mainnet chain info

The last step, we need to call setchain action in eosio.assert contracts to register EOS Mainnet chain info.

Here is the payload:

{
      "chain_id": "aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906",
      "chain_name": "EOS Mainnet",
      "icon": "4f9a83541efaed8b78b9070f8066bce152651bc0cfc56f325dbca0a6dcd22561",
}

cleos -u https://api.eoslaomao.com push action eosio.assert setchain '{"chain_id": "aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906","chain_name": "EOS Mainnet","icon": "4f9a83541efaed8b78b9070f8066bce152651bc0cfc56f325dbca0a6dcd22561"}' -p eosio -s -j -d > setup_assert.json

Update setup_assert.json, set expiration to a future time, set ref_block_num and ref_block_prefix to 0, and propose it.

We have proposed this transaction on EOS Mainnet : https://www.eosx.io/tools/msig/proposal?proposer=eoslaomaocom&name=setupassert We have included top 35 Block Producers on EOS Mainnet in this proposal, please review&verify. We have also included Crypto Lions in this proposal considering their experiences of deploying and testing eosio.assert on Jungle Testnet.

The actual transaction data used in EOS Mainnet proposal is setup_assert.json.

EOSLaoMao/Deploy-EOSIO-Assert

ErrorLooks like something went wrong!

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages