Proof of Burn tokens is a new functionality which can be used on Slimcoin with an extension of the PeerAssets protocol (originally developed by the Peercoin project).
A proof of Burn token tracks all burn transactions. Everybody who participated in Slimcoin's Proof-of-Burn process can claim tokens proportionally to the burnt coins, in a completely decentralized way. The proportion is determined by a so-called multiplier, specific for each token. For example, if the multiplier is 1000, for each burnt coin you can claim 1000 tokens.
See the PoB Token Concept for more information.
All basic functionality is explained in the PoB token manual.
How to participate in tests
You need a computer with Python 3.6+ to participate in the tests and a Slimcoin client. The software was tested only with Linux. It's currently a command line tool.
Installation is explained here.
There are two Github repositorys which you'll have to clone:
IMPORTANT: You have to clone the version from the slimcoin-project repos. The originals do not support PoB tokens!
In both cases, clone the master branch, which is the default branch (so simply clone the repository without caring about branches). Then change to the base directory of the downloaded code and install the tools with pip (you need Python 3.6+ and pip):
The Slimcoin testnet client must be running to use pacli. If it's the first time you sync ask for a node to connect to at Discord.
After installation, don't forget to initialize each deck you want to use:
pacli deck init $DECKID
An example DECKID is fb93cce7aceb9f7fda228bc0c0c2eca8c56c09c1d846a04bd6a59cae2a895974. This is a standard PoB token without block height limites. DECKIDs are transaction ids (32 bytes/64 hex characters).
What can you test?
- You can burn coins on testnet (with the standard Slimcoin commands or the pacli pobtoken burn_coins command and claim your tokens.
- You can create your own PoB token with the deck_spawn command. You can create a standard token, where all burn transactions lead to the right to claim tokens, but also a limited token, where you can set a block height limit (e.g. from block 150000 to 180000), and only burns inside this range are accepted.
- You can try to game the protocol, for example claiming tokens without having burnt coins, or claim more tokens than you're entitled to, or claim tokens several times.
- You can also test the Pacli Extended Tools (link contains manual with example commands), an extension which allows to store more complex data than the standard config file, for example assigning labels to decks (tokens) and addresses, and to perform re-org tests using checkpoints of recent blocks. It's a good idea to assign a label to the deck you are testing, so you don't need to enter the long DECKID again all the time.
Report bugs and issues
If you think you found a bug or have an issue, simply respond to this thread describing the issue, and pasting errors you get inside a code block (e.g. limited by backticks).
Announcements
If there's an update testers have to apply, for example when a bug was fixed, I'll edit this post to announce it.
