Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 709. (Read 243376 times)
January 14, 2018, 07:27:18 PM
I'm on board two days from now, but last few hours (may be 3 or 4).. blocks are passing, i am hashing... with "0" in "Coins mined in last hour" and no move in Total Balance.
January 14, 2018, 07:18:22 PM
Anyone who has trouble logging in to the pool with chrome or received an HTTP 500 Error:
https://pool.biblepay.org
Please press:
CTRL-F5
from the login page - then Log In.
https://pool.biblepay.org
Please press:
CTRL-F5
from the login page - then Log In.
January 14, 2018, 07:16:56 PM
I'm running 1.0.8.0b. Everything is looking "fine". I can see my hash rate in pool, my shares are moving, but... not a single coin was mined. At least....not for me.
02:09:16

getmininginfo
02:09:16

{
"blocks": 25743,
"currentblocksize": 6005,
"currentblocktx": 22,
"difficulty": 621.3203482366829,
"errors": "",
"genproclimit": 3,
"networkhashps": 90407777371.21313,
"hashps": 2267.96281673131,
"minerstarttime": "01-14-2018 23:40:34",
"hashcounter": 3906067,
"competetive_mining": true,
"competetivemining_hash_counter": 3758955,
"global_competetive_mining_tithe": 80,
"competetive_mining_ratio": 0,
"pooledtx": 22,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BLpu2s9FFs1PPjfovGgtfTD2aB43Efybuf; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; ",
"poolinfo2": "Submitting Solution 01-15-2018 00:08:45; Submitting Solution 01-15-2018 00:07:47; Submitting Solution 01-15-2018 00:07:59; ",
"poolinfo3": "",
"miningpulse": 674,
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"poolmining_use_ssl": true
}
Total Balance is frozen.
P.S.
Please, excuse my bad English.
02:09:16

getmininginfo
02:09:16

{
"blocks": 25743,
"currentblocksize": 6005,
"currentblocktx": 22,
"difficulty": 621.3203482366829,
"errors": "",
"genproclimit": 3,
"networkhashps": 90407777371.21313,
"hashps": 2267.96281673131,
"minerstarttime": "01-14-2018 23:40:34",
"hashcounter": 3906067,
"competetive_mining": true,
"competetivemining_hash_counter": 3758955,
"global_competetive_mining_tithe": 80,
"competetive_mining_ratio": 0,
"pooledtx": 22,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BLpu2s9FFs1PPjfovGgtfTD2aB43Efybuf; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; ",
"poolinfo2": "Submitting Solution 01-15-2018 00:08:45; Submitting Solution 01-15-2018 00:07:47; Submitting Solution 01-15-2018 00:07:59; ",
"poolinfo3": "",
"miningpulse": 674,
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"poolmining_use_ssl": true
}
Total Balance is frozen.
P.S.
Please, excuse my bad English.
Your mining_credit comes in a bigger batch once we solve a block with you on board
, so you should be fine... January 14, 2018, 07:14:49 PM
I just found out that the monthly budget decreases every time by exactly 1.5%:
This is an excellent deflationary feature, I like it. @Rob: I noticed that on the Proposals list page there is a fixed amount from the previous budget, so I guess it should be a dynamic value.
I was thinking: because we have 150 blocks/day, instead of 205, our monthly budget is actually every 41 days (6150 / 150) instead of every 30 days (6150 / 205) like it was meant to be. Since the block time issue seems to be non-trivial, maybe we could consider lowering the interval between superblocks from 6150 to 4500? (4500 / 150 = 30)
On the positive side of things, in the current situation where both exchanges are down, it's good that we still have about 33 days left until the next superblock, because right now it's difficult to determine BBP price for making proposals.
Code:
getsuperblockbudget 24600
5789219.786313
getsuperblockbudget 30750
5702381.489514
getsuperblockbudget 36900
5616845.767143
getsuperblockbudget 43050
5532593.08065
...
This is an excellent deflationary feature, I like it. @Rob: I noticed that on the Proposals list page there is a fixed amount from the previous budget, so I guess it should be a dynamic value.
I was thinking: because we have 150 blocks/day, instead of 205, our monthly budget is actually every 41 days (6150 / 150) instead of every 30 days (6150 / 205) like it was meant to be. Since the block time issue seems to be non-trivial, maybe we could consider lowering the interval between superblocks from 6150 to 4500? (4500 / 150 = 30)
On the positive side of things, in the current situation where both exchanges are down, it's good that we still have about 33 days left until the next superblock, because right now it's difficult to determine BBP price for making proposals.
Great points you make about 41 physical days. My main point of consternation is being able to pay Compassion with a constrained and lagging budget.
Let's see what kind of price we open at on c-cex, and we can try to formulate a game plan between now and March. I dont want to plan on any mandatories until the end of the 1st quarter, but if need be we can evaluate ideas that fix it around the end of March unless our price is so high that we don't need on-time budgets.
January 14, 2018, 07:13:18 PM
I'm running 1.0.8.0b. Everything is looking "fine". I can see my hash rate in pool, my shares are moving, but... not a single coin was mined. At least....not for me.
02:09:16

getmininginfo
02:09:16

{
"blocks": 25743,
"currentblocksize": 6005,
"currentblocktx": 22,
"difficulty": 621.3203482366829,
"errors": "",
"genproclimit": 3,
"networkhashps": 90407777371.21313,
"hashps": 2267.96281673131,
"minerstarttime": "01-14-2018 23:40:34",
"hashcounter": 3906067,
"competetive_mining": true,
"competetivemining_hash_counter": 3758955,
"global_competetive_mining_tithe": 80,
"competetive_mining_ratio": 0,
"pooledtx": 22,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BLpu2s9FFs1PPjfovGgtfTD2aB43Efybuf; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; ",
"poolinfo2": "Submitting Solution 01-15-2018 00:08:45; Submitting Solution 01-15-2018 00:07:47; Submitting Solution 01-15-2018 00:07:59; ",
"poolinfo3": "",
"miningpulse": 674,
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"poolmining_use_ssl": true
}
Total Balance is frozen.
P.S.
Please, excuse my bad English.
02:09:16

getmininginfo
02:09:16

{
"blocks": 25743,
"currentblocksize": 6005,
"currentblocktx": 22,
"difficulty": 621.3203482366829,
"errors": "",
"genproclimit": 3,
"networkhashps": 90407777371.21313,
"hashps": 2267.96281673131,
"minerstarttime": "01-14-2018 23:40:34",
"hashcounter": 3906067,
"competetive_mining": true,
"competetivemining_hash_counter": 3758955,
"global_competetive_mining_tithe": 80,
"competetive_mining_ratio": 0,
"pooledtx": 22,
"testnet": false,
"chain": "main",
"biblepay-generate": true,
"poolinfo1": "BLpu2s9FFs1PPjfovGgtfTD2aB43Efybuf; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; BF72gCHawYN19uhNU6tCGmmZynVczKjtkt; ",
"poolinfo2": "Submitting Solution 01-15-2018 00:08:45; Submitting Solution 01-15-2018 00:07:47; Submitting Solution 01-15-2018 00:07:59; ",
"poolinfo3": "",
"miningpulse": 674,
"poolmining": true,
"pool_url": "https://pool.biblepay.org",
"poolmining_use_ssl": true
}
Total Balance is frozen.
P.S.
Please, excuse my bad English.
January 14, 2018, 07:08:30 PM
"Regarding the dynamics of solving blocks on prior versions I will go into detail on that after church."
So although we required a mandatory upgrade between 1.0.7.7 and 1.0.7.8+, this was intended to upgrade instantsend, but not to kick the miners off the current block algorithm.
So the enforcement in this case was set for a protocol upgrade (for sanctuaries) and a soft-hangup on old versions.
This means that blocks solved on prior versions are not discarded unless mined on a fork. So when we get to the point of a 50% upgrade level, those old versions are going to be wasting hashpower. I see we have 63% right now on 1.0.7.1 that has not upgraded.
So this effect will come into play when the 63% solo level drops to 49%. That hash power is going to go to waste and provide more coins for the early birds who did upgrade.
Now here is a Very interesting effect that is happening right now and might answer some of our network questions. I flipped the switch on the pool requiring 1.0.7.9+ to hash against the pool. There are 63% now that are either solo mining or have a private pool, as they are still solving blocks at the 63% level on the network currently right this second (and cant be in the pool as the pool refuses the connection). That explains where 63% out of our 75% is, but we still do not know if its a solo group, a botnet or a private pool.
So, you think, that those last 25 block without pool hit, is because the pool has "small" hashpower?
Well the pool dropped from 4000 miners to 1900 miners, and the 24hr percent solved dropped from 25% to 19%.
But part of what I believe is right now those 63% that are mining outside of the main pool are still solving those other blocks... But once 1.0.8.0b becomes exactly 50% of the network, we will have two live chains and only one is going to win (the official one).
exec versionreport
January 14, 2018, 07:05:55 PM
mandatory to who? all or only sanctuaries?
and what block number to apply?
Sorry for the ambigious post and zero day deadline.and what block number to apply?
Awesome. I'm in the process of upgrading now.
For clarity, will older versions not be able to mine unless they upgrade?
(Btw, up to 100 votes to get BBP on next.exchange! Thanks and keep it up all
Thanks
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp#comment30547 )
I couldnt re-vote but I sent it to 7 cryptofriends, please vote all, we only need 100 more votes:
https://nextexchange.featureupvote.com/suggestions/3384/biblepay-bbp#comment30547 )[/b][/size]
January 14, 2018, 07:02:50 PM
"Regarding the dynamics of solving blocks on prior versions I will go into detail on that after church."
So although we required a mandatory upgrade between 1.0.7.7 and 1.0.7.8+, this was intended to upgrade instantsend, but not to kick the miners off the current block algorithm.
So the enforcement in this case was set for a protocol upgrade (for sanctuaries) and a soft-hangup on old versions.
This means that blocks solved on prior versions are not discarded unless mined on a fork. So when we get to the point of a 50% upgrade level, those old versions are going to be wasting hashpower. I see we have 63% right now on 1.0.7.1 that has not upgraded.
So this effect will come into play when the 63% solo level drops to 49%. That hash power is going to go to waste and provide more coins for the early birds who did upgrade.
Now here is a Very interesting effect that is happening right now and might answer some of our network questions. I flipped the switch on the pool requiring 1.0.7.9+ to hash against the pool. There are 63% now that are either solo mining or have a private pool, as they are still solving blocks at the 63% level on the network currently right this second (and cant be in the pool as the pool refuses the connection). That explains where 63% out of our 75% is, but we still do not know if its a solo group, a botnet or a private pool.
So, you think, that those last 25 block without pool hit, is because the pool has "small" hashpower?
January 14, 2018, 06:58:46 PM
Hi again everybody.
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I can't log on to the pool via Google Chrome.
Works for me with Firefox though
Btw: My Pi is running 1.0.8.0 (without b) now, no problems so far (except that it took quite a long time to sync...); HPS2 almost 25k (but right now with fewer miners every worker has higher HPS2 obviously).
Oh wait, I just realized at noon the pool needed a new .js file... For the pool in chrome, please go to the home page, click ctrl-f5 for a complete refresh, then login and you should be good.
January 14, 2018, 06:56:58 PM
"Regarding the dynamics of solving blocks on prior versions I will go into detail on that after church."
So although we required a mandatory upgrade between 1.0.7.7 and 1.0.7.8+, this was intended to upgrade instantsend, but not to kick the miners off the current block algorithm.
So the enforcement in this case was set for a protocol upgrade (for sanctuaries) and a soft-hangup on old versions.
This means that blocks solved on prior versions are not discarded unless mined on a fork. So when we get to the point of a 50% upgrade level, those old versions are going to be wasting hashpower. I see we have 63% right now on 1.0.7.1 that has not upgraded.
So this effect will come into play when the 63% solo level drops to 49%. That hash power is going to go to waste and provide more coins for the early birds who did upgrade.
Now here is a Very interesting effect that is happening right now and might answer some of our network questions. I flipped the switch on the pool requiring 1.0.7.9+ to hash against the pool. There are 63% now that are either solo mining or have a private pool, as they are still solving blocks at the 63% level on the network currently right this second (and cant be in the pool as the pool refuses the connection). That explains where 63% out of our 75% is, but we still do not know if its a solo group, a botnet or a private pool.
January 14, 2018, 06:52:26 PM
Hi again everybody.
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I can't log on to the pool via Google Chrome.
Works for me with Firefox though
Btw: My Pi is running 1.0.8.0 (without b) now, no problems so far (except that it took quite a long time to sync...); HPS2 almost 25k (but right now with fewer miners every worker has higher HPS2 obviously).
January 14, 2018, 06:37:47 PM
Biblepay - Mandatory Upgrade
1.0.8.0b
- Final fix for instantsend security vulnerability
- Fix crash we introduced today
** This version does fix the crash issue, and I confirm I can finally send instantsends successfully. All credit to God. **
(I mentioned earlier that you can continue on 1.0.7.9 for a while if need be, but Sanctuaries should upgrade asap.
Please upgrade if possible).
1.0.8.0b
- Final fix for instantsend security vulnerability
- Fix crash we introduced today
** This version does fix the crash issue, and I confirm I can finally send instantsends successfully. All credit to God. **
(I mentioned earlier that you can continue on 1.0.7.9 for a while if need be, but Sanctuaries should upgrade asap.
Please upgrade if possible).
Hi Rob, upgrading my sanctuary and controller wallet now.
Just for clarity (I sometime misunderstand things in general), regular miners can simply continue on 1.0.7.9?
Or is there a block number where miners on 1.0.7.9 will stop mining?
Thanks
.
January 14, 2018, 06:29:59 PM
Hi again everybody.
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I can't log on to the pool via Google Chrome.
Works for me with Firefox though
Alright Ill check into it now. I have a backlog of pool issues to look at next.
Thanks...
January 14, 2018, 06:29:29 PM
Biblepay - Mandatory Upgrade
1.0.8.0b
- Final fix for instantsend security vulnerability
- Fix crash we introduced today
** This version does fix the crash issue, and I confirm I can finally send instantsends successfully. All credit to God. **
(I mentioned earlier that you can continue on 1.0.7.9 for a while if need be, but Sanctuaries should upgrade asap.
Please upgrade if possible).
1.0.8.0b
- Final fix for instantsend security vulnerability
- Fix crash we introduced today
** This version does fix the crash issue, and I confirm I can finally send instantsends successfully. All credit to God. **
(I mentioned earlier that you can continue on 1.0.7.9 for a while if need be, but Sanctuaries should upgrade asap.
Please upgrade if possible).
January 14, 2018, 06:26:52 PM
Hi again everybody.
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I can't log on to the pool via Google Chrome.
Works for me with Firefox though
January 14, 2018, 06:19:41 PM
Hi again everybody.
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
I hate to sound like a bother, but could anybody explain if the pool is down or if I just cannot get into the pool at this point to mine?
I hope everyone's having a fine Sunday.
Jazz
January 14, 2018, 05:32:34 PM
somebody just buy about 10 000 000 bbp for 80000$ , isnt this required amount for instant send security bug?
, isnt this required amount for instant send security bug?@capulo ... be helpful and post some evidence for this
it was on c-cex, somebody spent few bitcoins to buy many times 700k bbp
Thanks @capulo, I appreciate your reply. I didn't realize c-cex was open for trading BBP.
January 14, 2018, 04:55:12 PM
Rob, thank you for the amazing coding work, and even more importantly, for perseverance.
January 14, 2018, 04:19:30 PM
I rolled back to 1.0.7.9 on the official web site.
Please try now.
As far as the bug, I found the issue- we will have this final release out in a few hours.
Linux is ready now if anyone wants the unofficial version for testing (1.0.8.0b).
Please try now.
As far as the bug, I found the issue- we will have this final release out in a few hours.
Linux is ready now if anyone wants the unofficial version for testing (1.0.8.0b).
Good find Rob! Can't make an omelette without breaking some eggs!
January 14, 2018, 04:17:20 PM
pool is down?
Jump to: