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

[bible_pay]

If the pool is currently disabled, is the processing we're doing now being wasted?  Thanks!

No, the hashpower is not wasted because what happens is the stratum error (cant connect to pool) occurs, then it sleeps, so it doesnt use electricity; but yes, the miner would have to be restarted in solo mining mode to make the hashes count.

Actually this is a good point, because we would like everyone to help keep the network secure, so please run your biblepay client in solo mining mode if possible.

[1715189794]

1715189794

[1715189794]

1715189794

[1715189794]

1715189794

[1715189794]

1715189794

[bible_pay]

** BBP Network Wide update **


So, I heard back from all the exchanges and they all have put us in maintenance.

This puts us in a good position to release our new mandatory upgrade and regression test/verify it tomorrow in prod, to ensure the anti-gpu feature works as expected.  Once we verify DWS and Anti-GPU, then we will give the exchanges the green light to upgrade.  

So the timeline looks something like this now:

- We will release the new mandatory upgrade in the next few hours.
- The cutover height is for tomorrow at 9 AM.
- We will verify DWS and Anti-GPU in prod tomorrow.  Then we give the exchanges the green light to upgrade Tuesday.
- Sometime tomorrow, I will be working on releasing an upgrade to the external miner.  This will be required to work with the new version.

Please keep your eyes peeled for the mandatory upgrade.  The chain will cutover at height 170830.

Sanctuaries, we are going to take this opportunity to require a mandatory Sanc upgrade at the same time.  This upgrades the PODC rules to the latest which fixes the low payment bug also.

[bible_pay]

BiblePay
1.4.8.6-Mandatory Upgrade for Entire Network @ 170830

- Increase sanctuary protoversion to 70751 (Enable new consensus rules
for PODC - fix low payment bug)
- Adjust deflation rate to match target in GetBlockSubsidy
- Add anti-gpu measures to POBH (reject high-nonce blocks)
- Mandatory height: 170830
- Adjust DWS creation and validation for DWS 2.0
- Add upgradesanc warning when no \r\n exists (Togo)
- Add addl warnings to exec rac, and ensure exec rac does not crash the
node
- Remove dead code from miner; modify miner to handle anti-gpu nonce
rules

** Note: We also have a mandatory upgrade for the external miner, please find the binaries here:
https://github.com/biblepay/cpuminer/tree/master/binaries

** Sanctuaries, please upgrade also

** The new POBH 2.0 rules do not start until 170830, so in the mean time, the pool will reject most of the shares.  As soon as this height passes the pool should start working correctly.  The pool is coming back online now.

POOLS:  Please upgrade.  The software has been updated here:
https://github.com/biblepay/node-stratum-pool/commits/master
To upgrade please follow the upgrade instructions in this document:
https://github.com/biblepay/node-open-mining-portal/blob/master/Deploy%20a%20Nomp%20BiblePay%20Pool.txt

[Borgholio]

Out of curiosity, what's the difference between the bbpminer-x86.exe and the bbpminer32.exe binaries?  Thanks!

[bible_pay]

Out of curiosity, what's the difference between the bbpminer-x86.exe and the bbpminer32.exe binaries?  Thanks!

The x86 version is the 64 bit version, and the 32 is for 32 bit processors.
(I remember we had to add the 32 for Prof. Budinga when he reported the 64 bit didn't run on his 32 bit windows xp machine).

Good luck.  I see our diff is around 5K.  Not sure if this is because of low switchover rates or if this is the new environment.

[bible_pay]

So far so good, I just ran my sanctuary report and the nodes are all in sync and agree with the explorer (Chainz has already upgraded):

https://chainz.cryptoid.info/bbp/block.dws?170840.htm


Please, if anyone finds a discrepency after upgrading - post.


I'll verify POBH 2.0 and DWS next.  Caution:  Although DWS appears to be working now, I caution against using it for a few days until we verify we are exchange ready.  We don't want a burn in the chain to get rolled back when more hashpower gets added (as you could lose the funds if your burn is not recorded in the main chain).

[WhyMe]

Why continue using standard x11 hash if you don't want gpu ? If you don't want gpu taking advantage, why not migrate to randomX for example ?

[bible_pay]

Why continue using standard x11 hash if you don't want gpu ? If you don't want gpu taking advantage, why not migrate to randomX for example ?

Ours is far different than x11:  We have POBH, which has the KJV bible in it, and it has anti-gpu features on top of it.

The new bounty will be reinstated that POBH 2.0 cannot function better in a GPU than in a CPU.

EDIT: The x11 you see in nomp is just the label (its there because we also use x11 below pobh).   I'll edit it.

[WhyMe]

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

[bible_pay]

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

1) No, we don't
2) I am aware of randomX and its entire virtual machine and its code; and this is already taken into account for our dotnetcore version.


If you would like to give an example as to how you would run POBH in an asic or gpu, feel free to continue the discussion, but you cant.
Please review the code again in kjv.cpp.

[bible_pay]

** Compassion Update **

So I just want to give a compassion.com transparency update.

We've spent $177,224 at compassion (which is btw, 82% of our total charity expenses since inception).  We sponsored 4,657 orphan months of charity with them!  An amazing accomplishment!  Thank you everyone, this has certainly aligned a lot of our users with God by fulfilling James 1:27 for them.

Anyway, I gave them the 30 day notice to cancel all of our 81 children as of Jan 20th 2020 (to give us close to a zero balance).
However what's nice about Compassion is they not only have an insurance program to continue to cover a canceled child.  But also they sometimes give us a credit balance back for the extra days.  So we still have something like a $1,600 credit available to spend; and I was originally going to suggest Compassion for Babies, but since then I have come up with a better idea (also babies don't allow us to generate bios so there is less accountability).

I think what we can do for the most impact is go ahead and sponsor 10 more children with compassion, and this will give us approx 4 more months of positive impact then I will repeat the process and cancel those 10 around the beginning of May. 

Praise Jesus.

[WhyMe]

New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.

[bible_pay]

New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.

Have you tried restarting with the "-erasechain=1" switch?

[WhyMe]

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

[bible_pay]

You use a standard x11 hash, then you use it in your pobh layer.
But it stays a true x11 hash, which is gpu and asic mineable since years ...

1) No, we don't
2) I am aware of randomX and its entire virtual machine and its code; and this is already taken into account for our dotnetcore version.


If you would like to give an example as to how you would run POBH in an asic or gpu, feel free to continue the discussion, but you cant.
Please review the code again in kjv.cpp.

Just to give more clarity on this, let me explain how a POBH hash is computed and why you cant run POBH in a GPU (because you claimed 'this x11 was gpu and asic mineable for years'):

1) The hash of the block header is hashed with X11 first, but not used in the core wallet
2) The X11 hash is hashed with POBH
3) The POBH hash is used in the wallet

Therefore, you can't hash it in a GPU, and skip over the POBH hash and use it in BBP.  Of course Marcino, who ported POBH v1.0 to GPU actually *ported* the whole KJV and all of our code *into CUDA*, so he didnt simply run X11 in a GPU to mine bbp.

The new version released today is a *Stopgap* version.  It I believe, is going to be fine until we release our next-gen miner.  I want to stress, we are still working on something cooler that will do useful work while it mines in POW mode.  But POBH 2.0 is still very good- because it still produces bible verses, and cant run in an gpu due to the new rules.  I'm sure Marcino can certify this as he tries to hack it.  Because it will take the hacker more clock cycles to circumvent security than to create a new block in parallel.  The new security is based on the fact that a GPU miner must create more blocks than they care to per second of hashing.

[bible_pay]

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

From what I understand we already released the binaries, could you please ensure you are running the right bitness?  If not please post the URL and platform-bitness?
Im running windows 64 here and Im on 1487.  I never uninstall the old version; I just install the latest and it works.

[shorty34]

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

From what I understand we already released the binaries, could you please ensure you are running the right bitness?  If not please post the URL and platform-bitness?
Im running windows 64 here and Im on 1487.  I never uninstall the old version; I just install the latest and it works.

Hi Rob,

dns4.biblepay.org is still on version 1.4.8.4 - Could you please upgrade that one?

[WhyMe]

Just found a solo block.
Seems the new miner try sending xx times the same share.
I've replaced the params value by ... for best reading, but was the same value for each.
So it's 1 accepted and 12 rejected.
Running on 12 cores, probably a relationship.

[2020-01-20 14:27:15] DEBUG: got new work in 3 ms

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:20] accepted: 1/1 (100.00%), 159.00 khash/s (yay!!!)

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:25] accepted: 1/2 (50.00%), 151.49 khash/s (booooo)
[2020-01-20 14:27:25] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:29] accepted: 1/3 (33.33%), 141.08 khash/s (booooo)
[2020-01-20 14:27:29] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:34] accepted: 1/4 (25.00%), 144.30 khash/s (booooo)
[2020-01-20 14:27:34] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:38] accepted: 1/5 (20.00%), 158.82 khash/s (booooo)
[2020-01-20 14:27:38] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:42] accepted: 1/6 (16.67%), 157.78 khash/s (booooo)
[2020-01-20 14:27:42] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:47] accepted: 1/7 (14.29%), 157.52 khash/s (booooo)
[2020-01-20 14:27:47] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:51] accepted: 1/8 (12.50%), 158.96 khash/s (booooo)
[2020-01-20 14:27:51] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:56] accepted: 1/9 (11.11%), 157.34 khash/s (booooo)
[2020-01-20 14:27:56] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:00] accepted: 1/10 (10.00%), 159.26 khash/s (booooo)
[2020-01-20 14:28:00] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:05] accepted: 1/11 (9.09%), 153.30 khash/s (booooo)
[2020-01-20 14:28:05] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:09] accepted: 1/12 (8.33%), 144.01 khash/s (booooo)
[2020-01-20 14:28:09] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:17] accepted: 1/13 (7.69%), 149.78 khash/s (booooo)
[2020-01-20 14:28:17] DEBUG2: reject reason: duplicate
[2020-01-20 14:28:17] DEBUG: got new work in 9 ms
[2020-01-20 14:29:17] DEBUG: got new work in 13 ms

[bible_pay]

Just found a solo block.
Seems the new miner try sending xx times the same share.
I've replaced the params value by ... for best reading, but was the same value for each.
So it's 1 accepted and 12 rejected.
Running on 12 cores, probably a relationship.

Code:

[2020-01-20 14:27:15] DEBUG: got new work in 3 ms

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:20] accepted: 1/1 (100.00%), 159.00 khash/s (yay!!!)

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:25] accepted: 1/2 (50.00%), 151.49 khash/s (booooo)
[2020-01-20 14:27:25] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:29] accepted: 1/3 (33.33%), 141.08 khash/s (booooo)
[2020-01-20 14:27:29] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:34] accepted: 1/4 (25.00%), 144.30 khash/s (booooo)
[2020-01-20 14:27:34] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:38] accepted: 1/5 (20.00%), 158.82 khash/s (booooo)
[2020-01-20 14:27:38] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:42] accepted: 1/6 (16.67%), 157.78 khash/s (booooo)
[2020-01-20 14:27:42] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:47] accepted: 1/7 (14.29%), 157.52 khash/s (booooo)
[2020-01-20 14:27:47] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:51] accepted: 1/8 (12.50%), 158.96 khash/s (booooo)
[2020-01-20 14:27:51] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:27:56] accepted: 1/9 (11.11%), 157.34 khash/s (booooo)
[2020-01-20 14:27:56] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:00] accepted: 1/10 (10.00%), 159.26 khash/s (booooo)
[2020-01-20 14:28:00] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:05] accepted: 1/11 (9.09%), 153.30 khash/s (booooo)
[2020-01-20 14:28:05] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:09] accepted: 1/12 (8.33%), 144.01 khash/s (booooo)
[2020-01-20 14:28:09] DEBUG2: reject reason: duplicate

!!
 SOLUTION FOUND !!!!
x11 - HASH [01b958f15c8b407316342e64b2ba05ed31da3922d94e18d943fd99cded7b4e96]

!! bbphash
 - HASH [00000000036dbc4ae5b068513f3393d8907f46504572123dcb06e697fc7fe9e3]


SUBMITTING RPC1 [{"method": "submitblock", "params": ["..."], "id":1}
]
[2020-01-20 14:28:17] accepted: 1/13 (7.69%), 149.78 khash/s (booooo)
[2020-01-20 14:28:17] DEBUG2: reject reason: duplicate

[2020-01-20 14:28:17] DEBUG: got new work in 9 ms
[2020-01-20 14:29:17] DEBUG: got new work in 13 ms

Please - only paste long pastes if they are surrounded by code tags.

I corrected this one as an example.


Can you please confirm you are synced with the chainz block explorer?

[bible_pay]

Seems to be working, wallet is synching now, thanks.
But we can't upgrade from 1.4.8.5 ?

From what I understand we already released the binaries, could you please ensure you are running the right bitness?  If not please post the URL and platform-bitness?
Im running windows 64 here and Im on 1487.  I never uninstall the old version; I just install the latest and it works.

Hi Rob,

dns4.biblepay.org is still on version 1.4.8.4 - Could you please upgrade that one?

Thats someone elses node; I will repoint that one right now.