Feat/sol contract whitelist policy

[spacesailor24]

Description

Adds a new Policy for restricting what contracts can be called by transactions signed by the @lit-protocol/vincent-ability-sol-transaction-signer Ability

Users whitelist specific Solana program IDs for each available Solana cluster (network i.e. devnet, testnet, mainnet-beta)

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Adds the policy to the existing E2E Solana tx signer Ability tests. Verifies a transaction is permitted to sign calling a whitelisted program on devnet, but Ability execution is denied when making a signing request to execute the same program on mainnet-beta (which has no whitelisted programs)

Checklist:

• I created a release plan (nx release plan) describing my changes and the version bump
• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vincent-app-dashboard	Ready	Preview	Comment	Oct 4, 2025 5:16am
vincent-docs	Ready	Preview	Comment	Oct 4, 2025 5:16am

[Copilot]

Pull Request Overview

This PR introduces a new Solana contract whitelist policy that restricts which programs can be called by transactions signed by the @lit-protocol/vincent-ability-sol-transaction-signer Ability. Users can whitelist specific Solana program IDs for each available Solana cluster (devnet, testnet, mainnet-beta).

• Adds a new @lit-protocol/vincent-policy-sol-contract-whitelist package with validation logic
• Integrates the policy with the existing Solana transaction signer ability
• Updates E2E tests to verify policy enforcement across different clusters

Reviewed Changes

Copilot reviewed 34 out of 65 changed files in this pull request and generated 3 comments.

File	Description
packages/apps/policy-sol-contract-whitelist/	New policy package implementation with schemas, validation logic, and build configuration
packages/apps/ability-sol-transaction-signer/	Integration of the new whitelist policy and schema updates
packages/apps/abilities-e2e/	Enhanced E2E tests to validate policy enforcement scenarios
nx.json	Build configuration updates

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

packages/apps/policy-sol-contract-whitelist/src/lib/lit-action-helpers/deserializeTransaction.ts:1

• The deserialization logic is duplicated between this file and the ability's deserializeTransaction helper. Consider extracting this logic to a shared utility module to avoid code duplication and ensure consistent behavior across both implementations.

import { Transaction, VersionedTransaction } from '@solana/web3.js';

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[spacesailor24]

I'm having to pass rpcUrl: null for both precheck and execute and make the parameter .optional().nullable() in both the Policy and Ability schemas in order to support having an optional parameter for a Policy

rpcUrl is something we want as a optional param for Policy/Ability precheck because otherwise we'd be using the publically available SOL RPC packaged in the web3.js SDK. However this RPC can be throttled and rate limited, so it needs to be possible for the caller to pass their own RPC URL for precheck to function. This isn't an issue with execute because the Lit nodes have their own private RPC available

However, when defining:

const ProgramWhitelistPolicy = createVincentAbilityPolicy({
  abilityParamsSchema,
  bundledVincentPolicy,
  abilityParameterMappings: {
    rpcUrl: 'rpcUrl',
    cluster: 'cluster',
    serializedTransaction: 'serializedTransaction',
  },
});

this throws an error if rpcUrl is undefined. The workaround is to pass null but this is bad Devx because you must pass rpcUrl: null whenever the Policy is enabled for the Ability