Roadmap | Solana — BizFirstAI

17 of 47 shipped: This node implements 17 of a 47-operation design, spanning all 10 resources. The remaining 30 are catalogued in the project's design docs but not yet routed.

Known Scope Limits in What's Already Shipped

Area	Limitation
NFT (`nft/getAsset`)	Resolves current owner correctly but not on-chain Metaplex metadata (name/uri) — no maintained .NET Metaplex library exists for either standard.
Staking (`staking/getAccount`)	Decodes the stake account's raw bytes against the documented layout by hand — no Solnet-provided decoder.
Nonce (`nonce/get`)	Similarly hand-decodes the nonce account layout.
Transaction writes	Only `sendNative` (native SOL transfer, fully server-side built + signed) is implemented — a generic "submit arbitrary caller-supplied instructions" operation is not.
Staking writes	Only `delegate` (against an existing, already-initialized stake account) is implemented — creating and initializing a new stake account is not.

Planned Additional Operations

The full 47-operation design spans every resource more deeply. Representative examples of what's not yet routed:

Resource	Planned Operation Examples
`account`	create, close
`block`	getBlock, getBlockTime, subscribe (slot/log listeners)
`transaction`	generic instruction submission (arbitrary caller-built instructions), simulate
`token`	mint, burn, approve/revoke delegate, getMintInfo
`nft`	Metaplex metadata resolution (name/uri/collection), mint, transfer
`staking`	create + initialize stake account, deactivate, withdraw, split, merge
`program`	Anchor IDL-aware decoding, generic instruction invocation, PDA derivation helpers
`wallet`	verify signature, derive address from a public key without a full secret-key credential
`nonce`	create, advance, withdraw

This is illustrative, not exhaustive — see the project's own design index for the authoritative full catalogue.

Triggers Are a Separate, Not-Yet-Built Concern

Slot/signature/program-log listeners (i.e. using Solana activity to start a workflow rather than being called from one) are intentionally not part of this action-node's routing switch — they'd be a separate trigger-executor, mirroring how the Ethereum node in this same Area also keeps triggers architecturally distinct from its action operations.

Design Philosophy Carried Forward

Additional operations will follow the exact same partial-class/service pattern as today's 17 — same resource/operation config shape, same per-cluster selection, same output-wrapping convention.
Write operations will continue resolving signing keys exclusively from the vault via credentialID — never a plain config field.
Where a maintained decoding library doesn't exist (Metaplex, Anchor IDL), operations will either wait for one, hand-roll a decoder against the documented on-chain layout (as staking/nonce already do), or return raw bytes and leave decoding to a downstream workflow step.

Want something sooner? Track progress via the BizFirst.Ai team, or reach out on community.bizfirstai.com with which of the remaining 30 operations would unblock your workflow.