Solana architecture
NIXIM on Solana.
NIXIM is designed around Solana mint addresses, SPL token data, Solana wallets, Solana RPC, and Solana-native trading venues.
Network
Solana Mainnet with SOL as the native network asset.
Token model
SPL token mints are read directly from Solana RPC using parsed account data.
01
SPL token inspection
NIXIM accepts standard Solana mint addresses. The token page reads the mint account and displays public supply, decimals, token-program ownership, mint authority, and freeze authority.
| Field | Meaning |
|---|---|
| Mint address | The canonical Solana identifier for a token. |
| Supply | Raw mint supply adjusted by the mint decimals. |
| Mint authority | If present, the authority can generally mint additional supply. |
| Freeze authority | If present, the authority may have token-account freeze capabilities. |
| Token program | The Solana program that owns the mint account. |
A valid SPL mint is not proof that a token is safe, official, liquid, or legally compliant.
02
Solana wallets
The interface looks for an injected Solana wallet provider such as Phantom or Solflare. Connecting exposes the public wallet address to the page. Private keys and seed phrases remain inside the wallet.
- Connect through the wallet extension
- Verify the selected wallet and transaction simulation
- Review SOL fees and every program account before signing
- Never enter a seed phrase into the NIXIM website
03
Solana launch program
Production token launches require a deployed NIXIM Solana program whose program ID is configured in config.json or NEXT_PUBLIC_NIXIM_PROGRAM_ID.
The browser form prepares token identity, artwork, links, wallet state, and Solana-specific checks. Transaction submission should only be enabled after the frontend instruction encoding has been matched to the audited deployed program.
A Solidity smart contract cannot simply be pointed at Solana. The launch logic must be implemented and deployed as a Solana program before production launches can be signed.
04
Solana trading access
Token pages link the exact mint to external Solana trading venues. The interface provides Jupiter and Raydium access for the selected mint.
Jupiter
Used as the primary external swap route destination for a configured mint.
Raydium
Provided as a secondary Solana liquidity venue. Available liquidity can differ from Jupiter routing.
Third-party swap interfaces are independent services. NIXIM does not control their routes, liquidity, fees, uptime, or token lists.
05
Configuration
| Property | Value |
|---|---|
| Network | Solana Mainnet |
| Cluster | mainnet-beta |
| Native asset | SOL |
| Default RPC | https://api.mainnet-beta.solana.com |
| Explorer | Solana Explorer ↗ |
| NIXIM program | Not configured |
| Official $NIXIM mint | 26MGA3UbCYD4n6iRgcdKguWpwTvXovkHJnY1XoqEpump |
- Deploy the Solana program.Audit the program and record the verified program ID.
- Configure RPC.Use a reliable production Solana RPC instead of relying on a public rate-limited endpoint.
- Set the program ID.Place it in
config.jsonor the environment variable. - Set the official mint.Put the verified $NIXIM mint in
config.json. The official token page and swap link update automatically. - Test with low value.Verify wallet flows, account ownership, instruction data, token authorities, and explorer links before public release.