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

[dave_bbp]

Hello,

I have some PCs running BOINC.
On 1 PC I have installed biblepaycore.
I associated this PC with Roseta.

After 3 days (Thursday till today) I get the following result:
"Command": "getboincinfo",
  "CPID": "fa5062d1c29baf2e298b674f40ee59b7",
  "Address": My_Walletaddress,
  "CPIDS": "fa5062d1c29baf2e298b674f40ee59b7;",
  "CPID-Age (hours)": 422416,
  "NextSuperblockHeight": 34030,
  "NextSuperblockBudget": 2660579,
  "fa5062d1c29baf2e298b674f40ee59b7_ADDRESS": My Wallet Address,
  "fa5062d1c29baf2e298b674f40ee59b7_RAC": 7972.06,
  "fa5062d1c29baf2e298b674f40ee59b7_TEAM": 15044,
  "fa5062d1c29baf2e298b674f40ee59b7_TaskWeight": 100,
  "fa5062d1c29baf2e298b674f40ee59b7_UTXOWeight": 75,
  "Total_RAC": 7972.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 5321158,
  "Superblock Count (One Week)": 2,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "33825,33620",
  "Last Superblock Height": 33825,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

and I keep getting negative payment.

Is this OK?

Hi,

You probably have negative payments for PODC Update - that is fine. The system is reporting to PODC your data.
The payment for rosetta work will come once per day on the superblock - next one is 34030.
To see if you are included in the next superblock see this post:
https://bitcointalk.org/index.php?topic=2388064.msg31969170#msg31969170

If your address is not in the superblock 34030 check it again after this block and I am sure your address will be there.

Best regards,
Simon

Actually a friend of mine has the exact same problem. He's "BOINCing" for several days with a correctly associated CPID, but his magnitude is still zero. His RAC should be somewhere around 2-3k and his PODC update transactions went through without problems. I don't think this is OK, why would it take several days for the magnitude to rise above zero?


On another note: are there new findings regarding the utxo being only 75% despite having staked enough BBP?

On yet another note: I managed to run my 2 raspberries and 1 Tinker Board on the main pool with an "unlocked" copy of my main wallet. This works so far, the pool already found some nice blocks. However I would appreciate it if there was some different method than to have a permanently unlocked wallet (for security reasons...).

[bible_pay]

FYI:

We had a few bugs in the last version (1107, 1108, 1109) that caused an error message to appear "Unable to sign cpid" when new users were attempting to type 'exec associate' in certain circumstances.  This is fixed, and will be released as a leisure in approx 2 hours.  (This next version also fixes the crash some users experience in POW mining with multiple threads).  Some other miscellaneous bugs are fixed also.

Hi Rob,
I have a question,

The wallet in Ubuntu Server, when I received a superblock reward or use sendtoaddress function , the wallet address will be changed new address (when I type getaccountaddress "", it can't show back original address), how to bind original address for the only display?
Because if I type exec podcupdate , it will show "Unable to sign cpid" , and re-associate will change the original address to new address.

Hmm, both bugs should be fixed in the new version.  1109b is out there for linux (not announced yet). Just reassociate your wallet, and see if the addressbook entry sticks this time, and the Unable to Sign error should also not appear.

Windows will be ready in 30 mins...

[SVK Noko]

Rob from traders point of view staking amount for magnitude in general should be as high as possible because it will increase demand for BBP on exchanges. BBP finally should have increased its value what will be good and motivating for everybody involved in BBP.

[Bitconee]

FYI:

We had a few bugs in the last version (1107, 1108, 1109) that caused an error message to appear "Unable to sign cpid" when new users were attempting to type 'exec associate' in certain circumstances.  This is fixed, and will be released as a leisure in approx 2 hours.  (This next version also fixes the crash some users experience in POW mining with multiple threads).  Some other miscellaneous bugs are fixed also.

Hi Rob,
I have a question,

The wallet in Ubuntu Server, when I received a superblock reward or use sendtoaddress function , the wallet address will be changed new address (when I type getaccountaddress "", it can't show back original address), how to bind original address for the only display?
Because if I type exec podcupdate , it will show "Unable to sign cpid" , and re-associate will change the original address to new address.

Hmm, both bugs should be fixed in the new version.  1109b is out there for linux (not announced yet). Just reassociate your wallet, and see if the addressbook entry sticks this time, and the Unable to Sign error should also not appear.

Windows will be ready in 30 mins...

Are unbanked CPID's being supported in this new version?

[Lichtsucher]

Hmm, both bugs should be fixed in the new version.  1109b is out there for linux (not announced yet). Just reassociate your wallet, and see if the addressbook entry sticks this time, and the Unable to Sign error should also not appear.
Windows will be ready in 30 mins...

Ubuntu packages are being build right now and should be ready in 60 minutes.

[bible_pay]

FYI:

We had a few bugs in the last version (1107, 1108, 1109) that caused an error message to appear "Unable to sign cpid" when new users were attempting to type 'exec associate' in certain circumstances.  This is fixed, and will be released as a leisure in approx 2 hours.  (This next version also fixes the crash some users experience in POW mining with multiple threads).  Some other miscellaneous bugs are fixed also.

Hi Rob,
I have a question,

The wallet in Ubuntu Server, when I received a superblock reward or use sendtoaddress function , the wallet address will be changed new address (when I type getaccountaddress "", it can't show back original address), how to bind original address for the only display?
Because if I type exec podcupdate , it will show "Unable to sign cpid" , and re-associate will change the original address to new address.

Hmm, both bugs should be fixed in the new version.  1109b is out there for linux (not announced yet). Just reassociate your wallet, and see if the addressbook entry sticks this time, and the Unable to Sign error should also not appear.

Windows will be ready in 30 mins...

Are unbanked CPID's being supported in this new version?

Yes, but only after all sanctuaries upgrade.  We have do some testing before the announcement.

[bible_pay]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)
Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

[znffal]

Please remember to vote on proposed changes to Utxo amount

http://forum.biblepay.org/index.php?topic=127.new#new

[tmike]

Please remember to vote on proposed changes to Utxo amount

http://forum.biblepay.org/index.php?topic=127.new#new

Please also read the comments before voting! Thanks!

[MIP]

Rob from traders point of view staking amount for magnitude in general should be as high as possible because it will increase demand for BBP on exchanges. BBP finally should have increased its value what will be good and motivating for everybody involved in BBP.

But also from trader's point of view, having only two exchanges (only one if you don't already have c-cex account) is a threat to liquidity and price discovery transparency. This will have to be addressed sooner or later.

[Bitconee]

FYI:

We had a few bugs in the last version (1107, 1108, 1109) that caused an error message to appear "Unable to sign cpid" when new users were attempting to type 'exec associate' in certain circumstances.  This is fixed, and will be released as a leisure in approx 2 hours.  (This next version also fixes the crash some users experience in POW mining with multiple threads).  Some other miscellaneous bugs are fixed also.

Hi Rob,
I have a question,

The wallet in Ubuntu Server, when I received a superblock reward or use sendtoaddress function , the wallet address will be changed new address (when I type getaccountaddress "", it can't show back original address), how to bind original address for the only display?
Because if I type exec podcupdate , it will show "Unable to sign cpid" , and re-associate will change the original address to new address.

Hmm, both bugs should be fixed in the new version.  1109b is out there for linux (not announced yet). Just reassociate your wallet, and see if the addressbook entry sticks this time, and the Unable to Sign error should also not appear.

Windows will be ready in 30 mins...

Are unbanked CPID's being supported in this new version?

Yes, but only after all sanctuaries upgrade.  We have do some testing before the announcement.

Ok, thanks . I just updated to 1.1.0.9b

So when all sanctuaries upgrade It will become avaliable automatically?

[gorbi]

Hello,

I have some PCs running BOINC.
On 1 PC I have installed biblepaycore.
I associated this PC with Roseta.

After 3 days (Thursday till today) I get the following result:
"Command": "getboincinfo",
  "CPID": "fa5062d1c29baf2e298b674f40ee59b7",
  "Address": My_Walletaddress,
  "CPIDS": "fa5062d1c29baf2e298b674f40ee59b7;",
  "CPID-Age (hours)": 422416,
  "NextSuperblockHeight": 34030,
  "NextSuperblockBudget": 2660579,
  "fa5062d1c29baf2e298b674f40ee59b7_ADDRESS": My Wallet Address,
  "fa5062d1c29baf2e298b674f40ee59b7_RAC": 7972.06,
  "fa5062d1c29baf2e298b674f40ee59b7_TEAM": 15044,
  "fa5062d1c29baf2e298b674f40ee59b7_TaskWeight": 100,
  "fa5062d1c29baf2e298b674f40ee59b7_UTXOWeight": 75,
  "Total_RAC": 7972.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 5321158,
  "Superblock Count (One Week)": 2,
  "Superblock Hit Count (One Week)": 2,
  "Superblock List": "33825,33620",
  "Last Superblock Height": 33825,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

and I keep getting negative payment.

Is this OK?

Hi,

You probably have negative payments for PODC Update - that is fine. The system is reporting to PODC your data.
The payment for rosetta work will come once per day on the superblock - next one is 34030.
To see if you are included in the next superblock see this post:
https://bitcointalk.org/index.php?topic=2388064.msg31969170#msg31969170

If your address is not in the superblock 34030 check it again after this block and I am sure your address will be there.

Best regards,
Simon

Actually a friend of mine has the exact same problem. He's "BOINCing" for several days with a correctly associated CPID, but his magnitude is still zero. His RAC should be somewhere around 2-3k and his PODC update transactions went through without problems. I don't think this is OK, why would it take several days for the magnitude to rise above zero?

I have the same problem.

[Asya77]

honestly I'm impressed that they want to sponsor orphans in 3rd world countries, so kind

[capulo]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)
Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

35110? this is far far away (~1 week), is this correct? will exchanges be blocked whole another week?

[znffal]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)
Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

35110? this is far far away (~1 week), is this correct? will exchanges be blocked whole another week?

Yes must be a week away.
Since the update is out already the exchange should be able to open with new mandatory version now. No need to wait for the 35110 block

[strayapple]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)
Before block 35110

- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)

How to setup UTXO manually? any exec command or config file?

[znffal]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)
Before block 35110

- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)

How to setup UTXO manually? any exec command or config file?

In config file

utxoamount=60000

For example

[inblue]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

This upgrade increased my sanctuary's constant CPU usage from 6% to about 33%. Can anyone else confirm this on their VPS?

[tmike]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

This upgrade increased my sanctuary's constant CPU usage from 6% to about 33%. Can anyone else confirm this on their VPS?

Mining is on by default, you can try turning it off.

[znffal]

Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

This upgrade increased my sanctuary's constant CPU usage from 6% to about 33%. Can anyone else confirm this on their VPS?

My CPU stayed at 4% before and after upgrading, but I have always had

gen=0

in my config