DataStore/jupiter-perpetuals-solana-onchain-data

Jupiter Perpetuals Historical Data Sample

This dataset has 32,353 rows of decoded Jupiter Perpetuals data from Solana mainnet, split across 40 tables (39 instruction tables and 1 event table). It covers slots 416,077,271 to 451,891,223, from 27 April 2026 to 30 September 2026 (UTC). Each table is cut to at most 1,000 rows, so busy tables cover minutes of that window while rare instructions stretch across months.

It's a free sample from datastore.sh. The full Jupiter Perpetuals dataset is delivered as partitioned Parquet with typed schemas, manifests and checksums, covering recent history or the full chain history.

What is Jupiter Perpetuals?

Jupiter Perpetuals (Jupiter Perps) is a decentralized perpetual futures exchange on Solana. Traders open leveraged long or short positions on assets such as SOL, ETH and BTC against the JLP liquidity pool, and keepers execute position requests on-chain. Program ID: PERPHjGBqRHArX4DySjwM6UJHiR3sWAatqfdBS2qQJu.

Files

There are two kinds of data here: instructions (what a wallet or keeper asked the program to do) and events (what the program logged when it ran).

jupiter_perpetuals_cpi_event.csv (1,000 rows, 12 columns) Events emitted by the program via self-CPI (trade, liquidation, pool events) with decoded payloads. 2026-09-05 12:55:57 to 2026-09-05 13:13:31 UTC.

jupiter_perpetuals_decrease_position_with_internal_swap.csv (1,000 rows, 30 columns) Keeper-executed decreases that swap collateral to the requested output token. 338 distinct owner, 3 distinct custody, 3 distinct custody_doves_price_account. 2026-09-20 16:38:53 to 2026-09-29 13:12:13 UTC.

jupiter_perpetuals_decrease_position_with_tpsl_and_internal_swap.csv (1,000 rows, 27 columns) TP/SL-triggered decreases with collateral swap. 504 distinct owner, 3 distinct custody, 3 distinct custody_doves_price_account. 2026-09-26 13:27:10 to 2026-09-30 06:25:36 UTC.

jupiter_perpetuals_increase_position_pre_swap.csv (1,000 rows, 19 columns) Pre-swap step before a keeper increases a position with a different input token. 4 distinct collateral_custody, 4 distinct collateral_custody_token_account, 2 distinct keeper. 2026-07-31 18:55:08 to 2026-09-29 16:43:56 UTC.

jupiter_perpetuals_increase_position_with_internal_swap.csv (1,000 rows, 28 columns) Keeper-executed increases that swap the input token into collateral. 4 distinct collateral_custody, 3 distinct custody, 3 distinct custody_doves_price_account. 2026-09-24 08:49:58 to 2026-09-30 06:20:36 UTC.

jupiter_perpetuals_instant_increase_position_pre_swap.csv (1,000 rows, 26 columns) Pre-swap step for instant position increases. 457 distinct owner, 4 distinct receiving_custody, 4 distinct receiving_custody_doves_price_account. 2026-09-29 01:35:45 to 2026-09-30 07:00:47 UTC.

All 40 files

File	What it contains	Rows	Columns
jupiter_perpetuals_add_custody.csv	Admin adds a new custody (supported asset) to the perpetuals pool	1	34
jupiter_perpetuals_add_liquidity2.csv	Deposits into the JLP liquidity pool (mints JLP tokens)	1,000	25
jupiter_perpetuals_borrow_from_custody.csv	Borrowing assets from a pool custody against a borrow position	1,000	21
jupiter_perpetuals_close_borrow_position.csv	Closing of a borrow position	1	13
jupiter_perpetuals_close_position_request2.csv	Keeper closes a position request and refunds its token account	1,000	20
jupiter_perpetuals_close_position_request3.csv	Keeper closes a position request (v3, custody-aware)	18	21
jupiter_perpetuals_cpi_event.csv	Events emitted by the program via self-CPI (trade, liquidation, pool events) with decoded payloads	1,000	12
jupiter_perpetuals_create_decrease_position_market_request.csv	User requests to reduce or close a position at market price	1,000	30
jupiter_perpetuals_create_decrease_position_request2.csv	User requests to reduce or close a position (market, limit or TP/SL)	1,000	35
jupiter_perpetuals_create_increase_position_market_request.csv	User requests to open or increase a leveraged position at market price	1,000	30
jupiter_perpetuals_decrease_position4.csv	Keeper-executed position decreases / closes	1,000	26
jupiter_perpetuals_decrease_position_with_internal_swap.csv	Keeper-executed decreases that swap collateral to the requested output token	1,000	30
jupiter_perpetuals_decrease_position_with_tpsl.csv	Take-profit / stop-loss triggered position decreases	1,000	24
jupiter_perpetuals_decrease_position_with_tpsl_and_internal_swap.csv	TP/SL-triggered decreases with collateral swap	1,000	27
jupiter_perpetuals_deposit_collateral_for_borrows.csv	Collateral deposits backing borrow positions	1,000	22
jupiter_perpetuals_increase_position4.csv	Keeper-executed position opens / increases	1,000	24
jupiter_perpetuals_increase_position_pre_swap.csv	Pre-swap step before a keeper increases a position with a different input token	1,000	19
jupiter_perpetuals_increase_position_with_internal_swap.csv	Keeper-executed increases that swap the input token into collateral	1,000	28
jupiter_perpetuals_instant_create_limit_order.csv	Limit orders created and registered instantly via the API keeper	1,000	35
jupiter_perpetuals_instant_create_tpsl.csv	Take-profit / stop-loss orders created via the API keeper	1,000	35
jupiter_perpetuals_instant_decrease_position.csv	Instant market position decreases / closes	1,000	35
jupiter_perpetuals_instant_increase_position.csv	Instant market position opens / increases (long or short)	1,000	33
jupiter_perpetuals_instant_increase_position_pre_swap.csv	Pre-swap step for instant position increases	1,000	26
jupiter_perpetuals_instant_update_limit_order.csv	Limit order updates (size or trigger price)	1,000	21
jupiter_perpetuals_liquidate_full_position4.csv	Full liquidations of perpetual positions	1,000	21
jupiter_perpetuals_partial_liquidate_borrow_position.csv	Partial liquidations of undercollateralized borrow positions	733	19
jupiter_perpetuals_redeem_stake.csv	Keeper redeems staked SOL held by a custody	1,000	13
jupiter_perpetuals_refresh_assets_under_management.csv	Keeper refreshes of JLP pool assets under management (AUM)	1,000	12
jupiter_perpetuals_remove_liquidity2.csv	Withdrawals from the JLP liquidity pool (burns JLP tokens)	1,000	24
jupiter_perpetuals_repay_to_custody.csv	Repayments of borrowed assets back to the custody	1,000	19
jupiter_perpetuals_set_custody_config.csv	Admin updates to custody configuration (oracle, pricing, limits)	1	36
jupiter_perpetuals_set_max_global_sizes.csv	Keeper updates of the maximum global long and short size per custody	6	17
jupiter_perpetuals_set_token_ledger.csv	Token ledger snapshots used to measure swap output	1,000	10
jupiter_perpetuals_swap2.csv	Token swaps executed directly against the JLP pool	1,000	27
jupiter_perpetuals_swap_with_token_ledger.csv	Pool swaps using a token ledger for the input amount	1,000	26
jupiter_perpetuals_unstake.csv	Operator unstakes SOL from a stake account	10	16
jupiter_perpetuals_update_decrease_position_request2.csv	Updates to an existing decrease request (size or trigger price)	573	18
jupiter_perpetuals_withdraw_collateral_for_borrows.csv	Collateral withdrawals from borrow positions	1,000	21
jupiter_perpetuals_withdraw_fees2.csv	Keeper withdrawals of accrued protocol fees from custodies	1,000	18
jupiter_perpetuals_withdraw_stake.csv	Keeper withdraws deactivated stake back to the custody	10	20

Common columns

Every table starts with the same transaction-position columns, then the instruction's accounts and arguments.

Column	Description
ts	Block time, UTC
slot	Solana slot number
tx_index	Position of the transaction within the block
ix_path	Where the instruction sits in the transaction. [3,1] means inner instruction 1 of top-level instruction 3
sig	Transaction signature (base58). Join key across tables
r	Row disambiguator when one instruction decodes to several rows (usually 0)
program_id	Program that executed the instruction
decoder_revision	Commit of the datastore.sh decoder that produced the row
remaining	Extra accounts passed after the declared ones, as a JSON array
data	For cpi_event tables: the decoded event as JSON, keyed by event name

jupiter_perpetuals_cpi_event.csv holds these event types: PoolSwapEvent (461), ClosePositionRequestEvent (189), CreatePositionRequestEvent (117), InstantIncreasePositionEvent (76), InstantCreateTpslEvent (68), InstantDecreasePositionEvent (35), InstantCreateLimitOrderEvent (18), AddLiquidityEvent (16), DecreasePositionEvent (12), LiquidateFullPositionEvent (5), IncreasePositionEvent (2), RemoveLiquidityEvent (1).

How the files connect

• Same transaction: join any tables on sig, then sort by slot, tx_index and ix_path for execution order. 1,678 of 28,539 transactions in this sample appear in more than one table.
• Each file is its own cut of up to 1,000 rows, so their windows end at different slots and rows near the edges may have no partner in another file.

Load it

import pandas as pd
df = pd.read_csv("hf://datasets/DataStore/jupiter-perpetuals-solana-onchain-data/jupiter_perpetuals_cpi_event.csv", na_values=["\\N"], low_memory=False)
print(df.shape)

# or with the datasets library (one config per table)
from datasets import load_dataset
ds = load_dataset("DataStore/jupiter-perpetuals-solana-onchain-data", "jupiter_perpetuals_cpi_event", split="train")

Before you run numbers

• Amounts are raw base units of the custody token; USD values inside events are 6-decimal fixed point.
• Many instructions come in request/execute pairs. The *_request row is the user's intent and the matching execution row (or event) is what happened.
• cpi_event carries the richest records (IncreasePositionEvent, DecreasePositionEvent, LiquidateFullPositionEvent, PoolSwapEvent). Start there for PnL work.
• This is a short sample. Use it to learn the schema, write a parser or test a pipeline. For volume trends, backtests or anything time-series, you need the full history.

Questions you can answer

• How much notional is opened and closed per hour, long versus short, by custody (SOL, ETH, BTC)?
• How often are positions liquidated, and what fees and losses do liquidations realise?
• How much liquidity enters and leaves the JLP pool, and in which tokens?
• How do instant (keeper-signed) position changes compare with the request-then-execute flow?

Where can I get the full history?

The Jupiter Perpetuals dataset on datastore.sh ships as partitioned Parquet with typed schemas, manifests and SHA-256 checksums. You choose a recent window or full history and keep the files, with no API quota. The same catalog has Jupiter Swap, Raydium CLMM, Raydium CPMM, Orca Whirlpool, Pump.fun, Meteora DLMM. Browse the Solana catalog.

This sample is also on Kaggle.

License & citation

Licensed under CC BY 4.0. If you use this data, please credit and link to datastore.sh:

datastore.sh (2026). Jupiter Historical On-Chain Data (Sample). https://huggingface.co/datasets/DataStore/jupiter-perpetuals-solana-onchain-data