--- Log opened Thu Sep 24 00:00:27 2020 00:05 < jasan> dr-orlovsky: by the way, 'lightning-cli: Connecting to 'lightning-rpc': Connection refused' usually means your lightningd is not running 00:05 < jasan> dr-orlovsky: I am able to connect to daki's node. 00:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 01:06 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 01:14 < m-schmoock> anyone that wants to open stracktrace output with line number (file:NUM) in vim without editing the ':' to a ' +' can use the following function in ~/.bashrc 01:14 < m-schmoock> function vim() { 01:14 < m-schmoock> if [[ "$1" =~ ^.*:[0-9]*$ ]]; then 01:14 < m-schmoock> set -- $(echo "$1" | awk '{ gsub(/:+/, " +" ); print; }') 01:14 < m-schmoock> fi 01:14 < m-schmoock> /usr/bin/vim $@ 01:14 < m-schmoock> } 01:14 < m-schmoock> directly jumps to the location when using i.e. vim common/daemon.c:38 01:14 < m-schmoock> ;) 01:14 < jasan> m-schmoock: thanks! I will try it. 01:15 < m-schmoock> can be enhanced by iterating and improving on the awk gsub I guess, but works in 99.9% the cases 01:23 -!- jonatack [~jon@82.102.27.171] has quit [Ping timeout: 256 seconds] 01:31 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning 02:02 -!- jonatack [~jon@213.152.161.211] has joined #c-lightning 02:03 -!- jonatack [~jon@213.152.161.211] has quit [Read error: Connection reset by peer] 02:04 -!- kexkey [~kexkey@89.36.78.166] has quit [Ping timeout: 240 seconds] 02:09 -!- jonatack [~jon@37.166.17.41] has joined #c-lightning 02:34 -!- sr_gi7 [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning 02:34 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 02:34 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Ping timeout: 265 seconds] 02:34 -!- sr_gi7 is now known as sr_gi 02:35 -!- HelloShitty [~narayan@bl20-171-222.dsl.telepac.pt] has joined #c-lightning 03:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 03:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 03:05 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:12 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:44 < dr-orlovsky> jasan: but I am able to establish other connections... Anyway, I will update docker instances with new master and will try again today 03:46 < jasan> dr-orlovsky: OK, there is yet another node with IPv4 address as well as onion. You can try that one. 03:48 < jasan> dr-orlovsky: See #4078 which became a postmortem chat 03:48 < jasan> s/mortem/merge/ 03:51 < dr-orlovsky> :) 03:59 -!- jonatack [~jon@37.166.17.41] has quit [Read error: Connection reset by peer] 04:46 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 04:49 -!- jonatack [~jon@37.166.201.89] has joined #c-lightning 05:00 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 05:24 < m-schmoock> cdecker: we have an issue with malformed SQL. See wallet/db_sqlite3_sqlgen.c line 1056 and 1057 missing (space before the WHERE) i.e. UPDATE outputs SET status=?, reserved_til=?WHERE prev_out_tx=? AND prev_out_index=?" 05:24 < m-schmoock> same for wallet/db_postgres_sqlgen.c 05:25 < m-schmoock> I found out by using the dblog.py plugin on some other testcases I work on, it crashes because of broken SQL statements 05:26 <@cdecker> Ok, the source for the query is wallet/wallet.c:417 05:27 < m-schmoock> ah there it is 05:27 <@cdecker> Seems we have a bad string continuation 05:27 < m-schmoock> is this serious? 05:27 < m-schmoock> at least to me it looks like it could be serious 05:27 <@cdecker> Ouch, it's part of the release, last touched 2020-07-15 05:27 < m-schmoock> fck 05:27 < m-schmoock> sry :/ 05:27 < m-schmoock> ^^ 05:28 < m-schmoock> for some reason this is not covered by a test 05:28 <@cdecker> It seems it's getting called only through the reservation system 05:28 < m-schmoock> and I found out by chance 05:30 <@cdecker> So far it seems like it's part of the `reserveinputs`, `fundpsbt` and `utxopsbt` RPC calls (the last two only if a reservation was specified) 05:31 < m-schmoock> I found out by adding the dblog.py plugin to the tests/test_connection.py test_fail_unconfirmed testcases where it crashed because of this 05:32 < m-schmoock> this testcase is not using the reservation api, right?? 05:33 <@cdecker> And `sendpsbt` is also impacted 05:33 < m-schmoock> also that is not used 05:33 -!- jonatack [~jon@37.166.201.89] has quit [Read error: Connection reset by peer] 05:33 < m-schmoock> shall I fix it quickly or do you want to handle it personally 05:33 < m-schmoock> ? 05:34 <@cdecker> Well tracing all the call paths might take some time, but this should have been triggered a number of times with all the calls involved 05:34 <@cdecker> Happy to let you fix it and I can add context to the PR :-) 05:34 <@cdecker> Since you found it credit should go to you for fixing it 05:34 < m-schmoock> kk. lets get it done quick 05:35 <@cdecker> Pretty sure you know how to fix it ^^ 05:37 < m-schmoock> I wonder if it would be useful to somehow run the complete testsuite one time with the dblog plugin to make sure this will not happen 05:38 < m-schmoock> but it needs a hack in the pyln test utils or something I guess 05:38 <@cdecker> Well, what I don't get is why this wasn't causing a crash. We bail on syntactic SQL statement errors usually 05:39 <@cdecker> Oh, wait I think I know why it didn't trigger 05:39 < m-schmoock> yes, thats strange 05:42 <@cdecker> Hm, no, not what I thought, digging further 05:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 05:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 05:46 <@cdecker> Hm, I can't get my node to choke on this, you were using the dblog plugin you were saying? 05:48 < m-schmoock> https://github.com/ElementsProject/lightning/pull/4090 05:48 < m-schmoock> there I describe it 05:49 < m-schmoock> your need this change i.e.: https://pastebin.com/yUTHcHgF 05:49 < m-schmoock> and then execute this particular testcase 05:50 <@cdecker> Gotcha 05:50 < m-schmoock> thats why I wonder if it would be an option to have a testsuit run with the plugin enforced 05:50 < m-schmoock> but maybe theres a better was 05:51 < m-schmoock> *way 05:55 <@cdecker> Very interesting, the only explanation I have for it not failing more often is that the C API of sqlite3 parses it correctly (not combining the `?` placeholder with the `WHERE`), but then once we expand the query with the actual parameters it fails to parse in anything that consumes the expanded query 05:56 < m-schmoock> hm 05:57 < m-schmoock> really fishy... if we have this here... I wonder how many testcases fail if I have the dblog plugin into a full run ^^ 05:57 < m-schmoock> hopefully no more than this 06:01 <@cdecker> Yep, I think we found the cause: SQL query expansion results in an unparseable SQL query :-) 06:02 < m-schmoock> so its just failing for the plugin ? 06:02 <@cdecker> No crashes until the plugin attempts to execute the statement, and thus fails to reply to the hook. If a plugin fails to reply we have to terminate, since it is not safe to continue 06:02 <@cdecker> Yep, pretty much 06:03 < m-schmoock> okay, so not really bad 06:03 < m-schmoock> just ugly and luck 06:03 <@cdecker> Added a comment with these findings on the PR, impact is relatively small and the circumstances are pretty specific 06:06 <@cdecker> I'll run the tests with the dblog plugin, but since we kill some nodes during tests we may get unrelated errors doing so (when the dblog DB gets out of sync with the actual DB) 06:06 < m-schmoock> yes I know, but thats easy to differentiate 06:07 <@cdecker> Indeed 06:07 < m-schmoock> just catch for "Error while processing db_write" 06:07 < m-schmoock> whats the best way to enable a plugin for all tests (except for the ones that already use that plugin) ? 06:07 < jasan> m-schmoock, cdecker: see https://github.com/ElementsProject/lightning/pull/4091 06:07 < m-schmoock> hehe 06:08 < jasan> all hand painted, still wet 06:09 < m-schmoock> uuuh 06:09 < m-schmoock> quite some occurences 06:09 <@cdecker> Hehe, yeah that's a one-time fix, no idea how to automate this 06:10 < jasan> cdecker: I think that after this change there will be no more errs because even when someone will copy&paste, it will be clear. 06:10 < jasan> And next year I can do it again anyway... ;) 06:10 < m-schmoock> lol just what I thought 06:11 < m-schmoock> cdecker: should I cherry pick jasan change ontop? 06:11 < jasan> m-schmoock: there were just a couple of those real things, but thanks for noticing it! 06:11 <@cdecker> No, let's not do widespread rewrites just for the sake of it 06:14 <@cdecker> Ok, just reproduced the original issue, now checking all tests ^^ 06:14 < jasan> cdecker: There were many copy&pastes where a line was added and it missed the space. I think it is good to show good example to whoever will add lines in the future. 06:15 < jasan> not many missed the space 06:15 < jasan> but many c&p 06:15 <@cdecker> I know, but we need to add tooling to find them instead of doing this manually every blue moon 06:16 < jasan> Sure. But before you have the tooling this is ready and for free. 06:18 <@cdecker> Yes, but this is (unnecessarily) touching almost ever single SQL statement 06:19 < jasan> I see. 06:19 <@cdecker> I'd rather fix the broken ones selectively, verify that we addressed the issue and protect us from future ones 06:20 <@cdecker> The impact is small enough that we don't need to rush a fix out, so let's make sure we fix it once and for all 06:20 < m-schmoock> yup 06:39 < m-schmoock> cdecker: I use this https://pastebin.com/me3XgMKA 06:40 < m-schmoock> and almost all tests fail :D 06:44 <@cdecker> I'm using this: https://gist.github.com/cdecker/f743d0dbbc4d6b71188fcd323a22685f 06:45 < m-schmoock> thats a more organized way of doing it :D 06:47 <@cdecker> I had a couple of goals for this: a) dblog.py is not part of pyln-testing so we need to add it outside, b) we need to have the option to opt out, c) it is only applicable to sqltie3 06:50 < m-schmoock> yes and yes. the code snippet of dblog.py can be included by ENV switch into the pytest utils 06:51 < m-schmoock> hm 06:51 < m-schmoock> nope 06:51 < m-schmoock> must be a plugin 06:52 <@cdecker> I guess we bumped against the limitations of statement expansion here. A really clean solution would be to return the unexpanded query and a list of bindings, juts like we treat them internally 06:53 <@cdecker> That'd be also way safer and would also be easier to compress (hexdecode binary parameters, deduplicate statement structure, ...) 06:53 <@cdecker> And we'd get postgresql support back for db_write hook calls as well 06:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 07:17 <@cdecker> Ok, I think we got them all, just found one last issue 07:21 < m-schmoock> cdecker: ack. do we patch traevis job to also run TEST_CHECK_DBSTMTS once or do we do it before release? 07:22 <@cdecker> Running on Travis with each change: https://github.com/ElementsProject/lightning/pull/4092 07:24 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 07:25 < m-schmoock> I see. good 07:26 < m-schmoock> lets wait for travis 07:27 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 07:33 <@cdecker> Mind if I rephrase the Changelog line a bit, now that we have a better understanding? 07:33 < m-schmoock> yes sure 07:33 < m-schmoock> already thought that 07:34 < m-schmoock> runner 1 keeps failing for no apparent reason 07:36 <@cdecker> Yeah, that's the one which tries to run without python but we have some issues detecting we don't need some of the generated things 07:38 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 07:39 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 07:39 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 07:41 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 07:42 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.] 07:43 -!- harding [quassel@2600:3c03::f03c:91ff:fe7b:78d1] has joined #c-lightning 07:46 < m-schmoock> cdecker: I did run locally. all good now. lets give rusty the final call, since it increases test load by another job 07:47 <@cdecker> Sounds good 07:48 < m-schmoock> i will close the underlying PR ok? 07:48 <@cdecker> jasan: sorry for being so prescriptive before, I appreciate your initiative taking on the issue, didn't want to shut you down 07:48 <@cdecker> Nah, leave the PR open for now 07:48 < m-schmoock> k 07:48 <@cdecker> We can merge them in order 07:49 < m-schmoock> jasan: this is normal, we want as little change as required and testcases for all of it. Even thought the statements could be cleaner, since they dont fail (now provably) no reason to change them 07:58 < m-schmoock> cdecker: you did not rephrase the commit Changelog in #4092 daad121 not sure which one we will pick. Also in #4090 there now not the change for db: Fix statement expansion bugs found through dblog mode 07:59 < m-schmoock> d7e92abnot sure if you want to force push / rebase again. just for the note 07:59 < m-schmoock> gotta go now. cu l8er 07:59 <@cdecker> I'll rebase 4092 on top of 4090 now 08:23 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning 08:27 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 08:44 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Ping timeout: 264 seconds] 08:47 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning 09:01 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 09:20 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 09:22 < m-schmoock> cdecker: using TEST_CHECK_DBSTMTS=1 is a neat way to enable SQL debugging 09:23 < m-schmoock> <3 09:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds] 10:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 10:48 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 10:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 10:49 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode] 10:51 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 10:57 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 10:58 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Read error: Connection reset by peer] 11:09 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 11:13 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 11:14 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 11:24 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 258 seconds] 11:28 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 12:00 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 12:16 < dr-orlovsky> jasan: made a new build, works perfectly fine: signet channel to you is funded 12:21 < HelloShitty> Hello peeps 12:21 < HelloShitty> I'm reading github on how to configure the config file 12:21 < HelloShitty> I'm a completelly new user to c-lightning implementation 12:21 < HelloShitty> and in github says: 12:22 < HelloShitty> To use a configuration file, create a file named config within your top-level lightning directory or network subdirectory (eg. ~/.lightning/config or ~/.lightning/bitcoin/config). See man -l doc/lightningd-config.5. 12:22 < HelloShitty> I can't make this part to work: 2~ 12:22 < HelloShitty> ups, sorry 12:22 < HelloShitty> See man -l doc/lightningd-config.5. 12:23 < HelloShitty> this file doc/lightningd-config.5 doesn't exist inside the repository I downloaded from github 12:23 < HelloShitty> ohh sorry 12:23 < HelloShitty> forget 12:23 < HelloShitty> I was mistyping it 12:26 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 12:43 < HelloShitty> I have a question about the configuration lines fee-base and fee-per-satshi... What is the relationship between these two? Changing one, changes anything on the other? How does fee-base works on a transaction? 12:45 < m-schmoock> HelloShitty: so many questions. Normally you dont have to touch routing fees 12:45 < m-schmoock> the fee-base applies a fixed amount to forwarded HTLCs given in milli-satoshi 12:46 < HelloShitty> ok, but fees-per-satoshi I can easily understand. But not the other or if they work together, how they work together 12:46 < m-schmoock> the fee per million-satoshi (ppm) is a relative amount to the size of the forwarded payment 12:46 < m-schmoock> the base fee applies fixed plus the relative ppm amount 12:47 < HelloShitty> ok, I think I get it 12:47 < m-schmoock> see see ./doc/lightning-setchannelfee.7 12:47 < m-schmoock> (I wrote it) 12:47 < HelloShitty> I'm still reading lightningd-config.5 12:47 < m-schmoock> or ./doc/lightning-setchannelfee.7.md if you use a text editor and not man 12:47 < HelloShitty> but I'll read that one too for sure 12:48 < m-schmoock> just if you want to learn about fees 12:48 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 12:48 < HelloShitty> I'm using vim 12:48 < HelloShitty> and as this is th first time I'm installing and working with c-lightning 12:48 < HelloShitty> there are a few terms in the help files I need to get familiar with 12:48 < HelloShitty> like that HTLC thing 12:49 < HelloShitty> but for now, I'm only reading and get to know available options in lightningd-config.5 12:50 < HelloShitty> m-schmoock: one quesiton about the first time we run lightning bin 12:50 < HelloShitty> and that we also run the bootstrap node script 12:50 < m-schmoock> the config, all you need to setup is something like this: 12:50 < m-schmoock> [8$alias= 12:50 < m-schmoock> network=bitcoin 12:50 < m-schmoock> bitcoin-rpcuser= 12:50 < m-schmoock> bitcoin-rpcpassword= 12:50 < m-schmoock> bitcoin-datadir=/home//.bitcoin 12:50 < HelloShitty> it has a peer lis inside 12:50 < m-schmoock> bitcoin-rpcconnect=localhost 12:50 < m-schmoock> bitcoin-rpcport=8332 12:50 < m-schmoock> whops, without th [8$ 12:51 < HelloShitty> wait, I don't have default options in my btc node 12:51 < m-schmoock> then change it accordingly 12:51 < HelloShitty> yes 12:51 < m-schmoock> you know how to generate a bitcoind rpc user? 12:51 < HelloShitty> no not yet 12:52 < HelloShitty> is it mandatory? 12:52 < HelloShitty> I just started lightning yesterday and only issued a getinfo command 12:52 < HelloShitty> I was reading about config file now 12:52 < HelloShitty> It's too much info... lol. Need to take baby steps 12:52 < m-schmoock> yes, this is mandatory I guess 12:53 < HelloShitty> but allow me to do some basic questions that I might not easily find answers 12:53 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds] 12:53 < HelloShitty> why lightning needs to know about bitcoin-datadir ? 12:53 < HelloShitty> I mean, I started it with no options or config file and it ran 12:54 < HelloShitty> didn't complaint about missing bitcoin datadir or such 12:54 < m-schmoock> I think it does not not need, but it needs an RPC user for sure 12:54 < HelloShitty> ah oki 12:54 < HelloShitty> But, that also rises another question 12:55 < HelloShitty> when I run lightning-cli getinfo, am I not already issuing an RPC command ? 12:55 < HelloShitty> Isn't this an RPC command itself? 12:55 < HelloShitty> I mean, this command will go to an RPC server, will be interpreted and then the result will be returned to lightning daemon which present the result in JSON format 12:55 < m-schmoock> you can generate a RPC user by using this (from bitcoin core soources) ./share/rpcauth/rpcauth.py 12:55 < HelloShitty> or something like this, no? 12:56 < m-schmoock> too many question in too little time :D 12:56 < HelloShitty> indeed, I'm sorry 12:56 < m-schmoock> lightning-cli getinfo issues an RPC command to lightnind not bitcoind 12:57 < HelloShitty> yes, that's what I said 12:57 < HelloShitty> I guess 12:57 < m-schmoock> try to create an RPC test user, put it in ~/lightning/config as described above 12:57 < m-schmoock> then restart lightnind and try getinfo 12:57 < HelloShitty> the getinfo command worked wven without me creating an RPC user 12:57 < HelloShitty> that's why I was asking about the need of an RPC user 12:57 < HelloShitty> but let me try 12:58 < m-schmoock> ig it shows you the bitcoind running and blockheight and such its working 12:58 < HelloShitty> yes 12:58 < HelloShitty> it did 12:58 < HelloShitty> but I never created an RPC user 12:59 < HelloShitty> I'll show you, in a bit, my config file. Let me just finish and save it 12:59 < m-schmoock> not sure how it can run without RPC user :D it need to communicate to bitcoind somehow 13:00 < HelloShitty> ok, gimme a minute and I'll show you the command output without creating any user 13:00 < az0re> m-schmoock: From `lightning-cli help setchannelfee`: s/routed trhough the channel, an proportional fee of 1,000 satoshi/routed through the channel, a proportional fee of 1,000 satoshi/ 13:00 < HelloShitty> maybe it gives that output by default but not the output it should in case an RPC user existed 13:01 < m-schmoock> az0re: thx :D make a PR ? 13:01 < az0re> I would love to but GitHub will not allow me to sign up 13:01 < m-schmoock> indeed a typo of mine 13:02 < m-schmoock> lol? 13:02 < az0re> (using Tor Browser) 13:02 < m-schmoock> okay, thats insane 13:02 < m-schmoock> you will have you reasons, so Im fine 13:02 < az0re> It's Kafkaesque; the CAPTCHA fails on signup. I get the green check mark, then clicking "Join" gives me a CAPTCHA error. 13:02 < m-schmoock> -.- 13:02 < m-schmoock> az0re: if you dont mind ill fix the typo then 13:03 < m-schmoock> so, gotta go now. cu l8er gn8 13:03 < az0re> When I try to submit a webform support request, they use the same CAPTCHA. I can't submit the support form about the CAPTCHA failure because, get this, the CAPTCHA fails! 13:03 < az0re> Yes, go ahead 13:03 < az0re> Then, to top it off, when I email support@github.com, they decline my ticket and auto respond that they only accept support tickets via their web interface. 13:04 < HelloShitty> m-schmoock: whhen I start lightningd I see this in the very first line: 13:04 < HelloShitty> 2020-09-24T20:03:26.429Z INFO plugin-bcli: bitcoin-cli initialized and connected to bitcoind. 13:04 < az0re> That looks like it's working, thenm 13:04 < az0re> then* 13:04 < HelloShitty> :) 13:05 < HelloShitty> So, do you still think I need to create an RPC user? 13:05 < HelloShitty> getinfo command also works 13:06 < az0re> You see the block height in getinfo? 13:06 < az0re> Then it works 13:06 < HelloShitty> blockheight": 649815, 13:06 < az0re> But you should probably still set an RPC user/password 13:06 < HelloShitty> ok 13:06 < az0re> Yup 13:07 < HelloShitty> now I tried with the config file 13:07 < HelloShitty> but it says 13:07 < HelloShitty> lightningd: /home/narayan/.lightning/bitcoin/config line 4: network: not permitted in network-specific configuration files 13:07 < HelloShitty> I set it to network=bitcoin 13:07 < az0re> Remove that 13:07 < az0re> You're already in the bitcoin-specific config 13:08 < az0re> ~/.lightning/bitcoin 13:08 < HelloShitty> ahh, ok 13:08 < HelloShitty> I understand the context of the message now 13:13 < HelloShitty> az0re: does the config file accepts relative paths like ~/Downloads/bitcoin-20.1/bin/bitcoi-cli ? 13:14 < HelloShitty> I tried to point it to my current bitcoin binaries folder and datadir, but it says datadir doesen't exist 13:14 < HelloShitty> and tells me to test it with a command and an echo 'Hello World' at the end 13:14 < HelloShitty> and this command works 13:14 < t0mix> HelloShitty, you'll need to set rpcuser only if you run c-lightning under different user than bitcoind. otherwise, rpc cookie is used 13:15 < HelloShitty> I never set an RPC user neither on bitcoind nor in c-lightning 13:15 < t0mix> you don't need to.. as I said. 13:15 < t0mix> you run both under same user, right? 13:15 < HelloShitty> yes 13:15 < HelloShitty> that's only me on this computer 13:16 < HelloShitty> and both bitcoind and lightningd are runnig under the same Debian user 13:16 < t0mix> sure, but you can run multiple c-lightning instances.. :) 13:16 < HelloShitty> *user account 13:16 < HelloShitty> ok 13:16 < HelloShitty> But in this case, I'm running only one 13:16 < HelloShitty> so, no RPC user needed, as I understand 13:16 < t0mix> like, I'm using spark wallet, and for that I have dedicated user and c-ln instance 13:17 < t0mix> yup, not needed 13:17 < HelloShitty> but the problem is that paths in lightning config file are not being accepted 13:17 < t0mix> can't you use absolute paths? 13:17 < az0re> Why don't you just use absolute paths? 13:18 < HelloShitty> not working even with absolute paths 13:18 < HelloShitty> going to ouble check but I think paths are fine 13:18 < t0mix> anyway, what are you trying to set? =D 13:18 < HelloShitty> bitcoin-cli=/home/naarayan/Downloads/bitcoin-0.20.1/bin/bitcoin-cli 13:18 < HelloShitty> crap 13:18 < HelloShitty> I see an error now 13:18 < HelloShitty> lol 13:19 < t0mix> you don't need to specify bitcoin-cli .. or do you? =| 13:19 < HelloShitty> ok, good 13:19 < HelloShitty> I'm not using Debian repository version of bitcoin 13:19 < HelloShitty> I'm using the one I clone from github which is different 13:19 < HelloShitty> but I haven't uninstalled the repository one 13:20 < HelloShitty> so, binaries of bitcoin in PATH are older 13:20 < t0mix> I see.. then just uninstall and set your env 13:20 < HelloShitty> than the ones from github clone repository 13:20 < HelloShitty> yeah, I'll do that later, when I'm happy with 20.0.1 13:20 < t0mix> btw, you have that one from repository still running? (I guess you do) 13:20 < HelloShitty> no no 13:21 < HelloShitty> I'm only running the one from github clone folder 13:21 < HelloShitty> or better, let me check 13:21 < t0mix> how is your c-lightning running? without bitcoin-cli? am I missing something? =D 13:22 < HelloShitty> I have bitcoin-cli in that folder I pasted here 13:22 < t0mix> when you execute "bitcoin-cli" without defining full path.. it works? 13:22 < HelloShitty> ~/Downloads/bitcoin-20.1/bitcoin-cli 13:23 < HelloShitty> yes, but that's DEbian repo version 13:23 < HelloShitty> not the one from github clone 13:23 < HelloShitty> that's why I set those in config file 13:23 < t0mix> and config gave you error 13:23 < HelloShitty> so that it sees the github clone folder versions instead of Debian repos 13:24 < HelloShitty> I mistyped the folder path 13:24 < t0mix> ah 13:24 < HelloShitty> ./home/naarayan/.... instead of ./home/narayan/... 13:24 < HelloShitty> now it started 13:25 < HelloShitty> but I think I might still be running bitcoind from Debian repositories and bitcoin-cli from github folder 13:25 < HelloShitty> That's what I need to check 13:25 < t0mix> ps -ef|grep bitcoind 13:26 < HelloShitty> now I'm running github version of the deamon for sure 13:29 < HelloShitty> Now, when we start lightning deamon, we have the choice to run that bootstrap-node.sh script 13:29 < HelloShitty> it has a list of peers inside 13:29 < HelloShitty> Who are those peers? 13:29 < HelloShitty> Are like peers considered stable and known? Why are those peers included in that script? 13:33 < t0mix> I see the list, but no idea what is its purpose. to collect gossip data? 13:33 < t0mix> I'm sure rusty knows :D 13:34 < HelloShitty> ok, well, questions keep popping up. Hope you don't mind to answer whenever you can and know 13:35 < t0mix> very happy to answer.. I'm not a pr0 ninja turbo.. but one day.. ONE DAY! 13:35 < HelloShitty> So, only running lightning deamon, is not of a big deal for itself, right? 13:35 < HelloShitty> So, lightning needs to connect to other peers everytime we lauanch the deamon, yes? 13:36 < HelloShitty> Or by just running the deamon without running that bootstrap script, already helps the network in some way? 13:39 < t0mix> well, you need to build channels to make any difference to network. gossip data should be map of whole network (as far as I understand). .. so you only get the "map", which you can then use to find routes. 13:39 < t0mix> (might be wrong on that one. I have surface scratching knowledge here.) 13:41 < HelloShitty> So, what's abbout the nodes in 1ml.com site? 13:42 < HelloShitty> I'm actually wathicng a video of someone installing c-lightning and setting it up with spark and etc 13:42 < HelloShitty> and he shows this site where e can find nodes and other statistics about lightning network 13:42 < t0mix> 1ml.com is data extracted from gossip_store and dressed in nice graphic 13:43 < t0mix> you can use it 13:43 < HelloShitty> Which makes me think that we need to connect to one of those nodes to be able to do anything. Am I wrong? 13:43 < HelloShitty> I can I just setup a channel between you and me and eschange payments between us? 13:43 < HelloShitty> exchange* 13:43 < t0mix> yes, that's how it works 13:43 < HelloShitty> 2nd sentence of mine? lol 13:44 < t0mix> you can connect to my node, then fund the channel 13:44 < HelloShitty> or the first? 13:44 < HelloShitty> ah, that's what I thought 13:44 -!- fiatjaf [~fiatjaf@2804:7f2:2a85:2fc:ea40:f2ff:fe85:d2dc] has quit [Ping timeout: 260 seconds] 13:49 < HelloShitty> now, I'm going to try to connect it via Tor 13:49 < HelloShitty> bitcoin core is behind tor 13:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 13:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 14:28 -!- fiatjaf [~fiatjaf@2804:7f2:2a85:2fc:ea40:f2ff:fe85:d2dc] has joined #c-lightning 14:39 -!- kexkey [~kexkey@89.36.78.166] has quit [Quit: Scaling pentatonically] 14:41 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 14:51 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 14:54 < HelloShitty> I tried to connect to a node in 1ml.com site 14:54 < HelloShitty> bit it always says conenction refused 14:54 < HelloShitty> Is it me missing something? 14:56 < t0mix> have you tried more then 1 node? 14:57 < t0mix> maybe the node lightning is down atm 14:58 < HelloShitty> I tried ACINC 14:58 < HelloShitty> ACINQ I mean 14:58 < HelloShitty> Can try another one 15:00 < HelloShitty> nope 15:00 < HelloShitty> lightning-cli connect 030c3f19d742ca294a55c00376b3b355c3c90d61c6b6b39554dbc7ac19b141c14f 15:00 < HelloShitty> { 15:00 < HelloShitty> "code": 401, 15:00 < HelloShitty> "message": "52.50.244.44:9735: Connection establishment: Connection refused. " 15:00 < HelloShitty> } 15:00 < HelloShitty> gonna try a few more 15:01 < HelloShitty> My node is now behind tor 15:01 < HelloShitty> not sure that's a game changer or not 15:02 < HelloShitty> I am using non standard ports 15:02 < HelloShitty> I'm not using 9735, for instance 15:02 < az0re> What is your proxy config? 15:02 < HelloShitty> but I think that cannot prevent me from connecting 15:03 < HelloShitty> I have this: 15:03 < HelloShitty> proxy=127.0.0.1:9050 15:03 < HelloShitty> bind-addr=127.0.0.1:9735 15:03 < HelloShitty> addr=statictor:127.0.0.1:9051 15:03 < HelloShitty> always-use-proxy=true 15:03 < HelloShitty> but changed 9050 for another port 15:04 < HelloShitty> and also the 9735 is different 15:04 < az0re> Why did you change 9050? 15:04 < az0re> Is your tor listening on another port(s)? 15:04 < HelloShitty> because I usually change default ports to something else 15:04 < az0re> Also not sure about this: addr=statictor:127.0.0.1:9051 15:04 < az0re> Isn't 9051 the control port? 15:04 < HelloShitty> I took that from here: https://lightning.readthedocs.io/TOR.html 15:04 < HelloShitty> yes 15:05 < HelloShitty> 9051 is the control port for bitcoin core too 15:05 < HelloShitty> not sure this should/must be the same or different 15:06 < HelloShitty> I'm sorry, control port is also different 15:06 < HelloShitty> but it's working with bitcoin core 15:07 < HelloShitty> May I try to connect to your node or is that a security issue doing that with someone you don't know? 15:07 < az0re> I use command line arguments, but here's mine: /home/user/lightning/lightningd/lightningd --network=bitcoin --mainnet --bind-addr=127.0.0.1:9735 --announce-addr=:9735 --proxy=127.0.0.1:9050 --always-use-proxy true [...] 15:08 < HelloShitty> hum, I see 2 I don't have 15:08 < az0re> I guess there is some stuff you can do to tell tor to create a hidden service over the control port 15:08 < HelloShitty> --mainnet 15:08 < HelloShitty> and --announce-addr 15:08 < HelloShitty> but isn't mainnet the same as saying --network=bitcoin ? 15:08 < az0re> But I recommend just manually creating a hidden service and setting the announce address manually 15:08 < az0re> No, there is bitcoin testnet 15:08 -!- kexkey [~kexkey@89.36.78.166] has quit [Quit: Scaling pentatonically] 15:09 < HelloShitty> So, how would I add --mainnet to my config file? Do you know? 15:09 < az0re> Oh, I'm wrong 15:10 < az0re> From the --help: 15:10 < az0re> --mainnet Alias for --network=bitcoin 15:10 < az0re> So it's redundant in my case 15:10 < HelloShitty> ok 15:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:10 < HelloShitty> You want to try to connect to my node? To see if you can? 15:11 < az0re> Sure. /msg me the details 15:11 < HelloShitty> ok 15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:13 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 15:21 < t0mix> did you work it out? 15:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 15:29 < az0re> Nope... 15:31 < t0mix> az0re, any message in your logs? 15:32 < t0mix> why connection was refused 15:33 < az0re> Yes, but it includes his pubkey 15:33 < az0re> Hang on, let me sanitize it 15:35 < az0re> user@host:~$ lightning-cli connect 15:35 < az0re> { 15:35 < az0re> "code": 401, 15:35 < az0re> "message": "Error connecting to [redacted].lseed.bitcoinstats.com: Tor server reply: host unreachable. [redacted].lseed.bitcoinstats.com:9735: Connection establishment: Connection refused. Error connecting to [redacted].lseed.darosior.ninja: Tor server reply: connection refused. [redacted].lseed.darosior.ninja:9735: Connection establishment: Connection refused. " 15:35 < az0re> } 15:36 < darosior> Ouch my seednode is down. 15:38 < t0mix> az0re, that's the message you got when tried to connect to HelloShitty? 15:39 < t0mix> if he is using non standard LN port, pubkey won't be enough.. probably 15:39 -!- kexkey [~kexkey@89.36.78.166] has quit [Quit: Scaling pentatonically] 15:43 < az0re> Yup exactly 15:45 < t0mix> su just try "lightning-cli connect @: 15:49 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 15:53 < az0re> Yeah, next step 15:53 < az0re> His node is offline now, though 15:53 < az0re> Will try tomorrow 15:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 15:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 15:59 -!- kexkey [~kexkey@89.36.78.166] has quit [Quit: Scaling pentatonically] 16:00 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 16:05 -!- kexkey [~kexkey@89.36.78.166] has quit [Client Quit] 16:06 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning 16:30 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 16:43 < polydin> can anyone help with a simple call of multifundchannel ? 16:43 < polydin> having trouble with the array declaration 16:55 -!- kexkey [~kexkey@89.36.78.166] has quit [Quit: Scaling pentatonically] 17:00 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 17:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 17:33 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Read error: Connection reset by peer] 17:58 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has quit [Quit: Lost terminal] 18:17 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 18:21 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Quit: ZNC 1.7.4+deb7 - https://znc.in] 18:22 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #c-lightning 19:00 -!- kexkey [~kexkey@89.36.78.166] has joined #c-lightning 19:39 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 19:43 -!- ksedgwic [~ksedgwic@157-131-253-103.fiber.dynamic.sonic.net] has joined #c-lightning 19:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 19:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 20:15 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:26 -!- niftynei [~niftynei@104.131.77.55] has quit [Ping timeout: 256 seconds] 20:34 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 20:50 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 20:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 21:37 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack] 22:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 22:55 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 23:15 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.] 23:16 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 256 seconds] 23:23 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 23:28 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 23:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Quit: Gone frying asparagus or my Windows had a BSOD] 23:45 < jasan> cdecker: Everything is fine. Thank you. I just ran out to polyphonic choir rehearsal yesterday. 23:51 < jasan> m-schmoock: Yes, everything is fine. I apologize for running away like that so I left you wondering. It was a good exercise anyway as doung the combing of SQL statements I found one generally applicable axiom (which goes in line with "little change") and it was DO NOTHING :-D actually one of examples which I wrapped because it is longer than 80 chars. I was surprised to see it even here. There 23:52 < jasan> are now people with T-shirts which say "Just do nothing". All is well. Thank you. 23:52 < zmnscpxj_> ? 23:54 < m-schmoock> (: 23:54 < zmnscpxj_> ! 23:57 < jasan> dr-orlovsky: Thanks for funding a channel. I am wondering about a 1ml.com-like for signet. Anyone has some code ready to be run? --- Log closed Fri Sep 25 00:00:31 2020