It seems after the hard-fork no changes in parameters were done, maybe because it was not known to the new generation of miners how to do that. Back in 2019, I provided some instructions on how to change block-related limits (see e.g. [Voting proposal] Increasing maximum computational cost for block ).
Let’s use the same trick to have indicative voting on EIP-27 emission soft-fork proposal ( EIP-0027: Emission Soft-Fork by kushti · Pull Request #52 · ergoplatform/eips · GitHub ). So if you support as a miner or a pool EIP-27, please vote also for increasing (non-significantly) computational cost limit per block (from current 7M to 8M). From observing the voting, we will get hashrate support %%.
For that, please put following “voting” section in your configs:
If you mining in a pool then the pool operator would be able to cast your vote if they really wanted to but I’d imagine most reputable mining pools would remain neutral on the re-emissions proposal but rather provide the miners with the correct tools to vote in a convenient manner. To keep things fair a lot of pools have implemented proof-of-vote that will let traditional pool miners cast their vote from the pool directly rather than needing a full node. Voting should remain as trustless as possible.
Your hash rate contributes to the collective hash rate of the pool, which is used to strengthen that vote.
Overly simplified; if one pool votes for “yes” with 3 TH power, and another votes for “no” with 2 TH, the yes vote will win because it has more hash power.
That’s how I understood it at least. Maybe someone can correct me if I’m wrong.
Hi, thanks for your response however I’m running a full node and need the actual setting to change in the config file. I guess my mistake for not being clear
are you aware of what to change in the config file?
I see 4 = 8000000 in this thread however isn’t that just related to increasing the memory?
I don’t see what I need to change in order to vote for EIP-0027
From my understanding adding the following code below to your full node config will essentially vote yes and if you don’t change your config you are essentially saying no to the re-emission proposal.