Hans Larsen

The HTTP Query Spec has a `Token` value in it that needs to be either generic or `any`

6

From the point of view of the spec, this field's type does not matter; whatever the canister returns we send back in the same shape. But from the Candid file...

We have two structures; ```rust #[derive(Deserialize)] struct CallCanisterArgs1 { canister: Principal, method_name: String, args: Vec, cycles: u64, } // RUNNING OUT OF CYCLE #[derive(Deserialize)] struct CallCanisterArgs2 { canister: Principal, method_name:...

(a) `Nat` <: `Int`, (b) `(Nat|Int)N <: (Nat|Int)M` where N < M, and (c) text format should use smallest necessary type

15

Right now, if you pass in `0` as a number as is, the textual parser turns it into an `Int`. A better experience would be to have the textual parser...

It should work if using ic-ref as the backend. Yak shaving: - [ ] icx should be able to upload asset files and directories. Tests to do: - [ ]...

One example is https://github.com/dfinity/agent-rs/blob/next/ic-utils/src/interfaces/management_canister.rs#L25-L30 which cannot fail unless we refactor the bits below and break backward compatibility.

Validate Certification of Update Calls

3

Currently blocked by https://github.com/dfinity-lab/ic-ref/pull/90