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

[scruffy scruffington]

Also I noted the wallet can no longer be opened by 2.0.41.  Lucky I had a backup, but I did use a wallet with a small amount.  I did not try the  latest download above.  I will try later, if I get some time.

Thank you again,  the version on the last link is much more stable.

[1714613846]

1714613846

[1714613846]

1714613846

[1714613846]

1714613846

[BadAss.Sx]

No offence, but why are you downloading a new wallet from someone with less posts and a different source then the official one?

[pt7]

No offence, but why are you downloading a new wallet from someone with less posts and a different source then the official one?

Good point.  Even though I trust for Scruffy, this is not a good way of doing this.  The download link should at least be in the OP or the official website.  Also the following may help: checksum, code review.

[scruffy scruffington]

No offence, but why are you downloading a new wallet from someone with less posts and a different source then the official one?

Yes,  you are right,  it was a bad idea. Even if it is not something bad in this case,  it creates a bad habbit to use untrusted sources. I will remember about it in the future.

[darlidada]

is it becaus scruffy posted it ? i remember zoidberg vouching for him.

[bitdraw]

just stick to the rule and only download wallets from op

[clintar]

We need your help in testing of the new version. I'm sure it has some issues,  but it is difficult sometimes to find them for the programmer even if they can be obvious for any other person.)

So,  if you have some free time, try this beta version of new wallet and write here your notes or errors you can find. It is beta-version,  so it is not in official boolberry repo now.

Windows installer: https://dl.dropboxusercontent.com/u/24069897/bbr/v5/setup.zip
Sources to build: https://github.com/jahrsg/boolberry/tree/new_ui (my boolberry sources fork, "new_ui" branch in it).

Please,  be careful with new version, backup your wallets key files before testing, don't use it with wallets with big bbr amount.

Thank you in advance.

It didn't compile for me in Linux. I got it to with a few changes. I'll post them tomorrow. Looking good so far.

[BadAss.Sx]

is it becaus scruffy posted it ? i remember zoidberg vouching for him.

Even when Zoidberg is doing that, you should not download wallets from an unknown source. Compiling it for Linux gives you more inside info about the wallet, but downloading an .exe which most of the time cannot be checked is asking for troubles. Not only boolberry, but it could also rip your passphrase of your bitcoin wallet or mailaccounts.

So even when Zoidberg is vouching for him, don't do it!

[q327K091]

is it becaus scruffy posted it ? i remember zoidberg vouching for him.

Even when Zoidberg is doing that, you should not download wallets from an unknown source. Compiling it for Linux gives you more inside info about the wallet, but downloading an .exe which most of the time cannot be checked is asking for troubles. Not only boolberry, but it could also rip your passphrase of your bitcoin wallet or mailaccounts.

So even when Zoidberg is vouching for him, don't do it!

second the above, one single malware and exchanges will react immediately by shutting their wallets down, seen it happen

you all are very sophisticated , it is not that difficult to compile binaries from sources

and not to mention risk of taking radical steps later like blockchain rollback... etc so .. please

[tifozi]

I have talked to Scruffy in Skype and he is an official dev. Zoidberg alluded to it in a post a few weeks ago to make it more "official", what a few of us knew for a while. Albeit it was zoidbergesque  

ATM scruffy is working on BBR new wallet version since i want to have second developer who familiar with BBR code, so this took more time that i expected, but this is need for project safety, a lot of people were talked about it before in this thread.

Zoidberg

Having said that, the feedback from everyone should surely resonate with the more formal approach that we expect from devs and Scruffy sure seems to be on board. I suspect he was enthusiastic to get testing going having worked on it for a while and didn't really mean any harm.  I know clintar may not necessarily have the inclination, but he is also a prime candidate to be an additional dev imo.

Great to see the community behind the two major CN coins - Monero and BBR. I know everyone is swimming uncharted waters and speculation is rampant, but the odds of CrtyptoNote making it where no coin not named Bitcoin has ever made it, are quite massive.

[shojayxt]

I have talked to Scruffy in Skype and he is an official dev. Zoidberg alluded to it in a post a few weeks ago to make it more "official", what a few of us knew for a while. Albeit it was zoidbergesque  

ATM scruffy is working on BBR new wallet version since i want to have second developer who familiar with BBR code, so this took more time that i expected, but this is need for project safety, a lot of people were talked about it before in this thread.

Zoidberg

Having said that, the feedback from everyone should surely resonate with the more formal approach that we expect from devs and Scruffy sure seems to be on board. I suspect he was enthusiastic to get testing going having worked on it for a while and didn't really mean any harm.  I know clintar may not necessarily have the inclination, but he is also a prime candidate to be an additional dev imo.

Great to see the community behind the two major CN coins - Monero and BBR. I know everyone is swimming uncharted waters and speculation is rampant, but the odds of CrtyptoNote making it where no coin not named Bitcoin has ever made it, are quite massive.

Monero and BBR are the future of cryptonote.  If BBR and XMR combined can get close to the market capitalization of another non-btc protocol coin like NXT within the next year that would be an accomplishment.  There's no reason it can't happen.     

[clintar]

We need your help in testing of the new version.
...

Here's the git diff of what I had to change to get it to compile in my Linux distro.

Code:

diff --git a/src/crypto/crypto.h b/src/crypto/crypto.h
index 27bed21..466dca2 100644
--- a/src/crypto/crypto.h
+++ b/src/crypto/crypto.h
@@ -26,11 +26,11 @@ namespace crypto {
 
 #pragma pack(push, 1)
   POD_CLASS ec_point {
-    char data[32];
+    protected: char data[32];
   };
 
   POD_CLASS ec_scalar {
-    char data[32];
+    protected: char data[32];
   };
 
   POD_CLASS public_key: ec_point {
diff --git a/src/crypto/mnemonic-encoding.cpp b/src/crypto/mnemonic-encoding.cpp
index 3a283ad..5781deb 100644
--- a/src/crypto/mnemonic-encoding.cpp
+++ b/src/crypto/mnemonic-encoding.cpp
@@ -3275,7 +3275,8 @@ namespace crypto
                {
                        int n = NUMWORDS;
                        vector<string> tokens;
-                       boost::split(tokens, boost::trim_copy(text), 
+                       string cptext = boost::trim_copy(text);
+                       boost::split(tokens, cptext, 
                                boost::is_any_of(" "));
                        if(tokens.size() % 3 != 0)
                                throw runtime_error("Invalid word count in mnemonic text");

It didn't like accessing crypto.data because it was private. I set it to be declared as protected, but I don't know if that's the right thing to do. I was just trying to get it to compile. Then it was just that I needed to do the trim_copy in a temp variable instead of sending to the split function.

[BadAss.Sx]

What do you mean protected? As you cannot look into the file? If so, stop compiling it!

Please tell me where to find this crypto.data so i can take a look into the old version of it.

[darlidada]

I feel this is a betrayal of loyal BBR investors/supporters.  Why not eventually add POS to BBR?  Is there any plan to distribute any of the new coins to BBR bag holders?
 

I've chosed second way. Befor new year we going to release new GUI, and next release will be the new wallet mode, that actualy utilize fully anonymouse outputs feature. But still, if someone don't like this my attitude - i don't have time and intention to convince you - feel free to quit.



Zoidberg

are u gonna be able to release new gui before new year ?

[Este Nuno]

I feel this is a betrayal of loyal BBR investors/supporters.  Why not eventually add POS to BBR?  Is there any plan to distribute any of the new coins to BBR bag holders?
 

I've chosed second way. Befor new year we going to release new GUI, and next release will be the new wallet mode, that actualy utilize fully anonymouse outputs feature. But still, if someone don't like this my attitude - i don't have time and intention to convince you - feel free to quit.



Zoidberg

are u gonna be able to release new gui before new year ?

Part of that probably depends on how many people are helping to test it I'd assume.

[clintar]

What do you mean protected? As you cannot look into the file? If so, stop compiling it!

Please tell me where to find this crypto.data so i can take a look into the old version of it.

I'm just talking about the the crypto class in the code. There was a section of the code trying to access crypto.data, and it was by default private, I assume. I just set it to protected instead so the code would work. Not sure about any security implications there. Just letting scruffy know what I had to do. It's in my diff what files were changed. I was just using his github repo that he posted.


As far as changes, I think it would be very nice to have the gui wallet check if a daemon is already running, since it just sits there and says "Wait, please..." if a daemon was running when you ran the gui wallet. Also, it just sticks when you close it and doesn't let go of the console. What tools are you guys building this gui in? I am no c++ dude, but I may be able to help with small stuff.

[TooDumbForBitcoin]

But still, if someone don't like this my attitude - i don't have time and intention to convince you - feel free to quit.



Zoidberg

That's what SatoSHE said

[tifozi]

As far as changes, I think it would be very nice to have the gui wallet check if a daemon is already running, since it just sits there and says "Wait, please..." if a daemon was running when you ran the gui wallet. Also, it just sticks when you close it and doesn't let go of the console.

Totally agree. I remember running into these same issues in ubuntu when I first downloaded and ran the wallet, and I didn't quite relay it to Zoidberg as clintar and others were around in IRC to help. I had completely forgotten about following up with devs on this.

Clintar also dug into the code to find out the correct usage of some commands, like connecting to peers manually etc, some of which could use some help with a little bit of additional documentation. This is something us mortals could also help with in github without taking the time away from more important stuff that the devs need to focus on I suppose 

[crypto_zoidberg]

Happy New Year friends!

Sorry for long delay with new version, we(me, Bitcrea, Scruffy) still finalizing and fixing bugs in new build. Hope it will come in next week.

I want to wish a luck to evey person related with crypto, i hope we are making this world better!


Zoidberg

[clintar]

Happy New Year friends!

Sorry for long delay with new version, we(me, Bitcrea, Scruffy) still finalizing and fixing bugs in new build. Hope it will come in next week.

I want to wish a luck to evey person related with crypto, i hope we are making this world better!


Zoidberg

It's good to hear from you! Happey New Yer everyone!

edit: And I'm not even drunk!