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

[btc-mike]

Are the developers working on fixing this difficulty re-targeting issue? It would be nice to know if they have the skills to fix this.

Diff/blockrate seems to have settled down nicely now - I expect it's just some big miners joining/leaving.

Seems no-one want to sell any BBR - anyone gonna put some lower sells up on the wtb/wts thread?

I'm interested to buy some BBR.

Boolberry trading thread

[1713943454]

1713943454

[1713943454]

1713943454

[crypto_zoidberg]

Hello.

2all who wondered what is going on: don't panic.
The problem is not in difficulty function. the function is fine.
The problem is that someone have pretty big part of hashrate and periodically turn on monster mining.

Probably someone have done optimized or GPU miner. Our scratchpad have dynamically increasing size, but it's still to small to resist GPU, and it's theoretically possible to implement GPU miner.

Miner optimization is endless story and i'm gonna focus development on improving usability now.

As soon as someone will share optimized or GPU hash i'll immediately include it into project repo with copyright. But i'm not expect those miners will hurry up to share it, it's a business.
So if some of devs want to support project with development - take care about hash optimization.
Good "luck".

PS: sorry if i'm not answering to PM, have a lot of task to do, will answer to all... or almost all.


FYI: Difficulty function can'n be changed after currency launch without hardfork. It's for any PoW currency.

[crypto_zoidberg]

I'm pleased to announce that btc-mike kindly offered his help with this project.

He started a thread for naming contest(yes, again) - please welcome.

[polocate]

Seemed very strong, and support the author!

[digicoin]

Are the developers working on fixing this difficulty re-targeting issue? It would be nice to know if they have the skills to fix this.

Look at the commits https://github.com/cryptozoidberg/boolberry/commits/master

[dr_chen]

Hello.

2all who wondered what is going on: don't panic.
The problem is not in difficulty function. the function is fine.
The problem is that someone have pretty big part of hashrate and periodically turn on monster mining.

Probably someone have done optimized or GPU miner. Our scratchpad have dynamically increasing size, but it's still to small to resist GPU, and it's theoretically possible to implement GPU miner.

Miner optimization is endless story and i'm gonna focus development on improving usability now.

As soon as someone will share optimized or GPU hash i'll immediately include it into project repo with copyright. But i'm not expect those miners will hurry up to share it, it's a business.
So if some of devs want to support project with development - take care about hash optimization.
Good "luck".

PS: sorry if i'm not answering to PM, have a lot of task to do, will answer to all... or almost all.


FYI: Difficulty function can'n be changed after currency launch without hardfork. It's for any PoW currency.

Anyway to solo mine together?

e.g. just open one demo, and use a miner or wallet to connect to the demo and integrate all the hashrates of different computers

this way run a demo on each computer and cannot integrate the hashrates

Code:

boolbd --start-mining=1Kec3ttzx1ahteNrjJaYBNgoiEDzK1bGJXh5wqvQ3keaAz1KbELR9nZVaJGhMMc25d99qs89k5uHof9F3Rns4e9qAau6LyZ --mining-threads=2

[prix]

How can i calculate the number of blocks per day?

Current difficulty is 53591178895.
I divide it by 60: 53591178895 / 60 = 893186315 h/s.
My hashrate is ~70 kh/s. My share per block is 70000 / 893186315 = 7.8e-5.
Then i multiply my share 7.8e-5 by the number of blocks per day 1440 = 0.11.
My per day block probability is 0.11 with 70kH/s.
Is it correct?

[fartbags]

Is it just me or is this coin messed up and not fixing itself?

On average I see blocks being found about 1 every 5 minutes.

[digicoin]

How can i calculate the number of blocks per day?

Current difficulty is 53591178895.
I divide it by 60: 53591178895 / 60 = 893186315 h/s.
My hashrate is ~70 kh/s. My share per block is 70000 / 893186315 = 7.8e-5.
Then i multiply my share 7.8e-5 by the number of blocks per day 1440 = 0.11.
My per day block probability is 0.11 with 70kH/s.
Is it correct?

user_hr = 70000
network_diff = 53591178895
block_per_day = (24 * 60 / 2) * user_hr / (network_diff / 120)
coin_per_day = block_per_day / 17.3

Code:

Python 3.3.5 (v3.3.5:62cf4e77f785, Mar  9 2014, 10:35:05) [MSC v.1600 64 bit (AM
D64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> user_hr = 70000
>>> network_diff = 53591178895
>>> block_per_day = (24 * 60 / 2) * user_hr / (network_diff / 120)
>>> coin_per_day = block_per_day / 17.3
>>> print(block_per_day)
0.11285439366522822
>>> print(coin_per_day)
0.006523375356371573
>>>
[code]

[/code]

[otila]

>>> coin_per_day = block_per_day / 17.3

Make that * 17.3

[prix]

Code:

0.11285439366522822

Yes, 2 min interval, not 1 as I have, but the same result.
Thanks.

[hornyPo]

Is this the effect of PoW-BCHAIN-BASED that the Hashrate is slowed down strongly?
First day i had 45kh/s, yesterday  40k and today 30k.
Pretty big differences.

What CPU ? Cache memory size ?

AMD Dual-Core 2.3 MHz, 2x512kB L2-Cache.

Itś about the smal cache?

[PhoneBloks]

Are the developers working on fixing this difficulty re-targeting issue? It would be nice to know if they have the skills to fix this.

Diff/blockrate seems to have settled down nicely now - I expect it's just some big miners joining/leaving.

Seems no-one want to sell any BBR - anyone gonna put some lower sells up on the wtb/wts thread?

I'm interested to buy some BBR.

Beware of keysersozeMC !!!

https://bitcointalk.org/index.php?topic=431099.msg6651813#msg6651813

[digicoin]

>>> coin_per_day = block_per_day / 17.3

Make that * 17.3

Yup, my mistake

[dbstmddhks]

My computer didn't find boolberry 

Pool is needed to get some Berrys!

[dbstmddhks]

Hello.

2all who wondered what is going on: don't panic.
The problem is not in difficulty function. the function is fine.
The problem is that someone have pretty big part of hashrate and periodically turn on monster mining.

Probably someone have done optimized or GPU miner. Our scratchpad have dynamically increasing size, but it's still to small to resist GPU, and it's theoretically possible to implement GPU miner.

Miner optimization is endless story and i'm gonna focus development on improving usability now.

As soon as someone will share optimized or GPU hash i'll immediately include it into project repo with copyright. But i'm not expect those miners will hurry up to share it, it's a business.
So if some of devs want to support project with development - take care about hash optimization.
Good "luck".

PS: sorry if i'm not answering to PM, have a lot of task to do, will answer to all... or almost all.


FYI: Difficulty function can'n be changed after currency launch without hardfork. It's for any PoW currency.

You say the "egalitarian distribution" is goal of cpu pow

but In my think someone (didn't know who he is) already getting everything.

it's most monopoly coin -_- this is business??

Even monero didn't lauch like this. Past some more days this coin will likes heavycoins

Someone already monopoly this coin~ warning!

[BorisTheSpider]

The problem is that someone have pretty big part of hashrate and periodically turn on monster mining.

Some of us have a big EC2 bill!!!!

Ps. It's not me, but I know some other people mining Boolberry.

[btc-mike]

Boolberry (HoneyPenny) Name Contest

Winning Name gets 125 BBR

https://bitcointalk.org/index.php?topic=618470.0

[Lordoftherigs]

what's the difference between this coin and Monero ?

http://www.monero.cc/

[btc-mike]

what's the difference between this coin and Monero ?

http://www.monero.cc/

1. Boolberry uses Wild Keccak algorithm while Monero uses CryptoNight. Here are the difference as noted in original post:

Main benefits of the Boolberry(boolberry.com) compared to Bytecoin(bytecoin.org ):

• Blockchain-based hash: unlike Bytecoin PoW hash, which works on 2MB scratchpad and takes avr 400 ms, new hash will work on blockchain random data to provide operation speed. It gives faster synchronization with network and immunity from DoS attacks.
• Transaction outs with guaranteed anonymity. An additional attribute for out is added: it can ONLY be used in the transaction with mixin level in ring signature not less than a given number. The feature is added to ensure the user’s anonymity of transactions ring signature over time.
• Alerts (signed by developers) broadcast via p2p mechanism, which will inform participants of the network of critical updates or other important events
• Donation-based crowdfunding: the project will not have premine, instamine or other unfair launch. The project has open and transparent model of project financing: part of the emission (1%) is reserved for the development of the project, BUT the rate of emission of these coins will be controled by network participants (miners) using votes.
  As a tribute to technology, we have fixed royalty percentage of donation, charged to the founders of Cryptonote.
• Removed dust from block reward - nice little thing to reduce weight of the blockchain transactions outs index.
• Wallet addresses aliasing: any wallet can be linked with symbolic name via special type extra record in coinbase. Blockchain will control registered names uniqueness.
• More rational emission curve
• Transaction identification by prefix: this feature will let us to cut off ring signatures from blockchain that under checkpoint - save space by 30-70%(depends of mixin usage)

2. Boolberry had a stable start with developer staying on board. Monero was started by a different developer as the coin Bitmonero. The Bitmonero dev was not online for several days and some devs forked the code, giving it the name Monero. The Bitmonero dev returned shortly after and continues to develop under bitmonero name. The Bitmonero dev made commits today on GitHub. Monero and Bitmonero are currently on the same blockchain and effectively the same coin BUT this cannot be guaranteed in the future due to different dev groups working on different code bases.