ZeroSlip adds maxSlot and minSlot to Trade API requests. These parameters define slot boundaries for execution: a transaction fails if it lands after the maximum slot or before the minimum slot.
For applications responding to a streamed event, maxSlot provides a way to reject a trade that reaches the network too late for the intended window. minSlot provides the corresponding lower boundary.
A rejected transaction can still incur network and priority fees. These settings constrain when a transaction may execute; they do not guarantee that it will land inside the window. Read the Trade API documentation for the parameters.
Original announcement
ZeroSlip adds support for selling tokens that charge a transfer fee, including tokens used on platforms such as Stonkfun. The announcement reports a fix for failures that previously affected these sales.
The Data Stream also exposes the current transfer-fee configuration through transferFeeConfig. Its fields include feeRate and maximumFee, so integrations can inspect the configuration alongside their other event data.
This release brings the trading fix and fee visibility together. Applications handling these tokens can account for their transfer behaviour while processing market activity. See the Data Stream documentation for the payload structure.
Original announcement
Lightning transactions now accept an apiKey in place of the privateKey parameter. Developers can generate the key through the Trade API page and use it across trading, transfers, burns, token creation and other supported methods.
The change adds an optional authentication path; the existing parameter remains supported. ZeroSlip’s documentation describes the API key as an encrypted representation of the wallet’s private key, so it remains a sensitive credential that authorises wallet operations.
This update changes the credential supplied to Lightning requests. ZeroSlip still signs and broadcasts those transactions on your behalf. See the Trade API documentation for the setup flow.
Original announcement