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

[bible_pay]

I was doing a little research to find out the era when the lifespan of man dropped from 1000 years to 100, as I was thinking it was an abrupt change.

(I was originally concluding because of Genesis 6:3, God commanded a change in the gene pool to abruptly change from 1000 to 100).  However after doing some research it appears the trend was very smooth instead:

https://wiki.biblepay.org/Genealogical_Ages

So now I believe the change was implemented to start after the flood and be complete by around the time the 12 tribes of Israel were born into a nation.

Very cool Rob.
I took the liberty of plotting it on a scatter plot rather than a bar chart. On the x-axis I plotted birth year before present, on the y-acix I plotted age at death. interesting stuff.



https://imgur.com/a/ryqCz

Very nice!  I am just guessing but I assume God's logic was to allow a longer lifespan to establish things and establish the population on the Earth.  It might have something to do with being fruitful and multiplying - if you live to 1000 you can have 10* more children (when the world needed to be populated with people).

[bible_pay]

Can anyone try and help madmurphy on the biblepay forums? He's having trouble with PODC-payments and I've run out of ideas to help him:

http://forum.biblepay.org/index.php?board=4.0

Hi Rob, we have tried but don't seem to be helping much.
Could you please take a look?
http://forum.biblepay.org/index.php?topic=141.15

Thanks

I see Jaap got him, cool.

[slovakia]

biblepay what you dont understand?  

missing the longest living guy: Matuzalem 969 years: translators of Bible had no knowledge of the fact that in the Old Testament, in the time before the legend of the sweat of the world. The age of man was calculated for months this is what little children learn at elementary schools in SLOVAKIA  

[bible_pay]

biblepay what you dont understand?  

missing the longest living guy: Matuzalem 969 years: translators of Bible had no knowledge of the fact that in the Old Testament, in the time before the legend of the sweat of the world. The age of man was calculated for months this is what little children learn at elementary schools in SLOVAKIA  

The wiki page doesnt say anywhere on it we are looking for oldest living humans does it?

[slovakia]

check old testament in church archive ... all is there.... i know this from religious education at primary school

[slovakia]

SHAME 38 ppl voted only... what are we waiting for now? almost week is this scheme same

[capulo]

at least 30 min stuck on 36079? whats wrong?

[FrankWatsonJr]

is others doing this masternode? how is your success with it?

[dave_bbp]

at least 30 min stuck on 36079? whats wrong?

Maybe the superblock at 36080 is having some problems? On the main pool all (heat) miners are gone, my windows wallet also doesn't really do anything when set to "setgenerate true 8" (normally this would block the CPU completely).

Let's keep calm and let the blockchain do it's thing.

[thesnat21]

I've got 3 machines "heatmining" on the main pool,  though the pool doesn't see them.

am in the same boat w/ stuck on block 79.  

[slovakia]

stakeed tooo

[cryptocadxyz]

Definitely stuck at 36079

[znjrols5]

at least 30 min stuck on 36079? whats wrong?

Maybe the superblock at 36080 is having some problems? On the main pool all (heat) miners are gone, my windows wallet also doesn't really do anything when set to "setgenerate true 8" (normally this would block the CPU completely).

Let's keep calm and let the blockchain do it's thing.

When I restart biblepay daemon, it starts mining again, then it stops after it finishes "synchronizing additional data" which takes around 5minutes, so I've set crontab restarting biblepayd every 5minutes, and this way it mines, and I can see my shares on pool.

[klappy]

I'm having the same issue of being stuck at block 36079. The only debugging info that I can find that might give a hint to the issue is that there are 6 outbound connections and 0 inbound. Patience and restarts result in the same issue. I'm doing wallet mining to help maintain the blockchain but it says I'm an hour behind. Seems like I can't help solve the next block if I don't have an inbound connection and receiving the latest data.

[Lichtsucher]

My debug.log contains this:

2018-03-22 23:16:43 IsBlockValueValid -- ERROR: Invalid superblock detected at height 36080: CTransaction(hash=f4ae2286aa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 03f08c0000)
    CTxOut(nValue=5470.19556860, scriptPubKey=210392a90fb9987d3c7fb1420b2e63)
2018-03-22 23:16:43 Height 36080.000000, Amount 5470.195569ERROR: ConnectBlock(biblepay): invalid superblock detected at height 36080

and:

2018-03-22 23:19:18 CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts
2018-03-22 23:19:18 Masternode indexes and governance triggers prepared  102ms

[znjrols5]

My debug.log contains this:

2018-03-22 23:16:43 IsBlockValueValid -- ERROR: Invalid superblock detected at height 36080: CTransaction(hash=f4ae2286aa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 03f08c0000)
    CTxOut(nValue=5470.19556860, scriptPubKey=210392a90fb9987d3c7fb1420b2e63)
2018-03-22 23:16:43 Height 36080.000000, Amount 5470.195569ERROR: ConnectBlock(biblepay): invalid superblock detected at height 36080

and:

2018-03-22 23:19:18 CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts
2018-03-22 23:19:18 Masternode indexes and governance triggers prepared  102ms

Also, this:
2018-03-20 17:31:02 ERROR: CMasternodePaymentVote::CheckSignature -- Got bad Masternode payment signature, masternode=8e8d6595dcee21ba7bbfcda2a3ebd6ece0adc2ccc28cbf7cc33023b28ebc86ac-0, error: Keys don't match: pubkey=4e5e8cd7cd0b9f2f74268aecaf73dd378a390661, pubkeyFromSig=67dd1b864cd47b36059283484a69e75940a50a28, strMessage=8e8d6595dcee21ba7bbfcda2a3ebd6ece0adc2ccc28cbf7cc33023b28ebc86ac-030705OP_DUP OP_HASH160 025cc54d334a09054f19f6ada50f05661709c638 OP_EQUALVERIFY OP_CHECKSIG, vchSig=HGL0jiXFYWhecJqKv5aV3W5pm5cpBbuJhO1Asx3wwjCSb4gnPjrWBN8BhVClRhPTD7LhsSFpwsk9F7/OzIhKFLI=

[bible_pay]

My debug.log contains this:

2018-03-22 23:16:43 IsBlockValueValid -- ERROR: Invalid superblock detected at height 36080: CTransaction(hash=f4ae2286aa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 03f08c0000)
    CTxOut(nValue=5470.19556860, scriptPubKey=210392a90fb9987d3c7fb1420b2e63)
2018-03-22 23:16:43 Height 36080.000000, Amount 5470.195569ERROR: ConnectBlock(biblepay): invalid superblock detected at height 36080

and:

2018-03-22 23:19:18 CGovernanceTriggerManager::AddNewTrigger -- Error creating superblock: CSuperblock::ParsePaymentSchedule -- Mismatched payments and amounts
2018-03-22 23:19:18 Masternode indexes and governance triggers prepared  102ms

Thanks, on the road but luckily I have the laptop, checking into this... so far it appears the daily superblock failed and the chain wont accept a normal block in place of it...

Checking....

[bible_pay]

Sancs, please vote down the current bad podc superblock:

gobject vote-many e41abd03827ac74114b118e602bd04d2cd9c0a4cde96f5b78c96f2695f8059b8 funding no

[bible_pay]

Sancs, please vote down the current bad podc superblock:

gobject vote-many e41abd03827ac74114b118e602bd04d2cd9c0a4cde96f5b78c96f2695f8059b8 funding no

Now vote in the fixed superblock:

gobject vote-many d8d6d4b43046c7a8f14acd2dfc31a49206e6e3e5b0e1e370a5797d2248a0c40f
funding yes

[ACP]

Looks like it's working now on miner end, also PODC updates are now being confirmed. Not sure about rewards.