To create a TC poll the initiator will need to own (or have delegated to them) a minimum of 0.5M LSU-equivalent XRD. (around $600 at today’s price)
Creating a poll in the RFP system will require the initiator to own (or have delegated to them) a minimum of 2M XRD ($2400 at today’s price)
Both of these complicate things immensely if you’re going the snapshot route. I would propose:
- Everyone can create a TC.
- Member(s) of the RAC can elevate a TC to an RFP.
You might think that this will create an enormous amount of spam TCs. I don’t think that’s an issue any more than spam RFCs. Only problem that I might see is a TC goes unnoticed, passes, and now the RAC needs to elevate it to a TC. My solution for that would be that the RAC can demand one extra revote if they deem the TC unsufficiently promoted. If after the revote, it passes and the RAC still refuse to elevate the TC to an RFP, they are legally bound to follow the “no-confidence” process.
Delegating this TC → RFP elevation duty to the RAC also reduces another problem: manipulating voting power through LSU borrowing. When someone knows they can promote a TC to an RFP on demand, and voting power is measured at the time of RFP creation, they can easily manipulate their voting power by borrowing LSUs only for when the vote starts. If the RAC can trigger the promotion at any time, this will be a lot more difficult.