officex
February 22, 2025, 7:35am
5
Yes we definately want (1) pass in timestamp to limit calls, (2) we do provide regular API keys, the signature is just a “default auth” for the initial session when there is no api-key generated yet.
Do you know if we should be using the ic-validator-ingress-message crate, or is it just as appropriate to use the lightweight standalone-sig-verifier ? (we are using standalone identities)
we’ve encountered another problem here. ic-validator-ingress is indirectly using the ic0 api somewhere (probably not called at all). This was fine for us on x86 as it doesn’t try to link to the “ic0” module, but is a problem if we use it in apps targeting the wasm32 platform while not being a canister, as it seems to be forcing the linking of this module.
More specifically this is the error that I get: "ic0": module is not an object or function if we try to use it in a wasm32 app
EDIT: minimal…