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

[darlidada]

i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now

[1714635174]

1714635174

[1714635174]

1714635174

[clintar]

i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now

Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.

[darlidada]

i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now

Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.

no, thats not what i mean, but no problem reminding it to you, though i dont even understand what you are talking about

What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.

Also, who is : 1G467p3k4qGiqQCwFPDqSc46wzQZ9qnXB9JtLW9WD7T5UbnnT3imGsLeMnfjW5tsbBAibLbafcARU5e jW17mgYSd2Nxnq2W  

?

He's taking all the good aliases

I'm interested in "@" and "0" and "1" PM ME !

[clintar]

i've just created an alias through clintar services, and its very fast and easy ! i miss a way to see what alias is attached to my own addresses in the gui though. because right now, when you make an alias there is no indication on the gui that its been made, thats it is linked with the address you are using right now

Oh, you mean when you enter your alias to check stats that it will show your actual bbr address? I forgot I was going to do that. Thanks for the reminder.

no, thats not what i mean, but no problem reminding it to you, though i dont even understand what you are talking about

What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.

Also, who is : 1G467p3k4qGiqQCwFPDqSc46wzQZ9qnXB9JtLW9WD7T5UbnnT3imGsLeMnfjW5tsbBAibLbafcARU5e jW17mgYSd2Nxnq2W  

?

He's taking all the good aliases

I'm interested in "@" and "0" and "1" PM ME !

In the wallet GUI. I see. I think the mock ups showed it that way.

[scruffy scruffington]

What i mean was a way to see WITHIN the GUI which alias was linked to the wallet.

Yes,  it is good idea, and not very difficult in implementation,  as far as I can see. We need to implement it in the future versions.)

[BadAss.Sx]

Tried to open up ports in iptables:

$ sudo iptables -A INPUT -p tcp --dport 10101 -j ACCEPT
$ sudo iptables -A INPUT -p udp --dport 10101 -j ACCEPT

But still can't get it to work. Keep saying [P2P9]Failed to connect to any of seed peers, continuing without seeds

I can ping the IP's though

$ ping 107.170.228.11
PING 107.170.228.11 (107.170.228.11) 56(84) bytes of data.
64 bytes from 107.170.228.11: icmp_seq=1 ttl=57 time=150 ms
64 bytes from 107.170.228.11: icmp_seq=2 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=3 ttl=57 time=151 ms
64 bytes from 107.170.228.11: icmp_seq=4 ttl=57 time=149 ms
64 bytes from 107.170.228.11: icmp_seq=5 ttl=57 time=149 ms

The problems are not only the ping rate its also the speed of the servers. Thats why many people keep getting reconnects when mining

I don't want to mine, i want to keep up a wallet for the instantdex supernet servers. Also it is a dedicated server which has quod core processors and 32GB of RAM.

The daemon runs, but after 45 minutes it quits itself. Very annoying and no solution to this. It needs to run for SuperNET.

[merkalor]

Cannot wait for the new wallet 

[scruffy scruffington]

The daemon runs, but after 45 minutes it quits itself. Very annoying and no solution to this. It needs to run for SuperNET.

Can you post here an errors from daemon log files?

[BadAss.Sx]

**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Dec-25 17:09:31.639308 [P2P0]Connect failed to 201.248.99.222:10101
2014-Dec-25 17:09:31.639438 [P2P0]Connecting to 178.130.36.81:10101(white=0, last_seen: d27.h3.m4.s13)...
2014-Dec-25 17:09:31.677886 [P2P0]Connect failed to 178.130.36.81:10101
2014-Dec-25 17:09:31.677963 [P2P0]Connecting to 94.232.214.80:10101(white=0, last_seen: d42.h15.m44.s14)...
2014-Dec-25 17:09:36.678241 [P2P0]Connect failed to 94.232.214.80:10101
2014-Dec-25 17:09:36.678335 [P2P0]Connecting to 89.248.160.238:10101(white=0, last_seen: d0.h16.m26.s28)...
2014-Dec-25 17:09:36.678701 [P2P0]Connect failed to 89.248.160.238:10101
2014-Dec-25 17:09:36.678744 [P2P0]Connecting to 101.69.219.140:10101(white=0, last_seen: d11.h3.m59.s36)...
2014-Dec-25 17:09:41.678936 [P2P0]Connect failed to 101.69.219.140:10101
2014-Dec-25 17:09:41.679001 [P2P0]Connecting to 69.30.251.251:10101(white=0, last_seen: d5.h22.m50.s58)...
2014-Dec-25 17:09:46.679335 [P2P0]Connect failed to 69.30.251.251:10101
2014-Dec-25 17:09:46.679405 [P2P0]Connecting to 80.186.42.180:10101(white=0, last_seen: d29.h23.m12.s33)...
2014-Dec-25 17:09:51.679878 [P2P0]Connect failed to 80.186.42.180:10101
2014-Dec-25 17:09:53.680037 [P2P1]Connecting to 183.136.214.7:10101(white=0, last_seen: d8.h23.m53.s59)...
2014-Dec-25 17:09:58.680366 [P2P1]Connect failed to 183.136.214.7:10101
2014-Dec-25 17:09:58.680469 [P2P1]Connecting to 123.162.24.121:10101(white=0, last_seen: d1.h4.m58.s2)...
2014-Dec-25 17:10:03.680984 [P2P1]Connect failed to 123.162.24.121:10101
2014-Dec-25 17:10:03.681077 [P2P1]Connecting to 54.84.54.139:10101(white=0, last_seen: d37.h21.m8.s9)...
2014-Dec-25 17:10:03.764806 [P2P1]Connect failed to 54.84.54.139:10101
2014-Dec-25 17:10:03.764848 [P2P1]Connecting to 23.92.210.2:10101(white=0, last_seen: d38.h18.m49.s48)...
2014-Dec-25 17:10:08.765124 [P2P1]Connect failed to 23.92.210.2:10101
2014-Dec-25 17:10:08.765273 [P2P1]Connecting to 80.186.216.94:10101(white=0, last_seen: d48.h2.m14.s35)...
2014-Dec-25 17:10:13.765826 [P2P1]Connect failed to 80.186.216.94:10101
2014-Dec-25 17:10:13.765981 [P2P1]Connecting to 209.73.145.187:10101(white=1, last_seen: d0.h0.m10.s36)...
2014-Dec-25 17:10:14.223901 [P2P4][209.73.145.187:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.224076 [P2P1]Connecting to 91.121.221.92:10101(white=1, last_seen: d0.h12.m24.s5)...
2014-Dec-25 17:10:14.247516 [P2P4][91.121.221.92:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:14.247604 [P2P1]Connecting to 5.9.81.9:10101(white=1, last_seen: d0.h0.m41.s54)...
2014-Dec-25 17:10:14.284622 [P2P4][5.9.81.9:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 17:10:36.361844 Connections:
Remote Host                  Peer id             Recv/Sent (idle,sec)     State                    Livetime(seconds)   
[OUT]38.93.234.100:10101     536377261e2a67f2    679564(21)/11137(21)     state_normal             82                 
[OUT]185.11.72.235:10101     39be3d71fedfa692    966650(21)/17590(21)     state_normal             81                 
[OUT]195.154.170.196:10101   5dce4bd82420f4f7    1049086(11)/18427(11)    state_normal             82                 
[OUT]209.73.145.187:10101    2addbf4a61085eec    12504(5)/1614(5)         state_normal             23                 
[INC]140.206.245.68:4325     17664cad1ca0eeb3    402(70)/4321(21)         state_synchronizing      71                 
[OUT]188.226.215.102:10101   e8bd5efe6ee7c067    1064126(21)/16229(21)    state_normal             82                 
[OUT]91.121.221.92:10101     c50117279b338a6c    2801(21)/777(21)         state_normal             22                 
[OUT]5.9.81.9:10101          42b33c50d2afa4fe    3425(21)/777(21)         state_normal             22                 
[OUT]95.85.21.33:10101       1549c89cc5eafc01    953559(21)/18347(21)     state_normal             80                 

2014-Dec-25 17:31:34.343818 [P2P1]Connecting to 80.186.10.183:10101(white=0, last_seen: d32.h20.m0.s38)...
2014-Dec-25 17:31:35.683496 [P2P1]Connect failed to 80.186.10.183:10101
2014-Dec-25 17:31:35.683629 [P2P1]Connecting to 5.9.23.116:10101(white=0, last_seen: d0.h3.m3.s44)...
2014-Dec-25 17:31:35.720692 [P2P9][5.9.23.116:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-Dec-25 18:14:22.239667 [P2P4][sock 21] Some problems at write: Broken pipe:32

After that the vps is still running (has 2.5GB RAM and 2.5GB SWAP), but the daemon is gone.

[BadAss.Sx]

It also eats a lot of memory for doing nothing..

[darlidada]

coin has been abandonned, better luck on the louis d'or thread.

in before louisd'or is a special order from jl777 and windjc for their supernet.

[BadAss.Sx]

Lol, i was working hard this week with coin dev for the wallet on Linux, so no, coin has not been abandoned. Coin will be part of SuperNET, so please dump them before it goes online.

[scruffy scruffington]

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.

[damashup]

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.

Is there an osx version? If there is, I'd be happy to test that.

[mitache365]

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.

send and recieve tested, working fine here!

[scruffy scruffington]

Is there an osx version? If there is, I'd be happy to test that.

Not yet,  I haven't osx installation now,  will be ready soon.

send and recieve tested, working fine here!

Thank you for testing.) Are there any issues?

And one more thing: Search doesn't work now,  it will be implemented in next version.

[mitache365]

Thank you for testing.) Are there any issues?

recent transactions tab is not working for me.

[pt7]

Thank you for testing.) Are there any issues?

recent transactions tab is not working for me.

Good work Scruffy but I did encounter the following issues:

• The Open Wallet screen is less intuitive.
  The "Destination" and "Password" labels look like either text boxes or buttons.  The actual text boxes were a bit too washed out to immediately notice on my screen.  Additionally, there is an "Open..." button and an "OPEN WALLET" link. Should the "Open..." button be instead "Browse..."?  It might be better to just remove the "Destination" label and place the destination text box next to the "Open" (or "Browse") button.
• When I closed the app, it seemed like it was not responding.  When I tried it again later, I realized that I did not see the "Deinitialing Core" text in the status area.  You might want to place "Please Wait" in big letters in the main window similar to when starting up.
• When I tried sending an amount (using an alias) I got a "Failed to send transaction: wrong payment_id" error.  I think this is because the payment ID text box had the "PAYMENT ID..." text.   When I cleared the text then it sent the amount.   However, there was no visible feedback other than the balance getting reduced.  It took me several clicks (=several sends) to notice.  
• Also I was not able to start version 2.0.41 later - it was stuck with "Loading blockchain data..." status. I started the app from a folder that I copied from the Windows Programs folder. I did try it from this folder prior installing the test version and it worked OK then.  It appears that the blockchain is not interchangable.  The test version is able to use the 2.0.41 blockchain but not the other way around. I had to clear the Windows Roaming folder, and re-download the blockchain.  Perhaps the recommendation should be to try the test version on a different computer or to save the old blockchain from the Windows Roaming folder prior to running the test version.

[scruffy scruffington]

recent transactions tab is not working for me.

• When I tried sending an amount (using an alias) I got a "Failed to send transaction: wrong payment_id" error.  I think this is because the payment ID text box had the "PAYMENT ID..." text.   When I cleared the text then it sent the amount.   However, there was no visible feedback other than the balance getting reduced.  It took me several clicks (=several sends) to notice.  
• Also I was not able to start version 2.0.41 later - it was stuck with "Loading blockchain data..." status. I started the app from a folder that I copied from the Windows Programs folder. I did try it from this folder prior installing the test version and it worked OK then.  It appears that the blockchain is not interchangable.  The test version is able to use the 2.0.41 blockchain but not the other way around. I had to clear the Windows Roaming folder, and re-download the blockchain.  Perhaps the recommendation should be to try the test version on a different computer or to save the old blockchain from the Windows Roaming folder prior to running the test version.

Thank you for your help,  sorry for corrupted blockchain data.(

This is the fix for issues listed in quote above: https://dl.dropboxusercontent.com/u/24069897/bbr/v6/setup.zip, only windows installer or sources at github again.

[pt7]

recent transactions tab is not working for me.

• When I tried sending an amount (using an alias) I got a "Failed to send transaction: wrong payment_id" error.  I think this is because the payment ID text box had the "PAYMENT ID..." text.   When I cleared the text then it sent the amount.   However, there was no visible feedback other than the balance getting reduced.  It took me several clicks (=several sends) to notice.  
• Also I was not able to start version 2.0.41 later - it was stuck with "Loading blockchain data..." status. I started the app from a folder that I copied from the Windows Programs folder. I did try it from this folder prior installing the test version and it worked OK then.  It appears that the blockchain is not interchangable.  The test version is able to use the 2.0.41 blockchain but not the other way around. I had to clear the Windows Roaming folder, and re-download the blockchain.  Perhaps the recommendation should be to try the test version on a different computer or to save the old blockchain from the Windows Roaming folder prior to running the test version.

Thank you for your help,  sorry for corrupted blockchain data.(

This is the fix for issues listed in quote above: https://dl.dropboxusercontent.com/u/24069897/bbr/v6/setup.zip, only windows installer or sources at github again.

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.