--- Log opened Wed Nov 13 00:00:06 2019 02:53 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 276 seconds] 04:20 -!- jonatack [~jon@213.152.161.74] has joined #secp256k1 05:13 -!- jonatack [~jon@213.152.161.74] has quit [Quit: jonatack] 06:40 -!- jonatack [~jon@37.164.55.120] has joined #secp256k1 07:43 -!- jonatack [~jon@37.164.55.120] has quit [Ping timeout: 265 seconds] 08:23 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #secp256k1 08:33 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #secp256k1 08:33 -!- andytoshi [~apoelstra@wpsoftware.net] has quit [Changing host] 08:33 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #secp256k1 12:41 -!- reallll [~belcher@unaffiliated/belcher] has joined #secp256k1 12:44 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 12:52 -!- reallll is now known as belcher 19:16 < gmaxwell> nickler: instagibbs: re the coldcard attack y'all were discussing on twitter. If the user's wallet software's lookahead is 20 addresses, simply picking a key 10,000 addresses ahead is probably enough to make the keys essentially unavailable to most users. 19:19 < gmaxwell> If you want to be awful, make the nonce in your signature Enc(change_private_key, H(this_private_key|message)). :P Then knoweldge of that signature and the private key used to sign for it automatically tells you the private key of the change. :P 19:21 < gmaxwell> instagibbs: with the ledger workaround ... so like, uh, if I make 50k transations the ledger wallet will just stop working? --- Log closed Thu Nov 14 00:00:08 2019