Pages:
Author

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

sr. member
Activity: 299
Merit: 250
Thanks your hard working! I really like this coins! But this coin needs stronger Dev!
full member
Activity: 231
Merit: 101
Is the wallet link in the OP (windows binaries) the correct current wallet download?

Also please the links for an Nvidia GPU miner?

I would like to mine at one of the pools, any suggestion anyone?
Epsylon/tpruvot's is probably the best for nvidia. https://github.com/tpruvot/ccminer , but he hasn't made a binary release with the larger scratchpad. I will try to get a binary created, or you can try the opencl one i mentioned a few posts ago, https://github.com/mbkuperman/cpuminer-multi-opencl/releases until then. As far as pools, I'm partial to my own http://mining.blue Grin, but here is a list of all the pools I know about. http://explorer.mining.blue/en/#pools

Thank you very much for the info, yes a Win binary would be great! And regarding the OP wallet links, are those correct??
No, I should build those, too.

Here is the updated tpruvot ccminer binary. Let me know if it works as I don't have a windows machine to test on. https://github.com/clintar/ccminer/releases/tag/v2.1-xbb

I'm having some issues with the boolberry wallet build. I'll update when I get that sorted.

Edit: OK, I made a release on my github repo for cryptozoidberg's latest master that has all the latest fixes. https://github.com/clintar/boolberry/releases/tag/v0.2a

Nice and thank you, I let wallet run overnight, no connections and no sync however, am I missing a conf file with nodes? I am familiar with cryptonote coins in linux and windows. Log file shows no connection to seeds, how to change or add connections, this I don't know, any advice? I ran you Win build from the link above.

EDIT: It connects if I use the "start" batch with proxy node flag in the folder, thanks Smiley
full member
Activity: 202
Merit: 104
Is the wallet link in the OP (windows binaries) the correct current wallet download?

Also please the links for an Nvidia GPU miner?

I would like to mine at one of the pools, any suggestion anyone?
Epsylon/tpruvot's is probably the best for nvidia. https://github.com/tpruvot/ccminer , but he hasn't made a binary release with the larger scratchpad. I will try to get a binary created, or you can try the opencl one i mentioned a few posts ago, https://github.com/mbkuperman/cpuminer-multi-opencl/releases until then. As far as pools, I'm partial to my own http://mining.blue Grin, but here is a list of all the pools I know about. http://explorer.mining.blue/en/#pools

Thank you very much for the info, yes a Win binary would be great! And regarding the OP wallet links, are those correct??
No, I should build those, too.

Here is the updated tpruvot ccminer binary. Let me know if it works as I don't have a windows machine to test on. https://github.com/clintar/ccminer/releases/tag/v2.1-xbb

I'm having some issues with the boolberry wallet build. I'll update when I get that sorted.

Edit: OK, I made a release on my github repo for cryptozoidberg's latest master that has all the latest fixes. https://github.com/clintar/boolberry/releases/tag/v0.2a
full member
Activity: 231
Merit: 101
Is the wallet link in the OP (windows binaries) the correct current wallet download?

Also please the links for an Nvidia GPU miner?

I would like to mine at one of the pools, any suggestion anyone?
Epsylon/tpruvot's is probably the best for nvidia. https://github.com/tpruvot/ccminer , but he hasn't made a binary release with the larger scratchpad. I will try to get a binary created, or you can try the opencl one i mentioned a few posts ago, https://github.com/mbkuperman/cpuminer-multi-opencl/releases until then. As far as pools, I'm partial to my own http://mining.blue Grin, but here is a list of all the pools I know about. http://explorer.mining.blue/en/#pools

Thank you very much for the info, yes a Win binary would be great! And regarding the OP wallet links, are those correct??
full member
Activity: 202
Merit: 104
Is the wallet link in the OP (windows binaries) the correct current wallet download?

Also please the links for an Nvidia GPU miner?

I would like to mine at one of the pools, any suggestion anyone?
Epsylon/tpruvot's is probably the best for nvidia. https://github.com/tpruvot/ccminer , but he hasn't made a binary release with the larger scratchpad. I will try to get a binary created, or you can try the opencl one i mentioned a few posts ago, https://github.com/mbkuperman/cpuminer-multi-opencl/releases until then. As far as pools, I'm partial to my own http://mining.blue Grin, but here is a list of all the pools I know about. http://explorer.mining.blue/en/#pools
full member
Activity: 231
Merit: 101
Is the wallet link in the OP (windows binaries) the correct current wallet download?

Also please the links for an Nvidia GPU miner?

I would like to mine at one of the pools, any suggestion anyone?
full member
Activity: 202
Merit: 104
Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner Smiley
Usually if you are compiling from source, the git repo will get updates, so you can just run
Code:
git pull
to get the changes and run make again, but if you are just using a binary, you'll have to wait for someone to compile a new one. Which miner are you using?

Using minerd (designed for algo wildkeccak_ocl with rx470, win10 64 bit, mining in pool). Where to put code: "git pull" in *.bat file. Please do not forget to paste address where i can send for help.
If it's a windows machine, I think you should be ok just downloading this latest miner. Looks like it has a scratchpad setting large enough. https://github.com/mbkuperman/cpuminer-multi-opencl/releases
newbie
Activity: 84
Merit: 0
Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner Smiley
Usually if you are compiling from source, the git repo will get updates, so you can just run
Code:
git pull
to get the changes and run make again, but if you are just using a binary, you'll have to wait for someone to compile a new one. Which miner are you using?

Using minerd (designed for algo wildkeccak_ocl with rx470, win10 64 bit, mining in pool). Where to put code: "git pull" in *.bat file. Please do not forget to paste address where i can send for help.
full member
Activity: 202
Merit: 104
Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner Smiley
Usually if you are compiling from source, the git repo will get updates, so you can just run
Code:
git pull
to get the changes and run make again, but if you are just using a binary, you'll have to wait for someone to compile a new one. Which miner are you using?
newbie
Activity: 84
Merit: 0
Any chance to reveal what can be done in miner to accept bigger scratchpad would be honored or can give me address for 10BBR, am a small miner Smiley
full member
Activity: 202
Merit: 104
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with
Code:
git clone -b lmdb_scratch https://github.com/clintar/boolberry.git
then
Code:
mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon
should compile it, at least in linux. Let me know if it compiles or not at least! Smiley

I tried this branch. It compiled without problems. The produced binary started and created an initial db file of about 1 GB.

There is no file conversion yet from the "old" .bin format to lmdb format, so it wants to sync the blockchain from start, even with a blockchain file within reach, right? At least that was what it did on my system.

Sync immediately ran into problems however. I had repeated messages as follows:

Code:
2017-Aug-06 13:37:10.273809 [P2P3][193.70.85.9:10101 OUT]Block verification failed, dropping connection

These messages come from currency_protocol_handler.inl, line #377 (as checked out from GitHub today):

Code:
       if(bvc.m_verifivation_failed)
        {
          LOG_PRINT_CCONTEXT_L0("Block verification failed, dropping connection");
          m_p2p->drop_connection(context);
          m_p2p->add_ip_fail(context.m_remote_ip);
          return 1;
        }

Sync stuck forever at block 3 with repeated messages like this one:

Code:
2017-Aug-06 13:37:09.362602 [P2P7][193.70.85.9:10101 OUT]Sync data returned unknown top block: 3 -> 840955 [840952 blocks (1167 days) behind]

Is it supposed to be able to sync with "conventional" Boolberry nodes?
It should, but it's not in a good state. I have some fixes, but it will fall if there is an alt chain. I haven't had a lot of time to debug the problems. You should probably create a different folder for it to keep it's files in and use --data-dir= to point it to that folder. It should at least sync, but don't trust it for anything yet. Hopefully this week I can look more into it.

BTW, did everyone notice the scratchpad got too large again for current miner software? Time to increase those buffers
newbie
Activity: 7
Merit: 0
If anyone wants to test out my latest db code, I have it at https://github.com/clintar/boolberry/tree/lmdb_scratch

you can get the branch with
Code:
git clone -b lmdb_scratch https://github.com/clintar/boolberry.git
then
Code:
mkdir -p build/release; cd build/release
cmake -DDATABASE=lmdb ../..
make -j4 daemon
should compile it, at least in linux. Let me know if it compiles or not at least! Smiley

I tried this branch. It compiled without problems. The produced binary started and created an initial db file of about 1 GB.

There is no file conversion yet from the "old" .bin format to lmdb format, so it wants to sync the blockchain from start, even with a blockchain file within reach, right? At least that was what it did on my system.

Sync immediately ran into problems however. I had repeated messages as follows:

Code:
2017-Aug-06 13:37:10.273809 [P2P3][193.70.85.9:10101 OUT]Block verification failed, dropping connection

These messages come from currency_protocol_handler.inl, line #377 (as checked out from GitHub today):

Code:
        if(bvc.m_verifivation_failed)
        {
          LOG_PRINT_CCONTEXT_L0("Block verification failed, dropping connection");
          m_p2p->drop_connection(context);
          m_p2p->add_ip_fail(context.m_remote_ip);
          return 1;
        }

Sync stuck forever at block 3 with repeated messages like this one:

Code:
2017-Aug-06 13:37:09.362602 [P2P7][193.70.85.9:10101 OUT]Sync data returned unknown top block: 3 -> 840955 [840952 blocks (1167 days) behind]

Is it supposed to be able to sync with "conventional" Boolberry nodes?
member
Activity: 94
Merit: 10
I have my block explorer up and running at http://explorer.mining.blue/en.
...

its great to have working block explorer again. thank you!
full member
Activity: 202
Merit: 104
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.
No, here is fine.
newbie
Activity: 7
Merit: 0
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

...

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

...

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.

Well, thanks for the fast repo update! I will have time to compile a new version from it and test probably this coming weekend.

But anyway: Yesterday I was running the daemon in a quick-and-dirty way on the non-standard port 50001, because of problems with port forwarding / NAT; today I switched to the standard 10101 port, and presto, no more "wrong network agent connected" messages. Maybe there is still a small bug somewhere that triggers when using --p2p-bind-port ...

By the way, is this forum here the right place to discuss such rather technical matters and problems? Maybe better to open issues on your GitHub repo for such things? Would be no problem for me.
full member
Activity: 202
Merit: 104
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?

Or still something not quite right with my new node?

Strange, I ran a release version of that all day and never got anything like that. I was going to edit this saying I updated the repo with some fixes. I thought I did before, but I guess not. Try it now.
newbie
Activity: 7
Merit: 0
I am new to Boolberry and in the process of setting up a full node. I am currently using a debug build of Clintar's db_changes branch on a recent Debian Linux. (I save testing the lmdb_scratch branch for later.)

It seems to run alright. I could sync the blockchain in less than a day, using the 5.9.44.154:10101 seed node that I found on the boolberry subreddit. I get new blocks and new transactions, and everything like current height is in agreement with the new blockchain explorer that went up yesterday (great work, by the way, congrats). Finally, other nodes can connect to my daemon; currently I have 4 incoming connections.

But one thing worries me: I get a lot of WRONG NETWORK AGENT CONNECTED! messages from the daemon, and after a while it even starts to ban ip's.

What is happening here? Boolberry nodes running outdated software versions getting rejected from my (hopefully) up-to-date daemon? Daemons of another Cryptonote currency trying to connect to my Boolberry node? Or other programs altogether that just happen to use the same ports as Boolberry?

Or still something not quite right with my new node?
full member
Activity: 202
Merit: 104
Ok, just an update on the explorer http://explorer.mining.blue/en. I got most things working now. I removed things we don't keep track of for this coin. Again, let me know of anything that looks to be wrong., but It should be pretty useful now. Have a great day!
sr. member
Activity: 505
Merit: 250
Activist Investor
both chainradar and minergate are down again

this shit again? are there any actual diagnostics on the network?

what are your daemons saying

1Block ya gonna help out again? You did say if the liquidity was there you would come back! If b4h4mu7 is serious about technical developments and has an active developer helping out we can bring some additional help and benefits for everyone.

exactly, its not out of the question! for now I'll just provide infrastructure where I can
sr. member
Activity: 868
Merit: 251
Dear all
I see Boolberry on Waves plateform!
It great for Boolberry
http://www.wavesgo.com/assets.html?3DH9QD9kzoUiDzHaFRos58WRW7zvg54ZTgUAcz7tSi1K
Thank you for this information,Do you know what information is there for DEV? :)After Delist on polo ,The community is not very active
Pages:
Jump to: