Method Signature
Parameters
The market application ID on Algorand
The escrow app ID of the existing maker order to match against
The Algorand address of the maker (order owner)
Quantity to match in microunits (e.g.,
1_000_000 = 1 share). Must not exceed the maker order’s unfilled quantity.Return Type
Whether the match succeeded. Always
true if the method completes without throwing an error.Array of transaction IDs from the match proposal (includes ALGO payment to maker escrow + match call)
The confirmed round number on the blockchain
Example
Behavior Notes
- Manual Matching: Unlike
createMarketOrder, which automatically finds and matches against multiple orders,proposeMatchrequires you to manually specify the exact maker order. - No Order Creation: This method does not create a new escrow for you. It’s typically used when:
- You want to match against a specific counterparty
- You’re building custom matching logic
- You’re integrating with external price feeds or strategies
- Transaction Structure:
- ALGO payment to the maker escrow (~2,000 microAlgos) to cover inner transaction fees
- Call to the matcher app’s
proposeAMatchmethod
- Fees:
- ~2,000 microAlgos ALGO payment to maker escrow
- ~10,000 microAlgos for the matcher app call
- Atomicity: The match proposal is atomic — either the entire trade settles or it fails.
- Complementary Matching: The matcher app handles complementary order matching logic (e.g., YES buy vs NO sell at complementary prices).
- Quantity Validation: The
quantityMatchedmust not exceed the maker order’s unfilled quantity, or the transaction will fail.
