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. |
|
|
|
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). |
|
|
|
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. |
|
|
|
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. |
|
|
|
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? |
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
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! |
|
|
|
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... |
|
|
|
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. |
|
|
|
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. |
|
|
|
Nice a new version :-D
But wat about the mining and transaction from today ...
I understand that a role back will take this away?
I made my first transaction today lol
(Just a minor miner on a old laptop )
It depends on if the chain you mined it on stays the longest chain. Everyones upgrading to 1034 now. If you mined it on 1034, it might stick. Anyway if it dissapears, the tx in the txlist will become an orphan and have a different icon. |
|
|
|
[quote author=tiras link=topic=2042657.msg21805705#msg21805705 date=1505333967]
"poolinfo3": "HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; ", [/quote] Hi Tiras, Pool is not updated yet to 1.0.3.4. Working on that next. It has to be upgraded to answer the calls properly. |
|
|
|
To give real service, you must add something which cannot be bought or measured with money, and that is sincerity and integrity.
+++ |
|
|
|
In addition to c-cex, what are the plans to be listed on other exchanges. And which ones will be listed?
I think what we should do is focus on testing the Sanctuary version in testnet, and debug it in full, add our beta software to the web site for governance, then talk about more exchanges. The next exchanges are bittrex and poloniex. |
|
|
|
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. |
|
|
|
|
Alright, lets rewind the whole day back to about 7 AM and try this again.
Version 1.0.3.4 (the future mandatory) is now checked in for linux only. This new version includes a 'protocol' upgrade meaning it wont communicate with prior versions. If anyone on linux wants to upgrade now and start pre-testing go for it.
Win is compiling and will be ready in two hours.
In the mean time I need to run some errands, Ill be back in two hours and we can release Windows and I will make a POST so everyone can be ready at approx the same time to try the mandatory upgrade again.
|
|
|
|
Any computers that I upgraded to 1.0.3.2 do not connect to nodes. No matter how many addnodes I have in the conf.
All of the computers running 1.0.3.1 do connect to nodes even after restarting them.
None are showing up on the pool.
JUST WAIT  Nice pic, thats what I feel like! So basically, 1.0.3.1-1.0.3.3 was a failure. This version contains a bad LogPrint message, that causes the entire wallet to die. The new version is almost ready. I just tested it and it works on debian and raises the subsidy back up to normal at block 7500. |
|
|
|
|
Sorry, been gone debugging the problem with the new version. Kind of hard to find the root cause.
You'll never believe how dumb the problem is- the issue is with changing the DGW parameter, in mid stream, a certain block header between 7100-7250 causes an unprintable log error, and that actually takes down the whole wallet.
The key is to set a future block number for the subsidy increase. I obviously would have done that, but I was viewing this as Hey we need a mandatory lets just change it now.
Let me go back and set up the change and Ill get back in about 30 minutes.
|
|
|
|
|
Show Posts
