--- Log opened Tue Jun 22 00:00:45 2021
00:05 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
00:11 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
00:22 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
00:27 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
00:35 -!- belcher_ is now known as belcher
00:45 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
00:50 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 252 seconds]
01:02 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
01:07 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
01:16 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
05:06 -!- tibo__ [~tibo@2400:4050:2a83:7000:78db:f2c0:5f72:c1f] has quit [Remote host closed the connection]
05:07 -!- tibo_ [~tibo@2400:4050:2a83:7000:78db:f2c0:5f72:c1f] has joined #bitcoin-rust
05:12 -!- tibo_ [~tibo@2400:4050:2a83:7000:78db:f2c0:5f72:c1f] has quit [Ping timeout: 252 seconds]
05:57 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
06:01 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
06:21 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 268 seconds]
06:22 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
06:29 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
06:31 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
06:43 -!- gffgfrt [~gffgfrt@2a02:908:e853:ec80:7880:286a:b6c:4005] has joined #bitcoin-rust
06:44 < gffgfrt> Is there a library to iterate over all incoming and outgoing transaction from a specific address? I need this to visualize some data.
06:44 < gffgfrt> *transactions
06:46 < darosior> gffgfrt: you need an indexer for that, take a look at Blockstream's fork of electrs for Esplora
06:48 < gffgfrt> Ty, will look into It.
07:00 -!- gffgfrt [~gffgfrt@2a02:908:e853:ec80:7880:286a:b6c:4005] has quit [Quit: Client closed]
07:59 < BlueMatt> I think its time. time for no_std. https://github.com/rust-bitcoin/rust-bitcoin/pull/603
08:01 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 268 seconds]
08:02 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
08:03 < elichai2> BlueMatt: devrandom I haven't reviewed the no_std yet because I'm still worried about the `core2` crate, but if there's a consensus that we're fine with it i'll review #603 later this week
08:05 < BlueMatt> elichai2: worried in what way?
08:08 < elichai2> BlueMatt: It's an alpha version, only 3 reverse dependencies (including bitcoin_hashes), 33 stars on github, I don't know the author. and as far as I know none of us actually really reviewed the code in that crate
08:08 < BlueMatt> elichai2: should we copy it and host it ourselves?
08:10 < BlueMatt> (I dont disagree, I'm just asking what the right solution is)
08:15 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
08:15 < BlueMatt> elichai2: I have skimmed its code, but not done a careful review. afaict its copy/paste from rustc.
08:15 < elichai2> Maybe a combination of reviewing it and hosting it?( I haven't even skimmed that crate so it might be more/less trivial than I think) 
08:16 < BlueMatt> its pretty trivial
08:16 < BlueMatt> docstring-stripped its probably 1KLoC or something
08:16 < BlueMatt> andytoshi: what do you think of forking core2 and just hosting it ourselves as bitcoin_io or so?
08:18 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
08:23 < BlueMatt> its kinda sad that there isn't an alternative, really. like, this is the kind of thing that should be pretty standardized
08:24 < BlueMatt> but, of course, everyone's just gonna wait around for rustc to fix std::error forever, I guess
08:25 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
08:25 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
08:41 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
08:42 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
08:48 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
08:48 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
08:49 < devrandom> BTW, it got renamed recently from bare-io
08:50 < devrandom> and note that we already made bitcoin_hashes dependent on it
08:50 < devrandom> oh, that was said already
08:51 < BlueMatt> even bare-io doesn't have a *lot* of use, but it seems to be the most popular solution for this, though that isnt saying much :/
08:51 < BlueMatt> you can use bitcoin_hashes with no_std *without* core2, though
08:51 < BlueMatt> whereas making rust-bitcoin work without core2/serialization would be somewhat useless/challenging
08:53 < BlueMatt> I wonder if rust-bitcoin should copy the rust-lightning write traits https://github.com/rust-bitcoin/rust-lightning/blob/main/lightning/src/util/ser.rs#L37-L88 since it doesn't implement the Write/Read side (unlike bitcoin_hashes, which does)
08:54 < BlueMatt> for bitcoin_hashes we couldn't practically provide our own traits because it implements both the Write side and the using-Write/Read side
08:54 < BlueMatt> but for rust-bitcoin I dont think thats the case?
08:55 < BlueMatt> but I'm also fine with core2, really. or just self-hosting it.
08:55 < BlueMatt> rustc looks like they wont fix this for at least a year, they first wanna import std::error into core/alloc, which by itself will probably take a while
09:03 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 268 seconds]
09:05 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
09:37 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 252 seconds]
09:44 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
09:49 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
09:54 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
09:59 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
10:08 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
10:17 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
10:28 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
10:33 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
10:37 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
10:42 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 252 seconds]
10:53 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
10:58 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 268 seconds]
11:02 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
11:08 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 252 seconds]
11:12 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
11:15 -!- belcher [~belcher@user/belcher] has quit [Quit: Leaving]
11:17 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
11:19 < elichai2> Yeah it sucks that there's no official support for it yet but it will take time https://github.com/rust-lang/project-error-handling/issues/11
11:20 < elichai2> I think both no-std and async are in this limbo where if you do it yourself there's nothing stopping you but they don't have good support in the standard library so it's hard to make them interoperable
11:25 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
11:31 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 265 seconds]
11:33 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
11:40 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Ping timeout: 252 seconds]
11:47 < BlueMatt> elichai2: yea, well at least in async-land you can "just use tokio" and then you're compatible with the world of tokio stuff, which is large
11:47 < BlueMatt> with no_std, if you want to use std::error or std::io you're basically building your own island
11:49 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
11:49 -!- ztzu1 [~ztzu1@2a02:908:e853:ec80:7880:286a:b6c:4005] has joined #bitcoin-rust
11:50 -!- ztzu1 [~ztzu1@2a02:908:e853:ec80:7880:286a:b6c:4005] has quit [Client Quit]
11:54 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
12:05 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
12:11 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
12:25 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
12:33 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
12:44 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
12:50 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
12:54 < BlueMatt> elichai2: what do you propose for this, though?
12:54 < BlueMatt> elichai2: would you prefer we fork it?
12:55 < elichai2> BlueMatt: I think personally I just want to know someone reviewed core2 and understands how it works, I don't think we need to actually fork it
12:56 < elichai2> I should probably do it and not hope someone else will :)
12:56 < elichai2> unless you already reviewed it
12:56 < BlueMatt> elichai2: I skimmed it previously, its basically copy+paste of the librustc code
12:56 < BlueMatt> I did not *review* it, no.
12:56 < BlueMatt> sorry, libstd code
12:56 < BlueMatt> but just the trait parts, really.
12:57 < elichai2> Isn't there some trick that switches between libstd and their types depending if std is available?
12:57 < BlueMatt> yes, it also has a "std" feature which just re-exports
12:57 < elichai2> or something, so the types will be interchangeable 
12:57 < BlueMatt> yes, it re-exports std based on a feature
12:57 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
12:57 < BlueMatt> (we dont use that, though - we just use std directly ourselves in that case)
12:58 < BlueMatt> I suppose you could depend on bitcoin_hashes/core2 + core2/std and then its all just std, but...
13:00 < elichai2> fwiw I think that means that core2 is never tested
13:01 < BlueMatt> hmm? oh you mean in our own tests? (a) I dont think we *ever* set core2/std (or shouldnt), and (b) we have new tests in bitcoin_hashes that run bitcoin_hashes (with calls to core2) with no_std on an arm board in qemu
13:02 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
13:08 < elichai2> Ok, I'm looking at core2 and then I'll review the PR. (also asked on Zulip to see if someone has thoughts about core2). let's make it happen :)
13:15 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
13:16 < BlueMatt> thanks!!!
13:16 < BlueMatt> I am now thinking maybe we should fork it - it looks like the project isn't superrrr actively maintained, I mean not like it really needs to be, its just std copied, but still
13:19 -!- belcher [~belcher@user/belcher] has joined #bitcoin-rust
13:20 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 258 seconds]
13:34 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
13:41 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 252 seconds]
13:44 -!- plsm [~plsm@user/plsm] has joined #bitcoin-rust
13:52 -!- plsm [~plsm@user/plsm] has quit [Ping timeout: 265 seconds]
13:59 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has joined #bitcoin-rust
15:03 -!- plsm_ [~plsm@host86-153-59-156.range86-153.btcentralplus.com] has quit [Quit: leaving]
16:56 -!- tibo_ [~tibo@2400:4050:2a83:7000:f559:ed16:6778:84e8] has joined #bitcoin-rust
17:07 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-rust
17:11 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
--- Log closed Wed Jun 23 00:00:46 2021