BiblePay - New Coin Launch - Official Thread

[bible_pay]

I noticed that ccex still has its wallet enabled. Something that worries me is that they're reporting that their block height is 7193 and the pool is at 7223 right now

Thanks, I sent him a reminder email (ticket still open).

[maarekelets]

So auditing the pools activity since block 7000, we had One block (7143) that appeared on the surface to be paid @ 0.
This block was orphaned, the pool didnt get it.  I deleted the records for it.

You can verify this by typing : run subsidy 7143.  The pools address is  the one found on 7139 (b6j). 
I dont see any other discrepencies (other than wildly fluctuation hashes due to people dropping in/out of the pool etc). 

It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.

[bible_pay]

So auditing the pools activity since block 7000, we had One block (7143) that appeared on the surface to be paid @ 0.
This block was orphaned, the pool didnt get it.  I deleted the records for it.

You can verify this by typing : run subsidy 7143.  The pools address is  the one found on 7139 (b6j). 
I dont see any other discrepencies (other than wildly fluctuation hashes due to people dropping in/out of the pool etc). 

It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.

Part of the problem was we were banning each other, now the supermajority is taking over again, possibly, God willing.

I dont want to say too much and jinx us.  In the morning lets -reindex and resync a few nodes and verify we didnt store any bad blocks etc.

[bitcoinsrule01]

Nothing is working for me...1.0.2.7, 1.0.2.9, or 1.0.3.1

the wallet will show that I am hashing but the pool show me doing nothing.

same here..

Same. No hashrate on the pool and a 10X decrease in reported hashrate from the wallet.

Wouldn't hurt so bad that its not working if I didn't see a huge hashrate on the network. A few are benefiting that's for sure! It's working for some.

A few may be benefiting...but please remember the most that benefit are the orphans and their families that this project supports and reinforces.  The developer is working HARD to get the issues under control.  

It was expected because of the algorithm change.  

Maybe in hindsight just a code change to automatically change block payout and the percentage of the payout to the  cause of donations that this project supports.

While that may seem good...the purpose was to change the algorithm to make it stay resistant to GPU and ASIC...as far as I know.

This "hiccup" is only temporary.  Like I said before....it will be stable again.  I look forward to that.  However sooner or later that may come.

This developer is the most active and understanding of our criticism that I have ever encountered!!!!!!!!

One thing I am not sure of...Are you the only one really running the day to day operations of all of this AWSEOME project?

First off I in no way meant any disrespect to the Admin or the the teams efforts to make this project a reality! I appreciate their hard work and dedication to this project and I wish it nothing but success. These children can use all the help they can get. I said what I did in an attempt to point out an unequal distribution in the network. It was not meant to be anything more or less.

[maarekelets]

So auditing the pools activity since block 7000, we had One block (7143) that appeared on the surface to be paid @ 0.
This block was orphaned, the pool didnt get it.  I deleted the records for it.

You can verify this by typing : run subsidy 7143.  The pools address is  the one found on 7139 (b6j). 
I dont see any other discrepencies (other than wildly fluctuation hashes due to people dropping in/out of the pool etc). 

It does seem to be smoothing out a bit. Had a lot more trouble getting my first Windows setup on than my 2nd. My Linux node is now compiling and *crossing fingers* it will join up smoothly and catch up on the correct chain.

Part of the problem was we were banning each other, now the supermajority is taking over again, possibly, God willing.

I dont want to say too much and jinx us.  In the morning lets -reindex and resync a few nodes and verify we didnt store any bad blocks etc.

I noticed that on my Windows machines as well....I actually laughed about it because I saw what was going on and thought "oh, yeah that's the downside to decentralization". I'll run those commands on my nodes in the morning. Glad to be participating in a project like this even in my little way.

[Shoko943]

Just reposting here for folks who may have missed it. There is a new mandatory (1.0.3.1). Please upgrade to it!

[svirusxxx2]

Code:

89UpdateTip: new best=1a97af0a3c386b296cf8e749813ca04e5eb9c10c5f36e23a6d08ad7cd0f603a7  height=7253  log2_work=45.742719  tx=11112  date=2017-09-12 07:36:39 progress=1.000073  cache=1.1MiB(4540tx)

I'am on good chain ?
I see same high on pool.biblepay.org , but i'am not sure it have same hash of 7253 block

EDIT
Hmm... i just recived withdraw from pool so maybe is good chain

[oliwer21]

Code:

89UpdateTip: new best=1a97af0a3c386b296cf8e749813ca04e5eb9c10c5f36e23a6d08ad7cd0f603a7  height=7253  log2_work=45.742719  tx=11112  date=2017-09-12 07:36:39 progress=1.000073  cache=1.1MiB(4540tx)

I'am on good chain ?
I see same high on pool.biblepay.org , but i'am not sure it have same hash of 7253 block

EDIT
Hmm... i just recived withdraw from pool so maybe is good chain

And when you make withdraw?

[svirusxxx2]

Code:

89UpdateTip: new best=1a97af0a3c386b296cf8e749813ca04e5eb9c10c5f36e23a6d08ad7cd0f603a7  height=7253  log2_work=45.742719  tx=11112  date=2017-09-12 07:36:39 progress=1.000073  cache=1.1MiB(4540tx)

I'am on good chain ?
I see same high on pool.biblepay.org , but i'am not sure it have same hash of 7253 block

EDIT
Hmm... i just recived withdraw from pool so maybe is good chain

And when you make withdraw?

few blocks ago

Code:

   "account": "",
    "address": "BNNUsLw8FEdqfPYuoBc7uoSw9kr9hT9VxD",
    "category": "receive",
    "amount": 100.00000000,
    "vout": 1,
    "confirmations": 7,
    "bcconfirmations": 7,
    "blockhash": "5887e95f8f55a2969b8197f1d7d379e2e6f331a6aecc886206e79c538d222d83",
    "blockindex": 2,
    "blocktime": 1505203785,
    "txid": "5fab85bf4029fea89c4e12683b4529e5b8891e69e08608fad0ee1c2a51202af7",
    "walletconflicts": [
    ],
    "time": 1505203426,
    "timereceived": 1505203426,
    "bip125-replaceable": "no"

[PhaseshiftUK]

...
"networkhashps": 30039306485.7743
...

Is the network really producing 30 Gh/s currently, or is this misleading?

[cryptocurrencyfreak]

None of my 1.0.3.1 linux miners are being recognized by the pool...

[svirusxxx2]

None of my 1.0.3.1 linux miners are being recognized by the pool...

what is your last block number and hash ?

BTW... I still looking at pool.biblepay.org and when I recive new block also pool change to the same number... so I'am on the same chain as pool.biblepay.org.

my last block:

Code:

 new best=90c17b28cdafeffc2db56f6b4fe41a55300fe6db0ce0a9b7c83453c735b761b1  height=7265  log2_work=46.228082  tx=11135  date=2017-09-12 09:43:03 progress=1.000073  cache=1.1MiB(4560tx) new best=90c17b28cdafeffc2db56f6b4fe41a55300fe6db0ce0a9b7c83453c735b761b1  height=7265  log2_work=46.228082  tx=11135  date=2017-09-12 09:43:03 progress=1.000073  cache=1.1MiB(4560tx)

@PhaseshiftUK
I think there is some wrong with calculating

[slovakia]

  NetDiff

  OUT OF SYNC on CCEX

where is problem now?

[Shoko943]

https://i.imgur.com/c4ECwSr.png  NetDiff

https://i.imgur.com/eopzpLg.png  OUT OF SYNC on CCEX

where is problem now?

The dev sent them a message earlier so they can take the wallet offline for now while the issues we have/had with f7000 are being resolved.  Also, last time I checked they were still using the 1.0.2.9 version instead of the new 1.0.3.1 so maybe it ended up crashing or couldn't find any connection or something else.

On that note, I would encourage anyone who hasn't upgraded to 1.0.3.1 to do it now

[civilufo]

  NetDiff

  OUT OF SYNC on CCEX

where is problem now?

The dev sent them a message earlier so they can take the wallet offline for now while the issues we have/had with f7000 are being resolved.  Also, last time I checked they were still using the 1.0.2.9 version instead of the new 1.0.3.1 so maybe it ended up crashing or couldn't find any connection or something else.

On that note, I would encourage anyone who hasn't upgraded to 1.0.3.1 to do it now

You are right, 1.0.2.9 is outdated with some issues, that's the reason c-cex out of synced. Dev has informed them to upgrade their wallet, so we just have to wait c-cex upgrade.

[svirusxxx2]

check if you are on correct fork.
now is 7274 92f669bd4d82538be825434abab3b6f146f33a6b8fb4cd540398e8582556c978

my peers on public vrs2.hostv.pl node:

Code:

biblepay-cli getpeerinfo | grep synced_blocks | sort -n  | uniq -c
      1     "synced_blocks": 7263,
      7     "synced_blocks": 7270,
      4     "synced_blocks": 7271,
      5     "synced_blocks": 7272,
      1     "synced_blocks": 7273,
     18     "synced_blocks": 7274,

[Exavier]

Seem to be having trouble connecting to nodes on the network. Any list of nodes I can manually add to help my wallet connect?

[svirusxxx2]

Seem to be having trouble connecting to nodes on the network. Any list of nodes I can manually add to help my wallet connect?

add this to $HOME$/.biblepaycore/biblepay.conf

Code:

addnode=137.74.0.113
addnode=37.59.14.211
addnode=94.23.196.50
addnode=94.23.12.37
addnode=91.121.83.119
addnode=188.165.193.28

or in debug console:

Code:

addnode pool.biblepay.org onetry
addnode vrs2.hostv.pl onetry

[happy_merchant]

What block are we currently on? I wasn't around yesterday so I just saw there was another mandatory update just now. The block explorer is still running 1.0.2.9 so it might need to be reindexed. Compiling 1.0.3.1 right now.

[Shoko943]

What block are we currently on? I wasn't around yesterday so I just saw there was another mandatory update just now. The block explorer is still running 1.0.2.9 so it might need to be reindexed. Compiling 1.0.3.1 right now.

I just checked the pool and it's showing 7282 right now.