05:49:48 <m-relay> <f​ineopal:nope.chat> Do the pool owners follow strict security measures? I don't think so.
06:05:27 <m-relay> <x​3cc:nope.chat> I think it depends, most of them are tech savvy I’m sure
06:05:55 <m-relay> <x​3cc:nope.chat> Also many hackers use pools for their botnets and maybe they already did some penetration testing lmao
06:07:26 <m-relay> <x​3cc:nope.chat> But still governments have publicly unknown exploits, and btw in for example you have to submit found vulnerability to authorities first within 48 hours
06:07:52 <m-relay> <x​3cc:nope.chat> In china*
06:11:02 <m-relay> <x​3cc:nope.chat> video_041fc17.mp4
06:12:56 <m-relay> <o​frnxmr:xmr.mx> Offtopic
06:13:24 <m-relay> <o​frnxmr:xmr.mx> This room is for core development, please use Monero
14:00:03 <m-relay> <s​gp_:monero.social> Heads up, not having a fix for the lookahead recently caused issues for another merchant. It would be really awesome if some fix for this could be implemented: https://github.com/monero-project/monero/issues/8954
22:31:00 <m-relay> <k​eyur279:matrix.org> Hey everyone,
22:31:02 <m-relay> <k​eyur279:matrix.org> Working on a PoC to add Monero support for a hardware wallet. I've implemented a device submodule inheriting from device_cold with basic functions (ki_sync, tx_sign, etc.) but I'm missing something.
22:31:04 <m-relay> <k​eyur279:matrix.org> Issue: When using transfer command, Monero does:
22:31:06 <m-relay> <k​eyur279:matrix.org> Lock → creates transaction → tries signing it(for PoC the wallet does have my secret keys) → unlock
22:31:08 <m-relay> <k​eyur279:matrix.org> Then calls my tx_sign() with completely different UTXOs (always 2, vs variable size before unlock)
22:31:10 <m-relay> <k​eyur279:matrix.org> Device mode is correctly set to TRANSACTION_CREATE_REAL.
22:31:12 <m-relay> <k​eyur279:matrix.org> What functions do I need to override so Monero treats my device as the primary signer and skips the software signing attempt during lock/unlock?
22:31:14 <m-relay> <k​eyur279:matrix.org> Any docs/resources on proper hardware wallet integration would be helpful too.
22:53:13 <m-relay> <k​eyur279:matrix.org> Hey everyone,
22:53:14 <m-relay> <k​eyur279:matrix.org> Working on a PoC to add Monero support for a hardware wallet. I've implemented a device submodule inheriting from device\_cold with basic functions (ki\_sync, tx\_sign, etc.) but I'm missing something.
22:53:16 <m-relay> <k​eyur279:matrix.org> Issue: When using transfer command, Monero does:
22:53:18 <m-relay> <k​eyur279:matrix.org> Lock → creates transaction → tries signing it(for PoC the wallet does have my secret keys) → unlock
22:53:20 <m-relay> <k​eyur279:matrix.org> Then calls my tx\_sign() with completely different UTXOs it seems
22:53:22 <m-relay> <k​eyur279:matrix.org> Device mode is correctly set to TRANSACTION\_CREATE\_REAL.
22:53:24 <m-relay> <k​eyur279:matrix.org> What functions do I need to override so Monero treats my device as the primary signer and skips the software signing attempt during lock/unlock?
22:53:26 <m-relay> <k​eyur279:matrix.org> Any docs/resources on proper hardware wallet integration would be helpful too.