Don't both blockchains technically have a corrupted block?
Kinda - but the longest chain is the one that we have to accept as "correct" and manually pin it.
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1474. (Read 4670622 times)
September 05, 2014, 04:01:52 PM
Kinda - but the longest chain is the one that we have to accept as "correct" and manually pin it.
September 05, 2014, 04:00:09 PM
Don't both blockchains technically have a corrupted block?
September 05, 2014, 03:54:14 PM
https://mega.co.nz/#!39lgGTiZ!cVMzm7E3lh2uR9FvHTL40PCvIg4D5O9szC_X8JED6zg torrent file
monero win64 #204352 block
monero win64 #204352 block
I understand that everybody wants to be cautious with unapproved blockchains but I also wanted to get my wallet synced and not wait any longer so I downloaded the above torrent file.
I can tell you that it worked perfectly for me and I sent some XMR to poloniex once I was on this chain and the payment has arrived. So all good for me.
My seedbox is seeding this chain on 500mbit if you want to grab it.
If you want to be super-super-cautious then wait for the devs to release an approved blockchain, which I don't understand why this hasn't happened yet.
That's really odd. That blockchain.bin didn't work for me on Windows 7 64-bit when I downloaded it earlier this morning, so I ended up having to use other means.
This is the torrent file and not the full .dat file that was posted on mega.co.nz, are you sure this is the one you downloaded?
Anyway, I'm not forcing anybody to download this, just sharing my experience with it and everybody can decide for themselves.
As mentioned before, my XMR arrived at poloniex without problems and the BTC I traded them for are in my BTC wallet now so no worries for me
Yep, it was the torrent file that I downloaded it with that resulted in a blockchain.bin file that didn't work.
Where I can to get the latest blockchain without MEGA?
thanks
UPD: http://www.fayloobmennik.net/4084993 or http://my-files.ru/c1p27u
September 05, 2014, 03:54:01 PM
My XMR client is on block #205022. I suppose that means I am on the correct chain?
September 05, 2014, 03:36:26 PM
I present here one small project to protect Monero network
ForkGuard
http://forkguard.com/
Watch last blocks on all pools
If pool operator/ exchange / seed node want to put stable results, please download forkguard-script and send me mail to get your free key
September 05, 2014, 03:23:58 PM
https://mega.co.nz/#!39lgGTiZ!cVMzm7E3lh2uR9FvHTL40PCvIg4D5O9szC_X8JED6zg torrent file
monero win64 #204352 block
monero win64 #204352 block
I understand that everybody wants to be cautious with unapproved blockchains but I also wanted to get my wallet synced and not wait any longer so I downloaded the above torrent file.
I can tell you that it worked perfectly for me and I sent some XMR to poloniex once I was on this chain and the payment has arrived. So all good for me.
My seedbox is seeding this chain on 500mbit if you want to grab it.
If you want to be super-super-cautious then wait for the devs to release an approved blockchain, which I don't understand why this hasn't happened yet.
That's really odd. That blockchain.bin didn't work for me on Windows 7 64-bit when I downloaded it earlier this morning, so I ended up having to use other means.
This is the torrent file and not the full .dat file that was posted on mega.co.nz, are you sure this is the one you downloaded?
Anyway, I'm not forcing anybody to download this, just sharing my experience with it and everybody can decide for themselves.
As mentioned before, my XMR arrived at poloniex without problems and the BTC I traded them for are in my BTC wallet now so no worries for me
Yep, it was the torrent file that I downloaded it with that resulted in a blockchain.bin file that didn't work.
September 05, 2014, 02:57:20 PM
any idea on time line? any news would be apreciated, thanks. I suppose Im a little impaticent, just started mining again because nothing out there seems worth wasting the hash on. within hours of mining this attack happened and my coins keep being sent and have no working wallet to recieve them. by the way good work on catching and taking action so fast.
You can still mine at pools as long as they're on the main chain -- just seeing your funds will be difficult until we update the code. Your coins will still exist fine though.
September 05, 2014, 02:51:28 PM
We're trying to get the code to fix the daemon out today. Standby. Our blockchain is now technically corrupted so the fix is a little more complicated than the simple one for the other CN coins.
any idea on time line? any news would be apreciated, thanks. I suppose Im a little impaticent, just started mining again because nothing out there seems worth wasting the hash on. within hours of mining this attack happened and my coins keep being sent and have no working wallet to recieve them. by the way good work on catching and taking action so fast.
September 05, 2014, 12:57:24 PM
We're trying to get the code to fix the daemon out today. Standby. Our blockchain is now technically corrupted so the fix is a little more complicated than the simple one for the other CN coins.
September 05, 2014, 12:51:42 PM
Why not run Windows VM with 30 days old blockchain, run Linux VM with up to date blockchain, block everything on firewall on Windows VM except Linux VM, then set up Linux VM as primary node on Windows VM. Sync safely.
Wow. I might do this just for the fun of it.
I imagine for most just syncing the outdated chain will take less time. Some places in the world it's lunchtime. Perfect for letting the computer crunch along.
September 05, 2014, 12:41:38 PM
Why not run Windows VM with 30 days old blockchain, run Linux VM with up to date blockchain, block everything on firewall on Windows VM except Linux VM, then set up Linux VM as primary node on Windows VM. Sync safely.
September 05, 2014, 12:35:09 PM
I managed to sync ok after I deleted my old blockchain and used the official -30 days- old one on a windows machine. I closed and restarted again just to check and it syncs ok.
September 05, 2014, 12:34:21 PM
If it is somebody well known in the community where it is reasonable to trust then I personally wouldn't have an issue with using a blockchain they provide.
We haven't uploaded an official one because our Windows development node refuses to sync despite several attempts. We're continuing to try, and either way once we have a fix to pin the malicious blocks, that will definitely make our Windows node cooperate and we'll have an official blockchain upload that point.
We haven't uploaded an official one because our Windows development node refuses to sync despite several attempts. We're continuing to try, and either way once we have a fix to pin the malicious blocks, that will definitely make our Windows node cooperate and we'll have an official blockchain upload that point.
It might be more efficient to take denned's chain and validate it in a VM (or just accept the testimonial offered). Once it has synced, that makes it vanishingly unlikely for it to be some sort of trojan.
That said, it wouldn't help debug the problems syncing the dev Windows machine, which is probably more pressing.
September 05, 2014, 12:28:12 PM
Corrected that for you......
Didn't need to as I mangled it. One of the ones someone keeps posting is also my mangled version.
I'm forever discovering that there is always someone smarter. It's getting a bit disheartening.
September 05, 2014, 12:24:19 PM
Corrected that for you......
Didn't need to as I mangled it. One of the ones someone keeps posting is also my mangled version.
September 05, 2014, 12:23:21 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.
September 05, 2014, 12:21:34 PM
Corrected that for you......
September 05, 2014, 12:20:30 PM
https://mega.co.nz/#!39lgGTiZ!cVMzm7E3lh2uR9FvHTL40PCvIg4D5O9szC_X8JED6zg torrent file
monero win64 #204352 block
monero win64 #204352 block
Downloaded it, and Monero tells me "Can't load blockchain storage from file". I guess it's not legit. Might have been created with an older version, or a pre-rc1 version of the .NET GUI?
DO NOT DOWNLOAD BLOCKCHAINS VIA TORRENT FILES POSTED BY RANDOM USERS HERE.
Only download the files from the OP.
September 05, 2014, 12:17:49 PM
Seriously STOP POSTING THAT LINK.
September 05, 2014, 12:07:40 PM
https://mega.co.nz/#!39lgGTiZ!cVMzm7E3lh2uR9FvHTL40PCvIg4D5O9szC_X8JED6zg torrent file
monero win64 #204352 block
monero win64 #204352 block
I understand that everybody wants to be cautious with unapproved blockchains but I also wanted to get my wallet synced and not wait any longer so I downloaded the above torrent file.
I can tell you that it worked perfectly for me and I sent some XMR to poloniex once I was on this chain and the payment has arrived. So all good for me.
My seedbox is seeding this chain on 500mbit if you want to grab it.
If you want to be super-super-cautious then wait for the devs to release an approved blockchain, which I don't understand why this hasn't happened yet.
That's really odd. That blockchain.bin didn't work for me on Windows 7 64-bit when I downloaded it earlier this morning, so I ended up having to use other means.
This is the torrent file and not the full .dat file that was posted on mega.co.nz, are you sure this is the one you downloaded?
Anyway, I'm not forcing anybody to download this, just sharing my experience with it and everybody can decide for themselves.
As mentioned before, my XMR arrived at poloniex without problems and the BTC I traded them for are in my BTC wallet now so no worries for me
Jump to: