|
Ive noticed on the pool that my workers "Hashes Per Sec2" is anywhere between 10-90% of its "Hashes Per Sec"
What is Hashes Per Sec2?
|
|
|
|
I dont think there is a surefire way to minimize orphan donation risk 100%, but we can probably minimize it a good amount? the future value of BiblePay coins could be very volatile I googled how long a sponorship lasts, and it lasts until an orphan is 18-22 years old https://www.compassion.com/sponsor_a_child/sponsorship-faq.htm#faq-tcm:5-308790so orphans are ages 0 to 22, to be certain our donation would never falter, we wouldn't want to sponsor an orphan until we could pay for the whole X years worth of their full remaining sponsorship, which could be on average 11 years, or potentially more or less depending on the age distribution of orphans Im not sure if its possible to pay up front?, and even if it was, would it be better for the worth to be stored in coins? or exchanged into dollars? This is all very interesting  |
|
|
|
|
The dev has been doing fantastic work!
Yeah at the current rate, since so many miners now, 70k hps will take like a week and a half to get 1 block O_O
|
|
|
|
the ROI has definitely been squeezed out for renting cloud machine, Ive been debating getting a physical machine, Im not sure which CPU to get, looks like 8 core is best bang for buck, and Id finally get to play with overclocking Im totally new to mining LOL, this has been an interesting project to follow |
|
|
|
I believe log1 is baz on the pool, looks like he got part of the last 2 blocks mined by the pool |
|
|
|
log1k, Ive heard there are 550+ miners, network hash is super high now, with 700k hps I think youll get 1 block a day (my understanding is that current network hash is 100x higher than it currently shows) theres been a lot of push for dev to make a hash pool because solo mining has gotten so hard, the pool is mostly working now |
|
|
|
|
Try adding these 2 lines to your biblepay.conf file:
addnode=node.biblepay.org
addnode=biblepay.inspect.network
|
|
|
|
|
I went missing on the leaderboard and HPS showed 0, and now its back, weird >.>
|
|
|
|
|
Innteeressstinnngg, so your using the spot request price hehe,
You were able to automate if your spot instance gets terminated?
I tried to look into it but couldnt figure it out, props to you!
|
|
|
|
|
log1k, isnt the price for those like 3 dollars an hour each? O_O
|
|
|
|
hmmm, pool website is working for me, reloaded my wallet and typed mininginfo and saw the pool info getmininginfo { "blocks": 3272, "currentblocksize": 1000, "currentblocktx": 0, "difficulty": 0.02596730643410695, "errors": "", "genproclimit": 2, "network_khashps": 1457.753675257911, "hashps": 24528.80481368526, "minerstarttime": "08-15-2017 19:27:40", "pooledtx": 0, "testnet": false, "chain": "main", "biblepay-generate": true, "poolinfo1": "", "poolinfo2": "", "poolinfo3": "", "miningpulse": 715, "poolmining": true } and then on the Account page of the pool website: http://pool.biblepay.org/Account.aspxShould be able to see your workers and their HPS Workers - main Username: togo_w1 Threads: 1 HPS: 24502.98 Notes: It took a few minutes for this to finally show up with an HPS after restarting my wallet/miner |
|
|
|
https://bitcointalk.org/index.php?topic=2070177.msg20874585#msg20874585Current pool is pointed at production chain, its still in testing but seems to be working quite well 1. Downloaded latest wallet from http://biblepay.org/2. Set up account and worker ID on pool website: http://pool.biblepay.org3. Set in biblepay.conf: poolport=80 pool=http://pool.biblepay.org workerid=the_worker_id gen=1 genproclimit=1 4. Start your wallet, boom! Notes: - if the pool goes down it should put you on solo mining - about 5% of miners are currently on the pool so far - theres currently a limit of 24 threads per worker - there is currently an issue where 10% of miners slowly get knocked off the pool, dev is working on that issue today - sometimes to log back into your account on pool website you have to press logout first - the network hash rate has been identified as being wrong and may be 100x what it shows - pool is still in testing Report any issues in BiblePay Pool Testing Thread: https://bitcointalk.org/index.php?topic=2070177.new#new
|
|
|
|
I agree with all this, except that I think the pool is receiving the correct amount of blocks for the userbases network hash level, as I really feel that only 5% of our base came over. Since we have not actually advertised it yet as ready for prod, I think 95% is still solo mining, but then I could be wrong about that.
If 5% really did come over, the wallet hash rate would be about 20* higher than the sum of the pool. (You sum to 8.2 Mh/s). That would put us at 165,144,280 or 165Mh/s total network (8257214*20). The old getnetworkhashps (btw that command still works) bears 12,882 currently in prod - if we multiply * 10000, we arrive at 128,820,000 which would be closer to what I expect.
Looking at the code for networkhashps, it just subtracts the old chainwork (from the beginning of the sample period) from the latest chainwork (from the end of the sample period) and does some averaging to arrive at how many hashes it should take to do that much chainwork. What is probably happening is the PoBh algorithm is much harder to solve than the standard sha256 or x11 hash. Apparently 1000* harder.
I believe to solve this, we will need to allow more of the network to jump in the pool and get a feel for how this thing goes, and then release a fix for networkhashps. If all goes well we will just multiply it * 10000, but in the mean time, let me look at the actual work done in the loop by the biblehash vs the x11 loop. Its leading me to believe that a CPU must perform 1000 iterations of the loop to hash one bible hash as compared to one x11 hash. That actually sounds relatively feasible.
EDIT: I have an idea that might help shed light. I can put a counter metric inside our PoBh mining loop that will shed light on how many x11 hashes it takes to hash one bible hash, and that should clarify this a great degree.
Im glad to hear youve potentially found the issue with the total network hash! You're doing fantastic work, I look forward to the future of this project! |
|
|
|
"blocks": 2997,
"currentblocksize": 1000,
"currentblocktx": 0,
"difficulty": 0.02491203714966913,
"errors": "",
"genproclimit": 24,
"network_khashps": 12961.72806720412,
"hashps": 281015.3268310414,
"minerstarttime": "08-13-2017 21:15:18",
"pooledtx": 0,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "",
"poolinfo2": "",
"poolinfo3": "",
"poolmining": false
No blocks in 24 hours, is it normal?
Let's do some maths: How much block / daY? : (1440 mins/day) / (7mins/blocks) = approx 205 blocks/day Your hasrate% vs network hashrate: (281 015 hash/s) / (12 961 000 hash/s)= approx 2%So you should get 2% of block = 4 blocks / day in average If it persist, maybe it is poor connection to the internet? There have been at least 3-4 other people saying that block reward rate doesnt seem right as well, I think they will figure out the issue once the pool is up, will be easier to identify then. I too am seeing less block rewards then I should be getting, mathematically/statistically. |
|
|
|
|
Something strange is definitely happening, saw blocks jump from 2618 to 2625
|
|
|
|
Is the explorer reporting correctly? http://biblepay.inspect.network/Im seeing some weird behavior, blocks with same timestamp, blocks with multiple recipients, amounts higher than 19k |
|
|
|
|
Show Posts
