Build a minimal web-based UI that lets users interact with the LEZ token program — specifically the new_definition, mint, and transfer
instructions — without needing CLI tooling or manual JSON construction.
Motivation
The token program supports a rich set of operations (create, mint, burn, transfer, NFTs), but currently the only way to interact with it is
by constructing raw JSON instructions and submitting them via the spel CLI or writing test code. A simple UI would lower the barrier for
demos, internal testing, and onboarding.
Scope
The app should support the following flows:
Token creation
- Input fields for token name, symbol, decimals, and initial supply
- Derive or display the mint PDA / definition account address
- Submit a new_definition instruction to the sequencer
Minting
- Select or paste a mint address
- Specify recipient account and amount
- Submit a mint instruction
Transfer
- Select or paste source and destination accounts
- Specify the token mint and transfer amount
- Submit a transfer instruction
Account inspection
- Look up and display token account balances
- Display token definition metadata (name, symbol, decimals, supply)
Technical notes
- Instructions are serialized as serde JSON and submitted to the sequencer via the wallet/SPEL toolchain or a compatible RPC interface
- Account data is Borsh-encoded on-chain; the UI will need to deserialize it for display
- Authentication/signing should integrate with the existing wallet setup (NSSA_WALLET_HOME_DIR)
- The app does not need to handle AMM or NFT flows in the initial version
Acceptance criteria
- User can create a new fungible token definition end-to-end
- User can mint tokens to an account
- User can transfer tokens between accounts
- User can inspect token account balances and definition metadata
- App connects to a local or testnet sequencer
Build a minimal web-based UI that lets users interact with the LEZ token program — specifically the new_definition, mint, and transfer
instructions — without needing CLI tooling or manual JSON construction.
Motivation
The token program supports a rich set of operations (create, mint, burn, transfer, NFTs), but currently the only way to interact with it is
by constructing raw JSON instructions and submitting them via the spel CLI or writing test code. A simple UI would lower the barrier for
demos, internal testing, and onboarding.
Scope
The app should support the following flows:
Token creation
Minting
Transfer
Account inspection
Technical notes
Acceptance criteria