BiblePay - 1.4.4.0
Leisure Upgrade for Users/Mandatory Upgrade for Sancs
- Modify Sanctuary GSC contract to account for maximum possible QT
change in 24 hours - Enhance spork for replaying blocks, allowing the wallet to Reassess
all non-main-chains
- Add payment limits information to exec testgscvote
- Add exec reassesschains command (this allows the user to manually kick
off a reassess
- Increment protocol version to force a mandatory sanctuary upgrade to
70735
Thanks for the welcome. Gilligan is too nice. I'm pretty sure he's more of a help to me. Just reading that testnet topic on the Biblepay forum blows my mind. Can you please tell me how to do this upgrade for windows? Appears I'm lagging here as 177 of 186 MN are now running the new version. To upgrade windows, you can just download the new version from the website (biblepay.org | Top level menu | Wallet downloads), save it to the drive, unblock it, run it, let it overwrite the old version, then when you re-run it, it will be the latest. Be careful though. This only works if you have your BBP wallet installed in the standard Windows directory (Program Files). If you are like me and have an extra folder for your mining/coin stuff, you have to manually select the correct installation folder every time you upgrade the BBP wallet, because the installer does not look for the actual installation folder. Just upgraded Win and Sanc wallets. I had to "Start" my sanc again, because right after upgrade it said "node just started, not yet activated". Is this expected to be required, or was I just too impatient? Nevertheless, it all works fine now on 1.4.4.0. CPU utilization in windows also seems to be roundabout the same as before (I'm using limit 8, sleep 10 on an older Xeon 1230v3 to get approx. 50% utilization). |
|
|
|
|
Rob, I'm still not exactly sure how the POG leaderboard works. For example I currently have "owed" coins 561.1 with a prominence of 0.6. This is the exakt same amount like someone called "trumpfan" has.
However, I have more than 20x the amount of "points" on the leaderboard than him. So how do these translate to the owed amount? Or is this just another hickup in the time frame of both columns?
Also, talking to a friend of mine who hasn't enough BBP for the new masternodes, it seems like just doing POG pays a lot better than the sancs. He made several hundered thousand BBP in one week. Of course this will slowly decrease with his lower coin age, but it's still orders of magnitude higher than sanc payments.
|
|
|
|
This is a long shot, but it cant hurt to try, could you please try going to coin control and check the row for the CHRISTIAN-PUBLIC-KEY, and then run the 'exec upgradesanc sancname 0' (dry run) again, and see if it actually emits? If so, we have to relax the rules in the next version.
I tried that, but same result. Status: 1/unconfirmed, broadcast through 9 nodes
Date: 03.07.2019 22:43
Total debit: -1.00000000 BBP
Total credit: 1.00000000 BBP
Transaction fee: -0.00243000 BBP
Net amount: -0.00243000 BBP
Transaction ID: 2f57d242c8e5cc4615d8375aaf17d43db32618b3cbe386a2d9cf7fbdda84b02a
Output index: 0
Transaction total size: 242 bytes
Height: 129407
Difficulty: 5010.29
Time: 07-03-2019 20:43:47
Subsidy: 5519.6978
Debit: -1.59708742 BBP
Credit: 0.59465742 BBP
To: BByCR19ExW8yUWZnj1A7SrvGrYyYtPSpSg 0.0000 BBP
Credit: 1.00000000 BBP
To: BC2kWHxwREa9htb34wutbwgxMFnPhyMBCE 1.0000 BBP
Transaction:
CTransaction(hash=2f57d242c8, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=129332, vExtraPayload.size=0)
CTxIn(COutPoint(a09af9d34b7065710682c4e14c6b550128c222015897122d05047cefa3c1394b, 1), scriptSig=47304402203afa0f2a4a2903, nSequence=4294967294)
CTxOut(nValue=0.59465742, scriptPubKey=76a914527b08b965629bd94e916463)
CTxOut(nValue=1.00000000, scriptPubKey=76a91453271202ceb79965ed4392d7)
|
|
|
|
1) You are running this from QT, correct?
2) Could you please ensure your coin control has absolutely no coins selected when you run the command? If one coin is selected, it might be unable to fund the dry-run pro tx.
Yes and yes, but still no luck.  Ok, we will try other things then. The wallet does need the "CHRISTIAN-PUBLIC-KEY" to send 1bbp to, can you check to see if yours exists and has more than 1bbp in it? (IE it hasnt been renamed or deleted right)? Yep, it's there and has several thousand BBP in various denominations in it, which almost all date from 2nd or 3rd of July. There is one older input, but it's <1BBP. |
|
|
|
1) You are running this from QT, correct?
2) Could you please ensure your coin control has absolutely no coins selected when you run the command? If one coin is selected, it might be unable to fund the dry-run pro tx.
Yes and yes, but still no luck. |
|
|
|
I just tried it and I get this: 
exec upgradesanc MN1 0
No funds at specified address (special transaction error) (code -32603)
What specified address is it referring to? I believe any address you have funds in; you need at least 1 bbp to run the command. Please ensure the wallet is unlocked and has at least 1 bbp plus the 4.5MM locked collateral for the sanc in the same wallet. NOTE: There was an error in the Dash link above - I corrected it (it was expired). Note2: I will try to upgrade one of my prod sancs now using upgradesanc. Nope, that can't be it. My wallet is unlocked and has more than enough coins. The command actually initiates a "payment to yourself" each time I execute it: Status: 1/unconfirmed
Date: 03.07.2019 21:56
Total debit: -1.00000000 BBP
Total credit: 1.00000000 BBP
Transaction fee: -0.00391000 BBP
Net amount: -0.00391000 BBP
Transaction ID: a36e60b6e483cd42d6f47e8ae8091b28f10e7db86594d4b216686257d5f8666d
Output index: 0
Transaction total size: 389 bytes
Height: 129404
Difficulty: 2975.01
Time: 07-03-2019 19:57:18
Subsidy: 2868.8632
Debit: -1.00000000 BBP
Debit: -0.13399582 BBP
Credit: 0.13008582 BBP
To: BB5o9DyyrrwPJhwcKw4rX8csfhZdppQFHL 0.0000 BBP
Credit: 1.00000000 BBP
To: BC2kWHxwREa9htb34wutbwgxMFnPhyMBCE 1.0000 BBP
Transaction:
CTransaction(hash=a36e60b6e4, ver=1, type=0, vin.size=2, vout.size=2, nLockTime=129403, vExtraPayload.size=0)
CTxIn(COutPoint(a09af9d34b7065710682c4e14c6b550128c222015897122d05047cefa3c1394b, 0), scriptSig=47304402203b690e40f5b571, nSequence=4294967294)
CTxIn(COutPoint(dcdfae64eedf2c1037b84c38f3d09b651576cbce1bfd7dd042b69347c5f66974, 0), scriptSig=4730440220149688a0ea5378, nSequence=4294967294)
CTxOut(nValue=0.13008582, scriptPubKey=76a91448c264bc9886d57c57516652)
CTxOut(nValue=1.00000000, scriptPubKey=76a91453271202ceb79965ed4392d7) |
|
|
|
I just tried it and I get this: 
exec upgradesanc MN1 0
No funds at specified address (special transaction error) (code -32603)
What specified address is it referring to? |
|
|
|
You just have to have ABN weight in the block, lets look at possible issues.
Its unlocked and unencrypted so that makes it easier.
Type: exec getabnweight
See if its > 256k?
If its not you need a little more age. 256k = 1 day of coin age * 256,000 bbp.
(Or you can temporarily send more to it).
Another tip: If your wallet is not mining (IE 0 hps in getmininginfo), you can look in the log and scan for "biblepayminer" or "ABN", and it should have some type of error in there.
PS: That explains why our diff dropped!
Ah I see, that makes sense. So the abnweight=256k is a coin age weight, not just an amount. Right now getabnweight gives about 60k, so either I wait until tomorrow, or I send more coins now and reduce the waiting time. But it would also be possible the other way round, right? Let's say I now pull off 128k from this wallet and wait for 2 days, the result is the same and the risk of the unlocked wallet is reduced (if there is any at all...). Nice to know that. |
|
|
|
|
Somehow I can't get my miners to work on the pool.
I copied a fresh wallet without a password on all of them and sent 256k there a couple of hours ago. The wallets don't have any password. However when I start the clients the "getmininginfo" output always shows "gsc_errors: low abn weight 0". Is there any additional requirement?
|
|
|
|
Thanks, yeah, I found it. So, it looks like your 1.85B point transaction made it into superblock 126095 and pays 359420. Congrats.
It appears the root of the issue is exec analyze should add 205 blocks to the height typed in - another words, we pay the rewards in the superblock after the close of the current superblock.
Ill fix that now.
Ah I see, thank you for clearing that up. So the same can be said for the leaderboard in the QT wallet, which looks almost 1 day into the future, so to say? I just tested another 1k POG payment and now my leaderboard says "owed 1.6k", which then would be for the superblock the day after tomorrow (126300), right? |
|
|
|
Can you do me a favor and give me the txid of the 50K tx?
Yep sorry, forgot to post that: exec getpoints f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29

{
"Command": "getpoints",
"pog_points": 1852187327.259578,
"coin_age": 50276099.10347233,
"diary_entry": "",
"orphan_donation": 50000
}
exec analyze 125890 dave_bbp
{
"Command": "analyze",
"Totals": "HEALING|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|0|0.00000000|dave_bbp|32395\nPOG|BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U|1852187327|0.37424046|dave_bbp|4701730961\n",
"0": "User: BM2e5zvdEf8jcosQdhP6e7NRs8kEMqJy7U, Diary: , Height: 125733.00, TXID: f7944ae99e93941080390e4164c815fc132cf819c60f25924e6a2513013a4c29, NickName: dave_bbp, Points: 1852187327.26, Campaign: POG, CoinAge: 50276099.1035, Donation: 50000.0000, UserTotal: 1852187327.26",
"1": ""
}
|
|
|
|
That's awesome stuff, Rob. Looking forward to some new statistics. Today I had another weird experience with the POG system, which I don't understand. Here's what's happened: Yesterday evening I had some issues with my masternode. So I decided to temporarily take it down and just once test how some of those now "free" coins would work in POG. I chose the MN coins from the inputs and manually sent 50k BBP via "exec sendgscc". After that I waited a couple of hours and was very pleased when the leaderboard showed my account with "owed: 200k". However, in the following payment I only received a mere 780 BBP.  Since yesterday I did not send out another POG donation, but after the last superblock my name came up again in the leaderboard, now showing "owed: 300k". So I had hoped, maybe tomorrow I get some of my 50k back. Unfortunately right now I'm completely missing from the leaderboard. So does this mean I lost my 50k into Oblivion? For me the system is still completely non-transparent.  |
|
|
|
Quick question: What will happen to the pool miners/workers once abn weight requirement kicks in? Will all workers not meeting it automatically be rejected by the pool? P.S.: Is the sanctuary payment gonna improve again in the future? Right now sancs pay half of what they paid before Evo and I don't think investors gonna like that very much.  |
|
|
|
So on this headless password, sorry, I gave you the wrong info. We made the first part of it an argument instead, this is to keep it out of the bash log (like FTP clients do).
So please try this (I think special chars will be OK):
biblepay-cli -headlesspassword <enter>
<Enter password here>
Then step 2:
biblepay-cli autounlockpasswordlength <enter>
<Should report the length of the pass>
The password that is memorized by the command will be used in the auto-unlock feature.
P.S. To script this, you can use an FTP-type script. MIP has one and I have one I could send you if you need it.
Awesome, now it works as it's supposed to do. I don't think I'll need an extra script for this since I won't use it too often and it's not really complicated once you know the trick.  On a completely unrelated note: I can't delete workers from my workers list on pool.biblepay.org There is the "garbage" symbol at the end of the line, but this is not clickable. Tested in Firefox and Vivaldi. |
|
|
|
Thanks Rob for your dedication! I think I found my mistake now. The moment that I associated my CPK (which I had to unlock my wallet for) the wallet itself sent out my very first GSC Transmission, whose details are: "Command": "getpoints",
"pog_points": 64935191.18979269,
"coin_age": 6493519.11897927,
"diary_entry": "",
"orphan_donation": 1000 I didn't know this and was therefore confused. Sorry about that. The new command seems awesome and easy to use, I'll check it out in the upcoming versions. Regarding the headlesspassword: This doesn't work for me, unfortunately. First, I discovered that the -cli in windows specifically looks for the biblepay.conf in the standard folder, whereas my biblepayevolution folder is located somewhere else. After I copied a dummy .conf to appdata/roaming... it responded fine (e. g. with getinfo etc.), but "headlesspassword" still throws an error: error code: -32601
error message:Method not found
[rest of my password] I think the problem is, that my wallet password contains a special character (followed by [rest of my password]). @MIP: Don't stress yourself for supporting Armbian, I don't think alot of people use this. Maybe I'll just try Ubuntu on my Odroid, when I have the time ... |
|
|
|
Edit: the new Linux binaries don't work anymore. The Arch Linux x64 gives an "error in binary file", the Linux 32 can't even be executed (only gives "no such file or directory"), same goes for the ARM version.
Can you please give me details on which platforms you are executing those binaries respectively? Output from should be enough for each system. Sorry, for the "normal" Linux I just realized that I got confused with the organization of the downloads on the webpage and apparantly had the wrong one. For ARM: the new version works if you have Ubuntu for ARM installed, but it fails for armbian: Linux odroidc2 4.19.42-meson64 #5.86 SMP PREEMPT Sun May 12 19:04:28 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux Thx. |
|
|
|
Will be back in a little while, but in the mean time Dave you can do an 'exec getpoints txid' on the first tx, then on the second.
I hypothesize on the first one you had all that unspent coin age (like the guys said here) and on the second you had very little age.
Nope, that's not it. Actually the second coin age was even higher. Here's the details: "Command": "getpoints",
"pog_points": 6732621.631641014,
"coin_age": 673262.1631641014,
"diary_entry": "",
"orphan_donation": 1000 => POG payment 15k "Command": "getpoints",
"pog_points": 21944033.90635219,
"coin_age": 750475.4030584025,
"diary_entry": "",
"orphan_donation": 25000 => POG payment 1.3k "Command": "getpoints",
"pog_points": 16899955.68905194,
"coin_age": 577970.3545636164,
"diary_entry": "",
"orphan_donation": 25000 => POG payment unknown right now, but leaderboard shows me with only 0.1 prominence and "owed" 980. [edit: payment was 15.1k, no idea how this had anything to do with what the leaderboard stated earlier ...] If not even the "pog_points" correlate with the reward, then what does? We do have the autounlock feature but its accessed from the command line now:
./biblepay-cli headlesspassword password
AFAIK this only works for CLI, but not for the GUI wallet I use in Windows. It only returns "method not found" Edit: the new Linux binaries don't work anymore. The Arch Linux x64 gives an "error in binary file", the Linux 32 can't even be executed (only gives "no such file or directory"), same goes for the ARM version. |
|
|
|
Could anyone plz explain how this POG works in numbers? I tried to get the hang of it over the last 2 days but failed miserably. Here's what's happened: I associated everything, put "pog_coinagepercentage=.50" and "pog_foundationdonation=1000" in the conf and sent one transaction via . Everything worked fine, but I was very surprised to see that on the following superblock my reward was a whopping 15k BBP! After this I tried to send more donations (a couple of 1k and also a large 25k donation). So for the next superblock I had contributed more than 30k BBP. However now my reward was only 1.2k, so actually I lost 30k BBP today! How is this even possible? Also it would be really nice to have the "auto-unlock" feature back for the QT wallet (like we had for PODC), because I hate to leave my wallet unlocked and I usually don't have time to send anything manually. Thx in advance. |
|
|
|
BiblePay
1.4.3.3-Leisure Upgrade
** Note: Sancs, please upgrade within 21 days at your convenience **
** Linux and Mac is building **
Mac and Intel Linux (32/64 bit) compiles are ready, ARM (32/64) still building. ARM (32/64) binaries ready. Excuse my stupid question, but where do I find these? The website doesn't list anything for ARM; the latest release on github is 1.4.3.1 and there seems to be no repository for ARM. btw: up to now my windows QT wallet hasn't crashed again |
|
|
|
I thought you knew it would be changing when we retired POG and started creating GSC's for Evo (along with all the new evo features) - please see here: https://wiki.biblepay.org/Nutrition_InformationI posted this a while back. I'm shooting for us to be a top 100 coin. I surely hope you didn't want to keep everything the same as it was and stay a #1000 coin. (As I think originality is what makes us worthy of top 100). On the leaderboard clearing, I think that only happens once every 90 days roughly (when Im working on it). I happen to be working on it today, because our HPS is astronomical (pending the release that is coming in 4 hours). Regarding CPK, please try to unlock the wallet first. Then see if you have a Christian-Public-Keypair in the address book if that does not work. If it still doesn't work paste the log surrounding the exec cpk command. Regarding crashing on win10, I don't have any other users claiming that. You will have to try to reproduce and tell us what happens right before the crash. Maybe start with -zapwallettxes=1 first and see if that helps. We had one incident of crashing on a NULL wallet txid entry. Awesome, thanks for answering. Of course I did not unlock the wallet before trying to exec cpk. Stupid me. Now it worked and I am in the leaderboard (sending the payment manually because I don't like to leave my wallet unlocked ... I also tried the zapwallettx 1, let's see if it helps with the random wallet crash. Other than that it seems like the transition to EVO went smooth. I'm excited to see what the future holds for this coin. |
|
|
|
|
Show Posts
