Terminal: the Padre rebrand does not change the wallet boundary
Terminal combines multi-chain discovery, hosted wallets, rapid execution, and persistent exits. The current name matters for avoiding impostors; the account, key, routing, and automation model matters for protecting funds.
The short answer
Terminal, formerly Padre, is a web and PWA trading terminal for Solana, Ethereum, Base, and BNB Chain, with Ethervista included in its Ethereum coverage. It offers discovery feeds, token analytics, wallet tracking, market orders, buy-dip orders, take-profit and stop-loss orders, trailing stops, position-based limits, exit strategies, and a Solana submission mode called Inferno.
Terminal and Padre currently refer to the same product lineage
The official documentation is titled “Terminal (formerly Padre),” while the application and many help pages still use padre.gg domains and Padre wording. That mixed branding is expected during the transition, but it creates an opening for lookalike domains and fake support accounts.
Start from the official docs and follow their application link. Save the exact domains, verify any PWA installation source, and never import a key or enter an account password after following a direct message, sponsored search result, or copied social link.
“Non-custodial” still includes hosted account dependencies
Terminal says its wallet system uses Turnkey, 2FA, and encryption tied to a user-created password, and that the Terminal team cannot access user keys. The wallet guide supports creating chain-specific wallets, importing a private key, exporting a private key, and managing withdrawal addresses. Those are useful recovery controls.
They do not make the wallet hardware-local. Trading still depends on a Terminal account, its authentication and session controls, Turnkey infrastructure, browser integrity, and the platform's transaction path. Treat the security page as an architectural claim to evaluate, not an audit result. Use a unique password and 2FA, review sessions, test export and independent recovery, and never import a primary wallet. See wallet compartmentalization for a safer balance split.
Trending activity and token labels are leads, not verdicts
Terminal's trending and new-pair views filter by chain, DEX, volume, market cap, buys, and sells. Token pages add pair age, price, liquidity, socials, holder and insider fields, and a liquidity-lock indicator. This makes the interface efficient for triage, not proof of safety.
A lock constrains specified LP tokens under a particular locker and term; it does not rule out mint authority, token taxes, owner controls, concentrated holders, a second pool, or insider selling. Terminal's glossary defines an insider through block-zero activity or transfers from another labeled insider. That is a useful heuristic, not proof of common identity or intent. Verify the contract, pool, authorities, locker, holder graph, and executable liquidity onchain.
Every chain gives the same controls different consequences
On Solana, Terminal exposes priority fees, builder tips, slippage, and MEV routing. On EVM networks it exposes gas priority, slippage, and chain-dependent MEV protection; the current docs say the protection option is unavailable on Base. Tips, private paths, and priority settings can change landing probability, but none guarantee a fill or a fair price.
Documentation screenshots and examples use values such as 20% slippage. An example is not a safe preset. Derive the maximum tolerance from pool depth, trade size, taxes, route, volatility, and the worst price you will accept. Verify the output quoted before submission and the amount actually received.
Dynamic exits solve sizing drift but add state dependence
Terminal supports fixed limit orders and position-based orders that dynamically size from current holdings. Position-based orders can stay proportional after a partial exit or added buy. Exit Strategies can attach as many as five independent take-profit or stop-loss conditions to a market or buy-dip order, while trailing stops follow a peak before submitting a sell.
These instructions depend on Terminal's view of the position. External transfers, trades in another interface, stale prices, taxes, liquidity changes, or failed transactions can make the intended percentage differ from the executable result. A trigger submits a market sell; it does not guarantee the trigger price. Audit active orders after every manual action and verify whether an exit can be edited or must be cancelled and recreated.
Separate platform fees, routing costs, and cashback
An official Padre deck published through the product's domain states that trades incur a 1% fee. Current referral documentation describes 35% cashback for referred users and fee shares for referrers, excluding gas and taxes. Because the published materials differ by age and surface, confirm the actual percentage and rebate in the live order preview before trading.
Add DEX or launchpad charges, network gas, priority fees, builder tips, token taxes, approval costs on EVM chains, price impact, slippage, failed or reverted paths, and each automated exit. Record cashback only when credited, not as an assumed discount at execution.
A safer evaluation workflow
- Resolve the rebrand through official docs. Save the current app domain, support path, and PWA source before creating an account.
- Create a dedicated wallet. Enable the strongest authentication, export the key, recover it independently, and fund a minimal balance.
- Verify one token view. Match chain, contract, pool, liquidity, lock conditions, authorities, holders, and insider evidence to an explorer.
- Build one conservative preset per chain. Set explicit slippage, priority, tip, and MEV choices from the route rather than the screenshot.
- Test one tiny order. Compare the quote, platform fee, every submitted signature, landed output, and final wallet delta.
- Test automation separately. Measure trigger, fill, dynamic sizing, cancellation, partial exits, and behavior after an external transfer.
What belongs in the journal
Record the product domain and displayed name, chain, wallet, contract and pool, discovery claims, explorer evidence, order type, fixed or position-based sizing, exit conditions, slippage, priority and tip, MEV or Inferno mode, every signature, platform and venue costs, cashback status, actual output, and timestamp.
Primary sources
Turn the terminal into evidence
Reconstruct the wallet, route, and active exit state.
A renamed interface is still accountable to transaction-level outcomes.
Open the journal