BRC-185: 1Sat Ordinal Collections - #13
Merged
Merged
Conversation
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
1 participant
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.
Define collection membership through either conforming MAP plus matching issuer Sigma, or an exact collection-origin spend. Clarify that parent-path items need neither item MAP nor Sigma, and missing Sigma evidence affects only the MAP path. Preserve original metadata types and required app/name/description; define exact rarity-percentage syntax and trait/attachment container boundaries. Reject mandatory legacy coercion. Musashi is cryptographic evidence, not positive metadata conformance. Keep static evidence and remove the executable review tool.
Validation: whitespace and relative file links checked. Collection, BAP, group and MAP revisions received independent read-only review; 15 local MAP checks pass for the revised semantics. Validation scripts are retained outside the BRC repository.
Targets master on the fork. No merge or upstream submission is requested. Resolve final upstream numbering and canonical dependency links during integration. BRC-178 settlement remains separately owned.