Does your 1242 blockhash and diff agree, btw?
Yes, I have the same hash for block 1242. But I have more strange things happening now. I restarted the client and it says block source not available and will not sync, even though it has one connection to your node (and I checked that it's not banned). I didn't know what to do, so I tried to rebuild the index (the option from the wallet repair tab) and now the wallet won't start at all, the splash screen shows "Activating best chain..." and then it dies. Btw, @bible_pay: Last post from luksbit got me thinking - do you think this forum topic should be in the announcements category? Because its purpose is testing buggy things, not to be a main topic for this coin for people to randomly find in the ann category. And maybe you should put the link to it in the OP of the main topic. On the topic location, I dont have permissions to create subtopics yet, or to move topics. I originally tried to make it a subtopic of Biblepay but couldnt. (We have a dedicated forum on a private server already, but I dont want to enable it until we hit 1000 users). Ill notify the mod to move it. |
|
|
|
Been trying to build this on a VPS but the build always fails on the make step. Is it possible to build just 'biblepayd' only?
For context, I've been building other wallet daemons with a 'make -f makefile.unix' without problem.
Do you mean to build Biblepay wallet in Linux? I have tried to build biblepay in Ubuntu 14.04 but failed with openssl version issue. Then I built again in Ubuntu 16.04 without problem. Just follow the instructions of a file named something like "build biblepayforlinux.txt" in the git will do. Do you need to run it desktop or can you run it command line. I followed the instructions to install the wallet but i can not figure out how to run it but im new to the world of linux Mod can you answer this please. thanks If you want to run the qt (gui) version: cd src ./biblepay-qt We also have a biblepayd daemon, you can find more by googling about bitcoind if you want to run the daemon. |
|
|
|
So the project is in full swing? Are you forecast when it will be listed on coinmarketcap?
Yeah, we have not hit any severe snags yet. Im in no hurry as I dont think we are greed based, but I mentioned on the main thread anyone is welcome to reach out to coinmarketcap to have us listed. |
|
|
|
|
11:28:11

showblock 1242
11:28:11

{
"hash": "d988e253ce99a1228feb909a10ed4c53225f01c97f4b0ad3e8307ee27eaf0362",
"confirmations": 1,
"size": 1311,
"height": 1242,
"difficulty": 0.6529178808936711,
"biblehash": "0000000007f5a4995e2e8587091a8cfce91f6acb8327b19f5c07bdab3ca7a5e3",
"prayers": ""
}
Does your 1242 blockhash and diff agree, btw?
Let me know if you can mine a block also.
Diff should be very easy to mine one.
|
|
|
|
OK, synced now. But something strange is happening. First it started to mine, using too much of my CPU (100%, computer barely responding), but showing a very small hash rate (about tenth of what I normally have - 15k instead of 150k). Then after 2 minutes, it completely stopped without me doing anything - getgenerate / biblepay-generate was still true but hashps was 0. Then after 2 more minutes it just started mining again on its own. Again 100% CPU.
Then I tried to lower genproclimit, but that did nothing, CPU still on 100%. Finally, hashps showed 0 again, but this time CPU was still at 100% and I couldn't stop it, like it was stuck, so I quit the client. And sometime in between I found one block. No errors in debug.log except two stale block errors.
Good deal, all these things 'should' (lol) be explainable. The bad blocks at the end of the chain-> my issue, since I had a rogue version mine a few with DGW parameters that were non-allowable. The re-index-> an unintended or inherited bug (will be fixed in the next version). The jerky mining-> Ensure you have in your master biblepay.conf (even though we are in testnet, modify the main one in \biblepaycore) to not do any pool mining by putting an x in front of pool (ie xpool). Ensure setgenerate is pretty low, since we are using a new hashing algo in testnet (ie setgenerate 5). So I finally see the nodes in my peers list are not being kicked off. I realize we will have a few problems with this build, but it should shed light on what needs adjusted. As far as the khashps being lower, the 100% biblepay algo is about 50-80% slower than the algo in prod (because there are no x11 hashes involved). Let me grab a few blockhashes and see if we match. |
|
|
|
OK, now I'm also on 1009, but for some reason in some parts of the interface it shows 994 (hover over progress bar and in the information window). But I can't mine, it says hashps is 0 and there is no activity on my CPU. Maybe because it still says synchronizing and 4 days behind? getmininginfo
{
"blocks": 1009,
"currentblocksize": 0,
"currentblocktx": 0,
"difficulty": 0.0007747477227062956,
"errors": "",
"genproclimit": 12,
"networkhashps": 7733395.331874545,
"hashps": 0,
"minerstarttime": "08-17-2017 14:49:57",
"ratio": 0,
"hc1": 0,
"bhc2": 0,
"pooledtx": 0,
"testnet": true,
"chain": "test",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"miningpulse": 0,
"poolmining": false
}
Btw, I think you should put the letter after the version number in the About window, because now I'm not sure if I'm running the correct version of 1.0.2.1. The setup .exe file also only shows 1.0.2.1. Yeah, I agree we need to know the distinct version. Even on minor upgrades, I think Ill increment the version during the next build. So, I had some issues over here while reindexing, and found a bug in BBP in our reindex routine, which is fixed but is unfortunately in your version, but we have a way to get around it. I pruned the blocks 1225+ out of the chain, reindexed with the unreleased version, and restarted again. Could you now please try unbanning me and restarting yet again and see if you sync to 1225 now? |
|
|
|
I downloaded the Windows version, ran it with -testnet flag (I got green background) and immediately upon opening I found 7 blocks in 2 seconds, and now it says I am on block 7.  Difficulty is 0.000279. I found a new chain somehow? I don't know how to access the test chain with 1248 blocks. But after a few seconds mining stopped by itself and I couldn't restart it with setgenerate because I couldn't connect to the network. Although I could do this in the Peers window: https://i.imgur.com/WqnKJpg.pngI thought my client banned the main node, but after I restarted it, the ban came back, so it probably means my node is banned. Also, these are the error messages from the debug.log, maybe they can help you: 2017-08-17 14:00:07 ERROR: ContextualCheckBlockHeader : incorrect proof of work at 1226
2017-08-17 14:00:07 Misbehaving: 97.99.69.33:40001 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-08-17 14:00:07 ERROR: invalid header received 00001d88f29397bee28457a5da46b5b729f9b581161e628d2000cf100e55ac72
2017-08-17 14:00:07 ProcessMessages(headers, 1945 bytes) FAILED peer=2 Thanks, Yeah, testnet allows mining without peers and without a chain, so that part is good. The node will reorganize anyway once it finds a longer chain. I think the problem here is my testnet node was mining on the prior version and mined some blocks that are not allowed anymore and I never rebooted, therefore they were not checked again. Ok, I deleted my chain on that node and restarted. Could you please unban me and then restart again and lets see how far we get? It took me back to block 1009 (thats about 4 days ago when we were all poolmining in testnet). |
|
|
|
1021c testers: I found two issues that will need fixed regardless in this version, so I had to push a commit.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
Alright 1021d is now available for download on biblepay.org. (Windows). Please try to solomine against testnet; we are on block 1248. I see part of the problem for us testing up til now: My external testnet node keeps banning anyone connecting to it on a prior version, since the diff adjustment has changed thereby banning every connection on the external IP. Let this be a lesson for me to increment the network minimum version (IE make it a mandatory for testnet) in the future. For now lets try to deal with it and get past it - I will try to keep unbanning the peers unless it is impossible. Let me know if anyone can mine on testnet past 1249. |
|
|
|
Good thing we have a pool, even there i dont get very much but at least some!
I was just looking at the block distribution history in the pool and there is no your name for the block 3493, but you are there on all the other ones. Were you off at that time or the pool didn't count your shares for some reason? The issue with one 12khs miner entry is that in the current model, if the 12khs miner has trouble solving some of the shares consecutively for over 15 mins, they can fall out of the pool and not be paid when the block distribution hits at the time of the solve. We are actively working on this in testnet to make it more likely the miner stays in (by ratcheting up the diff more slowly for the miner). The next version that has not been announced yet helps take care of this. There are some testnet issues going on - through the night but progress is still being made. |
|
|
|
|
1021c testers: I found two issues that will need fixed regardless in this version, so I had to push a commit.
If you are on linux, please get 1021d. If not please wait til the morning for the Windows release.
|
|
|
|
i cant login on pool. everytime i clicked login it redirects me to login page. this was working last night
Just click logout-login. |
|
|
|
Hi Dev, Moderator,
How to mine this coin BiblePay? Can we use GPU AMD or it's ASIC to mine?
Can somebody post the command line please
no you cant, only CPU, also if you mine with cpu you cant over 24 threads if you do you go solo mine Thanks for answering. Where is the link to download the miner please and what is the command line Yeah, just run the latest wallet from biblepay.org, and follow these easy instructions on the top of this thread: https://bitcointalk.org/index.php?topic=2070177.new#newMine against Prod, although we have not officially released the pool to prod, its running in beta mode. |
|
|
|
PS Btw guys, the windows version on biblepay.org is 1021c, so anyone can jump in and help on testnet now.
Tried doing a completely clean install of the 64-bit Windows release of 1021c, but it's still not working on testnet for me. Don't know if it'll help, but I uploaded the debug log to pastebin at https://pastebin.com/di2U3wMf-edit- Updated to a new pastebin debug log, since it started throwing a bunch of errors after I posted the first. Wait- I think I jumped the gun on that comment - I was RDPed in from a restaurant. And I believe BBP was off the screen. Ok, it does load in testnet mode for me from win64 bit. Could you please try reloading now that I have the node up and let me know if it syncs to 1230+? Then we can try mining a block. I just mined a few from Nix and a few from windows. The errors in your log appear to be OK- its that same old occasional cannot create block; I will look at that. But it shouldnt affect our testing. EDIT: PS, I see that two nodes were banned on the testnet external node; I just unbanned them. |
|
|
|
PS Btw guys, the windows version on biblepay.org is 1021c, so anyone can jump in and help on testnet now.
Tried doing a completely clean install of the 64-bit Windows release of 1021c, but it's still not working on testnet for me. Don't know if it'll help, but I uploaded the debug log to pastebin at https://pastebin.com/di2U3wMf-edit- Updated to a new pastebin debug log, since it started throwing a bunch of errors after I posted the first. No wonder no one is able to test, thanks, well whats strange is its mining fine on nix, but on windows its exiting silently on start but only in testnet. Let me check this out for a while. |
|
|
|
I saw the other coin that just launched an ann thread called Jesus coin. I think you guys should work together to achieve more.
Let us know what they have to offer that is unique? |
|
|
|
I dont see anything strange in testnet. Please try closing the wallet, delete banlist.dat, addnode=node.biblepay.org, delete all of the blocks and chainstate in the testnet3 folder, then restart.
It could be that whatever I mined on the ghost chain last night caused you to ban me.
It should technically sync back to 1240 or so and then we can start mining in testnet.
I don't have access to my miners right now, so sadly I can't make any changes for another day. But one of the miners I tried to deploy on the testnet was brand new, with a fresh installation of the wallet. But that one also didn't get any connections. Thats cool, I have to leave in a few mins myself, but I was actually hoping some people could get in and solo mine on testnet (I dont think the pool is up right now on the testnet side), Im trying to see if we can solo mine testnet and look at the next 20 blocks diffs and subsidies and chainwork and ratio of biblehashes etc. When I get a chance Ill try to grab another node also. PS Btw guys, the windows version on biblepay.org is 1021c, so anyone can jump in and help on testnet now. |
|
|
|
|
I dont see anything strange in testnet. Please try closing the wallet, delete banlist.dat, addnode=node.biblepay.org, delete all of the blocks and chainstate in the testnet3 folder, then restart.
It could be that whatever I mined on the ghost chain last night caused you to ban me.
It should technically sync back to 1240 or so and then we can start mining in testnet.
I see a potential issue with the anti-x11 feature, we are going to create a very high diff (not as far as blocks flying by) but as far as the diff showing artificially high, and therefore, very diluted subsidies (since we have the high-diff/low subsidy protection in), so if the subsidy drops below 19000 we will need to add more code to the testnet version to fix these two things, but, lets see how it behaves anyway and learn from it in case there are more things.
|
|
|
|
On the testnet I'm having trouble starting my miners. I've tried to start mining with two miners (low end laptops).
The first miners (sjappie_miner) wallet says '0 active connection(s) to biblepay network'. It does say it's in sync, and I'm able to mine (it does show up in the leaderboard from time to time), but with a very low HPS (about 80). I've used this miner before for mining on the testnet.
The second miners (jaapgvk_frotlaptop) wallet also says '0 active connection(s) to biblepay network'. It also says 'no block source available'. I've tried manually adding the node 'node.biblepay.org', but it doesn't seem to help.
Similar issue. Works on main but not on test. Debug log isn't giving much, just says "Reindexing block file blk00000.dat..." then silently crashes/exits. --edit-- Even if it's mining on main, won't any block it finds likely be rejected by the rest of the network not running 1.0.2.1? On older clients, the proof of work algorithm for checking blocks would still be expecting both an X11 hash and a Biblehash that are below the target difficulty, no? Ive been trying to maintain one codebase up to this point so I know it is a little confusing the way the features are phased in. On 1021, mining in main is the same as 1020- no changes have been made to the algo in main. Basically, we would need to test it in testnet, announce the mandatory to prod and give a target block # like say block 6000, and alert ccex of the coming mandatory. At 6000, it would Then behave like testnet. Testnet on the other hand has the new anti-x11 feature in it now. I too have no connections. Let me take a look at that next. EDIT: But of course, the non-breaking compatibility features, like the diminishing-kh fix is in immediately. On both chains. |
|
|
|
The pool is working good for me, finally somewhat stable "income". Good job dev!
LOL, yeah, I see our price keeps dropping by 1 satoshi per day, but thats probably because people have a high degree of fear of whats going to happen Friday when we empty the orphan wallet, but I think Monday when they see the orphan database they will have a change of heart. Anyway the pool is *OK* in most respects, performance wise seems very good. I am waiting for the effects of the next release to hit to see if the diminishing hps bug is resolved as I want to keep the problems isolated, so we can fix things properly. The release is being tested in testnet now by a couple people; we will post more in the pool thread once its working. We have not released the pool to prod yet as I believe this the pool is still in beta. |
|
|
|
|
1.0.2.1c - Non-Mandatory Release
- For upcoming mandatories rule @1350(testnet)||@7000(Prod), Testnet features: test anti-block-clump retarget rule, slow_block_threshhold = 30 mins rule,
removing the x11 component from POW, and ratio of x11:biblehashes in getmininginfo
- In wallet Bible Reader (Help | Read Bible). NOTE: You currently must choose the Book after the page loads.
- Fixes for in-wallet pool-miner (fixes diminishing KHS)
- adjustment to getnetworkhasps
** Im releasing it here, lets test it out. **
If successful, we should mine without x11 in testnet, and prod should have the fix for the diminishing hashps.
Then we can release on the prod side.
EDIT: PS, I think once we merge in the txindex lookup feature, we can lower the mandatory block # by a 1000 or so. Also, last night I lowered the block # to 1240 in testnet, so the above 1350 is no longer correct.
|
|
|
|
|
Show Posts
