I will update my upthread summary of top anonymity coins to note your advantage. But note your advantage doesn't really solve the scaling problem of one-time ring signatures.
When I said my enthusiam waned, I didn't mean to imply that you are not a capable programmer, because obviously you are. I meant that you are picking features to work out which don't really achieve the necessary level of functionality to unequivocally pull out in front of the rest of the coins. But I don't fault you for this, because most everyone else can't figure it out either. It is just that you are up against apparently a significant team of devs with Monero. I am not saying you couldn't pull a radical innovation out of your hat anything is possible.
Boolberry is not perfect, sure. Every coin have practical problems. But this is obviously that our project is technically stronger than any other CN coin, despite "significant team of devs with Monero". (nothing personal - i still like a few pretty nice persons from Monero )
The technically strong devs respect each other and will gravitate towards the winning technical solution. In theory every technically strong and extremely productive dev can be sufficiently rewarded with bounties, because the market is gargantuan if we solve the scaling problems and there is a lot to work on. I am sure most of us would love to work on changing the fundamental structure of the internet to turn back the corporate fascist takeover, e.g. facebook, google, yahoo. This we can fund from the coin that can scale.
Some silly name brainstorming off the top of my head:
Zoidberry
Mixberry
Moolaberry
Zeroberry
Nullberry
Moberry
Sieve <-- probably the best name I've thought of recently.
About your PoW hash, I am concerned there isn't enough entropy on the blockchain headers to prevent some trivial preimaging. I haven't had time to think deeply about it though, so no one should quote my concern as any thing more than an intuitive guess.
We don't use the whole header's data since it obviously not all of it is pseudo-random. For adding to scratchpad i use only:
* prev block id
* coin-base transaction's onetime key
* coinbase transaction's outs keys (xored with prev_id)
* blocks merkle hash
So i took only that data that seems to be maximum close to random.
(take a look into get_block_scratchpad_addendum(const block& b, std::vector& res) in src\currency_core\currency_format_utils.cpp: line 868)
My concern is this data is not any where near even 2^128 in entropy.
You can reduce the number of computed random lookups using this block chain header entropy, but my intuitive guess is you can't safely eliminate all the computation which increases the
apparent (i.e. easily knowable without cryptanalysis attack) entropy via confusion and diffusion[1]. So I think you need to reintroduce some computed lookups and only replace some of the computed lookups with the block header entropy. However, I haven't studied your PoW source code, so it might already apply confusion and diffusion to the block header input entropy.
[1]
http://en.wikipedia.org/wiki/Confusion_and_diffusion http://www.theamazingking.com/crypto-block.php