00:20 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-29#1077198 << w/ current-day gpu, asciilifeform suspects wouldn't take even coupla days per |
00:20 |
dulapbot |
Logged on 2022-01-29 16:06:04 whaack: asciilifeform: the genesis starts with a decently high difficulty, it would take a while to generate the synthetic blocks on a home computer |
| |
~ 2 hours 1 minutes ~ |
02:21 |
vex |
anyone got the ATC chain? |
02:28 |
vex |
wasn't that just a new genesis with v4ish? |
02:34 |
vex |
I forget, but I seriously doubt tat cooked it for a week |
02:39 |
vex |
possible readymade reorg initial testchain, replete with wayoff timestamps |
02:43 |
vex |
may not exist in any zoo |
02:47 |
* |
asciilifeform dun have it |
02:49 |
vex |
arguably a waste of kwhrs in anycase |
02:51 |
vex |
although, potential for previously unknown weird exists |
| |
~ 2 hours 28 minutes ~ |
05:19 |
asciilifeform |
billymg: eggog 500 on pestlogger www ? |
05:20 |
billymg |
just noticed, looking now |
05:21 |
billymg |
looks like postgres crashed. trying to start / restart / stop it gives: pg_ctl: PID file "/var/lib/postgresql/10/data/postmaster.pid" does not exist |
05:24 |
asciilifeform |
billymg: iirc that's the lockfile. start oughta work |
05:24 |
billymg |
start gives: * WARNING: postgresql-10 has already been started |
05:25 |
asciilifeform |
kill it manually (if alive), rm the lockfile, oughta start |
05:25 |
billymg |
but no postgres processes turn up |
05:25 |
billymg |
`ps aux | grep postgres` no results |
05:25 |
billymg |
do you know off hand where the lockfile is? |
05:25 |
asciilifeform |
dmesg dun show any disk eggogs, does it ? |
05:26 |
asciilifeform |
the pid thing ~is~ the lockfile iirc |
05:27 |
asciilifeform |
( check /var/run/postgresql/ also for pg liquishit ) |
05:27 |
* |
asciilifeform not witnessed this particular barf afaik |
05:29 |
billymg |
dmesg shows some out of memory errors actually |
05:29 |
billymg |
Out of memory: Kill process 16688 (postgres) score 186 or sacrifice child |
05:29 |
asciilifeform |
nuffin suggestive of ssd demise, neh ? |
05:30 |
billymg |
Killed process 16688 (postgres) total-vm:685136kB, anon-rss:1612kB, file-rss:367580kB |
05:31 |
* |
asciilifeform must, unfortunately, to bed |
05:31 |
billymg |
asciilifeform: can't say i'd know what to look for re: disk problems |
05:32 |
asciilifeform |
billymg: eggogs featuring /dev/sda, sdb |
05:32 |
billymg |
nah, none of those |
05:32 |
asciilifeform |
aite then soft barf |
05:33 |
* |
asciilifeform will bbl, will help investigate tomorrow if billymg not finds pill earlier |
05:39 |
billymg |
gonna restart the box |
05:43 |
billymg |
well, restart didn't appear to help |
05:44 |
billymg |
ah, wait, now it's back |
05:53 |
billymg |
so looking at the postgres logs it looked like it indeed kept getting kill-9'd by the os |
05:55 |
billymg |
prior to that it was getting some bogus queries through the crawler www, e.g. lookup info where host=drupal.php |
| |
↖ |
05:56 |
billymg |
so possibly the site got it by a bot that was trying to sql inject |
05:57 |
billymg |
none of the queries had any bad effect, other than wasting pg resources (my fault for not having sanitization in place at the app level) |
| |
↖ |
06:09 |
billymg |
i backfilled the lines in #a from asciilifeform's logger. only one line was dropped in pest (which i pasted in the channel). i've added 8gb of swap to the rk for now but will have to plug the unsanitized client input hole tomorrow |
| |
~ 4 hours 55 minutes ~ |
11:04 |
cgra |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-29#1077198 << note that, peculiarly, the genesis hash was nominally ~2600x harder to mine than the genesis difficulty required! for easy check, see next block hash: ~1300x larger integer than the genesis hash. |
| |
↖ |
11:04 |
dulapbot |
Logged on 2022-01-29 16:06:04 whaack: asciilifeform: the genesis starts with a decently high difficulty, it would take a while to generate the synthetic blocks on a home computer |
11:05 |
cgra |
sometime earlier, i made two experiments to verify some upper limits of blocks. at the time they weren't valid blocks, but i rectified that in the mean time: it took perhaps <1 hour per block to mine, with an 8-core CPU, and a python(!) miner |
11:05 |
dulapbot |
(therealbitcoin) 2020-10-03 cgra: asciilifeform: re your ada piece, i hand-crafted two versions of #1 block (although with invalid hash and merkle tree, had to temporarily disable those specific checks to experiment). |
11:05 |
cgra |
asciilifeform: btw, did you ever comment on this one? valid block species now here and here (obv the eating node must've chain height below the builtin checkpoints) |
11:05 |
dulapbot |
(therealbitcoin) 2020-10-03 cgra: one of them had ~1MB output script, the other had ~112k outputs, and they both got accepted by trb (fresh install, 0% synced). i saw much tighter limits set in your code |
| |
~ 5 hours 7 minutes ~ |
16:13 |
asciilifeform |
cgra: oh hm, must've missed somehow? |
16:13 |
asciilifeform |
cgra: how the hell does one stuff ~112k outputs in <= 1e6 bytes tho |
16:15 |
* |
asciilifeform rereads nqb structs, can nao see how |
16:15 |
* |
asciilifeform when gets a chance to pick ^ up again, will have to properly calculate the maxima... |
16:16 |
asciilifeform |
err, correct link |
16:16 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-30#1077242 << this kinda thing used to happen w/ early phuctor regularly |
16:16 |
dulapbot |
Logged on 2022-01-30 00:57:59 billymg: none of the queries had any bad effect, other than wasting pg resources (my fault for not having sanitization in place at the app level) |
| |
~ 1 hours 43 minutes ~ |
18:00 |
cgra |
whaack: i'm possibly not aware of all implications, but i keep contemplating a 'pesttronic block explorer' accepting read-only sql queries from wot |
| |
↖ ↖ ↖ |
18:04 |
cgra |
for example, the last dig i did was "what's the last block mined with the hard-coded, minimum difficulty the genesis block started off with?" |
| |
~ 21 minutes ~ |
18:25 |
signpost |
cgra: yep, imho this can be generalized to perhaps an async RPC mechanism. |
18:26 |
signpost |
would be quite marvelous to interact with "bots" in this manner, where you pass them a structured request, and receive a structured response back via pest. |
18:26 |
signpost |
the IRC request -> paste response mechanism is a rough approximation that can be much improved. |
| |
↖ |
18:31 |
signpost |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-17#1073543 << what I meant here by UCI miners was boxen being paid to run jobs distributed over wot. |
| |
↖ |
18:31 |
dulapbot |
Logged on 2022-01-17 12:33:59 signpost: (and worthwhile to consider how to allow folks to turn arbitrary boxes into "UCI miners" as easily as possible, i.e. "run this here proggy, contains a whole linux within") |
18:38 |
signpost |
old thread on subj for those not familiar with the UCI macro http://logs.nosuchlabs.com/log/trilema/2017-07-20#1687384 |
18:38 |
dulapbot |
(trilema) 2017-07-20 asciilifeform: i want a nonstar topology. |
18:39 |
thimbronion |
speaking of old threads - bitcoin-assets appears to be gone. |
18:39 |
asciilifeform |
thimbronion: gone from where ? |
18:40 |
signpost |
but upstack, the logical progression of IRC botworks is being able to (deedbot:deed "signed payload to be deeded") into pest, and receive back an ack that it was heard. |
| |
↖ |
18:41 |
signpost |
obviously s-exp is perhaps not the best encoding, just giving it as a placeholder. |
18:41 |
signpost |
asciilifeform: looks like the www, unless I forgot the url |
18:42 |
signpost |
http://logs.bitcoin-assets.com/ << irrc |
18:42 |
thimbronion |
asciilifeform: the domain http://log.bitcoin-assets.com/ is gone |
18:42 |
signpost |
*iirc |
18:42 |
asciilifeform |
signpost, thimbronion : http://logs.nosuchlabs.com/log/asciilifeform/2021-07-06#1043123 |
18:42 |
dulapbot |
Logged on 2021-07-06 15:46:47 kakobrekla: i took that shit down recently, i only kept it up so long cause alfie said im gonna fold before mp does or some shit like that |
18:42 |
thimbronion |
asciilifeform: ah - missed that |
18:42 |
asciilifeform |
gone for at least that long |
18:42 |
signpost |
kako was in the end a pretty small-ego'd guy, seems like. |
18:43 |
* |
signpost does not have much use for people whose principles flow only from what pays them. |
18:48 |
* |
thimbronion occasionally checked to see what they were currently making sarcastic remarks about |
18:49 |
signpost |
sad when folks make their only basis of relationship bawing about old wounds. |
18:50 |
* |
signpost is here because the decentralization tech tree still grows. |
18:50 |
signpost |
back in a bit. |
| |
~ 31 minutes ~ |
19:21 |
asciilifeform |
thimbronion: iirc by the time kako unplugged that thing, no one had said ~anyffin in yr+ |
19:21 |
asciilifeform |
signpost: wasn't clear to asciilifeform that kako ever had anyffin in the way of principles |
19:23 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-30#1077257 << imho the correct place for a block exploder is ultimately a pseudoserver within trb noad per se, locally |
| |
↖ ↖ |
19:23 |
dulapbot |
Logged on 2022-01-30 13:00:46 cgra: whaack: i'm possibly not aware of all implications, but i keep contemplating a 'pesttronic block explorer' accepting read-only sql queries from wot |
19:23 |
asciilifeform |
(can expose the port to net at large, if operator wants, naturally) |
| |
~ 46 minutes ~ |
20:10 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-30#1077244 << only 256x, neh |
20:10 |
dulapbot |
Logged on 2022-01-30 06:05:04 cgra: http://logs.nosuchlabs.com/log/asciilifeform/2022-01-29#1077198 << note that, peculiarly, the genesis hash was nominally ~2600x harder to mine than the genesis difficulty required! for easy check, see next block hash: ~1300x larger integer than the genesis hash. |
20:11 |
asciilifeform |
hash of gen block was 000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f; at diff==1, needed 2 fewer leading 0's than he had |
20:18 |
asciilifeform |
or hm, iirc needed 32 leading 0 bits at diff1. which'd make the genesis, with 43 leading 0's, 2^11 i.e. '2048x harder than had to' |
| |
↖ |
20:19 |
* |
asciilifeform if slipped sumwhere, invites folx to correct. |
20:19 |
asciilifeform |
( 0 ~bits~ that is ) |
| |
~ 2 hours 30 minutes ~ |
22:50 |
asciilifeform |
http://logs.nosuchlabs.com/log/asciilifeform/2022-01-30#1077262 << fwiw asciilifeform still waiting for sumbody to invent cpu work that's actually worth the overhead (and snoop risk) of farming out to fleets of boxen |
22:50 |
dulapbot |
Logged on 2022-01-30 13:31:39 signpost: http://logs.nosuchlabs.com/log/asciilifeform/2022-01-17#1073543 << what I meant here by UCI miners was boxen being paid to run jobs distributed over wot. |
22:51 |
asciilifeform |
( mining per se was ~briefly~ it, gpu/asicism quickly made such schemes -ev tho, in '13-14 already faded to ~nuffin (supposing was ~ever~ +ev at all) |
22:51 |
dulapbot |
Logged on 2020-05-15 21:00:56 asciilifeform: lru: w/ bitcoin proper, as late as 2013 there were trojan payloads that (with variable success -- variations in iron/drivers made this nontrivial) gpu mined. |
22:52 |
asciilifeform |
) |
22:53 |
asciilifeform |
trb noad operation was sometimes quite erroneously given as example of 'useful' payload for hypothetical bots; but if you think about it, it takes considerable sweat even for ~willing~ operator to maintain a noad worth connecting to |
22:54 |
asciilifeform |
( see also. ) |
22:54 |
dulapbot |
Logged on 2022-01-17 13:12:59 asciilifeform: archaetypical 'botnet' aint actually as useful as folx naively think. |
22:54 |
asciilifeform |
there'sa reason wai most botnets historically used for brute ddos-for-hire. |
22:54 |
asciilifeform |
there simply aint much else anyone knows how to do with'em atm. |
23:01 |
asciilifeform |
( possibly still used for e.g. premining newly-perpetrated shitcoins? i.e. before the gpu/asic folx cotton on. nfi. ) |
23:02 |
asciilifeform |
ftr on a typical bot box you dun have the cpu all to yerself, either -- often enuff will share it w/ over9000 similar shits |
23:03 |
asciilifeform |
( + the luser himself running a 40GB msoffice etc lulz ) |
23:04 |
asciilifeform |
1 hypothetically interesting application may be 'mining' the mswin rng in conjunction w/ prb privkey gen. |
23:05 |
asciilifeform |
(would require storing the 'utxo set' tho) |
23:06 |
asciilifeform |
storing on ea. victim, that is. |
| |
~ 22 minutes ~ |
23:29 |
scoopbot |
New article on billymg: Building TRB on a 2022 Vintage Musl Gentoo |