# Upcoming Changes

## Strict Solana recipient matching (effective November 29, 2026)

We are extending how the **Recipient condition** is matched against Solana transactions.

**Timeline:**

- **October 21, 2026:** The **Strict Solana recipient matching** toggle is available under **Settings** > **Safeguards**. It is off by default, so matching only changes for organizations that turn it on.
- **November 15, 2026:** The toggle turns on for organizations that haven't changed it. If you turned it off, it stays off.
- **November 29, 2026:** The toggle is removed, and strict matching applies to all organizations.


**What is changing:** Without strict matching, on Solana, the Recipient condition only sees the programs a transaction calls directly. With strict matching, it also sees where each transfer actually lands, and will recognize when that destination, such as a pool or token account, belongs to a known DApp.

**Background:** A Recipient condition, on any chain, only matches a transaction when every recipient it touches is covered by the rule. On Solana, that picture has so far been limited to directly-called programs, which misses recipients further down the call stack: most swaps route funds through a program's own calls to other programs, so the pool or token account that actually receives the funds was never checked against the rule. This change closes that gap.

**What you may need to do:** A Recipient condition in a rule still has to cover every recipient a transaction touches. Strict Solana recipient matching can surface addresses that an existing Recipient condition doesn’t cover, causing it to stop matching and the transaction to fall through to the next rule, typically a stricter Approval or Block rule. Review your Solana policy rules that use a Recipient condition before November 29, 2026, when strict matching applies to all organizations. If you haven't changed the toggle, strict matching already applies from November 15, 2026, so either review your rules by then or turn the toggle off to keep the current matching until November 29:

- **Where a rule names an individual address that belongs to a DApp, use the DApp instead.** A DApp recipient, or a DApp group, also covers the pools and token accounts that strict matching surfaces, whereas a single address only ever covers itself.
- **Add Jito and LayerZero** to rules that should keep matching transactions with a tip or fee leg that routes through them.
- **Add Raydium and Invariant** to rules that should keep matching swaps routed through those pools.


Once your rules are updated, go to **Settings** > **Safeguards** and toggle on **Strict Solana recipient matching**.

**Not affected by this change:** Fordefi's in-app swap feature and plain SOL/token transfers already report their actual recipient today, so rules covering those transaction types are unaffected.

If you have questions or need help adjusting your policies before this change takes effect, please reach out to us at [support@fordefi.com](mailto:support@fordefi.com).