PropAMM Bundle Submission
Proprietary AMMs (PropAMMs) let market makers stream live, signed price quotes directly to block builders, keeping on-chain pricing in step with real-time market conditions rather than relying on a passive bonding curve. This means tighter spreads and better execution for trades routed through PropAMM liquidity, compared to trading against a stale pool price.
pamm_submit_bundle is a dedicated endpoint for submitting bundles that route through PropAMM liquidity. It gives traders and searchers a direct path to this liquidity through bloXroute's Cloud API, with the same fast, reliable bundle delivery you get from blxr_submit_bundle today.
This service is available via Cloud API only.
Submission Endpoint
Method:
pamm_submit_bundleEndpoint:
api.blxrbdn.comRequest type:
HTTPS,WSS
Parameters
transaction
A list of raw transaction bytes without a 0x prefix.
block_number
Block number of a future block to include this bundle in, in hex value. For traders who would like more than one block to be targeted, please send multiple requests targeting each specific block.
min_timestamp
[Optional] The minimum timestamp that the bundle is valid on, an integer in unix epoch format. Default value is None.
max_timestamp
[Optional] The maximum timestamp that the bundle is valid on, an integer in unix epoch format. Default value is None.
reverting_hashes
[Optional] A list of transaction hashes within the bundle that are allowed to revert. Default is empty list: the whole bundle would be excluded if any transaction reverts.
dropping_hashes
[Optional] A list of transaction hashes within the bundle that can be removed from the bundle if it's deemed useful (but not revert). For example, when transaction is invalid. Default is empty list: the whole bundle would be excluded if any transaction fails.
uuid
[Optional] A unique identifier of the bundle. This field can be used for bundle replacement and bundle cancellation. Some builders like bloxroute, builder0x69 and flashbots support this field. After receiving a new UUID bundle, the builder would replace the previous bundle that has the same UUID. When the list of transactions is empty in new UUID bundle, the previous bundle associated with the same UUID would be effectively canceled. The response is empty/null instead of bundle hash when UUID is provided in the request.
enable_backrunme
[Optional, default: True] A boolean flag indicating if the bundle should be enrolled in the BackRunMe service.
backrunme_reward_address
[Optional] When the bundle is enrolled in the BackRunMe service, the transaction's from address collects backrun reward by default. The reward address can be overwritten with this parameter.
refund_recipient
[Optional] A string representing the wallet address to receive refund when priority_fee_refund flag is enabled. Users who do not want to specify the refund_recipient parameter must contact bloXroute to enable their refund address.
blocks_count
[Optional, default: 1] An integer that specifies the number of subsequent blocks that the bundle is valid for. The maximum value allowed for this parameter is 20. For example, when block_number parameter is 1000, and blocks_count is 3, then the current bundle would be processed with block numbers 1000, 1001, 1002.
Example
Cloud API
Response:
(Response will not include a bundle hash if UUID is included in request.)
Last updated