Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1370. (Read 4670630 times)

If it can be hacked, cheated, or manipulated it must be done. Don't know what, if anything BCX was trying to point out. But this is the burden that comes along with new frontiers. If ya can't hold, best get off the ride now.  

Will somebody clarify the mining exploit found. What % what miners disadvantaged and what pools were involved?

BCX did great on manipulating people. He may also did great with buying/selling to affect the XMR/BTC chart in his favour.

Just take a look at max zoom-out at the last five days:

https://hitbtc.com/terminal/XMRBTC

Small miners and small bagholders are lured to sell now (better loose some than everything) - and they do sell, many small trades @ the orderbook.
However diff is not lower than the average, so network is doing good.

The timing of all this fud-n-fear scenario could not be better: Just some weeks before the official GUI wallet hits the download page. The GUI wallet gets XMR to the public, to the 90% of humans out there not being able to open a DOS/terminal box and execute bitmonerod and simplewallet.

So let´s see if I am terribly mistaken about all this...

I am going to re-iterate my idea of the core devs holding both the database and GUI in "ransom" for large sums.  Those features are released when people donate that amount of money.

Will somebody clarify the mining exploit found. What % what miners disadvantaged and what pools were involved?

If it can be hacked, cheated, or manipulated it must be done fixed. Don't know what, if anything BCX was trying to point out. But this is the burden that comes along with new frontiers. If ya can't hold, best get off the ride now.  

Will somebody clarify the mining exploit found. What % what miners disadvantaged and what pools were involved?

Still under consideration, including waiting to see what input we get from MEW.

There was no attack (unless you consider a threat to be an attack), so no statement can be made about an attack.

We aren't ever going to comment about undisclosed exploits except after they are fixed. This is should not be taken to imply an exploit was found or wasn't, simply a relevant statement of policy.

No suspicious activity has been observed other than the pool exploit that was fixed recently (and probably not related, as it has apparently be around for a while).


Still under consideration, including waiting to see what input we get from MEW.

Sure, just depends on the legacy that matters to BCX.  All that remains would be for BCX to claim victory.  After all, BCX got everything BCX asked for from the outset.

We all can see how BCX's crushing might of brute force hashing, summonable on command plus a deep history of expert TW assaults and DDoS capability of BCX's repute, has forced the hand of the XMR dev team to alter their commits just to address this threat. 

That the DEV team also came to BCX, hat in hand, asking publicly for help from BCX shows their both humility and single-minded dedication to the success of their project.  They dropped all pretense of ego, all they care about is tight code.  They seem willing to admit that given enough power, the block chain, any block chain, can be overwhelmed. 
They did manage to raise the barricades a good bit, and battened down the hatches with their decentralized and nimble checkpointing innovation.  This would make any TW dependent attack much more costly to BCX with much less disruptive effect.

XMR is in the crib, in the years to come it will have to contend with much greater adversaries than BCX.  It was born out of a litter of CryptoNote alts, had a brief foster parentage with TFT, and now has a strong well balanced family of its own with its current team.

There is no perfect offering, XMR just managed to achieve "best yet", and within the 72 hours of the BCX challenge issued.  Other baby alts would be wise to follow this leadership in TW defenses.

There are TLAs more powerful than BCX.  Thanks to BCX, XMR is a bit more ready for those challenges to come.

I am peeved by this one. Not really differenciating between a crippled miner against a cheating pool. And Monero got both of them. Will there ever be a stop on doing that? Next comes botnet mining doing most of hashrate?

No suspicious activity has been observed other than the pool exploit that was fixed recently (and probably not related, as it has apparently be around for a while).

Couple of questions I hope a core dev could clear up:

1. Did they release the statement about the attack? Have any exploits been discovered?

2. Can we get some clarity on core development funding and how that will proceed?

No you weren't. You were never threatened. A perceived threat (you perceive _everything_ to be a threat) isn't the same thing as a real threat. You just have an extremely low tolerance for things not going your way.

You jumped plumb off the crazy springboard, accusing everybody you disagree with as being part of a grand conspiracy against you. Your paranoia is out of this world and its quite safe to say you don't have the stomach for this game. We all witnessed you fall apart pretty hard in the last week. It was funny, but sad.

Maybe you should take a break for a little while, you know, just for your own mental health and to help you regain some composure.

Never forget we were actually threatened, it doesn't matter the excuses he tried to use.

Suddenly getting lots of the following errors in the daemon (pages full of red text):


I upgraded to head after the fix for the the BCX attack was deployed, and until now it's been running fine.

After restarting the daemon, I have the correct block height (239586 as of now).

Are these errors anything to worry about?

I'm confident the entire reason BCX wants to "bet" is to pay for the hash power required to attack the coin. The reason he hasn't (seemingly) tried is probably because he doesn't want to expense it.

So no, Risto's refusal of the bet would have little to do with his confidence in Monero and everything to do with him not wanting to directly fund its attack.