00:50:46 @tevador It's an inherent byproduct able to be taken advantage of whenever. I was not proposing changes for it. I'd actually love if you reviewed the posited algebra, even if you don't sign off on implementing the feature + advertising it at this time. 00:51:26 Uhhh, since you're explicitly saying it require changes, where's the confusion? 00:51:27 Implementing OVKs requires changes, agreed. Having the door be open is inherent. 00:59:15 I'm not advocating we implement the new private key + wallet utils at this time. I'm noting it's made possible. 04:00:01 Added thoughts on forward secrecy. That'd appear possible *with a new opening proof*, which I don't want to get into now due to scope creep concerns. 06:37:52 Or can we get some comments and trying to get it merged and funded so we can get started? <= I don't think there is a need to wait until the next meeting 06:38:00 We can get comments in now already 18:42:50 Thank you tevador for the full write-up on Helios and Selene :D And apologies again if I made you feel like I was inviting scope creep (especially with the follow-up on forward secrecy I added) 18:44:30 I still haven't fully reviewed your write-ups about OVKs and forward secrecy. I'll try to leave some comments later. 18:45:36 I guess it's time for me to finally start learning rust. 22:45:19 "OVKs" would actually be a completely new wallet format with backwards compatible addresses: https://gist.github.com/kayabaNerve/0e1f7719e5797c826b87249f21ab6f86?permalink_comment_id=5014753#gistcomment-5014753