00:12:48 <cohcho> Is expected error for invalid transaction received from peer: "WARNING ringct  src/ringct/rctOps.cpp:442 ge_frombytes_vartime failed at 442" ?
00:15:03 <moneromooo> Not really. It means someone made an invalid tx, or there's a bug in verification. Hopefully the former, it's less bad.
00:16:18 <moneromooo> If you have the txid, you can check whether some block explorers have it. Hopefully everyone would reject it or noone would.
00:18:44 <cohcho> This one probably: 3680dbc064c9e6d8616435ad4888f342a14af3cfb69c23fb3f9f84c08d54b7da
00:18:55 <cohcho> print_pool_stats doesn't report failing txs
00:19:41 <moneromooo> They're rejected outright, never get into the txpool.
00:20:11 <moneromooo> I have this one in my pool.
00:20:24 <cohcho> There were two txs with many inputs
00:20:29 <cohcho> 1st one in block already
00:20:34 <cohcho> 2nd one is that^
00:20:37 <moneromooo> Is this tx in your txpool ?
00:20:40 <cohcho> error appeared after 2nd
00:20:42 <cohcho> yes, it is
00:20:51 <moneromooo> So it's unlikely it's this one.
00:20:55 <cohcho> s/error/warning/
00:21:16 <cohcho> yes, 2nd in block too now
00:21:16 <moneromooo> I have no ge_frombytes_vartime errors in my log (I'm been on level 2 for a while).
00:21:20 <cohcho> then I don't know
00:21:32 <moneromooo> So it's likely some other tx you rejected and that I did not see.
00:21:52 <moneromooo> Likely originating from one of your direct peers.
00:22:16 <cohcho> Anonimty set of bad tx is > 1 since txs are accumulated for validation
00:22:37 <cohcho> ok, i'll skip this warning
00:23:23 <moneromooo> I don't understand "Anonimty set of bad tx is > 1 since txs are accumulated for validation"
00:28:10 <cohcho> This tx is the only one mentioned in log within 10s window and isn't found now: c9206daea147b8dda33826d63a2de5ce7a3b8eb13e69b6a04ac270861ecd3ae1
00:28:19 <cohcho> ignore that poorly written sentence
00:28:53 <moneromooo> my daemon does not know that tx.
06:58:16 <ninjabz1> bing bang,
06:58:47 <ninjabz1> anyoone up for 2k ? https://www.reddit.com/r/Monerujo/comments/ejac5i/2k_bounty_on_github/
06:58:53 <ninjabz1> no autokick?
06:58:53 <ninjabz1> wow
06:58:54 <ninjabz1> )
07:16:25 <Inge-> no autokick.
07:16:31 <Inge-> We like to make it personal
07:18:11 <Inge-> ooof. Not sure if there is any practical way to brute force Crazypass.
07:18:42 <Inge-> I'll make a wild guess that you did not write down your seed.
09:28:55 <ErCiccione[m]> luigi1111: could you merge 6232 when you can? The binaries for GUI 0.15.0.3 have been on github for some days, but on the download page there are still the old ones.
09:29:15 <ErCiccione[m]> 6232 is binaryfate's gpg key
09:53:46 <ninjabz> @Inge- no seed, no the crazypass thing. and not sure why would i need to bruteforce it when i actually still have access to the phone via adb shell
09:53:56 <ninjabz> I mean, i dumped all the files off the phone
09:54:04 <ninjabz> and i can restore them back with twrp
09:54:21 <ninjabz> Im not trying to do it on other device
09:54:47 <ninjabz> simply, phone wouldnt load up anymore i had to go into twrp recovery
09:54:55 <ninjabz> to extract files, make full backup.
09:55:18 <ninjabz> twrp backup is like dd i guess, ) i can dd it back
09:56:07 <ninjabz> I m just trying to figure out how does the crazypass being made,, with the files i have from keymaster?
12:20:34 <selsta> ErCiccione[m]: v0.15.0.3 GUI is waiting for other reasons
16:46:51 <Snixer> When's the next dev-meeting? I tried checking on github but sadly i can't find a date
17:01:19 <binaryFate> Has anyone seen xiphon on IRC recently? I'd like to talk to them
17:56:23 <rottensox> Snixer: https://revuo-monero.com/issue-41.html
17:56:33 <rottensox> January 12, 2020 (Sunday) – 17:00 UTC
17:56:33 <rottensox> Dev Meeting - #monero-dev IRC channel
17:56:48 <rottensox> you can use revuo as your source for upcoming xmr-related meetings. they get posted there.
17:56:59 <rottensox> every thursday night i post them around and on /r/Monero.
17:57:05 <rottensox> there's a rss feed as well.
17:57:40 <sarang> MRL meetings have moved to Wednesdays
17:58:05 <sarang> So the meeting listed on the Revuo for 6 January @ 17:00 UTC will occur on 8 January @ 18:00 UTC
17:58:09 <sarang> and weekly thereafter
17:58:22 <rottensox> yes. rehrar is aware.
17:58:35 <sarang> roger, thanks
17:59:28 <sarang> The github meta issues and -lab topic should always show the correct next meeting datetime
18:27:37 <Snixer> rottensox: Thanks a lot! <3
18:32:13 <rottensox> xoxo Snixer <3.
19:59:41 <ErCiccione[m]> selsta: you mean for the binaries on getmonero? because i already see them on github
20:00:38 <selsta> only the tag binaries should be up soon^tm
21:38:38 <moneromooo> xiphon: binaryFate wanted to talk to you
21:38:57 <binaryFate> thanks moneromooo we've caught up
21:43:29 <xiphon> moneromooo: yeah, thanks, on it
22:02:53 <moneromooo> Anyone here runs a seed node apart from pony and ginger ?
23:33:49 <Inge-> What differentiates a seed node from a public full node?
23:34:07 <rottensox> it has a seed in it.
23:34:12 <rottensox> audience laughs.
23:35:42 <selsta> Inge-: Seed nodes are hardcoded in the code.
23:36:16 <selsta> They are used for initial connection unless you specify your own.
23:37:25 <Inge-> So basically it is just a full node where there is some understood commitment to keeping it operational, up-to-date and with a decent amount of available bandwidth?
23:38:51 <selsta> AFAIK yes.
23:50:00 <nonie> Every p2p project has this problem. When you start the client for the first time - the program knows nothing about the network and it needs a starting point. So it uses one or more of the hard coded seed ip addresses to connect to the network. Once it learned the network, there is no need for the initial seed.
23:53:31 <nonie> I like the way ratox solves the problem. The Makefile calls nodegen - a bash script to build the file nodes.h on the fly. nodgen just calls wget and awk to get a list of seed addresses.
23:53:47 <nonie> see https://git.2f30.org/ratox/log.html
23:55:40 <nonie> But maybe it is safer to have the seeds in the repository.
23:56:56 <hyc> wget from where?
23:58:12 <nonie> @hyc curl -s https://nodes.tox.chat/json  <- some url.
23:59:42 <hyc> yeah, just moves the problem