No one is using this shitcoin.
I'll keep exchanging xmr for ETH
Are you actually implying people are using ETH to buy stuff? Lol No, ETH is not a currency its so much more. Anyone actually using XMR to buy stuff ? Blocks are empty so no... Name one merchant that accepts xmr ... People are holding ETH for two reasons, speculation or development, mostly the former; its the same situation as Monero right now. Monero and development are two words that don't go together. I've been around since the bytecoin fork (April 2014), very little has been done in TWO YEARS... I've seen shitcoins with a 3 month lifespan do more development-wise than monero in two fucking years.. |
|
|
|
Blocks are empty of transactions.. No one is using this shitcoin.. Isn't that awesome? It is like using that new highway with fresh new tarmac all by yourself, without anyone knowing, for free! Now when thinking about it I really like keeping it for myself, so please move over to your over-hyped toll road. Sure donkey, keep the 'highway' all to yourself.. |
|
|
|
No one is using this shitcoin.
I'll keep exchanging xmr for ETH
Are you actually implying people are using ETH to buy stuff? Lol No, ETH is not a currency its so much more. Anyone actually using XMR to buy stuff ? Blocks are empty so no... Name one merchant that accepts xmr ... |
|
|
|
Why don't you short XMR, if you are so certain "no one is using this shitcoin" and it "won't even exist this time next year?"
I've still got around 40k + I mine around 250xmr daily .. No need for a loan .. Why do you think the price decreased from 160k to 130k ... Most of the sells were mine.. |
|
|
|
Once ETH releases ring signatures dapp its over. The only chance for monero to survive is to increase adoption by a tenfold. Monero doesn't even have a GUI (not saying that would increase adoption!). Man-child developers.. Look at the blockchain, http://chainradar.com/xmr/blocks , blocks are empty of transactions.. No one is using this shitcoin.. Anyway, I'll keep exchanging xmr for ETH, most likely it won't even exist this time next year. |
|
|
|
Has it forked again ? Difficulty is way lower than it usually is! Expecting all time low (low 4xxx 's) 8 hours from now...
I see no evidence of a fork. Seems like the usual fluctuations, although i would agree it is odd to see the difficulty dropping as the price is rising. Good time to mine. It's far from usual, hover over the current rate/time then look a week or a month back, it is usually in the 8xx range.. http://www.coinwarz.com/difficulty-charts/monero-difficulty-chartI'm expecting 45xxx in 8 hours.. |
|
|
|
|
Has it forked again ? Difficulty is way lower than it usually is! Expecting all time low (low 4xxx 's) 8 hours from now...
|
|
|
|
LOL you think xmr can hit the same price as Dash or what?
Well, eventually it will- when dash starts it's long way down.... With what? One update "bug fixing" per year from Lousy Monero developers or is it with spamming Dash ANN thread with hate messages from Monero supporters including you're developer Smooth? Edit : Monero needs a new development team and a new marketing vision. I agree, developers are total retards (fluffypony, moneromoo, smooth). |
|
|
|
I've bought 15btc worth of XMR and will be buying another 20btc, the difference in price, DASH/XMR is killing me..
Now is the perfect time to show some support!
No, you are trolling lol. You hate XMR.  It's a bit ambiguous, because he mines with 300 KH/s as well. No short-term hidden agenda here, yeah once XMR takes off and is at least .004 i will start selling/dumping, call it whatever you like.. |
|
|
|
|
I've bought 15btc worth of XMR and will be buying another 20btc, the difference in price, DASH/XMR is killing me..
Now is the perfect time to show some support!
|
|
|
|
|
DASH : 0.011
XMR : 0.0011
Its over...
|
|
|
|
There was no fucking attack, it was just a bug!
Oh really? Where did the version 2 block come from? Buggy code! |
|
|
|
|
There was no fucking attack, it was just a bug!
|
|
|
|
Nice try from the attackers. Very fast answer, thanks to everyone who worked on the fix.
No harm done I believe.
No harm done ? Look at the net hash rate, it has halved... |
|
|
|
|
Another fuck-up by the devs. They had a whole year to work on this minor release and guess what, they fucked it up. Retards.
|
|
|
|
Crosspost: NB: https://forum.getmonero.org/1/news-announcements-and-editorials/2452/monero-network-malicious-fork-from-block-913193-updates-and-resolutionFrom that post (which will be kept updated) - Hi all, The Monero network was (once again) the subject of an attack. Due to an error during the development of 0.9, Hydrogen Helix, we omitted a check that allowed for v2 blocks to be added to the network prior to the hard fork block height. Thus instead of forking on March 20, at block height 1009827, a v2 block was added to the network at block height 913193. This is obviously problematic as not all services have updated to 0.9, and the bulk of the network hash rate is still on 0.8.x. We are preparing a point release to 0.9 that resolves this, but in the meantime only if you are running 0.9 you can do the following as a quick patch: Shut down your Monero daemon Grab a checkpoints.json file from getmonero: https://downloads.getmonero.org/checkpoints.jsonPut the file in your bitmonero working directory (eg. ~/.bitmonero or C:\ProgramData\bitmonero) Restart the daemon As soon as the patched point release is out you can remove the checkpoints.json file, if you wish, and run the updated version. The checkpoints.json patch is a quick fix and does not prevent the attacker from replaying their attack at a later block. ANOTHER FUCK-UP BY THE MAN-CHILD DEVELOPERS!!! |
|
|
|
|
DASH doing great too, 0.0090.
Retarded developers ruined Monero.. Such a shame..
|
|
|
|
I hit three blocks in a row again, with less than 300kh/s .. This shouldn't be possible at the current difficulty... 909839 49 to go 1054658909 eaf7aabb143fe3aef10bdfee8d8ecb7eabc7c32f479d17361493ec90bc8b936e 1/12/2016, 11:53:48 PM 3%
909837 47 to go 1057789727 d52b7b1afb24a093e8d3d642014062a0910d232197ffaa8221f6588ab580ea17 1/12/2016, 11:51:58 PM 10%
909833 43 to go 1060389309 3d7bf46d75c5847a1deed22dfa19da42ad0eb0eb8895dba2fa1990732f0e3514 1/12/2016, 11:45:31 PM 2%
909832 42 to go 1058626345 7f967bbc5076d0cfddc297565acd253dc6b08caddf3f573b321f84cae68b899b 1/12/2016, 11:44:22 PM 3%
909831 41 to go 1057809920 0b355e2c882eff0c0392d2ff49ffb8a06ddfe733e63a761ae966c9d8fe5d5ac0 1/12/2016, 11:42:08 PM 29%
Seems like block propagation is the issue here, once you hit a block probability you get the next one is higher than it should be.. EDIT : This needs to be looked at, pools or anyone with high hash rate might find a way to exploit this.. It's not really "higher than it should be", there is no "what it should be". Yes probability to find a block is slightly higher if you know the previous one before anyone else, and it's not an exploit, just a fact due to propagation times. I doubt this is having a meaningful (visible) impact with 1mn time blocks, but anyway the network will switch to 2mn blocks next hard fork (March). I've been finding 2-3-4 blocks in a row both yesterday and today, with around 1% of total net hash. Do the math, this should not happen! Just imagine the advantage miners with 1mh/s+ have... Today's sudden rise in diff. stinks of an exploit .. |
|
|
|
I hit three blocks in a row again, with less than 300kh/s .. This shouldn't be possible at the current difficulty... 909839 49 to go 1054658909 eaf7aabb143fe3aef10bdfee8d8ecb7eabc7c32f479d17361493ec90bc8b936e 1/12/2016, 11:53:48 PM 3%
909837 47 to go 1057789727 d52b7b1afb24a093e8d3d642014062a0910d232197ffaa8221f6588ab580ea17 1/12/2016, 11:51:58 PM 10%
909833 43 to go 1060389309 3d7bf46d75c5847a1deed22dfa19da42ad0eb0eb8895dba2fa1990732f0e3514 1/12/2016, 11:45:31 PM 2%
909832 42 to go 1058626345 7f967bbc5076d0cfddc297565acd253dc6b08caddf3f573b321f84cae68b899b 1/12/2016, 11:44:22 PM 3%
909831 41 to go 1057809920 0b355e2c882eff0c0392d2ff49ffb8a06ddfe733e63a761ae966c9d8fe5d5ac0 1/12/2016, 11:42:08 PM 29%
Seems like block propagation is the issue here, once you hit a block probability you get the next one is higher than it should be.. EDIT : This needs to be looked at, pools or anyone with high hash rate might find a way to exploit this.. |
|
|
|
|
Show Posts
