jl777
Legendary

Activity: 1176
Merit: 1134
|
 |
September 06, 2014, 05: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
If you are serious have a word with drawingthemoon. He is an asshat. check my posts in the BBR thread 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
|
|
|
|
tacotime
Legendary

Activity: 1484
Merit: 1011
|
 |
September 06, 2014, 05: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_exceptionWe 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.
|
XMR: 44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns
|
|
|
smooth
Legendary

Activity: 2982
Merit: 1203
|
 |
September 06, 2014, 05: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_exceptionWe 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.
|
|
|
|
|
|
5w00p
|
 |
September 06, 2014, 05:44:12 AM |
|
|
|
|
|
|
fluffypony
Donator
Legendary

Activity: 1274
Merit: 1069
GetMonero.org / MyMonero.com
|
 |
September 06, 2014, 05: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_exceptionWe 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.
|
|
|
|
fluffypony
Donator
Legendary

Activity: 1274
Merit: 1069
GetMonero.org / MyMonero.com
|
 |
September 06, 2014, 06: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.
|
|
|
|
|
xiaosu
|
 |
September 06, 2014, 06:57:08 AM |
|
Hi,i'm new to the community,do we have any good news from dev or some important updates?
|
|
|
|
|
Jungian
Legendary

Activity: 930
Merit: 1010
|
 |
September 06, 2014, 07:02:26 AM |
|
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?
|
|
|
|
Mumbles
Newbie

Activity: 50
Merit: 0
|
 |
September 06, 2014, 07:06:11 AM |
|
lol. Is that like a $5 USD bounty?
|
|
|
|
|
polecrab
Member


Activity: 68
Merit: 10
|
 |
September 06, 2014, 07:16:13 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_exceptionWe 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. Thanks you and other devs for getting on top of this. It's a distraction from progressing with features, but just like addressing a bug in a production application, you should gain some knowledge out of all this that can be of value in the future.
|
|
|
|
|
drawingthesun
Legendary

Activity: 1176
Merit: 1018
|
 |
September 06, 2014, 07:27:11 AM |
|
lol. Is that like a $5 USD bounty? Hopefully it could be a $250 bounty in several months...
|
|
|
|
|
|
5w00p
|
 |
September 06, 2014, 07:42:05 AM |
|
lol. Is that like a $5 USD bounty? Yeah, thanks for doing the math on that one. You get an ass hat for that.  I'm one guy with a few XMR, trying to mine my way to some more XMR. I'm not a pool op, a dev, a BTC early-adopter, or anything like that. I could have begged for help, but instead I offered a bounty. Glad you got a lulz.
|
|
|
|
|
Jungian
Legendary

Activity: 930
Merit: 1010
|
 |
September 06, 2014, 08:01:15 AM |
|
lol. Is that like a $5 USD bounty? He offers something. If you don't like it, don't take it. What do you offer?
|
|
|
|
|
otila
|
 |
September 06, 2014, 08:25:06 AM |
|
well, you get integer overflow due to incorrect range check for cnt: size_t ints_size = cnt * HASH_SIZE;
Check rather that cnt <= SIZE_MAX/HASH_SIZE Anyways, it does not help because you use alloca(), you probably have 8 MiB stack size limit on Linux. tree_hash_cnt could be simplified, I have size_t cnt = (size_t)1 << __fls(count - 1);
(__fls from Linux source code)
|
|
|
|
|
|
papa_lazzarou
|
 |
September 06, 2014, 08:53:56 AM |
|
lol. Is that like a $5 USD bounty? Yeah, thanks for doing the math on that one. You get an ass hat for that.  Dude, right now its not profitable. You are better of buying XMR with the money you'll spend on AWS.
|
|
|
|
|
coins101
Legendary

Activity: 1456
Merit: 1002
|
 |
September 06, 2014, 09:24:10 AM |
|
Some questions tied to speculative thoughts on the attack.
When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?
Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.
To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?
Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.
Happy to delete this post if you think it just promotes unnecessary FUD.
|
|
|
|
|
smooth
Legendary

Activity: 2982
Merit: 1203
|
 |
September 06, 2014, 09:42:30 AM |
|
Some questions tied to speculative thoughts on the attack.
When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?
Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.
To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?
Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.
Happy to delete this post if you think it just promotes unnecessary FUD.
Let's address all this after we are done with recovery and have official builds up.
|
|
|
|
|
|
OrientA
|
 |
September 06, 2014, 09:51:22 AM |
|
Some questions tied to speculative thoughts on the attack.
When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?
Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.
To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?
Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.
Happy to delete this post if you think it just promotes unnecessary FUD.
I have the similar thought
|
|
|
|
|
goofy73
Member


Activity: 65
Merit: 10
|
 |
September 06, 2014, 10:00:17 AM |
|
I have a problem with bitmonerod, here is log: 2014-Sep-06 13:52:18.139976 Starting... 2014-Sep-06 13:52:18.189979 bitmonero v0.8.8.2(0.1-g1b8a68f) 2014-Sep-06 13:52:18.223980 Module folder: F:\monero.win.x64.experimental.0526\bitmonerod.exe 2014-Sep-06 13:52:18.259983 Initializing p2p server... 2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:108 Exception at [node_server::init_config], what=input stream error 2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:239 Failed to init config. 2014-Sep-06 13:52:18.318986 ERROR ..\..\src\daemon\daemon.cpp:174 Failed to initialize p2p server. 2014-Sep-06 13:52:18.345987 Mining has been stopped, 0 finished Before ive cleared my temp directory
|
|
|
|
|
|
brownmon
|
 |
September 06, 2014, 10:09:16 AM |
|
What's the status of XMR's collaboration with i2p?
|
|
|
|
|
|