BiblePay - New Coin Launch - Official Thread

[GoodLad]

Do you have an official whitepaper?

[ste1]

I can't login to my pool account!

[bible_pay]

Do you have an official whitepaper?

Go ahead and put a ticket in for it and assign to me for escalate.

[bible_pay]

Here you go, here is some relevant pool info here:

http://forum.biblepay.org/index.php?topic=2.new#new

[seasonw]

I noticed that pool has changed user interface, it is much better compared to version 1 

And I also noticed the pool's load always less than 10% after cloudflare implementation. Pool is quite stable now.

BTW, I cannot find transaction history in new UI, am I overlook?

[bible_pay]

I noticed that pool has changed user interface, it is much better compared to version 1 

And I also noticed the pool's load always less than 10% after cloudflare implementation. Pool is quite stable now.

BTW, I cannot find transaction history in new UI, am I overlook?

Thanks.

Yeah, it is missing!  You can temporarily access it from pool2.biblepay.org.

I will add it now, and update you asap.

[616westwarmoth]

What exactly is happening at f7000?

F7000 (block 7000) the underlying algo base will transition from its provisional state (now) where it is a combination of X11 and the dev's own "Proof of BibleHash" (in simple terms,  crypto based on hashing the King James Version of the Bible).  It will transition to a final state where the only algo is the Proof of Biblehash.  Basically the final (big) tweak to the underpinning of the coin.  The other big sign on the road map is Masternodes (or "Sanctuaries") which will be implemented at the end of the year.

Thanks for explanation! I wonder what the new hashrates will be

You could test your rate in the testnet (it was using the block 7000 underpinnings).  In general you'll see a tremendous drop.  But keep in mind, so will everyone else, and in the end it should all be pretty relative after 7000 as it was before.

[616westwarmoth]

But we are getting hard to find a block per day now, I see that we can't even get 205 blocks per day recently, so I was wondering will we still have 1.4billion in the 1st year.

If you look at the overall rate of expected blocks, we're pretty much right on target (well, we were when I ran the numbers this morning).

How are we right on target? Last GMT day (September 2, 00:00-23:59) there were only 141 blocks instead of the expected 205. You can check in the block explorer that the first block for the day was 5729 and the last one was 5870.

And every day is similar, you can continue going to the past like this to check, or you can simply divide the total number of blocks found (currently 5922) by the total number of days (currently 41 and a half) and you'll get the average of: 5922 / 41.5 = 142.7 blocks per day. Not only is it way off from the 7 minute block time (205 blocks per day, so almost a third of the blocks are missing), it's also suspiciously close to the 10 minute block time which is 144 blocks per day.

Numbers don't lie, but some are dismissing the possibility that something is wrong and that this must be "temporary luck", that in the long term it will be 205 blocks/day or 1 block/7 minutes. But there's never been a day with more than 205 blocks for it to be a normal averaging variance, it's always less than even 165 or so. We'll see how things will change with f7000.

Addendum: to acknowledge how impacting this is to the coin and the total supply calculations, if it had 205 blocks per day, we would have a total of 657M coins by 01.01.2018, but the reality is that we will have 458M coins instead, so almost 200M less. At least at this rate, but I expect changes after block 7000.

Btw, I'm a hodler, so I'm totally fine with this situation. I'm just putting the numbers down.

I wasn't trying to mislead anyone, I did run the numbers the other day, but obviously was in error.   We'll see how it pans out after block 7000, but your numbers are spot on.

[bible_pay]

I noticed that pool has changed user interface, it is much better compared to version 1 

And I also noticed the pool's load always less than 10% after cloudflare implementation. Pool is quite stable now.

BTW, I cannot find transaction history in new UI, am I overlook?

Ok TxHistory is present now under reports.

[Cryptoby]

This coin is an interesting idea   ...

... I like it ... I think I have to watch this project   ...

Can I mine it with a laptop or is it not possible?

[seasonw]

Ok TxHistory is present now under reports.

Cool, I got it under reports category now

[seasonw]

This coin is an interesting idea   ...

... I like it ... I think I have to watch this project   ...

Can I mine it with a laptop or is it not possible?

Yes, this coin has a bright future.

And you are able to mine with your laptop's CPU, but you have to observe your CPU temperature, ensure it is not over heat. Actually, mining with laptop is not really recommended.

[calxibe]

After the launch of the new design at http://pool.biblepay.org/ it isn't possible to log in.

It says "Invalid Username or Password", but i know for certain that it's the same password as i had last night (and it works at http://pool2.biblepay.org), can it be the symbols inside pwd maybe?

[ste1]

It uses only 40% of my CPU 6600K. Set to 4 threads. Can I mine more?

[bek77]

It uses only 40% of my CPU 6600K. Set to 4 threads. Can I mine more?

how many coins do you mine?

[bek77]

There are faucet or baunty?
pos is possible? and what %?

[ste1]

It uses only 40% of my CPU 6600K. Set to 4 threads. Can I mine more?

how many coins do you mine?

89717.43   Hashes Per Second

[HODL_guy]

This coin is the hidden diamond among all the shitcoins on this forum. I hope not too much ppl will mine it at an early stage.

[bek77]

It uses only 40% of my CPU 6600K. Set to 4 threads. Can I mine more?

how many coins do you mine?

89717.43   Hashes Per Second

in add worker the page in in ERROR... why?

[ste1]

It uses only 40% of my CPU 6600K. Set to 4 threads. Can I mine more?

how many coins do you mine?

89717.43   Hashes Per Second

in add worker the page in in ERROR... why?

What? I  don't see an error.