00:09:06 <bonedaddy> is it possible to do reserve proofs for multisignature wallets?
05:22:46 <happyfr0gg> Seems like Norton deleted monerod.exe. How do I restore it or where can I gt it?
06:35:28 <m2049r> vtnerd: thanks - i'll open an issue with the client logs. the only difference i could see from a normal transaction was the length of time it took for the tx to appear in print_pool_sh so maybe it's a combination of d++ & client stuff.
10:00:35 <coppa> has anyone looked into ledger live to add monero support here ?
11:28:50 <selsta> Ledger has released the new monero app
11:30:39 <sarang> Nice!
11:31:40 <dEBRUYNE> coppa: I think Ledger said they were exploring it, but no concrete plans
12:03:50 <selsta> hmm, having problems with Ledger app :/
12:04:00 <selsta> Error: Reason: invalid input
12:04:04 <selsta> any way to get more infos?
12:07:01 <sarang> ^ grydz_
12:11:29 <selsta> https://www.irccloud.com/pastebin/T5Sjfvu7/
12:11:30 <selsta> logs ^
12:21:24 <coppa> @dEBRUYNE ok, i'm cloning the project to see if it is soo complex than that
12:21:47 <coppa> may take time but worth looking at it never now if it is feasable
12:29:20 <dEBRUYNE> coppa: Do you intend to work on the integration yourself?
12:32:10 <coppa> i'm noob with crypto but work as react and fullstack engineer so will give it a try yes
12:32:43 <coppa> can't hurt trying anyway
12:32:44 <dEBRUYNE> I am certain it will be welcomed by the Monero community!
12:34:49 <sarang> selsta: running on current mainnet?
12:34:54 <selsta> testnet
12:36:23 <sarang> What app version?
12:36:29 <selsta> 1.7.0
12:58:41 <selsta> Stagenet (not on CLSAG yet) still works fine so Ledger has a bit of time to resolve this issue.
13:00:46 <sarang> I'll reach out to their team
13:01:27 <dEBRUYNE> Stagenet is not forked yet, right?
13:01:28 <selsta> I did comment here https://github.com/LedgerHQ/app-monero/pull/80#issuecomment-694842710
13:01:32 <selsta> dEBRUYNE: nope
13:03:55 <sarang> I emailed the project lead with your link selsta
13:04:42 <sarang> I wonder what happened?
13:05:01 <sarang> At least it was discovered with a month to go until the upgrade
14:15:02 <sarang> OK, the Ledger team lead responded and is informing developers (and pinged on the PR too)
17:19:49 <wgytfr78> My privats videos skype webcam 400gb links open in Tor Browser gg.gg/m7dgu
17:20:42 <sarang> no thanks
17:22:19 <binaryFate> Thanks to TheCharlatan and scoobybejesus, and selsta of course, for taking the time to deterministic build and PR to gitian :)
17:37:43 <rehrar> Sarang you don't have the 400gb to spare, huh?
17:37:54 <rehrar> All take up with blockchains.
19:12:53 <sech1> So I've updated to v0.17 and got this error in log: 2020-09-18 19:11:33.401 [P2P6]  ERROR   cn      src/cryptonote_basic/cryptonote_format_utils.cpp:811    wrong miner tx in block: <fb877ea3400f731c2b948e87655368f1c0486e3c114bb3f8f3839bec1b2f9596>, b.miner_tx.vin.size() != 1
19:13:02 <sech1> harmless, or?
19:16:58 <moneromooo> I've seen that reported before. Can you repro ? It'd be interesting to see the actual tx as json and the call stack.
19:17:37 <moneromooo> That hash doesn't seem to be a known tx or block.
19:17:53 <moneromooo> But it seems unlikely someone is trying to mine invalid txes...
19:17:55 <sech1> I don't know how to repro. I've just started it and got this ~1 minute later
19:18:17 <sech1> nothing in the log since then
19:19:24 <sech1> I was on v0.15.0.0 before that was running non-stop since 2019-11-09
19:19:27 <sech1> if that matters
19:21:58 <sech1> Maybe someone is trying to send invalid mined blocks? Is PoW checked after miner_tx?
19:28:29 <moneromooo> PoW goes first I think.
19:28:52 <moneromooo> Might be an idea to reorder checks carefully to have fast ones first.
19:32:06 <sech1> yes, in case someone is spamming blocks, easy checks must go first, PoW last
19:32:50 <sech1> still nothing more in log
19:59:44 <selsta> fluffypony: v0.17 should have fixed the tx sanity check error you had a couple weeks ago
19:59:58 <bonedaddy> any documentation about reserve proofs, how they work and stuff like that
20:00:12 <bonedaddy> doesnt seem to be on the monero docs as far as i can tell
20:04:18 <fluffypony> awesome tks selsta
20:07:13 <selsta> bonedaddy: https://github.com/monero-project/monero/pull/3027
20:09:48 <moneromooo> bonedaddy: try commit messages
20:11:10 <bonedaddy> nice this pull request looks good
20:11:10 <bonedaddy> thanks
20:15:45 <bonedaddy> > Also note that the signature file is not encrypted, so it's not meant to be shared publicly.
20:17:08 <bonedaddy> theres no information regarding this in the PR as far as I can tell, but the only reason you shouldnt share it publicly, would be if you dont want people to know your reserves? it doesnt seem like theres any "sensitive" information beyond a proof that shows address X holds Y funds
21:03:45 <dEBRUYNE> bonedaddy: I would deem that kind of information quite sensitive though
21:03:54 <dEBRUYNE> Especially if it is linked to, say, a nick
22:24:32 <bonedaddy> yea true, i guess it would be the context under which the information is disclosed. lets say im operating a public reserve of XMR that people can deposit funds into, posting public reserve proofs would allow you to do this without impacting the privacy of those that deposited funds?