BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[dave_bbp]

Quick question: What will happen to the pool miners/workers once abn weight requirement kicks in? Will all workers not meeting it automatically be rejected by the pool?


P.S.: Is the sanctuary payment gonna improve again in the future? Right now sancs pay half of what they paid before Evo and I don't think investors gonna like that very much.

[1713963434]

1713963434

[1713963434]

1713963434

[capulo]

... that node will just throw an error once per minute (when the miner is enabled) something to the effect of :  ABN weight not sufficient to create a block. ...

in this case, will machine save power (cpu 0%) or it will mine as usually but just cant hit block?

[bible_pay]

if i set one wallet for miners and put some coins there, how it will work? i red somewhere that abn will be 256k
so if i have now
  "Command": "getabnweight",
  "weight": 26944.78025462963,
  "total_required": 18490

then i will wait until weight will be 256k? and then one miner will be able to find block? and then some tx spend my weight to 0 and i will need to wait again until 256k?
and for higher frequency of blocks i will need to stake more coins so weight will be increasing faster?

Yes, exactly, in about 250 more blocks the ABN requirement starts and requires 256K ABN weight in order to mine a block.

So basically in your example here, that node will just throw an error once per minute (when the miner is enabled) something to the effect of :  ABN weight not sufficient to create a block.  (Note that if we have a late block, > 60 mins, those miners who have insufficient weight will actually turn on automatically because anyone can mine a late block).

So yes, if you deposit more into that miner, then it will mine (after block 126,000).

Note one other very important nuance:  Your ABN weight will not be reset to 0 unless you actually solve a block.  The weight keeps being recycled as the best block changes and never
 spent.  If you solve a block, your ABN transmission gets cashed in inside that block and therefore your abn weight recycles back to 0.  Obviously if you had 512,000 in the mining wallet(s) you would have enough to keep mining while its recycling...etc.

Hi Rob, So it means recycled per block ? if the miner solve a blocks then next block+ with ABN weight turn to 0, how about the block+1 still have chance to mine ?

To be specific, the original vins that get spent in the block you solved reset to 0 coin age, but if you have a wallet with other unspent coins in it, that keeps your coin*age above 256K then yes, height+1 would mean the miner is still mining.

To make it easier to understand, the response from getabnweight would need to be > 512K so that when the 256k coin age is spent the miner still has at the very least 256K to continue mining.  As time goes on the original 256k would be aging again (increasing total coin age once again).  Best bet is to put more than enough in a shared wallet for mining, to get a feel for it and then look at the logs scanning for "ABN" to see if no errors exist. 

Also getmininginfo will show any ABN errors.

[bible_pay]

... that node will just throw an error once per minute (when the miner is enabled) something to the effect of :  ABN weight not sufficient to create a block. ...

in this case, will machine save power (cpu 0%) or it will mine as usually but just cant hit block?

It would save power, it would sleep 30seconds while its taking a look at coin age over and over.

(Unless a late block is encountered), then it would wake up.

[bible_pay]

Quick question: What will happen to the pool miners/workers once abn weight requirement kicks in? Will all workers not meeting it automatically be rejected by the pool?


P.S.: Is the sanctuary payment gonna improve again in the future? Right now sancs pay half of what they paid before Evo and I don't think investors gonna like that very much.

On the sanc payment, impho, as things currently are with QT in place, those rewards would not improve; except in the case that If our price rose above the AUP trigger (.01 cent), the biblepay wallet would emit more coins per block.  This lower Sanc share is due to the GSC contract escrow % being held back at the gross level per block.  I understand both sides, that sancs feel they should get the gross reward first, then the GSC gets the net.   Since I am a sanc owner myself I feel that if the community feels this is important to discuss a higher reward, I encourage someone here to make a forum proposal, proposing a change, and then voted on (as I don't want to spearhead this myself).

On the ABN effects on the pool, the pool will keep working, but a small change needs deployed tonight; this basically rejects any solutions submitted that don't contain the minimum ABN weight in the serialized block.  So the pool miner who has insufficient pool weight will also end up sleeping.

[bible_pay]

I added an RPC command to show the ROI in steps of 1000 per tithe amount.  This will be in the next version.

[bible_pay]

... that node will just throw an error once per minute (when the miner is enabled) something to the effect of :  ABN weight not sufficient to create a block. ...

in this case, will machine save power (cpu 0%) or it will mine as usually but just cant hit block?

It would save power, it would sleep 30seconds while its taking a look at coin age over and over.

(Unless a late block is encountered), then it would wake up.

When BBP sleeps, does this mean it devotes 0% to mining? I could perhaps run BOINC side by side and crunch scientific tasks when BBP is sleeping?

Yes, it devotes 0% to mining, so you could run boinc and get work out of it yes.  I believe the wallet should take no more than 1% cpu time when the miner is off (roughly, depending on the machine).

[MIP]

Almost 27M BBP 24h volume on SouthXChange, this is good sign.

Edit: 45M now!

[bible_pay]

Reminder: 23K reward to write a letter in the pool, please write one and upvote the others.

[bible_pay]

Code:

"Command": "roi",
  "Notes": "Please note this information is for the POG campaign only, and based on yesterday's participation levels.",
  "Contract Height": 125890,
  "Total Paid": 960398.4899999996,
  "Total Points": 4701763214,
  "Payment Per Point": 0.0002042634744217469,
  "My Current Coin Age": 4274157.274166666,
  "My free balance": 6145459,
  "Sanctuary Reward @125889.00": 3116,
  "Sanctuary ROI Annualized %": 25.27421660572964,
  "Tithe 2.00 Points": 5385100.720283875,
  "Tithe 2.00 Reward": 1099.979383236236,
  "Tithe 2.00 Daily ROI %": 54898.96916181182,
  "Balance 6145459.00 Annualized ROI %": 6.521278148324255,
  "Tithe 1002.00 Points": 42770048.14831872,
  "Tithe 1002.00 Reward": 8736.358635960987,
  "Tithe 1002.00 Daily ROI %": 771.8920794372242,
  "Balance 6145459.00 Annualized ROI %": 45.93702280213342,
  "Tithe 2002.00 Points": 53868951.55844972,
  "Tithe 2002.00 Reward": 11003.45920878572,
  "Tithe 2002.00 Daily ROI %": 449.6233371021838,
  "Balance 6145459.00 Annualized ROI %": 53.46277000964105,
  "Tithe 3002.00 Points": 61657710.54789208,
  "Tithe 3002.00 Reward": 12594.41818140283,
  "Tithe 3002.00 Daily ROI %": 319.5342498801742,
  "Balance 6145459.00 Annualized ROI %": 56.97267911496982,
  "Tithe 4002.00 Points": 67859323.65167531,
  "Tithe 4002.00 Reward": 13861.18122100103,
  "Tithe 4002.00 Daily ROI %": 246.3563523488513,
  "Balance 6145459.00 Annualized ROI %": 58.55707678898152,
  "Tithe 5002.00 Points": 73096804.95385367,
  "Tithe 5002.00 Reward": 14931.00734900291,
  "Tithe 5002.00 Daily ROI %": 198.5007466813857,
  "Tithe 9002.00 Points": 88912639.17760453,
  "Tithe 9002.00 Reward": 18161.60459842464,
  "Tithe 9002.00 Daily ROI %": 101.7507731440195,
  "Balance 6145459.00 Annualized ROI %": 22.62080688618299,
  "Tithe 21002.00 Points": 107706501.8026414,
  "Tithe 21002.00 Reward": 22000.50427601968,
  "Tithe 21002.00 Daily ROI %": 4.754329473477215,
  "Balance 6145459.00 Annualized ROI %": -15.07367834580864,
  "Tithe 33002.00 Points": 129791678.5588794,
  "Tithe 33002.00 Reward": 26511.69921346727,
  "Tithe 33002.00 Daily ROI %": -19.66638623881198,
  "Balance 6145459.00 Annualized ROI %": -38.54813427417621,
  "Tithe 39002.00 Points": 138468818.4274658,
  "Tithe 39002.00 Reward": 28284.12195106818,
  "Tithe 39002.00 Daily ROI %": -27.48032933934625,

Explanation for this command in the next version:

exec roi

Annualized Sanctuary ROI: 25.2% - This is the ROI a sanctuary receives per year as of the last superblock.
Tithe 2BBP in POG, Daily ROI% = 54898%.  This is the ROI you would receive if you tithed 2BBP and had the coin age (4,274,000 MM) in the example, the ROI by which you receive a reward of 1099 bbp on a 2bbp tithe = 54898%.  However if you want the ROI on the free wallet balance ( 6.14MM bbp), see the Balance 6,145,459 Annualized ROI : 6.52% (this is more realistic, and it means how much roi you receive annually on your free balance if you tithed 2 bbp).
These figures are all caclulated as of the last superblock.

Then we increment in steps, showing you the ROI increases to 56% with a 3002 bbp tithe.  But notice what happens with a 9002 bbp tithe:  22.6% roi (it decreases).
Then with a 39002 bbp tithe:  a -38.48% roi (due to the diminishing reward and the cost of the tithe itself being more than the reward due to GSC participation levels as of the last block).

This next version should be out this evening.

[dave_bbp]

That's awesome stuff, Rob. Looking forward to some new statistics.

Today I had another weird experience with the POG system, which I don't understand. Here's what's happened:
Yesterday evening I had some issues with my masternode. So I decided to temporarily take it down and just once test how some of those now "free" coins would work in POG. I chose the MN coins from the inputs and manually sent 50k BBP via "exec sendgscc". After that I waited a couple of hours and was very pleased when the leaderboard showed my account with "owed: 200k". However, in the following payment I only received a mere 780 BBP.  
Since yesterday I did not send out another POG donation, but after the last superblock my name came up again in the leaderboard, now showing "owed: 300k". So I had hoped, maybe tomorrow I get some of my 50k back.

Unfortunately right now I'm completely missing from the leaderboard. So does this mean I lost my 50k into Oblivion? For me the system is still completely non-transparent.

[inblue]

I thought that pog_coinagepercentage was in fact free balance percentage, because that's how I think it worked for the first 2 days when I tried it. But yesterday and today, I noticed it takes a much smaller balance than I configured. For example if I put .50, it uses about 25% of my free balance instead of 50%. Why?

[bible_pay]

That's awesome stuff, Rob. Looking forward to some new statistics.

Today I had another weird experience with the POG system, which I don't understand. Here's what's happened:
Yesterday evening I had some issues with my masternode. So I decided to temporarily take it down and just once test how some of those now "free" coins would work in POG. I chose the MN coins from the inputs and manually sent 50k BBP via "exec sendgscc". After that I waited a couple of hours and was very pleased when the leaderboard showed my account with "owed: 200k". However, in the following payment I only received a mere 780 BBP.  
Since yesterday I did not send out another POG donation, but after the last superblock my name came up again in the leaderboard, now showing "owed: 300k". So I had hoped, maybe tomorrow I get some of my 50k back.

Unfortunately right now I'm completely missing from the leaderboard. So does this mean I lost my 50k into Oblivion? For me the system is still completely non-transparent.

Can you do me a favor and give me the txid of the 50K tx?

[bible_pay]

I thought that pog_coinagepercentage was in fact free balance percentage, because that's how I think it worked for the first 2 days when I tried it. But yesterday and today, I noticed it takes a much smaller balance than I configured. For example if I put .50, it uses about 25% of my free balance instead of 50%. Why?

Its based on the coin age percentage, in contrast to the free wallet balance percentage.

[dave_bbp]

Can you do me a favor and give me the txid of the 50K tx?

Yep sorry, forgot to post that:

Code:

exec getpoints f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29

{
  "Command": "getpoints",
  "pog_points": 1852187327.259578,
  "coin_age": 50276099.10347233,
  "diary_entry": "",
  "orphan_donation": 50000
}

Code:

exec analyze 125890 dave_bbp
{
  "Command": "analyze",
  "Totals": "HEALING|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|0|0.00000000|dave_bbp|32395\nPOG|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|1852187327|0.37424046|dave_bbp|4701730961\n",
  "0": "User: BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U, Diary: , Height: 125733.00, TXID: f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29, NickName: dave_bbp, Points: 1852187327.26, Campaign: POG, CoinAge: 50276099.1035, Donation: 50000.0000, UserTotal: 1852187327.26",
  "1": ""
}

[bible_pay]

Can you do me a favor and give me the txid of the 50K tx?

Yep sorry, forgot to post that:

Code:

exec getpoints f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29

{
  "Command": "getpoints",
  "pog_points": 1852187327.259578,
  "coin_age": 50276099.10347233,
  "diary_entry": "",
  "orphan_donation": 50000
}

Code:

exec analyze 125890 dave_bbp
{
  "Command": "analyze",
  "Totals": "HEALING|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|0|0.00000000|dave_bbp|32395\nPOG|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|1852187327|0.37424046|dave_bbp|4701730961\n",
  "0": "User: BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U, Diary: , Height: 125733.00, TXID: f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29, NickName: dave_bbp, Points: 1852187327.26, Campaign: POG, CoinAge: 50276099.1035, Donation: 50000.0000, UserTotal: 1852187327.26",
  "1": ""
}

Thanks, yeah, I found it.  So, it looks like your 1.85B point transaction made it into superblock 126095 and pays 359420.  Congrats.

It appears the root of the issue is exec analyze should add 205 blocks to the height typed in - another words, we pay the rewards in the superblock after the close of the current superblock.

Ill fix that now.

[dave_bbp]

Thanks, yeah, I found it.  So, it looks like your 1.85B point transaction made it into superblock 126095 and pays 359420.  Congrats.

It appears the root of the issue is exec analyze should add 205 blocks to the height typed in - another words, we pay the rewards in the superblock after the close of the current superblock.

Ill fix that now.

Ah I see, thank you for clearing that up. So the same can be said for the leaderboard in the QT wallet, which looks almost 1 day into the future, so to say? I just tested another 1k POG payment and now my leaderboard says "owed 1.6k", which then would be for the superblock the day after tomorrow (126300), right?

[bible_pay]

Thanks, yeah, I found it.  So, it looks like your 1.85B point transaction made it into superblock 126095 and pays 359420.  Congrats.

It appears the root of the issue is exec analyze should add 205 blocks to the height typed in - another words, we pay the rewards in the superblock after the close of the current superblock.

Ill fix that now.

Ah I see, thank you for clearing that up. So the same can be said for the leaderboard in the QT wallet, which looks almost 1 day into the future, so to say? I just tested another 1k POG payment and now my leaderboard says "owed 1.6k", which then would be for the superblock the day after tomorrow (126300), right?

Yes, exactly, we should put a block range on the heading of the leaderboard, and that would clear that up.  Then the end of the range would be the future superblock height.

[noxpost]

Almost 27M BBP 24h volume on SouthXChange, this is good sign.

Edit: 45M now!

I was just coming here to post this! Incredible day of trading. Congratulations everyone!

[inblue]

I thought that pog_coinagepercentage was in fact free balance percentage, because that's how I think it worked for the first 2 days when I tried it. But yesterday and today, I noticed it takes a much smaller balance than I configured. For example if I put .50, it uses about 25% of my free balance instead of 50%. Why?

Its based on the coin age percentage, in contrast to the free wallet balance percentage.

If all UTXOs in my wallet have exactly the same age, then coin age percentage and free balance percentage would be the same, right?

OK, now let's say I have two UTXOs in my wallet:
UTXO1: 10k BBP (10 days old) = 100k weight
UTXO2: 100k BBP (1 day old) = 100k weight

So in this particular case, these two outputs weigh the same, except I don't know how the algorithm then decides which of these two outputs to take if I want to use 50% of weight, more on that below.

Now take this example:
UTXO1: 100k BBP (1 day old) = 100k weight
UTXO2: 100k BBP (2 days old) = 200k weight

So the total weight is 300k. Then if I set pog_coinagepercentage to .50, that means I want to use half of my weight (150k). But will that use 100k of weight from UTXO1 and 50k of weight from UTXO2, or will it use 150k of weight just from UTXO2? Or any other combination in between?

Because if 100k of weight is taken from UTXO1 and 50k of weight is taken from UTXO2, the total amount of coins used is:
(100k/100k)*100k + (50k/200k)*100k = 1*100k + 0.25*100k = 100k + 25k = 125k

But if no weight is taken from UTXO1 and 150k of weight is taken from UTXO2, then the total amount of coins used is:
(0k/100k)*100k + (150k/200k)*100k = 0*100k + 0.75*100k = 0 + 75k = 75k

So how do we know which of these scenarios will happen (or any scenarios in between)?

Another thing which confuses me is how is one supposed to use all of their free coins? If I put pog_coinagepercentage=1, in the example above that should mean I want to use 300k weight (100% of it), so it should simply use all free coins (200k BBP). But in my experience it uses about 50% of all free coins. Why not all free coins, because 100% of coin age should be all coins, no?