motion for Chrome · 1.0.17

Trade from GMGN, Axiom and fomo with your motion account

Open a Robinhood Chain, BNB or Solana coin on gmgn.ai, axiom.trade or fomo.family and a Trade in Motion button appears next to the site's own trade box. It opens a side panel with the motion ticket — the same login, the same wallets and the same balances you use on motion.gift. Your keys stay in your motion vault (vault.motion.gift); the extension holds none.

Download for Chrome Read the source
SHA-256—

Installed from this page as a developer-mode extension (four steps below). Chrome Web Store listing: coming soon — both installs use the same motion account.

gmgn.ai/robinhood/token/…
PAD$20.0K+38.4%1m
▸▸ Trade in Motion
Keys stay in your motion vault
motion0.21 ETH
PADROBINHOOD$0.0000200
0.010.050.10.5
10%25%50%100%
Illustration of the side panel on a GMGN coin page.

Install in four steps

  1. motion-extension-1.0.17.zip
    →
    motion-extension
    Download and unzip Unzip into a folder you keep — Chrome loads the extension from that folder, so don't delete it afterwards.
  2. chrome://extensions
    Developer mode
    Turn on Developer mode Open chrome://extensions and switch on Developer mode (top right).
  3. Load unpacked
    →
    motion-extension
    Load unpacked Click Load unpacked and pick the unzipped folder (the one with manifest.json in it).
  4. Motion
    ▸▸ Trade in Motion
    Pin it and open a coin Pin Motion from the puzzle-piece menu, open a coin on GMGN, Axiom or fomo and press Trade in Motion. Log in once in the panel.

Chrome may show a notice about developer-mode extensions — that is expected for anything not installed from the Web Store.

Updating

Developer-mode installs don't update themselves. When a new version is out, the panel shows a quiet Update available row that links here. Download the new zip, unzip it over the same folder, then press the reload ↻ button on Motion in chrome://extensions. Your wallets live in your motion vault, not in the extension — nothing is lost by updating or reinstalling.

What it can access

  • gmgn.ai, axiom.trade, fomo.family — reads the address of the page you're on to show the Trade in Motion button on coin pages. Nothing is injected anywhere else.
  • motion.gift — your login and the vault page (which frames vault.motion.gift, where your keys are kept and sign), coin prices and your trade history. Balances and trades go through that vault page; the extension talks to no blockchain node itself.
  • Side panel and storage — the panel itself and your presets and panel settings. No tabs permission: the panel sees the address of the active tab only on the sites listed here.

What it can't do

  • Read your private keys. They are created and kept in the vault frame on vault.motion.gift; the extension only asks it to trade and gets back results.
  • Read other sites. It has no access outside the hosts listed on the left.
  • See your browsing history. It reads the address of the active tab only to know which coin to show.
  • Protect you from motion.gift itself. The vault's code is served by motion.gift. The extension keeps other sites, other extensions and the page you are on away from your wallets — but whoever controls motion.gift's servers controls trading on them, exactly as on the website.
  • Trade every venue. On Solana it trades pump.fun curves, PumpSwap and Meteora DLMM pools paired with SOL (other Solana venues get a clear "not supported" and a link to motion.gift); NEAR coins link to motion.gift.

Is it the same code as on GitHub?

Every file has a fingerprint — a SHA-256 hash, a long code computed from every byte of it. Change one byte and the fingerprint is completely different. So if two files have the same fingerprint, they are the same file.

  1. The zip you downloaded is the one we published. Its fingerprint is shown under the Download button above. Compute the fingerprint of your file and compare: 
    Windows:  certutil -hashfile motion-extension-1.0.17.zip SHA256
macOS:    shasum -a 256 motion-extension-1.0.17.zip
Linux:    sha256sum motion-extension-1.0.17.zip
    Same code → it's exactly our release. Different → don't install it.
  2. That release is built from the public code. The code is on GitHub, tagged with this version. Anyone can build it and get byte-for-byte the same files as in the zip — the steps are below and in the repository's README. We did it from a clean copy; so can you, or anyone you trust.
  3. Chrome loaded that folder. In chrome://extensions the Motion card shows version 1.0.17 and the ID nojealomoobhcodabdhmlajjfejeboec.

The keys themselves never live in the extension: they stay in the vault on vault.motion.gift, whose code is also public and checkable the same way — see the Security Center (press Run checks).

Read the source

The full source of this version — exactly the files the build reads, the build configs and the dependency lockfile — is published next to the download and on GitHub at github.com/motiongift/motion-extension. Build it yourself and compare with the zip above:

npm ci
npm run build        # writes dist/
diff -r dist path/to/unzipped-motion-extension
Download the source (.zip) Source on GitHub
SHA-256—

The manifest's key is the extension's public key; it fixes the extension id that the motion vault relay accepts. No private key, token or password is part of the extension or its source.

Chrome Web Store

A Web Store listing is coming soon. It will trade against the same motion account, so you can switch between the two installs whenever you like.