Author

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

legendary
Activity: 2716
Merit: 1116
Don't panic!

Wow! Bittrex also disabled monero wallet and market as safe measure.
legendary
Activity: 1176
Merit: 1134
It looks like Mintpal and HitBTC are both still actively trading as well as withdraws and deposits are open.

Trading I can't do anything about. We've tried to contact those exchanges but haven't been able to.

However, I strongly recommend that you do not attempt to do deposits or withdraws

The block chain is a mess right now and there is no way to know what would happen to your coins.

Do not engage in any transactions at this time

I got in touch with freeworm and he says he froze XMR at bter
Let me know when it is all clear to resume

James
member
Activity: 190
Merit: 10

So what? The code base is brand new and needs work. Every Monero investor should know this.

Bitcoin was crap as a stack of cards at one point, it even had freaking goto loops in the code.

Lets keep the record straight: Bitcoin v1.0 had significantly better code quality than Cryptonote does from what I've seen; I just checked and there weren't any goto statements in the codebase. Cleaning up this mess isn't going to be easy, although it certainly is doable.

I'd strongly suggest taking the good part of Cryptonote - the ring signatures - and porting them over to the Satoshi codebase. Monero could be re-released based on that much better codebase and the UTXO set ported over at the same time so all coin owners on the old system were coin owners on the new system.

Cool idea, let's do that
legendary
Activity: 1120
Merit: 1152

So what? The code base is brand new and needs work. Every Monero investor should know this.

Bitcoin was crap as a stack of cards at one point, it even had freaking goto loops in the code.

Lets keep the record straight: Bitcoin v1.0 had significantly better code quality than Cryptonote does from what I've seen; I just checked and there weren't any goto statements in the codebase. Cleaning up this mess isn't going to be easy, although it certainly is doable.

I'd strongly suggest taking the good part of Cryptonote - the ring signatures - and porting them over to the Satoshi codebase. Monero could be re-released based on that much better codebase and the UTXO set ported over at the same time so all coin owners on the old system were coin owners on the new system.
hero member
Activity: 700
Merit: 500
not just monero but all cryptonote coins are at risk.
sr. member
Activity: 311
Merit: 250
Seems that Monero is totally broken.
legendary
Activity: 1176
Merit: 1015

So what? The code base is brand new and needs work. Every Monero investor should know this.

Bitcoin was crap as a stack of cards at one point, it even had freaking goto loops in the code.
full member
Activity: 198
Merit: 100
Don't panic  Smiley It is just an accident
Yeah,don't be panic and don't sell your nodes for such low price.holders will win.we will see.

Agreed.

Funny thing: The price of BBR is not (yet?) going up -- in face of the XMR attack.
member
Activity: 112
Merit: 10
gah so i cant even trade it... shit happens i guess.
jr. member
Activity: 51
Merit: 10
It looks like Mintpal and HitBTC are both still actively trading as well as withdraws and deposits are open.

Trading I can't do anything about. We've tried to contact those exchanges but haven't been able to.

However, I strongly recommend that you do not attempt to do deposits or withdraws

The block chain is a mess right now and there is no way to know what would happen to your coins.

Do not engage in any transactions at this time


Unfortunately, I'm attempt send XMR...
Simplewallet log:
2014-Sep-04 08:39:49.209510 Processed block: <861e91b6a4a4969017096828732d3b951eec297c9a62e4bf997815f034bbce75>, height 202631, 93(0/93)ms
2014-Sep-04 08:39:49.214501 Spent money: 0.100000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.214501 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.100000000000
2014-Sep-04 08:39:49.219492 Spent money: 0.400000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.220490 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.400000000000
2014-Sep-04 08:39:49.226479 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.226479 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.232467 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.232467 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.237458 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.237458 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.243446 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.244445 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.251442 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.251442 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.260415 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.260415 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.268398 Spent money: 0.300000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.268398 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.300000000000
2014-Sep-04 08:39:49.274388 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.274388 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.280376 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.280376 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.285366 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.285366 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.291356 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.291356 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.296345 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.296345 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.301336 Spent money: 0.300000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.301336 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.300000000000
2014-Sep-04 08:39:49.307325 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.307325 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.312315 Spent money: 0.500000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.313313 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.500000000000
2014-Sep-04 08:39:49.318303 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.318303 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.324293 Spent money: 0.500000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.324293 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.500000000000
2014-Sep-04 08:39:49.330281 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.330281 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.336269 Spent money: 0.300000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.336269 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.300000000000
2014-Sep-04 08:39:49.342258 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.342258 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.347255 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.347255 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.353238 Spent money: 0.300000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.353238 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.300000000000
2014-Sep-04 08:39:49.359226 Spent money: 0.200000000000, with tx: <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>
2014-Sep-04 08:39:49.359226 Height 202632, transaction <87beebbfde22c48f547799be2c4f4aee4ea377a989e98be4983e9a77989938bd>, spent 0.200000000000
2014-Sep-04 08:39:49.415120 Processed block: <4b9873cee9170be4965164e77c12240106981ddfe1d012d826d2854016bd3f0f>, height 202632, 203(0/203)ms

Go to http://monerochain.info/block/7adf9703a96d2867d4678d08cfc20c2a3c1109189ed07fe82f437858cfd49377 and see:

Block
Hash   7adf9703a96d2867d4678d08cfc20c2a3c1109189ed07fe82f437858cfd49377
Height   202631
Timestamp (UTC)   2014-09-04 05:57:25
Difficulty   1,239,873,341
Reward (XMR)   14.535049504847
Transactions   1
Block Size   255
Transactions
Hash   Amount (XMR)   Size
331a22ca068a051e2def936411d8999a6f92dd4547257b333e8f56a11aa1ed28    14.535049504847    255

That's all...

It is interesting, where is my 6 XMR hang out?
full member
Activity: 125
Merit: 100
Don't panic  Smiley It is just an accident
Yeah,don't be panic and don't sell your nodes for such low price.holders will win.we will see.
legendary
Activity: 1106
Merit: 1000
Don't panic  Smiley It is just an accident
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
Yes, create a new wallet, preferably on an offline computer, write down the seed words it gives you, and write down the public address it gives you. That is your paper wallet. Send to the wallet using the public address. Use the seed words to access the coins from it by creating a new online wallet with the '--restore-deterministic' option.

Wow, great explanation! Though I knew about the deterministic option, I somehow thought that XMR has no such thing as paper wallet.
Now... let's push my luck.. and is there any way to actually know how much is on a paper wallet without restoring it and going online? (my guess is "no", but I already guessed wrong once).


* NeuroticFish continues to read, to understand what happened with the network last night
legendary
Activity: 2968
Merit: 1198
It looks like Mintpal and HitBTC are both still actively trading as well as withdraws and deposits are open.

Trading I can't do anything about. We've tried to contact those exchanges but haven't been able to.

However, I strongly recommend that you do not attempt to do deposits or withdraws

The block chain is a mess right now and there is no way to know what would happen to your coins.

Do not engage in any transactions at this time
hero member
Activity: 532
Merit: 500
It looks like Mintpal and HitBTC are both still actively trading as well as withdraws and deposits are open.
legendary
Activity: 1624
Merit: 1008
On IRC they said that mining should be suspended so I shut down my miner.  We will be told when to restart.
donator
Activity: 1274
Merit: 1060
GetMonero.org / MyMonero.com
I'm up and picking up from tacotime - just need 15 mins to orient myself.
legendary
Activity: 1484
Merit: 1005
I need to crash. Fluffypony and the other devs will be up soon and will continue diagnosing it.

My guess it that it's a buffer underflow/overflow code relating to the merkle tree code, but I'm not entirely sure. The crazy block that broke the network had the following idiosyncrasies:
- Normal coinbase
- 510 tx with 0.0000000000001 inputs and 0.000000000000 outputs (effective fee 0.000000000001)
- 2 tx at the end of the block with 2.0 inputs and 1.9999999999999 outputs

--> 513 tx total included, possibly overflowing a value related to the merkle tree tx calculation somewhere (for instance, if a binary merkle tree has two branches which are allowed to contain 256 tx each, and then when you get over 512 something bad happens, eg memory access somewhere there shouldn't be)

Now, the outputs of 0.0000000000001 that were used were produced 4 days ago, so it looks like the attackers were well aware of the bug, but needed to expand the block size to get all these outputs into a single block. To do so, they emulated normal pool payout transactions but added high mixin and tx_extra content to bloat the tx. These transactions were otherwise indistinguishable from pool tx payouts, aside from occasionally using strangely large inputs. To not raise suspicion, the tx mempool was not flooded by tx, but rather 4-10 new tx were submitted whenever a new block entered the network (so that the mempool didn't look suspiciously large). Our course, we recognized these as bizarre ealier in the day and were watching the blockchain like a hawk.

Overall, it appears it was an extremely well coordinated attack to exploit an unexpected engineering flaw in the handling of merkle trees. I still don't understand why it happened, but I'm already up way too late and I need to get some sleep.

Someone will pick up where I left off.
sr. member
Activity: 311
Merit: 250
Jump to: