 Is something wrong on the pool, or something change after 10k block. Miners raports only 1-2 shares and reset to 0. It looks like what happened was at block 10,000, the pool started treating 90% of the shares submitted as stale due to a bug. The bug has been resolved. This affected 14 paid blocks. I credited every pool miner with 20* the estimated shortpay amount. You can see the credit in the Transaction Log report. Yes, everything is ok. Good job Bible_pay Btw all, to see the Mining_Credit click "Reports | Transaction History" and search the page for "BLOCK_10K". |
|
|
|
Is something wrong on the pool, or something change after 10k block. Miners raports only 1-2 shares and reset to 0. It looks like what happened was at block 10,000, the pool started treating 90% of the shares submitted as stale due to a bug. The bug has been resolved. This affected 14 paid blocks. I credited every pool miner with 20* the estimated shortpay amount. You can see the credit in the Transaction Log report. |
|
|
|
Is something wrong on the pool, or something change after 10k block. Miners raports only 1-2 shares and reset to 0. Yeah, you have found a problem, researching now... |
|
|
|
Please let question. The schedule is here: (205 blocks per day, 7 minute block targets): // Yearly decline of production by ~10% per year, projected ~14.54 Billion coins max by year 2050+.
// Year: 2017, Subsidy: 20000, Emission: 1496500000, Grand Total: 1 496 500 000
// Year: 2018, Subsidy: 18000, Emission: 1346850000, Grand Total: 2 843 350 000
// Year: 2019, Subsidy: 16200, Emission: 1212165000, Grand Total: 4 055 515 000
// Year: 2045, Subsidy: 1046, Emission: 78318973, Grand Total: 14 260 129 248
// Year: 2050, Subsidy: 618, Emission: 46246570, Grand Total: 14 548 780 867
Is the schedule out of the current blocks? The block reward breakdown is as follows:
100 Reward (example)
10 : Charity (sponsoring orphans, 100% goes to the orphans)
10 : MasterNode network (goes live at Christmas of 2017 - allows for rewards for running full sanctuary nodes, allows the coin to become a Charitable DAO organization, fully running by the community itself)
(Note this is 0 for the first 40000 blocks)
80 : Block Subsidy to the Node who mined the block using POB
Is MasterNode started from the 40000 blocks? When is it? The schedule was estimated based on Jan 1 2017 but in reality we started Aug 2017, so reality is lagging behind the schedule. Also, we emit less due to a high diff and due to our block rate lagging behind. The sanctuaries go live at Christmas 2017. Block 40,000 will be readjusted with the correct block. |
|
|
|
I'm sure this has been asked but I can't find the info anywhere. What is the difference between hps and hps2 on the pool? I know this is still kind of in beta, but that pool website can't possibly be anymore clunky and non-intuitive!
From a technical perspective, its not clunky (as its smooth as silk, with ajax callbacks), so thats false. From the non-intuitive perspective, its actually that you dont know how to use it yet - its not non-intuitive. Non intuitive is if you are trying to write a letter and the option is hidden, but with the pool, everything is available from the left menu and labeled. Maybe jealousy is the word? Do you want to port it to another coin? LOL look, I didn't mean to offend you, but saying "its actually that you don't know how to use it yet" proves my point. Lets start with the basic fact that the Help Guide link doesn't work which is the one place I would expect to learn how to use the site. The pool doesn't explain the difference between hps1 and hps2, and why there is a mismatch. The letter writing thing to the orphans is a mystery as to what it is exactly. I could keep going but I think it should be obvious. Either way I didn't create the post to ridicule a website, I honestly just wanted to know what the hps2 was. Thanks for the input. We will try to improve the pool to accomodate "newbies". I apologize for offending you. Does anyone want to volunteer to write a Help guide? We can link to it from the Help | Help menu. Have a nice day. |
|
|
|
Interesting coin...so you can only cpu mine it??
Yes, and if anyone ever finds a way to run it in a GPU or an ASIC, let us know, as our new slack team will add a guard around the miner and start using mining keypairs that expire hourly. We will implement the feature that makes Biblepay CPU only permanently. |
|
|
|
I'm sure this has been asked but I can't find the info anywhere. What is the difference between hps and hps2 on the pool? I know this is still kind of in beta, but that pool website can't possibly be anymore clunky and non-intuitive!
From a technical perspective, its not clunky (as its smooth as silk, with ajax callbacks), so thats false. From the non-intuitive perspective, its actually that you dont know how to use it yet - its not non-intuitive. Non intuitive is if you are trying to write a letter and the option is hidden, but with the pool, everything is available from the left menu and labeled. Maybe jealousy is the word? Do you want to port it to another coin? |
|
|
|
So we have to run multiple daemons to get better rewards (HPS2)? It seems the pool reward algorithm is wrong? All the shares are equal no matter the difficulty of the share is?
One 10-CPU machine with 1 miner gives 29k HPS2.
One 10-CPU machine with 10 miners gives 120k HPS2.
29k to 120k. it is 4 times reward.
This will let us create many many workers in the pool.
Btw, you can consolidate your workers so we dont have massive long list of miners in the leaderboard- once you know your avg HPS2, you can point two or more daemons at one workerid and should see the increased HPS2 now. The HPS itself will be wrong, but HPS2 should rise. |
|
|
|
So we have to run multiple daemons to get better rewards (HPS2)? It seems the pool reward algorithm is wrong? All the shares are equal no matter the difficulty of the share is?
No, the assumption isnt that its wrong, the assumption is the biblehash algorithm favors small rigs. Remember the biblehash algorithm isnt written to reward the fastest proc, its written to reward who solves the biblehash chained verses with a solution- and that requires a full node- take a look at the code for the hash algorithm- it requires you to look at the block, get things every so often when the timestamp needs changed, chain the verses together and execute some business logic from the full node to hash it. Now as far as how do we explain why the pool seems to favor distributed nodes over super machines, I have no clue. Ive looked at the code for the solution reward, and its like this: I hand out 20 equal easy problems to the team, and as you solve those equal easy problems you get a share. Thats how it works. Why multiple machines solve these equal weighted shares 'easier' is still beyond me. |
|
|
|
Thank you so much for all that.  Let me archive this on our wikipedia page. You're welcome. You could also add the instructions there on how to run multiple nodes, from my previous posts. I am also hoping for your rough opinion of the results. Thanks. Yeah, I wrote one line about it at the top. Anyone, feel free to edit the page to make it nicer. I am in the middle of starting the slack team guys so I have to stay focused. Im also writing code for the governance web interface for support for the upcoming changes. (We have to convert proposals to hex, have pages to enter proposals, convert to RPC commands, create transactions, send escrows, list the proposals, submit the proposals, etc, and all that is just for the first sanctuary command, etc). Thats why it is important for us to start an IT department over the next 3 days. |
|
|
|
Wild, good deal that you got that far. I havent done it with biblepay yet, but here is a link where someone connects to his second instance of multichain-cli: https://www.multichain.com/qa/2817/how-to-run-datadir-in-multichainIt appears the biblepay-cli command authenticates you through a default rpc port and that guy is specifying a second one Thanks for the link. So I accessed the second CLI like this: ./biblepay-cli -datadir=/home/inblue/.biblepaycore2 getmininginfo (I put the listen=0 in the conf file) I actually already tried the above command before and it didn't work, but it's because I was too tired and I typed ./biblepay-cli getmininginfo -datadir=/home/inblue/.biblepaycore2 (so the order of arguments is important).
RESULTSAll values are taken after about half an hour of mining. Type of computer: 10-CPU Xeon Skylake. Note that for the pool to register more than one instance, every instance has to be a different worker.Running 1 biblepayd at genproclimit 20: HPS: 52k
HPS2: 29kRunning 2 biblepayd at genproclimit 10 each: HPS: 29k + 28k = 57k
HPS2: 30k + 30k = 60kRunning 4 biblepayd at genproclimit 5 each: HPS: 15k + 14.5k + 14.5k + 14.5k = 58.5k
HPS2: 19k + 22k + 19k + 20k = 80kRunning 10 biblepayd at genproclimit 2 each: HPS: 6k x 10 = 60k
HPS2: 12k x 10 = 120kSo the conclusion is obvious - the HPS is about the same regardless of the number of daemons, but HPS2 rises considerably.
The next test I did was running 10 daemons on 10 separate 1-CPU machines (the CPU is the same as in the 10-CPU machine) and also genproclimit 2 as before. This scenario gives: HPS: 10k x 10 = 100k
HPS2: 17k x 10 = 170kSo this is even more than if you run 10 daemons on the same machine, which is 60k HPS and 120k HPS2, as noted above.
SummarySolo miningOne 10-CPU machine with 1 miner gives 52k HPS.
One 10-CPU machine with 10 miners gives 60k HPS.
Ten 1-CPU machines with 1 miner each give 100k HPS.Pool miningOne 10-CPU machine with 1 miner gives 29k HPS2.
One 10-CPU machine with 10 miners gives 120k HPS2.
Ten 1-CPU machines with 1 miner each give 170k HPS2.Thank you so much for all that. Let me archive this on our wikipedia page. Wiki Link:
http://wiki.biblepay.org/Multiple_Instances |
|
|
|
I found this Bible Pay just browsing around I didn't even know it existed. Are there any exchange's it's listed on??
We're on c-cex so far. If anyone is just browsing around, wondering what we do, we sponsor orphans from 10% of the blockchain, check this site out: http://accountability.biblepay.org/
Click on Orphans | Orphan Active Sponsored Orphans list. We have about 94 orphans already sponsored. |
|
|
|
I found this Bible Pay just browsing around I didn't even know it existed. Are there any exchange's it's listed on??
We're on c-cex so far. |
|
|
|
|
Yikes, 250738574 is back! Lots of hashpower pointed at the pool.
Last subsidy: 1777 BBP:
250738574 9607 13749.0000 1777.1636 9/27/2017 9:04:05 PM 1007822.08 0.0018179076054448 9/27/2017 9:03:59 PM 121: 6473 (1007822)
122: 6629 (1007822)
123: 6623 (1007822)
124: 6510 (1007822)
125: 6393 (1007822)
126: 6438 (1007822)
127: 6493 (1007822)
128: 6626 (1007822)
129: 6675 (1007822)
130: 6690 (1007822)
131: 6808 (1007822)
132: 6808 (1007822)
133: 6823 (1007822)
134: 6693 (1007822)
135: 6826 (1007822)
136: 6689 (1007822)
137: 6661 (1007822)
138: 6675 (1007822)
139: 6768 (1007822)
250738574: 5463 (1007822)
250738574-1: 7025 (1007822)
250738574-10: 6017 (1007822)
250738574-11: 5877 (1007822)
250738574-12: 5878 (1007822)
250738574-13: 5877 (1007822)
250738574-14: 5857 (1007822)
250738574-2: 7271 (1007822)
250738574-3: 7160 (1007822)
250738574-4: 7101 (1007822)
250738574-5: 6685 (1007822)
250738574-6: 6004 (1007822)
250738574-7: 6708 (1007822)
250738574-8: 6651 (1007822)
250738574-9: 6929 (1007822)
5136-1: 6008 (1007822)
5136-10: 5988 (1007822)
5136-11: 6008 (1007822)
5136-12: 5999 (1007822)
5136-13: 5493 (1007822)
5136-14: 5500 (1007822)
5136-15: 5461 (1007822)
5136-16: 5452 (1007822)
5136-17: 5483 (1007822)
5136-18: 5501 (1007822)
5136-19: 5453 (1007822)
5136-2: 5972 (1007822)
5136-20: 6413 (1007822)
5136-21: 6381 (1007822)
5136-22: 6473 (1007822)
5136-23: 6368 (1007822)
5136-24: 6477 (1007822)
5136-25: 6424 (1007822)
5136-26: 6470 (1007822)
5136-27: 6418 (1007822)
5136-28: 6412 (1007822)
5136-29: 6424 (1007822)
5136-3: 5950 (1007822)
5136-30: 4810 (1007822)
5136-31: 4803 (1007822)
5136-32: 5044 (1007822)
5136-33: 4799 (1007822)
5136-34: 4044 (1007822)
5136-35: 5077 (1007822)
5136-36: 4794 (1007822)
5136-37: 4819 (1007822)
5136-38: 5041 (1007822)
5136-39: 5065 (1007822)
5136-4: 5983 (1007822)
5136-40: 5065 (1007822)
5136-41: 5073 (1007822)
5136-42: 4788 (1007822)
5136-43: 4805 (1007822)
5136-44: 5055 (1007822)
5136-45: 4789 (1007822)
5136-5: 5985 (1007822)
5136-6: 5986 (1007822)
5136-7: 5933 (1007822)
5136-8: 5971 (1007822)
5136-9: 5990 (1007822)
8451: 6995 (1007822)
8452: 6003 (1007822)
8453: 6787 (1007822)
8456: 6685 (1007822)
8457: 6636 (1007822)
8458: 6679 (1007822)
8459: 6064 (1007822)
8460: 6016 (1007822)
8461: 6066 (1007822)
8462: 6005 (1007822)
8463: 6066 (1007822)
8464: 6069 (1007822)
8465: 6006 (1007822)
8466: 6009 (1007822)
8467: 6021 (1007822)
8468: 6049 (1007822)
8469: 6077 (1007822)
I'm going to add a feature tomorrow to sort the block_distribution by height descending,subsidy descending - its in Test now.
Stay ready for the rapture.
|
|
|
|
Error: Unable to bind to 0.0.0.0:40000 on this computer. Biblepay Core is probably already running.
Error: Failed to listen on any port. Use -listen=0 if you want this.
Wild, good deal that you got that far. I havent done it with biblepay yet, but here is a link where someone connects to his second instance of multichain-cli: https://www.multichain.com/qa/2817/how-to-run-datadir-in-multichainIt appears the biblepay-cli command authenticates you through a default rpc port and that guy is specifying a second one |
|
|
|
In the mean time, the other thing that no one has reported is what happens when you run two copies of BBP against two different datadirectories on the Ryzen? If anyone can test that out and report back that would be immensely helpful also. I think inblue was going to try that on a server at one point.
Someone tried that on a Xeon before: I just run 8 times biblepayd with genproclimit=1 on my Xeon E3-1245 v5 @ 3.5GHz
and now is 70583.5 hashps
Before with one biblepayd with genproclimit=8 I had about 68000 hashps so it's not big diffrent
I run gentoo linux 4.7.10-hardened with ZFS filesystem.
But I couldn't find a way to run multiple daemons. The .biblepaycore directory is locked when one daemon is running and I don't know how to point a second daemon to a different directory (or any other way to achieve it). How to do it without editing the source code and recompiling for every instance? Oh wow, great info, I didnt see that post, cool. You can specify the -datadir for each launched instance to be different and share the same box with the same codebase. |
|
|
|
whats with pool? no blocks we mined
Last night at 10pm biblepayd on the pool went out, I just restarted it all is well now, the pool auto-paid everyone through the night. Hopefully the system can stay up for 30 days straight now. |
|
|
|
Out of curiosity while I compile.. I had a question. Is the command below assigning the password = pwd to BBP root just so it can write in and out without issue?
BP_ROOT=$(pwd)
No, BP_ROOT is not the root account, its the BiblePay Root Directory argument, and pwd is not the password, but the 'current working compile directory'. Its needed to make BerkleyDb4.8 work in linux. The reason we cant go to 5.1+ is we are staying with Bitcoin compatibility for the wallet format. |
|
|
|
Thanks for the testing. So in a nutshell you are saying the Ryzen will only use 35% of the processor no matter what proclimit is set, and both the 32 bit and 64 bit builds are essentially the same.
Ok, that sounds like a different problem than I had on the windows xeon 2 proc. The xeon on 64 bit only used 50% of the proc, but on 32 bit I got it to use 90% of the proc and on the pool it solves roughly what the linux equiv box solves.
Additionally, non use of resources is a different problem than was discussed after f7000 went live. The problem we looked at before was the hash rate drop on the servers compared to the laptops and the shares solved per HPS- while assuming the whole processor was being utilized. This is more of an issue where the processor is not being utilized.
I think I will have time to take a look at making a test miner that holds a reference to two KJV bibles.
In the mean time, the other thing that no one has reported is what happens when you run two copies of BBP against two different datadirectories on the Ryzen? If anyone can test that out and report back that would be immensely helpful also. I think inblue was going to try that on a server at one point.
Hmmm... same cpu as emdes and win10. Wallet 1.0.4.0 64bit On 16 genproclimit i get 100% usage and pc reacts like he is under heavy load... but hps2 is round 19k... I have problem with 35 cpu usage limit but not on this version. It's a random behaviour on one walllet i got on other not. I think It's connected to setting of genproclimit. If genproc reacys like 1 is 1 thread i dont have limit... but if on 16 i got 45% so you must like emdes said 32 to get hash2 above 20k And still get best hps on 6 genproclimit(in wallet) but hps2 is 9k. If i rise genproclimit hps will drop and hps2 will be bigger. But my optimal is 11 genproclimit. After that hps2 is droping again... like now on 16 i got 19k I'm forking the bible miner now, testing hash speed with Dual KJV bibles in memory. |
|
|
|
While I really like the idea behind news on the block chain, I would ask you reconsider and maybe instead work it into the wallet. For the same reason we don't want Orphan Letter's in the chain four years from now, we won't want most news more than 10 days from now. Utilizing the block chain for data of temporal interest just doesn't make a lot of sense to me. Technical documents and the like, yes, but what modestly newsworthy event happened, not so much.
That did get me thinking, if there might be a way to tweak the wallet/core so that it would have a few fields (much like the prayer request field) that would be alterable.
One would be a Pool Indicator. Basically a text indication of if you were solo or pool mining, and ideally what pool you were on if mining.
Second would be a Pool Message. That would enable the pool to tell users this pool will be making Core 1.0.x.x mandatory in "y" days, or that the fee structure is changing or you need to write a letter to avoid a fee. That sort of thing.
Third would be a Coin Message. That would enable communication to the user base without having to rely on the forums. Things like, the newest version is 1.0.x.x, upgrade soon.
I think blockchain news, regardless of how old it is, is quite an awesome idea, one that adds value to BiblePay. Anyone who opposes the idea is more than welcome create a sanctuary vote with a full proposal on either enhancing the feature or changing the feature or even removing the feature. Thats the beauty of sanctuaries, you will have an equal amount of weight to voice your opinion among the rest of the community. As far as more pie in the sky features, Ill see what I can do to get this slack group jump started so you will have someone to address these issues with. |
|
|
|
|
Show Posts
