2460f745bc6fb79ab01967e55782b5a6688c3ea6
Despite being certain I was doing it wrong, the behavior I had implemented was to assign ownership of a key to the peer that knows the key's successor, not to the successor of the key.
Description
No description provided
Languages
Go
96.2%
Shell
3.5%
Dockerfile
0.3%