Overview

The upgrade1.1 proposal upgrade system contract to meetone-1.1 to enable consensus protocol.

This proposal makes one change to the system:

merge eosio.contract 1.7.0 to meetone-1.0.

Review proposal

cleos -u https://fullnode.meet.one multisig review meetone.m upgrade1.1

Proposal Status

cleos -u https://fullnode.meet.one get table eosio.msig meetone.m approvals2

Approve proposal

cleos -u https://fullnode.meet.one multisig approve meetone.m upgrade1.1 '{"actor":"meetone.m","permission":"active"}' -p meetone.m

Compare code changes

Build system contract

Use eosio.cdt 1.6.2 and eosio 1.8.x to build eosio.contracts meetone-1.1 smart contract.

git clone git@github.com:meet-one/eosio.contracts.git

cd eosio.contracts/

git checkout meetone-1.1

./build.sh

Upgrade eosio.system contracts

Generate the unsigned transaction which upgrade the system contract:

cd build/contracts

shasum -a 256 eosio.system/eosio.system.wasm

cleos set contract eosio eosio.system -p eosio -s -j -d > upgrade1.1.json

Update expiration to a time that sufficiently far in the future to give enough time to collect all the necessary signatures, set ref_block_num and ref_block_prefix to 0, you will get a transaction like this:

{
  "expiration": "2019-08-31T21:00:00",
  "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": "setcode",
      "authorization": [{
          "actor": "eosio",
          "permission": "active"
        }
      ],
      "data": "......",
    },{
      "account": "eosio",
      "name": "setabi",
      "authorization": [{
          "actor": "eosio",
          "permission": "active"
        }
      ],
      "data": "......"
    }
  ],
  "transaction_extensions": [],
  "signatures": [],
  "context_free_data": []
}