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

IntroVert

full member

Activity: 265

Merit: 119

Quote from: 33zer0w0lf on June 13, 2014, 07:18:20 PM

Now, thanks to DGA and his improved version of simpleminer, it appears mining with pools is now viable for this coin. Wanted to share with everyone the features of Extreme Pool.

Extreme Pool - New and Improved!

Features
•2% Fee
•Longpolling Enabled on http ports (Disabled for BBR)
•Payouts after 60 block confirmations
•Latest pool code
•Variable Difficulty based on your individual CPU performance (Adjusted for BBR based on DGA's and my tests)
•Verified Secure
•Dedicated Staff
•Exceptional Support

Extreme Pool currently offers a pool for every cryptonote coin, including Boolberry.

We are constantly working with all the communities to provide whatever services need to be provided, from testing functionality to setting up bounties!

Visit us at http://www.extremepool.org
Email us @ [email protected]
Talk to us on IRC, Server Freenode, channel #extremepool or #boolberry

Hope to mine with you soon!

So, I am one of the 12 miners on your pool, been mining for the past three days and I am likely the one with lowest hashrate. Is it possible that a link to the improved Win64 simpleminer executable is provided either on your pool or here? I have no way to build the binary...

33zer0w0lf

full member

Activity: 224

Merit: 100

Now, thanks to DGA and his improved version of simpleminer, it appears mining with pools is now viable for this coin. Wanted to share with everyone the features of Extreme Pool.

Extreme Pool - New and Improved!

Features
•2% Fee
•Longpolling Enabled on http ports (Disabled for BBR)
•Payouts after 60 block confirmations
•Latest pool code
•Variable Difficulty based on your individual CPU performance (Adjusted for BBR based on DGA's and my tests)
•Verified Secure
•Dedicated Staff
•Exceptional Support

Extreme Pool currently offers a pool for every cryptonote coin, including Boolberry.

We are constantly working with all the communities to provide whatever services need to be provided, from testing functionality to setting up bounties!

Visit us at http://www.extremepool.org
Email us @ [email protected]
Talk to us on IRC, Server Freenode, channel #extremepool or #boolberry

Hope to mine with you soon!

crypto_zoidberg

hero member

Activity: 976

Merit: 646

Quote from: dga on June 13, 2014, 02:25:58 PM

Ahh, thanks! I've committed a fix for this into my repository and added it to the pull request to the master.

(it's a one line change if you want to update and try it)

Merged!
Sorry for delay

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: cubydu on June 13, 2014, 04:53:56 PM

Pool http://79.135.200.108/ returned with great hash rate - 10 MH/s!

Come on guys we can find many blocks together

11 MH/S now! Roll Eyes

+ 1 block

33zer0w0lf

full member

Activity: 224

Merit: 100

We are hitting blocks at http://bbr.extremepool.org

cubydu

sr. member

Activity: 308

Merit: 250

Pool http://79.135.200.108/ returned with great hash rate - 10 MH/s!

Come on guys we can find many blocks together

btc-mike

hero member

Activity: 938

Merit: 1001

Quote from: 33zer0w0lf on June 13, 2014, 04:42:47 PM

Extreme Pool hashrate rising steadily. should hit 6MHs here in a second!

DGA's new simpleminer is working great so far!
http://bbr.extremepool.org

how do i just compile simpleminer? i know i can get just boolbd with just this:

Code:

rm -rf build; mkdir -p build/release; cd build/release; cmake -D STATIC=ON  -D CMAKE_BUILD_TYPE=Release ../..; make daemon

33zer0w0lf

full member

Activity: 224

Merit: 100

Extreme Pool hashrate rising steadily. should hit 6MHs here in a second!

DGA's new simpleminer is working great so far!
http://bbr.extremepool.org

33zer0w0lf

full member

Activity: 224

Merit: 100

Quote from: cubydu on June 13, 2014, 03:54:39 PM

Quote from: Anotheranonlol on June 13, 2014, 02:48:37 PM

Quote from: dga on June 13, 2014, 12:40:46 PM

Btw - we (extremepool, lucasjones, and i) just figured out one of the sources of slowdowns -- pool owners should leave long polling *disabled* for now.

I'll get a patch out next week to enable it in the miner.

The hashrate people are seeing on extremepool should go up by 2-4x now. Combined with the new miner update, that should get a lot more blocks flowing from the pools.

Great work. I've updated to your latest commit and can report increased performance.
we have one pool down, one pool that's never found a block Huh

, & one pool in maintenance mode. . I hope for now most users will simply pick one because it's crazy to earn less on pool than solo and 3 days for a last block on a multi MH pool is surreal

I run new pool at 30 minutes. With big pool hashrate

http://pastebin.com/q0Cd1uE8

anyone know how to solve the libboost linking problem I seem to be having?

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: Anotheranonlol on June 13, 2014, 02:48:37 PM

Quote from: dga on June 13, 2014, 12:40:46 PM

Btw - we (extremepool, lucasjones, and i) just figured out one of the sources of slowdowns -- pool owners should leave long polling *disabled* for now.

I'll get a patch out next week to enable it in the miner.

The hashrate people are seeing on extremepool should go up by 2-4x now. Combined with the new miner update, that should get a lot more blocks flowing from the pools.

Great work. I've updated to your latest commit and can report increased performance.
we have one pool down, one pool that's never found a block Huh

, & one pool in maintenance mode. . I hope for now most users will simply pick one because it's crazy to earn less on pool than solo and 3 days for a last block on a multi MH pool is surreal

I run new pool at 30 minutes. With big pool hashrate

Anotheranonlol

hero member

Activity: 588

Merit: 504

Quote from: dga on June 13, 2014, 12:40:46 PM

Btw - we (extremepool, lucasjones, and i) just figured out one of the sources of slowdowns -- pool owners should leave long polling *disabled* for now.

I'll get a patch out next week to enable it in the miner.

The hashrate people are seeing on extremepool should go up by 2-4x now. Combined with the new miner update, that should get a lot more blocks flowing from the pools.

Great work. I've updated to your latest commit and can report increased performance.
we have one pool down, one pool that's never found a block Huh

, & one pool in maintenance mode. . I hope for now most users will simply pick one because it's crazy to earn less on pool than solo and 3 days for a last block on a multi MH pool is surreal

dga

hero member

Activity: 737

Merit: 511

Quote from: cubydu on June 13, 2014, 02:00:50 PM

Quote from: dga on June 13, 2014, 11:38:00 AM

Hi, all - I've committed to my personal branch a substantial improvement to simpleminer's efficiency with multiple threads.

I'd appreciate it if a few folks could test it and make sure it works on several pools before I submit it as a pull request to crypto_zoidberg.

https://github.com/dave-andersen/boolberry/commit/a687c341fbcef5cd55372a5e12743b49e2871c92

This takes my i7-4770 up to about 400kh/s, from yesterday's 320kh/s, when running to a pool on the same machine.

If this is solid, then the next step on the roadmap will be to improve performance when dealing with pools that are responding a little more slowly. There are a few things I can do there, but they're a bit more invasive yet.

Let me know and I'll submit it this evening if it's not breaking.

update: It seems stable enough given the fairly low amount of hashrate on the current pools. I've submitted a pull request to the main repository for these upgrades. Once they're in, I'd suggest people try them out, but please keep an eye out for any bugs and let me know.

Sometimes get message

Code:

2014-Jun-13 20:59:31.033116 ERROR /root/boolberry/contrib/epee/include/storages/http_abstract_invoke.h:112[bool epee::net_utils::invoke_http_json_rpc(const string&, const string&, t_request&, t_response&, t_transport&, unsigned int, const string&, const string&) [with t_request = mining::COMMAND_RPC_SUBMITSHARE::request; t_response = mining::COMMAND_RPC_SUBMITSHARE::response; t_transport = epee::net_utils::http::http_simple_client; std::string = std::basic_string]]RPC call of "submit" returned error: -1, message: Duplicate share

Ahh, thanks! I've committed a fix for this into my repository and added it to the pull request to the master.

(it's a one line change if you want to update and try it)

cubydu

sr. member

Activity: 308

Merit: 250

Quote from: dga on June 13, 2014, 11:38:00 AM

Hi, all - I've committed to my personal branch a substantial improvement to simpleminer's efficiency with multiple threads.

I'd appreciate it if a few folks could test it and make sure it works on several pools before I submit it as a pull request to crypto_zoidberg.

https://github.com/dave-andersen/boolberry/commit/a687c341fbcef5cd55372a5e12743b49e2871c92

This takes my i7-4770 up to about 400kh/s, from yesterday's 320kh/s, when running to a pool on the same machine.

If this is solid, then the next step on the roadmap will be to improve performance when dealing with pools that are responding a little more slowly. There are a few things I can do there, but they're a bit more invasive yet.

Let me know and I'll submit it this evening if it's not breaking.

update: It seems stable enough given the fairly low amount of hashrate on the current pools. I've submitted a pull request to the main repository for these upgrades. Once they're in, I'd suggest people try them out, but please keep an eye out for any bugs and let me know.

Sometimes get message

Code:

2014-Jun-13 20:59:31.033116 ERROR /root/boolberry/contrib/epee/include/storages/http_abstract_invoke.h:112[bool epee::net_utils::invoke_http_json_rpc(const string&, const string&, t_request&, t_response&, t_transport&, unsigned int, const string&, const string&) [with t_request = mining::COMMAND_RPC_SUBMITSHARE::request; t_response = mining::COMMAND_RPC_SUBMITSHARE::response; t_transport = epee::net_utils::http::http_simple_client; std::string = std::basic_string]]RPC call of "submit" returned error: -1, message: Duplicate share

33zer0w0lf

full member

Activity: 224

Merit: 100

Extreme Pool
I have worked with DGA and our BBR pools seems to be working much better now, and his miner also as a significant increase in hash.
Join us @ http://bbr.extremepool.org

dga

hero member

Activity: 737

Merit: 511

Btw - we (extremepool, lucasjones, and i) just figured out one of the sources of slowdowns -- pool owners should leave long polling *disabled* for now.

I'll get a patch out next week to enable it in the miner.

The hashrate people are seeing on extremepool should go up by 2-4x now. Combined with the new miner update, that should get a lot more blocks flowing from the pools.

sottymax

newbie

Activity: 18

Merit: 0

foolberry sucks. get some real anonymous power.

33zer0w0lf

full member

Activity: 224

Merit: 100

Quote from: dga on June 13, 2014, 11:38:00 AM

Hi, all - I've committed to my personal branch a substantial improvement to simpleminer's efficiency with multiple threads.

I'd appreciate it if a few folks could test it and make sure it works on several pools before I submit it as a pull request to crypto_zoidberg.

https://github.com/dave-andersen/boolberry/commit/a687c341fbcef5cd55372a5e12743b49e2871c92

This takes my i7-4770 up to about 400kh/s, from yesterday's 320kh/s, when running to a pool on the same machine.

If this is solid, then the next step on the roadmap will be to improve performance when dealing with pools that are responding a little more slowly. There are a few things I can do there, but they're a bit more invasive yet.

Let me know and I'll submit it this evening if it's not breaking.

testing now I will report back shortly.

dga

hero member

Activity: 737

Merit: 511

Hi, all - I've committed to my personal branch a substantial improvement to simpleminer's efficiency with multiple threads.

I'd appreciate it if a few folks could test it and make sure it works on several pools before I submit it as a pull request to crypto_zoidberg.

https://github.com/dave-andersen/boolberry/commit/a687c341fbcef5cd55372a5e12743b49e2871c92

This takes my i7-4770 up to about 400kh/s, from yesterday's 320kh/s, when running to a pool on the same machine.

If this is solid, then the next step on the roadmap will be to improve performance when dealing with pools that are responding a little more slowly. There are a few things I can do there, but they're a bit more invasive yet.

Let me know and I'll submit it this evening if it's not breaking.

update: It seems stable enough given the fairly low amount of hashrate on the current pools. I've submitted a pull request to the main repository for these upgrades. Once they're in, I'd suggest people try them out, but please keep an eye out for any bugs and let me know.

onemorebtc

sr. member

Activity: 266

Merit: 250

Quote from: cbuchner1 on June 13, 2014, 05:30:28 AM

Quote from: baigreen on June 13, 2014, 04:24:31 AM

Quote from: sdersdf2 on June 13, 2014, 03:32:28 AM

I realise you have a very full plate, but are there any plans to make it easier for people to transfer their coins between exchanges? What are your thoughts on this?

That is the cryponote coin's reason.
All cryponote coins are all like this, need pay id.

Not sure if this is already planned or not: I think a good cryptonote GUI wallet should assist you in storing payment IDs in some kind of address book. They key to the address book database should not just be the destination address, but rather destination address + payment ID. This is so you can have multiple entries e.g. for poloniex for depositing coins to multiple accounts.

Christian

a payment id is more a message than an id. poli changes them frequently.

afaik the only reason exchange requires a paymentid is because the cn-daemons are not optimized and get very slow with many addresses.

this could be solveable

cbuchner1

hero member

Activity: 756

Merit: 502

Quote from: baigreen on June 13, 2014, 04:24:31 AM

Quote from: sdersdf2 on June 13, 2014, 03:32:28 AM

I realise you have a very full plate, but are there any plans to make it easier for people to transfer their coins between exchanges? What are your thoughts on this?

That is the cryponote coin's reason.
All cryponote coins are all like this, need pay id.

Not sure if this is already planned or not: I think a good cryptonote GUI wallet should assist you in storing payment IDs in some kind of address book. They key to the address book database should not just be the destination address, but rather destination address + payment ID. This is so you can have multiple entries e.g. for poloniex for depositing coins to multiple accounts.

Christian

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