03:49:03 <br-m> <entropyhoover:matrix.org> For a small commit(around 100-200 lines diff), is it recommended to squash before pr, or squash only after pr is reviewed by someone?
03:50:47 <UkoeHB> Squash if you haven't submitted yet
08:32:17 <br-m> <entropyhoover:matrix.org> I am curious why does the monero official wallet did not directly integrate the atomic swap? Is there any regulatory risk of doing this?
08:35:47 <moneromooo> From afar, it looks like it doesn't belong. Same as the linux kernel doesn't include a text editor.
08:36:21 <moneromooo> It can be pretty useful, but it's just not what the kernel is. 
08:36:50 <moneromooo> Monero also doesn't include a marketplace, exchange, etc, for the same reasons.
08:37:09 <moneromooo> Someone else may build those, and there'll be choice (and, probably, danger).
08:38:38 <moneromooo> Then again, monero does support a couple hardware wallets with code that doesn't really feel like it belong.
08:39:39 <br-m> <entropyhoover:matrix.org> Feels like currently one the biggest problem for monero is scattered liquidity, it seems really difficult for new people(especially not tech savvy people) to figure out "how to reliably get monero".
08:39:52 <moneromooo> It also depends on how feasible it is to build something else that does what you want (here, atomic swaps) without needing changes to monero software.
08:40:25 <br-m> <maxxor:nitro.chat> @entropyhoover:matrix.org: there's sites like https://kycnot.me/?currency-mode=or&currencies=xmr
08:40:41 <moneromooo> Yes, the issue is also one of looking at things differently. We're hackers (in the original meaning), and people using monero are often not.
08:41:01 <br-m> <entropyhoover:matrix.org> I am thinking probably having an extension section in wallet that can optionally deploy those atomic swap in one click
08:41:15 <br-m> <entropyhoover:matrix.org> In this way it doesn't clutter the main wallet
08:41:35 <br-m> <maxxor:nitro.chat> a plugin system for the wallet? like it's implemented in electrum
08:41:37 <moneromooo> Plugins would be great. They also require a very clean and stable/versioned API, so a pretty mature architecture.
08:41:48 <moneromooo> And a lot of grunt work.
08:43:20 <br-m> <ofrnxmr:xmr.mx> also, regarding atomic swaps, who's implementation do you choose? they require third party services. regarding hardware wallets, jus yesterday tobtoht pushed for removing them from the core repo
08:43:25 <br-m> <ofrnxmr:xmr.mx> "I don't think we should allow third party hardware integrations in the main repo. We can set up a generic USB interface, and if a vendor wants to offer Monero support they can go ahead and implement that. We have given Trezor/Ledger way too much leverage over our code and dependencies."
08:44:08 <br-m> <ofrnxmr:xmr.mx> and regarding plugins, even feather wallet rejected an atomic swap plugin, and is moving towards removing 3rd party stuff from the wallet
08:45:21 <moneromooo> For trezor/ledger, I think two large parts for why they went in was "it seems very desirable to have" and "someone else is willing to do the work".
08:45:59 <br-m> <ofrnxmr:xmr.mx> you need a bitcoin etc wallet integrated with the GUI to add atomic swaps, and third party networking -- the scripting is done via messaging and on the bitcoin network. id say these reasons along are enough to disauqlify any idea of integrating them into a monero core wallet
08:46:47 <br-m> <ofrnxmr:xmr.mx> yeah, but now trezor is vibe coding 10000 lines of slop for their claude created interface
08:47:34 <moneromooo> That seems like self sabotage for something with the overarching goal is security.
08:47:47 <br-m> <ofrnxmr:xmr.mx> the number one commiter is claude
08:48:11 <br-m> <ofrnxmr:xmr.mx> https://github.com/trezor/trezor-suite/graphs/contributors?from=5%2F23%2F2026
08:48:37 <br-m> <ofrnxmr:xmr.mx> https://github.com/trezor/trezor-suite/pull/29235 slop
08:51:08 <br-m> <entropyhoover:matrix.org> > <@ofrnxmr:xmr.mx> also, regarding atomic swaps, who's implementation do you choose? they require third party services. regarding hardware wallets, jus yesterday tobtoht pushed for removing them from the core repo
08:51:08 <br-m> <entropyhoover:matrix.org> My thought are not really polluting the wallet by directly put their code in, but mostly get a separate menu, list out the mature implementations along some introduction, and a simple script to download and verify the bin, and can directly start the binary in that menu. So someone want an atomic swap can directly look at this  [... too long, see https://mrelay.p2pool.observer/e/k6vz2qULWFR1czg0 ]
08:53:00 <br-m> <ofrnxmr:xmr.mx> i widely disagree
08:53:26 <br-m> <ofrnxmr:xmr.mx> atomic swap platforms require wallets. eigenwallet and basicswap, for example, include monero wallets. they dont need to be in gui.
08:55:58 <br-m> <ofrnxmr:xmr.mx> and bitcoin definitely doesnt need to be in gui.
10:27:20 <br-m> <thomasbuilds:matrix.org> tevador / SChernykh for randomX, is src/aes_hash_rv64_zvkned.cpp meant to require the Zvkned intrinsics on every riscv64 build, even when the capability probes report the extension absent? It doesn't build with Ubuntu's riscv64 gcc 13.3.0.
10:29:18 <br-m> <ofrnxmr:xmr.mx> thats sect1 *
10:29:21 <br-m> <ofrnxmr:xmr.mx> sech1 ***
10:29:53 <sech1> It requires gcc 14, I think? Or gcc 15
10:29:59 <sech1> whichever supports zvkned properly
10:30:24 <sech1> https://github.com/monero-project/monero/pull/10038
10:30:32 <sech1> "RandomX bump requires GCC 14 bump on RISC-V platforms."
10:38:36 <br-m> <thomasbuilds:matrix.org> README still says gcc 4.8+/7+ and lists RISCV64 as validated
10:51:01 <br-m> <ofrnxmr:xmr.mx> why would it say otherwise
10:51:05 <br-m> <ofrnxmr:xmr.mx> randomx v2 isnt shipped?
10:51:29 <br-m> <ofrnxmr:xmr.mx> are you building v1.x?
11:01:41 <br-m> <thomasbuilds:matrix.org> master not v1.x, my bad on the README
18:38:41 <aps2026> is there a darkmode version of this chat?
18:42:38 <DataHoarder> that is totally up to you and your client
18:42:53 <DataHoarder> it's IRC, you can join it using any IRC client you prefer
19:23:34 <aps2026> any new updates on monero dev?