Commons Stack
Search…
Welcome to Commons Stack
Token Bonding Curve for Commons Fund
Conviction Voting Module
Request funding app
Contributors Guide
How To Donate to Commons Stack - Iteration 0
Transparent log of burn events
Research
Commons Research
Digital Commons
Library
Powered By GitBook
Transparent log of burn events

In accordance with the need for graduated sanctions in any healthy commons[^1], The Commons Stack may destroy some of the non-monetary token, CSTK, which represents reputation in the Trusted Seed. We laid out these conditions:

On the off chance that the Commons Stack Association loses faith in a member of the Trusted Seed, (specifically, if we suspect that their motivation is to extract value from these systems rather than to nurture them,) then graduated sanctions may be applied to the member in question, the most severe of which would be the burning of that person’s CSTK tokens. If it becomes necessary for us to take punitive action against a CSTK holder, the sanction(s) will be carried out with maximum transparency and community consultation.

But in March, we found a different reason to burn CSTK: an accounting error caused a doubling of one person's tokens. This called into question how we can maintain integrity in these scenarios. The result is this burn log. While it's not necessary to initiate a community process over an accounting error, we will document it here for transparency. In the event of future token burns (those warranting more community engagement or not), they will also be logged here.

BURN EVENTS

Date
Reason for Burn
Etherscan Link
02 March 2020
Accounting error, 706 tokens were sent twice
31 March 2020
Member's address compromised,
​reissued here​
15 June 2020
Contract wallet can't interact with CSTK tokens
15 June 2020
Accounting error, 302 tokens were sent twice
13 September 2020
Address Change Request, replacement tokens sent vote 17
24 September 2020
Accounting error
12 October 2020
Address change request
12 October 2020
Member lost access to keys
12 October 2020
Address change request
12 October 2020
Member's address compromised
12 December 2020
20 Members requested to change their addresses
​See our DAO votes #31-50​
29 January 2021
CSTK minted for DApp development testing
11 February 2021
Accounting error
25 February 2021
Accounting error
25 February 2021
3 Members terminated their membership
​See our DAO votes #78-80​
25 February 2021
8 Members requested to change their addresses
11 March 2021
Address change request
11 March 2021
After a live test of the DApp with a new address, CSTK requiered being moved to the correct member's address
24 April 2021
4 Members requested to change their addresses
9 May 2021
3 Members requested to change their addresses
25 May 2021
1 member terminated their membership
27 May 2021
CSTK minted for DApp development testing
27 May 2021
Address change requests
​See link A​ and B​
27 May 2021
Errors prompted by bridge failure
​See link A​ and B​
27 May 2021
THE BURN: An unique event where CSTK from non activated members was burned
​List of 155 burns​
28 May 2021
CSTK minted for DApp development testing
​See link A​ and B​
01 June 2021
Griff's CSTK Ratio Adjustment Burn
09 June 2021
Accounting Error
10 June 2021
Address change request
16 June 2021
Membership termination
​See link A​ and B​
13 July 2021
Membership terminations
​See link A​, B​, C​, D​, E​, and F​
30 July 2021
Accounting Error
03 August 2021
Address change requests
​See link A​ and B​
10 August 2021
Address change request
11 August 2021
Accounting Error
11 August 2021
Address change request
17 August 2021
Address change request
20 October 2021
Address change request
​
​
​

[^1]: http://www.makecommoningwork.fed.wiki/view/graduated-sanctions-according-to-ostrom​

Previous
How To Donate to Commons Stack - Iteration 0
Next - Research
Commons Research
Last modified 6d ago
Copy link
Contents
In accordance with the need for graduated sanctions in any healthy commons[^1], The Commons Stack may destroy some of the non-monetary token, CSTK, which represents reputation in the Trusted Seed. We laid out these conditions:
But in March, we found a different reason to burn CSTK: an accounting error caused a doubling of one person's tokens. This called into question how we can maintain integrity in these scenarios. The result is this burn log. While it's not necessary to initiate a community process over an accounting error, we will document it here for transparency. In the event of future token burns (those warranting more community engagement or not), they will also be logged here.
BURN EVENTS
[^1]: http://www.makecommoningwork.fed.wiki/view/graduated-sanctions-according-to-ostrom