--- Log opened Fri Jan 15 00:00:15 2021
00:16 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
01:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
01:05 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
01:14 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
02:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
02:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
02:48 -!- gwillen [~gwillen@unaffiliated/gwillen] has quit [Ping timeout: 260 seconds]
03:00 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Read error: Connection reset by peer]
03:00 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
03:00 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Remote host closed the connection]
03:00 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Write error: Broken pipe]
03:00 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
03:00 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
03:00 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Write error: Connection reset by peer]
03:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #c-lightning
03:03 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
03:03 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning
03:03 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #c-lightning
03:03 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
03:03 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
03:04 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:05 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
03:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds]
03:43 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #c-lightning
04:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:09 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
05:10 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
06:18 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Ping timeout: 256 seconds]
06:47 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
07:04 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning
07:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
07:14 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
07:15 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
07:16 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
07:18 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
07:21 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
08:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
08:13 -!- jonatack [~jon@213.152.162.74] has quit [Ping timeout: 264 seconds]
08:15 -!- jonatack [~jon@88.124.242.136] has joined #c-lightning
08:19 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
08:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
08:30 -!- kexkey [~kexkey@static-198-54-132-93.cust.tzulo.com] has joined #c-lightning
08:43 -!- kexkey [~kexkey@static-198-54-132-93.cust.tzulo.com] has quit [Ping timeout: 272 seconds]
08:47 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 240 seconds]
08:47 -!- jonatack [~jon@213.152.162.10] has joined #c-lightning
08:56 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
08:56 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
08:56 -!- vasild_ is now known as vasild
09:43 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
09:59 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning
10:08 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Quit: liberliver]
10:29 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
10:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
10:32 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
10:33 -!- cdecker changed the topic of #c-lightning to: Next meeting here @8PM UTC Monday Jan 25  Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning  Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.9.3rc2 Logs at http://gnusha.org/c-lightning/ Dev Roadmap: https://github.com/ElementsProject/lightning/wiki
10:33  * cdecker just tagged release candidate 2 for the 0.9.3 release, now with more onions and offers :-)
10:49 < az0re> cdecker: can you explain real quickly what you mean by onions and offers?
10:50 < az0re> doesn't c-lightning already do onion-routed payments?
10:50 < az0re> and what are offers? did I miss some BOLT?
10:51 <@cdecker> It does, but there are two new proposals (onion messages and offers) that add new subprotocols that allow arbitrary communication (not payment related) and real-time negotiation of invoices
10:51 <@cdecker> Onion messages: https://github.com/lightningnetwork/lightning-rfc/pull/755
10:51 <@cdecker> Offers: https://github.com/lightningnetwork/lightning-rfc/pull/798
10:52 <@cdecker> I have a blogpost queued up giving a high level overview, but the PRs should already give a pretty good idea of what they enable
10:53 < az0re> thanks a lot
10:53 < az0re> I'll check 'em out
10:53 < az0re> so does this open up the ability to chat with my channel peer operators?
10:54 < az0re> honestly that would be a great feature, e.g. to coordinate channel balancing and (ideally automatic) fee refunds for them
11:15 < HelloShitty> Hi
11:16 < HelloShitty> If that onion messages an offers is about what az0re is saying, yes, really cool feature
11:16 < HelloShitty> to be able to message other nodes, via node explicitely, instead of using other means to comunicate with node/peers owners
11:24 < az0re> ya I don't think so; skimming the changes from those PRs cdecker mentioned leads me to believe onion messages are exclusively to support invoice requests/responses for offers
11:24 <@cdecker> That's definitely an option for onion messages, but it is apriori not a chat message, more of a way for nodes (and plugins) to exchange messages
11:25 <@cdecker> They are a pretty generic tool, it's just that we use offers as the first showcase for it. Later you can simply create a chat on top of onion messages
11:25 < az0re> Would that mean that more types have to be added here? https://github.com/lightningnetwork/lightning-rfc/pull/798/files#diff-ad65f0beaac5cef88f5fd7a8b9ca36cbc5a790f4815b4b50b9ea794a55aaf012
11:27 < az0re> I mean in 04-onion-routing.md, under the types for `onionmsg_payload`
11:27 <@cdecker> Yep, you'd add new payload fields (presumably containing the chat message, nickname and signature, etc)
11:27 -!- belcher_ is now known as belcher
11:28 < az0re> No need for nickname or signature, right?
11:28 < HelloShitty> Let me ask a question about what I see and I'm not familiar at all (I'm not a dev by nature, so I don't know how workflows use to be for devs)
11:29 < az0re> "message from <node id or scid of the node id if they're your channel peer>: blah blah"
11:29 < az0re> ah maybe a signature is needed, sure
11:29 < HelloShitty> You devs are required to create these *.md files with the data types used why? Is it just a aquick way to check datatypes used or what?
11:30 < az0re> it's a spec
11:30 < HelloShitty> But doesn't bolts already do that? Or they are not that techcnicaly intended as those .m files?
11:30 < HelloShitty> s/.m/.md
11:33 < az0re> cdecker: it would be cool to add a generic `notification` type to the spec that allows application-defined behavior without having to update client software
11:34 < az0re> for plugins
12:04 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
12:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
13:14 -!- Ademan [~ademan@47.185.102.158] has quit [Ping timeout: 264 seconds]
13:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
15:20 -!- Netsplit *.net <-> *.split quits: berndj, wraithm
15:21 -!- Netsplit over, joins: berndj
15:22 -!- Netsplit over, joins: wraithm
17:27 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
18:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has left #c-lightning []
18:58 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-grtgkzfemgwjcvcq] has joined #c-lightning
19:00 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
19:06 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
19:13 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has quit [Remote host closed the connection]
19:14 -!- mryandao [~mryandao@gateway/tor-sasl/mryandao] has joined #c-lightning
20:06 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
20:12 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:55 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
20:55 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Disconnected by services]
20:55 -!- vasild_ is now known as vasild
21:30 -!- sr_gi [~sr_gi@47.61.62.148] has quit [Read error: Connection reset by peer]
21:30 -!- sr_gi [~sr_gi@47.61.62.148] has joined #c-lightning
--- Log closed Sat Jan 16 00:00:17 2021