You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order for XCQ to be generic, we need to have a meta type system to describe types. This is required to support chains with different type definitions for common operation. For example, the AssetId for a fungible extension could be a numeric ID (asset hub), or a xcm::Location (also asset hub), or an enum (Acala). Therefore we need to allow the chain to describe such type and then the client can decode the output correctly using the type information.
We could either build a simple one, or use scale-info
enumPrimitiveType{/// Unsigned Integer up to 128 bitsUnsigned,/// Signed Integer up to 128 bigsSigned,U256,I256,Bool,/// Vec<u8>Bytes,/// [u8; 32]H256,}structField{iden:Vec<u8>,type:Type,}structStructType{iden:Vec<u8>,fields:Vec<Field>,}enumVariantField{Unnamed(Vec<Type>),Named(Vec<Field>),}structVariant{iden:Vec<u8>,fields:Vec<VariantField>}structEnumType{iden:Vec<u8>,variants:Vec<Variant>}enumType{Primitive(PrimitiveType),Struct(StructType),Enum(EnumType),}
The text was updated successfully, but these errors were encountered:
In order for XCQ to be generic, we need to have a meta type system to describe types. This is required to support chains with different type definitions for common operation. For example, the AssetId for a fungible extension could be a numeric ID (asset hub), or a
xcm::Location
(also asset hub), or an enum (Acala). Therefore we need to allow the chain to describe such type and then the client can decode the output correctly using the type information.We could either build a simple one, or use scale-info
The text was updated successfully, but these errors were encountered: