Understand
Registered Issuer M1 Flow
Why issuer material, AtomicBroker capacity, and signed swap payloads all have to line up.
The registered issuer path lets a swap settle with collateral whose lifecycle is controlled outside the pool. For the M1 demo path, the runtime has to bring issuer material into the swap in a way the hook can verify.
Moving Parts
- Issuer material proves the offchain issuer action the trade depends on.
- AtomicBroker inventory determines what can actually be delivered or redeemed.
- Quote server signatures bind the request to the deployed market and expiry.
- SDK helpers package hook data for the transaction.
Capacity Is Not Just Balance
Redeem capacity depends on broker balance and allowance. A balance-only check can overstate what the market can safely return.
Why The Flow Is Server Assisted
The browser should not hold signer keys or issuer credentials. It can request material and submit transactions, but the policy decision and signing boundary belong in a controlled service.
Source Files
src/AtomicBroker.solquote-server/src/quote.tssdk/src/registeredIssuer.tsscript/testing/request-usdm1-test-tokens.mjs