Enzo Haussecker

This is especially necessary due to #15

Owing to the fact that the canister's initializer, used for access control, does not persist across upgrades.

If you're looking for a better example that demonstrates how to build a canister for the Internet Computer in C, then I would recommend checking out https://github.com/enzoh/counter.

Absolutely agree! I have not had time to document this yet.

Rogue key attacks are guarded by the distinct message [requirement](https://github.com/enzoh/go-bls/blob/master/bls.go#L373). If you want indistinct messages, then that paper would be the way to go. I welcome a PR for this.

No, unfortunately, I never got around to wrapping up the implementation. If you submit a PR, then I will gladly review it. It should not be too difficult to implement....

@kritzcreek Can you implement it? I'm perfectly okay with swapping out for more efficient implementations as they become available. Right now I just need features.

@kritzcreek https://dfinity.atlassian.net/browse/SDK-790

I would prefer to not have more than one sort function in the API. So, if the preservation of these semantics is a requirement, which is perfectly fine, then lets...

The red-black tree module depends on the iterator module, which depends on this module, so no, I don't think that would work from a dependency standpoint.