So I have been looking around but wasn't able to find an answer for it on Reddit and some other site on the internet. When exactly does the fork happen for the RandomX (RX) mining algorithm? I read it is coming with the v0.15 update but considering that the CLI has already released and the only thing required is a GUI update, does this mean that the algorithm will switch when the GUI update is released?
The fork to RandomX will happen around November 30, block height 1978433 |
|
|
|
Well this is huge, time to warn the guys to dump.  It's not that huge. The main thing that got deflated here was the hype about MW being a strong privacy technology when in fact it has always been weak privacy with some other benefits, and sober (non-hype) review and analysis has said that all along. Then again, I guess given the level of hype with this one (more than most, to say the least), deflating that could indeed be seen as somewhat huge. |
|
|
|
FYI AeonCLI isn't building on Windows now with the latest msys updates. I attempted to roll back boost but still getting errors.
Under investigation |
|
|
|
|
@qwizzle if you have a beef with Febo, that's still not relevant to this thread (maybe take it up with forum mods if you think he is violating some rule). In any case, please take it elsewhere.
|
|
|
|
Upcoming point releaseWe're going to be tagging a point release fairly soon with a bunch of minor to moderate bug fixes. It won't require any sort of fork, just upgrading. If you are aware of any bugs or issues please be sure they are reported in the next day so we can evaluate whether there are fixes worth including in this release. This could include testing the current unreleased master branch if you are able to compile from source (EDIT: binaries added below), as that is likely to be same as the new release (unless new problems are discovered). https://github.com/aeonix/aeon/issueshttps://github.com/aeonix/aeon-gui/issues
|
|
|
|
So are “big bang protections” just higher fees to incentivize people to send as much, or something else?
No, it has nothing to do with fees (at least not directly, although any surge in demand that greatly increases the blocksize would also imply increasing fees in practice). Big bang protection was a reworking of the dynamic blocksize so the growth rate slows way down after a 50x increase. An increase from the existing blocksize limit equilibrium (which at present is the minimum of 300 KB) of up to 50x can happen within a relatively short time if demand calls for it, but further increases are slowed way down and take place on the scale of months or years. In practice this is done with a dual median, one of the past 100 blocks and one over the past 100000 blocks. Here is some of the original discussion of the big bang attack: https://www.reddit.com/r/Monero/comments/aj21yt/big_bang_attack_on_xmr/ |
|
|
|
I wonder why i was thinking it was 1500 theoretical?
There was once an estimate close to that which was purely based on CPU validation. However it was before ringCT+bulletproofs and may not even be close any more (I'm not sure). Plus of course CPU validation alone is not sufficient; running the network also requires nodes with sufficient network bandwidth and storage. Hopefully we could handle more than 50 tps currently, at least for a time before nodes start running out of disk space, etc. That's just the point where big bang protection kicks in and further growth slows, not a cap. |
|
|
|
I would think the answer could be infinity... right?
Protocol-wise, in theory, yes. In practice it certainly wouldn't be technologically possible for any node to actually process infinity-sized blocks, and there are also some practical limits of the implementation such as integer overflows in block size calculations. The big bang protection that was forked in at some point limits the rate of block size growth, so if extreme growth started happening there should be ample opportunity to address these issues via updates, including figuring out where the actual hardware limits might be and what to do about it. Big bang protection kicks in at 50x so that would be 15 MB blocks every 2 minutes. At that point, block size growth would slow way down. |
|
|
|
Fork happened already? Everything went smooth? Smooth?
Yes, all good. No network issues at all. |
|
|
|
Steemit.com works wonderful for me
Yes it can shut in any momant. Your Steems can get stuck so watch it Stop spreading FUD. Steemit.com is non-custodial. Even if it were to get shut down, which there is absolutely no evidence whatsoever is going to happen, as long as you have your master pw and/or private keys, you can still access your coins on the blockchain using another UI such as steempeak or even run a node yourself and transfer coins using the cli wallet. |
|
|
|
What are the block number and the expected date for the randomx fork? Is there a site where I could follow a countdown?
No tagged release yet. Stay tuned. |
|
|
|
quick question to @smooth .. do you know but not a show stopper to me at least it is not since I can connect to remote nodes for transactions, is it possible to fast sync and not on ssd drive steem chain (similar to eth with the --fast switch that syncs the chain local and allows transactions to proceed) again not a show stopper since remote works super well! thanks so much in advance
There is no fast sync but if you sync on one system (say a fast/expensive cloud node you rent for several hours), clean shutdown, and copy the shared memory file and block log to another system, it will work, even if the second system is much slower, has a lot less memory, doesn't have SSD, etc. They probably need to have the same OS, compiler versions, etc. Added: To be sure, there is a limit to this. The second system can't have really low memory and no SSD because the swapping will be too slow to keep up with the network. But either low memory or non-SSD will work. If you can't meet that minimum you'll have to use a remote node. |
|
|
|
Binance says also they are delisting steem soon
Where did they say that? Judging from the user's post history, he is just making stuff up on the spot to increase his post count... im saying Binance will follow all the big exchanges will just like Poloniex. you can trust me when im saying it. obvious they will announce it soon right. The big whale have come and gone now with Steemit and the cash cow is milk. We can expect it to fall to .5 cent in coming days maybe even minuet. Its better to sale it before more whale can exit the scam No, what you wrote was a very specific claim: Binance says also they are delisting steem soon
Where did they say it or are you indeed a liar as claimed? |
|
|
|
Binance says also they are delisting steem soon
Where did they say that? |
|
|
|
Monero's cripple miner was inherited from a forked codebase and was not Premeditated also it was a very small portion of coins V/S Evans Scamcoin that not only was massive but he changed the Code to increase the value by lowering the block reward amount after he got his stolen coins!!!
And staked them in masternodes to earn even more. |
|
|
|
|
I think the coingecko dev rating is actually based on some metrics about commits, issues, etc. from GitHub. At least that's what it was a few years ago.
|
|
|
|
But its still listed on Yobit
Unfortunately the yobit wallet hasn't worked in ages |
|
|
|
Aletheia (0.13.0.0)This mandatory release improves the long term stability, sustainability, decentralization, and performance of the blockchain by removing the ASIC-resistant PoW (which requires frequent forking in an arms race with ASIC-developers) and replacing it with the much faster-to-verify and ASIC-friendly (currently FPGA-friendly) Keccak-based KangarooTwelve (K12) algorithm. The use of K12 for PoW was reviewed and approved by the Keccak-team, developers of Keccak/SHA3. It also contains numerous other improvements for reduced transaction size, improved fungibility, safer long-term blocksize growth, and dozens of performance and reliability patches. The mainnet fork date is scheduled on October 25 (height 1146200)Changes include: KangarooTwelve (K12) Keccak variant PoW for FPGA- and eventually ASIC-friendly protocol stability Borromean signatures for smaller transactions Tighter big bang protection preventing exponential blockchain growth Consensus lock time aligned with reference wallet preventing alternate wallets from damaging fungibility Fixed ring size at 3 for improved fungibility Gamma-distribution selection on non-RCT outputs for better ring member ambiguity Improved non-RCT tx output selection for reduced transaction linkages Upstream reliability and performance improvements AEON community-contributed improvements Thanks to stoffu for the majority of the AEON-specific work and additional thanks to all of the AEON community and upstream contributors https://github.com/aeonix/aeon/releases/tag/v0.13.0.0-aeonhttps://github.com/aeonix/aeon-gui/releases/tag/v0.13.0.0-aeon
|
|
|
|
|
Enough personal and character attacks having nothing to do with Monero Speculation.
I'm not going to bother deleting the replies for now (but forum mods still might). If it continues I'll start hitting the delete button.
|
|
|
|
|
Show Posts
