surfer43
Sr. Member
 Offline
Activity: 560
Merit: 250
"Trading Platform of The Future!"
|
 |
September 25, 2014, 01:32:48 AM |
|
...
we consider the threat credible and are acting accordingly.
...
Our recommendation for exchange is to remain frozen for external transactions.
...
phantom attack: success |
|
|
|
|
|
|
|
|
|
Once a transaction has 6 confirmations, it is extremely unlikely that an attacker without at least 50% of the network's computation power would be able to reverse it.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
nsimmons
|
|
September 25, 2014, 02:03:57 AM |
|
...
we consider the threat credible and are acting accordingly.
...
Our recommendation for exchange is to remain frozen for external transactions.
...
Dear Monero Can I have have access to my fucking money yet?? |
|
|
|
NewLiberty
Legendary
Offline
Activity: 1204
Merit: 1002
Gresham's Lawyer
|
|
September 25, 2014, 02:08:47 AM |
|
...
we consider the threat credible and are acting accordingly.
...
Our recommendation for exchange is to remain frozen for external transactions.
...
phantom attack: successWeird, I would have picked some other words to indicate success. Such as: "We will be distributing updated checkpoint files that will continue to protect the blockchain without the need for a full update of the daemon."This has been done exactly never before on other coins. It shows the innovation on demand this team can produce, with rapid on-point responsiveness to a real-time threat with no warning, whether it be real or not. They could be writing anything, anywhere, and yet have chosen to work on this project. I am humbled by their generosity to advancing the state of the art as we know it in this arena. Thank you gentlemen, thank you kindly, you are a credit to your profession. |
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
September 25, 2014, 02:17:35 AM |
|
...
we consider the threat credible and are acting accordingly.
...
Our recommendation for exchange is to remain frozen for external transactions.
...
phantom attack: successI agree. As with the previous attacks this will make us stronger. |
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
September 25, 2014, 02:18:30 AM |
|
Can I have have access to my fucking money yet??
It would do you fuck all good to have it stolen or destroyed. |
|
|
|
|
mmortal03
Legendary
Offline
Activity: 1762
Merit: 1010
|
|
September 25, 2014, 03:04:19 AM |
|
...
we consider the threat credible and are acting accordingly.
...
Our recommendation for exchange is to remain frozen for external transactions.
...
phantom attack: successWeird, I would have picked some other words to indicate success. Such as: "We will be distributing updated checkpoint files that will continue to protect the blockchain without the need for a full update of the daemon."This has been done exactly never before on other coins. It shows the innovation on demand this team can produce, with rapid on-point responsiveness to a real-time threat with no warning, whether it be real or not. They could be writing anything, anywhere, and yet have chosen to work on this project. I am humbled by their generosity to advancing the state of the art as we know it in this arena. Thank you gentlemen, thank you kindly, you are a credit to your profession. For people interested in a general discussion on checkpoints (as it applied to Bitcoin), see here: https://bitcointalk.org/index.php?topic=194078.0 |
|
|
|
|
|
aerbax
|
|
September 25, 2014, 03:49:49 AM |
|
Out of curiosity, what's been added that requires unbound? I'm familiar with it being a DNS resolving library, but what's in store?
Edit:
Also, of note, installing just the unbound dev libraries was not enough, "ldns" is also a requirement.
On Debian, this should satisfy the new dependencies: apt-get install libunbound-dev libunbound2 libldns-dev
|
|
|
|
|
pa
|
|
September 25, 2014, 04:25:11 AM |
|
Out of curiosity, what's been added that requires unbound? I'm familiar with it being a DNS resolving library, but what's in store?
Edit:
Also, of note, installing just the unbound dev libraries was not enough, "ldns" is also a requirement.
On Debian, this should satisfy the new dependencies: apt-get install libunbound-dev libunbound2 libldns-dev
In OS X, this worked: brew install unbound brew install --HEAD bitmonero |
|
|
|
|
NewLiberty
Legendary
Offline
Activity: 1204
Merit: 1002
Gresham's Lawyer
|
|
September 25, 2014, 04:30:23 AM |
|
Can I have have access to my fucking money yet??
Yes, if its on poloniex. They're updated and open for withdrawals and deposits of all coins. I've not checked all the others yet, but suspect they are also open or will be soon. |
|
|
|
|
aerbax
|
|
September 25, 2014, 04:57:23 AM |
|
Out of curiosity, what's been added that requires unbound? I'm familiar with it being a DNS resolving library, but what's in store?
Edit:
Also, of note, installing just the unbound dev libraries was not enough, "ldns" is also a requirement.
On Debian, this should satisfy the new dependencies: apt-get install libunbound-dev libunbound2 libldns-dev
thanks, I had to install this too Aaaannnd tewinget just updated the repo to remove that dependency.  https://github.com/monero-project/bitmonero/commit/145dc19eebd2c9f289381debfa1fb7a4b8c71ef7 |
|
|
|
|
pa
|
|
September 25, 2014, 05:00:48 AM |
|
So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:
2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
Did I do something wrong?
|
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
September 25, 2014, 05:03:40 AM |
|
So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:
2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
Did I do something wrong?
What does diff say? |
|
|
|
|
|
aerbax
|
|
September 25, 2014, 05:05:02 AM |
|
So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:
2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
Did I do something wrong?
I'm in the same boat (and the same block). I'm wondering if it's due to everyone I'm connected to not being on the latest rev. Smooth, my diff says: 2014-Sep-25 01:04:34.991768 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s |
|
|
|
|
pa
|
|
September 25, 2014, 05:14:15 AM |
|
So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:
2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
Did I do something wrong?
I'm in the same boat (and the same block). I'm wondering if it's due to everyone I'm connected to not being on the latest rev. Smooth, my diff says: 2014-Sep-25 01:04:34.991768 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s Mine is: diff 2014-Sep-25 01:12:49.076636 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s 2014-Sep-25 01:12:57.568924 [P2P9][143.239.71.93:18080 OUT]Sync data returned unknown top block: 232616 -> 232704 [88 blocks (0 days) behind] SYNCHRONIZATION started 2014-Sep-25 01:12:58.730542 [P2P9][76.16.250.210:18080 OUT]Sync data returned unknown top block: 232616 -> 232704 [88 blocks (0 days) behind] SYNCHRONIZATION started |
|
|
|
|
|
pa
|
|
September 25, 2014, 05:28:52 AM |
|
So, I just recompiled bitmonerod, and now it seems to be stuck on block 232616. Here's some of the output:
2014-Sep-25 00:59:26.151813 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:32.237618 [P2P5][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:38.255829 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Sep-25 00:59:44.404735 [P2P8][188.232.142.138:18080 OUT]Sync data returned unknown top block: 232616 -> 232692 [76 blocks (0 days) behind]
SYNCHRONIZATION started
Did I do something wrong?
I'm in the same boat (and the same block). I'm wondering if it's due to everyone I'm connected to not being on the latest rev. Smooth, my diff says: 2014-Sep-25 01:04:34.991768 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s Mine is: diff 2014-Sep-25 01:12:49.076636 BH: 232616, DIFF: 1074246915, HR: 17904115 H/s I just re-downloaded the blockchain following the link on the OP. Now bitmonerod has synced. Latest diff: diff 2014-Sep-25 01:28:18.357703 BH: 232726, DIFF: 1092360188, HR: 18206003 H/s |
|
|
|
|
Nekomata
Member
Offline
Activity: 99
Merit: 10
|
|
September 25, 2014, 05:31:11 AM
Last edit: April 19, 2015, 06:07:30 AM by Nekomata |
|
XMR is the future.
|
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
September 25, 2014, 05:37:29 AM |
|
It happened here too, I dont remember the block, I had to download the blockchain from OP...
That certainly shouldn't be necessary and definitely shouldn't be required but I'm glad you found a work-around. We will investigate this. If anyone else has the problem please let us know before trying the blockchain download since having your node stuck might help debug it. Everything worked fine on our test systems. |
|
|
|
|
|
aerbax
|
|
September 25, 2014, 05:44:41 AM |
|
Heading to bed, but I can help debug tomorrow if you'd like. I'm comfortable applying diff based patches and the like.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
September 25, 2014, 06:06:13 AM |
|
The problem with syncing is due to not getting the latest update correctly. From my recent update announcement: Plain 'git pull' wont work. Unless you are doing your own modifications to the code it is probably easiest to make a new clone. If you are doing your own modifications you should know how to use git.
So you can either git clone into a new destination or you can do "git reset --hard HEAD~20 ; git pull" |
|
|
|
|
smfuser
Member
Offline
Activity: 82
Merit: 10
|
|
September 25, 2014, 06:10:54 AM |
|
It happened here too, I dont remember the block, I had to download the blockchain from OP...
That certainly shouldn't be necessary and definitely shouldn't be required but I'm glad you found a work-around. We will investigate this. If anyone else has the problem please let us know before trying the blockchain download since having your node stuck might help debug it. Everything worked fine on our test systems. I also have a node that appears to have a similar problem (but stuck at an earlier block before the last checkpoint). I haven't tried downloading the blockchain from the OP. I built from a new git clone. |
|
|
|
|
|
