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.

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.

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.

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.

i think guys we have a GPU miners there.

if someone is ready to share his GPU miner, or ready to implement it - i will put sources  to project repo with copyright and put respect here.

i guess until someone have a pretty big part of hash rate he could swing difficulty of any smoothness.

This situation is the pest prove that even if optimized hash exists it is note produced by developer, since he would not be shake his own network.

It changes with slight delay about 100-200 blocks.
Difficulty calculated on last 720 block's timestamps(DIFFICULTY_WINDOW), but it begins to react already after the 60 blocks.

Seems that block have absolutley wrong PoW hash.
how often does this happen?

1. No premine. 1% of money supply reserved for devs but emission of this reservation is smooth, the same curve as supply emission, and it controled votes in blocks (each block have a vote).
2. Formula:
But, reward is depends on block cumulative size also, take a look details on website: http://boolberry.com/index.html#reward

Difficulty will go to sky....

Hash check is much easier than on bytecoin/monero. You just need to use another protocol with incremental delivering scratchpad to client.

I've expected this thesis when you asked about case)
May be, but it's to late to change it.
The only thing i can do is to add soft rule in client software, to protect from unintended taking some case-related alias.
But if someone is going to do it intentionally, he is able to do it.

FOLK, i strongly suggest you to map aliases in lower case, since we going to make default wallet prefer low case aliases in transfers commands, to avoid confusion and cheats.

Good news!

I''ve added HowTo section http://boolberry.com/howto.html and put detailed specification of the coin to website and announce.
Feel free to PM me if you found some mismatch or mistakes(including english).

And i want to ask seriously, where is the bug reports ?
Please take a look, it is in our mutual interests to find a bugs now, until we went too far.

Peace!

Sorry about this man, i'll help with pool protocol and thin miner to anyone who would have serious intentions to make pool.

Can you explain about 3 sec ?

Yes you can, if you prove that you own this address (sign missage with address private key).
Updating implemented in core, and in tests. But have not implemented in command line interface. I think we'll done this in UI.
Alias case sensitive.

Done.

I've cut off simpleminer since we have pretty different approach with PoW hash(blockchain-based pow), i'll support those who start developing pools with protocol implementation for thin miner.

DON'T USE libboost 1.54
Thank you to point this, i've updated readme and cmakelists.