<f​ineopal:nope.chat> Do the pool owners follow strict security measures? I don't think so.

<x​3cc:nope.chat> I think it depends, most of them are tech savvy I’m sure

<x​3cc:nope.chat> Also many hackers use pools for their botnets and maybe they already did some penetration testing lmao

<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

<x​3cc:nope.chat> In china*

<x​3cc:nope.chat> video_041fc17.mp4

<o​frnxmr:xmr.mx> Offtopic

<o​frnxmr:xmr.mx> This room is for core development, please use Monero

<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: monero-project/monero #8954

<k​eyur279:matrix.org> Hey everyone,

<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.

<k​eyur279:matrix.org> Issue: When using transfer command, Monero does:

<k​eyur279:matrix.org> Lock → creates transaction → tries signing it(for PoC the wallet does have my secret keys) → unlock

<k​eyur279:matrix.org> Then calls my tx_sign() with completely different UTXOs (always 2, vs variable size before unlock)

<k​eyur279:matrix.org> Device mode is correctly set to TRANSACTION_CREATE_REAL.

<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?

<k​eyur279:matrix.org> Any docs/resources on proper hardware wallet integration would be helpful too.

<k​eyur279:matrix.org> Hey everyone,

<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.

<k​eyur279:matrix.org> Issue: When using transfer command, Monero does:

<k​eyur279:matrix.org> Lock → creates transaction → tries signing it(for PoC the wallet does have my secret keys) → unlock

<k​eyur279:matrix.org> Then calls my tx\_sign() with completely different UTXOs it seems

<k​eyur279:matrix.org> Device mode is correctly set to TRANSACTION\_CREATE\_REAL.

<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?

<k​eyur279:matrix.org> Any docs/resources on proper hardware wallet integration would be helpful too.