EOS Token with burning and signup (for making the token RAM cheap)
Branch: master
Clone or download
Latest commit f55a1db Aug 8, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitignore
LICENSE Update LICENSE Jul 3, 2018
README.md Fixed spelling error. Aug 8, 2018
poorman.token-burn-rc.md Add ricardian, burn, transferfree, issuefree Aug 6, 2018
poorman.token-signup-rc.md Add ricardian, burn, transferfree, issuefree Aug 6, 2018
poorman.token-transfer-rc.md Add ricardian, burn, transferfree, issuefree Aug 6, 2018
poorman.token.abi Add ricardian, burn, transferfree, issuefree Aug 6, 2018
poorman.token.cpp Add ricardian, burn, transferfree, issuefree Aug 6, 2018
poorman.token.hpp Add ricardian, burn, transferfree, issuefree Aug 6, 2018

README.md

poorman.token

EOS Token Contract with "Burning" and "Signup" built in (for making the token RAM cheap)

This token uses the standard eosio.token contract with two modifications.

The poorman.token test is available on the mainnet

Everyone feel free to signup for the "Free airdrop test" of the poormantoken

You can go this at https://eostoolkit.io/airgrab

To signup for an airdrop:

cleos push action poormantoken signup '{"owner":"iwanttokens1","quantity":"0.0000 POOR"}' -p iwanttokens1@active

The signup function allows an account to create a balance entry using their own personal ram.

The signup restricts the quantity to 0 however you could configure this in the contract code to allow a "signup bonus".

You would have to add some controls to prevent double signups though, so 0 quantity signup is safest.

To burn tokens run the command:

cleos push action poormantoken burn '{"from":"tokensowner1","quantity":"1.0000 POOR","memo":"Lets remove POOR supply!"}' -p tokensowner1@active

The burn function burns the token from the "from account" and also reduces the supply.

The burn function makes sure you can't burn more tokens than supply.

The burn function has been modified to allow you to burn your zero balance if you don't want to wait for the airdrop.

Guarantee you don't pay ram

Two additional commands have been added:

  1. issuefree
  2. transferfree

These commands work the same as issue and transfer, however they fail if the destination does not have a table row already.

The purpose of this is to prevent you accidentally paying RAM for accounts that unregister from the airgrab (via burn) after you've taken a snapshot.