You are more interested in the first one: f1b2be0790514f7bcca7653889ddfd7daac08ac1123c708d9d764abc04f1c3e8 , as this one has the 226,615,208 points on it.
Then do an 'exec getpoints f1b2be0790514f7bcca7653889ddfd7daac08ac1123c708d9d764abc04f1c3e8' and lets see what comes out.
"Command": "getpoints",
"pog_points": 226152084.6227908,
"coin_age": 22615208.46227908,
"diary_entry": "Prayed for my teen nephew to make his tumor gone",
"orphan_donation": 1000
So be very careful and disregard the *10 multiplier on the orphan donation (cubed root of (1000)), and just hone in on the coin_age of 22.6MM.
So the elephant in the room is, Orbis, do you have 22 mil coin age?
This could be 2.2MM bbp just 10 days old btw...... So that sounds very possible.
Now if you watch his next one, he is probably reset to zero meaning tomorrow he would have more like a 2.2 MM coin age.
that would be awesome
I've used 472k for sendgscc, but it looks that my coinage makes the magic
it looks that there were all coins from POG.
And I'm sorry, I didn't read this thread before. Now I saw that you want just to send 2,5BBP.
Sorry, I saw that POG works, and I used my testnet configs. My huge superiority in leaderboard was the moment why I started to read this thread
And I have question.
It's needed to use something like "utxooverride=-1" on my VPS or it is guaranteed that GSC tx will run only once per 12h per one CPK?
Rob, and I think that I found a bug.
When I click on any new (unconirmed) tx in transaction view, my wallet crashed (WIN 10 64bit).
It happens to me yesterday and today. I has only log from yesterday, but it was the same today. here is:
https://pastebin.com/P2WD5tkvNote: After you upgrade to 1.4.3.2, please do a
./biblepay-qt -zapwallettxes=1
If you still experience a crash on a tx double click; from what I'm seeing - the root of the problem is in a non-zapped tx in the local wallet.
Everyone else - you don't have to do this.