November 2017

i'll start with mainnet2, it's building now and going down shortly

Hold on, I have another thing I want to patch which will requires resync. We are failing to properly categorize P2SH spends because the pattern matching conflicts with other spend types.

ah, ok

nice, good finds

This is now complete in v3 and master. I still have to port the former issue to master, but v3 (head) is ready for deployment testing.

Master is now updated as well. However note that v3 is the release quality branch - master is staging for v4.

mainnet2 testnet going down shortly for an upgade and re-sync

I'll be in Riga, Latvia for Baltic Honeybadger 2017, Nov 25/26

master and version3 branches are now both updated. There was an additional change in libbitcoin, so if you had already updated server, sorry - need to do it again as of just a minute ago. This is basically two patches that both affect server indexing of address history. P2SH indexing was largely missed, and there was a race that caused infrequent dropping of entries for an addresses with multiple entries in multiple txs of one block. Once the community servers are updated and we have good feedback I'll tag a v3.4. Thanks everyone for the reporting and help!

mainnet2 and testnet2 going down shortly for the recent v3 update and re-sync

mainnet2 is finally back(!). testnet2 has been back for some time

:)

hrm, testnet2 w/o checkpoints seems to be getting stuck after block 11100 still

for now i'm going to enable checkpoints for testnet1

What is the error in the log when it gets stuck?

the one pasted above, rejected block

Did you verify the checkpoint?

ah, let me try that

Well default behavior always takes hold in that case.

and default is mainnet genesis?

Yes. I may eventually eliminate default checkpoints in v4.

i think it's fair, i just didn't realize. maybe worth warning that the node is configured for testnet but is using a mainnet checkpoint? not sure

Mainnet should be verified without checkpoints as well. The 3.4 changes affect address indexing, but I may have a consensus bug to patch when I get home in a few days. First one in a couple years, but not positive yet.

so the current status is this: mainnet2/testnet2 and now testnet1 are the very latest heads of version3. mainnet1 is the original v3.3. the plan was to use the mainnet2 store (i believe it's 3.4 compatible) on mainnet1

so that's the plan anyway at the moment. keep me posted and i'll rebuild when tagged

It won't invalidate the store, but it would be nice to get a full sync. It may be sufficient to checkpoint the full sync though, since the check is block static and prob wouldn't be skipped by checkpoints.

testnet1 back online and sync'd

as a point of reference, the store on mainnet1 (vanilla v3.3) is currently 312GB. The store on mainnet2 (pre-tagged v3.4) is currently 276GB. a solid ~11.5% reduction.

Yeah, it was just wasted space.

both mainnet1 and mainnet2 will be going down shortly and will be down until the updated store is copied over (estimating an hour or so).

mainnet1/mainnet2 back online!

Thanks!

np. still need to resync mainnet2 w/o checkpoints at some point, but crashing now ;-)

I've patched this issue in master and version3: https://github.com/libbitcoin/libbitcoin/issues/834

There is no need to resync community servers as I am resyncing locally and will verify the chain against the servers.

This patch is now merged.

community servers updated. was the version tagged?

Not yet.

ok good, wanted to make sure i didn't mess up :-)

Mainnet1/mainnet2 may be down. Power outage. Can be resolved later, but if a resync is needed, it may be a week or so before they're back in working order

Yes, they are both down.

ok, thanks, but ugh

testnet1/testnet2 back online!

👍

I've redirected testnet.libbitcoin.net to testnet1 due to an apparent configuration problem with testnet3, which is currently responding on secure queries only.

What time slots that caught your fancy?

Nothing in particular. There are 4 panels and I speak in 1/2/4. Libbitcoin is mentioned several times.

thanks for the youtube links!

👍

Regtest support is now fully implemented in the version3 branch.