Hi,i'm new to the community,do we have any good news from dev or some important updates?
Well.. they just waded off one of the most serious attacks in cryptocurrency history. How's that for good news?
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1472. (Read 4670622 times)
September 06, 2014, 03:02:26 AM
Well.. they just waded off one of the most serious attacks in cryptocurrency history. How's that for good news?
September 06, 2014, 02:57:08 AM
Hi,i'm new to the community,do we have any good news from dev or some important updates?
September 06, 2014, 02:06:05 AM
I did nothing like this, i simply downloaded the 30 day old bin file and it synced to the proer chain. Da fuq is the prob,devs??? Am i a moron here LOL.......
You did nothing wrong - you got lucky in terms of what peers you connected to:) From scratch it will *eventually* find consensus, but you also may be stuck with the wrong short_chain_history, and thus it *expects* the wrong block 202612. This is what we're patching.
September 06, 2014, 01:59:37 AM
More soon.
Any update on the updated update regarding the updated update yet?Yeah. We tried a couple different things and this one seems to work.
https://github.com/tewinget/bitmonero/commits/202612_exception
We may replace the tree-hash code still because that solution from CN isn't quite right either, but you can download this, build, and try syncing it to the main chain now if you'd like.
Just to correct this - we're NOT going to be using the CN tree_hash.c change, because as you pointed out it's not entirely correct. Our correctly patched tree_hash.c is here: https://github.com/rfree2monero/bitmonero/blob/pr-fix-treehash2/src/crypto/tree-hash.c - we patched that two days ago, but it needs to be done in conjunction with the 202612 exception.
September 06, 2014, 01:44:12 AM
2.5 XMR Bounty to create AWS Linux AMI to mine XMR on CPU and GPU https://bitcointalksearch.org/topic/m.8695669
September 06, 2014, 01:36:08 AM
More soon.
Any update on the updated update regarding the updated update yet?Yeah. We tried a couple different things and this one seems to work.
https://github.com/tewinget/bitmonero/commits/202612_exception
We may replace the tree-hash code still because that solution from CN isn't quite right either, but you can download this, build, and try syncing it to the main chain now if you'd like.
BTW, this is a test release.
Feel free to build if you are comfortable doing so. We will have a slightly different full release with official builds shortly. Testing continues.
More soon.
September 06, 2014, 01:16:51 AM
More soon.
Any update on the updated update regarding the updated update yet?Yeah. We tried a couple different things and this one seems to work.
https://github.com/tewinget/bitmonero/commits/202612_exception
We may replace the tree-hash code still because that solution from CN isn't quite right either, but you can download this, build, and try syncing it to the main chain now if you'd like.
September 06, 2014, 01:11:03 AM
just checking in
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
If you are serious have a word with drawingthemoon. He is an asshat.
I also PM'ed him a short to the point question. If he is against me I will recommend the BBR community to shun him
XMR community overnight is all mature and I am very impressed by this!
Let us just hope it is the "little brother" syndrome that takes just a bit of time to grow out of. Give him a day or two.
Thanks
James
September 06, 2014, 01:08:19 AM
I did nothing like this, i simply downloaded the 30 day old bin file and it synced to the proer chain. Da fuq is the prob,devs??? Am i a moron here LOL.......
Shhhh that's far too easy... stop making sense.
I have a feeling that the devs are being extremely cautious in all regards due to the potential existential threat these kinds of vulnerabilities can pose. The fact that this might seem easy has no bearing on what they perceive are future threats.
They got it, lets just buy cheap XMR...
September 06, 2014, 01:07:15 AM
just checking in
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
If you are serious have a word with drawingthemoon. He is an asshat.
September 06, 2014, 01:04:31 AM
I did nothing like this, i simply downloaded the 30 day old bin file and it synced to the proer chain. Da fuq is the prob,devs??? Am i a moron here LOL.......
Shhhh that's far too easy... stop making sense.
September 06, 2014, 12:00:05 AM
just checking in
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
Thank you James.
We're testing, have everything we need right now. I'll be in touch if that changes though.
September 05, 2014, 11:58:59 PM
just checking in
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
let me know if there is anything I can do to help!
I am very encouraged to see such professional behavior, especially in times of such stress
James
September 05, 2014, 10:58:05 PM
owlcatz, I downloaded the Win64 blockchain.bin from the front page of this thread and the wallet client sync'd just fine.
Did you delete the old wallet.bin before starting the client?
Did you delete the old wallet.bin before starting the client?
September 05, 2014, 10:34:00 PM
I have the same problem
Where I can to get the latest blockchain without MEGA?
thanks
UPD: http://www.fayloobmennik.net/4084993 or http://my-files.ru/c1p27u
These instructions may help you:
If anyone wants to sync themselves due to the chance of a dodgy blockchain (mine isn't but I can understand the concerns - see smooth's post below), download the blockchain from the OP and then start bitmonerod with the flag "--add-priority-node 88.151.101.22:18080". That will preferentially try to sync to a known good node (thanks to hegemoOn and his pool [monero.coolmining.club] for that). It's how I got my chain synced to the right fork. You can still end up on the wrong fork but this gives you a better chance.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Quote
--add-exclusive-node 178.253.202.230:18080 --add-exclusive-node 79.140.20.93:18080 --add-exclusive-node 78.27.112.54:18080 --add-exclusive-node 114.219.164.13:18080 --add-exclusive-node 89.240.241.74:18080 --add-exclusive-node 37.52.249.122:18080 --add-exclusive-node 128.171.159.20:18080 --add-exclusive-node 75.118.218.3:18080
I did nothing like this, i simply downloaded the 30 day old bin file and it synced to the proer chain. Da fuq is the prob,devs??? Am i a moron here LOL.......
September 05, 2014, 10:29:52 PM
I have the same problem
Where I can to get the latest blockchain without MEGA?
thanks
UPD: http://www.fayloobmennik.net/4084993 or http://my-files.ru/c1p27u
These instructions may help you:
If anyone wants to sync themselves due to the chance of a dodgy blockchain (mine isn't but I can understand the concerns - see smooth's post below), download the blockchain from the OP and then start bitmonerod with the flag "--add-priority-node 88.151.101.22:18080". That will preferentially try to sync to a known good node (thanks to hegemoOn and his pool [monero.coolmining.club] for that). It's how I got my chain synced to the right fork. You can still end up on the wrong fork but this gives you a better chance.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Quote
--add-exclusive-node 178.253.202.230:18080 --add-exclusive-node 79.140.20.93:18080 --add-exclusive-node 78.27.112.54:18080 --add-exclusive-node 114.219.164.13:18080 --add-exclusive-node 89.240.241.74:18080 --add-exclusive-node 37.52.249.122:18080 --add-exclusive-node 128.171.159.20:18080 --add-exclusive-node 75.118.218.3:18080
Ok , i call BS. wtf, i downloaded the 30 day old bin off the ANN thread.. Sooo.. Why is my chain ok? You people are getting far and away from reality and i'm calling you out now... xmr devs or not, this is f'in bs.... Edit - My point being you cant even give us the valid blockchain for x64 windows. for real?
September 05, 2014, 10:29:03 PM
David, Your link to the Monero Community Hall of Fame is for the current one while the link on the first page of this thread is for the original one which then has a link to the current one. I don't know if you want to change the link on page 1.
Thanks. Fixed. 
September 05, 2014, 10:23:16 PM
I have the same problem
Where I can to get the latest blockchain without MEGA?
thanks
UPD: http://www.fayloobmennik.net/4084993 or http://my-files.ru/c1p27u
These instructions may help you:
If anyone wants to sync themselves due to the chance of a dodgy blockchain (mine isn't but I can understand the concerns - see smooth's post below), download the blockchain from the OP and then start bitmonerod with the flag "--add-priority-node 88.151.101.22:18080". That will preferentially try to sync to a known good node (thanks to hegemoOn and his pool [monero.coolmining.club] for that). It's how I got my chain synced to the right fork. You can still end up on the wrong fork but this gives you a better chance.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Also, you can 'save' your blockchain in bitmonerod at around block 202000, so that way if you end up on the wrong fork just close bitmonerod without saving and try again.
Quote
--add-exclusive-node 178.253.202.230:18080 --add-exclusive-node 79.140.20.93:18080 --add-exclusive-node 78.27.112.54:18080 --add-exclusive-node 114.219.164.13:18080 --add-exclusive-node 89.240.241.74:18080 --add-exclusive-node 37.52.249.122:18080 --add-exclusive-node 128.171.159.20:18080 --add-exclusive-node 75.118.218.3:18080
September 05, 2014, 10:22:58 PM
More soon.
Any update on the updated update regarding the updated update yet? September 05, 2014, 10:14:05 PM
Seems people have many troubles with downloading blockchain. Still can't understand why devs won't upload blockchain to mega as a mirror. I'll never download blockchain from untrusted source these days and ever.
The trouble isn't with downloading it, that works just fine. The trouble is with us updating the Windows download to a non-forked one, which necessitates us first finishing off this block-pinning code.
Why is the op blockchain over a month old? The post says its kept current, but its not. I still had to sync 12 days when i download for the 8.8.2 upgrade after the last attack.
On an average connection getting through 12 days should not take long at all.
it takes about 4 hours on my 15mbps, but that wasn't my point. my point was the block in the op was a month old, before this attack, it is supposed to be current. I want to know what current means because right now 30 days take me all day to download while locking up my system to near uselessness.
Jump to: