Bitcoin CLI tooltips and hacks @BitcoinToolTips

bitcoin-cli getblock $(bitcoin-cli getblockhash 666666) 0 | xxd -r -p | fq -d bitcoin_block '.transactions[] | .outputs[] | select(.scriptpub[0].op == "return") | .scriptpub[1].arg'

$ bitcoin-cli getblock $(bitcoin-cli getblockhash 0) 2 | jq .tx[0].hex | xxd -r -p | strings | head -n 1 EThe Times 03/Jan/2009 Chancellor on brink of second bailout for banks Happy Birthday #Bitcoin 🥳

bitcoin-cli getblock $(bitcoin-cli getblockhash 0) 0 | xxd -r -p | xxd

calle @callebtc

4 years ago

bitcoin-cli getblock $(bitcoin-cli getblockhash 0) 0 | xxd -r -p | xxd https://t.co/Eg70OxhmIQ

4 0 8 0 2

bitcoin-cli getblockhash 0 | xargs -I{} bitcoin-cli getblock {} 0

$ bitcoin-cli getblockchaininfo | jq .softforks.taproot.bip9.status "active"

@pwuille @Mario_Gibney $ date -d "+$(bitcoin-cli getblockchaininfo | jq '.softforks.taproot.bip9.min_activation_height - .blocks')0 minutes" -uR Wed, 17 Nov 2021 13:31:05 +0000

Finding missed opportunities in lnd.log: zgrep "insufficient bandwidth to route htlc" ~/.lnd/logs/bitcoin/mainnet/lnd.log* | grep "ChannelLink" | cut -d' ' -f5,11 | awk 'BEGIN { FS=OFS=SUBSEP=" "}{arr[$1]+=$2 }END {for (i in arr) print i,arr[i]}' | sort -n -t' ' -k2 -r

@zndtoshi if you’re on linux, use it with “watch” for the live experience watch -t bitcoin-cli -netinfo 4 and for more info, run bitcoin-cli -netinfo help

# aggragate mempool fees bitcoin-cli getrawmempool true | fx "Object.keys(this).map( (e,i,a)=>this[e].fee) .reduce((a, v)=> a+v)"

@benthecarman @DoggeBTC list of all the config options ./src/bitcoind -help or ./src/bitcoind -? list of all the RPCs ./src/bitcoin-cli help detailed help for an RPC ./src/bitcoin-cli help (rpc call name) ./src/bitcoin-cli help getaddressinfo

Bashified the coarse difficulty adjustment estimation. I'm still not sure if this is a reasonable correct way of estimating an upcoming difficulty adjustment.

mutatrum @mutatrum

4 years ago

Bashified the coarse difficulty adjustment estimation. I'm still not sure if this is a reasonable correct way of estimating an upcoming difficulty adjustment. https://t.co/x2HuBNxmnf

0 1 0 0 0

Download Image

# % sync'd prog() { local w=80 p=$1; shift printf -v dots "%*s" "$(( $p*$w/100 ))" ""; dots=${dots// /.} printf "\r\e[K|%-*s| %3d %% %s" "$w" "$dots" "$p" "$*" } while : ; do prog $(bitcoin-cli getblockchaininfo | jq '.verificationprogress * 100|floor') sleep 10 done ; echo

bitcoin-cli -netinfo 4 | grep -E "(bitnodes|nodes.multiven.io|https://t.co/0f4cfWkYZM|btc_node_scanner)" | awk '{ print $10 }' | awk -F: '{print $1}' | xargs -I {} sh -c 'echo "$(date) # banning {} ..."; bitcoin-cli setban "{}" "add" 999999999' on a cron

@murchandamus Oh, commands to get this data: $ ./bitcoin-cli getpeerinfo | grep subver | sort | uniq -c | sort -n $ tail -n5000000 ~/.bitcoin/debug.log | sed -n 's/.*receive version message: //p;' | sed 's/ version [0-9]*, blocks=.*//' | sort | uniq -c | sort -n (2nd requires -debug=net)

admin@mynode:~$ bitcoin-cli getnetworkinfo { "version": 210100, "subversion": "/Satoshi:0.21.1/" Upgrade your #bitcoin node Pass it on.

@JohnOnChain bitcoin-cli getpeerinfo | jq -r .[].subver | sort

d=1; for ((i=0; i < $(bitcoin-cli getblockchaininfo | jq .blocks); i += 2016)) do n=$(bitcoin-cli getblock $(bitcoin-cli getblockhash $i) | jq .difficulty); c=$(echo "($n/$d * 100) - 100" | bc -l); echo $i: $c; d=$n; done

keyboard_arrow_left Previous keyboard_arrow_right Next

echo $(bitcoin-cli decoderawtransaction $(bitcoin-cli getrawtransaction $(bitcoin-cli getblock $(bitcoin-cli getblockhash 681629) | jq -r '.tx[0]')) | jq -r '.vin[0].coinbase' | xxd -r -p)

$ bitcoin-cli getblockchaininfo | jq .softforks.taproot.bip9.statistics.count 69 Nice.