ZeroSlip Data Stream now includes preBalances in every event. The field describes the balances of accounts involved before the event occurred and follows the same format as postBalances.
Having both states in an event makes it easier to inspect how the transaction affected those accounts. Developers can compare the incoming balances with the resulting balances while processing the rest of the event data.
The update adds another piece of transaction context to the stream, alongside its existing event details. See the Data Stream documentation for examples of the balance fields.
Original announcement
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 announced support for Raydium CLMM as its ninth supported protocol. The release adds CLMM trade events to the Data Stream and trading in those pools through the Trade API.
This broadens the pools developers can observe and interact with through ZeroSlip. The announcement also points to Raydium CLMM’s use for tokenized assets, making the integration relevant to applications following those markets.
Existing applications can review how the added pool type fits their event handling and trading workflows. See the Data Stream documentation for event formats and the Trade API documentation for request details.
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
ZeroSlip adds token creation for Raydium LaunchLab, including Stonkfun and other Raydium launchpads. This extends the existing ability to trade tokens from those launchpads.
A creation request uses "action": "create" with "pool": "raydium-launchpad", alongside the token’s details. ZeroSlip fills in the applicable launchpad rules, reducing the setup needed to work with an existing configuration.
Developers who want their own launchpad can use "action": "createConfig" to create a configuration instead. See the Raydium token creation documentation for the request format and configuration options.
Original announcement
ZeroSlip now supports creating tokens on Meteora Launchpad. Developers can select "pool": "meteora-launchpad" and choose a launchpad configuration through the same request-based workflow used for other supported token creation operations.
The release also adds createConfig for building a launchpad configuration. It lets developers set the quote mint, token supply, market caps and fees associated with tokens launched through that configuration.
For a combined launch flow, the configuration, token creation and initial developer buy can be included in one transaction. Visit the Meteora token creation documentation for the available request fields.
Original announcement
ZeroSlip introduces distributeFees for fee payouts on pump.fun and PumpSwap. The event identifies the payout type and includes the recipient wallets and their amounts in recipients.
The announced types cover token holders, wallets in a fee-sharing configuration, creator claims, and claims associated with X or GitHub account owners. This gives integrations a common event format for tracking the supported payout flows.
The September release also set 1 October 2026 as the scheduled retirement date for claimCreatorFees. Integrations using that older event should migrate their payout handling to distributeFees. See the Data Stream documentation for the updated format.
Original announcement
ZeroSlip Data Stream adds the createConfig event for Raydium and Meteora launchpads. It makes a new launchpad configuration visible before the first token is created on it.
The event provides information about fees before and after migration, locked liquidity and permissions affecting liquidity or token supply. Developers can use those details to inspect a launchpad’s rules earlier in its lifecycle.
That visibility supports more informed analysis, but a configuration event alone does not establish whether a project is safe. Read the Data Stream documentation to see the information exposed by createConfig and incorporate it into your existing checks.
Original announcement
ZeroSlip now supports percentage amounts for buys. An Actions request can acquire a quote token and then use "amount": "100%" to spend that token balance on the next purchase in the same transaction.
The update is useful for tokens paired with USDC or tokenized assets when you do not want to leave an intermediate quote-token balance behind. Other percentages are supported as well, including partial-balance amounts.
For a supported full-balance purchase, the emptied token account can be closed and its rent returned. The current Trade API documentation specifies that percentage buys apply to quote-token balances rather than SOL. See Actions for the combined-operation workflow.
Original announcement
ZeroSlip announced support for pump.fun’s holder rewards changes, while keeping older cashback tokens working. The update exposes holderRewardsRate and adds token creation controls through rewardFee and holderRewardsEnabled. For eligible quote mints other than WSOL or USDC, creators can configure additional fees of up to 3% for themselves or holders.
The release also moves ZeroSlip transactions to the V1 format. The announcement describes support for transactions up to 4 KB, allowing more operations to fit into a single Actions transaction, including buying a quote token before spending it on a target token.
Developers signing local transactions need a compatible Solana SDK. The update also fixes Data Stream and Trade API bugs, including failures affecting some Meteora DLMM and Pump AMM transactions. See the Trade API documentation.
Original announcement
ZeroSlip reported an approximately fifteen-minute Data Stream interruption on 2 September 2026. The team attributed the disruption to Solana and said it affected services beyond ZeroSlip.
The announcement confirmed that normal operation had resumed. It also noted reported improvements in Solana slot times and further reductions expected in the future.
For developers following the incident, the immediate update was that the Data Stream was available again. The reported network improvements were context for the announcement, rather than a guarantee about when individual transactions would execute.
Original announcement
ZeroSlip confirmed deployment of the previously announced quoteInPool correction. For pump.fun migrations with mayhemMode disabled, migration events now report approximately 67.4 SOL instead of approximately 85 SOL.
The correction aligns the migration value with the real quote liquidity present at that point. It follows the previous day’s explanation that the larger figure included virtual liquidity, while trade events already reported the actual balance correctly.
Integrations that assumed the old migration value should account for the corrected figure. Read the Data Stream documentation for the current event payloads.
Original announcement
ZeroSlip announced a correction to quoteInPool for pump.fun migrations where mayhemMode is disabled. The affected migration events reported about 85 SOL, while roughly 67.4 SOL was actually present in the pool at migration.
The announcement explains that the remaining approximately 17.6 SOL was virtual liquidity added gradually through boost mode during the first five minutes. Trade events already reported the real balance correctly; the discrepancy affected migration events.
The fix was scheduled for the following day, with migration events switching to the real balance. Developers relying on the old figure were given advance notice. The next announcement confirms the release.
Original announcement
ZeroSlip adds virtualQuoteInPool to Pump AMM Data Stream events and cuLimit to Trade API requests.
virtualQuoteInPool exposes the virtual quote liquidity associated with the pool. The announcement describes it as liquidity eligible for recovery after migration, giving integrations a field to read as that behaviour evolves.
cuLimit lets developers specify the transaction’s compute unit limit. Lowering it may improve transaction priority, but setting it too low increases the chance of failure because the transaction can exhaust its compute allowance.
The Data Stream and Trade API documentation cover the respective fields.
Original announcement
ZeroSlip Data Stream now includes decimals in every trade event. Previously, the field was provided in token creation events.
The addition puts token precision information closer to the trade being processed. Developers can read it alongside the event’s existing fields instead of relying only on the earlier creation event for that value.
This is a small schema addition with practical value for applications handling tokens with different decimal precision. It adds information to trade events without changing the announcement’s existing token creation coverage. Review the Data Stream documentation for examples of the updated payloads.
Original announcement
ZeroSlip restored the Historical Replay data affected by the 12 August service interruption. The team reported rebuilding the four hourly segments labelled 2026/08/12/06, 2026/08/12/07, 2026/08/12/08 and 2026/08/12/09.
The recovery announcement also introduced temporary fee relief for Trade API buy transactions through the stated deadline of 14 August 2026. That promotion applied to the incident response period and has ended.
Rebuilding the missing replay hours made the affected historical data available again after the earlier interruption.
Original announcement
ZeroSlip reported a service interruption lasting two hours and thirty minutes on 12 August 2026. The team attributed the outage to an automatic system package update that caused its server to crash and prevented connections to the service.
After restoring service, the team disabled automatic package updates to address the trigger identified in its announcement. ZeroSlip also apologised for the disruption to users and their integrations.
Later that day, the team announced restoration of the affected Historical Replay data and temporary fee relief for Trade API buy transactions.
Original announcement
ZeroSlip Data Stream adds breakdown to trade and liquidity events. The field exposes individual trades, including their traders and amounts, beneath the stream’s aggregated result.
A transaction can contain both buying and selling in the same pool. The main event can therefore show a net amount that is smaller than the total activity inside the transaction. breakdown preserves the detail needed to inspect those separate movements.
This is useful when examining trader activity or calculating fees associated with the underlying trades. Integrations can keep using the aggregated event while reading breakdown when they need more detail. See the Data Stream documentation.
Original announcement
ZeroSlip now supports Meteora DLMM pools in both the Data Stream and Trade API. Developers can receive trade events from these pools and use ZeroSlip to submit trades against them.
The release expands the protocols available through the same integration. It also adds access to activity in DLMM pools used for tokenized assets, alongside the other tokens traded through the protocol.
For applications already using ZeroSlip, the announcement introduces another pool type to account for when processing events or selecting a trading route. Review the Trade API documentation before adding Meteora DLMM support to your application.
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
ZeroSlip announced a performance update affecting both trade execution requests and streamed data. The team reported a 200 ms improvement for the Trade API and a 20 ms reduction in Data Stream latency.
The update also addressed recurring stream delays. According to the announcement, spikes previously appeared every one to two minutes and added roughly 50–300 ms of lag; the team reported removing that pattern.
These figures describe the improvements reported for this release. They are not a fixed response time for every request or network connection. Explore the Trade API and Data Stream documentation for integration details.
Original announcement
ZeroSlip issued a community notice about scammers impersonating its team. The announcement warns users about unsolicited requests for wallet private keys, money or visits to suspicious links.
When someone contacts you claiming to represent ZeroSlip, verify the contact through the official developer community. A familiar display name or copied profile picture is not enough to establish who is sending a message.
The notice concerns communication with people claiming to provide support. Keep it separate from the documented authentication methods used by the Trade API, and follow the official product documentation when configuring an integration.
Original announcement
ZeroSlip Data Stream now includes two additional fields in its events: programsUsed and addressLookupTables.
programsUsed identifies the program addresses involved in triggering an event, giving developers more context about the transaction’s route. addressLookupTables lists the address lookup tables used by the transaction to reference additional accounts.
The same announcement reminds developers who calculate prices themselves to use the supplied price field. This keeps integrations aligned with the pricing information ZeroSlip provides when upstream pool behaviour changes.
See the Data Stream documentation for event formats and examples.
Original announcement
ZeroSlip is inviting developers to submit projects for its partners page. The showcase helps visitors discover products built with ZeroSlip and gives builders a place to introduce their work to the community.
The announced submission process asks teams to add a clickable ZeroSlip link and logo to their main page, then provide a project name, a short description and an SVG logo. These details give the team what it needs to prepare a listing.
Visit the partners page to see the showcase, and use the official developer community to confirm the current submission contact.
Original announcement
Pump City is a playable demonstration of what ZeroSlip Agent can build beyond trading bots. For the launch showcase, the team used a single prompt to create a game and added the result to the ZeroSlip Agent website.
The demonstration includes generated voices for its characters. It gives visitors a concrete example of the agent’s coding capabilities and a way to explore a finished project, rather than relying only on a feature description.
You can try Pump City or watch the demonstration. The announcement describes the game as available across devices.
Original announcement
ZeroSlip Agent brings bot development and strategy testing into a hosted AI workspace. You can describe what you want to build, ask the agent to backtest a strategy, and have it write and run a bot using preinstalled ZeroSlip skills.
The agent runs on its own server, rather than requiring access to files on your computer. Three separate balances cover its operation: an hourly server balance, a balance for AI conversations, and a Solana wallet for the agent’s trading and other onchain actions.
The launch introduces a way to explore automated workflows without starting from a blank codebase. Visit ZeroSlip Agent to explore the service.
Original announcement