~6% APY through native Solana staking + Jito MEV rewards
Zero custody: private keys are used only to sign transactions, never stored on the server
On-chain verification via solentic.theblueprint.xyz memo

Installation

npm install @elizaos/plugin-solentic

Configuration

Add the plugin to your character config:

{
  "plugins": ["@elizaos/plugin-solentic"],
  "settings": {
    "secrets": {
      "SOLANA_PRIVATE_KEY": "your-base58-private-key",
      "SOLANA_PUBLIC_KEY": "your-wallet-address"
    }
  }
}

Environment Variables

Variable	Required	Description
`SOLANA_PRIVATE_KEY`	For staking	Base58-encoded Solana private key. Needed for stake/unstake/withdraw.
`SOLANA_PUBLIC_KEY`	Recommended	Wallet address. Used for portfolio lookups and balance checks.
`SOLENTIC_API_URL`	No	API base URL. Defaults to `https://solentic.theblueprint.xyz`.

Actions

STAKE_SOL

Stake SOL with the Blueprint validator. Extracts the amount from natural language.

Triggers: "stake 10 SOL", "put 5 SOL into staking", "delegate SOL to Blueprint"

UNSTAKE_SOL

Deactivate a stake account. If only one active stake account exists, it is selected automatically. Otherwise the agent asks the user to choose.

Triggers: "unstake my SOL", "deactivate my stake", "stop staking"

WITHDRAW_SOL

Withdraw SOL from a deactivated stake account back to the wallet. Checks cooldown readiness before attempting.

Triggers: "withdraw my staked SOL", "claim my SOL back", "get my SOL out"

CHECK_STAKE_STATUS

View the staking portfolio: all stake accounts, balances, states, and estimated rewards.

Triggers: "check my staking status", "how much SOL do I have staked?", "show my stakes"

GET_VALIDATOR_INFO

Get Blueprint validator details: APY, commission, performance, total stake, version.

Triggers: "what's the validator APY?", "tell me about the Blueprint validator", "what yield can I get?"

Provider

solenticStakingInfo

Automatically provides staking portfolio context to the agent so it can proactively reason about idle SOL, staking opportunities, and withdrawal readiness.

Security

Private keys are sent to the Solentic API for one-shot transaction signing and are never stored or logged on the server
All transactions include an on-chain memo (solentic.theblueprint.xyz) for verification
The API source code is auditable via the verify_code_integrity endpoint
HTTPS only for all API communication