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 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 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 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 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