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

[znffal]

ROB  same problem like others ... no rewards in last SUPERBLOCK    where is problem?  

I'm pretty sure most people that missed the superblock was because their wallet got stuck in the chain. I had to clean my MN wallet and reindex

[1713558574]

1713558574

[1713558574]

1713558574

[slovakia]

znffal my wallet was on correct chain=block, users carwash too ... we are on 1117 wallets

Rob didnt receive superblock reward too

 ... im curious about Robs answer  

[znffal]

znffal my wallet was on correct chain=block, users carwash too ... we are on 1117 wallets



 ... im curious about Robs answer  

Ah, then I don't know

[capulo]

i'm not stuck, already on block 41881, had update, had everything, except payment

was there any payment at all?

[coinsinspect]

I found this old post:
Quote from: slovakia on March 30, 2018, 09:17:36 AM
Rob any advice why we have different CPID when we registered with same email like on rosetta? thanks

Yeah, my CPIDs are different also. Same email address.

I've been reading this. Let's see if it can help...

https://steemit.com/gridcoin/@dutch/the-definitive-guide-to-fixing-a-split-cpid-gridcoin-s-and-boinc-s-1-problem

[slovakia]

i'm not stuck, already on block 41881, had update, had everything, except payment

was there any payment at all?

nebud nemtavy a pozri si kazdeho odmeny https://www.biblepay-central.org/en/podc-leaderboard/  sa to klasicky prerozdelilo medzi ostatnych

coinsinspect stop spamming

[jaapgvk]

Yeah I wouldn't trust the pool from yesterday. I'm pretty sure that info was completely off from my final payout.
 

I received about double the BBP I was expecting in the last superblock. I went and checked the superblock-report on the pool right after that, and it was still showing the latest block (Height: 41820). A lot of people weren't in the report, and everyone who was in had about double the magnitude you would expect.

When I look at the pool superblock-report now (Height: 42025). Everyone seems to be back on the list again, so I don't think it was related to 'stalled wallets' in hindsight, because I would still expect missing people if that were the case.

But whatever it was, its something that shouldn't have happend, and we should look into what went wrong.

[turbokongen]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:
https://pasteboard.co/HhCbPKK.png
Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

[jaapgvk]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:

Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

Hi John,

Unfortunately, the link to the image isn't working...

[znffal]

Yeah I wouldn't trust the pool from yesterday. I'm pretty sure that info was completely off from my final payout.
 

I received about double the BBP I was expecting in the last superblock. I went and checked the superblock-report on the pool right after that, and it was still showing the latest block (Height: 41820). A lot of people weren't in the report, and everyone who was in had about double the magnitude you would expect.

When I look at the pool superblock-report now (Height: 42025). Everyone seems to be back on the list again, so I don't think it was related to 'stalled wallets' in hindsight, because I would still expect missing people if that were the case.

But whatever it was, its something that shouldn't have happend, and we should look into what went wrong.

Yes I guess it depends when you looked at it. I think I looked at a time when things were funny. But it looks perfect today.

[zhugy78]

BiblePay takes out 10% of the coins and goes directly to the third world countries to sponsor orphans, a very meaningful project. It has improved children's lives and hopes that the project has been going well.

[turbokongen]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:
https://photos.app.[Suspicious link removed]/pv0LK9hyWCf6KRra2
Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

Hi John,

Unfortunately, the link to the image isn't working...

I updated the original post with a different share link.
Thanks.

[jaapgvk]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:

Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

Hi John,

Unfortunately, the link to the image isn't working...

I updated the original post with a different share link.
Thanks.

Thanks. Let's see... If you really followed the cleaning guide step-by-step, and it didn't work, then I would suggest to just start all over again. Backup your wallet.dat (and also the backup folder, just to be sure). Then remove the wallet (+ all files in your appdata folder). Reinstall the wallet, start it and let it sync. Then close the wallet and put your old wallet.dat in your appdata folder. Then restart.

Maybe this isn't necessary, and someone else has another solution. I just say what I would personally do in a situation like this

[turbokongen]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:
https://photos.app.[Suspicious link removed]/pv0LK9hyWCf6KRra2
Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

Hi John,

Unfortunately, the link to the image isn't working...

I updated the original post with a different share link.
Thanks.

Thanks. Let's see... If you really followed the cleaning guide step-by-step, and it didn't work, then I would suggest to just start all over again. Backup your wallet.dat (and also the backup folder, just to be sure). Then remove the wallet (+ all files in your appdata folder). Reinstall the wallet, start it and let it sync. Then close the wallet and put your old wallet.dat in your appdata folder. Then restart.

Maybe this isn't necessary, and someone else has another solution. I just say what I would personally do in a situation like this

I'll give that a go. Thank you.

[turbokongen]

Hi,
I was just doing some maintenance after discovering the wallet had crashed, and followed the wallet update and cleaning guide.
Now the wallet just crashes with this:
https://photos.app.[Suspicious link removed]/pv0LK9hyWCf6KRra2
Balance is 0, the wallet seemingly does continue to run, but it isn't since when it is restarted, it start to sync all over again.
Please advice.

Rgds
John

Hi John,

Unfortunately, the link to the image isn't working...

I updated the original post with a different share link.
Thanks.

Thanks. Let's see... If you really followed the cleaning guide step-by-step, and it didn't work, then I would suggest to just start all over again. Backup your wallet.dat (and also the backup folder, just to be sure). Then remove the wallet (+ all files in your appdata folder). Reinstall the wallet, start it and let it sync. Then close the wallet and put your old wallet.dat in your appdata folder. Then restart.

Maybe this isn't necessary, and someone else has another solution. I just say what I would personally do in a situation like this

I'll give that a go. Thank you.

Ok. Now I uninstalled the wallet through windows app manager, deleted the BiblePayCore directory reinstalled, and excactly the same error. It happens when the wallet starts to sync against the network.
Cleaned out again. Installed the 32-bit version, and excactly the same. I'm at a loss now.
From the debug log:

Code:

2018-04-21 09:01:24 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

2018-04-21 09:01:24 

************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE       
bad lexical cast: source type value could not be interpreted as target       
C:\Program Files (x86)\BiblepayCore\biblepay-qt.exe in Runaway exception       

And also:

Code:

************************
EXCEPTION: St8bad_cast       
std::bad_cast       
C:\Program Files\BiblepayCore\biblepay-qt.exe in ProcessMessages()      
2018-04-21 09:19:33 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument 

[dave_bbp]

Well, that sucks...
I updated both my controller wallets (Windows x64) to 1122 on Thursday and I never had any problems, no chain stuck, , no errors whatsoever, everything synced without hesitation. However I didn't get any payouts on the last superblock. :/
Moreover, since I didn't receive any payout my heat-miners are useless because my CPID has no magnitude from the last payment. Maybe it would be a good idea to soften this rule, say perhaps look at the average magnitude from the last 5 superblocks and if it's >0 then allow heat-mining...

Would be nice if we could get behind what caused this and prevent it from happening again today. I myself am at a wedding so I won't be here again until sometime tomorrow.

[afeno]

Same here.
No PODC rewards on the last superblock.     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!

[Dimarzio123]

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?
*********************************************************

Stand down!!

Waited for 30 minutes
Seems to sorted itself out

Regards
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."
}

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]

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...

[gagaha]

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!