Skip to content

crypto: re-export order signing types, make parse_addressable public - #5

Merged
erubboli merged 2 commits into
mainfrom
crypto-order-signing-reexports
Oct 5, 2026
Merged

erubboli merged 2 commits into
mainfrom
crypto-order-signing-reexports

Conversation

@erubboli

@erubboli erubboli commented Oct 5, 2026

Copy link
Copy Markdown
Member

Signing an order's fill/conclude/freeze inputs requires the order's balances via TxAdditionalInfo::with_order_info, but the SDK did not re-export OrderId, OrderAdditionalInfo or TokenId, and kept parse_addressable private (pub(crate)) — so downstream code could not build the additional info for signing a conclude-order input without depending on mintlayer-core directly.

  • re-export OrderAdditionalInfo next to TxAdditionalInfo
  • re-export OrderId and TokenId from crypto::types
  • make crypto::parse_addressable public (parse a bech32 address into any Addressable, e.g. an OrderId or TokenId)

cargo check --features crypto passes; a full conclude-and-recreate flow (build conclude input, re-create order output, TxAdditionalInfo, per-input witnesses, encode_signed_transaction, get_order_id) compiles against this branch.

Signing an order's fill/conclude/freeze inputs requires the order's
balances via TxAdditionalInfo::with_order_info, but the SDK did not
re-export OrderId, OrderAdditionalInfo or TokenId, and kept
parse_addressable private - so downstream code could not build the
additional info without depending on mintlayer-core directly.

- re-export OrderAdditionalInfo next to TxAdditionalInfo
- re-export OrderId and TokenId from crypto::types
- make crypto::parse_addressable public (parse a bech32 address into
  any Addressable, e.g. an OrderId or TokenId)
@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

✅ OpenCodeReview: Review complete: 0 finding(s) across 1 selected item(s).

Move the TokenId re-export to satisfy rustfmt's import ordering and
link the parse_addressable doc comment to types::OrderId, which rustdoc
-D warnings could not resolve from the crypto module scope.
@erubboli
erubboli merged commit 24080c0 into main Oct 5, 2026
19 checks passed
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.

3 participants