12:43:25 What is the point of not exporting a view key from a hardware wallet? 13:00:03 hardware wallets are for secure key management, so maybe you are concerned about the view key getting stolen 13:03:38 It should be protecting the view key from malware on your machine, right? 13:04:36 if that's where you would export it, I suppose so 13:08:32 I think it does not make any sense. You still have to do input selection, amount entering, amount masking, broadcasting, address entering and a bunch of other things on the host. 13:08:44 If you assume that your host is malicious, the host has all this information. 13:09:11 Which is effectively what you are trying not to expose by not exporting the view key. 13:09:59 Never mind that scanning will introduce a bunch of side channels that are probably hard to mitigate on the hardware wallet itself. 13:15:08 well once someone has your view key they will know about all the outputs you own indefinitely, and if they also know your normal address public spend key they can generate all your subaddresses which is quite useful for large-scale attacks 13:15:38 Besides, there is always the potential for the malicious host to embed metadata in the unsigned transaction that is not detected by the hardware wallet, but perfectly visible as a tag from the outside. 13:16:07 So the answer is forward secrecy in case you encounter a non-malicious host? 13:16:56 seems that way 13:18:04 forward secrecy for owned outputs, and lessens the chance a malicious host will learn your full set of subaddresses 13:30:00 seems like a high price to pay for that :/ 22:34:26 https://usercontent.irccloud-cdn.com/file/l2LEOaIJ/image.png 22:36:56 How malformed can a transaction be and still calculate a tx_ID? 22:39:09 Note that you can just move the attack back by one function. 22:39:10 i.e. start with a valid transaction, fix 2 of the 3 inputs, and find a collision one of the subfields like one-time address or public 22:41:44 (assuming the verification is being carried out by Core codebase) 22:44:05 If it parses, it should have a txid, whatever the semantics of what gets parsed. 22:44:33 Parses meaning it can find all the stuff it wants. Inputs, outputs, proofs, etc. 22:52:41 * Isthmus nods 22:52:42 Thanks 22:54:31 If my node hears a fluffy block containing a certain hash, but I don't receive a copy of the transaction, how long will my node wait before writing off the block as bad/ 22:54:36 s///? 22:54:39 dang 22:55:06 s/in ha/in transaction ha 22:55:06 Isthmus meant to say: If my node hears a fluffy block containing a certain transaction hash, but I don't receive a copy of the transaction, how long will my node wait before writing off the block as bad/ 22:57:00 It will not write it off as bad.