--- Log opened Tue May 23 00:00:09 2023
02:32 < real_or_random> stratospher[m]: want to re-review https://github.com/bitcoin-core/secp256k1/pull/1316 ?
02:34 < stratospher[m]> real_or_random: oh sure!
05:22 -!- DeanGuss [~dean@user/deanguss] has quit [Excess Flood]
05:23 -!- DeanGuss [~dean@nonplayercharacter.me] has joined #secp256k1
05:23 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host]
05:23 -!- DeanGuss [~dean@user/deanguss] has joined #secp256k1
06:23 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
07:17 -!- roconnor_ is now known as roconnor
07:18 < roconnor> In the context of some of the fiat-crypto issues, what does proven correct assembly mean?  I know that the compcert folks have a model of assembly, but AFAIK it is proprietary.
07:26 < sipa> That's a good question. I don't know.
07:27 < sipa> Perhaps CryptOpt has its own model of assembly semantics, which would be reasonable as it only supports a tiny number of instructions anyway.
13:37 -!- achow101 [~achow101@user/achow101] has quit [Ping timeout: 240 seconds]
13:45 -!- achow101 [~achow101@user/achow101] has joined #secp256k1
22:05 -!- preimage [~halosghos@user/halosghost] has quit [Ping timeout: 240 seconds]
--- Log closed Wed May 24 00:00:10 2023