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

[cAPSLOCK]

I am unwatching this thread, and will resist posting here....

Lack of self control?

Changed my mind.  OK with you?

Yes, that what ignore button is for

OOh.  I feel all warm inside.

[windblow11]

Can't send the coins, it shows "failed to send transactions : transaction was rejected by daemon". It works fine a few days ago and I already updated to 0.2.0.37 and deleted the boolb folder in roaming folder

Try to rebuild your wallet: http://boolberry.com/howto.html#rebuild_wallet_datafile

solved.  I changed the coin value from 23.95 to 23.9, it was sent. But why?

[Lordoftherigs]

Wow.. the bids are getting chewed up.  It's a buyers market for sure.

10% of all BBRs in existence were dumped today. Have no worry my friend, it cannot last forever

One would imagine that dump of this magnitude will retest the bottom price on market.

[OrientA]

Can't send the coins, it shows "failed to send transactions : transaction was rejected by daemon". It works fine a few days ago and I already updated to 0.2.0.37 and deleted the boolb folder in roaming folder

Try to rebuild your wallet: http://boolberry.com/howto.html#rebuild_wallet_datafile

solved.  I changed the coin value from 23.95 to 23.9, it was sent. But why?

Two reasons: it has to pay the fee, which is more than 23.95 if added. Or the transaction data size over certain value, in XMR, it is 24kB.

[crypto_zoidberg]

Can't send the coins, it shows "failed to send transactions : transaction was rejected by daemon". It works fine a few days ago and I already updated to 0.2.0.37 and deleted the boolb folder in roaming folder

Please, send me logs from daemon and wallet (if you use CLI) or logs from qt-boolb.log if you use GUI to crypto.zoidberg($)gmail.com

[crypto_zoidberg]

Good news!

We have a new build v0.3.0.38(109f49c), where we finally started to prune ring signatures.

What is going on ?
New build prune ring signatures in all transactions that lay under height 70000 (new checkpoint).
When you launch new version, you could see that message(numbers would be little different):



How does it work:

1. When new version (v0.3.x, build 38 and older ) load blockchain from drive, it prune signatures from transactions under chekpoints after storage loaded from drive and before core start work.
2. When new version (v0.3.x, build 38 and older ) download blockchain via network from older clients (v0.2.x, build 37 and younger) it downloads full blockchain and prune transactions locally before put it into the storage.
3. When new version (v0.3.x, build 38 and older ) download blockchain via network from the clients with version v0.3.x it downloads blockchain with pruned ring signatures.
4. When old version (v0.2.x, build 37 and younger) will try to sync with client (v0.3.x) starting from height higher then 70000 (less than ~17 days ago) it will successfully synchronized
5. When old version (v0.2.x, build 37 and younger) will try to fully download blockchain from scratch from new clients (v0.3.x) they fail to do it, so you need to use new client. Or manually download scratchpad from website.
6. On handshake both peers figure out what checkoint height has other party, and consider it to figure out if synchronization is possible. If you see such messages in logs that also means that you have old version and should update your client. But it still work's properly.

Now, when new clients download blockchain via network from versions v0.3.x it looks like this:




Important: If you have version v0.2.x and by some reasons can't/don't want to update it to v0.3.x, and have to synchronize your client from height under 70000, you better to pre-download blockchain from website:
Windows blockchain: http://boolberry.com/downloads/windows/blockchain.bin
Linux blockchain: http://boolberry.com/downloads/linux/blockchain.bin

Well, we tested it, but it's still possible to have bugs, so i won't push update alerts for next few hours to collect feedback.
Let me know is something is going wrong.


Good luck!

[jeezy]

Thanks for your hard work zoidberg. This is really starting to look like a decent coin. Btw will you be part of the SuperNET once it's up?

[superplus]

Thanks for your hard work zoidberg. This is really starting to look like a decent coin. Btw will you be part of the SuperNET once it's up?

its already added

[matrix961]

So with pruning the ring signatures below block 70000 this will keep the size of the blockchain smaller? This won't affect mixing since we will still have ring signatures above this block going forward correct? So in the future will pruning be done again? If so is there going to be some type of schedule like every 70k blocks?

I hope I'm understanding this correctly. Please correct me if I'm not.

[sonoIO]

Good news!

We have a new build v0.3.0.38(109f49c), where we finally started to prune ring signatures.

What is going on ?
New build prune ring signatures in all transactions that lay under height 70000 (new checkpoint).
When you launch new version, you could see that message(numbers would be little different):



How does it work:

1. When new version (v0.3.x, build 38 and older ) load blockchain from drive, it prune signatures from transactions under chekpoints after storage loaded from drive and before core start work.
2. When new version (v0.3.x, build 38 and older ) download blockchain via network from older clients (v0.2.x, build 37 and younger) it downloads full blockchain and prune transactions locally before put it into the storage.
3. When new version (v0.3.x, build 38 and older ) download blockchain via network from the clients with version v0.3.x it downloads blockchain with pruned ring signatures.
4. When old version (v0.2.x, build 37 and younger) will try to sync with client (v0.3.x) starting from height higher then 70000 (less than ~17 days ago) it will successfully synchronized
5. When old version (v0.2.x, build 37 and younger) will try to fully download blockchain from scratch from new clients (v0.3.x) they fail to do it, so you need to use new client. Or manually download scratchpad from website.
6. On handshake both peers figure out what checkoint height has other party, and consider it to figure out if synchronization is possible. If you see such messages in logs that also means that you have old version and should update your client. But it still work's properly.

Now, when new clients download blockchain via network from versions v0.3.x it looks like this:




Important: If you have version v0.2.x and by some reasons can't/don't want to update it to v0.3.x, and have to synchronize your client from height under 70000, you better to pre-download blockchain from website:
Windows blockchain: http://boolberry.com/downloads/windows/blockchain.bin
Linux blockchain: http://boolberry.com/downloads/linux/blockchain.bin

Well, we tested it, but it's still possible to have bugs, so i won't push update alerts for next few hours to collect feedback.
Let me know is something is going wrong.


Good luck!

Now we really live in the future 
Ty Zoidberg!

[tifozi]

That's great that RS pruning is now live !

@zoidberg, AnonyMint (or someone posing as AnonyMint) gave you a thumbs up recently https://bitcointalk.org/index.php?topic=771925.msg8744506#msg8744506 In the past he had ridiculed the "Boolberry" name but never attacked you personally. I think this is the first time he has shown some support for BBR in the open.

I am not yet updated, but if anyone has, can you please compare percentage change of the pruned blockchain size?

[Lordoftherigs]

Boolberry promised, Zoidberg delivered 

[shojayxt]

This is great work! 

I checked the blockchain file size before I updated and after. This trimmed 4.075977% off of the blockchain on my computer.  It was actually more because I hadn't synced for a day or two before I updated and resynced the blockchain.  BBR already synced faster than the other CN coins and this will just make it that much faster and more usable.  I can't wait to see what future developments you come up with crypto_zoidberg.  Advances in the implementation of the Cryptonote technology like this are the reason that BBR IS the BEST Cryptonote coin.  You have made more significant changes to the original codebase than any other implementation of CN.  It's only a matter of time before that becomes a well known fact within the crypto community and BBR takes its rightful place as the leader among Cryptonote coins. 

You deserve some kind of recognition for your hard work so I'm donating another 500 BBR to your dev fund.  BBR transaction# 682e5ea5c373bc8f877189d3b0632c580a384135f8818fd53d6ca5fab417db4c

Keep up the good work!


Blockchain with release "bbr-win-x64-v0.2.0.37(ceecfdf)":




Blockchain after updating to version "bbr-win-x64-v0.3.0.38(109f49c)":

[shojayxt]

Boolberry promised, Zoidberg delivered  

Everything he says he's going to do he does.  

[tifozi]

Another great addition should be a database. Are there plans of implementing that yet?

[luigi1111]

Good news!

We have a new build v0.3.0.38(109f49c), where we finally started to prune ring signatures.

What is going on ?
New build prune ring signatures in all transactions that lay under height 70000 (new checkpoint).
When you launch new version, you could see that message(numbers would be little different):



How does it work:

1. When new version (v0.3.x, build 38 and older ) load blockchain from drive, it prune signatures from transactions under chekpoints after storage loaded from drive and before core start work.
2. When new version (v0.3.x, build 38 and older ) download blockchain via network from older clients (v0.2.x, build 37 and younger) it downloads full blockchain and prune transactions locally before put it into the storage.
3. When new version (v0.3.x, build 38 and older ) download blockchain via network from the clients with version v0.3.x it downloads blockchain with pruned ring signatures.
4. When old version (v0.2.x, build 37 and younger) will try to sync with client (v0.3.x) starting from height higher then 70000 (less than ~17 days ago) it will successfully synchronized
5. When old version (v0.2.x, build 37 and younger) will try to fully download blockchain from scratch from new clients (v0.3.x) they fail to do it, so you need to use new client. Or manually download scratchpad from website.
6. On handshake both peers figure out what checkoint height has other party, and consider it to figure out if synchronization is possible. If you see such messages in logs that also means that you have old version and should update your client. But it still work's properly.

Now, when new clients download blockchain via network from versions v0.3.x it looks like this:




Important: If you have version v0.2.x and by some reasons can't/don't want to update it to v0.3.x, and have to synchronize your client from height under 70000, you better to pre-download blockchain from website:
Windows blockchain: http://boolberry.com/downloads/windows/blockchain.bin
Linux blockchain: http://boolberry.com/downloads/linux/blockchain.bin

Well, we tested it, but it's still possible to have bugs, so i won't push update alerts for next few hours to collect feedback.
Let me know is something is going wrong.


Good luck!

Now we really live in the future 
Ty Zoidberg!

Nice, should probably spell "signatues" correctly.

[windjc]

Great job Zoidberg!

As a community it is up to us to get the word out to everyone about the great work you are doing.

[enerbyte]

after syncing, it has reduced the size of the blockchain, great work!

[Hotmetal]

New build prune ring signatures in all transactions that lay under height 70000 (new checkpoint).
When you launch new version, you could see that message(numbers would be little different):

How about transparent GZIP support in the node-cryptonote-pool? (The patches for the miners can be added afterwards)
This will compress json traffic down to almost nothing, cut down on bandwidth and speed up transactions.

[crypto_zoidberg]

So with pruning the ring signatures below block 70000 this will keep the size of the blockchain smaller?

Blockchain will be smaller, but mostly it will be seen on those parts of blockchain that contain more transactions, early blockchain consist mostly from coinbase transactions that are not affected.

This won't affect mixing since we will still have ring signatures above this block going forward correct?

You can mixin with transactions that is as under checkoint as after checkpoin - no difference, it's not affect. Any of them still could be usen for mixin.

So in the future will pruning be done again? If so is there going to be some type of schedule like every 70k blocks?
I hope I'm understanding this correctly. Please correct me if I'm not.

Frankly, i was thinking to start pruning transactions after first year of currecy live, since it's not really significant effect from this feature for early blockchain where most of transactions is coinbase. But few my friends suggested me that some people think that our features is fake and it would be better to demonstrate it in real work. So enabled this feature and it's seems to be working now.
I think i'll be doing pruning every 6 mounth.