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

SVK Noko

newbie

Activity: 267

Merit: 0

Quote from: bible_pay on April 21, 2018, 11:05:33 AM

Quote from: jaapgvk on April 21, 2018, 06:49:55 AM

Quote from: slovakia on April 21, 2018, 06:32:04 AM

i believe that ROB will found where was problem ... we dont need this bugs in PODC

Yes, PODC should be bulletproof.

Sorry for the delay- I had to meet Ginger from Compassion yesterday, and have to go through the manual payments to compassion which takes hours.

The meeting went very well, she was very impressed with what we do, and is impressed at how fast we are growing. She gave me a pamphlet on their new upcoming product: Sponsoring babies. They are working on the ability to pay for childbirth medical expenses and all expenses until the child is 3 years old and then the baby will transition to a normal orphan in the system. This product type will cost more (mostly because of the medical expenses), and is not as transparent. If we end up sponsoring babies, we will only receive a Pastors name, a church name the parents showed up to ask for help, and one letter from the pastor.

She did make me aware that the children we sponsor receive 4 meals per week and are scheduled to be at the church 4 days per week. A lot of the expense compassion pays ($28 of the $38) goes directly to the church to cover the program, the churches rent, etc, making it very efficient. So a day in the life of one of the children is something like: heading to the church, receiving Sunday school (or should I say bible lessons), a free meal, etc. She was saying some of the starving children do not have the means to eat anything until the next day, so they receive a double portion of food and compassion is the only service actually keeping them alive.

Regarding prepayments, we are getting stronger: We prepaid 216 orphan payments today, so I went ahead and sponsored 10 new orphans today (since we are now prepaid over 3 months in the future) I went ahead and decided to grow a little

. We are still waiting for the 10 from Cameroon One to come online - putting us at 229 as of today! (See Orphans | expenses and fundraiser).

Regarding this PODC payment issue, first we have to remove the elephant in the room. The biggest problem I see is the older legacy code, version 1.1.2.0 and down, can only handle about 380 cpids of size in a contract. We obviously cannot release a mandatory upgrade including exchanges until June 30th, hence the reason these upgrade notices are either "sanctuary only" or Mandatory for Users and Leisure for exchanges. That being said, the most critical issue in our network is the governance object size was Extended in version 1.1.2.1. What you have to realize is this is *not* a sanctuary problem, this is a General User problem and in this case, the Users version is affecting the entire network.

I see when running exec versionreport, unfortunately the supermajority (60%) is still on prior versions below 1.1.2.0. So what we need is everyone remaining to upgrade to 1.1.2.1+ so that PODC contracts can propagate.

Basically part of the problem is the contract that only contained < 380 CPIDS was smaller than the limit allowed on the network so it passed through. We now have over 381 CPIDs every day, so we really need everyone else to upgrade. Specifically the problem is that if a segment of the network has a node standing between that geographical area that is on a low version, it will *not* be able to forward the superblock! It will instead throw an error. So everyone in the segmented area will not have the gobject. I can imagine this can be causing our fork, as those nodes will have a different view of their sanctuary count, and gobject list.

So first things first we need to have a supermajority on 1.1.2.2+.

Anton checked in an enhancement last night giving us a pretty nice left menu, its being merged in now.

Could somebody explain this issue with simple English for not native English speakers?

Thanks.

afeno

jr. member

Activity: 175

Merit: 1

How can I upgrade my Linux Ubuntu wallet? I am using ppa:lichtsucher/biblepay repository and I think that the last version there is the 1.1.1.9

Code:

biblepayd is already the newest version (1.1.1.9-xenial1).

There is an official repository?

Edit: I noticed that the link "https://www.Biblepay.org/get-Biblepay/." is broken in the GitHub webpage (https://github.com/biblepay/biblepay)

Cryptoalt1990

newbie

Activity: 48

Merit: 0

Quote from: bible_pay on April 21, 2018, 11:05:33 AM

Quote from: jaapgvk on April 21, 2018, 06:49:55 AM

Quote from: slovakia on April 21, 2018, 06:32:04 AM

i believe that ROB will found where was problem ... we dont need this bugs in PODC

Yes, PODC should be bulletproof.

Sorry for the delay- I had to meet Ginger from Compassion yesterday, and have to go through the manual payments to compassion which takes hours.

The meeting went very well, she was very impressed with what we do, and is impressed at how fast we are growing. She gave me a pamphlet on their new upcoming product: Sponsoring babies. They are working on the ability to pay for childbirth medical expenses and all expenses until the child is 3 years old and then the baby will transition to a normal orphan in the system. This product type will cost more (mostly because of the medical expenses), and is not as transparent. If we end up sponsoring babies, we will only receive a Pastors name, a church name the parents showed up to ask for help, and one letter from the pastor.

She did make me aware that the children we sponsor receive 4 meals per week and are scheduled to be at the church 4 days per week. A lot of the expense compassion pays ($28 of the $38) goes directly to the church to cover the program, the churches rent, etc, making it very efficient. So a day in the life of one of the children is something like: heading to the church, receiving Sunday school (or should I say bible lessons), a free meal, etc. She was saying some of the starving children do not have the means to eat anything until the next day, so they receive a double portion of food and compassion is the only service actually keeping them alive.

Regarding prepayments, we are getting stronger: We prepaid 216 orphan payments today, so I went ahead and sponsored 10 new orphans today (since we are now prepaid over 3 months in the future) I went ahead and decided to grow a little

. We are still waiting for the 10 from Cameroon One to come online - putting us at 229 as of today! (See Orphans | expenses and fundraiser).

Regarding this PODC payment issue, first we have to remove the elephant in the room. The biggest problem I see is the older legacy code, version 1.1.2.0 and down, can only handle about 380 cpids of size in a contract. We obviously cannot release a mandatory upgrade including exchanges until June 30th, hence the reason these upgrade notices are either "sanctuary only" or Mandatory for Users and Leisure for exchanges. That being said, the most critical issue in our network is the governance object size was Extended in version 1.1.2.1. What you have to realize is this is *not* a sanctuary problem, this is a General User problem and in this case, the Users version is affecting the entire network.

I see when running exec versionreport, unfortunately the supermajority (60%) is still on prior versions below 1.1.2.0. So what we need is everyone remaining to upgrade to 1.1.2.1+ so that PODC contracts can propagate.

Basically part of the problem is the contract that only contained < 380 CPIDS was smaller than the limit allowed on the network so it passed through. We now have over 381 CPIDs every day, so we really need everyone else to upgrade. Specifically the problem is that if a segment of the network has a node standing between that geographical area that is on a low version, it will *not* be able to forward the superblock! It will instead throw an error. So everyone in the segmented area will not have the gobject. I can imagine this can be causing our fork, as those nodes will have a different view of their sanctuary count, and gobject list.

So first things first we need to have a supermajority on 1.1.2.2+.

Anton checked in an enhancement last night giving us a pretty nice left menu, its being merged in now.

Thanks for the update Bible_pay,

This issue is very unfortunate and hopefully it can be resolved soon by having everyone upgrade.

That meeting with Compassion is really exciting. Would it be possible to scan that pamphlet so that can all have a look at it too?

Also, I had a look at the expenses/fundraiser page in the pool and I was wondering if we could add another page (or add something somewhere) that would have the current balance in BBP, BTC, USD, etc. of what is in the BiblePay foundation accounts?

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: jaapgvk on April 21, 2018, 06:49:55 AM

Quote from: slovakia on April 21, 2018, 06:32:04 AM

i believe that ROB will found where was problem ... we dont need this bugs in PODC

Yes, PODC should be bulletproof.

Sorry for the delay- I had to meet Ginger from Compassion yesterday, and have to go through the manual payments to compassion which takes hours.

The meeting went very well, she was very impressed with what we do, and is impressed at how fast we are growing. She gave me a pamphlet on their new upcoming product: Sponsoring babies. They are working on the ability to pay for childbirth medical expenses and all expenses until the child is 3 years old and then the baby will transition to a normal orphan in the system. This product type will cost more (mostly because of the medical expenses), and is not as transparent. If we end up sponsoring babies, we will only receive a Pastors name, a church name the parents showed up to ask for help, and one letter from the pastor.

She did make me aware that the children we sponsor receive 4 meals per week and are scheduled to be at the church 4 days per week. A lot of the expense compassion pays ($28 of the $38) goes directly to the church to cover the program, the churches rent, etc, making it very efficient. So a day in the life of one of the children is something like: heading to the church, receiving Sunday school (or should I say bible lessons), a free meal, etc. She was saying some of the starving children do not have the means to eat anything until the next day, so they receive a double portion of food and compassion is the only service actually keeping them alive.

Regarding prepayments, we are getting stronger: We prepaid 216 orphan payments today, so I went ahead and sponsored 10 new orphans today (since we are now prepaid over 3 months in the future) I went ahead and decided to grow a little

. We are still waiting for the 10 from Cameroon One to come online - putting us at 229 as of today! (See Orphans | expenses and fundraiser).

Regarding this PODC payment issue, first we have to remove the elephant in the room. The biggest problem I see is the older legacy code, version 1.1.2.0 and down, can only handle about 380 cpids of size in a contract. We obviously cannot release a mandatory upgrade including exchanges until June 30th, hence the reason these upgrade notices are either "sanctuary only" or Mandatory for Users and Leisure for exchanges. That being said, the most critical issue in our network is the governance object size was Extended in version 1.1.2.1. What you have to realize is this is *not* a sanctuary problem, this is a General User problem and in this case, the Users version is affecting the entire network.

I see when running exec versionreport, unfortunately the supermajority (60%) is still on prior versions below 1.1.2.0. So what we need is everyone remaining to upgrade to 1.1.2.1+ so that PODC contracts can propagate.

Basically part of the problem is the contract that only contained < 380 CPIDS was smaller than the limit allowed on the network so it passed through. We now have over 381 CPIDs every day, so we really need everyone else to upgrade. Specifically the problem is that if a segment of the network has a node standing between that geographical area that is on a low version, it will *not* be able to forward the superblock! It will instead throw an error. So everyone in the segmented area will not have the gobject. I can imagine this can be causing our fork, as those nodes will have a different view of their sanctuary count, and gobject list.

So first things first we need to have a supermajority on 1.1.2.2+.

Anton checked in an enhancement last night giving us a pretty nice left menu, its being merged in now.

inblue

full member

Activity: 462

Merit: 103

Quote from: zthomasz on April 21, 2018, 08:40:42 AM

3rd NOTICE:

Thanks to everyone who donated or loaned BBP to the SouthXchange.com Listing Fee Fund. If you haven't been reimbursed yet, PM me or post the receiving address that you want your BBP sent to.

If your loan was anonymous, please include the transaction info and/or donation date & amount of BBP in order to identify yourself as the lender.

Any loans not claimed by April 30, 2018 will be donated to the BiblePay orphan fund.

Thanks again for helping us complete another successful BiblePay goal!

Thank you for your efforts and integrity. But don't you think it's more logical to donate the coins to Jaap's new exchange fund, because that's what those people would have wanted, right? They intended the coins for bringing BiblePay to a new exchange, so why not preserve the same purpose of those coins.

zthomasz

member

Activity: 489

Merit: 12

3rd NOTICE:

Thanks to everyone who donated or loaned BBP to the SouthXchange.com Listing Fee Fund. If you haven't been reimbursed yet, PM me or post the receiving address that you want your BBP sent to.

If your loan was anonymous, please include the transaction info and/or donation date & amount of BBP in order to identify yourself as the lender.

Any loans not claimed by April 30, 2018 will be donated to the BiblePay orphan fund.

Thanks again for helping us complete another successful BiblePay goal!

Dimarzio123

newbie

Activity: 75

Merit: 0

me too
pool.biblepay.org now showing

Magnitude: 0
UTXO Weight: 0
Task Weight: 0

It was correct earlier this morning
*************************************

Quote from: slovakia on April 21, 2018, 06:54:52 AM

i have again stakebalance 0
1123 wallet
chain is correct

edit://after few few minutes is stakebalance OK ... dont understand it then

stevenzak

newbie

Activity: 15

Merit: 0

CPID_HAS_NO_MAGNITUDEHIGH_HASH
noticed most people mining more than 2 machines are having issues.

what is the meaning of this, so i can try to fix it. Yesterday I added two machines now i am getting no coins.

jaapgvk

full member

Activity: 574

Merit: 104

Quote from: turbokongen on April 21, 2018, 08:09:35 AM

Ok, by just leaving the wallet with the error open for quite a while, it looks like it sorted itself.
But my balance is wrong. I lost all my previously staked bbp.

Code:

14:57:05

getmininginfo


14:57:05

{
  "blocks": 41931,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 693.6450457751241,
  "difficulty_pow": 1483.662604573834,
  "difficulty": 693.6450457751241,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 713394.0251528968,
  "hashps": 340.9034190167208,
  "minerstarttime": "04-21-2018 12:56:51",
  "hashcounter": 4098,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "podc_tried": 0,
  "podc_sent": 0,
  "podc_sent_amount": 0,
  "podc_average_amount_sent": 0,
  "miningpulse": 5,
  "poolmining": true,
  "pool_url": "http://pool2.biblepay.org",
  "poolmining_use_ssl": false
}


14:57:18

exec getboincinfo


14:57:21

{
  "Command": "getboincinfo",
  "CPID": "72a5162338116948c70e904a21916e42",
  "Address": "B99KSo452MCNpDEaRsWtveGpRkDyw98YYq",
  "CPIDS": "72a5162338116948c70e904a21916e42;",
  "CPID-Age (hours)": 423420,
  "NextSuperblockHeight": 42025,
  "NextSuperblockBudget": 1179301,
  "72a5162338116948c70e904a21916e42_ADDRESS": "B99KSo452MCNpDEaRsWtveGpRkDyw98YYq",
  "72a5162338116948c70e904a21916e42_RAC": 1978.73,
  "72a5162338116948c70e904a21916e42_TEAM": 15044,
  "72a5162338116948c70e904a21916e42_WCGRAC": 2657,
  "72a5162338116948c70e904a21916e42_TaskWeight": 0,
  "72a5162338116948c70e904a21916e42_UTXOWeight": 0,
  "Total_RAC": 4635.73,
  "Total Payments (One Day)": 448,
  "Total Payments (One Week)": 2039,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "41820,41615,41410,41205,41000,40795,40590,40385",
  "Last Superblock Height": 41820,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 448,
  "Magnitude (One-Day)": 0.3798860511438555,
  "Magnitude (One-Week)": 0.2469986155236994
}


14:57:37

exec stakebalance


14:57:37

{
  "Command": "stakebalance",
  "StakeBalance": 712
}


14:58:46

exec podcupdate true


14:59:04

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (8) over 1 CPID(s) successfully."
}

If you view the transaction details in the 'Transactions' tab of your wallet, you can see the amount that has been staked with the latest transaction. It takes 6 blocks for the network to recognize your staking amount, so please check again in a few blocks. It should be fine then

turbokongen

newbie

Activity: 30

Merit: 0

Ok, by just leaving the wallet with the error open for quite a while, it looks like it sorted itself.
But my balance is wrong. I lost all my previously staked bbp.

Code:

14:57:05

getmininginfo


14:57:05

{
  "blocks": 41931,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 693.6450457751241,
  "difficulty_pow": 1483.662604573834,
  "difficulty": 693.6450457751241,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 713394.0251528968,
  "hashps": 340.9034190167208,
  "minerstarttime": "04-21-2018 12:56:51",
  "hashcounter": 4098,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "podc_tried": 0,
  "podc_sent": 0,
  "podc_sent_amount": 0,
  "podc_average_amount_sent": 0,
  "miningpulse": 5,
  "poolmining": true,
  "pool_url": "http://pool2.biblepay.org",
  "poolmining_use_ssl": false
}


14:57:18

exec getboincinfo


14:57:21

{
  "Command": "getboincinfo",
  "CPID": "72a5162338116948c70e904a21916e42",
  "Address": "B99KSo452MCNpDEaRsWtveGpRkDyw98YYq",
  "CPIDS": "72a5162338116948c70e904a21916e42;",
  "CPID-Age (hours)": 423420,
  "NextSuperblockHeight": 42025,
  "NextSuperblockBudget": 1179301,
  "72a5162338116948c70e904a21916e42_ADDRESS": "B99KSo452MCNpDEaRsWtveGpRkDyw98YYq",
  "72a5162338116948c70e904a21916e42_RAC": 1978.73,
  "72a5162338116948c70e904a21916e42_TEAM": 15044,
  "72a5162338116948c70e904a21916e42_WCGRAC": 2657,
  "72a5162338116948c70e904a21916e42_TaskWeight": 0,
  "72a5162338116948c70e904a21916e42_UTXOWeight": 0,
  "Total_RAC": 4635.73,
  "Total Payments (One Day)": 448,
  "Total Payments (One Week)": 2039,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "41820,41615,41410,41205,41000,40795,40590,40385",
  "Last Superblock Height": 41820,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 448,
  "Magnitude (One-Day)": 0.3798860511438555,
  "Magnitude (One-Week)": 0.2469986155236994
}


14:57:37

exec stakebalance


14:57:37

{
  "Command": "stakebalance",
  "StakeBalance": 712
}


14:58:46

exec podcupdate true


14:59:04

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (8) over 1 CPID(s) successfully."
}

slovakia

full member

Activity: 770

Merit: 100

i have again stakebalance 0
1123 wallet
chain is correct

edit://after few few minutes is stakebalance OK ... dont understand it then

jaapgvk

full member

Activity: 574

Merit: 104

Quote from: slovakia on April 21, 2018, 06:32:04 AM

i believe that ROB will found where was problem ... we dont need this bugs in PODC

Yes, PODC should be bulletproof.

znffal

full member

Activity: 364

Merit: 102

Quote from: gagaha on April 21, 2018, 05:59:25 AM

Quote

Maybe you mined it on a fork?
I don't see the transaction in the blockchain

http://explorer.biblepay.org:3001

I'm not sure about that and I also don't know how that could have happened.
Either way - I just started my wallet with a backup wallet.dat and that seems to have sorted out the problem.
Balance is back to normal as it was before.
Thanks anyway

Glad it worked out!

slovakia

full member

Activity: 770

Merit: 100

i believe that ROB will found where was problem ... we dont need this bugs in PODC

gagaha

newbie

Activity: 3

Merit: 0

Quote

Maybe you mined it on a fork?
I don't see the transaction in the blockchain

http://explorer.biblepay.org:3001

I'm not sure about that and I also don't know how that could have happened.
Either way - I just started my wallet with a backup wallet.dat and that seems to have sorted out the problem.
Balance is back to normal as it was before.
Thanks anyway

znffal

full member

Activity: 364

Merit: 102

gagaha

newbie

Activity: 3

Merit: 0

Hi!

I have a problem with my wallet.
It seems that most of my balance has disappeared. 1.2mio bbp are gone.

Just checked the logs and tried to understand how that might have happened.
Tonight my wallet (Linux v1.1.2.2) crashed, resulting in a restart of my wallet. Since then it seemed to have been stuck on an invalid block 41871.
Today I stopped the wallet cleaned my Biblepaycore directory (rm blocks, chainstate.. etc) and upgraded to v1.1.2.3.
But after reindexing my wallet balance is only 7777 bbp.

Part of the logs:

Code:

2018-04-21 09:11:51 CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts
2018-04-21 09:11:51 Masternode indexes and governance triggers prepared 745ms
2018-04-21 09:11:51 Governance Objects: 689 (Proposals: 48, Triggers: 640, Watchdogs: 1/1, Other: 0; Seen: 1253), Votes: 6657
2018-04-21 09:11:51 init message: Loading fulfilled requests cache...
2018-04-21 09:11:51 Reading info from netfulfilled.dat...
2018-04-21 09:11:51 Loaded info from netfulfilled.dat 0ms
2018-04-21 09:11:51 Nodes with fulfilled requests: 23
2018-04-21 09:11:51 Nodes with fulfilled requests: 1
2018-04-21 09:11:51 init message: Memorizing Prayers...
2018-04-21 09:12:00 mapBlockIndex.size() = 41871
2018-04-21 09:12:00 chainActive.Height() = 41837
2018-04-21 09:12:00 setKeyPool.size() = 1000
2018-04-21 09:12:00 mapWallet.size() = 310
2018-04-21 09:12:00 mapAddressBook.size() = 2
2018-04-21 09:12:00 init message: Loading addresses...
2018-04-21 09:12:00 torcontrol thread start
2018-04-21 09:12:00 Loaded 18818 addresses from peers.dat 242ms
2018-04-21 09:12:00 dnsseed thread start
2018-04-21 09:12:00 net thread start
2018-04-21 09:12:00 addcon thread start
2018-04-21 09:12:00 opencon thread start
2018-04-21 09:12:00 mnbcon thread start
2018-04-21 09:12:00 msghand thread start
2018-04-21 09:12:00 Starting Thread #0.000000 with Bible #0.000000 BibleMiner -- started thread 0.000000
2018-04-21 09:12:00 MinerSleep 325.000000
2018-04-21 09:12:00 ** Started 1.000000 BibleMiner threads. **
2018-04-21 09:12:00 Genesis Hash 3b4431310395638c0ed65b40ede4b110d8da70fcc0c2ed4a729fb8e4d78b4452
2018-04-21 09:12:01 init message: Done loading
2018-04-21 09:12:01 AddToWallet 7b382973eb26fbbcd705e1f38353dccb0d0c46239f1581afabce7607503590f1
2018-04-21 09:12:11 Loading addresses from DNS seeds (could take a while)
2018-04-21 09:12:11 1 addresses found from DNS seeds
2018-04-21 09:12:11 dnsseed thread exit
2018-04-21 09:12:14 ERROR: AcceptBlockHeader: block is marked invalid
2018-04-21 09:12:14 ERROR: invalid header received 3fde3a41710e3e1c730731309e577519d0318b8d306136c8017dfcde656140d4
2018-04-21 09:12:22 ERROR: AcceptBlockHeader: block is marked invalid
2018-04-21 09:12:22 ERROR: invalid header received 3fde3a41710e3e1c730731309e577519d0318b8d306136c8017dfcde656140d4
2018-04-21 09:13:02 ERROR: AcceptBlockHeader: block is marked invalid

Listtransactions:

Code:

~# docker exec bp biblepay-cli listtransactions
[
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "receive",
"amount": 604611.50000000,
"label": "",
"vout": 2,
"confirmations": 0,
"bcconfirmations": 0,
"trusted": false,
"txid": "7b382973eb26fbbcd705e1f38353dccb0d0c46239f1581afabce7607503590f1",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524294072,
"bip125-replaceable": "unknown"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "receive",
"amount": 604611.50000000,
"label": "",
"vout": 1,
"confirmations": 0,
"bcconfirmations": 0,
"trusted": false,
"txid": "7b382973eb26fbbcd705e1f38353dccb0d0c46239f1581afabce7607503590f1",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524294072,
"bip125-replaceable": "unknown"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "send",
"amount": -604611.50000000,
"label": "",
"vout": 2,
"fee": -0.00125860,
"confirmations": 0,
"bcconfirmations": 0,
"trusted": false,
"txid": "7b382973eb26fbbcd705e1f38353dccb0d0c46239f1581afabce7607503590f1",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524294072,
"bip125-replaceable": "unknown",
"abandoned": false
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "send",
"amount": -604611.50000000,
"label": "",
"vout": 1,
"fee": -0.00125860,
"confirmations": 0,
"bcconfirmations": 0,
"trusted": false,
"txid": "7b382973eb26fbbcd705e1f38353dccb0d0c46239f1581afabce7607503590f1",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524294072,
"bip125-replaceable": "unknown",
"abandoned": false
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "generate podc-payment",
"amount": 7776.19000000,
"label": "",
"vout": 38,
"confirmations": 294,
"bcconfirmations": 294,
"generated": true,
"blockhash": "3fde3a41710e3e1c730731309e577519d0318b8d306136c8017dfcde656140d4",
"blockindex": 0,
"blocktime": 1524178458,
"txid": "5da001d48ee2aa282fddcffdf33fce42a7818d8df887dddf5dbc68162228d624",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524302639,
"bip125-replaceable": "no"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "immature podc-payment",
"amount": 24815.07000000,
"label": "",
"vout": 21,
"confirmations": 89,
"bcconfirmations": 89,
"generated": true,
"blockhash": "287539c916ebcbae557ce6b3b1e8ce123ce874b9a4d1620b9691cc4d33ef891a",
"blockindex": 0,
"blocktime": 1524267871,
"txid": "81c55153e43d9f468dd4a831b78139ddf3071569dcff52f3fbb3b8ddb4dd9dc1",
"walletconflicts": [
],
"time": 1524294072,
"timereceived": 1524302642,
"bip125-replaceable": "no"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "receive",
"amount": 3888.50000000,
"label": "",
"vout": 2,
"confirmations": 6,
"bcconfirmations": 6,
"blockhash": "a940c9b17a55a1535fd5f951ce2d09f09ddccbac34e43bfda94b820eab9208ca",
"blockindex": 2,
"blocktime": 1524303095,
"txid": "68ed0ec64456b6bc5ed11ffc4322dcf0c10a2e2970e1633ad794579e0e623eac",
"walletconflicts": [
],
"time": 1524302954,
"timereceived": 1524302954,
"bip125-replaceable": "no"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "receive",
"amount": 3888.50000000,
"label": "",
"vout": 1,
"confirmations": 6,
"bcconfirmations": 6,
"blockhash": "a940c9b17a55a1535fd5f951ce2d09f09ddccbac34e43bfda94b820eab9208ca",
"blockindex": 2,
"blocktime": 1524303095,
"txid": "68ed0ec64456b6bc5ed11ffc4322dcf0c10a2e2970e1633ad794579e0e623eac",
"walletconflicts": [
],
"time": 1524302954,
"timereceived": 1524302954,
"bip125-replaceable": "no"
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "send",
"amount": -3888.50000000,
"label": "",
"vout": 2,
"fee": -0.00131800,
"confirmations": 6,
"bcconfirmations": 6,
"blockhash": "a940c9b17a55a1535fd5f951ce2d09f09ddccbac34e43bfda94b820eab9208ca",
"blockindex": 2,
"blocktime": 1524303095,
"txid": "68ed0ec64456b6bc5ed11ffc4322dcf0c10a2e2970e1633ad794579e0e623eac",
"walletconflicts": [
],
"time": 1524302954,
"timereceived": 1524302954,
"bip125-replaceable": "no",
"abandoned": false
},
{
"account": "",
"address": "BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7",
"category": "send",
"amount": -3888.50000000,
"label": "",
"vout": 1,
"fee": -0.00131800,
"confirmations": 6,
"bcconfirmations": 6,
"blockhash": "a940c9b17a55a1535fd5f951ce2d09f09ddccbac34e43bfda94b820eab9208ca",
"blockindex": 2,
"blocktime": 1524303095,
"txid": "68ed0ec64456b6bc5ed11ffc4322dcf0c10a2e2970e1633ad794579e0e623eac",
"walletconflicts": [
],
"time": 1524302954,
"timereceived": 1524302954,
"bip125-replaceable": "no",
"abandoned": false
}
]

Could someone please explain to me how that could happen and what I can do to get my coins back?
As you see from list transactions there are transactions from a podc update with 604k bbp.. but no confirmations.
Is it possible that a podc update on the invalid block resulted in removing most of my balance?

Thanks!

afeno

jr. member

Activity: 175

Merit: 1

Quote from: Lichtsucher on April 18, 2018, 02:08:36 AM

You should be able to switch between lichtsucher/biblepay and biblepay/stable by changing the apt configs in /etc

Would you mind to explain how? Im not very good with Linux...

Dimarzio123

newbie

Activity: 75

Merit: 0

I didn't get paid either last night
I updated wallet / re-indexed yesterday about 17H00

exec getboincinfo - looked correct
exec stakebalance - looked correct
exec totalrac - looked correct

exec podcupdate true - threw an arror at 18H31 GMT

18:31:31

{
"Command": "podcupdate",
"PODCUpdate": "Unable to create PODC UTXO::Balance (0.00) less than target UTXO (1466071.00)."
}

Running it again this morning - looks correct

10:15:13

{
"Command": "podcupdate",
"PODCUpdate": "Processed (138) over 1 CPID(s) successfully."
}

Problem fixed?
*********************************************************

Quote from: jaapgvk on April 20, 2018, 01:46:53 PM

Quote from: Dimarzio123 on April 20, 2018, 01:23:22 PM

Stand down!!

Waited for 30 minutes
Seems to sorted itself out

Regards
PM
************************

Quote from: Dimarzio123 on April 20, 2018, 12:17:15 PM

Hi
Can you explain how to do this please: "restart the Biblepay QT"

I have updated the wallet to 1.1.2.2 and have this issue
TIA
PM

18:14:50
exec stakebalance

18:14:52
{
"Command": "stakebalance",
"StakeBalance": 0
}

18:15:25

exec podcupdate true

18:15:25

{
"Command": "podcupdate",
"PODCUpdate": "Unable to find any CPIDS. Please try exec getboincinfo."
}

Quote from: cryptocadxyz on April 20, 2018, 10:57:46 AM

For those of you who reindexed your wallet, please note that you need to also restart the Biblepay QT. I noticed that my wallet was not execing podcupdates after the reindex and when i ran one manually it said that my CPID was not associated. I restarted the wallet and then i was able to send podcupdates.
Just a tip so you don't miss out on the next block reward.

Maybe it was still syncing?

afeno

jr. member

Activity: 175

Merit: 1

Same here.
No PODC rewards on the last superblock. Sad

What is happening? Is it fixed?
And it seems that my magnitude was set to 0 in the last superblock so I cannot heat mine anymore...

How can I check how is my magnitude in the last superblock?

Thanks!

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