Junkie Jeff 4th July Hard Fork Information

On July 4, 2021, there will be a network upgrade (“hard fork”) with Wownero “Junkie Jeff” v0.10 release. The release will likely end large scale pool mining. Wownero will aim to be solo-mining only. There is a problem with pool centralization, especially concentrated in China. The two top pools make up over 70% of the network hash.

We have to do something drastic to ensure a more decentralized and secure network, the status quo is unsustainable. Therefore, we will introduce consensus code that checks miner signatures for each newly minted block. Miners will need to sign block header data with private spend key and amend the resulting signature to a new block header field before doing a Proof of Work hash. Each new nonce attempted must be hashed and signed by the miner with their private key. Idea was originally proposed last year by tevador/SChernykh. You can find the implemented code here.

Difficulty will be reset to 2018 levels (100 million) and the difficulty algorithm will be changed from LWMA back to Monero’s default difficulty algorithm. The current difficulty has been driven up by large pools, a reset to lower levels would help solo-miners find blocks after the fork. The lower level will be fixed for 720 blocks to readjust the difficulty window. LWMA was originally implemented to counter NiceHash attacks and gaming the algorithm by large miners “coin jumping” pools. Since we are going to become solo-mining only, a long and smooth difficulty adjustment would be more preferable than the more aggressive adjustments that come with LWMA. Besides, Monero’s difficulty code seems more battle tested than LWMA.

Solo mining will not be easy. Miners have become accustomed to monitoring difficulty levels and prices on a minute by minute, hour by hour basis, and getting regular “dust” payouts from pools. With solo mining, miners have to play the “long game”. The risks are higher (some miners could mine for days, weeks, months, and get nothings), but the rewards are higher… miners could get lucky and win the full block reward (without having to pay pool fees or share the reward with other miners). Solo mining is like a lottery. Everyday there are 288 blocks that will be randomly awarded to miners. On average, a miner with a Ryzen 3700X CPU could expect to win a reward within 30-40 days (with the lower difficulty after the reset… this is only a rough estimate since it depends purely on luck, there is also the possibility a miner will never get a block).

Someone has proposed changing the block time from 5 minutes to 2 minutes per block in order to increase the number of blocks per day (2 minutes would be increase blocks per day to 720 blocks, which is the same as Monero). More blocks means more chances for solo miners to win a reward. However, I not sure if this would be a good idea. Decreasing the block time would mean the blockchain size would grow faster and we would need to adjust the emission rate either by lowering the per block reward and extending the emission beyond the target 50 years or maintaining the same reward amount but shortening the emission period to less than 50 years. This would be a major change and would need community input to reach a rough consensus if anything should be done about this or left the same. Please express your opinion about this proposal below.

The random coinbase unlock time will be dropped and fixed to 1 day (288 blocks) unlock time.

The fork will also include Bulletproofs+, a new range proof that will make transactions smaller and improve verification performance. You can read more about it here. Many upstream updates and bug fixes are included in the update.

For a step by step guide on how to solo mine with Wownero, check out: How to Solo Mine

Full disclosure: This is all very experimental and we have no idea if this will actually work. If shit is broken, we can later fork pools back in or consider other alternatives like P2Pool mining, merge mined derivative “hash coin”. We are nimble… float like a butterfly, sting like a bee!

8 Likes

rip megapools. we hardly knew ye (because you just joined, pamped the difficulty, and left)

#JeSuisJeff

1 Like

So c3pool will be forced to delist WOW ? People get build CPU-Rig and increase the prize of them ? I’m ok for the decentralization but this will encourage anymore theses dudes miners to have the biggest d*ck or car. What’s your opinion ?

Anyway, moi aussi #JeSuisJeff

:clap:

sir, WOW is delisting c3pool

1 Like

After this change, will it still be possible to mine with several PCs by pointing xmrig at a single node I control, or will each and every PC I intend to mine with need its own node and copy of the blockchain?

You would have to run wownerod full node on each computer. You can use same miner’s address for all nodes.

I think XMRIG proxy will support having one node and linking multiple computers together, but their code needs to be updated.

1 Like

I support all of the proposed changes. I know it will be disruptive to miners used to pool mining, but I think it would be a good test to shake things up and remove that centralization, even as just an experiment. I am planning on solo mining to support the network and try to find blocks.

I think we should leave block times and emissions alone for now and revisit on another release; this one has got a lot going on already.

7 Likes

If get_block_template is made to spit out the private key, XMRig (connecting to daemon or to xmrig-proxy) could be made to work.

pool kill is exciting :smiley:

not sure i understand about emission change for shorter curve, think having longer curve makes wow attractive for those learning crypto now that realize most everything else is all mined

4 Likes

Yeah, I am not totally sold on changing the emission/block time stuff, partly because I barley understand how it works. I think we are going to leave it as it is. If anyone feels compelled to push for a change, they are free to make a PR and/or campaign for the change in a future release.

I wanted to host a community pool… i almost bought a VPS for that… but you made this.
So i will never make a 0% fee pool ;-;

Also, I think that making solo-miners only will kill a lot of small miners who get less than 4 KH/s.

2 Likes

This is exciting! I’m looking forward to seeing how things change after the 4th.

Also, everything that @lza_menace said was exactly what I was thinking when reading the post.

Happy to be a soldier on Pool Independence Day.

Viva La Wow!

Pardon my newbness. But if all pool mining will end after the 4th doesn’t this mean that people mining with lower power machines like myself are essentially pushed out of minning? I’ve enjoyed mining WOW on herominers for about a month with my old Optiplexes but it seems if solo mining is the only option my hardware doesn’t stand a chance against dedicated mining rigs running the latest Ryzen processors.

2 Likes

Well the difficulty right after fork is set to 100 million. Right now difficulty is 50.000.000.000 , so about 500 times more profit right after the fork. What happens after is interesting to see, I mean for sure some miners will drop because of the solo mining aspect. This also gives opportunity for those who want to take the risk.

This will also pump the number of wow nodes, a nice side effect. I’m fan of this disruptive change, really interesting to see what network hashrate eventually will do. I will take my chances and be patient to mine some solo blocks :smiley:

1 Like

Some members of the Monero community state that this fork would not successfully mitigate pools because:

  • There’s no risk in sharing the key

  • A pool can simply add the tx private key (the new header signing key), to each stratum job

  • Pool nodes can hardcode the private key (e.g., as 1)

  • You need the wallets private spend key, not the tx private key for the proposal to work

I’m not an expert by any means, so am wondering if this is true and if so what changes are being made in response.

2 Likes

Yes, we are still testing and code needs to be changed to take into account the observation.

1 Like

Thank you for letting me know, that’s good to hear. One remaining issue they mention is that after the required changes are made, the problem of mining to a private pool (e.g., botnet/cloud) still persists, since sharing the coinbase spendability doesn’t matter.

Though if these issues remain, maybe it would be better to push back the fork a month or two, until they can be verified.

it is possible to have private “member’s only” pools, where the miners do not mind sharing their wallet private keys with the pool operator and other miners (they would have trust them). Same is true with cloud/botnet mining, but the private keys would need to be communicated to all bots, and block header information back and forth.

Not only system administrators would notice the mining activity more easily, they would have access to the private keys too. As the data that needs to be signed changes every block, the amount of bandwidth needed to constantly share information among bots would substantially increase the cost of operating a large botnet.

3 Likes