Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 518. (Read 243386 times)

newbie
Activity: 37
Merit: 0


It’s been since 4/9/18 that I have been pulling shares with no magnitude in pool, any idea how long it takes BOINC to solve enough tasks to start pulling in magnitude? Anything else I should check, any commands I should type into debug to figure out any other issues that could be causing the no mag issue? Should I just move all BBP coins to one wallet under one CPID number to see if that fixes the Magnitude issue? Should I switch pools? Thanks.

If you type exec getboincinfo, you should see positive RAC by now.
Please paste your CPID, and also, check your boinc client to see if its RAC agrees with the biblepay exec getboincinfo.
Also, you should be in the pool superblock view report.




Here is what I am getting from debug commands. Any advice on what to do next?


20:32:15

{
  "Command": "getboincinfo",
  "CPID": "eb3eee4eac3ce7c6f903198678bf4075",
  "Address": "BGn1YG311oNkgBH9G8iVeX54cPwtAGcuUf",
  "CPIDS": "eb3eee4eac3ce7c6f903198678bf4075;",
  "CPID-Age (hours)": 423291,
  "NextSuperblockHeight": 41000,
  "NextSuperblockBudget": 1179301,
  "eb3eee4eac3ce7c6f903198678bf4075_ADDRESS": "BGn1YG311oNkgBH9G8iVeX54cPwtAGcuUf",
  "eb3eee4eac3ce7c6f903198678bf4075_RAC": 0,
  "eb3eee4eac3ce7c6f903198678bf4075_TEAM": 15044,
  "eb3eee4eac3ce7c6f903198678bf4075_WCGRAC": 0,
  "eb3eee4eac3ce7c6f903198678bf4075_TaskWeight": 0,
  "eb3eee4eac3ce7c6f903198678bf4075_UTXOWeight": 0,
  "Total_RAC": 0,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "40795,40590,40385,40180,39975,39770,39565,39360",
  "Last Superblock Height": 40795,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


20:35:06

exec totalrac


20:35:07

{
  "Command": "totalrac",
  "Total RAC": 0,
  "UTXO Target": 10
}
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
Just to be sure. Is this correct?

-In order to heat mine, you need magnitude.
-To get magnitude, you need to be included in at least one superblock.
-You need to stake at least 5% (1BBP/RAC) to be included in a superblock.

Because I was thinking about people that want to heat mine first in order to get BBP to stake for Boinc-mining. There are a lot of people that think exchanges are cumbersome (convert fiat to BTC to BBP). But I think the best route for them to go is to earn free BBP (Letter Writing, Gospel Links, BiblePay University) instead of heat mining, if it's impossible to get magnitude without staking first.


Yes, this was born from the back and forth Swongle discussions for added POW security.
You do need to be in a superblock to receive magnitude, so that alludes to the fact you need at least 5% of your UTXO staked to fall in the 10% bracket.

Of course if the RAC is low, thats not a lot of BBP.  (Also you might add that unbanked CPIDs can be in a superblock without a UTXO).
Remember they can get a few BBP from Faucets also.

We might want to ask T-Mike to start an advanced faucet on PODC.org his web site to maybe compensat new Rosetta/WCG users with startup capital if they show a new CPID (to our system), he could fund them with P2P proposal funds (IE one 500,000 proposal for 6 months of new users capital etc).  
member
Activity: 126
Merit: 10
This may be well known but if you havent heard -

CEX shares an account with Bitfinex that belongs to a polish bank that is very small. Its all fishy as fishy can get. If you have not moved your assets off CEX, you need to be doing that ASAP given the volume of restrictions, sanctions, and subpoenas on Bitfinex to prove its Tether backing.
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
I found the root cause of the nt7bios-string length limit exceeded error, we will have the fix in the next release.

EDIT: Regarding the slow block completion times, where the daily superblock is 1 hour later per day:  In our June quarterly mandatory release, we will mathematically measure the slippage % and fix it permanently.


When this is fixed could you look into reducing the block reward variability.  Right now the PoDC daily super block is 1,179,301 which, since the PoDC reward and the Sanctuary rewards are supposed to both be 38.5% (equal), means the average Sanctuary reward should be 5752.  I've not seen anything remotely close to that.  In the last 5 weeks I have seen one transaction above 5000.

This daily PoDC superblock also implies the average block should be a reward of 14,942.  This is also significantly below the target maximum block reward.  The target block reward is 20,000, reducing by 1.5% compounded every 6150 blocks (monthly in coin time terms), which means we should have had 6 1.5% reductions, meaning the maximum block reward should be at 18,266, which again is far below what the PoDC Super block or MN rewards extrapolate to.  

The max coin supply at this point (block 40800) should be roughly 780M Coins but we're currently at about 555M.  While that in some ways is good for the price, etc, it's causing our maximum supply number to be really off if we continue down that path.   So I guess what I'm really asking is, if the block timing issue gets solved the rest of the way, is there any reason to not make the block reward equal to the maximum for that time period (with the understanding that the reward gets escrowed for superblocks and the like)?


The block reward variability is due to our GetBlockSubsidy being influenced by our current difficulty level.

The higher the difficulty, the lower the reward.  This is an important and useful feature and added by design, and we should of course have it in the wallet.  It will help us weather botnet attacks from heat miners over time.

I can easily see our *actual* coin emission being 20% lower than the projected emission chart, possibly higher depending on how popular we become.  If we ever became as popular as dash, it would be 50% lower than the projected (as emission would be based on 5000 BBP blocks).  

The great news is that 19.5% compounded deflation rate still works in addition to the variable block reward.

Regarding the 7 minute blocks, yes, thanks Inblue for the chart, but we are still off a tiny bit so I believe we will need a slight adjustment in June to make the blocks (approximately) 1 hour faster per day.


Nice chart Jaap!  It corresponds to the Pools Difficulty history report.

jr. member
Activity: 235
Merit: 3
When this is fixed could you look into reducing the block reward variability.  Right now the PoDC daily super block is 1,179,301 which, since the PoDC reward and the Sanctuary rewards are supposed to both be 38.5% (equal), means the average Sanctuary reward should be 5752.  I've not seen anything remotely close to that.  In the last 5 weeks I have seen one transaction above 5000.

Your post inspired me to make this chart, I hope it can be useful for someone:
(wait while it loads)



The dots are indicating individual payouts and the yellow line is a moving average.

I only took 3 sanctuaries for this chart, my own and two others I picked from the explorer, then I exported data from those addresses. I had to manually extract sanctuary payouts from other transactions. (In your own wallet though, you can just go to Transactions, type your sanctuary label in the text box at the top and then click the Export button to get a nice CSV file). I don't know if there is a way this can be done through the API or something, getting payout data from all sanctuaries without going manually through each one.

It's a small sample, but maybe these three are enough to make a somewhat informative chart.
Interesting! Although, I'll say that the trendline there doesn't make the summer look very profitable...
full member
Activity: 462
Merit: 103
When this is fixed could you look into reducing the block reward variability.  Right now the PoDC daily super block is 1,179,301 which, since the PoDC reward and the Sanctuary rewards are supposed to both be 38.5% (equal), means the average Sanctuary reward should be 5752.  I've not seen anything remotely close to that.  In the last 5 weeks I have seen one transaction above 5000.

Your post inspired me to make this chart, I hope it can be useful for someone:
(wait while it loads)



The dots are indicating individual payouts and the yellow line is a moving average.

I only took 3 sanctuaries for this chart, my own and two others I picked from the explorer, then I exported data from those addresses. I had to manually extract sanctuary payouts from other transactions. (In your own wallet though, you can just go to Transactions, type your sanctuary label in the text box at the top and then click the Export button to get a nice CSV file). I don't know if there is a way this can be done through the API or something, getting payout data from all sanctuaries without going manually through each one.

It's a small sample, but maybe these three are enough to make a somewhat informative chart.
full member
Activity: 462
Merit: 103
Sorry, my fault. I wanted to write less than 205 blocks per 24 hours. Anyway superblock is not per 24 hours but 24 hours plus something, cause superblock is one per 205 blocks.

It's okay. The point was that earlier we only had around 150 blocks per day on average and that was fixed recently. I agree on your point then, superblock is certainly meant to be every 24h.


>superblock is certainly meant to be every 24h.

It was not, you can be found the PODC Payment on transaction list in your wallet, each new payment is later than the last payment time.

From this calculation, there are only 27-28 payments in a month , not every 24hrs = 1 PODC Payment.

I said it was meant to be every 24h, not that it is every 24h. Because setting a superblock at every 205 blocks looks like an obvious intent of the developer for the superblock to be every 24 hours. As I said, I agree with SVK Noko's point, because we have about 200 blocks per day.
full member
Activity: 574
Merit: 104
Just to be sure. Is this correct?

-In order to heat mine, you need magnitude.
-To get magnitude, you need to be included in at least one superblock.
-You need to stake at least 5% (1BBP/RAC) to be included in a superblock.

Because I was thinking about people that want to heat mine first in order to get BBP to stake for Boinc-mining. There are a lot of people that think exchanges are cumbersome (convert fiat to BTC to BBP). But I think the best route for them to go is to earn free BBP (Letter Writing, Gospel Links, BiblePay University) instead of heat mining, if it's impossible to get magnitude without staking first.
newbie
Activity: 39
Merit: 0
Sorry, my fault. I wanted to write less than 205 blocks per 24 hours. Anyway superblock is not per 24 hours but 24 hours plus something, cause superblock is one per 205 blocks.

It's okay. The point was that earlier we only had around 150 blocks per day on average and that was fixed recently. I agree on your point then, superblock is certainly meant to be every 24h.


>superblock is certainly meant to be every 24h.

It was not, you can be found the PODC Payment on transaction list in your wallet, each new payment is later than the last payment time.

From this calculation, there are only 27-28 payments in a month , not every 24hrs = 1 PODC Payment.
newbie
Activity: 153
Merit: 0
One simple question. Could somebody tell me the data consumption of rosetta or wcg task (or tasks) during the communication with server? Do somebody have this statistics?

Thank you.


Rosetta packets stored at my computer are far bigger than than wcg packets at least 10x. I store for 1 day and at the moment I have 3.16 GB rosetta tasks and 460 MB wcg tasks.

Hopefully this gives an estimate.
full member
Activity: 462
Merit: 103
Sorry, my fault. I wanted to write less than 205 blocks per 24 hours. Anyway superblock is not per 24 hours but 24 hours plus something, cause superblock is one per 205 blocks.

It's okay. The point was that earlier we only had around 150 blocks per day on average and that was fixed recently. I agree on your point then, superblock certainly seems to be meant to be every 24h.
newbie
Activity: 267
Merit: 0
[...] if the block timing issue gets solved the rest of the way [...]

Rob has solved this already, we have about 200 blocks per day.

Solved as solved. We have less then 200 blocks per 24 hours.

Last 15 days



01.04: 37849-38048 (200)
02.04: 38049-38245 (197)
03.04: 38246-38445 (200)
04.04: 38446-38651 (206)
05.04: 38652-38844 (193)
06.04: 38845-39042 (198)
07.04: 39043-39244 (202)
08.04: 39245-39439 (195)
09.04: 39440-39642 (203)
10.04: 39643-39843 (201)
11.04: 39844-40043 (200)
12.04: 40044-40241 (198)
13.04: 40242-40443 (202)
14.04: 40444-40643 (200)
15.04: 40644-40837 (194)



Average:
199.27 blocks per day

Please stop spreading FUD.


Sorry, my fault. I wanted to write less than 205 blocks per 24 hours. Anyway superblock is not per 24 hours but 24 hours plus something, cause superblock is one per 205 blocks.
newbie
Activity: 267
Merit: 0
One simple question. Could somebody tell me the data consumption of rosetta or wcg task (or tasks) during the communication with server? Do somebody have this statistics?

Thank you.
full member
Activity: 462
Merit: 103
[...] if the block timing issue gets solved the rest of the way [...]

Rob has solved this already, we have about 200 blocks per day.

Solved as solved. We have less then 200 blocks per 24 hours.

Last 15 days


01.04: 37849-38048 (200)
02.04: 38049-38245 (197)
03.04: 38246-38445 (200)
04.04: 38446-38651 (206)
05.04: 38652-38844 (193)
06.04: 38845-39042 (198)
07.04: 39043-39244 (202)
08.04: 39245-39439 (195)
09.04: 39440-39642 (203)
10.04: 39643-39843 (201)
11.04: 39844-40043 (200)
12.04: 40044-40241 (198)
13.04: 40242-40443 (202)
14.04: 40444-40643 (200)
15.04: 40644-40837 (194)


Average:
199.27 blocks per day

Please stop spreading lies.
newbie
Activity: 267
Merit: 0
[...] if the block timing issue gets solved the rest of the way [...]

Rob has solved this already, we have about 200 blocks per day.

Solved as solved. We have less then 200 blocks per 24 hours.
full member
Activity: 462
Merit: 103
[...] if the block timing issue gets solved the rest of the way [...]

Rob has solved this already, we have about 200 blocks per day.
full member
Activity: 406
Merit: 101
I found the root cause of the nt7bios-string length limit exceeded error, we will have the fix in the next release.

EDIT: Regarding the slow block completion times, where the daily superblock is 1 hour later per day:  In our June quarterly mandatory release, we will mathematically measure the slippage % and fix it permanently.


When this is fixed could you look into reducing the block reward variability.  Right now the PoDC daily super block is 1,179,301 which, since the PoDC reward and the Sanctuary rewards are supposed to both be 38.5% (equal), means the average Sanctuary reward should be 5752.  I've not seen anything remotely close to that.  In the last 5 weeks I have seen one transaction above 5000.

This daily PoDC superblock also implies the average block should be a reward of 14,942.  This is also significantly below the target maximum block reward.  The target block reward is 20,000, reducing by 1.5% compounded every 6150 blocks (monthly in coin time terms), which means we should have had 6 1.5% reductions, meaning the maximum block reward should be at 18,266, which again is far below what the PoDC Super block or MN rewards extrapolate to.  

The max coin supply at this point (block 40800) should be roughly 780M Coins but we're currently at about 555M.  While that in some ways is good for the price, etc, it's causing our maximum supply number to be really off if we continue down that path.   So I guess what I'm really asking is, if the block timing issue gets solved the rest of the way, is there any reason to not make the block reward equal to the maximum for that time period (with the understanding that the reward gets escrowed for superblocks and the like)?
member
Activity: 489
Merit: 12
Purepool question .. can you have multiple miners using the same receiving address?
Yes. Just copy wallet.dat to each miner from your primary wallet.
You can set id to each miner by
Code:
workerid=address/minerid

Thanks vahtis! Also posted the question in the new purepool forum at: http://forum.biblepay.org/index.php?topic=157.0
full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
** Purepool support forum created! **

Forum: http://forum.biblepay.org/index.php?topic=157.0

I will enter this in the OP for reference.
full member
Activity: 406
Merit: 101
All time high woo!

Well, not quite an all time high in either price (USD) nor price (BTC) but very definitely the strongest values since January.
Jump to: