What TRK does

Wallet

A local, self-custody Solana wallet. Create a new key or a BIP-39 recovery phrase (compatible with the standard Solana derivation path used by Phantom and Solflare), or import an existing phrase or secret key.

• Keys are encrypted right away under your account email and password (scrypt + AES-256-GCM) and stored only on your device.
• Transactions are signed locally. Secrets are never printed, logged, put in history or sent anywhere.
• Receive with your address shown alongside a fingerprint and a QR code. Copying it checks the clipboard and clears it automatically.
• Balances for SOL and all your SPL and Token-2022 tokens, plus an activity history.

Token sends (SOL, SPL and Token-2022)

Send SOL, SPL tokens and Token-2022 tokens. Token sends use checked transfers with decimals enforced. If the recipient's token account is missing it is created, and the rent is shown.

• Token-2022 safety checks block risky mints (for example permanent delegate, non-transferable or default-frozen) and show transfer fees.
• The escrow program holds native SOL only for now, so token sends need the typed skip-escrow waiver.

Escrow by default

SOL sends go through TRK's on-chain escrow unless you choose otherwise. The rules are enforced by the program, not only by the app.

• 30-minute hold after funding.
• After the hold, you confirm the recipient. The program checks the address against the one stored in the escrow.
• If you never confirm (for example a wrong or poisoned address), after the hold plus 24 hours you alone can cancel and get a refund.
• Funds are released exactly once. A second release fails.

Address book

An encrypted address book. Tampering is detected and a tampered book is refused.

• Changed address: if a saved address changed since your last send, you get a loud warning with the old and new address, re-authentication and a typed confirmation.
• Look-alike address: if an address shares its first or last 4 characters with one you've saved or paid but is different, you get a warning, re-authentication and a typed confirmation. This defends against address poisoning.
• You re-type the last characters of new addresses, and dust from look-alike senders is flagged.

Sign-in and authentication

Your account is email + password, kept locally. The password is the encryption secret and is never stored or transmitted. You get 10 recovery codes at sign-up and must confirm you've saved them before you can sign anything.

• Password: strength-checked, with growing back-off after failed attempts.
• Biometrics: optional quick-unlock after a full sign-in, within the same session.
• Authenticator code: optional 6-digit codes from an authenticator app (TOTP). Replayed codes are rejected.
• Emailed code: an equal alternative to the authenticator. Codes expire after 10 minutes.

Sensitive actions such as exporting keys, enabling mainnet or raising caps need your password plus your second factor.

Auto-lock

TRK locks after 5 idle minutes by default (adjustable from 1 to 60) and after at most 8 hours in total. On lock, keys are wiped from memory and pending approvals are cancelled. It also locks when you close the session, and you can lock manually at any time.

Spending caps

Set per-transaction and 24-hour spending caps per network when you create your account. Caps count the amount, the TRK fee, network fees and any account rent.

• Over a cap: a loud OVER SPENDING CAP warning, re-authentication and a typed confirmation. Otherwise nothing is signed.
• Raising or removing a cap needs your password (and second factor when enabled).

Mandatory transaction preview

Nothing is signed without a preview, for every signature. It shows:

• A plain-language summary of what the transaction does.
• Amount and token, and every fee on its own line, including the 1% TRK fee.
• Destinations and the programs involved, named in plain words. Unknown programs get a warning.
• Simulated balance changes, the network badge and your spending-cap status.

The default answer is No. Dangerous instructions, such as handing over control of your wallet or token accounts, are hard-blocked.

Bot warnings (No-bots policy)

There is no auto-approval anywhere in TRK. Known trading-bot domains and handles are blocked with a warning, and automated paths are hard-blocked. If you open a bot-flagged link yourself, you see the full warning and must type I ACCEPT THE RISK to continue.

Status page

A public, read-only status page shows the health of the Solana RPC endpoints TRK uses and of its other services, plus incidents, known issues and update history. No sign-in needed.

Open the status page