SIP: Use PoX for fuelling Bitcoin development #66
Conversation
| | 30 | 3,899 | 101 | 54 | 1.3635 | | ||
| | 31 | 3,673 | 327 | 46 | 3.7605 | | ||
|
|
||
| Assuming that the data from stacking.club is correctly collected, over the last 31 cycles, looking exclusively at "vacant PoX slots", an approximate total of 146 BTC were burnt. |
There was a problem hiding this comment.
Wow, that's huge! Arguably, burning BTC is in and of itself useful because it makes all BTC holders slightly richer ;)
That would be cool even. At the Lab we have an idea on how we could potentially solve the "write back to Bitcoin problem". That might open the door to having a DAO on Stacks that manages the Bitcoin sent to vacant slots. A decentralised dev fund where all STX holders can vote, how much fun would that be? |
|
Great idea, Ludo! |
|
Is there a way to structure the mechanism so that a cartel of Stacks miners can't just take control of it to re-distribute BTC back to themselves? That would permit the cartel to discount-mine during this time. |
|
Edited the title because this SIP does not yet have an assigned number. |
jcnelson
changed the title
Assuming the totality of the 4,000 slots can never be fully reserved, can we use this quantity of forever vacant slots for doing something good, that would be beneficial for the Stacks Blockchain, while staying neutral, from a Stacker / Miner / PoX point of view?
I'd like to use this PR to generate discussions around the idea of using what seems to be a "waste" in the PoX implementation. I acknowledge that the document in its current form is not conforming to what would be expected for an actual SIP, but this should be enough to kickstart conversations.