Björn Tackmann
Björn Tackmann
In the Interface Spec meeting, we suggested that we may want to mark this feature as experimental.
Is this already in production? Then this would be a breaking change.
You're right, thanks for pointing this out!
As described above, we suggest keeping the old semantics (specifying a limit on allocated heap memory rather than "remaining" memory), in which case the scheduling is also much clearer (just...
Current state from the interface spec meeting: Likely the best path forward is wait for the replicated query work to mature, and switch the ICRC-21 methods to query mode. For,...
Closing this for now since we want to wait for a more secure query mechanism – this should not go through update.
Overall, looks good to me. I wonder whether we shouldn't move more formal parts from the [feature docs](https://2xf6o-laaaa-aaaam-abrla-cai.icp0.io/docs/current/references/t-schnorr-how-it-works#ed25519-hierarchical-key-derivation) here into the spec?
> Wouldn't it be possible to have an API where a first call returns `R` (the commitment to randomness) to the caller. Then the caller does the hashing himself and...
One additional aspect that adds a bit of complexity is key derivation for different canisters. So the outstanding signatures may not only apply to a single canister as in the...
Yes makes sense. As just discussed in the interface spec: - General API - Bitcoin - Provisional seems the right thing to do.