Bitcoin full node and query server

September 2020

Archive of the libbitcoin Slack #general channel.

Saturday, September 12, 2020

X
xraid15:07
hi
15:07
I can't get V4 to sync
15:07
is it supposed to function to sync fully now
X
xraid15:15
14:22:51.160772 ERROR [node] Internal failure generating block locator for [185.107.80.146:8333] object does not exist
(edited)
evoskuil15:42
No, sync is incomplete.
X
xraid15:47
ahhh . good to know 🙂

Friday, September 18, 2020

X
xraid18:14
18:12:09.768306 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:14.770429 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:19.772423 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:24.774415 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:29.776226 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:34.778305 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:39.780446 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:44.782491 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:49.784050 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:54.786230 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:12:59.788325 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:04.790492 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:09.792602 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:14.794603 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:19.795829 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:24.798031 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:29.800016 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:34.801241 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out 18:13:39.803460 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out
evoskuil18:18
Are you suggesting mainnet.libbitcoin.net is offline?
X
xraid18:19
? looks like it
18:19
18:17:32.425577 INFO [network] Connected outbound channel [173.249.0.235:8333] (2) 18:17:34.898160 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out
neillm18:19
Shouldn't be, I can kick it if needed
18:19
Seems to respond here though
18:21
I'll shut it down and restart it -- one sec
X
xraid18:21
also why is time not in UTC in log
1 reply · pmienk · last Sep 18, 2020
pmienk19:29
The logging system uses utc. Is your system clocks utc time properly set?
X
xraid18:23
its up now
neillm18:23
What's the block height -- maybe I'm not sure which is mapped to mainnet right now
X
xraid18:23
18:23:27.441113 INFO [blockchain] Block [648952] 2634 txs 5638 ins 11 wms  92 vms  16 vµs  3 rµs  1 cµs  9 pµs  3 aµs  0 sµs 577 dµs 0.992404
neillm18:24
On mainnet.libbitcoin.net, I mean
(edited)
X
xraid18:24
same as core
18:24
2020-09-18T18:23:23Z UpdateTip: new best=00000000000000000000a885a59129bd8d0aaf7e1747bec1646467da7c034b03 height=648952 version=0x20400000 log2_work=92.297073 tx=569603725 date='2020-09-18T18:23:15Z' progress=1.000000 cache=112.8MiB(820043txo) warning='63 of last 100 blocks have unexpected version'
neillm18:25
Ok, good. I had taken mainnet1 down, but I think mainnet.libbitcoin.net is mapped to mainnet2, which was current (and that's the mapping we want). mainnet1 was a couple blocks behind, catching up because i took it down earlier today
X
xraid18:28
ahhhbx fetch-height tcp://mainnet.libbitcoin.net:8333 connection timed out
18:33
could be some router jokey from EU to USA ?
18:35
I can't reach mainnet from local but can from central EU
18:39
but bx fetch-height tcp://mainnet.libbitcoin.net:8333 times out
evoskuil18:49
Port?
neillm18:56
Try bx fetch-height tcp://mainnet.libbitcoin.net:9091
X
xraid18:58
ahhh yes block 648956 om main net now
evoskuil18:59
You were using the p2p port.
X
xraid18:59
yeah my confusion sorry
evoskuil18:59
Np
X
xraid19:00
my node now connects to mainnet fine again
👍 1

Saturday, September 19, 2020

neillm01:33
@xraid No worries, it happens and I've made that mistake myself. Just remember: Port 8333 ... slow p2p port ... Port 9091 ... fast zmq port (this is your friend for real work). Totally unbiased info here! 🙂

Tuesday, September 22, 2020

A
Artem14:37
@neillm Hi, i got a problem how to generate key and address for testnet node? auto prv = hd_private(root_key, hd_private::testnet);//this works well and private key is correct and succed imported to node auto pub = prv.to_public();//guess this is incorrect because it didnt give me valid testnet pub key return ec_public(pub.point()).to_payment_address().encoded();//this is address formating
(edited)

Wednesday, September 23, 2020

neillm00:49
@Artem When you call to_payment_address, you pass in a version. Try passing in either payment_address::testnet_p2kh or payment_address::testnet_p2sh (rather than use the default for mainnet).

Friday, September 25, 2020

X
xraid14:05
@neillm mainnet
(edited)
14:08
since 12:41:17.922227 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out
14:08
to now 14:08:10.140967 WARNING [network] Failure connecting [mainnet.libbitcoin.net:8333] manually: connection timed out
(edited)
neillm14:39
Wrong port nevermind, try again
(edited)
14:41
DNS should be mapping mainnet to mainnet2 btw ...
14:41
I think it's not anymore
X
xraid14:51
works now 14:40:56.569323 INFO [network] Connected manual channel [mainnet.libbitcoin.net:8333] as [72.65.246.83:8333] (3)
(edited)
X
xraid14:57
maybe think of a HAProxy fallback set up . so any 1-4 ? can answer if up with only main net dns conf
neillm15:00
I don't run the dns, but yeah, I considered something like that in the past on the machine actually being mapped. Haven't had time yet 😉
X
xraid15:02
SysOp is fun but less so then DevOp 🎉

Wednesday, September 30, 2020

X
xraid09:03
i try do 
bx fetch-block
and i get : object does not exist
09:04
bx fetch-block -t 1
(edited)
09:06
bx fetch-block --height 650631
09:09
same : object does not exist ?
neillm12:25
This is a version 4 API, so you need to query a v4 server (i.e. you run one, as no public ones are known at this time).
12:27
Unofficially, if you create a bx.cfg file with the url line like url = tcp://testnet2.libbitcoin.net:29091, you can run this: 
./bx fetch-block -c bx.cfg.v4.testnet -t 1
block
{
    bits 486604799
    hash 00000000b873e79784647a6c82962c70d228557d24a747ea4d1b8bbe878e1206
    merkle_root f0315ffc38709d70ad5647e22048358dd3745f3ce3874223c80a7c92fab0c8ba
    nonce 1924588547
    previous_block_hash 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943
    time_stamp 1296688928
    version 1
    transactions
    {
        transaction
        {
            hash f0315ffc38709d70ad5647e22048358dd3745f3ce3874223c80a7c92fab0c8ba
            inputs
            {
                input
                {
                    address_hash a2f76840287f14442f42551050c8700d8ad16481
                    previous_output
                    {
                        hash 0000000000000000000000000000000000000000000000000000000000000000
                        index 4294967295
                    }
                    script "[20e7494d] [7f] [2f503253482f]"
                    sequence 4294967295
                }
            }
            lock_time 0
            outputs
            {
                output
                {
                    address_hash ee9103399bfb42a091a7b537bed4a8552e9611ca
                    script "[021aeaf2f8638a129a3156fbe7e5ef635226b0bafd495ff03afe2c843d7e3a4b51] checksig"
                    value 5000000000
                }
            }
            version 1
        }
    }
}