--- Log opened Sun Feb 17 00:00:52 2019 02:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 02:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:56 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:58 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 03:23 < m-schmoock> cdecker: `make update-mocks` is my friend :> 04:50 < fiatjaf> can I generate an invoice with a specific preimage without having to specify an expiry date and a fallback list? 04:51 < fiatjaf> invoice msatoshi label description [expiry] [fallbacks] [preimage] [ex 04:51 < fiatjaf> poseprivatechannels] 05:10 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 244 seconds] 05:23 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 05:33 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 06:20 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has quit [Remote host closed the connection] 06:20 -!- ctrlbreak [~ctrlbreak@142.162.20.53] has joined #c-lightning 07:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 08:05 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 08:36 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 08:37 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 10:05 < m-schmoock> fiatjaf: i think you can talk directly to the JSON rpc interface and set the preimage without the other optional params 10:06 < m-schmoock> you can for example use this nodejs lib: https://www.npmjs.com/package/json-ipc-lib 10:06 < m-schmoock> and use something like this: 10:06 < m-schmoock> const ipc = require('json-ipc-lib'); 10:06 < m-schmoock> const LN_RPC = process.env['LN_RPC'] || '~/.lightning/lightning-rpc'; 10:06 < m-schmoock> 10:06 < m-schmoock> function getClient(){ 10:06 < m-schmoock> return new ipc.Client(LN_RPC); 10:06 < m-schmoock> } 10:06 < m-schmoock> 10:06 < m-schmoock> module.exports = { 10:06 < m-schmoock> getClient 10:06 < m-schmoock> }; 10:06 < m-schmoock> then call any LN function you want 10:06 < m-schmoock> you can use other libs and implementations as well 10:10 < fiatjaf> right, I'm doing that 10:10 < fiatjaf> I'm talking directly to the json rpc interface 10:10 < fiatjaf> but it expects a thing called '"params": []' 10:10 < fiatjaf> so what should I pass there? 10:11 < m-schmoock> you can use named params as well 10:11 < fiatjaf> wait, let me read the docs 10:11 < fiatjaf> oh, can I? 10:11 < fiatjaf> how? 10:11 < m-schmoock> uhm 10:11 < m-schmoock> now that i asked, i never tried :D 10:12 < m-schmoock> i will have a look later, need to go for a while 10:13 < fiatjaf> ok, thank you :P 10:13 < m-schmoock> i will try it in my nodejs implementation... normally a json interface should support this 10:15 < m-schmoock> instead of json_iface.invoice([param1, param2]) you would have to do a json_iface.invoice({"msatoshi" : 123, "preimage": "...", "some_other_param" : "foo"}) 10:15 < m-schmoock> dont know though if clightning supports it 10:16 < m-schmoock> im rather new here 10:28 < fiatjaf> so you were right 10:29 < fiatjaf> although not documented anywhere, this is indeed supported by the rpc interface. instead of "params": [] you can pass "params": {} with named parameters. 11:36 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.3] 11:54 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 12:33 < m-schmoock> :D 12:34 < m-schmoock> thx for testing. maybe you can update the doc to point out usage of named parameters. but its more or less standard in json rpc interfaces 13:07 -!- kexkey [~kexkey@87.101.92.74] has joined #c-lightning 14:19 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:35 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 14:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 15:16 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 15:20 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 16:44 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 17:06 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 17:24 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection] 17:25 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning 17:57 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 18:30 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 19:09 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection] 19:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:46 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 20:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 21:00 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 21:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:25 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:54 < jonasschnelli> jonassc+ 28673 3.4 3.8 21475181744 2551064 pts/8 R+ Feb16 95:30 /home/jonasschnelli/lightning/lightningd/lightning_gossipd 21:54 < jonasschnelli> is that normal? 21:54 < jonasschnelli> 100% cpu 3.9% of ram (64GB system) 21:55 < jonasschnelli> and the process seems not to calm down 22:03 < jonasschnelli> a restart cured it,... not sure if its a memory leak 23:02 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 255 seconds] --- Log closed Mon Feb 18 00:00:53 2019