update language to match new draft bcp on determinism#17
Merged
Conversation
darobin
approved these changes
Mar 9, 2026
Co-authored-by: Robin Berjon <robin@berjon.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The new BCP draft is here and simplified my thinking a bit. Main difference, other than dropping references to CBOR/core and language adjustments, is a little more clarity (thanks @vmx) on the application-level mitigations of type collisions that would arise translating from vanilla-CBOR to DAG-CBOR (historically handled by IPLD Schemata, potentially handleable by only encoding data wrapped in MASLs and/or described by ATP lexicons).