04:31:21 <kayabaNerve_> Not sure how much the community will like this, but if there's any Python developers here, this may be useful. https://github.com/kayabaNerve/cryptonote-library
04:32:17 <kayabaNerve_> It's a CN/Monero library I wrote last year and just got permission to open source. It handles TX structure/serialization, keys, payment ID and subaddresses, commitments, finding spendable transaction outputs, encoding/decoding the extra field... only calls out to C for key image creation/RingCT signing.
04:33:09 <kayabaNerve> Unfortunately, it was built for Monero v12, so it's been unusable for a few weeks now. May still be a good look at the crypto/potential base to build off of if anyone needs a Wallet + WatchWallet solution?
04:33:30 <kayabaNerve> But just using the wallet2 API may be better for a long term solution. Not sure. Just wanted to post about an alternative.
08:51:41 <dEBRUYNE> kayabaNerve: Do you plan to update it to make it compatible with CLSAG?
15:11:15 <kayabaNerve> dEBRUYNE: Not really. If it only requires updating the struct/serialization code, as in, the signing API is the same than maybe? I think it may be like that, yet I haven't touched this code in a whille and didn't feel like stting up the test environment to find out to be honest
15:12:35 <moneromooo> From the looks of it, it does not include tx validation. Is that correct ?
15:22:10 <kayabaNerve> moneromooo: It isn't a light wallet, as it needs to be paired with a trusted RPC connection. That said, it does fully verify transaction outputs.
15:22:43 <kayabaNerve> As in, it discovers spendable transactions, rebuilds commitments, handles miner outputs and regular outputs...
15:23:03 <kayabaNerve> THe distinction is it doesn't do any chain inclusion proofs/SPV tracking
15:23:14 <kayabaNerve> Or were you thinking of something else?
15:27:02 <moneromooo> I was thinking of rct validation and BP/Borromean validation. As in, verifying commitments sum to 0, that kind of thing.
15:35:40 <kayabaNerve> Got it. That was something I never really considered tbh. Always would've thought as that as out of scope
16:33:25 <moneromooo> Well, you get to define the scope of your own software/
16:34:14 <moneromooo> I think having an independent progam to verify rct would be good, to detect whether there is a bug in the monero implementation.
16:34:33 <moneromooo> Long, longstanding wish list :)
16:35:41 <hyc> why would you trust the independent impl more?
16:35:49 <Mmmmmmmmmm> I have a voice now?
16:35:53 <Mmmmmmmmmm> Oh, cool.
16:39:10 <kayabaNerve> moneromooo: Ha! I didn't, actually :P It was a contract for a third party
16:39:17 <moneromooo> You would likely not.
16:39:21 <kayabaNerve> But yes, now that it's FOSS hosted by me, I do.
16:39:28 <kayabaNerve> hyc: The point is cross checking.
16:39:43 <moneromooo> A difference tells you you need to look into it, not trust any one more,
16:39:54 <kayabaNerve> So if one acts up, you can figure out which one it is. You can trust the independent impl is the better one, but you can debug to find out exactly.
16:40:15 <kayabaNerve> I'll let moneromooo cover it :P Sorry for intruding.
16:40:53 <kayabaNerve> I actually did look for any other RCT libraries. Using the internal C API was annoying to figure out
16:41:21 <kayabaNerve> All I found was some incomplete Python code from before the v12 testnet. Pretty sure it was for MLSAG though.
16:41:35 <kayabaNerve> (not that it'd be fast enough for anything beyond pure cross testing anyways)
16:43:05 <kayabaNerve> Even my code scrapes the threshold of tolerable speed, and that's for small-medium sized services.
17:42:05 <gingeropolous> random idea. for d++ stemming, perhaps a node should prefer sending to nodes in its "--add-priority-node" first
17:42:12 <gingeropolous> it sort of build on the web of trust idea
17:42:34 <gingeropolous> presumably, you've added these peers because you trust them over the random collection provided by the network
17:43:10 <hyc> seems that's more recognizable than a random pick
17:43:16 <gingeropolous> and you can leverage that reciprocal implied trust, so if A trusts B, then B can somehow.... no that won't do
17:43:56 <gingeropolous> well, if A trusts B, and A always sends to B, and if B is connected to all AHP, i guess it fluffs anyway
17:44:09 <gingeropolous> from A
21:39:23 <binaryFate> v0.17.1.3 binaries are out on getmonero.org, great job good people
21:42:35 <M5M400> ++
21:53:33 <selsta> ideally all seed nodes would update to v0.17.1.3 and apply this block list https://gui.xmr.pm/files/block.txt with --ban-list flag
21:56:03 <Inge-> I guess it would be helpful for as many nodes as possible to update to that version so fewer one-hop-away-from-seed nodes connect to AHPs?
22:22:27 <selsta> should it be possible to run --anonymous-inbound without --tx-proxy?