[BBR] Boolberry: Privacy and Security - Guaranteed Since 2014

[e-coinomist]

Did you read the info at Poloniex Balances page?

Deposit: You MUST send your deposit using the Payment ID below, or it will not be credited.

did you see my payment id? Transaction id: bbb186545e7c6096148b12c15037a75008fd7dccfafc70505d3dba65c072a876, size: 796 bytes
Payment id: e0196fdb756e63acc886012eb7c0a365ce692c77e4d08722d06f666271a6ec77
what wroong i have?

sent an email to busoni@poloniex with that data. today is a bit .. bad timing. this is the wrong thread, too.

to calm you down ... 12 hours ago should have arrived save. in a day from now, things should have settled (wallets upgraded, and such)

[1715606493]

1715606493

[1715606493]

1715606493

[1715606493]

1715606493

[1715606493]

1715606493

[1715606493]

1715606493

[jeezy]

Good morning dear friends!

Just awakened by the call and findout news that Monero is under attack.

I'm started looking on it now, and, well, i have 2 news! Good one and bad one!

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.
Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!

So, i have time to calmly research the problem.

Zoidberg

Thanks for your quick support on this. Let's keep an eye on the chain and solve this bug asap.

[digicoin]

Good news is that we are safe 

[ripplebtc]

https://www.dropbox.com/s/hz5sfauvf7ned3w/bbr.jpg?dl=0
please help me, did i lose my money, i sent to poloniex for 12 hour ago

Did you read the info at Poloniex Balances page?

Deposit: You MUST send your deposit using the Payment ID below, or it will not be credited.

did you see my payment id? Transaction id: bbb186545e7c6096148b12c15037a75008fd7dccfafc70505d3dba65c072a876, size: 796 bytes
Payment id: e0196fdb756e63acc886012eb7c0a365ce692c77e4d08722d06f666271a6ec77
what wroong i have?

https://minergate.com/blockchain/bbr/blocks

Search your transaction id or payment id, it shows "No results found"

[slb]

Good morning dear friends!

Just awakened by the call and findout news that Monero is under attack.

I'm started looking on it now, and, well, i have 2 news! Good one and bad one!

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.
Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!

So, i have time to calmly research the problem.

Zoidberg

If it is easy to spot isn't it possible a notify script to be written? If you tell me how to detect I can make script to detect and notify. PM me if there is need for such a script.

[jl777]

Good morning dear friends!

Just awakened by the call and findout news that Monero is under attack.

I'm started looking on it now, and, well, i have 2 news! Good one and bad one!

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.
Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!



Zoidberg

so this means BBR is safe as long as you see the attack preparation? do you think you can fix the flaw before an attack could be implemented?

my understanding is this attack takes days
and so it can be detected
I have a feeling CZ will be able to fix the code so even with this attack, it just pushes the excess tx into the next block

James

DTS: before you start saying that my statement is disrespecting the XMR devs, plz dont. I just said what I thought CZ could do, nothing more nothing less.

ok load off my mind.. i both love and hate waking up to big drama that bter hack took it out of me. at least this seems like a relatively minor issue for BBR. with monero in the shitter and BBR looking safe.. there could be massive influx of money flowing from xmr to BBR..

i dont see why.
this could have hit BBR just as easily, so the fact it was XMR was just cuz XMR is a bigger target
its in the common code, it is a shared problem
If you look at the market price, you will see BBR suffered right along for this.
both coins suffer short term from the fact there was this bug, but it is one less vulnerability
also, this is more like the GLEFU in NXT, not really a money thing, annoying, a pain, but I dont think they even need to rollback

so like the GLEFU in a few days it is as if it never happened

James

[crypto_zoidberg]

Good morning dear friends!

Just awakened by the call and findout news that Monero is under attack.

I'm started looking on it now, and, well, i have 2 news! Good one and bad one!

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.
Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!

Zoidberg

so this means BBR is safe as long as you see the attack preparation? do you think you can fix the flaw before an attack could be implemented?

Attack won't be success anyway since if i see attack begines i'll prevent it with workaround update.

[Lordoftherigs]

Good morning dear friends!

Just awakened by the call and findout news that Monero is under attack.

I'm started looking on it now, and, well, i have 2 news! Good one and bad one!

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.
Exactly that's why we have alerts feature - in case of emergency i could update network pretty quickly!

So, i have time to calmly research the problem.

Zoidberg

+1 to ability to send network alerts.

[clovis A.]

I'm wandering on over from the BTCD thread to say what up to fellow SuperNet community member BBR .  Hope that's alright with you guys.... Good to have you all on board, great to see something that has the potential to unite the cryptosphere and bring communities together in a positive way.  Looking forward to the future and what's to come......

Peace to the BBR community
clovis

[crypto_zoidberg]

Have no idea - why Monero developers broke Visual Studio build ?....

I agree - msvc not the best compiller - but hey, there are so much developers that work on it and don't use linux toolchain at all... ufff....

it was just my "cry from the heart"

[ChenXue]

BBR is a good coin and this community makes me feel like home,i will do whatever i can do!

[S3MKi]

BBR is a good coin and this community makes me feel like home,i will do whatever i can do!

good said.

[crypto_zoidberg]

Good news!

Seems that CryptoNote fixed flaw with merkle hash!
Fix is already on github, new Boolberry build is coming soon.


Well.... it was pretty hard day for many people here

UPD: Actually have to say that Monero devs has also fixed this bug independently in their own way. Good job.

[enerbyte]

Good news!

Seems that CryptoNote fixed flaw with merkle hash!
Fix is already on github, new Boolberry build is coming soon.


Well.... it seems that it was pretty hard day for many people here

This is good news for CryptoNote.

[jeezy]

Good news!

Seems that CryptoNote fixed flaw with merkle hash!
Fix is already on github, new Boolberry build is coming soon.


Well.... it seems that it was pretty hard day for many people here

Great! Any link to the fix code?

[smooth]

UPD: Actually have to say that Monero devs has also fixed this bug independently in their own way. Good job.

Let's be clear about this.

We have a different fix on github, but we also sent the exact same fix to you for your opinion well before "Cryptonote" (whoever that is) sent it out.  

Crediting it to "Cryptonote" when rfreeman_w and I (EDIT: and tacotime) had already debugged it and sent you the exact same fix first is pretty sad. At least give credit where credit is due.

I expected better from you.

[ebite]

CN survived finally.

[iCEBREAKER]

UPD: Actually have to say that Monero devs has also fixed this bug independently in their own way. Good job.

Let's be clear about this.

We have a different fix on github, but we also sent the exact same fix to you for your opinion well before "Cryptonote" (whoever that is) sent it out.  

Crediting it to "Cryptonote" when rfreeman_w and I had already debugged it and sent you the exact same fix first is pretty sad. At least give credit where credit is due.

I expected better from you.

I expected nothing less than 'grumpy smooth' to be the result of BBR pulling even in volume with XMR.   

And that was yesterday, hours before the fork.

Let's hope CZ has better things to do than meticulously footnote every post he makes, for fear of offending oversensitive and irritable people.

Anyway, congratulations BBR and CZ for being number one on Poloniex!

[smooth]

I expected nothing less than 'grumpy smooth' to be the result of BBR pulling even in volume with XMR.  

I assure you my irritation has nothing to do with trading and everything to do with not being properly credited for the work that rfreeman_w and I did (he first discovered the source of the problem and I came up with the sizeof*8 fix).

EDIT: tacotime also deserves credit for pointing to the tree-hash function based on the transaction count in the poison block used for the attack. It was a great intuition.

[darlidada]

UPD: Actually have to say that Monero devs has also fixed this bug independently in their own way. Good job.

Let's be clear about this.

We have a different fix on github, but we also sent the exact same fix to you for your opinion well before "Cryptonote" (whoever that is) sent it out.  

Crediting it to "Cryptonote" when rfreeman_w and I had already debugged it and sent you the exact same fix first is pretty sad. At least give credit where credit is due.

I expected better from you.

I expected nothing less than 'grumpy smooth' to be the result of BBR pulling even in volume with XMR.  

And that was yesterday, hours before the fork.

Let's hope CZ has better things to do than meticulously footnote every post he makes, for fear of offending oversensitive and irritable people.

Anyway, congratulations BBR and CZ for being number one on Poloniex!

how is that grumpy? do you think smooth care about bbr volume? i'm sure he has plenty of other things to do and its totally possible he also owns some bbr. a lot of xmr holders also speculate on bbr as the latter tends to boom when the former rallies. i sure own some. 3K ish. and before you begin to tell your myths about people liquidating, i can send you a screenshot. we all gamble on bbr.

this is not being grmpy at all. this is about honesty and trust.

i dont know about u but knowing that zoidberg had received a fix from the xmr devs for the cryptonote bug 1 HOUR BEFORE magically receiving the bug fix from the cn team  and then conveniently fogets to credit them makes me want to puke.

if you had any morals you would want to puke too.

@zoidberg: i remember you once wondered why bbr lacked support. this is the reason. lack of transparency. lack of openness. lack of trust. this has nothing to do with fud. you guys are just building yourself your own grave and you are not even aware of it.