--- Log opened Wed Jun 26 00:00:53 2019
00:20 -!- reallll is now known as belcher
01:45 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
03:38 -!- rlgt [9ff26f16@159.242.111.22] has joined #rust-bitcoin
03:42 < rlgt> Hello. I would like to leverage the rust-lightning library to create the approriate messages for a payment (update_add_htlc, commitment_signed, revoke_and_ack) but send and recieve them to and from my (private) lightning channel using my own communication band. Is this something that rust-lightning woudl enable me to do? Or is message communication
03:42 < rlgt>  something it handles internally?
03:46 < rlgt> Ideally, I would use rust-lightning to open (and manage) a single private channel whilst online. Then when the machine is offline, I can instruct it to still make a payment, but routing the required messages, generated for me by r-lightning, over another communication channel.
04:37 -!- rlgt [9ff26f16@159.242.111.22] has quit [Ping timeout: 260 seconds]
05:25 -!- rlgt [9ff26f16@159.242.111.22] has joined #rust-bitcoin
05:29 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
05:31 -!- rlgt [9ff26f16@159.242.111.22] has quit [Remote host closed the connection]
05:45 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 260 seconds]
06:01 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-zrmrphvvhhcgkfud] has joined #rust-bitcoin
07:20 < e4xit> sorry I reconnected with another nick, but I asked a question above earlier as "rlgt" which I would still be interested in knowing the answer to :)
07:40 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #rust-bitcoin
08:05 -!- michaelsdunn1 [~michaelsd@38.126.31.226] has joined #rust-bitcoin
08:05 -!- michaelsdunn1 [~michaelsd@38.126.31.226] has quit [Changing host]
08:05 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #rust-bitcoin
09:32 -!- jtimon [~quassel@205.201.35.37.dynamic.jazztel.es] has joined #rust-bitcoin
09:48 < ariard> e4xit: yes rust-lighting was designed without relaying on a specific communication channel, you should have a look on ChannelManager high-level API in channelmanager.rs
09:50 < ariard> Basically you should poll Event from ChannelManager pending_events and dispath serialized messages to the communication channel which suit your needs
09:50 < ariard> s/dispath/dispatch/
09:53 < ariard> e4xit: using Lightning offline is usable but you should maintain a communcation channel with a gateway to get blocks updates and verify state of your channels
10:14 -!- belcher [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
11:44 < BlueMatt> ariard: do you know what version of c-lightning you were connected to when you saw https://github.com/rust-bitcoin/rust-lightning/issues/342 ?
12:56 < ariard> BlueMatt: it was against few cdecker testnet node 03f1042bf244923fbb521680f9266d49c028687ad24ab7ea19a237a39009892615@34.93.63.12:9735 and 02fbe11d3c8c8b76f42769d86b21a3031a4db60dd02ec0855640a565cf7bf825e6@34.77.79.10:9735
13:13 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
13:21 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: quit]
13:33 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
14:02 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #rust-bitcoin
14:03 < e4xit> thanks ariard! I will have a low-bandwith comms channel and also a blocksat to monitor for on-chain transactions. Therefore I think, to simply make a ln payment, I only need to relay the HTCl messages
14:58 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
15:26 -!- vegandonut [324e635e@50-78-99-94-static.hfc.comcastbusiness.net] has joined #rust-bitcoin
15:30 -!- vegandonut [324e635e@50-78-99-94-static.hfc.comcastbusiness.net] has left #rust-bitcoin []
15:32 -!- vegandonut [324e635e@50-78-99-94-static.hfc.comcastbusiness.net] has joined #rust-bitcoin
16:57 -!- vegandonut [324e635e@50-78-99-94-static.hfc.comcastbusiness.net] has quit [Ping timeout: 260 seconds]
17:06 -!- Netsplit *.net <-> *.split quits: gwillen, schmidty, valwal___, sgeisler
17:06 -!- sgeisler [sid356034@gateway/web/irccloud.com/x-sxullczdfigfxtaa] has joined #rust-bitcoin
17:06 -!- valwal___ [sid334773@gateway/web/irccloud.com/x-teustjwbxhtmkuct] has joined #rust-bitcoin
17:06 -!- Netsplit over, joins: gwillen
17:07 -!- schmidty [sid297174@gateway/web/irccloud.com/x-yfosxlgrnlcgdoev] has joined #rust-bitcoin
17:17 < andytoshi> if i have a pubkeyhash is there no way to get a bitcoin::Address from that?
17:18 < andytoshi> hmm i guess https://github.com/rust-bitcoin/rust-bitcoin/pull/254 is what i want
17:19 < andytoshi> stevenroose: i don't get your comment on https://github.com/rust-bitcoin/rust-bitcoin/pull/286
17:19 < andytoshi> are you suggesting users of script::Builder should maintain a list of opcodes in parallel to the Builder?
17:46 -!- elichai2 [uid212594@gateway/web/irccloud.com/x-zrmrphvvhhcgkfud] has quit [Quit: Connection closed for inactivity]
19:55 < ariard> e4xit: if your offline device is only spending, and assuming it doesn't broadcast old commitment txn you don't need to watch the chain beceause every previous balance would be in your benefit
19:56 < ariard> If it's also receiving payment you should have gateways providing you internet access to broadcast penalty txn in case of channel breach
19:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
20:22 -!- jtimon [~quassel@205.201.35.37.dynamic.jazztel.es] has quit [Ping timeout: 252 seconds]
21:04 -!- gwillen [~gwillen@unaffiliated/gwillen] has quit [Remote host closed the connection]
22:45 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has joined #rust-bitcoin
22:48 -!- gwillen [~gwillen@unaffiliated/gwillen] has joined #rust-bitcoin
22:51 -!- ccdle12 [~ccdle12@cpc139350-aztw33-2-0-cust310.18-1.cable.virginm.net] has quit [Remote host closed the connection]
23:42 -!- TamasBlummer1 [~Thunderbi@p200300DD67196B4991D1696F4001E110.dip0.t-ipconnect.de] has joined #rust-bitcoin
23:44 -!- TamasBlummer [~Thunderbi@p200300DD67196B33693E23985DA2C18A.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
23:44 -!- TamasBlummer1 is now known as TamasBlummer
--- Log closed Thu Jun 27 00:00:54 2019