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

did you do bankroll for 1.8M for PoG?

https://forum.biblepay.org/tools/podcstatus.php?cpid=3d5cf9907193201f335ee72555acdd5e

Having a seemingly different error on PODCupdates.  My wallet isn't sending PODC updates, and when I do a manual one, it returns:


19:26:36
exec podcupdate true
19:26:36
{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (1) over 0 CPID(s) successfully."
}

but doesn't actually create a transaction.  Also, my getboincinfo Total RAC is zero.  I'm on the correct chain as well.

No problem.

I think the pool.biblepay.org is definitely on a fork. I just updated my miners and checked with getblockhash to be on the "right" chain. Now I am at 99.99 % error percentage on the pool. Before (with some of them on the fork chain) I was at approx. 50%.

Working for me now also.

 In addition to the posts above, sunk818's explanation here helped me resolve issue: https://github.com/biblepay/biblepay/issues/70

I just moved all my non-tithe BBP to my ROSETTA address. Once I did this, podcupdate worked.

I did not need to make a utxooverride=xxx entry

Thx! It appears to be working again

I had this problem too. I fixed it by creating a "receiving address" named PODC (or something similar) and sending the amount of coins I wanted to use for PODC updates to this address (I chose mostly small inputs in coin control for that, but it doesn't really matter). Then add the following line to your config:
utxooverride=XXXXXXXXXX
with XXXXXXXXX being the amount of BBP you want to stake for PODC. In your case 400000 should be enough.

After restarting it sent PODCupdates again and it does so until now (wallet 1198).


P.S.: I just realized that the POG leaderboard in bezaleel theme is a bit buggy. First of all it doesn't "switch" the navigation bar highlight when activated (the bar always stays on the former), and also the leaderboard itself highlights a random person instead of myself. Even when I actively highlight myself it changes upon refresh.
Nothing to worry about, only cosmetics.

My wallet didn't send any PODC-updates in the last few days also, but I have been on 1194. Updated to 1198 today to see if that would fix it, but now I get the same "Unable to locate coins not marked as POG bankroll denominations." message (I got a different message before, but I forgot what it said). I must mention that I have PODC+POG in the same wallet, so I don't expect it to work flawlessly.

I getting error : "PODCUpdate": "Unable to locate coins not marked as POG bankroll denominations."

Anyone have a suggestion on a fix for this.I have done several  bankroll commands for POG & seemed to have effected my podc stakebalance.  I can't get a PODC update to send for 3 days. Seems to be happening since wallet upgrade to 1198, but may just be a coincidence?

Someone mentioned a possible fix with a UTXO entry in biblepay.conf, but not sure what value to use. My totalrac is:

"Command": "totalrac",
  "Total RAC": 21249.21,
  "UTXO Target": 467482.6200000001,
  "StakeBalance": 1732501,
  "Threshhold to receive 10% rewards (below this UTXO Amount rewards are lost)": 16999.37,
  "Stake Level Required For 10% Level": 17424.35,
  "Stake Level Required For 20% Level": 42498.42,
  "Stake Level Required For 30% Level": 84996.84,
  "Stake Level Required For 40% Level": 127495.26,
  "Stake Level Required For 50% Level": 169993.68,
  "Stake Level Required For 60% Level": 212492.1,
  "Stake Level Required For 70% Level": 254990.52,
  "Stake Level Required For 80% Level": 297488.94,
  "Stake Level Required For 90% Level": 339987.36,
  "Stake Level Required For 100% Level": 382485.78,
  "Total Team RAC": 5942801

There will be no centralization and less than we have now.  The POW reward is in each wallet, the POS/POG reward will be once per day decided by our sancs in a decentralized way in a hard calculated contract.  (No web service).

The gospel code will not be centralized; it will run in Stratis with one copy running on each sanc.  (Decentralized).

IPFS might be used for the orphan letter writing, but that is a topic in itself we need a thread for, as BiblePay is working on that simultaneously for another undertaking.

Does this mean there will be a bigger reliance on centralized web services? Or is IPFS playing a bigger role? I can appreciate the desire for stability... It is important to build trust and confidence in the BiblePay product.

** BIBLEPAY UPDATE **




Due to the fork we experienced yesterday, I have decided that future fork risk must be mitigated as our highest priority (even at the expense of features or mining algorithms), as security and reliability Trumps everything else.

Because of this, I have decided to rearrange the roadmap.  We will be accelerating the release of Biblepay-Evolution to be our next highest priority.

In Evolution, we will still use proof-of-biblehash for POW, but it will be modified to be compatible with Dash's 51% attack preventer, and be modified to prevent fork risk.

Depending on the votes over the next 30 days, most likely we will see PODC be retired.  It is also possible that I will modify POG to become a sanctuary contract - whatever it takes to remove fork risk entirely.  So be aware, the next version of BiblePay will most likely be CPU-POW based, with our full daily reward, with a split between the CPU miners and the 'generic daily sanctuary contract that rewards proof-of-stake or proof-of-giving rewards' for the remaining part of the reward.  The important thing is that each block is highly secure and has no fork risk.

One other large change that is coming is we will be changing our business model in IT to be more reliant on Dash releases - this is for production stability.  Basically what this means is our R&D department code will be moved to Stratis, and we will open that project up again so that Sanctuaries will execute R&D code while production is unaffected.  Put another way, when Dash releases appear, MIP will help create Prod releases of BiblePay, while myself and the other teamembers work on Gospel code in a separate environment and we will make it so this code can be accessed by clicking on in-wallet menus that access HTML5 Sanctuary features.

This change should be very positive for our Production stability and reliability.  Please be patient while we work on our next release.

i'm using latest .9.8 or so
i had few crashes also

now i did 2 podcupdates at same time dont know how it is possible
but it starts updating weirdly, one time it did update with much lower value, then pile was splitted and updates stopped and so - i also dont know whats going on here

Everyone please consider keeping PODC. Being able to mine POBH and PODC is really nice.

Plus I'm in the middle of writing a book on crypto and would like to include BBP, as I'm not aware of any other coin that allows two methods of mining simultaneously.

If the community wants to dump PODC, fine. But I'll need to find another example..

Please, everyone check your hash:

getblockhash 105180
764b71b6a3a8a6cfc349d911f57bce1ff38e5bcdd2aafb339ad96216e6705330

If yours does not agree, please re-sync your chain.



In the mean time, we are working on minimizing future fork risk so this nuisance can be put behind us permanently.  I had a call today with MIP and we have a plan to mitigate this problem in the future.  I'll announce the plan tomorrow morning.

I have this hash also (the higher work):

getblockhash 105056

1d02ebd95fa5581f353fe013e300c2ad6e271cc12332cc7d74284a24d289d5d8




I've just contacted SouthExchange to confirm their hash.


I'm reindexing every one of my sancs simultaneously, will double check the results asap.

Thanks, that comment was not meant for you- it was because people seemed to be questioning my suggestion to 'exec associate' again on the existing cpid.

What I wanted to explain yesterday was that the original DCC association record with the original CPID signature expired after 6 months, and anyone who received "invalid destination" should re-associate the CPID with the latest wallet.  (No, the CPID itself does not expire).

Vahtis, I do not take your comment disrespectfully.  I value you in our community.

Please, let us start again.

Sometimes things get a little hot because we have multiple problems today.

I wish the same for Sun, I just wish people would act more like Jesus all the time and not invite strife into the forum.

I finally managed to do the reassociation (after my wallet completely crashing and messing up the blockchain data on a former attempt). I didn't have time to wait for the confirmation, but when I came back home I now I saw that my wallet had sent a PODCupdate and everything seems to be back in order right now.

I honestly have no idea what you even mean by that ...

So naming people and promoting oneself over others is your christian way to do things.
I can see from to code that you are good developer, but man you are lacking social skills badly. I do not want to fork new dash or biblepay. I want to support biblepay. I am from free country and all of must have rights to opinion. They are often conflicting, but this does not give You or anyone else rights to name people bad.

Sorry to hear that you have lost. I am not responsible for that and after all you have been paid so my statement that you are the one getting paid is true and therefore I have no reason to apologize.