-
Notifications
You must be signed in to change notification settings - Fork 169
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
define manifest data type for FIP 0031 #329
Conversation
FIPS/fip-0031.md
Outdated
The _Manifest_ data for version 1 (the only version currently defined) is a CID linking | ||
to an IPLD `Vector<(String, CID)>`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should formally define the order of this vector.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and, most importantly, in the system actor's state.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So whats the order? By type? Lexicographic?
I dont think it really matters all that much, but i am not opposed ti specifying it either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the bundler uses a BTreeMap, which orders by actor type -- this is perfectly reasonably I guess, should we make this the standard order?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to define the order by enum position.
* fip-0031: prepare for move to Last Call. * define manifest data type for FIP 0031 (#329) Co-authored-by: raulk <raul@protocol.ai> Co-authored-by: vyzo <vyzo@hackzen.org>
No description provided.