https://github.com/xjonathanlei/eosyield

A contract whose owner can temporaily yield control over it until a later time
https://github.com/xjonathanlei/eosyield

blockchain eos immutability smart-contracts

Last synced: about 2 months ago
JSON representation

A contract whose owner can temporaily yield control over it until a later time

• Host: GitHub
• URL: https://github.com/xjonathanlei/eosyield
• Owner: xJonathanLEI
• License: mit
• Created: 2018-08-06T04:21:53.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2022-01-18T21:14:05.000Z (almost 3 years ago)
• Last Synced: 2023-03-04T00:44:11.706Z (almost 2 years ago)
• Topics: blockchain, eos, immutability, smart-contracts
• Language: C++
• Size: 10.7 KB
• Stars: 23
• Watchers: 4
• Forks: 12
• Open Issues: 0
• Metadata Files:
  • Readme: README.MD
  • License: LICENSE

Awesome Lists containing this project

README

        
# EOS Yield Contract

This contract demostrates how an EOS contract can be made immutable in a given period of time, without losing mutability forever. Such a mechanism guarantees immutability when trustlessness is necessary, with code changes possible with prior notice to users.

The intent of this contract is explained in [this reddit post](https://www.reddit.com/r/eos/comments/94zoch/demo_contract_for_temporary_immutability/).

## Powered by EOS Yield

The following dApps feature implementation of the Temporary Immutability pattern proposed by this contract:

- [Final Noob](https://github.com/erikajung/finalnoobcryptogame): A decentralized EOS game.

- [DeltaDex](https://deltadex.io): A fully on-chain decentralized exchange.

## Clone and Compile

To clone the repository and compile the contract into binary:

    $ git clone https://github.com/xJonathanLEI/eosyield.git

    $ cd eosyield

    $ eosiocpp -o eosyield.wast eosyield.cpp

    $ eosiocpp -g eosyield.abi eosyield.cpp

Three files: `eosyield.wast`, `eosyield.wasm` and `eosyield.abi` will be generated after compilation succeeds.

## Contract Setup

To test the contract, first set up a contract account, say `yield`:

    $ cleos system newaccount --buy-ram "1000.0000 SYS" --stake-net "100.0000 SYS" --stake-cpu "100.0000 SYS" eosio yield YOUR_PUBLIC_KEY;

Publish the contract:

    $ cleos set contract yield /path/to/contract/folder;

Give account `owner` permission to `eosio.code` permission so that the contract itself can modify its own permission settings:

    $ cleos set account permission yield owner '{"threshold": 1,"keys": [{"key": "YOUR_PUBLIC_KEY","weight": 1}],"accounts": [{"permission":{"actor":"yield","permission":"eosio.code"},"weight":1}]}' -p yield@owner;

Set the owner to be your account (`jonathan` here):

    $ cleos push action yield setowner '["jonathan"]' -p yield@owner;

To yield control on the contract:

    $ cleos push action yield yieldcontrol '[60]' -p jonathan;

If you check permission now, you would see the contract code would be the sole owner of itself:

    $ cleos get account yield;

Check the yield info from database:

    $ cleos get table yield yield yieldinfo;

To extend the yield period:

    $ cleos push action yield extend '[120]' -p jonathan;

To regain control after the expiration is reached:

    $ cleos push action yield regain '' -p jonathan;

## License

This EOS contract is licensed under the MIT license.