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

[bible_pay]

we want answers

what chain is correct?

Just verify you are on the correct chain:


getblockhash 99930
9bcfc9b2ef4a2fd71a5350c057f5b25fd26e269e5260eb62f6237403ccea33a2


On a side note, verify that your miners are on this chain.  Any miner not on this chain still mining wont be showing up in your miners list, and will have errors on the leaderboard.

[Aurum420]

Ok, so I ran 'exec utxoreport cpid' for your cpid, and I do see that you have sent UTXOs after Feb 1:in my sql database for your cpid.
(I see you have a registered DCC record).

I've only made deposits to my BBP wallet. The wallet sent those UTXOs on its own.
I don't know what a DCC record is.

[bible_pay]

missing my hashes ped second 2 on 1 machine... where is problem?

So on this issue it looks like your two miners that start with name "kl*" were deleted when your account was deleted (due to the orphanage attack I mentioned in the email).

So you can just recreate them, but please dont use that offensive name again or Ill manually delete them.

Please rename them in your configs also.

[bible_pay]

Ok, so I ran 'exec utxoreport cpid' for your cpid, and I do see that you have sent UTXOs after Feb 1:in my sql database for your cpid.
(I see you have a registered DCC record).

I've only made deposits to my BBP wallet. The wallet sent those UTXOs on its own.
I don't know what a DCC record is.

Right, the dcc record is the original 'exec associate' when you joined team biblepay, and I realize your wallet sent these utxos from the core qt wallet.

What I'm basically hypothesizing is that we have two current issues:

1) The forum tool used for diagnosing the problem is not picking up data after 2-1
2) Our own mincoinage PODC rule requiring .50 aged utxo's is causing a big problem for PODC right now (I'm confirming this right now)

I e-mailed TheSnat for #1.

I'll verify #2 and if its a problem I will address this before noon today but note everyone we will have a fallback plan to prevent cheating.

[capulo]

i had suspicion on .5 age rule todays morning, i stopped automatic updates, now i'm waiting for 0.5 coin age and we will see (in few next hours)

[bible_pay]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

[slovakia]

0.5 coin age is 12hours?

[slovakia]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

excellent...thanks Rob

here is problem with setgenerate true x

[Aurum420]

I've tried following the instructions at https://wiki.biblepay.org/Ecommerce so I can buy gift cards. I can't make it work:

Code:

09:22:08   exec listproducts
09:22:09
{
  "Command": "listproducts"
}

The shelves are empty. They talk about unlocking my wallet but I can find no way to do that. I added my shipping address in my biblepay.conf file and restarted my wallet.

[slovakia]

exists any restriction for numbers of cores for POW? 

[bible_pay]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

excellent...thanks Rob

here is problem with setgenerate true x

What did you type in for setgenerate true, an x or what was the thread count?

[bible_pay]

I've tried following the instructions at https://wiki.biblepay.org/Ecommerce so I can buy gift cards. I can't make it work:

Code:

09:22:08   exec listproducts
09:22:09
{
  "Command": "listproducts"
}

The shelves are empty. They talk about unlocking my wallet but I can find no way to do that. I added my shipping address in my biblepay.conf file and restarted my wallet.

Yeah, we did have Amazon integration once, but that is temporarily disabled due to the high fees.   But now we have Walmart integration live, but only inside the pool.

To buy the gift card please visit pool.biblepay.org and click Store.  Its all we have right now.

(Im going to work on Walmart gift cards that can be emailed very soon).

[bible_pay]

0.5 coin age is 12hours?

Yes, but now its set to zero, so it should work like it did in the past - except TheSnat will monitor manually (using his reports).

[bible_pay]

exists any restriction for numbers of cores for POW? 

No restriction, but with more than 20 threads the cpu use should already be above 90%.

[slovakia]

random i tried on my 4 machines on win 10 home/pro;win 7


setgenerate true 12
setgenerate true 40
setgenerate true 80
setgenerate true 112

[bible_pay]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

excellent...thanks Rob

here is problem with setgenerate true x

What did you type in for setgenerate true, an x or what was the thread count?

If you are michelle_75779 on SouthXChange, why are you so courteous here and backstabbing to us on there?  (IE swearing and saying we are dying quickly).

I thought your other handle was michelle, from the days of forum.biblepay.

[bible_pay]

random i tried on my 4 machines on win 10 home/pro;win 7


setgenerate true 12
setgenerate true 40
setgenerate true 80
setgenerate true 112

Please find the setgenerate level that crashes your miner, then enter a github ticket.
A dev needs to debug the miner on windows.

Then run it on a lower thread count til we solve it.

[slovakia]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

excellent...thanks Rob

here is problem with setgenerate true x

What did you type in for setgenerate true, an x or what was the thread count?

If you are michelle_75779 on SouthXChange, why are you so courteous here and backstabbing to us on there?  (IE swearing and saying we are dying quickly).

I thought your other handle was michelle, from the days of forum.biblepay.

 this:  


you are totally but totally paranoid  

[slovakia]

random i tried on my 4 machines on win 10 home/pro;win 7


setgenerate true 12
setgenerate true 40
setgenerate true 80
setgenerate true 112

Please find the setgenerate level that crashes your miner, then enter a github ticket.
A dev needs to debug the miner on windows.

Then run it on a lower thread count til we solve it.

github what?  you did it.....its your problem!!!!

[capulo]

Ok guys, it's a shame that it happened but unfortunately our .50 podc mincoinage rule is causing all these problems.
Let's blame all of our problems this week on this key.

(The issue was that we couldn't actually predict how frequent or when PODC updates would occur by each user, and since they spent their own coin age on each podc update, technically they lost the coin age and then the sancs didn't include them in the consensus mechanism).

So I have disabled the rule via our spork and now starting in tonight's PODC superblock we should be back on the prior rules.

Warning:  The 20BBP per rac rule is implemented for a reason.  If you are caught deliberately abusing PODC by sharing UTXO funds, we have the capability to blacklist the CPID.  The sancs already have this code running, so it is a very real possibility your CPID will be blacklisted if you share UTXO funds.  TheSnat has the capability to report on this activity and will be monitoring for this starting tomorrow.

i just sent podc update with age 0.55 for cpid 69e9ffe8c747b24d6cfe2afa05684612
you can check if it works if you want

ok and what is the rule exactly? because i;'m moving machines from one account to another and logicaly i will need to move also coins from time to time
so i move coins and now what? i need to wait for something? wait for some time.. or?