12:51 |
shinohai |
$vwap |
12:51 |
busybot |
The 24-Hour VWAP for BTC is $ 31677.14 USD |
| |
~ 3 hours 5 minutes ~ |
15:57 |
asciilifeform |
!w poll |
15:57 |
watchglass |
Polling 17 nodes... |
15:57 |
watchglass |
185.85.38.54:8333 : Could not connect! |
15:57 |
watchglass |
84.16.46.130:8333 : Could not connect! |
15:57 |
watchglass |
185.163.46.29:8333 : Could not connect! |
15:57 |
watchglass |
205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.083s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.091s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
205.134.172.27:8333 : Alive: (0.084s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 (Operator: asciilifeform) |
15:57 |
watchglass |
205.134.172.26:8333 : Alive: (0.091s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
205.134.172.28:8333 : Alive: (0.022s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=691447 (Operator: whaack) |
15:57 |
watchglass |
192.151.158.26:8333 : Alive: (0.204s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
143.202.160.10:8333 : Alive: (0.234s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
208.94.240.42:8333 : Alive: (0.159s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
54.38.94.63:8333 : (ns3140226.ip-54-38-94.eu) Alive: (0.331s) V=88888 (/therealbitcoin.org:0.8.88.88/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
176.9.59.199:8333 : (static.199.59.9.176.clients.your-server.de) Alive: (0.342s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=412062 (Operator: jurov) |
15:57 |
watchglass |
213.109.238.156:8333 : Alive: (0.332s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.860s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 |
15:57 |
watchglass |
71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.196s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=691447 (Operator: asciilifeform) |
15:58 |
watchglass |
54.39.156.171:8333 : Violated BTC Protocol: Bad header length! |
| |
~ 5 hours 7 minutes ~ |
21:05 |
billymg |
the crawler www is now browsable |
| |
↖ |
21:07 |
whaack |
!e uptime |
21:07 |
trbexplorer |
whaack: time since my last reconnect : 6d 1h 39m |
21:07 |
whaack |
!e height |
21:07 |
trbexplorer |
690611 |
21:09 |
whaack |
billymg: nice and mega congrats. Now we must do the lords work and get cracking on populating that list with trb cients |
21:12 |
billymg |
whaack: thanks, and yes, now there's a scoreboard |
21:14 |
whaack |
I have a grim feeling about the health of the network, given the alleged widespread use of segwit |
21:15 |
whaack |
the day of reckoning can come when miners stop enforcing the segwit rule and loads of "bitcoin" users have their coins wiped out from under their feet |
| |
↖ |
21:15 |
billymg |
whaack: have you totaled up the balance sitting in all segwit addresses yet? |
21:16 |
signpost |
pretty damned cool billymg |
21:16 |
whaack |
billymg: That's not possible afaik, because segwit addresses are hidden behind a script and only at the time of spending can you retroactively discover that it was a segwit address |
21:17 |
whaack |
However I can try to figure out how many coins are in pay-to-script-hash addresses |
21:18 |
whaack |
or similarly how many coins are in proper addresses, which from my understanding are (1) pay-to-public-key (found in the first couple of hundred blocks) and (2) pay-to-public-key-hash addresses |
| |
↖ |
21:19 |
billymg |
signpost: thanks! hopefully it ends up being useful, lemme know if you find bugs / have suggestions for it |
21:19 |
whaack |
i also have the thought that my trbexplorer should have the ability to respond to arbitrary sql "read" statements |
21:20 |
whaack |
This way the logs can be filled with a question like billymg's above, and the repsonse can be a query to trbexplorer |
21:21 |
billymg |
whaack: i'm trying to find asciilifeform's log line now where he suggests posting a realtime updated "bounty" somewhere to miners who are willing to defect, but that would be my end goal with this information |
21:22 |
signpost |
"The results indicate that only 55 of the 7998 nodes active in the last 48hrs are actually participating on the Bitcoin network in true p2p fashion." |
21:22 |
signpost |
woof. |
21:22 |
billymg |
http://logs.nosuchlabs.com/log/asciilifeform/2021-07-17#1046284 << this seems like not a bad approach |
21:22 |
dulapbot |
Logged on 2021-07-17 17:18:44 whaack: or similarly how many coins are in proper addresses, which from my understanding are (1) pay-to-public-key (found in the first couple of hundred blocks) and (2) pay-to-public-key-hash addresses |
21:22 |
billymg |
signpost: yeah, that's what i was hoping would be the "smoking gun" to wake up the prb users |
21:24 |
whaack |
What is "bloom"? Is this some new prb shenanagins having to do with bloom filters? |
21:24 |
billymg |
signpost: i was also going to create a "TRB dominance" metric, that only counts from those (currently) 55 real nodes -- showing that TRB is already like a third of the real network |
21:24 |
billymg |
whaack: i believe short for bloom filters? i forget what prb feature it is |
21:25 |
signpost |
my suspicion is that getaddr doesn't send the whole list, so this may not be a complete picture. |
21:28 |
billymg |
signpost: that's definitely possible too, or that there is some other unknown secret handshake for prb that we haven't figured out yet |
21:29 |
signpost |
evidence for drift between trb and prb in either ccase |
21:29 |
signpost |
*case. |
21:30 |
mats |
https://txstats.com/dashboard/db/segwit-usage?orgId=1 |
21:30 |
mats |
https://txstats.com/dashboard/db/p2sh-statistics?orgId=1 |
21:30 |
mats |
https://txstats.com/dashboard/db/bech32-statistics?orgId=1 |
21:33 |
mats |
in a future where miners have been exiled from .cn, its harder to imagine some of these balances getting looted |
21:33 |
signpost |
https://github.com/bitcoin/bitcoin/blob/d8f1e1327f9c2f9fcc804468f6a981580acdf30a/src/addrman.h#L589 << still wading through the soup, but yeah, this suggests you don't get them all |
21:34 |
signpost |
in some case(s) |
21:37 |
billymg |
signpost: interesting, the crawler results do seem to show that it's capped somewhere at about 2000 (i've never seen higher than 2001) |
21:37 |
signpost |
https://github.com/bitcoin/bitcoin/blob/ddc6979b8baab048bbf0c5c2dd23345a8eb5c60e/src/net_processing.cpp#L155 |
21:38 |
signpost |
looks like those are relevant magic numbers |
21:38 |
billymg |
signpost: aha |
21:40 |
signpost |
https://github.com/bitcoin/bitcoin/blob/ddc6979b8baab048bbf0c5c2dd23345a8eb5c60e/src/net_processing.cpp#L3657 << >> https://github.com/bitcoin/bitcoin/blob/d8f1e1327f9c2f9fcc804468f6a981580acdf30a/src/addrman.cpp#L543 |
21:41 |
signpost |
seems like if you're getting 1 address for many peers, *their* peer count is indeed low, but probably not 1 |
21:44 |
whaack |
mats: nice link. |
21:44 |
billymg |
ah, i see. i wonder if bumping up the 'peershots' value in watchglass would net more peers (currently i have it set to 3) |
21:50 |
billymg |
just restarted the crawler with peershots=5, it finishes scanning all nodes in the network in about 20 minutes |
21:51 |
billymg |
looks like in fact it did do something, 106 of the 8001 nodes now |
21:52 |
billymg |
163 now |
21:52 |
billymg |
ty signpost |
21:53 |
billymg |
and a new record for peers returned, 2504 |
| |
↖ |
21:54 |
signpost |
cool, yw |
21:54 |
* |
signpost will have to read the watchglass sauce and see what peershots is |
22:01 |
billymg |
signpost: in asciilifeform's original it was used to retry the getaddr N times in case of failure (and break out when it succeeds). i modified it to just retry again regardless of success/failure because i noticed i was getting more peers that way (probably due to the magic numbers you pointed out above) |
22:02 |
billymg |
looking at it closer i may see pretty careless mistake on my part though, i'm not de-duping this peers list as i build it |
22:03 |
billymg |
see a* |
| |
~ 1 hours 1 minutes ~ |
23:04 |
billymg |
ok, well fixed that little bug, my version of that piece of watchglass now looks like this: http://paste.deedbot.org/?id=q9KZ |
23:05 |
billymg |
err, hrm, i mean like this http://paste.deedbot.org/?id=khse (forgot the last line) |
23:09 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-07-17#1046271 << neato! |
23:09 |
dulapbot |
Logged on 2021-07-17 17:05:48 billymg: the crawler www is now browsable |
23:19 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2021-07-17#1046319 << the 'violated protocol!' thing is arguably a misfeature in asciilifeform's orig. proggy -- it simply means that the thing timed out and 'died with full pants' |
23:19 |
dulapbot |
Logged on 2021-07-17 17:53:53 billymg: and a new record for peers returned, 2504 |
23:20 |
asciilifeform |
(i.e. probably oughta read simply 'timed out') |
23:31 |
billymg |
asciilifeform: ok, will adjust |
23:32 |
billymg |
i was planning on coming up with some other mapping for those statuses anyway but for now i just output what watchglass returned |
23:35 |
billymg |
asciilifeform: adjusting the peershots knob from 3 to 5 seems to have helped for certain prb nodes: http://bitdash.io/nodes/5.103.137.146-9333 |
23:35 |
billymg |
notice all the previous probes returning only 1 peer |
23:36 |
* |
billymg had also planned to return to tuning the actual crawler/probe code after first getting the results visible on the www |