Happy,
Btw, I wanted to say you are definitely on the right track and what you explained is a good idea, and would almost work - that is to pull the core miner out of biblepay, and extend the X11 miner standalone EXE program to generate biblehashes, and modify the Web side of the Pool to accept biblehash as a solution, but there is one thing that I am trying to accomplish in BBP to keep it from growing into the run of the mill rat-race type greed system, where everyone just wants to spend money on hardware instead of running a full node: that is early on, I attempted to make the biblehash algo itself reference a historical tx in the chain, so that to run the biblepay miner, you had to run a full node (giving us network stability) by the hash algo itself exercising the ability to find historical chain info when reqd. More recently I settled on passing in things about the current and previous block into the miner, meaning that, the X11 standalone EXE would only be able to run a miner if we pass it those things - or if it is a fullnode it already knows those things. Thats good however, as it adds value to our full node network. (The question is do we want to add something in to make it impossible to run a standalone X11 miner? Im mostly against the standalone miner and Pro-full node hashing).
So I hope that explains why it would be more of a preferred choice for me to make the "standalone X11 bible miner" an extension of the qt clients capabilities (so as to future proof the algo cemented inside the wallet) - and then just write a web pool interface (OR, pull the X11 pool
web code first, that is sort of a 50-50).
Okay, I see what you mean. BibleHash uses the previous block's timestamp in generating the hash, and that information's not provided in a typical stratum job. That definitely raises the bar a little for creating a standalone miner, but not really something that would hamper any serious efforts. Your original historical transaction idea would probably be effective, if the transaction was somehow deterministically chosen using the block header hash similar to how you choose bible verses, since that would be something the pool couldn't determine prior to issuing jobs and each miner would have to retrieve itself for every BibleHash attempt thus requiring them to have access to the full blockchain.
I like the idea of integrating a pool miner with the wallet. It'd make BBP more accessible for users who aren't crypto enthusiasts.