Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 466. (Read 1210753 times)
Is the new version already released?, including binaries?
Some fresh news, to keep all informed.
1. Fixed bug in displaying hashrate while mining is turned off
2. Implemented stricted alias check in wallet (http://boolberry.com/howto.html#aliases)
3. Updated miner to work all threads on one shared scratchpad (begins to make sense in the nearest future)
4. Fixed problem with dead connecions (it was seen on this graph)
Now it's fine.
And also it could be seen as this problem:
6. Problem with stuck transactions in tx pool investigated, not solved yet. I wrote some recomendations how to avoid this problem.
All the bests!
1. Fixed bug in displaying hashrate while mining is turned off
2. Implemented stricted alias check in wallet (http://boolberry.com/howto.html#aliases)
3. Updated miner to work all threads on one shared scratchpad (begins to make sense in the nearest future)
4. Fixed problem with dead connecions (it was seen on this graph)
Now it's fine.
And also it could be seen as this problem:
I get a error on Ubuntu 13.10 in the daemon
Let me know if this will apear again with new version.Code:
2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32
6. Problem with stuck transactions in tx pool investigated, not solved yet. I wrote some recomendations how to avoid this problem.
All the bests!
Code:
2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32
That should be moved to log level 2 .. don't worry about it.
good point!I've just fixed one bug that made this messages apeared frequently.
I see transaction with about 450BBR that stuck in memory pools(and two other transactons also).
The problem is in fee.
Wallet use just default hardcoded fee(and here is problem actually).
At the other hand daemon's transaction pool use "greedy" policy to collect transactions into block - and this transaction not fits to this conditions (it depends of fee/tx_size ratio).
To solve this problem we need to improve wallet to set fee up to current tx_pool state, to have fee/tx_size ratio enough to be included in block.
It will be implemented soon, but for current version - i strongly recomend you to send big amount with few small transfers not bigger than 100BBR
Senders of those transactions can PM me, i'll try to help with this issue.
The problem is in fee.
Wallet use just default hardcoded fee(and here is problem actually).
At the other hand daemon's transaction pool use "greedy" policy to collect transactions into block - and this transaction not fits to this conditions (it depends of fee/tx_size ratio).
To solve this problem we need to improve wallet to set fee up to current tx_pool state, to have fee/tx_size ratio enough to be included in block.
It will be implemented soon, but for current version - i strongly recomend you to send big amount with few small transfers not bigger than 100BBR
Senders of those transactions can PM me, i'll try to help with this issue.
Code:
2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32
That should be moved to log level 2 .. don't worry about it.
I get a error on Ubuntu 13.10 in the daemon
and then a lot of red output.
...
in the Monero thread someone have the same problem.
e.g.:
https://bitcointalk.org/index.php?topic=583449.msg6559881;topicseen#msg6559881
Code:
2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32
and then a lot of red output.
Code:
2014-Mai-21 23:28:58.465427 [P2P3] ERROR /home/user/boolberry/contrib/epee/include/...
in the Monero thread someone have the same problem.
e.g.:
https://bitcointalk.org/index.php?topic=583449.msg6559881;topicseen#msg6559881
Good roadmap. GUI and database are very needed features. Hopefully the "Nice GUI" is much nicer than Bitcoin-qt!
IMPORTANT NOTICE
Aliases now have restricted to this alowed characters:
I'm very sorry to all who already assigned some extra symbols.
This is made to protect your aliases from "pfishing" or confusing cheats.
For example if there some well-known @goodpool alias, i want to make this name safe from same-looking names like @Goodpool or @goodpóól, or @goodpoo|.
I'll be back when i finish current developent iteration, with short description of what is done.
Good "luck".
Your Zoidberg.
Aliases now have restricted to this alowed characters:
Code:
#define VALID_ALIAS_CHARS "0123456789abcdefghijklmnopqrstuvwxyz-."
I'm very sorry to all who already assigned some extra symbols.
This is made to protect your aliases from "pfishing" or confusing cheats.
For example if there some well-known @goodpool alias, i want to make this name safe from same-looking names like @Goodpool or @goodpóól, or @goodpoo|.
I'll be back when i finish current developent iteration, with short description of what is done.
Good "luck".
Your Zoidberg.
WTB 2000 BBR @ 0.001 BTC (you send first or escrow)
1. Boolberry uses Wild Keccak algorithm while Monero uses CryptoNight. Here are the difference as noted in original post:
Quote
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.
Boolberry (HoneyPenny) Name Contest
Winning Name gets 125 BBR
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.
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.
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!
My computer didn't find boolberry 
Pool is needed to get some Berrys!
Pool is needed to get some Berrys!
>>> coin_per_day = block_per_day / 17.3
Make that * 17.3
Yup, my mistake
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?
Beware of keysersozeMC !!!
https://bitcointalksearch.org/topic/m.6651813
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.
AMD Dual-Core 2.3 MHz, 2x512kB L2-Cache.
Itś about the smal cache?
Code:
0.11285439366522822
Thanks.
>>> coin_per_day = block_per_day / 17.3
Make that * 17.3
Jump to: