BiblePay - New Coin Launch - Official Thread

[happy_merchant]

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.

That's what all my nodes are reporting.

[oliwer21]

Topic run so quick:P

 another thing to mention is that 1.0.3.1 linux outperfomed win version running on a higher end hardware.
 in my case ryzen7 with linux had x10 times hashrate compared to win.

@bible_pay can you write something about this?

[bible_pay]

Topic run so quick:P

 another thing to mention is that 1.0.3.1 linux outperfomed win version running on a higher end hardware.
 in my case ryzen7 with linux had x10 times hashrate compared to win.

@bible_pay can you write something about this?

Ive still got the back end systems to bring up, and looks like I have to babysit in 15 mins, so we can circle back on this tonight.

[bible_pay]

I see Liugang has 99 miners pointed at the pool, we have to watch out we dont blow out the STATS field in the database.

Ill try to put a limit on the field in Blockhistory now so he doesnt take the whole pool down.

[emdes]

Topic run so quick:P

 another thing to mention is that 1.0.3.1 linux outperfomed win version running on a higher end hardware.
 in my case ryzen7 with linux had x10 times hashrate compared to win.

@bible_pay can you write something about this?

Ive still got the back end systems to bring up, and looks like I have to babysit in 15 mins, so we can circle back on this tonight.

So that could be the reason my Ryzen only runs at 35% load now ? since the 725X block. 100% load before block 7000. 54% load between 7000 and 725X

[ajeef1234]

i can't download win64 wallet from http://biblepay.org/

[PhaseshiftUK]

Biblepay 1.0.3.4-Mandatory Upgrade
www.biblepay.org

- Fix ST13 Error
- Fix f7000 Low-Subsidy based on High-Diff calculation
- Fix Pool banning issue
- Fix Read Disk error

- At block 7500, we raise the subsidy back to ~18,000.

Sadly I'm still having trouble with the Linux version crashing.  I deleted my chain and other files (except the .conf files, wallet and backups) and set it going:

2017-09-13 22:32:09 Biblepay Core version 1.0.3.4 (2017-09-13 13:50:37 -0500)
2017-09-13 22:32:09 InitParameterInteraction: parameter interaction: -externalip set -> setting -discover=0
2017-09-13 22:32:09 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-09-13 22:32:09 ProdMode: Prod 1.000000Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
<snip>
2017-09-13 22:32:55 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:55 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:56 UpdateTip: new best=617068fc15cd6a331c353bc84c44481c18a7a481232f70e859638d85afda2ef3  height=7425  log2_work=48.7033  tx=11427  date=2017-09-13 11:17:14 progress=0.995910  cache=1.1MiB(4726tx)
2017-09-13 22:32:56 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7425.000000 pindexPrev 617068fc15cd6a331c353bc84c44481c18a7a481232f70e859638d85afda2ef3
2017-09-13 22:32:57 ERROR: CheckBlockHeader(): proof of work failed
2017-09-13 22:32:57 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-13 22:32:57 Misbehaving: 66.151.244.166:40000 (0 -> 1)
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 ProcessNewBlock : ACCEPTED
2017-09-13 22:32:57 UpdateTip: new best=e7eee938ff20b68d9c3c7193433e36929baec65c47a571fb48659a8e542b5188  height=7426  log2_work=48.708165  tx=11428  date=2017-09-13 11:19:30 progress=0.995924  cache=1.1MiB(4727tx)
2017-09-13 22:32:57 UpdateTip: new best=60b8771dfcae5bc928a67bb25d68025bede5c2529b1831c35afe0823ad1bfaaa  height=7427  log2_work=48.71815  tx=11430  date=2017-09-13 11:28:27 progress=0.995979  cache=1.1MiB(4728tx)
2017-09-13 22:32:57 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7427.000000 pindexPrev 60b8771dfcae5bc928a67bb25d68025bede5c2529b1831c35afe0823ad1bfaaa
2017-09-13 22:32:57 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3263902)*** Failed to read block
2017-09-13 22:32:57 Error: Error: A fatal internal error occurred, see debug.log for details
2017-09-13 22:32:57 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-09-13 22:32:57 tor: Thread interrupt
2017-09-13 22:32:57 torcontrol thread exit
2017-09-13 22:32:57 scheduler thread interrupt
2017-09-13 22:32:57 msghand thread interrupt
2017-09-13 22:32:57 addcon thread interrupt
2017-09-13 22:32:57 mnbcon thread interrupt
2017-09-13 22:32:57 net thread interrupt
2017-09-13 22:32:59 opencon thread interrupt
2017-09-13 22:32:59 PrepareShutdown: In progress...
2017-09-13 22:32:59 StopNode()
<snip>

[bible_pay]

Biblepay 1.0.3.4-Mandatory Upgrade
www.biblepay.org

- Fix ST13 Errornal error occurred, see debug.log for details
2017-09-13 utdown: In progress...
2017-09-13 22:32:59 StopNode()
<snip>

Try possibly deleting chainstate,database,blocks and all files except .conf and wallet?
Could be the chainstate file.
Also I know you tried but ensure you sync from 0 with no banlist.dat present?
Could be an old blockindex stored somewhere.
Ive been able to get all mine up on the new version so something must be grabbing a blockheader from an old online node.
Ensure on your LAN all nodes are updated first also?

[inblue]

I see Liugang has 99 miners pointed at the pool, we have to watch out we dont blow out the STATS field in the database.

Ill try to put a limit on the field in Blockhistory now so he doesnt take the whole pool down.

I had an idea about the block history page - would it be possible to display just a small table of blocks where the rows would open a modal window on click (like the others you use on the site) where you can see more details and a full list of miners for that block, like know.

So basically, the small table would only have one row per one block, and it would contain the following columns: height, subsidy, PPH and time. This data is anyway always the same for one block and now it's being repeated a lot in the big table, needlessly. Then when you click on a row of a certain block, you would see the list of miners with all the other data.

This way the page would be much smaller and faster to load, assuming the modal windows are only loaded on request (click on row). Especially because a lot of the times for example I want to take a quick look only at the last mined block details.

[happy_merchant]

Hmm, two of my nodes went down at the same time. Other nodes were unaffected.

Code:

2017-09-13 22:40:50 ProcessNewBlock : ACCEPTED
2017-09-13 22:40:50 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 7491.000000 pindexPrev 64$2017-09-13 22:40:50 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3269787)*** Failed to read$2017-09-13 22:40:50 Error: Error: A fatal internal error occurred, see debug.log for details
2017-09-13 22:40:50 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-09-13 22:40:50 tor: Thread interrupt
2017-09-13 22:40:50 msghand thread interrupt
2017-09-13 22:40:50 torcontrol thread exit
2017-09-13 22:40:50 scheduler thread interrupt
2017-09-13 22:40:50 addcon thread interrupt
2017-09-13 22:40:50 opencon thread interrupt
2017-09-13 22:40:50 mnbcon thread interrupt
2017-09-13 22:40:50 net thread interrupt
2017-09-13 22:40:50 PrepareShutdown: In progress...
2017-09-13 22:40:50 StopNode()
2017-09-13 22:40:50 Verifying mncache.dat format...
2017-09-13 22:40:50 Loaded info from mncache.dat  0ms
2017-09-13 22:40:50      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$
2017-09-13 22:40:50 Writting info to mncache.dat...
2017-09-13 22:40:50 Written info to mncache.dat  1ms
2017-09-13 22:40:50      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list:$2017-09-13 22:40:50 mncache.dat dump finished  1ms
2017-09-13 22:40:50 Verifying mnpayments.dat format...
2017-09-13 22:40:50 Loaded info from mnpayments.dat  0ms
2017-09-13 22:40:50      Votes: 0, Blocks: 0
2017-09-13 22:40:50 Writting info to mnpayments.dat...
2017-09-13 22:40:50 Written info to mnpayments.dat  1ms
2017-09-13 22:40:50      Votes: 0, Blocks: 0
2017-09-13 22:40:50 mnpayments.dat dump finished  1ms
2017-09-13 22:40:50 Verifying governance.dat format...
2017-09-13 22:40:50 Loaded info from governance.dat  0ms
2017-09-13 22:40:50      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 Writting info to governance.dat...
2017-09-13 22:40:50 Written info to governance.dat  2ms
2017-09-13 22:40:50      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-13 22:40:50 governance.dat dump finished  3ms
2017-09-13 22:40:50 Verifying netfulfilled.dat format...
2017-09-13 22:40:50 Loaded info from netfulfilled.dat  0ms
2017-09-13 22:40:50      Nodes with fulfilled requests: 0
2017-09-13 22:40:50 Writting info to netfulfilled.dat...
2017-09-13 22:40:50 Written info to netfulfilled.dat  1ms
2017-09-13 22:40:50      Nodes with fulfilled requests: 0
2017-09-13 22:40:50 netfulfilled.dat dump finished  1ms
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50
BiblepayMiner -- terminated
2017-09-13 22:40:50 Shutdown: done
2017-09-13 22:45:05

I was able to just restart biblepayd with no apparent issues and they're fully synced with the network again.

[PhaseshiftUK]

Try possibly deleting chainstate,database,blocks and all files except .conf and wallet?
Could be the chainstate file.
Also I know you tried but ensure you sync from 0 with no banlist.dat present?
Could be an old blockindex stored somewhere.
Ive been able to get all mine up on the new version so something must be grabbing a blockheader from an old online node.
Ensure on your LAN all nodes are updated first also?

Thanks, I'd done all the deletions before that error.  There were no others running on my LAN at the time, however restarting it again (but not deleting this time) seems to have got it over the bump, and (fingers crossed) it is working now.

[ManOnTheMoon]

Hey dev, quick question. 

I've noticed you added BLOOM to this coin's protocol. May I ask why? Also, considering the only other coin that uses bloom is BTX, do you plan to implement their other features, such as the super fast syncing, HD wallet feature, and segwit?


Cheers.

[seasonw]

Ubuntu miners dropped from pool still happen. Any clue?

[tiras]

Ubuntu miners dropped from pool still happen. Any clue?

second this.    have to restart them often to keep alive in the pool

[bible_pay]

Hey dev, quick question. 

I've noticed you added BLOOM to this coin's protocol. May I ask why? Also, considering the only other coin that uses bloom is BTX, do you plan to implement their other features, such as the super fast syncing, HD wallet feature, and segwit?


Cheers.

It was just added to allow the sanctuaries to reply with the set of filtered votes when requested, but no, the HD seeded addresses and segwit were not considered yet.  But I do plan on bringing a volunteer on board that monitors bitcoin and dash for relevant pushes of new features, and handles security monitoring patches also.

I would like to say that our IT dept wont rest until we do something groundbreaking with Biblepay.

[bible_pay]

Try possibly deleting chainstate,database,blocks and all files except .conf and wallet?
Could be the chainstate file.
Also I know you tried but ensure you sync from 0 with no banlist.dat present?
Could be an old blockindex stored somewhere.
Ive been able to get all mine up on the new version so something must be grabbing a blockheader from an old online node.
Ensure on your LAN all nodes are updated first also?

Thanks, I'd done all the deletions before that error.  There were no others running on my LAN at the time, however restarting it again (but not deleting this time) seems to have got it over the bump, and (fingers crossed) it is working now.

Lets try one more thing, try going into your backups folder and restoring an old wallet file on top of wallet.dat.

Anyone with constant restarts? Try that too.
Otherwise Ill have to continue looking at this in the morning.

[bible_pay]

Try possibly deleting chainstate,database,blocks and all files except .conf and wallet?
Could be the chainstate file.
Also I know you tried but ensure you sync from 0 with no banlist.dat present?
Could be an old blockindex stored somewhere.
Ive been able to get all mine up on the new version so something must be grabbing a blockheader from an old online node.
Ensure on your LAN all nodes are updated first also?

Thanks, I'd done all the deletions before that error.  There were no others running on my LAN at the time, however restarting it again (but not deleting this time) seems to have got it over the bump, and (fingers crossed) it is working now.

Lets try one more thing, try going into your backups folder and restoring an old wallet file on top of wallet.dat.

Anyone with constant restarts? Try that too.
Otherwise Ill have to continue looking at this in the morning.

I think I figured out what the hang up was: Ive got an old machine that wouldnt sync past 7200, over and over, even after deleting everything but wallet.dat.

It turns out, there is a hidden file (either a .lock(ed) database file or binary chainstate hidden file) inside the blocks dir.  To get around this (because deleting didnt work), create a new directory, and MOVE your blocks,chainstate,database into the subdirectory called Trash, then restart and sync from 0 and it synced right up.


I doubt this will fix the other reported issue (but it at least should get you synced).

[bible_pay]

I see Liugang has 99 miners pointed at the pool, we have to watch out we dont blow out the STATS field in the database.

Ill try to put a limit on the field in Blockhistory now so he doesnt take the whole pool down.

I had an idea about the block history page - would it be possible to display just a small table of blocks where the rows would open a modal window on click (like the others you use on the site) where you can see more details and a full list of miners for that block, like know.

So basically, the small table would only have one row per one block, and it would contain the following columns: height, subsidy, PPH and time. This data is anyway always the same for one block and now it's being repeated a lot in the big table, needlessly. Then when you click on a row of a certain block, you would see the list of miners with all the other data.

This way the page would be much smaller and faster to load, assuming the modal windows are only loaded on request (click on row). Especially because a lot of the times for example I want to take a quick look only at the last mined block details.

Yeah, I like the idea, we can do it.  I have classes in the code for that, so it should work great.

[bible_pay]

Ubuntu miners dropped from pool still happen. Any clue?

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.

[seasonw]

Ubuntu miners dropped from pool still happen. Any clue?

I believe that was just before the pool upgraded to 1.0.3.4.  Should be good now.

This message was found with miner 1.0.3.4 to pool 1.0.3.4. Actually it happened since 1.0.3.1, and weird issue is some miners do not have this problem at all... Any other info do you want me to provide so that you can trace the issue?