circle-questionFAQ

Your fastest route to clarity on common questions.

chevron-rightHow do you plan to monetize?hashtag

Right now everything is free. In the future, we plan to roll out trading features and make money through transaction fees, similar to existing trading platforms.

chevron-rightHow do I get an invite code?hashtag
  1. Like and repost our launch tweet ↗arrow-up-right

  2. Join our Telegram community: t.me/frontrun_communityarrow-up-right

  3. Share a screenshot of your repost with any admin in TG and we’ll send your invite code.

chevron-rightDoes my invite code expire? I’m getting an “invalid code” error.hashtag

Your invite code never expires. That message almost always appears when you’re signed in with a different email than the one that originally requested the code. Log in with the same account you used before, and the code will work. If you still have trouble, reach out to our teamarrow-up-right and we’ll sort it out right away.

chevron-rightIs the code open sourced? How can I audit it?hashtag

We’ve open-sourced the exact Plasmo build that we publish to the Chrome Web Store. This bundle contains every line of code that actually runs in your browser when you use the Frontrun extension.

We haven’t released the entire development repository because we work in a monorepo that also includes private packages and internal tooling unrelated to the extension. Those components contain proprietary logic and infrastructure code, so keeping them private protects both intellectual property and security.

By sharing the Plasmo build, we provide full transparency into what’s shipped to users while sensibly separating out non-essential, internal modules. If you’d like to audit the build, you can even paste it into ChatGPT for a line-by-line review: https://chatgpt.com/c/684bb27d-5ebc-8003-acb5-58f730904425arrow-up-right

chevron-rightWhy does Frontrun ask for these Chrome permissions? Is it really necessary—and is my data safe?hashtag

Frontrun only requests the minimum set of permissions required to deliver its in-browser tooling. Every permission has a specific, narrowly scoped purpose:

Permission
What we use it for
Why it matters to you

storage

Save your labels, watch-lists, and UI preferences locally.

Keeps your custom settings without needing a back-end database.

scripting

Inject lightweight scripts that add wallet labels, fee-cut indicators, and other overlays on X, Solscan, GMGN, etc.

Enables all the on-page insights you installed Frontrun for.

sidePanel

Show the Frontrun control panel.

Gives you a convenient place to review positions or toggle features.

webRequest

Efficiently intercept and cache extension data.

Reduces page-load overhead so overlays appear instantly.

windows

Open and manage popup windows (e.g., settings, login).

Keeps UX tidy by using native Chrome pop-ups instead of new tabs.

identity

OAuth sign-in to sync your settings across devices

Lets you carry labels and preferences from laptop to desktop if you turn it on.

  • Smaller footprint than most: This list is shorter than what you’ll find in many web-3 wallets (e.g., Phantom requests additional permissions for account management and transaction signing).

  • No clipboard access, ever: Frontrun has zero permissions to read or write your clipboard.

  • Privacy & security first: All logic runs client-side; no keystrokes, private keys, or browsing history are sent to our servers. The open-sourced Plasmo build lets you verify this yourself.

In short, each permission directly powers a feature you can see, and nothing more.

Last updated