- 
sech1 
- 
sech1 "We are researching a new mining algorithm, as well as other changes" 
- 
sech1 I wonder what they come up with. Maybe RandomX variant? 
- 
sech1 Either ProgPow or RandomX variant, I just don't see any other easy to integrate algorithms for them 
- 
gingeropolous oh man that'd suck if eth enters the general compute space. I can't see how their GPU miners would be for it though 
- 
hyc yeah, it's progpow or nothing for them 
- 
hyc they'd have a full scale revolt if they tried to adopt randomX 
- 
gingeropolous oh eth classic 
- 
gingeropolous "While some mining pools can improve their systems to encourage honest mining for sure, they are not responsible for the security of the network and we don’t want them to be." indeed 
- 
gingeropolous but M5M400 , how would you guys handle a new protocol rule that puts a random lock time on the block reward, between 1 and 30 days? 
- 
Inge- What is the purpose of the random lock time? 
- 
asymptotically Inge-: wownero is adding a random lock time to try and prevent profit switching miners, not sure what it would do in monero though 
- 
Inge- hm 
- 
moneromooo Why random and not fixed long ? 
- 
asymptotically good question 
- 
hyc eh? if it's a fixed time they can still profit switch 
- 
hyc they'll know exactly when to come back 
- 
moneromooo AFAIK "profit switch" is "the current exchange rate for this coin is high, so let's mine it and sell asap". Is that not right ? 
- 
asymptotically it prevents them from dumping their mining rewards quickly though. by time they can sell it the price will probably be 0 :P 
- 
moneromooo A fixed long time prevents the "asap" part, and the exhange rate will have randomly moved away. 
- 
hyc any predictable time interval works in their favor 
- 
hyc by the same token, I've always wondered about the fixed unlock time in the wallet 
- 
hyc instead of allowing you to spend immediately, you have to wait 20 minutes. so big deal 
- 
hyc you can just monitor for all spends within 20 minutes of receipt 
- 
hyc fixed intervals don't change the probabilities 
- 
moneromooo I don't understand "any predictable time interval works in their favor". Can you expand ? 
- 
moneromooo If anything, reversion to the mean will tend to move the price down if they wanted to mine in times of high prices. 
- 
hyc if miners dumping are the primary downward pressure on the price, they will still be the same pressure, just delayed X minutes later 
- 
hyc if they're the primary pressure, nothing else is going to change things during those X minutes 
- 
hyc you're just making the pipeline longer, but not changing the overall outcome 
- 
hyc just like in a CPU pipeline. 
- 
hyc e.g.: maybe you have a CPU with a 10-cycle pipeline, that completes 2 instructions a cycle, every cycle, once the pipeline is full 
- 
hyc compared to a CPU with a 4-cycle pipeline, that also completes 2 instr/cycle every cycle, once its pipeline is full 
- 
moneromooo Ah I see. Self feedback. If they're not the primary pressure though, but a random walk, a fixed long delay does mitigate the behaviour. 
- 
hyc once their pipelines are full ,the two are indistinguishable 
- 
moneromooo and on-off miners are unlikely to be the primary driver, since they're temporary. 
- 
moneromooo Other miners also sell, and those would get less, since emission is ~constnat. 
- 
Inge- also, the fed should apply a random 25 basis point move of interest rates 
- 
moneromooo Ah, the IRC curse of sending to thre wrong channel every once in a while :) 
- 
Inge- pfft 
- 
hyc but if on-off miners and long term miners are subject to the same fixed delay, there's still no mitigation of their impact 
- 
moneromooo I don't see why not. They want to see at inflated prices. They can only do that  with high certainty if they can sell as soon as possible, to avoid reversion to the mean. 
- 
moneromooo s/see/sell/ 
- 
hyc long term miners can't sell any faster than the on-off miners 
- 
moneromooo I don't see how that matters. 
- 
hyc therefore, they can't overshadow the on-off sell pressure 
- 
gingeropolous i don't think its about price, more about chain / network stability. but yeah, if there's a long lock, then miners can't sell immediately, so there's less incentive to hop on and mine 
- 
gingeropolous i was thinking more in terms of pool centralization. it could be that introducing a random lock causes pool administration to be more .... risky. 
- 
gingeropolous thus, they would increase fees to accommodate for this risk 
- 
gingeropolous presumably, larger pools would counter the random lock with an offer to still pay out regular payouts 
- 
gingeropolous but they'd need a slush fund to do so 
- 
gingeropolous so larger pools with larger expenses might have to have higher fees to create the slush fund and keep things going 
- 
gingeropolous whereas smaller pools, which have less costs (because they're not running 50 thousand servers in every nook of the world), won't have that much overhead 
- 
gingeropolous so their fee increase to create a slush fund would be less 
- 
gingeropolous thats all perhaps. I'm no crypto-mining-economists. thats why im trying to get M5M400 's feel for what they would do as pool admins 
- 
gingeropolous furthermore, smaller pools (take monerohash for instance) already have a dedicated core of users that are accustomed to longer payouts 
- 
gingeropolous i mean, thats not a small pool, its a medium pool but the point is the same 
- 
gingeropolous asymptotically, Inge- ^ 
- 
asymptotically as just a user and not a crypto-mining-economist i wouldn't expect a pool to pay me out early before the blocks unlocked 
- 
asymptotically i think it would stop being a problem after a short while of mining 
- 
hyc nobody mining to a pool expects an immediate payoff. it always takes time to reach the payout threshold 
- 
gingeropolous true 
- 
gingeropolous cryptoconomist 
- 
niocbrrrrrr a big reason that people use big pools is for a more immediate payout 
- 
gingeropolous also true 
- 
gingeropolous i mean, if people didn't mind variance they would solo mine. people mind variance. 
- 
M5M400 gingeropolous: if random reward reward lock times become a thing, so will be PPS pools (which are currently a comperatively high-fee niche) 
- 
M5M400 also, the really big pools (provided they are fair and don't touch abandoned balances) should have a large enough sum sitting in the pool wallet to buffer a month worth of payout fluctuations 
- 
M5M400 so if the goal of the exercise is to prevent pool hopping and diff rocking... I think it will not work 
- 
niocbrrrrrr currently one wow pool has 73.5% of the HR 
- 
niocbrrrrrr I think that this is one of the issues that is trying to be addressed 
- 
niocbrrrrrr it's a 1% fee PPS+ pool 
- 
asymptotically they probably automatically dump the rewards on tradeogre and exchange as soon as it unlocks 
- 
M5M400 I mean, PoW has been a thing for a long time. and it's weaknesses in that regard has rekt a lot of chains. would it be fair to assume that if there was an easy solution to the problem, it would have been implemented somewhere by now? 
- 
xmrpow Why does randomx has such a high cache barier like 2mb l3 cache per core. Wouldnt it be better to set these limits in such a way that even an android phone can mine like a normal pc? 
- 
sech1 2mb is not big, it's barely a minimum to be memory hard 
- 
sech1 android phones have power efficiency not worse than Ryzen CPUs 
- 
xmrpow What be the problem of not being memory hard? Most of the arm chips do have a lack of cache. 
- 
xmrpow Why exlcuding these devices by raisng the cache barrier? 
- 
xmrpow *What would be 
- 
sethsimmons Memory hard algos are a common path to ASIC-resistance, as it raises the cost/size/complexity of ASICs 
- 
sethsimmons But it's not enough by itself, of course, so it's just part of what RandomX does to prevent ASICs having an extreme advantage. 
- 
xmrpow seth: But couldnt an asic company just slam ton of arm cores with enough cache on a board? 
- 
sethsimmons It's not that simple, and if they did something similarly it wouldn't have a serious advantage over some guy in his garage running 100 smartphones on RandomX AFAIK 
- 
sethsimmons An ASIC could be built for any algo, even RandomX, but the point of the algo is to make it costly and reduce/remove the massive efficiency advantage normally associated with ASICs. 
- 
sethsimmons If it costs you millions of $ to fab an ASIC that is only 2x faster/more efficient than a Ryzen CPU, you're not gonna do it because the payoff would take forever 
- 
sethsimmons But I'm by no means the expert here so could be off on some of these points :) 
- 
xmrpow Ok, but I thought the algos before randomx where already memory hard and despite of that asic manufacturers have been able to produce one. Is memory hardness really needed with randomx? 
- 
xmrpow Isnt randomx mostly relying on cpu operations like branch prediction floating point operations etc. ? 
- 
selsta 
- 
sethsimmons Thanks, selsta :) 
- 
xmrpow Am I right by saying: Randomx needs the cache barrier for making it impossible to parallel the computational part of randomx and thereby it is not possible to scale compute without scaling up caches -> No efficiency gain, because wrong ratio between cache and compute? 
- 
sech1 2 MB scratchpad is there to make each computing core big, to prevent ASIC from having thousands of cores on a single chip 
- 
sech1 they can store scratchpads in external memory together with dataset (HBM2 for example), but it hurts power efficiency a lot 
- 
hyc actually no. ARM is slightly worse than AMD Ryzen in efficiency with randomX 
- 
hyc mainly because of typically small caches on ARM 
- 
hyc ARM is still ahead of Intel efficiency tho 
- 
hyc but I'm not sure if that would still be true, if ARM chips scaled clock speeds up to match Intel 
- 
sech1 I didn't say which Ryzen 
- 
sech1 1st gen Ryzen ~ ARM in efficiency 
- 
xmrpow hyc: Do you know why ARM does have less cache compared to amd? Is it just because of the cache costs? 
- 
xmrpow or does cache consume that much energy? 
- 
xmrpow sech1: Interesting... 
- 
xmrpow Might it be possible that our cloud miner went solo mining? There is a 160mhs gap between pool hashrate and network hashrate.