Whew, was starting to sweat there.

It looks like we rolled past block 37, so the rule worked.

So when that happens, it spams the debug.log, and slows down the mining (exacerbating the actual issue).

Ill remove the spam tomorrow also while working on the miner.

Thanks, the airdrop Is a good idea, and also a faucet would be nice.  I am up for contributing a few hundred $ for part of the airdrop, but I have to look into how that is done technologically.

Hi Viking,

So looking at this a little closer, I see the difficulty rose quickly over the last 4 blocks from 34-37 and we are due for a retarget.
I dont think the blockchain is out of sync, I think the diff is rather high since 5 people dropped off.

Let us not fear, this coin has a feature where if the chain gets stuck for more than one hour, the diff will decrease by 75%.  So in about 3 minutes we should be able to solve this block and roll again.

Guys- it mines fine on windows and linux (Im running one wallet on each node) and have mined a few blocks out of our 30.
Remember with 7 minute blocks, it could take a few hours to generate a block with 19 miners running right now (at least 19 are connected to the external node).  So please have patience.

As far as pegging the processor, tomorrow, I will look into modifying the code to max out all cores - I see in the bitcoinminer they do allow you to start one thread per core, so we will try that together tomorrow afternoon.

Try restarting wallet Cherry, then setgenerate over again, and also while it is re-running again, click Tools | Info | Open and scan debug log to see if miner crashed.  I havent heard of it yet, but it could say something like biblepayminer thread exiting etc.

Check out miner.cpp, the miner basically consumes one thread, and constantly hashes about 65535 times and then sleeps for a couple milliseconds then starts over with a new nonce.  I really cant answer this exactly today, because CPUs have different core sizes and OSs might cause processes to sleep between thread interrupts etc.  I suppose we will need to address this in a way where we allow the user to run the miner on all cores and consume as much processor as possible- Im all for being as fair as possible but I can assure you everyone is running the same miner. 

Just got a message in the BiblePay inbox (contact@biblepay.org) that someone is running this on his sons AlienWare, so that is good news also.

You can still solo mine since the diff is so low.

That brings up an interesting point - should we support pools?  For now, if someone wants to write a pool, you are welcome to go for it  .



Blocks mature at height N+100.

Thats the block size, the reward is still 20,000.  It would only be 1,000 if Diff was much much higher and block solve times much lower than normal.

Yes sir.

Also your blocks match my blocks.

Others: you can do the 'getgenerate' also to see if you are mining.

From the Debug | RPC Console | type "setgenerate true"
The gen=1 is for the .conf file.


Node.biblepay.org has 18 connections, so we are getting more popular!


Addnode:

addnode node.biblepay.org

To test the node from windows command line:

telnet node.biblepay.org 40000

There was once a NYC school IT technician that loaded BTC on hundreds of PCs, so I suppose it could be, but of course do not condone it.

The %appdata%\biblepaycore\biblepay.conf file must contain "gen=1" and be restarted, or alternatively, type setgenerate true from the rpc.

To verify you are mining, do a 'getgenerate'

So I spoke to Yuri from CCEX the other day, and he said he would list us on the exchange free of charge since we are a charitable org.

I will contact him again in a few days, and shoot for roughly the beginning of August for an exchange go live.

You can either leave the wallet running with gen=1 set in the config, or you can run the BiblePay headless daemon (biblepayd.exe).

The lead dev is not sure if he wants to unmask yet.

The block reward is 20,000 BBP as long as the duration between blocks stays around 7 mins (if solved too fast, the reward is lower).
Yes, you have to run a full node in order to run the algo.  You can run the full node on linux or windows (wallet is at biblepay.org in downloads).

(Mac still requires self-compiling at this stage).

That is just because difficulty is very low (< .0005) with only 5 of us or so online.  The POB algo will get harder as the bar is raised.


Usefulness of Coin:
The coin helps sponsor orphans, but attracts investors since we are deflationary.

On the wallet connection:
telnet node.biblepay.org 40000
(We are on port 40000, looks like it is working, please try manually adding the node with addnode node.biblepay.org?) (Shouldnt have to).

Next:

What is diference PROOF OF BIBLEHASH with pow or pos:
POB is a flavor of POW, but since the algorithm contains all 31000 bible verses, it would be a feat to port it to an asic (since the results are md5 chained and encrypted), so it keeps the full nodes hashing on PCs, and keeps the energy consumption down.

Next:

May I use this coin if I'am atheist?  Grin

LOL, Yes of course.  As a community I hope we can help convince you that God exists (I am not starting a war, so please take that in a positive way).

Algo: BibleHash Algorithm (PC Only, no ASICs or GPUs)

Wallet Binary:  www.biblepay.org

Source: See OP Page 1 Post

Pow/Pos:  POW only, through BibleHashAlgo (No POS later)