--- Log opened Tue Aug 27 00:00:53 2019 00:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 00:51 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds] 00:52 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 00:52 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds] 01:02 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 02:03 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds] 02:03 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 02:04 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 268 seconds] 02:09 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 02:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 258 seconds] 03:33 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 03:34 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 04:16 -!- vincenzopalazzo [~vincenzop@209.58.163.27] has joined #c-lightning 04:16 < vincenzopalazzo> Hello Guys, I'm new in the c-lightning world and I have two different question, the first is, How can create an channel on my personal node? 04:16 < vincenzopalazzo> The second question, I can developer a wrapper for lighitingd with java? if yes the url definition for connect is "http://user:pass@127.0.0.1:9735"? 04:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 04:25 -!- vincentpalazzo [~vincenzop@host22-50-dynamic.7-87-r.retail.telecomitalia.it] has joined #c-lightning 04:27 -!- vincenzopalazzo [~vincenzop@209.58.163.27] has quit [Ping timeout: 258 seconds] 04:40 <@cdecker> Ciao vincentpalazzo, you can create a new channel with some other (publicly reachable) node by first connecting to the node (`lightning-cli [node_id] [ip@port]`) and then funding a channel on that connection (`lightning-cli fundchannel [node_id] [satoshis]`). 04:41 <@cdecker> After this you should be able to use `lightning-cli listpeers` to see the peer and the channel that you are opening with it. 04:41 <@cdecker> Once the state is `CHANNELD_NORMAL` you can start using the channel to perform payments 04:42 <@cdecker> More on these commands can be found here: https://lightning.readthedocs.io/lightning-fundchannel.7.html 04:43 < backpacker69> command to connect is actually `lightning-cli connect [node_id] [ip@port]` 04:43 < backpacker69> you accidently a word 04:47 < backpacker69> there are some coins that have timestamp as part of their transaction, to make commitment transactions work both sides have to agree on timestamp, this information was missing so i had to add it to htlc structure during exchange, things seem to be working as long as channel is one to one, but once you have somebody in the middle things go wrong. i am wondering if there is a better way to go forward rather than i have done 04:47 <@cdecker> Whoops, I seem to be doing that lately :-) 04:48 < backpacker69> https://github.com/backpacker69/lightning 04:48 < backpacker69> it’s a little messy because i wasn’t sure if i am doing the right thing 04:48 <@cdecker> Not sure I understand what timestamp you're referring to 04:48 <@cdecker> For forwarding the blockheight is important 04:49 < backpacker69> proof of stake coins such as peercoin have timestamp as part of the transaction blob 04:49 < backpacker69> right after the version 04:49 <@cdecker> Ah, ok so this is not bitcoin related 04:49 < backpacker69> it also gets hashed, so timestamp affects transaction id 04:50 < backpacker69> yes, it’s not pure bitcoin, leaving reasons for having the timestamp in transaction aside, i was wondering what you would recommend to do 04:56 <@cdecker> For your fork using peercoin, or in general? 05:05 < vincentpalazzo> Thanks , so for create a wrapper rpc with java, I can use the her url? 05:11 <@cdecker> I don't quite get where you'd use the URL, are you trying to talk to your node (then no, since we don't expose the RPC over the network by default), or are you trying to connect your node to a remote node (in which case, no because the scheme is wrong, we don't use username and password and the node_id is missing) 05:16 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 248 seconds] 05:17 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 05:17 <@cdecker> What kind of wrapper are you trying to build? 05:17 < vincentpalazzo> I have try this operation "I don't quite get where you'd use the URL, are you trying to talk to your nod", because module rpc not expost over the network? 05:17 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds] 05:18 < vincentpalazzo> I want create a wrapper or command for create my personal app with java, an example to GUI with a web app 05:20 <@cdecker> Ok, so it's a wrapper to talk between your app and your node 05:21 <@cdecker> Have you taken a look at https://github.com/ElementsProject/lightning/pull/2223 ? It was Rene's Java client library. It was pretty good, but we wanted to keep client libraries out of the core project which is why it was closed 05:21 <@cdecker> It should be a good starting point to get your own app off the ground :-) 05:29 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 05:32 < vincentpalazzo> Thank so much, I will look the pool request 05:33 <@cdecker> No problem, feel free to reach out if you need help ^^ 05:38 < vincentpalazzo> :) 06:01 < backpacker69> cdecker: sorry got sidetracked, yes, i am doing this for peercoin at the moment 06:01 < backpacker69> but i imagine the problem would be identical for any peercoin forks 06:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 07:22 -!- Kostenko [~Kostenko@195.12.50.233] has quit [Ping timeout: 245 seconds] 07:39 -!- Kostenko [~Kostenko@195.12.50.233] has joined #c-lightning 07:48 -!- vincentpalazzo [~vincenzop@host22-50-dynamic.7-87-r.retail.telecomitalia.it] has quit [Ping timeout: 245 seconds] 07:49 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has joined #c-lightning 07:53 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zegkwibbopnqyxhp] has left #c-lightning [] 07:53 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zegkwibbopnqyxhp] has joined #c-lightning 07:56 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has quit [Quit: Leaving] 07:56 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has joined #c-lightning 08:02 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds] 08:03 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 08:03 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 246 seconds] 08:03 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has quit [Quit: Leaving] 08:11 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 08:25 -!- trueptolemy [47139248@71.19.146.72] has joined #c-lightning 08:28 -!- trueptolemy [47139248@71.19.146.72] has quit [Remote host closed the connection] 08:30 -!- trueptolemy [2d582886@45.88.40.134] has joined #c-lightning 08:32 -!- trueptolemy [2d582886@45.88.40.134] has quit [Remote host closed the connection] 09:10 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 246 seconds] 09:11 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 258 seconds] 09:11 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 09:19 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 10:38 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 272 seconds] 10:38 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #c-lightning 10:38 -!- rafalcpp_ [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 245 seconds] 10:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 11:17 -!- trueptolemy [47139248@71.19.146.72] has joined #c-lightning 11:17 < trueptolemy> niftynei: Thank you for your explanation! Now when I implement to cancel the channel after `fundchannel_complete` before funding broadcast, I meet this case: we forget the channel and send a error message to the remote peer, but the default behavior of remote is to broadcast unilateral close. 11:19 -!- trueptolemy10 [2d582886@45.88.40.134] has joined #c-lightning 11:19 -!- trueptolemy [47139248@71.19.146.72] has quit [Remote host closed the connection] 11:20 < trueptolemy10> ZmnSCPxj said "Either way we should immediately forget the channel if we receive error during CHANNELD_AWAITING_LOCKIN if we are fundee.", the link is https://github.com/ElementsProject/lightning/issues/2740#issue-455535978 11:27 -!- trueptolemy [2d582886@45.88.40.134] has joined #c-lightning 11:28 < trueptolemy> do you agree with "forget the channel if we receive error during CHANNELD_AWAITING_LOCKIN if we are fundee"? I find if "fundee" doesn't forget channel immediately, "funder" will meet the error of "Already have active channel" from fundee when funder tries to `fundchannel_start` again 11:28 -!- trueptolemy10 [2d582886@45.88.40.134] has quit [Ping timeout: 260 seconds] 11:33 -!- trueptolemy74 [2d582886@45.88.40.134] has joined #c-lightning 11:34 -!- trueptolemy [2d582886@45.88.40.134] has quit [Ping timeout: 260 seconds] 11:42 -!- trueptolemy74 [2d582886@45.88.40.134] has quit [Ping timeout: 260 seconds] 13:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:21 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving] 13:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 258 seconds] 13:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:54 -!- rusty1 [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds] 14:15 -!- rusty1 [~rusty@pdpc/supporter/bronze/rusty] has quit [Disconnected by services] 14:15 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:43 <@niftynei> right, ZmnSCPxj is correct about needing the peer to immediately forget the channel on error during AWAITING_LOCKIN, with the caveat that they must not have seen the transaction on chain yet 14:45 <@niftynei> if the transaction is on-chain, you'd need to close it out 15:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zegkwibbopnqyxhp] has left #c-lightning [] 16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zegkwibbopnqyxhp] has joined #c-lightning 16:19 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 16:21 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning 17:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 18:38 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has quit [Ping timeout: 244 seconds] 19:00 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has joined #c-lightning 19:43 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has quit [Ping timeout: 245 seconds] 19:45 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has joined #c-lightning 21:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 246 seconds] 22:37 < rusty> b 1182 --- Log closed Wed Aug 28 00:00:54 2019