I&#x27;m conflicted on Axolotl. For every layer of security you add, you increase the odds of someone doing something careless (this[1] is way more common than you&#x27;d think).<p>Key-leak healing is an interesting function out-of-the-box, but if your priv key gets uploaded accidentally, odds are so did your DH Identity&#x2F;Ratchet&#x2F;Chain keys as well, effectively rendering you &quot;fully compromised&quot;. It only offers protection in an instance where you keep your keys compartmentalized.<p>Is there a general consensus within the crypto community as to whether a) this is conceptually sound, and b) if there&#x27;s an audited implementation? It&#x27;s so so easy to mess up and have that error be overlooked (i.e. the OpenSSL debacle), which makes me want to just stick with the tried and true GPG DH&#x2F;ELG setup with PKI and revocation. Definitely a real interesting project to watch and a real interesting take on perfect-forward secrecy though! Thanks for your feedback. If you see this, read my other post in this thread and e-mail me, I&#x27;d love your feedback.<p>[1]<a href="http:&#x2F;&#x2F;rdist.root.org&#x2F;2008&#x2F;02&#x2F;05&#x2F;tlsssl-predictable-iv-flaw&#x2F;" rel="nofollow">http:&#x2F;&#x2F;rdist.root.org&#x2F;2008&#x2F;02&#x2F;05&#x2F;tlsssl-predictable-iv-flaw&#x2F;</a>