Author

Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 149. (Read 1210749 times)

hero member
Activity: 658
Merit: 500
Maybe.   I still get a lot of failed to connects..  Example..

Will leave it run and see what happens.

Code:
2016-Apr-28 19:37:59.869782 [P2P9]Connecting to 66.228.33.249:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:00.250539 [P2P5]Fresh maintainers info recieved(timestamp: 1409856855)
2016-Apr-28 19:38:00.254543 [P2P5][66.228.33.249:10101 OUT]Sync data returned unknown top block: 244941 -> 508702 [263761 blocks (366 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:00.262013 [P2P5][66.228.33.249:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:00.266505 [P2P9]Connecting to 59.120.166.36:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:01.254746 [P2P4][59.120.166.36:10101 OUT]Sync data returned unknown top block: 244941 -> 508702 [263761 blocks (366 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:01.261750 [P2P4][59.120.166.36:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:01.265733 [P2P9]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:06.270764 [P2P9]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:38:06.273766 [P2P9]Connecting to 95.85.21.33:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:06.830499 [P2P3][95.85.21.33:10101 OUT]Sync data returned unknown top block: 244973 -> 508702 [263730 blocks (366 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:06.839504 [P2P3][95.85.21.33:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:06.843506 [P2P9]Connecting to 107.170.97.197:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:07.031974 [P2P4][107.170.97.197:10101 OUT]Sync data returned unknown top block: 245042 -> 508702 [263660 blocks (366 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:07.039979 [P2P4][107.170.97.197:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:07.043481 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:12.048843 [P2P9]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:38:12.052845 [P2P9]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:17.059008 [P2P9]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:38:17.064012 [P2P9]Connecting to 213.239.213.235:10101(white=0, last_seen: d0.h0.m1.s10)...
2016-Apr-28 19:38:17.504383 [P2P1][213.239.213.235:10101 OUT]Sync data returned unknown top block: 246341 -> 508702 [262361 blocks (364 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:17.512889 [P2P1][213.239.213.235:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:17.517898 [P2P9]Connecting to 176.9.147.178:7180(white=0, last_seen: d0.h0.m0.s21)...
2016-Apr-28 19:38:18.089965 [P2P7][176.9.147.178:7180 OUT]Sync data returned unknown top block: 246379 -> 508702 [262324 blocks (364 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:18.098470 [P2P7][176.9.147.178:7180 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:18.103975 [P2P9]Connecting to 5.9.38.137:10101(white=0, last_seen: d0.h5.m31.s9)...
2016-Apr-28 19:38:18.584219 [P2P0][5.9.38.137:10101 OUT]Sync data returned unknown top block: 246526 -> 508702 [262176 blocks (364 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:18.591730 [P2P0][5.9.38.137:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:18.595237 [P2P9]Connecting to 91.155.234.25:10101(white=0, last_seen: d0.h0.m0.s46)...
2016-Apr-28 19:38:19.326546 [P2P4][91.155.234.25:10101 OUT]Sync data returned unknown top block: 246541 -> 508702 [262161 blocks (364 days) behind]
SYNCHRONIZATION started
2016-Apr-28 19:38:19.334050 [P2P4][91.155.234.25:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2016-Apr-28 19:38:21.339207 [P2P0]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:26.344421 [P2P0]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:38:26.348248 [P2P0]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:31.353608 [P2P0]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:38:31.356923 [P2P0]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:36.362691 [P2P0]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:38:38.366821 [P2P1]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:43.373604 [P2P1]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:38:43.377249 [P2P1]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:48.382744 [P2P1]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:38:48.387248 [P2P1]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:38:53.393805 [P2P1]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:38:55.398108 [P2P4]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:00.403220 [P2P4]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:39:00.407723 [P2P4]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:05.413670 [P2P4]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:39:05.417677 [P2P4]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:10.423106 [P2P4]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:39:12.458957 [P2P7]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:17.463783 [P2P7]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:39:17.467252 [P2P7]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:22.473133 [P2P7]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:39:22.476636 [P2P7]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:27.481865 [P2P7]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:39:29.486010 [P2P5]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:34.491033 [P2P5]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:39:34.495034 [P2P5]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:39.501591 [P2P5]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:39:39.505593 [P2P5]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:44.510638 [P2P5]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:39:46.515028 [P2P1]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:51.520698 [P2P1]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:39:51.524701 [P2P1]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:39:56.530929 [P2P1]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:39:56.535931 [P2P1]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:01.542001 [P2P1]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:40:03.547727 [P2P8]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:08.555455 [P2P8]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:40:08.560624 [P2P8]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:13.566909 [P2P8]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:40:13.571846 [P2P8]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:18.578553 [P2P8]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:40:20.584722 [P2P5]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:25.589731 [P2P5]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:40:25.592732 [P2P5]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:30.597293 [P2P5]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:40:49.103125 [P2P5]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:40:54.108719 [P2P5]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:40:56.115230 [P2P8]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:01.122479 [P2P8]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:41:01.127675 [P2P8]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:06.133664 [P2P8]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:41:06.139669 [P2P8]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:11.144934 [P2P8]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:41:13.148818 [P2P6]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:18.154170 [P2P6]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:41:18.157171 [P2P6]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:23.161752 [P2P6]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:41:23.165000 [P2P6]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:28.169564 [P2P6]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:41:30.181493 [P2P9]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:35.186060 [P2P9]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:41:35.189640 [P2P9]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:40.195840 [P2P9]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:41:40.199342 [P2P9]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:45.204740 [P2P9]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:41:47.208995 [P2P8]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:52.215653 [P2P8]Connect failed to 62.201.213.25:10101
2016-Apr-28 19:41:52.219657 [P2P8]Connecting to 107.170.228.11:10101(white=1, last_seen: never)...
2016-Apr-28 19:41:57.224475 [P2P8]Connect failed to 107.170.228.11:10101
2016-Apr-28 19:41:57.227978 [P2P8]Connecting to 180.97.28.56:10101(white=1, last_seen: never)...
2016-Apr-28 19:42:02.234535 [P2P8]Connect failed to 180.97.28.56:10101
2016-Apr-28 19:42:37.301503 [P2P0]Connecting to 62.201.213.25:10101(white=1, last_seen: never)...
hero member
Activity: 658
Merit: 500
Hi Folk!

Sorry for being away all this time, was really busy with preparing public betta of our second project.
I've reconfigured first seed node and in process of re-configuring others nodes.

http://boolberry.com/state.html is up again.  

Zoidberg

The wallet doesn't want to download any blocks. Its stuck on Connecting.



Did you delete p2pstate.bin and poolstate.bin then launch using the priority nodes?

You'll want to delete those files and launch boolbd.exe from the command line.
 
Windows
Code:
boolbd.exe --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 --add-priority-node 107.170.228.11:10101 --add-priority-node 180.97.28.56:10101 --add-priority-node 66.228.33.249:10101 

Linux
Code:
./boolbd --add-priority-node 66.228.33.249:10101 --add-priority-node 59.120.166.36:10101 --add-priority-node 62.201.213.25:10101 --add-priority-node 95.85.21.33:10101 --add-priority-node 107.170.97.197:10101 --add-priority-node 107.170.228.11:10101 --add-priority-node 180.97.28.56:10101 --add-priority-node 66.228.33.249:10101 

After it syncs then exit and launch the GUI.

I have 8 connections



Found this.  It worked.  Thanks
@bb
full member
Activity: 137
Merit: 100


I tried the miner, it run only couple of hours before crash. I have tried it several times and the result is same, crashed in some hours.

Here is the screenshot.
https://www.sendspace.com/file/335hzt


Hmm, darn. And you did a git pull for the latest? I've been running mine for days without problems... If you do a git checkout master and use that, does it work ok (without the -K option, though)?

Yesterday I run the master at pooltobe, no crash even there are many reconnect and relogin, but after lubuntu 14.04 software update, now I try again at cncoinfarm with keepalive using last pull, I hope it works stable.
legendary
Activity: 896
Merit: 1001
This works for both AMD and Nvidia

https://github.com/mbkuperman/cpuminer-multi-opencl/releases

OpenCL stratum GPUMiner by mbk (recommended for AMD cards)

Example:

minerd.exe -a wildkeccak_ocl -o stratum+tcp://xxx.yourpool.com:7777 -u YOUR_WALLET_ADDRESS -p x -k http ://xxx.yourpool. com/scratchpad.bin -l scratchpad.bin
for windows

or minerd -a wildkeccak_ocl -o stratum+tcp://xxx.yourpool.com:7777 -u YOUR_WALLET_ADDRESS -p x -k http ://xxx.yourpool. com/scratchpad.bin -l ~/scratchpad.bin
for linux

Take a look at this thread as well:

https://bitcointalksearch.org/topic/bbr-boolberry-gpu-miner-discussion-amd-nvidia-opencl-cuda-693118
hero member
Activity: 658
Merit: 500
Wondering is someone could point me in the right direction.  I downloaded the installer and packages, however upon attempting to connect to the network, I run into this error and can't seem to pinpoint where to resolve it.

When I start the daemon or GUI wallet, I cannot connect to the network and just get failed handshake and failed to connect errors. 

This is the error that the daemon returns upon trying to connect to the network to synchronize.

Code:
2016-Apr-27 19:41:29.843608 [P2P7]ERROR c:\jenkins\workdir\boolberry\src\p2p\net_node.inl:430[nodetool::node_server >::do_handshake_with_peer::::operator ()][188.226.215.102:10101 OUT]COMMAND_HANDSHAKE Failed, wrong network!, closing connection.
full member
Activity: 202
Merit: 104


I tried the miner, it run only couple of hours before crash. I have tried it several times and the result is same, crashed in some hours.

Here is the screenshot.
https://www.sendspace.com/file/335hzt


Hmm, darn. And you did a git pull for the latest? I've been running mine for days without problems... If you do a git checkout master and use that, does it work ok (without the -K option, though)?
@bb
full member
Activity: 137
Merit: 100


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. .......

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.


Can you tell me if you tried .....

Also, you would need to run with -K to turn on keepalive.

Hi, sorry my gtx 750 ti rig was struck by tropical rainstorm last ......

I had compiled your last push successfully.

Oh, did you try the opencl one, then?

Not yet, I have no experience compiling in windows, and also because my amd 5870 could only work right its opencl in windows. I tried my amd 5870 with ubuntu 14.04 but didn't work, the error is something about invalid opencl buffersize (ubuntu 14.04 reports 512MB of GPU RAM while it should be 1GB)


I tried the miner, it run only couple of hours before crash. I have tried it several times and the result is same, crashed in some hours.

Here is the screenshot.
https://www.sendspace.com/file/335hzt
@bb
full member
Activity: 137
Merit: 100


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. .......

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.


Can you tell me if you tried .....

Also, you would need to run with -K to turn on keepalive.

Hi, sorry my gtx 750 ti rig was struck by tropical rainstorm last ......

I had compiled your last push successfully.

Oh, did you try the opencl one, then?

Not yet, I have no experience compiling in windows, and also because my amd 5870 could only work right its opencl in windows. I tried my amd 5870 with ubuntu 14.04 but didn't work, the error is something about invalid opencl buffersize (ubuntu 14.04 reports 512MB of GPU RAM while it should be 1GB)
full member
Activity: 202
Merit: 104


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. I think I might have a fix, but haven't tested enough since a real low difficulty share doesn't happen very often.

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.


Can you tell me if you tried to git pull my latest and use that? I was running it all weekend without issue.

Also, you would need to run with -K to turn on keepalive.

Hi, sorry my gtx 750 ti rig was struck by tropical rainstorm last week(i put it under roof, because heavy rain  and wind, the water penetrate the roof, usualy not if just normal rain), and still unable to bring it alive, I hope it is just the psu unit that broken, and I am still very busy, dont have time to fix it. Luckily the amd rig is fine.

I had compiled your last push successfully.

Oh, did you try the opencl one, then?
@bb
full member
Activity: 137
Merit: 100


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. I think I might have a fix, but haven't tested enough since a real low difficulty share doesn't happen very often.

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.


Can you tell me if you tried to git pull my latest and use that? I was running it all weekend without issue.

Also, you would need to run with -K to turn on keepalive.

Hi, sorry my gtx 750 ti rig was struck by tropical rainstorm last week(i put it under roof, because heavy rain  and wind, the water penetrate the roof, usualy not if just normal rain), and still unable to bring it alive, I hope it is just the psu unit that broken, and I am still very busy, dont have time to fix it. Luckily the amd rig is fine.

I had compiled your last push successfully.
full member
Activity: 202
Merit: 104


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. I think I might have a fix, but haven't tested enough since a real low difficulty share doesn't happen very often.

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.


Can you tell me if you tried to git pull my latest and use that? I was running it all weekend without issue.

Also, you would need to run with -K to turn on keepalive.
legendary
Activity: 1354
Merit: 1020
I was diagnosed with brain parasite
Hey folk!

I was talking with windjc, since at the moment i don't have time to do fulltime development, we may be need to rise some funds and hire dev for most critical tasks.
The primary tasks is to put DB into the code, and implement "dark mode" for wallet.
But db is really critical.

I can help a bit with development, but still need experienced full time C++ dev for a 2 months at least i guess.

Zoidberg

I can ask some friends, is this still actual right?
legendary
Activity: 2156
Merit: 1072
Crypto is the separation of Power and State.

If what you're asking for is the ability to create a secure offline wallet (by this I mean create a wallet on a computer that has never connected to the network or indeed the internet, send money to that wallet's address and at a later stage connect to the network to retrieve your funds) then this is a good suggestion. I can see how this would be useful to some users [...]
 

 Tongue


Simplewallet can run offline and generate wallet address have a look :

root@rootdgc:~/boolberry# ./simplewallet --generate-new-wallet 1 [...technical stuff...]

Thanks. Maybe the basic question is whether you are designing a coin for 20 people who know tech or for 20,000 who don't.

You initially design the coin for the 20 people who are capable of building the tools (pool/gui/miner/exchange) for the next 20k early adopters.

That's how Bitcoin happened.

It took decades before Yahoo Mail make it easy for Grandma to SMTP/POP.

Until then, we had to use our brains.   Embarrassed
hero member
Activity: 955
Merit: 500

If what you're asking for is the ability to create a secure offline wallet (by this I mean create a wallet on a computer that has never connected to the network or indeed the internet, send money to that wallet's address and at a later stage connect to the network to retrieve your funds) then this is a good suggestion. I can see how this would be useful to some users [...]
 

 Tongue


Simplewallet can run offline and generate wallet address have a look :

root@rootdgc:~/boolberry# ./simplewallet --generate-new-wallet 1 [...technical stuff...]

Thanks. Maybe the basic question is whether you are designing a coin for 20 people who know tech or for 20,000 who don't.
sr. member
Activity: 259
Merit: 250

Simplewallet can run offline and generate wallet address have a look :

root@rootdgc:~/boolberry# ./simplewallet --generate-new-wallet 1
Boolberry wallet v0.3.0.41(abcdeab)
password: *****
Generated new wallet: 1J8hKJ9jCdiPjnYSM6BbfA2i68fwZyLJG7qiYKn6SUHfBRY1Z8DcmaxRBRqPLvzMSbAJ1SbYjM81gYd WCAKFoT9WETcPbMs
view key: 8088aafbae0e6d1a227c494300ce433bdb5a8a303211c19a3e60908e00e3bf05
**********************************************************************
Your wallet has been generated.
To start synchronizing with the daemon use "refresh" command.
Use "help" command to see the list of available commands.
Always use "exit" command when closing simplewallet to save
current session's state. Otherwise, you will possibly need to synchronize
your wallet again. Your wallet key is NOT under risk anyway.
**********************************************************************
[Boolberry wallet 1J8hKJ]:

Great thanks.

Being able to generate an offline wallet via the GUI might be a useful feature.
 
@bb
full member
Activity: 137
Merit: 100

I have had recent discussions with CZ and he has intimated to me that once Lui is launched he is interested in bringing enhanced features to BBR, [...] However this developer wanted clear directions from the community about where we wanted to take BBR.
Jon

Db implementation and a "fully enhanced anonymous transaction wallet" sound like a good starting point to get development back on track. What would be useful (for a non-technical person like me) is [...]

lol

-----

Since I own some BBR and am actually a real non technical person who has no clue about any of this shit, I'll give some advice that might be helpful. I have enough experience with cryptonote to know that I will get gang attacked if I say the wrong thing, but since I do own some I will try to give one piece of useful advice.

What makes bitcoin somewhat popular is that it actually tries to inspire confidence. It does not do anything overtly sneaky. And if a person were to notice something that seemed problematic, they could point it out and it would get addressed accurately  (talking about general bitcoin issues, not sha2, nsa stuff etc., which will draw out the heavy bullshitters).

When I bought some BBR and downloaded the installer so I could make a backup wallet and take coins off an exchange, I followed the same procedure as with any wallet. a) Install it. b) Run it. c) copy the address so I can send coins then d) make a backup of the wallet. With every coin that is pretty much the basic process.

But with Boolberry when I ran the wallet, in hopes of generating an address I could send coins to and a wallet I could back up, I was not given an address nor a wallet. Instead I got the message "connecting to network" or something.

All wallets connect to a network, if available, of course.

But most wallets will create a wallet for somebody like me who has limited technical skills.

When I mentioned this issue the first time I got some kind of response like "You are mistaken. The wallet can be easily created by doing xyz". 

I went back to the installer and looked for xyz and did not see any way to create a wallet, except by first connecting to a network.

This isn't a small problem that will only bother a few people. If I were genuinely interested in privacy currency, say if I was smuggling kilos of cocaine for the cia or selling guns for the fbi/atf or trying to unload some black market nukes for the kgb, and I needed a privacy centric currency, I would stop right at the point where I realize that a wallet cannot be easily created except by connecting to a network. Then I would just funnel my drug money or whatever through bitcoin.

I may not be entirely "typical", but I am sure I am not the only person who notices this
-
tldr / Any coin that makes a novice connect to a network before creating a backup is broken. Fix little shit like that before worrying about things like DB implementation that most people are not so concerned about.

Simplewallet can run offline and generate wallet address have a look :

root@rootdgc:~/boolberry# ./simplewallet --generate-new-wallet 1
Boolberry wallet v0.3.0.41(abcdeab)
password: *****
Generated new wallet: 1J8hKJ9jCdiPjnYSM6BbfA2i68fwZyLJG7qiYKn6SUHfBRY1Z8DcmaxRBRqPLvzMSbAJ1SbYjM81gYd WCAKFoT9WETcPbMs
view key: 8088aafbae0e6d1a227c494300ce433bdb5a8a303211c19a3e60908e00e3bf05
**********************************************************************
Your wallet has been generated.
To start synchronizing with the daemon use "refresh" command.
Use "help" command to see the list of available commands.
Always use "exit" command when closing simplewallet to save
current session's state. Otherwise, you will possibly need to synchronize
your wallet again. Your wallet key is NOT under risk anyway.
**********************************************************************
[Boolberry wallet 1J8hKJ]:
sr. member
Activity: 259
Merit: 250

I have had recent discussions with CZ and he has intimated to me that once Lui is launched he is interested in bringing enhanced features to BBR, [...] However this developer wanted clear directions from the community about where we wanted to take BBR.
Jon

Db implementation and a "fully enhanced anonymous transaction wallet" sound like a good starting point to get development back on track. What would be useful (for a non-technical person like me) is [...]

lol

-----

Since I own some BBR and am actually a real non technical person who has no clue about any of this shit, I'll give some advice that might be helpful. I have enough experience with cryptonote to know that I will get gang attacked if I say the wrong thing, but since I do own some I will try to give one piece of useful advice.

What makes bitcoin somewhat popular is that it actually tries to inspire confidence. It does not do anything overtly sneaky. And if a person were to notice something that seemed problematic, they could point it out and it would get addressed accurately  (talking about general bitcoin issues, not sha2, nsa stuff etc., which will draw out the heavy bullshitters).

When I bought some BBR and downloaded the installer so I could make a backup wallet and take coins off an exchange, I followed the same procedure as with any wallet. a) Install it. b) Run it. c) copy the address so I can send coins then d) make a backup of the wallet. With every coin that is pretty much the basic process.

But with Boolberry when I ran the wallet, in hopes of generating an address I could send coins to and a wallet I could back up, I was not given an address nor a wallet. Instead I got the message "connecting to network" or something.

All wallets connect to a network, if available, of course.

But most wallets will create a wallet for somebody like me who has limited technical skills.

When I mentioned this issue the first time I got some kind of response like "You are mistaken. The wallet can be easily created by doing xyz".  

I went back to the installer and looked for xyz and did not see any way to create a wallet, except by first connecting to a network.

This isn't a small problem that will only bother a few people. If I were genuinely interested in privacy currency, say if I was smuggling kilos of cocaine for the cia or selling guns for the fbi/atf or trying to unload some black market nukes for the kgb, and I needed a privacy centric currency, I would stop right at the point where I realize that a wallet cannot be easily created except by connecting to a network. Then I would just funnel my drug money or whatever through bitcoin.

I may not be entirely "typical", but I am sure I am not the only person who notices this
-
tldr / Any coin that makes a novice connect to a network before creating a backup is broken. Fix little shit like that before worrying about things like DB implementation that most people are not so concerned about.

If what you're asking for is the ability to create a secure offline wallet (by this I mean create a wallet on a computer that has never connected to the network or indeed the internet, send money to that wallet's address and at a later stage connect to the network to retrieve your funds) then this is a good suggestion. I can see how this would be useful to some users and it should be added to the list of things to be implemented (if it is possible).

I cannot vouch for whether or not users can create offline wallets  already as I haven't tried it.

From what I understand implementing the database is critical (see CZ post above), thus it should concern all BBR users that this is fixed.

Equally any active development on the coin (and more consistent communication) would be welcome at this juncture - which was the basic jest of my post.
 
hero member
Activity: 976
Merit: 646
Hey folk!

I was talking with windjc, since at the moment i don't have time to do fulltime development, we may be need to rise some funds and hire dev for most critical tasks.
The primary tasks is to put DB into the code, and implement "dark mode" for wallet.
But db is really critical.

I can help a bit with development, but still need experienced full time C++ dev for a 2 months at least i guess.

Zoidberg
full member
Activity: 202
Merit: 104


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. I think I might have a fix, but haven't tested enough since a real low difficulty share doesn't happen very often.

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.

Nope, but could you try the latest version I put out, please?
@bb
full member
Activity: 137
Merit: 100


Ok. I got it, now it is running here is the screenshot https://www.sendspace.com/file/duwwb1

Looks stable. Lets see tomorrow.


Thanks, can you tell me which one you are running? I've seen a crash with the cudaminer when hitting a low difficulty share. I think I might have a fix, but haven't tested enough since a real low difficulty share doesn't happen very often.

Oh, looking at the screenshot, I guess it's the cudaminer. Any issues since last night?

Edit: I actually submitted a fix. It should reconnect instead of crash now. Smiley

It was crashed last night after json error and scratchpad mismatch messages, here is the screenshot https://www.sendspace.com/file/ze2d4l

Do you need the coredump ? If yes please tell me where it is located.
Jump to: