Instant delivery

Lifetime updates

1 domain license

Blockchainv6.1.1

Solana Blockchain Addon

Name: Solana Blockchain Addon
Brand: MashDiv
SKU: solana
Price: 119.00 USD
Availability: InStock

SOL and SPL custody inside your own wallet stack — per-user addresses, credited deposits, signed sends.

4.8037 sales

$119$139Save 14%

You'll also need Bicrypto and Ecosystem for Bicrypto

On its own, Solana Blockchain Addon won't work — it only runs if you already own these products. Open the Requirements tab to see exactly what you need and add them to your order.

See it working Live demo Documentation View on CodeCanyon

A Solana address per user per currency, with the key held on your server
Native SOL and SPL deposits, watched live and by a background scanner
Deposits credit the moment they are detected — no confirmation-depth wait
The last 25 signatures replay on every scan, so a closed tab loses nothing
Lookup-table transactions parse, so exchange-sent deposits still credit
Crediting is idempotent twice over — one signature can only pay out once
Native withdrawals signed by the customer's key, with the fee probed exactly
SPL withdrawals signed by the customer, with the master wallet as fee payer
Token accounts created on both sides, their rent paid by the master wallet
Broadcast-but-unverified parks as TIMEOUT, never as a refund you cannot recall
Deploy your own SPL mint, or list any existing token by its mint address
A requirements report that prints the cluster your install really resolved to

Inside Solana Blockchain

Custody on Solana, held on your server

Switch it on and your Ecosystem wallets speak Solana: an address per customer per currency, native SOL and SPL token deposits credited without anyone watching, and withdrawals signed and broadcast from your own install.

In detail

Solana Blockchain extends your Ecosystem wallets to a chain the base addon does not carry. Switch it on and every ECO wallet gains a Solana deposit address, native SOL and SPL token deposits are detected and credited without anyone watching, and withdrawals are signed and broadcast from your own install. It is custody, not a wallet connector: the platform holds a private key for every customer address on your server, and when a withdrawal will not sign, you are the one who fixes it.

How it works

A customer opens a deposit page; the platform derives a fresh Solana keypair, encrypts it with the Ecosystem vault key and shows the address. A live subscription watches the address while the page is open; a background scanner keeps watching for 72 hours after they close it; both replay the address's last 25 signatures, so a deposit sent to a closed tab still lands. Detection credits the wallet on the spot; anything that could not be credited straight away is parked in Redis and retried by a 60-second job. Withdrawals are a queue, not a request: the wallet is debited durably first, then native SOL is signed by the customer's own key while SPL adds the master wallet as fee payer.

The real configurable surface

Knob	What it does
`SOL_NETWORK`	`mainnet` or `testnet` — every other value silently means devnet
Chain toggle	the database row that arms the module; seeded off
Token fee	percentage and minimum, per token, charged in the withdrawn currency
SPL tokens	import any mint by address, or deploy your own from the admin panel
`ECOSYSTEM_SCAN_RATE_SOL`	background scan pace — 0.5 address scans per second
`ECOSYSTEM_SCAN_ACTIVE_TTL_MS`	how long an address stays watched — 72 hours

What operators control

Enable or disable the chain from Admin → Ecosystem → Blockchains. Create one Solana master wallet, fund it with SOL, and disable it the moment you suspect the key. Deploy an SPL mint with the master wallet as mint authority and no freeze authority, or list an existing token by its mint address. Run a requirements report that prints the cluster it really resolved to, probes the RPC live and grades deposits and withdrawals separately. Clear the TIMEOUT queue: a transaction that broadcast but could not be verified is parked for a human, never auto-refunded.

There is no custom RPC endpoint — the connection is built from SOL_NETWORK alone and always calls the public cluster, so a paid RPC subscription changes nothing. Size your Solana volume for that, and budget for Bicrypto plus the Ecosystem addon plus an activated licence before a single address can be issued.

Two gates, and the console names the one that failed

Solana is gated twice and both must pass: an activated licence file on disk, and a chain row in your database that ships switched off. A third thing catches people out — a valid licence with no extracted chain service leaves every flow dead, address generation included. The requirements console checks all of it in one pass, prints the cluster it actually resolved to, and grades deposits and withdrawals separately rather than as one green tick.

Requires Bicrypto and the Ecosystem addon. Without them this is an unreachable code path and a database row. Flipping the chain row takes effect with no restart; a change to SOL_NETWORK does not, because the connection is built once and held for the life of the process.

There is no RPC field — and that is the number to plan around

Every other chain family in Ecosystem takes an endpoint: Tron and TON each read an RPC host and an API key, Monero points at your own daemon. Solana reads a cluster name and nothing else, then calls the public cluster for it. That is why the module ships paced — background address scans half a second apart, five seconds between queued withdrawals, half an hour of transaction-history cache. You cannot buy past it, so size your Solana volume for it.

SOL_NETWORK recognises exactly two values, mainnet and testnet. Unset, misspelled, or set to the plausible-looking mainnet-beta, the service connects to devnet: addresses generate, diagnostics pass, and a customer's real SOL never arrives. The cluster-resolution line in the requirements report is the one place that cannot be misread.

Two ways to list an asset, and one of them costs the master wallet

Any SPL token becomes a listed asset by pasting its mint address — that address is exactly what deposit detection subscribes to and what withdrawals send against, so no mint is deployed and no SOL is spent to list it. The other mode deploys a fresh mint from the admin panel at the decimals you choose, signed and paid for by your Solana master wallet, which becomes the mint authority; no freeze authority is set. That wizard prints the rent estimate next to the master wallet balance and refuses to advance until the balance covers it. Either way you set the token's own withdrawal fee — a percentage with a floor, charged in the token being withdrawn — along with its deposit and withdrawal limits and the decimal precision your platform accepts, which is a separate field from the mint's decimals.

Deploying needs a Solana master wallet; importing needs the mint address plus the usual listing fields — though sending an imported SPL token later still needs that wallet as fee payer. Both modes assume the original SPL token program: a Token-2022 mint cannot be deployed here, and importing one is not refused — the row lists, then never detects or sends. Initial supply is minted by a background job the deploy starts and does not wait for, and if that mint fails the row stays listed with no supply and nothing tells you — check the mint on an explorer before you announce the token.

Two keys sign, and one status stops a double payout

A native SOL withdrawal is signed by the customer's own key and pays its network fee out of the balance being sent — the master wallet is never touched. An SPL withdrawal is signed by the customer and partially signed by the master wallet as fee payer, which also covers token-account rent on both sides. So an empty master wallet fails selectively: every SPL send breaks while native SOL keeps clearing. A transaction that broadcast but could not be verified is parked as TIMEOUT, not FAILED, because refunding money that has already left is the expensive mistake.

TIMEOUT rows do not clear themselves — you take the signature, check it on a block explorer and settle the row by hand. A growing TIMEOUT queue is the clearest sign your Solana volume has outgrown the public cluster.

gates before anything runs: 2
paced address scans: 0.5/s
between queued sends: 5s
deposit retry pass: 60s

Everything included

81 capabilities, in 6 areas

Every item below exists in the source you receive. Nothing here is a roadmap.

Turning it on, and proving it is on

Two gates, one cluster variable, and a console that names whichever one failed.

Seeded Solana chain row in Admin → Ecosystem → Blockchains, shipped switched off
Licence-file gate on the toggle: enabling without an activated licence is refused
The chain service checks both gates again itself, on a five-minute cache
Enabling the row takes effect with no restart; a cluster change needs one
Cluster chosen by one variable — mainnet or testnet, every other value devnet
Requirements report listing every Solana variable the runtime reads, set or unset
The variables that are read by nothing, labelled as such in the same report
Live probe: the resolved cluster printed as a URL, RPC health, and a live slot number
Chain-service-installed check, graded separately from the licence check
Readiness graded per flow — deposits and withdrawals, not one green tick
Withdrawal readiness also fails on a locked vault or a missing or disabled master wallet
Warnings for an unrecognised cluster name and for the two network variables disagreeing
Chain detail screen with the installed version, a licence check and an update check
Solana offered in the token and master-wallet chain pickers only once the row is on

Addresses and key custody

Where a customer's Solana address comes from, and who holds its key.

One Solana address per customer per currency, issued on the first deposit-page visit
A fresh BIP39 mnemonic and ed25519 keypair per address at m/44'/501'/0'/0'
User addresses are independent keypairs, not derived from the master wallet
Mnemonic, derivation path, public key and secret key encrypted with the Ecosystem vault key
Address map on the wallet row carrying the address, its network label and a display balance
An address entry that lost its address is regenerated in place on the next fetch
One Solana master wallet per install, enforced — a second attempt is refused
Master wallet generated by the chain service, encrypted at rest, never written to disk in plaintext
Master wallet can be disabled to stop SPL signing without disabling the chain
Withdrawal destinations parsed as Solana public keys before any balance is touched
No custodial contracts on Solana — every deposit lands at the customer's own address

Deposits

Two detection paths, two ways of watching each, and one crediting rule they share.

Native SOL credited from the increase in that account's lamport balance
SPL token deposits credited at the customer's associated token account
Live logs subscription on the address while the deposit page is open
Token-program account subscription filtered to the exact mint and owner, for SPL
The address's last 25 signatures replayed before subscribing
Background scanner keeps an address watched for 72 hours after its last deposit-page visit
Each watched address re-scanned roughly every two minutes
A per-chain token bucket paces Solana at half an address scan per second
One process runs the scan loop, held by a Redis lock
Version-0 transactions with address lookup tables resolved, so exchange-sent deposits credit
SPL detection reads transferChecked and plain transfer, with a token-balance-delta fallback
Deposits credit on detection — no confirmation-depth wait on this chain
Anything that could not credit immediately is parked and retried on a 60-second pass
Idempotent twice over: a prior row for the same signature and wallet, and a keyed balance credit
Concurrent lookups of one signature share a request; a result is held for a minute
Live monitors self-cancel after an idle hour and re-arm on the next page visit
An invalid mint fails fast naming the token, instead of an endless subscription retry
Deposit confirmation pushed to the open page over WebSocket, plus a notification

Withdrawals

The queue, the debit and the recovery jobs are Ecosystem's; the two keys that sign are this module's.

The balance is debited durably before anything is broadcast
Native SOL signed by the customer's own key — the master wallet is never touched
The network fee priced per transaction by a fee probe, falling back to 5,000 lamports
A send that cannot cover its own fee is reduced to fit, against a freshly read on-chain balance
SPL signed by the customer and partially signed by the master wallet as fee payer
Associated token accounts created on both sides when absent, their rent paid by the master wallet
The sender's token balance checked before the transfer is built
Platform fee from the token's own rule — a percentage with a minimum, in the withdrawn currency
Confirmation against the blockhash the transaction was built with
Up to ten verification polls on a growing backoff before any verdict is recorded
A definitive on-chain error marks the row FAILED with the error attached
Broadcast but unverifiable parks as TIMEOUT rather than FAILED, so nothing is refunded twice
Five-second per-chain cooldown between queued Solana sends
Amount precision checked against the token's configured precision
Withdrawal 2FA enforced when the platform policy demands it
A destination belonging to another platform user short-circuits to an internal transfer
Withdrawing to your own deposit address is refused outright
Boot sweep, five-minute watchdog and half-hour pass re-enqueue rows stranded by a restart
A processing row that already carries a signature is completed, never re-broadcast

SPL tokens

List somebody else's mint, or create your own from the admin panel.

Import any existing SPL token by its mint address
Deploy a new SPL mint from the admin panel at the decimals you choose
Mint authority is the master wallet; no freeze authority is set
Initial supply minted to a nominated holder as a background job, with retries
Deployment cost estimate — the rent-exempt minimum for a token account
The wizard will not advance until the master wallet balance covers that estimate
Per-token withdrawal fee: a percentage and a minimum
Per-token precision, set independently of the mint's decimals
Enable or disable a token without deleting it
One deploy-or-import wizard, shared with every other chain

What you watch, and what you tune

Master wallet balance read live in the admin panel, cached for a minute
Chain state on the ecosystem dashboard — ready, degraded, blocked or idle
The last diagnostics verdict stored per chain, with the time it was run
Solana transaction history per address — the last 50 signatures, cached for half an hour
Explorer link per cluster: mainnet, testnet and devnet
Every deposit and withdrawal on the platform ledger, with the signature as its reference
Background deposit scanner switchable off platform-wide
Solana-specific override for the background scan rate
Scan interval and the address working-set lifetime, both configurable

Licence: Licensed and activated separately from Ecosystem. Activation writes a machine-bound licence file this install checks in two places.
Requires: Bicrypto and the Ecosystem addon, both. Without them this is an unreachable code path and a database row.
Runs on: Your own server, inside the Bicrypto backend and cron processes you already run. It adds no process and no port.
Stack: Ecosystem's: MySQL or MariaDB, Redis and ScyllaDB, plus the vault key in your .env. Solana itself adds no service.
Network: The public Solana cluster for whichever of mainnet or testnet you select. No node to run.
Assets: Native SOL at 9 decimals, plus any SPL token you import by mint address or deploy from the admin panel
Admin surface: Seven existing Ecosystem admin screens that Solana appears in. There are no Solana-only screens.
Access control: The 13 Ecosystem permission keys that already gate those screens. None of them is Solana-specific.
Scheduled work: Three existing Ecosystem cron jobs: deposit verification every minute, a withdrawal watchdog every five, a recovery pass every thirty
There is no RPC endpoint field: The connection is built from the cluster name alone and calls the public cluster. Buying a paid Solana endpoint changes nothing about where your traffic goes — size your volume for the public one.
Two cluster values, and only two: mainnet and testnet are recognised. Unset, misspelled, or the plausible-looking mainnet-beta all select devnet silently — addresses generate, diagnostics pass, real SOL never arrives.
Classic SPL only: Deposits and withdrawals use the original SPL token program. Token-2022 mints are neither detected nor sent.
TIMEOUT rows need a human: A withdrawal that broadcast but could not be verified is parked rather than refunded. Nothing clears it for you: take the signature, check it on an explorer, settle the row by hand.
Custody, not a wallet or a market: Addresses, deposits, withdrawals and SPL mints. No staking, no NFTs, no program interaction, and no customer wallet connection.
Two views are EVM-shaped: The address transaction list parses native transfers only, so an SPL-only address shows empty rows, and the token-holders view needs an explorer API Solana has no equivalent of. Balances and crediting are unaffected.