New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rework codecs & extrinsics for poc-3 compatibility #161
Comments
Yeah, I'll work on this. |
This could be useful - #149 No need to use anything in there, but it is probably worth a look - it makes some attempt for saner Json/u8a encoding/decoding. Either way, the work here will replace the above, so it will never be merged as-is, nor make much progress form where it is. Feel free to adapt, copy or completely ignore as a science experiment. |
New extrinsics format for poc-3 - https://github.com/paritytech/wiki/blob/master/Extrinsic.md The basics are the same, version header added, order somewhat changed. More importantly, it is now documented. |
From Gav - "
" |
UInt encoding paritytech/substrate#847 |
Putting here to have a written record of what's been discussed on Riot. It must be done in the following order.
interface Codec {
static decode(input: any): any;
encodedLength: number;
toHex(): string;
toJSON(): any;
toString(): string;
toU8a(): Uint8Array;
} |
Add toString() - this is quite useful in display (UI only uses this - although I suppose it doesn't need to be on the interface since it is part of base "Object") |
@amaurymartiny what branch will you be using to work on it? |
@ltfschoen It's not a one branch effort, Jaco and I have been creating small PRs all the way to slowly refactor all stuff, see all the linked PRs above. All PRs that are related to this refactoring have a "Related #161" message. |
Closing. Feature-complete. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
I cannot put it more succinctly :)
:code
, basically all these Extract well known keys into a single place paritytech/substrate#764)cc @amaurymartiny :)
The text was updated successfully, but these errors were encountered: