Padre Terminal FAQ: The Official Answers, Recovered and Checked

The official Padre and Terminal FAQ is gone. Not moved, not replaced. docs.padre.gg sends every path to a sign-in wall, and the FAQ went with it.

Google still lists it. People still search for it. So here it is, recovered from a Wayback capture dated 8 January 2026, with each answer checked against the app as it runs today.

The password answer, which is the one that costs money

Taking this out of order, because it is the only answer here where getting it wrong is permanent. The official FAQ said:

"Unfortunately, there is no way to recover a forgotten password. For security reasons, Padre team does not have access to your password at any point, only you know it. Since all private keys to your wallet are encrypted with this password, we strongly recommend exporting your private keys and securely storing them offline. This precaution ensures you retain access to your funds even if your password is lost or forgotten."

That is the publisher's own wording, and it has not softened with time. We found no password reset route anywhere in the shipped application when we read its code, so as far as we can establish this is still how it works.

The upside of the same design is real and worth stating: this is what non-custodial actually means in practice. Nobody at the company can be compelled to hand over your keys, because they do not hold the password that decrypts them. That is a genuine security property, and the cost of it is that recovery is on you.

Enlarge

Finding things in the interface

Four of the original answers are pure navigation. They are still the fastest route to things people hunt for.

Your user ID. Open Account Overview using the person icon in the upper right. The ID sits just below your email or Telegram account details, labeled ID, and clicking it copies it. Support tickets want this, so find it before you need it rather than while something is broken.

Your PnL card. Open the Portfolio tab in the top bar, go to Open Positions or Closed Positions, then Position Overview on the trading page, and click the trophy icon next to your profit. One detail the documentation mentioned and most people miss: the generated card contains a QR code of your referral link. Worth knowing before you post one publicly, in either direction.

Your order ID. Open the Order History tab on the token page, click Status to open the order details, then click the copy icon next to the Order Summary title. Every failed trade in Terminal renders an error ID and asks you to open a support ticket with it, so this is the companion to the error catalog.

The lighter color scheme. Settings via the gear icon in the upper right, then the Colors tab, then toggle Lighter colors.

Signing in on mobile

Terminal has no native mobile app. It is a progressive web app, which is a point the web gets wrong often enough that it is worth repeating here.

The documented sign-in route: open Account Overview using the person icon, expand the "Sign in on mobile" section, then open the app on your phone and choose the QR code login method. Scan the code from Account Overview and you are in.

If you are looking for a Terminal download in an app store, there is not one, and anything presenting itself as an official Terminal mobile app deserves a hard look. We list the domains we can confirm as official, and several lookalikes that are not, in is padre.gg safe.

The errors and warnings the FAQ covered

The original page carried a short errors section. It overlaps with our own catalog, which we transcribed from the app rather than the docs, and the two agree.

Transaction timed out

The official causes, verbatim in substance:

Your wallet balance was too low at the moment of the transaction to cover both the size of the trade and its cost. Or two trades were sent at around the same time, for instance a limit order triggering in the background while you sent a market order. Or your slippage tolerance was exceeded before the transaction could confirm.

That third one is the common case and it connects to the most expensive default in the app. Terminal ships with 20% slippage in the standard interface, which is a setting that quietly eats small trades. Why slippage settings lose money on Terminal works through the arithmetic with a real user's numbers.

Freezable accounts

"When freeze authority is enabled, the token developer can block users from selling their position in that token. Be extremely cautious with tokens that have freeze authority enabled and always check Data & Security for potential red flags."

This is the documentation for the Account Frozen error you will eventually see in the app. Freeze authority is a property of the token, set by whoever deployed it, and it is visible before you buy in the Data and Security panel. Terminal routes orders to venues; it does not vet the tokens on them, and anyone can deploy one permissionlessly. Checking that panel is on you, and the Trenches guide covers which safety signals are worth reading.

Sell Initials: Insufficient Amount

"When the market price drops below your entry, your holding won't be able to cover the initial investment and you'll see this message."

Sell Initials takes your original stake back off the table by selling however much of the position covers it. If the position is now worth less than you put in, there is nothing to take back, and the warning says so. It is a fact about the position, not a malfunction. Terminal's full set of exit tools is in order types and exit strategies.

Charts not loading from Telegram links

Not a Terminal problem, and the fix is on Telegram's side. Charts and some other features do not render correctly inside Telegram's built-in browser. To change it: open Telegram, go to Settings, then Data and Storage, scroll to Other, tap "Open Links in", and switch from Telegram's internal browser to your default browser.

What this page does not answer

Worth being explicit about the gaps, because an archive can look more authoritative than it is.

The original FAQ was thin. It covered eleven questions across navigation and errors, and it did not touch fees, chain support, custody beyond the password answer, or anything about the rewards mechanics. It also predates a lot of the current product: since this capture, Terminal has shipped features that no documentation covers at all, which we went through in Terminal's undocumented features.

For the things the FAQ never covered, our own pages are more current than this one by construction, because they were written from the running app: fees and how they stack, what the rewards tabs do, and the full error catalog.

Provenance

Source: docs.padre.gg/padre-v2/faq, recovered from an Internet Archive capture dated 8 January 2026. The page reported itself as last updated about a month before that, so its answers describe the application around December 2025, after the pump.fun acquisition and before the documentation went offline.

We have edited for readability and checked each answer against the running app, flagging where things have moved. We have not changed what the answers say. Where our own reporting disagrees with the archived text, the disagreement is marked in place rather than resolved silently.

The rest of what we recovered, and how, is in the documentation archive.