You are reading content from Scuttlebutt
@Dominic %dBTvd7fCWqhHpA9wYKThoa+xGEp3R9UD+B+Jb1GqzFs=.sha256
Re: %b6nlgiAu3

@andrestaltz sounds like good progress! it wouldn't be too hard to reimplement the crypto as async, because the changes would be relatively contained. The biggest difference is asymmetric operations, symmetric crypto is fast anyway.

The parts that might go slow are verifying messages (on receive) and decrypting messages (although, I have changes planned that will make the asymmetric part cacheable.

Join Scuttlebutt now