BiblePay - New Coin Launch - Official Thread

[svirusxxx2]

http://biblepay.inspect.network/

I'm really not sure if the block explorer is correct or not. It's running 1.0.3.1 still until the mandatory updates get ironed out. I'm still having trouble getting 1.0.3.4 to sync properly on any of my rigs, so I don't have anything to cross-reference it with.

Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool.  Give me about 7 mins.

after that please show hash of block 7477

[bravetheheat]

I haven't seen the real innovation from this coin, nothing new and nothing really constructive.

And what's the relationship between religion and this coin, it seems that there is not explicitly relationship in it.

And the total amount of this coin is too many, the price would be really high.

[bible_pay]

I haven't seen the real innovation from this coin, nothing new and nothing really constructive.

And what's the relationship between religion and this coin, it seems that there is not explicitly relationship in it.

And the total amount of this coin is too many, the price would be really high.

"And the total amount of this coin is too many, the price would be really high."

This pretty much sums up that you made a worthless post. 

[jobetheminer]

I am now on Windows version 1.0.3.4 (64-bit) and when trying to update blockchain I am getting stuck on 2 days behind on block 7032.  Any suggestions?  Thank you!!

[maarekelets]

I haven't seen the real innovation from this coin, nothing new and nothing really constructive.

And what's the relationship between religion and this coin, it seems that there is not explicitly relationship in it.

And the total amount of this coin is too many, the price would be really high.

"And the total amount of this coin is too many, the price would be really high."

This pretty much sums up that you made a worthless post.  

Well I mean low CPU power mine-able deflationary cryptos that donate 10% of their value to sponsor the poor are really a dime a dozen /s

I am now on Windows version 1.0.3.4 (64-bit) and when trying to update blockchain I am getting stuck on 2 days behind on block 7032.  Any suggestions?  Thank you!!

I shutdown and deleted my banlist file in %appdata%/Biblepaycore/banlist.dat then restarted and had more luck getting the last 2 days

[jobetheminer]

I am now on Windows version 1.0.3.4 (64-bit) and when trying to update blockchain I am getting stuck on 2 days behind on block 7032.  Any suggestions?  Thank you!!

I'll let it run and see if it eventually updates, looks like it got a few more blocks.

[inblue]

Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool.  Give me about 7 mins.

Could you make this field on the pool display the correct version?



It's in About page and Home page

[emdes]

I am now on Windows version 1.0.3.4 (64-bit) and when trying to update blockchain I am getting stuck on 2 days behind on block 7032.  Any suggestions?  Thank you!!

Same happened here on a few PC's. Deleted the banlist and restarted the wallet worked for me

[x5650]

Wallet not syncing, stuck 2 hours behind. Restarted a few times and no luck.

[maarekelets]

Wallet not syncing, stuck 2 days behind. Restarted a few times and no luck.

Shutdown biblepay, delete your banlist file (in windows it's in %appdata%/Biblepaycore) and restart....see if that helps.

[jobetheminer]

Wallet not syncing, stuck 2 days behind. Restarted a few times and no luck.

Let it run, I've had mine running stuck on 2 days and its updating blocks slowly but surely.  I'm at 30 hours behind now.

[inblue]

Wallet not syncing, stuck 2 days behind. Restarted a few times and no luck.

Let it run, I've had mine running stuck on 2 days and its updating blocks slowly but surely.  I'm at 30 hours behind now.

That should mean you're on a fork and on the tip of the chain, so blocks are not being updated slowly, but are being mined on that chain. Otherwise, they would have been updated in a second.

[happy_merchant]

Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool.  Give me about 7 mins.

Everything seems to be syncing now and it looks like blocks are being mined.  Updating the block explorer now.

[bible_pay]

Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool.  Give me about 7 mins.

Could you make this field on the pool display the correct version?



It's in About page and Home page

Thats the Pool version, but it looks like we could use the wallet version , yeah, I think so...

[bible_pay]

Yeah, could be that node.biblepay.org is running the old version and the new version requires a protocol upgrade.
Let me upgrade that now, then the pool.  Give me about 7 mins.

Everything seems to be syncing now and it looks like blocks are being mined.  Updating the block explorer now.

Thanks!

[x5650]

All ok, up and mining 

[jobetheminer]

Wallet not syncing, stuck 2 days behind. Restarted a few times and no luck.

Let it run, I've had mine running stuck on 2 days and its updating blocks slowly but surely.  I'm at 30 hours behind now.

That should mean you're on a fork and on the tip of the chain, so blocks are not being updated slowly, but are being mined on that chain. Otherwise, they would have been updated in a second.

I'm updated and up and mining!  Thank you bible_pay!

[bible_pay]

Are we on the same chain now:


16:47:30

getblockhash 7480


16:47:30

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2


Two of mine agree now, the third is syncing.

[maarekelets]

Are we on the same chain now:


16:47:30

getblockhash 7480


16:47:30

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2


Two of mine agree now, the third is syncing.

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2 is my hash for 7480 for both my Windows and Linux nodes that I've upgraded so looks like I ended up on the right chain.

[remtiwk]

Are we on the same chain now:


16:47:30

getblockhash 7480


16:47:30

ac9f6a4cddcbdb04acbb6c117ac847f1ae1365da0878e714fb416a6ff6dff6c2


Two of mine agree now, the third is syncing.

I've got the same on mine.