Hazel

I'm hitting this issue now too. I think what @bodily11 was referring to is the following. Take for instance ```candid type Balances = vec record { 0: text; 1: nat64;...

Actually, I think nested definitions might be okay. But, the numbered tuple format isn't ```candid // Doesn't work type BalanceTuple = record { 0: text; 1: nat64; }; // Works...

Updated the above to include `icrc12_subscribe` & `icrc12_unsubscribe` following feedback by rossberg [here](https://forum.dfinity.org/t/canister-events/18697/2)

Updated the above to remove `event_type : text;` following comments from [skilesare](https://forum.dfinity.org/t/canister-events/18697/3?u=hazel)

> I am wondering if Publisher should provide an interface to allow icrc12_servicediscovery that could return the name of the service provider along with the services offered. This would help...

Thanks for sharing here! Looks like some great ideas in here tbh.

> The canister interface is exposed via Candid, unfortunately, there isn't an ORB like naming service and we have no clue what the service would do when exposed. Ahh, I...

> This makes sense to leave space...but isn't having it be a variant enough? Can't it just be: It definitely could. But, consider the following situation: ```candid type Identity =...

@neeboo - That would definitely help. Sounds like we both had similar ideas with [authorization systems](https://github.com/DepartureLabsIC/dl_authorize). Personally, for this standard I think we should keep the core as simple as...

> Why is it important to have a canister wallet standard, as opposed to treating all wallets equally (canister and external)? Im not too familiar with the frontend wallet implementations...