> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allium.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Solana Network Upgrade Changes (October 2026)

> Changes to Solana transfers, fees and staking commission that align our datasets with the 2026 network upgrades. Fees changed for new data on 13 October 2026 and fees history was backfilled on 19 October 2026; transfers changed for new data on 22 October 2026 and transfers history was backfilled on 23 October 2026; staking commission changed on 6 November 2026; the transfers preview tables are removed on 13 November 2026.

> [!WARNING]
>
> **Solana datasets are changing:**
>
> * **13 October (live):** fees, for new data
> * **19 October (complete):** fees, history backfill
> * **22 October (live):** transfers, for new data
> * **23 October (complete):** transfers, history backfill
> * **6 November (live):** staking commission
> * **13 November:** the two transfers preview tables are removed
>
> The preview table removal was planned for 30 October and moved to 13 November 2026. Query `solana.assets.transfers` before then.
>
> Most changes add rows or update values, and table names stay the same. Check the [table guide](#find-your-table) to see if your queries need to change.

> [!NOTE]
>
> **Changes since the September notice**
>
> Marked on this page with Added (not in the September notice) or Changed (in the notice, but different now).
>
> * **Timing:** fees went live for new data on 13 October, and the fees history backfill was completed on 19 October. Transfers went live for new data on 22 October, and the transfers history backfill was completed on 23 October.
> * **Transfers:** the scope is wider than the four p-token and prefund instructions in the notice.
>   * Rows are also added for nonce withdrawals, Token-2022 fees, `permissionedBurn`, confidential transfers, and lookup-table and program closes.
>   * A new `batch_instruction_index` column keeps each member of a `batch` instruction as its own row.
>   * New `transfer_type` values, including four for stake and vote movements in `solana.assets.transfers_and_stake`.
>   * `token_type` changes from `SPL-TOKEN` to `SOL` on native SOL rows.
> * **Fees:**
>   * Rows are added for transactions in the new Transaction V1 format (from 15 September 2026), which pay their priority fee without a ComputeBudget instruction.
>   * `priority_fee` and `base_fee` match the fees paid on chain.
>   * `effective_compute_unit_limit` matches the runtime's limit, which is more detailed than the rule in the notice.
> * **Staking commission:** `solana.raw.rewards.commission` is no longer backfilled. It stays `NULL` from 16 July 2026 and keeps its type, matching what the RPC returns.
>   * Commission is computed from on-chain data and stored in `solana.staking.rewards` (new `commission_bps` and `commission_percent`) and `solana.staking.validator`.
>   * A new table, `solana.staking.validator_commission`, gives each validator's commission per payout epoch.
>   * For 16 July – 8 September 2026, the `commissionBps` value the RPC returned is in `solana.raw.rewards._extra_fields`.
> * **Raw tables:** new keys in `_extra_fields`, live since 7 October.

## Timeline

These changes follow Solana upgrades between March 2025 and September 2026:

* p-token (SIMD-0266)
* Prefunded accounts (SIMD-0312)
* Commission in basis points (SIMD-0291)
* Custom commission collectors (SIMD-0232)
* Transaction V1 (SIMD-0385): a new Solana transaction format that sets its compute limit and priority fee in the transaction itself, instead of in separate ComputeBudget instructions
* Default compute-limit changes (SIMD-0170)

**1. 7 October 2026 — new raw fields (complete)**

Added New keys in `_extra_fields` on Solana raw tables. No action required. [Details](#extra-fields)

**2. 13 October 2026 — fees, new data (live)**

Updated compute limits and Transaction V1 rows in `solana.raw.fees` for new data ([Fees](#fees))

**3. 15 October 2026 — transfers history in preview tables**

Added The transfers history backfill, from December 2020, in two temporary tables in the Allium App and Explorer ([Preview the backfill](#preview-the-backfill))

**4. 19 October 2026 — fees, history backfill (complete)**

The fee changes applied to all historical rows of `solana.raw.fees` ([Fees](#fees))

**5. 22 October 2026 — transfers, new data (live)**

More value movements in the transfer tables, and a new `batch_instruction_index` column ([Transfers](#transfers))

**6. 23 October 2026 — transfers, history backfill (complete)**

The same changes applied to historical rows of `solana.raw.token_transfers`, `solana.assets.transfers` and `solana.assets.transfers_and_stake`, from December 2020 ([Transfers](#transfers))

**7. 6 November 2026 — staking commission (live)**

Changed Commission in `solana.staking.rewards` and `solana.staking.validator`. [Staking commission](#staking-commission)

**8. 13 November 2026 — transfers preview tables removed**

Planned for 30 October 2026 and moved to 13 November 2026.

`solana.assets.transfers_backfill` and `solana.assets.transfers_with_backfill` are removed. Query `solana.assets.transfers` instead ([Preview the backfill](#preview-the-backfill))

## Do I need to change anything?

If a Solana table isn't listed, **there are no changes**.

<table>
  <thead><tr><th>Table</th><th>Change</th><th>Action needed?</th></tr></thead>

  <tbody>
    <tr><td>`solana.raw.token_transfers`\
    `solana.assets.transfers`</td><td><ul><li>Rows added</li><li>New column `batch_instruction_index` Added</li><li>New `transfer_type` values Added</li><li>`token_type` on native SOL rows Added</li><li>Lower `closeAccount` amounts after `unwrapLamports` or `withdrawExcessLamports` Added</li></ul></td><td>**Only if** you:<ul><li>deduplicate by instruction position</li><li>filter on `transfer_type` or `token_type`</li><li>sum SOL from `closeAccount` rows alone</li></ul>[Transfers](#transfers)</td></tr>
    <tr><td>`solana.assets.transfers_and_stake`</td><td>Four new `transfer_type` values for stake and vote movements Added</td><td>**Only if** you filter on `transfer_type`\
    [Transfers](#transfers)</td></tr>
    <tr><td>`solana.raw.fees`</td><td><ul><li>`effective_compute_unit_limit` updated on all history Changed</li><li>Transaction V1 rows added from 15 Sep 2026 Added</li></ul></td><td>**Only if** you:<ul><li>use `effective_compute_unit_limit`</li><li>count rows</li></ul>[Fees](#fees)</td></tr>
    <tr><td>`solana.assets.transfers_w_tx_cols`\
    `solana.dex.trades_w_tx_cols`\
    `solana.dex.aggregator_trades_w_tx_cols`\
    `solana.decoded.instructions_w_tx_cols`</td><td>`priority_fee` includes Transaction V1 Added</td><td>No</td></tr>
    <tr><td>`solana.raw.rewards`</td><td>`commission` is `NULL` from 16 Jul 2026 Changed</td><td>**Yes, if** you read `commission`: use `solana.staking.rewards`\
    [Staking commission](#staking-commission)</td></tr>
    <tr><td>`solana.staking.rewards`</td><td>New `commission_bps` and `commission_percent` Added</td><td>No</td></tr>
    <tr><td>`solana.staking.validator`</td><td>`last_commission_rate` is current again</td><td>No</td></tr>
    <tr><td>`solana.staking.validator_commission`</td><td>New table: each validator's commission per payout epoch Added</td><td>No</td></tr>
  </tbody>
</table>

> [!TIP]
>
> If you copy these tables into your own warehouse, reload the rows changed on each date. Updated rows have an `_updated_at` on or after that date.

***

## Transfers

* **When:** new data from 22 October 2026 (live); history backfilled on 23 October 2026 (complete)
* **Tables:** `solana.raw.token_transfers`, `solana.assets.transfers`, `solana.assets.transfers_and_stake`

### Preview the backfill

Added Before the history backfill landed in `solana.assets.transfers`, two temporary tables in the Allium App and Explorer showed it, from December 2020 to 14 October 2026.

| Table | Rows |
| - | - |
| `solana.assets.transfers_backfill` | Only the backfilled rows: transfers missing today, plus corrected amounts for `closeAccount` rows that follow an unwrap |
| `solana.assets.transfers_with_backfill` | `solana.assets.transfers` with the backfill applied. A backfilled row replaces the existing row with the same `unique_id` |

Both have the columns of `solana.assets.transfers` plus `batch_instruction_index`, which is `NULL` on rows that are not backfilled. Backfilled rows use the new `token_type`. Filter on `block_timestamp` to keep queries fast.

> [!NOTE]
>
> The backfill landed in `solana.raw.token_transfers` and `solana.assets.transfers` on 23 October 2026, so these tables will be removed. The removal was planned for 30 October 2026 and is now **13 November 2026**. Point any query that reads them at `solana.assets.transfers`, which now has every row they had.

### What changes

* **More value movements get a row.** Existing rows keep their amounts and addresses, except a `closeAccount` row that follows an `unwrapLamports` or `withdrawExcessLamports` on the same account in the same transaction (below). New rows include:
  * the new p-token and prefund instructions (49.2 million rows from 13 May 2026; see [Rows added](#rows-added))
  * nonce withdrawals Added
  * Token-2022 fees Added
  * lookup-table and program closes Added
* Added **New column `batch_instruction_index`.** Each member of a p-token `batch` instruction gets its own row, numbered by its position in the batch.
* Added **New `transfer_type` values:**
  * `withdraw_excess_lamports`, `transfer_fee_withheld`, `transfer_fee_withdrawal`
  * in `solana.assets.transfers_and_stake` only: `stake_move`, `stake_split`, `stake_merge`, `vote_withdrawal`
* Added **`token_type`** changes from `SPL-TOKEN` to `SOL` on rows that move native SOL with no token account.
* Added **`closeAccount` amounts after `unwrapLamports` or `withdrawExcessLamports`.** When either comes before a `closeAccount` on the same account in the same transaction, the close row's `raw_amount` drops by the new row's amount, so the SOL is not counted twice. The account's total outflow is unchanged. This applies from 13 May 2026, when p-token added these instructions. See the example "Unwrap, then close" below.

### Rows added

Counted in the backfill from December 2020 to **14 October 2026 21:00 UTC**. Rows from then until the change went live on 22 October came from the new decoder; with them, the backfill added 421,328,039 rows and lowered 7,004,534 `closeAccount` amounts.

| Change | Rows from | Rows added |
| - | - | - |
| p-token and prefund instructions (SIMD-0266, SIMD-0312) | 13 May 2026 | 49,175,018 |
| Nonce withdrawals | December 2020 | 17,896,482 |
| Token-2022 fees withheld | January 2023 | 322,736,424 |
| Token-2022 fee withdrawals | January 2023 | 15,672,033 |
| `permissionedBurn` | 31 Aug 2026 | 42,623 |
| Confidential deposits and withdrawals | 28 Mar 2025 | 810 |
| Lookup-table and program closes | January 2021 | 7,427,554 |
| **Total** | | **412,950,944** |

* 20.9 million of the p-token rows are `batch` transfers of a single token (`EqUoWB2umVoJzGQfe2nikceRqEgZw8FoDwS6AtMv8it8`), almost all on 18 and 29 May 2026. Without it the p-token and prefund total is 28.2 million.
* 6,643,161 existing `closeAccount` rows from 13 May 2026 also get a lower amount (above). They are corrected rows, not added ones.

### What to do

1. Deduplicate on `unique_id`, the table's key with `block_timestamp` and `txn_id`. Two kinds of rows now share `instruction_index`, `inner_instruction_index` and `pseudo_instruction_order`:

   * the members of one `batch` instruction
   * a Token-2022 transfer and its `transfer_fee_withheld` row

   Deduplicating on instruction position keeps one of those rows and drops the rest. See [Deduplication](#deduplication).
2. When ordering rows within a transaction, add `batch_instruction_index` and then `unique_id` as the last keys. A fee row has no column of its own that orders it; `unique_id` puts it right after its transfer. See [Query patterns](#deduplication).
3. Review `transfer_type` filters for the new values above.
4. If you filter on `token_type = 'SPL-TOKEN'`, native SOL rows no longer match.

### Examples

Real transactions, showing the rows that exist today and the rows added. Payloads show a subset of columns.

> [accordion] Swap ending in an unwrap: partly recorded today
>
> Jupiter swap of 20 USDC for SOL, 3 Oct 2026, slot 452,936,442 · [Solscan ↗](https://solscan.io/tx/121EDchpGQvkpGagoztGseo3hDM4KTFGz1My7KhdAcpigEE96vhEKtLZhTWU4DKSXeYZPLzMye9qGKoSmAqJFQ2C)
>
> The swap legs are recorded today. The final `unwrapLamports`, where the wallet receives its SOL, is not.
>
> | | `transfer_type` | `type` | mint | from → to | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | `spl_token_transfer` | `transfer` | USDC | `9PCP…1Ngq` → `GMCJ…HpC` | 20,000,000 |
> | Today | `spl_token_transfer` | `transfer` | wSOL | `GMCJ…HpC` → `9PCP…1Ngq` | 167,518,534 |
> | Today | `spl_token_transfer` | `transfer` | wSOL | `9PCP…1Ngq` → `GP8S…nDf1` (fee) | 201,022 |
> | **Added** | `account_closure_sol_balance_transfer` | `unwrapLamports` | SOL | `9PCP…1Ngq` → `3L4Y…DRn4` | 167,317,512 |
>
> ```json Added row theme={null}
> {
>   "type": "unwrapLamports",
>   "transfer_type": "account_closure_sol_balance_transfer",
>   "mint": "So11111111111111111111111111111111111111112",
>   "from_address": "9PCP7gpY8B4oPrL5zr4bGqYZrXuMyeNkM3veHEtv1Ngq",
>   "to_address": "3L4YLrxtz8vNk1ZEvCs1X4b3YJNeQKm7rg6snwiCDRn4",
>   "token_acc_from": null,
>   "token_acc_to": null,
>   "raw_amount": 167317512,
>   "batch_instruction_index": null,
>   "unique_id": "txn_id-121EDchpGQvkpGagoztGseo3hDM4KTFGz1My7KhdAcpigEE96vhEKtLZhTWU4DKSXeYZPLzMye9qGKoSmAqJFQ2C_i_index-2_ii_index-5"
> }
> ```

> [accordion] Unwrap with no rows today
>
> A wallet unwraps its own wSOL with one `unwrapLamports`, 15 Sep 2026, slot 447,133,168 · [Solscan ↗](https://solscan.io/tx/2BtbL1tqf4XNKEnZw2KcUHfhWuX6LTgFgJLgkWkfMz1sPnWfDJRXCjGPDrZCfHSFS1ywEKY7rWYdiHkf1TpCm17w)
>
> The transaction has no transfer rows today. 36,338,315 lamports leave the wSOL account and become spendable SOL in the same wallet.
>
> | | `transfer_type` | `type` | mint | from → to | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | no rows | | | | |
> | **Added** | `account_closure_sol_balance_transfer` | `unwrapLamports` | SOL | `GTd6…qFYt` → `GTd6…qFYt` | 36,338,315 |
>
> ```json Added row theme={null}
> {
>   "type": "unwrapLamports",
>   "transfer_type": "account_closure_sol_balance_transfer",
>   "mint": "So11111111111111111111111111111111111111112",
>   "from_address": "GTd6sNB1epWQeVk6afzcQrZ6RQrjgke9fLiAnDaeqFYt",
>   "to_address": "GTd6sNB1epWQeVk6afzcQrZ6RQrjgke9fLiAnDaeqFYt",
>   "token_acc_from": null,
>   "token_acc_to": null,
>   "raw_amount": 36338315,
>   "batch_instruction_index": null,
>   "unique_id": "txn_id-2BtbL1tqf4XNKEnZw2KcUHfhWuX6LTgFgJLgkWkfMz1sPnWfDJRXCjGPDrZCfHSFS1ywEKY7rWYdiHkf1TpCm17w_i_index-2_ii_index-null"
> }
> ```

> [accordion] Unwrap, then close: the close amount is split
>
> Swap of 9,174.80 USDC for 86.50 SOL that unwraps the wSOL, then closes the account, 13 Oct 2026, slot 456,435,445 · [Solscan ↗](https://solscan.io/tx/nxvVtG55wKgMUBPyoN7KTeGYDzxhEDtRarfLddFJfc4yUgMmd97zSBjGXjePPAG3oKsTpPmrnyzPijwrsdC5ptC)
>
> Today the `closeAccount` row carries all 86,498,332,343 lamports that leave the wSOL account `8gFZ…BsMR`. With the `unwrapLamports` row added, the close returns only the account's rent. The two rows still total 86,498,332,343.
>
> | | `transfer_type` | `type` | mint | from → to | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | `spl_token_transfer` | `transfer` | USDC | `F7p3…gmNe` → `7yD7…eZbG` | 9,174,795,034 |
> | Today | `spl_token_transfer` | `transfer` | wSOL | `7yD7…eZbG` → `F7p3…gmNe` | 86,496,843,901 |
> | **Added** | `account_closure_sol_balance_transfer` | `unwrapLamports` | SOL | `8gFZ…BsMR` → `F7p3…gmNe` | 86,496,843,901 |
> | **Changed** | `account_closure_sol_balance_transfer` | `closeAccount` | SOL | `8gFZ…BsMR` → `F7p3…gmNe` | 86,498,332,343 → 1,488,442 |
>
> ```json Changed row theme={null}
> {
>   "type": "closeAccount",
>   "transfer_type": "account_closure_sol_balance_transfer",
>   "token_type": "SOL",
>   "mint": "So11111111111111111111111111111111111111112",
>   "from_address": "8gFZKWfWHcaLekuCoe7qNY8qdLwRKvsdRxU4zMHsBsMR",
>   "to_address": "F7p3dFrjRTbtRp8FRF6qHLomXbKRBzpvBLjtQcfcgmNe",
>   "raw_amount": 1488442,
>   "unique_id": "txn_id-nxvVtG55wKgMUBPyoN7KTeGYDzxhEDtRarfLddFJfc4yUgMmd97zSBjGXjePPAG3oKsTpPmrnyzPijwrsdC5ptC_i_index-4_ii_index-null"
> }
> ```

> [accordion] batch instruction: one row per member
>
> A wallet consolidates token accounts with one `batch` of 17 members, 6 Oct 2026, slot 453,898,051 · [Solscan ↗](https://solscan.io/tx/kNPinchsChynYrhzH6GFqFDuW8zMfs5cphBDcVqgBKQEat2d23dQk9rBxpYeFRBfpNvu8jfdeXyD3piLdWPbZAj)
>
> The transaction has 7 transfer rows today, none of them from the batch. The batch adds 17: two `transferChecked` members moving tokens into one account, and 15 `closeAccount` members returning each closed account's SOL to the wallet.
>
> | | `transfer_type` | `type` | `batch_instruction_index` | token accounts | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | 7 rows from other instructions | | `NULL` | | |
> | **Added** | `spl_token_transfer` | `transferChecked` | 0 | `Cg3T…ULmn` → `DcDx…qit9` | 7,963,165,663,461 |
> | **Added** | `account_closure_sol_balance_transfer` | `closeAccount` | 1 | `Cg3T…ULmn` closed | SOL in the account |
> | **Added** | … 3 more `closeAccount` | | 2 – 4 | | |
> | **Added** | `spl_token_transfer` | `transferChecked` | 5 | `9y76…2JUz` → `DcDx…qit9` | 1,150,771,931,789 |
> | **Added** | … 11 more `closeAccount` | | 6 – 16 | | |
>
> All 17 rows share `instruction_index` 0 and `inner_instruction_index` 0. `batch_instruction_index` and the `unique_id` suffix tell them apart.
>
> ```json Added row (first member) theme={null}
> {
>   "type": "transferChecked",
>   "transfer_type": "spl_token_transfer",
>   "mint": "o6zqqiw7cKpTXCjjjEjAakp7qShGdS9WRFhtSnxUCvD",
>   "from_address": "UWVz4w6PrbNe48yAraebk3hUNhMy4CCJbTET7vhGWmq",
>   "to_address": "UWVz4w6PrbNe48yAraebk3hUNhMy4CCJbTET7vhGWmq",
>   "token_acc_from": "Cg3TBydezGNuQL9fxg2P5WGWh5pR446TCXTH6EfjULmn",
>   "token_acc_to": "DcDxPCneAo4aPWibKjYyXJe8FySpN7W2Lmemff3Cqit9",
>   "raw_amount": 7963165663461,
>   "batch_instruction_index": 0,
>   "unique_id": "txn_id-kNPinchsChynYrhzH6GFqFDuW8zMfs5cphBDcVqgBKQEat2d23dQk9rBxpYeFRBfpNvu8jfdeXyD3piLdWPbZAj_i_index-0_ii_index-0_b_index-0"
> }
> ```

> [accordion] Nonce withdrawal
>
> SOL withdrawn from a durable-nonce account, 6 Oct 2026, slot 453,895,708 · [Solscan ↗](https://solscan.io/tx/129Q8VAQThMeoD94Sn8XgZKmt5qF87m6QJ1JisHciN4whY8Y7Z7ev6vVXNBc97b6nfsekavNduFMJ3kzY5gZy8Zn)
>
> | | `transfer_type` | `type` | mint | from → to | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | no rows | | | | |
> | **Added** | `sol_transfer` | `withdrawFromNonce` | SOL | `HCi4…wP8p` (nonce account) → `6qwo…uWQN` | 1,056,640 |
>
> ```json Added row theme={null}
> {
>   "type": "withdrawFromNonce",
>   "transfer_type": "sol_transfer",
>   "mint": "So11111111111111111111111111111111111111112",
>   "from_address": "HCi4ZHSiE9jkYeoJE7JmV28XPBqCXXK86vsnHLfhwP8p",
>   "to_address": "6qwo9vDb4LZc9UJDManiqANbT3Vptk2KZvK34XpTuWQN",
>   "raw_amount": 1056640,
>   "batch_instruction_index": null,
>   "unique_id": "txn_id-129Q8VAQThMeoD94Sn8XgZKmt5qF87m6QJ1JisHciN4whY8Y7Z7ev6vVXNBc97b6nfsekavNduFMJ3kzY5gZy8Zn_i_index-0_ii_index-null"
> }
> ```

> [accordion] Token-2022 transfer with a fee
>
> Transfer of 1,802.59 tokens on a mint with a 3% transfer fee, 6 Oct 2026, slot 453,898,831 · [Solscan ↗](https://solscan.io/tx/1KgG3F3GRhEKB982pNZzaLqkNaE7sUKhFEpsuqL1mP5MSZJ6ifnuXb7k98pYFS552eWhyxHAKHgXh9esTBuCecr)
>
> The transfer row stays as it is today, at the gross amount. A fee row is added for the 54.0777 tokens withheld in the recipient's account. Both rows have `instruction_index` 3 and `inner_instruction_index` `NULL`; only `transfer_type` and the `_fee` suffix on `unique_id` tell them apart.
>
> | | `transfer_type` | `type` | token accounts | `raw_amount` |
> | - | - | - | - | - |
> | Today | `spl_token_transfer` | `transferCheckedWithFee` | `5cSK…HeXn` → `Dzo9…AqtZ` | 1,802,590,000,000 |
> | **Added** | `transfer_fee_withheld` | `transferCheckedWithFee` | `Dzo9…AqtZ` → withheld | 54,077,700,000 |
>
> ```json Added row theme={null}
> {
>   "type": "transferCheckedWithFee",
>   "transfer_type": "transfer_fee_withheld",
>   "mint": "HcRLc9VDgjLeK154xDawfb1dmVJ98DoSqcwTHGqiDeJR",
>   "from_address": "FhRiiVdT5Q2NDb6szFyETdyZK9Ui2e84Mi9qPNhV8tTK",
>   "to_address": null,
>   "token_acc_from": "Dzo9GFasgPu1TNggmZ88CF5e1fscnGvNNfq8Uns8AqtZ",
>   "token_acc_to": null,
>   "raw_amount": 54077700000,
>   "batch_instruction_index": null,
>   "unique_id": "txn_id-1KgG3F3GRhEKB982pNZzaLqkNaE7sUKhFEpsuqL1mP5MSZJ6ifnuXb7k98pYFS552eWhyxHAKHgXh9esTBuCecr_i_index-3_ii_index-null_fee"
> }
> ```

> [accordion] Account created with createAccountAllowPrefund
>
> A new account funded with `createAccountAllowPrefund`, 6 Oct 2026, slot 453,896,373 · [Solscan ↗](https://solscan.io/tx/2nsgmGeqBBGE6wsCbwsJub3QHHHYVJpQZZ1aLWCCaMrEU76ue37rL6VZ5dLaR8ghu6MWwMhtmgipKcaRhPq4HxPR)
>
> | | `transfer_type` | `type` | mint | from → to | `raw_amount` |
> | - | - | - | - | - | - |
> | Today | no row for this instruction | | | | |
> | **Added** | `sol_transfer` | `createAccountAllowPrefund` | SOL | `sRe1…vG41` → `5zMn…4N8W` | 1,112,520 |
>
> ```json Added row theme={null}
> {
>   "type": "createAccountAllowPrefund",
>   "transfer_type": "sol_transfer",
>   "mint": "So11111111111111111111111111111111111111112",
>   "from_address": "sRe1GfB5QaDp7hWrdriN6uakvkKUAaJqPfsiTBTvG41",
>   "to_address": "5zMnhoZZkqj9yeyygjSdfm1GaDM854hMRBYd1CU74N8W",
>   "raw_amount": 1112520,
>   "batch_instruction_index": null,
>   "unique_id": "txn_id-2nsgmGeqBBGE6wsCbwsJub3QHHHYVJpQZZ1aLWCCaMrEU76ue37rL6VZ5dLaR8ghu6MWwMhtmgipKcaRhPq4HxPR_i_index-2_ii_index-0"
> }
> ```

### Deduplication

Deduplicate on `unique_id`. Deduplicating on instruction position (`txn_id` or `txn_index`, `instruction_index`, `inner_instruction_index`) was safe until now, because each instruction had at most one row. After this change it drops rows.

> [accordion] Example: a batch loses 16 of its 17 rows
>
> The [batch example](https://solscan.io/tx/kNPinchsChynYrhzH6GFqFDuW8zMfs5cphBDcVqgBKQEat2d23dQk9rBxpYeFRBfpNvu8jfdeXyD3piLdWPbZAj) adds 17 rows, all with `instruction_index` 0 and `inner_instruction_index` 0.
>
> | Deduplicated on | Rows kept | Rows lost |
> | - | - | - |
> | `txn_id`, `instruction_index`, `inner_instruction_index` | 1, arbitrary | 16. Either `transferChecked` member (raw 7,963,165,663,461 or 1,150,771,931,789) can be among them, along with the account closures |
> | `unique_id` | 17 | 0 |
>
> The 17 `unique_id` values differ only in their suffix:
>
> ```text theme={null}
> txn_id-kNPinchsChyn…_i_index-0_ii_index-0_b_index-0
> txn_id-kNPinchsChyn…_i_index-0_ii_index-0_b_index-1
> …
> txn_id-kNPinchsChyn…_i_index-0_ii_index-0_b_index-16
> ```

> [accordion] Example: a Token-2022 fee can replace its transfer
>
> The [fee example](https://solscan.io/tx/1KgG3F3GRhEKB982pNZzaLqkNaE7sUKhFEpsuqL1mP5MSZJ6ifnuXb7k98pYFS552eWhyxHAKHgXh9esTBuCecr) has two rows at `instruction_index` 3, `inner_instruction_index` `NULL`:
>
> | `transfer_type` | `raw_amount` | `unique_id` |
> | - | - | - |
> | `spl_token_transfer` | 1,802,590,000,000 | `txn_id-1KgG3F3GRhEK…_i_index-3_ii_index-null` |
> | `transfer_fee_withheld` | 54,077,700,000 | `txn_id-1KgG3F3GRhEK…_i_index-3_ii_index-null_fee` |
>
> Deduplicating on instruction position keeps one of the two. If it keeps the fee row, the transfer you have today is gone and the volume reads 54 tokens instead of 1,802. On `unique_id`, both rows stay.

> [accordion] Query patterns
>
> ```sql theme={null}
> -- Before: drops batch members and fee rows
> qualify row_number() over (
>     partition by txn_id, instruction_index, inner_instruction_index
>     order by _updated_at desc) = 1
>
> -- After
> qualify row_number() over (
>     partition by block_timestamp, txn_id, unique_id
>     order by _updated_at desc) = 1
>
> -- If you need a key made of columns, add both new distinctions
> partition by txn_id, instruction_index, inner_instruction_index,
>              batch_instruction_index, transfer_type
>
> -- Gross transfers only (as before this change)
> where transfer_type <> 'transfer_fee_withheld'
>
> -- Order within a transaction: solana.raw.token_transfers
> order by pseudo_instruction_order, coalesce(batch_instruction_index, -1), unique_id
>
> -- Order within a transaction: solana.assets.transfers (no pseudo_instruction_order)
> order by instruction_index, coalesce(inner_instruction_index, -1),
>          coalesce(batch_instruction_index, -1), unique_id
> ```
>
> `unique_id` works only as the last key: a fee row's `unique_id` is its transfer's plus `_fee`, so it sorts right after the transfer. On its own, `unique_id` compares numbers as text (`i_index-10` before `i_index-2`).

### Reference

> [accordion] All instructions that get rows
>
> `type` is the instruction name; `transfer_type` is the category you filter on. Rows are written only when value moves.
>
> | Instruction | `type` | `transfer_type` | Rows from |
> | - | - | - | - |
> | `unwrapLamports` (p-token) | `unwrapLamports` | `account_closure_sol_balance_transfer` | 13 May 2026 |
> | `withdrawExcessLamports` (p-token, Token-2022) | `withdrawExcessLamports` | `withdraw_excess_lamports` **(new)** | 13 May 2026 |
> | Members of a `batch` (p-token, Token-2022) | the member's own type | same as the standalone instruction | 13 May 2026 |
> | `createAccountAllowPrefund` (System) | `createAccountAllowPrefund` | `sol_transfer` | 15 Jun 2026 |
> | `withdrawFromNonce` (System) Added | `withdrawFromNonce` | `sol_transfer` | all history |
> | `permissionedBurn` (Token-2022) Added | `permissionedBurn` | `spl_token_transfer` | 31 Aug 2026 |
> | Confidential deposit / withdraw (Token-2022) Added | `depositConfidentialTransfer`, `withdrawConfidentialTransfer` | `spl_token_transfer` | Mar 2025 |
> | Address lookup table close Added | `closeLookupTable` | `account_closure_sol_balance_transfer` | all history |
> | Program / buffer close, upgrade refund Added | `close`, `upgrade` | `account_closure_sol_balance_transfer` | all history |
> | Transfer fee on Token-2022 fee mints Added | the transfer's type | `transfer_fee_withheld` **(new)** | all history |
> | `withdrawWithheldTokensFromMint` / `FromAccounts` Added | the instruction name | `transfer_fee_withdrawal` **(new)** | all history |
>
> In `solana.assets.transfers_and_stake` only Added:
>
> | Instruction | `transfer_type` (new) |
> | - | - |
> | Stake `moveLamports` / `moveStake` | `stake_move` |
> | Stake `split` | `stake_split` |
> | Stake `merge` | `stake_merge` |
> | Vote `withdraw` | `vote_withdrawal` |

> [accordion] batch rows
>
> p-token's `batch` instruction runs up to 62 token instructions inside one instruction. Each member gets a row with:
>
> * `batch_instruction_index`: its 0-based position in the batch (`NULL` on all other rows)
> * `unique_id` ending in `_b_index-<n>` (other rows' `unique_id` is unchanged)
> * the wrapper's `instruction_index`, `inner_instruction_index` and `pseudo_instruction_order`
>
> To order rows within a transaction, see [Query patterns](#deduplication): instruction position, then `batch_instruction_index`, then `unique_id`.

> [accordion] Token-2022 transfer fee rows
>
> Added
>
> * The transfer row keeps the **gross** amount.
> * A `transfer_fee_withheld` row records the fee moving into the recipient's withheld balance. Its `unique_id` is the transfer's with `_fee` appended.
> * A `transfer_fee_withdrawal` row records the fee authority collecting it.
>
> | `transfer_type` | from → to | `raw_amount` |
> | - | - | - |
> | `spl_token_transfer` | sender → recipient | 1,000 |
> | `transfer_fee_withheld` | recipient → withheld | 50 |
>
> * The fee row has the transfer's `instruction_index`, `inner_instruction_index`, `pseudo_instruction_order` and `batch_instruction_index`. Tell them apart by `transfer_type` or `unique_id`.
> * The fee row has no `to_address` or `token_acc_to`. A `transfer_fee_withdrawal` row has no `from_address` or `token_acc_from`.
> * Recipient's net amount received: transfer `raw_amount` minus the fee row's `raw_amount`.
> * Fee amounts not stated by the instruction (a plain `transfer` on a fee mint, withdrawals) are derived from balance changes in the transaction, and assume no [invisible movement](https://docs.allium.so/historical-data/supported-blockchains/solana/solana/assets.md#4-invisible-sol-transfers) of the same account's balance.

> [accordion] program\_name for p-token
>
> * p-token runs at the same program ID as SPL Token, so `program_name` stays `spl-token`.
> * Token-2022 rows are also `spl-token`.
> * Use `program_id` to tell SPL Token from Token-2022.

***

## Fees

* **When:** new data from 13 October 2026 (live); history backfilled on 19 October 2026 (complete)
* **Table:** `solana.raw.fees`, all history

### What changes

* Changed **`effective_compute_unit_limit`** now matches the limit the Solana runtime applied.
  * Includes changes to how the default was calculated since 2022.
  * `set_compute_unit_limit` still holds the requested value.
* Added **Transaction V1 rows added** from 15 Sep 2026, about 47 million per day.
  * Transaction V1 is a new Solana transaction format, live since 15 September 2026 and used by a large share of non-vote transactions.
  * It sets the compute limit and priority fee in the transaction itself, instead of in ComputeBudget instructions. These rows take both values from there.
* Added **`priority_fee` and `base_fee`** match the fees paid on chain.

### What to do

* If you analyse compute headroom or utilisation, re-run it: the history backfill is complete.
* If you count rows, expect about 47 million more per day from 15 Sep 2026.
* Use `priority_fee` directly rather than deriving it from `set_compute_unit_price`.

***

## Staking commission

* **When:** 6 November 2026.
* **Tables:** `solana.staking.rewards`, `solana.staking.validator`, `solana.raw.rewards`

Since SIMD-0232 (8 Sep 2026):

* Validators can pay commission to any account.
* The RPC no longer returns a commission rate on rewards.

Commission is now rebuilt from on-chain data and lives in the staking tables.

> [!NOTE]
>
> **No type change.** In September we announced that `solana.raw.rewards.commission` and `solana.staking.validator.last_commission_rate` would change to `NUMBER(38,10)`. We didn't make that change. Both keep `NUMBER(38,0)`, so you don't need to change your loads. Commission in basis points and percent is in new columns in `solana.staking.rewards`.

### What changes

* Changed **`solana.staking.rewards`** is the recommended source:
  * new `commission_bps` (`NUMBER(38,0)`) and `commission_percent` (`NUMBER(38,10)`), for all history from December 2020. They are `NULL` before August 2021, where the RPC returned no commission.
  * `validator_vote_account` filled for native staking rewards. A small number of rewards before 20 July 2026 stay `NULL`.
* **`solana.staking.validator`**: `last_commission_rate` is current again, capped at 100.
* Changed **`solana.raw.rewards`** mirrors the RPC:
  * `commission` is `NULL` from 16 Jul 2026
  * for 16 Jul – 8 Sep 2026, the RPC's `commissionBps` is in `_extra_fields`
  * as of 6 October 2026, 54.8 million rows have a `NULL` commission across `Staking`, `DeactivatedStake` and `Voting` rewards. 22.4 million of them are from 8 Sep 2026, when the RPC stopped returning a rate.
* Added **`solana.staking.validator_commission`**: each validator's commission per payout epoch, out of its commission collector's `Voting` reward. `is_estimated` is true when several validators share the collector.

### What to do

1. Read commission from `solana.staking.rewards` instead of `solana.raw.rewards.commission`.
2. For commission per validator, use `solana.staking.validator_commission`. Don't read a `Voting` reward's `pubkey` as the validator. From 8 Sep 2026 it is the commission collector. That is the validator's vote account, unless the validator set a custom collector, which several validators can share.
3. If you copy `solana.staking.rewards` into your own warehouse, reload all of it. Its history was rewritten on 6 November 2026, and every row has an `_updated_at` on or after that date.

> [accordion] Which epoch's rate applies
>
> * Since SIMD-0249 (22 Jun 2026), a commission change takes effect with a delay.
> * Rewards paid at the start of epoch N use the rate in force at the start of epoch N − 2.
> * `commission_bps` is the rate the chain applied.

***

## Reference

> [accordion] \_extra\_fields on raw tables (7 October 2026)
>
> Added
>
> Solana raw tables keep RPC fields that aren't modelled as columns in a `VARIANT` column, `_extra_fields`.
>
> * New column on `solana.raw.blocks` and `solana.raw.rewards`.
> * New keys in `solana.raw.transactions._extra_fields` from 7 October 2026: `txn.version`, `message.transactionConfig` (Transaction V1) and `message.addressTableLookups`.
>
> ```sql theme={null}
> select txn_id,
>        _extra_fields:"message.transactionConfig":computeUnitLimit::number as compute_unit_limit,
>        _extra_fields:"message.transactionConfig":priorityFee::number     as priority_fee
> from solana.raw.transactions
> where block_timestamp >= '2026-10-08'
>   and _extra_fields:"txn.version"::number = 1
> limit 10;
> ```

## Support

If these changes affect your workflows or you need help, reach out to [support@allium.so](mailto:support@allium.so) or your account team.
