Skip to content

Parse consignments of rgb-lib f3975623 - #6

Open
nklyy wants to merge 4 commits into
mainfrom
feat/rgb-lib-f3975623
Open

nklyy wants to merge 4 commits into
mainfrom
feat/rgb-lib-f3975623

Conversation

@nklyy

@nklyy nklyy commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

rgb-lib f3975623 moves to new protocol crates (rgb-consensus 4a614b72, rgb-ops 9d831d2, rgb-schemas aa1e7fd) with an incompatible consignment layout, so the parser takes the same pins:

  • terminals are gone from the format, and from Info and the Go types;
  • the BFA genesis carries a root-level Unicode ticker, name, details and precision instead of an AssetSpec;
  • the mint metadata 1003 is beforeBlock;
  • propagate, transferInflation and transferLink transitions parse.

A V1 file written before the change now fails with a clear LegacyTerminals error. Fixtures are rebuilt with the new types: a propagated right, its mint, then a split and the burn in one bundle.

The protocol crates are private, so CI fetches them from our mirrors with the RGB_PRIVATE_DEPS_TOKEN secret.

nklyy added 4 commits October 29, 2026 13:09
rgb-lib f3975623 moves to new protocol crates (rgb-consensus 4a614b72,
rgb-ops 9d831d2, rgb-schemas aa1e7fd) with an incompatible consignment
layout, so the parser takes the same pins:
- terminals are gone from the format, and from Info and the Go types;
- the BFA genesis carries a root-level Unicode ticker, name, details
  and precision instead of an AssetSpec;
- the mint metadata 1003 is beforeBlock;
- propagate, transferInflation and transferLink transitions parse.

A V1 file written before the change now fails with a clear
LegacyTerminals error. Fixtures are rebuilt with the new types: a
propagated right, its mint, then a split and the burn in one bundle.

The protocol crates are private, so CI fetches them from our mirrors
with the RGB_PRIVATE_DEPS_TOKEN secret.
The consignment layout is the same as at f3975623: rgb-consensus
af0b751d, rgb-ops ed1d60d and rgb-schemas 641a06f change no encoding
and no schema id. Only the status JSON of validated containers renamed
its DAG key (dagDataOpt -> opsDag). The parser does not read it; the
contract fixtures are regenerated with it.

The synthetic BFA burn now carries real anchors: each witness tx spends
the seals its bundle closes and commits the bundle in an OP_RETURN, so
the pinned validation runs on it (new test). It follows the burn rgb-lib
1ae1c160 builds: a propagate of a genesis right, a mint spending a right
it made, then the split and the burn in one bundle.

The darwin_arm64 archive is left out: CI rebuilds all four.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant