--- Log opened Mon Feb 17 00:00:41 2020
00:09 -!- Kiminuo [~mix@141.98.103.124] has joined #rust-bitcoin
00:34 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
00:34 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
00:52 -!- wumpus2 is now known as wumpus
01:13 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
01:14 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
01:30 < willcl_ark> BlueMatt: is this error (from lightning-bitcoinrpc) ```#[error("OSX creatively eats your data, using Lightning on OSX is unsafe")]``` still correct/current advice? If so, do you forsee this changing anytime soon?
03:06 -!- Reed80Ernser [~Reed80Ern@ns334669.ip-5-196-64.eu] has joined #rust-bitcoin
05:47 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
05:54 -!- varioust [~varioust@cpe-108-167-11-88.neb.res.rr.com] has joined #rust-bitcoin
05:54 -!- varioust [~varioust@cpe-108-167-11-88.neb.res.rr.com] has quit [Remote host closed the connection]
05:54 -!- varioust [~varioust@cpe-108-167-11-88.neb.res.rr.com] has joined #rust-bitcoin
05:57 -!- varioust_ [~varioust@rrcs-76-79-17-10.west.biz.rr.com] has joined #rust-bitcoin
05:59 -!- varioust [~varioust@cpe-108-167-11-88.neb.res.rr.com] has quit [Ping timeout: 260 seconds]
05:59 -!- varioust_ is now known as varioust
06:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
07:37 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 260 seconds]
07:58 -!- varioust [~varioust@rrcs-76-79-17-10.west.biz.rr.com] has quit [Ping timeout: 272 seconds]
09:15 -!- Kiminuo [~mix@141.98.103.124] has joined #rust-bitcoin
10:02 -!- Kiminuo [~mix@141.98.103.124] has quit [Read error: Connection reset by peer]
10:03 -!- Kiminuo [~mix@141.98.103.124] has joined #rust-bitcoin
10:05 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qihsiglcjcbokopg] has quit [Ping timeout: 246 seconds]
10:06 < BlueMatt> willcl_ark: last I checked the rust libstd doesn't properly call fdatasync (cause OSX is dumb and decided that fsync should just be a noop)...
10:07 < BlueMatt> willcl_ark: i mean if your machine doesnt crash, its fine, but dont expect data consistency across hard reboots
10:07 -!- dpc [dpcmatrixo@gateway/shell/matrix.org/x-slfxgckmzxfvwhyp] has quit [Ping timeout: 240 seconds]
10:24 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qdaiuvjbvcvohzfc] has joined #rust-bitcoin
10:34 -!- dpc [dpcmatrixo@gateway/shell/matrix.org/x-irdpcatzcwargpvr] has joined #rust-bitcoin
11:13 < ariard_> BlueMatt: what's about #462? just to know if it's good enough to start building on top of it
11:13 < ariard_> will review #494 soon
11:13 < BlueMatt> ariard_: yea, sorry, I'm happy with the direction.
11:14 < BlueMatt> will take another look later today, spent this weekend getting rust-lightning-bitcoinrpc running with rescan (which works now, but led to several bugs that I need to open PRs for)
11:15 -!- Reed80Ernser [~Reed80Ern@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds]
11:16 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
11:18 < ariard_> ah great!, spent mine on refactoring core rescan
11:18 < ariard_> well still on it
11:25 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
11:27 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
11:37 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
11:46 -!- dpc [dpcmatrixo@gateway/shell/matrix.org/x-irdpcatzcwargpvr] has quit [Quit: killed]
11:47 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qdaiuvjbvcvohzfc] has quit [Quit: killed]
11:47 < BlueMatt> ariard_: can you review/ack https://github.com/rust-bitcoin/rust-lightning/pull/455 ?
11:47 < BlueMatt> it'd be nice to remove one conflicting pr from the stack
11:49 -!- sanket1729 [~sanket172@72.36.89.11] has quit [Ping timeout: 250 seconds]
11:50 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 268 seconds]
11:51 -!- sanket1729 [~sanket172@72.36.89.11] has joined #rust-bitcoin
11:59 < BlueMatt> also because I want to land 503 and its based on 455
12:14 -!- Kiminuo [~mix@141.98.103.124] has joined #rust-bitcoin
12:19 -!- dpc [dpcmatrixo@gateway/shell/matrix.org/x-rhfcmlyswdjtlfdl] has joined #rust-bitcoin
12:29 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 268 seconds]
12:30 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
12:32 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
12:35 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
12:47 -!- icota[m] [icotamatri@gateway/shell/matrix.org/x-qgdvtvrbxrlnzoxg] has joined #rust-bitcoin
13:07 -!- Kiminuo [~mix@141.98.103.124] has quit [Ping timeout: 260 seconds]
14:05 < stevenro-> andytoshi: I'd like to have a function on hal where `hal psbt sign --privkey <private-key> <raw-psbt>` where you just add a signature to the psbt input. Should that be possible with miniscript's satisfiers?
14:20 < willcl_ark> @BlueMatt: thanks for the info. Not 100% sure how to test exactly, but it looks like https://github.com/rust-lang/rust/commit/d602a6b942e32f4f9a36b6c44471cfcd80a81bb6 might fix the sync issue on OS X :S
14:23 < BlueMatt> likely indeed
14:25 < willcl_ark> ^^
14:25 < BlueMatt> I mean the other solution is to never have a machine crash and use testnet so you dont care :p
14:26 < willcl_ark> Thats.... what I'm doing!
14:27 < willcl_ark> Still nice to dot the i's and cross the T's if possible
14:27 < BlueMatt> right.
14:33 < willcl_ark> yep, seems to run ""fine"" on OSX (for testing)
14:44 <@andytoshi> stevenro-: if you're adding a signature to the psbt that has nothing to do with miniscript at all
14:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
14:51 < stevenro-> I thought miniscript had some code to figure out sighashes.
15:15 <@andytoshi> no, that's rust-bitcoin
15:16 <@andytoshi> sighashes are independent of script (well, independent of miniscript)
15:16 <@andytoshi> elichai2: when i try to build rust-secp with wasm-bindgen i'm getting a weird failure
15:16 <@andytoshi> cargo:warning=depend/secp256k1/contrib/lax_der_parsing.c:7:10: fatal error: 'string.h' file not found
15:18 <@andytoshi> this is different from the "linking with emcc" bug that we have in travis rn
15:18 < elichai2> Hmm sounds like it doesn't include libstd(C) library correctly
15:19 < elichai2> What exactly are you doing? Do you have a binary that includes rust-secp and is compiled to wasm? With what command?
15:20 <@andytoshi> i'm using wasm bindgen
15:20 <@andytoshi> the command is `wasm-pack build`
15:21 <@andytoshi> i'm basically doing this https://rustwasm.github.io/book/game-of-life/hello-world.html but i added a secp dependency
15:21 <@andytoshi> this used to work
15:25 <@andytoshi> oh derp
15:25 <@andytoshi> we renamed the std target didn't we?
15:27 < elichai2> not sure that's it. wasm-pack should work with full std
15:27 <@andytoshi> should it?
15:27 <@andytoshi> like, does it use emscripten?
15:27 < elichai2> interesting. my old example also gives the same error: https://github.com/elichai/rust-lightning/blob/wasm/wasm-test
15:27 < elichai2> and that's 0.15
15:27 <@andytoshi> in any case it does seem like my old code had no no_std stuff in it..
15:28 <@andytoshi> right, mine was using 0.13, same story
15:28 <@andytoshi> but i couldn't remember what changes we'd done when
15:29 <@andytoshi> hmmm. so this is really irritating
15:29 < BlueMatt> ariard_: lmk when you respond to the comments/rebase 462 and I'll take another look. I dunno that we should delay it too long, its generally pretty good and fixes current bugs on master.
15:30 < BlueMatt> also would love to merge 440, if you get a chance :)
15:30 < BlueMatt> I think you just need to glance at the changes i made against your review, you were already happy with it
15:31 < elichai2> andytoshi: even just `cargo build --target=wasm32-unknown-unknown` fails
15:32 <@andytoshi> elichai2: good find. i guess now we can step through different toolchain versions and see where the breakage started ..
15:33 <@andytoshi> okaay, it seems to happen even with 1.30.0, which i know didn't used to be the case
15:33 < elichai2> FWIW just tried 1.37.0 and it's still broken ther
15:33 < elichai2> I'm 100% sure it worked to me here as is  https://github.com/elichai/rust-lightning/blob/wasm/wasm-test
15:34 <@andytoshi> 1.26 is broken too
15:34 <@andytoshi> yeah i'm 100% sure this used to work, too ... i have a similar test repo
15:35 < elichai2> andytoshi: hmmm https://github.com/alexcrichton/cc-rs/issues/446
15:36 < elichai2> it might be our systems
15:37 < elichai2> maybe my llvm implementation doesn't contain the libstd headers for wasm32?
15:37 <@andytoshi> could be
15:37 <@andytoshi> what distro are you using
15:38 < elichai2> arch, with self compiled llvm :D
15:38 <@andytoshi> lol
15:38 <@andytoshi> ok, i'm also using arch
15:38 < elichai2> maybe it's a clang-9 problem?
15:38 < elichai2> i wonder if we can make it use gcc
15:39 < elichai2> works :)
15:39 < elichai2> fatal error: 'string.h' file not found
15:39 < elichai2> ops
15:39 < elichai2> CC=gcc cargo build --target=wasm32-unknown-unknown
15:40 <@andytoshi> nicee
15:40 <@andytoshi> also works with wasm-pack
15:43 < elichai2> it seems like we can take it down to `clang --target=wasm32-unknown-unknown -I../secp256k1 -I../include -I../src -I. lax_der_parsing.c`
15:44 <@andytoshi> now i'm getting this error "allocators must be statics" when i try to build my test projcet with `CC=gcc wasm-pack build`
15:44 < elichai2> or basically `clang --target=wasm32-unknown-unknown  something.c` where `something.c` includes string.h
15:44 <@andytoshi> ok, cool
15:44 <@andytoshi> google suggests i need to build my own llvm :(
15:44 < elichai2> what flags are needed to get the wasm libs? and why is this excluded?
15:45 <@andytoshi> idk, and apparently it's just a default
15:45 <@andytoshi> to save space/build time i guess
15:46 < ariard_> BlueMatt: yes #440 is rtm
15:46 < ariard_> okay will address your comment and arik's one on #462 soon, agree to not delay it too long
15:47 < BlueMatt> cool, thanks. trying to ride folks for review since I want to get the long pile of shit merged and cut a release in not-too-long :)
15:47 < elichai2> andytoshi: that's some weird error
15:47 < elichai2> only results are from the code
15:48 <@andytoshi> elichai2: lol right
15:48 < BlueMatt> especially since rust-lightning-bitcoinrpc now depends on a branch with a bunch of random unmerged crap lol
15:49 <@andytoshi> if i change to return a `&'static str` instead of a String, i get
15:49 <@andytoshi> error: it is currently not sound to use lifetimes in function signatures
15:49 <@andytoshi> which is also insane and i've never seen it before
15:50 < elichai2> any chance your wasm-bindgen isn't up-to-date? https://github.com/rustwasm/wasm-bindgen/issues/1187
15:50 < elichai2> *wasm-pack and wasm-bindgen lib? ?
15:50 <@andytoshi> oh yeah
15:50 <@andytoshi> i'm at 1.39
15:51 <@andytoshi> lol updated to 1.41
15:51 < ariard_> BlueMatt: what do you want in MPP, modular hanshake, OnchainTxHandler, ...?
15:51 <@andytoshi> now i get *both* the "allocators must be statics" error and the error about lifetimes
15:51 <@andytoshi> but there aren't any allocations anymore
15:51 <@andytoshi> and wtf is a static
15:51 <@andytoshi> and wtf is an allocator
15:52 < elichai2> I'm getting `note: rust-lld: error: unknown file type: lax_der_parsing.o`
15:52 < BlueMatt> ariard_: less concerned with MPP and more concerned with just making sure all the known bugs are fixed
15:53 < BlueMatt> ariard_: which I think requires OnchainTxHandler, but not MPP or modular handshake
15:53 < elichai2> yeah lately i've had a bunch of issues where ld didn't like what clang outputs and lld doesnt like what gcc outputs
15:53 <@andytoshi> sigh
15:53 < elichai2> it's so bad I replaced all my `/usr/bin/*` with their llvm replacements
15:53  * elichai2 facepalm
15:53 <@andytoshi> hahah
15:54 <@andytoshi> so, i'm trying not to be insane here ... i just want to write some miniscript library functions for use in esplora
15:54 < elichai2> things I never knew llvm did! they have their own `ar` a freaking archiver
15:54 <@andytoshi> and i shouldn't have to custom-compile my entire toolchain and symlink random binaries to get a test working
15:54 <@andytoshi> lol!!
15:55 < elichai2> what about wasi?
15:55 < BlueMatt> ariard_: I tagged a bunch of crap 0.0.10, so, at least that, but maybe also 489, depends on when I finish rewriting the fuzzer for it, and also 472 only if tokio does another release first.
15:55 < elichai2> never tried it. but theoretically they're saying it can make things better
15:55 < ariard_> BlueMatt: I need to fix a watch output miss in check_spend_remote_htlc and a spendable output somewhwre
15:55 <@andytoshi> elichai2: how do i use wasi?
15:55 < BlueMatt> ariard_: though there's still shit I haven't pr'd, and probably wont until some other stuff gets merged.
15:55 < ariard_> that the bugs I have in mind
15:56 <@andytoshi> elichai2: i really don't understand what any of these things are or how they fit together
15:56 <@andytoshi> wasm, wasm-pack, wasi, cargo web
15:56 < BlueMatt> ariard_: cool, thanks
15:56 <@andytoshi> emcc
15:56 < elichai2> basically, there's the wasm ASM. but then there's different executers each providing a different set of syscalls
15:56 < elichai2> emcc is basically made to plug directly into nodejs/javascript
15:57 < elichai2> as far as i understand
15:57 < BlueMatt> elichai2: what all do you need if you *only* want malloc
15:57 < BlueMatt> ie only use core not std
15:57 < ariard_> BlueMatt: okay see 0.0.10 you should add #411 and #338
15:58 < elichai2> BlueMatt: good question. probably use wasm32-unknown-unknown and link in malloc
15:58 < BlueMatt> ariard_: I think you can do it? but will do
15:58 < elichai2> wasm32-unknown-unknown is "pure" wasm, so you need to link in your own malloc and some C functions
15:58 < ariard_> BlueMatt: oh yes it works I can
15:58 < elichai2> wasm-pack is a wrapper that lets you link into a web and execute the wasm easily
15:58 < elichai2> wasi, is a standard for wasm outside the web
15:59 < BlueMatt> dear god thats confusing...even for the most basic case
16:00 < elichai2> oh wait! wasm-bindgen is the actual syscall linking wrapper and there's competition at their end, called `stdweb`
16:00 < BlueMatt> what does all this mean? I dont speak javascript
16:00 < elichai2> shit. that's what it means lol
16:00 < BlueMatt> damn it
16:00 < elichai2> it's mostly around linking the functions and helping you export/import symbols from javascript to wasm
16:01 < BlueMatt> right.
16:02 <@andytoshi> i imagine things would be less confusing if we could get anything to work
16:02 < elichai2> they were less confusing in the past :/
16:03 <@andytoshi> yeah
16:03 <@andytoshi> seriously wtf at stdweb appearing as a competitor to wasm-bindgen
16:03 < BlueMatt> I dunno I just presume arik will fiure most of the shit out for rust-lightning
16:03 <@andytoshi> why can't javascript developers get anything working before they feel a need to fragment everything and redo stuff
16:04 < BlueMatt> because you're gonna end up depending on both of them in your dep tree anyway, this way they all get to be security holes for each other :p
16:04 < elichai2> yeah stdweb is completely wtf.
16:04 <@andytoshi> BlueMatt: lol
16:04 < elichai2> oh there's a new problem in town. a lot of wasm executers just skip linking and provide the symbols at run time. and apparently this violates the C++ standard :)
16:05 < BlueMatt> lolololololol
16:05 < BlueMatt> standards?! psh you didnt need that
16:06 <@andytoshi> i had to get my glasses fixed today. i visited a strange man in austin who had a little shop full of glasses parts, and he showed me the 10 or 15 things he does, and his price sheet ... i let him do his thing, then he was all proud of having rebuilt the flashings (i don't remember what these are) and how he'd painted the new arms to match the frames
16:06 <@andytoshi> i was kinda jealous of him
16:06 <@andytoshi> because my job is this :P
16:07 <@andytoshi> elichai2: are you able to produce the "allocators must be statics" error?
16:07 < BlueMatt> stop playing with javascript. then your job will be much easier
16:07 < elichai2> andytoshi: looooooool
16:07 < harding> andytoshi: lol :-)
16:07 < elichai2> andytoshi: nope. if you want quick and dirty maybe give emscripten a try :/
16:07 <@andytoshi> BlueMatt: i know, i know ... i wasn't for so long, but then on friday lawrence told me "just write some functions with wasm bindings, i'll do all the rest" and it sounded like maybe i could do this without having to deal with the painful parts
16:07 < elichai2> i'm getting the linker problem
16:08 < BlueMatt> andytoshi: doesn't lawrence have a whole bindings system for his shit? make him do it? or at least whoever maintains green bindings for libwally
16:08 <@andytoshi> BlueMatt: yes
16:08 <@andytoshi> all i'm trying to do is write a simple test site
16:08 <@andytoshi> so i can test my stuff
16:09 <@andytoshi> otherwise i'm writing code completely blindly
16:09 < BlueMatt> my previous approach is to get elichai2 to do my work for me. also seemed to be effective :)
16:09 < elichai2> whatever this is is weird. https://rust.cc/article?id=d432acfb-0c5f-4184-a525-715ccdc86cb2
16:09 <@andytoshi> how do i pass data from rust to javascript? who knows. when i try i get mysterious compiler errors that literally nobody else has ever gotten
16:09 <@andytoshi> BlueMatt: lol :)
16:10 < elichai2> lol :D
16:10 < elichai2> I wonder if it'll work in an ubuntu vm with clang
16:11 <@andytoshi> oh, i've got a computer with clang 8 actually
16:11 < BlueMatt> it'll probably work on a mac, given thats what all the javascripters tend to use :p
16:13 < elichai2> lol
16:13 < elichai2> ok as much as I enjoy this it's 2+AM here so I guess i'll leave you to it, tell me if you made it work in ~9 hours :) andytoshi
16:14 <@andytoshi> lol ok
16:14 <@andytoshi> get some sleep! night
16:15 < elichai2> andytoshi: look what I saw: https://github.com/elichai/rust-lightning/blob/wasm/wasm-test/src/lib.rs#L732
16:15 < elichai2> I used a custom allocator
16:15 < elichai2> idk why. but maybe there was a reason?
16:15 <@andytoshi> that's just part of the tutorial ... they say this allocator is smaller but slower
16:15 <@andytoshi> and it's turned off by default
16:15 < elichai2> oh
16:15 <@andytoshi> i guess i could try using it, but i don't think compilation gets far enough for this to matter
16:17 < elichai2> well this allocator is static :P
16:17 <@andytoshi> haha
16:24 < elichai2> andytoshi: CC='clang -isystem /usr/local/include -isystem /usr/include' wasm-pack build works for me
16:28 < elichai2> I'm just bad at going to sleep lol. I'm writing an email to the llvm mailing list now
16:29 <@andytoshi> haha
16:29 <@andytoshi> for the last 15 minutes i have been scp'ing my entire test program to my clang8 machine
16:29 <@andytoshi> there are waaay more files than i expected
16:29 < elichai2> rm -rf target/
16:30 <@andytoshi> i'm scared to do that because there's working javascript files in there
16:48 <@andytoshi> sigh
16:48 <@andytoshi> on my clang8 system i don't have C issues anymore, but i still get "allocators must be statics"
16:52 <@andytoshi> the code doesn't compile on 1.31 because of the usual "rust developers using bleeding edge features" bulshipt
16:53 <@andytoshi> 1.33 givse the same error
16:53 <@andytoshi> err, the "allocators must be statics" error
16:53 <@andytoshi> so does 1.32
16:54 <@andytoshi> wtf. this makes no sense. i even got rid of the &'static stuff. so i'm basically using the code from the website, with an old clang and an old rustc
16:54 <@andytoshi> and i know this worked a month ago
16:54 <@andytoshi> fuck me
16:54 < elichai2> Can you do "clang-8 - -target=wasm32-unknown-unknown - v test.c"?
16:54 <@andytoshi> i'm signing off for the evening
16:54 <@andytoshi> lol
16:54 <@andytoshi> yep one sec
16:54 <@andytoshi> what should test.c have in it? an include?
16:54 < elichai2> Try deleting the target dir? Maybe it's using old objects
16:54 < elichai2> Yeah do touch test.c
16:54 < elichai2> That should be enough
16:55 <@andytoshi> clang-8: error: unable to execute command: Executable "wasm-ld" doesn't exist!
16:55 < elichai2> Ha lol wtf
16:55 <@andytoshi> lol indeed
16:55 <@andytoshi> deleted target dir..
16:55 <@andytoshi> ...same error "allocators must be statics"
16:55 < elichai2> Weird. Everything is fucking weird lately
16:55 <@andytoshi> yeah. this is really mysterious
16:56 <@andytoshi> but i really am gonna sign off .. i am meeting a friend soon
16:56 <@andytoshi> and you should get some rest!
16:56 < elichai2> Enjoy :) and yeah you're probably right hebe
16:57 <@andytoshi> night :)
18:02 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
18:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
19:42 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
22:11 -!- mryandao_ [~mryandao@gateway/tor-sasl/mryandao] has joined #rust-bitcoin
22:11 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
22:20 -!- mryandao_ is now known as mryandao
22:58 -!- Kiminuo [~mix@141.98.103.124] has joined #rust-bitcoin
--- Log closed Tue Feb 18 00:00:44 2020