Website blueprint · 11 h ago

backed.trade

“BACKED: memecoins, now backed”

Template-written 50 evidence items REA analysed 1 scripts

What this means for you

BACKED only talked to its own servers while we watched.E1

Tech check: the site claims on-chain / smart contracts, and its public page shows matching evidence.E49 E47 E48
We saw no known analytics or advertising services load on the first visit.E1
Its code can ask your wallet to sign transactions. Read every wallet pop-up before approving.E47

Tech check

What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.

Evidence found

On-chain / smart contracts

“…itions Rules and custody $BACKED 7fRm…cZ49 The $BACKED contract address appears here at launch, and nowhere else first. Every…”E49

Wallet requests in its code: signTransaction, signMessageE47 E48

Calls its own backend /api/traces, /api/config, /api/statsE10 E11 E12 E13

Wallet code signTransaction, signMessageE47 E48

Contract calls in its code none seen

Talks to AI services none seen

Live connections receives a live stream of updates from a serverE9

What it is

The Internet Archive first saved this site on 2018-08-21 (2990 days ago).E50
The site describes itself as: “Lock SOL or supply behind your pump.fun coin. Fixed rules decide when holders get it. Promises are easy. Backing is onchain.”E2
It's built with React (common tools for building web apps).E7
In your browser it saves small bits of data in your browser and receives a live stream of updates from a server.E8 E9
It has sections such as /explore, /back, /me, /rules, /b and /token.E35 E36
While loading, it called 5 endpoints on its own servers, such as /api/traces, /api/config, /api/stats and 2 more.E10 E11 E12 E13

Where your data goes

On a first visit the page only talked to its own servers (backed.trade).

Crypto and wallets

signTransaction: asks a wallet to sign transactions (often Solana wallets).E47
signMessage: asks a wallet to sign a message.E48

How key features work

What it can ask your wallet to sign

Its code can ask your wallet for signTransaction. Each of these opens a wallet pop-up you must approve; read it before you click.E47

signTransaction

Sign-in and accounts

Sign-in and account features show up in its code or traffic (/v1/auth/challenge and /v1/auth/verify).E21 E22

/v1/auth/challenge/v1/auth/verify

Live updates

It keeps live connections open (server-sent events) so content updates without reloading.E9

event_source

Loading its content

Its content loads from its own API while you browse (/api/traces, /api/config, /api/stats, /api/feed and 1 more).E10 E11 E12 E13 E14

/api/traces/api/config/api/stats/api/feed/official.json

Saving data on your device

It saves data in your browser (localStorage and sessionStorage), so some things persist between visits.E8 E6

local_storagesessionStorage

Cookies and storage

Names only. We never store the values.

sessionStorageE6: bk.v3open

Pages and API calls

Pages it links to

//explore/back/me/rules/b/token_film*exploreb/:idtoken/:mintbackmerules/v2/*/v3/*/*

Endpoints

Called while loading (seen) or named in the code (code).

backed.trade/api/traces	seenE10
backed.trade/api/config	seenE11
backed.trade/api/stats	seenE12
backed.trade/api/feed	seenE13
backed.trade/official.json	seenE14
/official.json	codeE15
/v3/*	codeE16
/v2/*	codeE17
/*	codeE18
/api/stream	codeE19
/v1/config	codeE20
/v1/auth/challenge	codeE21
/v1/auth/verify	codeE22
/v1/tokens	codeE23
/v1/tokens/stream	codeE24
/v1/launch/prepare	codeE25
/v1/launch/prepare-and-mint	codeE26
/v1/launch/submit	codeE27
/v1/launch/cosign	codeE28
/v1/trade/quote	codeE29
/v1/trade/buy	codeE30
/v1/trade/sell	codeE31
/v1/tx/submit	codeE32
/v1/creator/claim	codeE33
/api/history	codeE34

Evidence

Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.

Page title: BACKED: memecoins, now backed

page title · https://backed.trade/

Page description: Lock SOL or supply behind your pump.fun coin. Fixed rules decide when holders get it. Promises are easy. Backing is onchain.

page description · https://backed.trade/

Site name: BACKED

page site_name · https://backed.trade/

Main heading: Memecoins. Now backed.

page h1 · https://backed.trade/

15 request(s) to backed.trade

types: 5 fetch, 2 font, 2 image

GET https://backed.trade/ · fetch · 15 requests · network recording

sessionStorage: 1 key(s) saved in your browser

sessionStorage keys: bk.v3open · values not stored

React detected by REA (react-runtime)

confidence: medium

backed.trade/assets/index-BbM64Zgz.js · “react-runtime” · REA analyze-web-bundle 6.4.0

Uses the browser ability: local_storage

saves small bits of data in your browser

backed.trade/assets/index-BbM64Zgz.js @ 191:40780 · “localStorage.setItem(” · pattern scan

Uses the browser ability: event_source

receives a live stream of updates from a server

backed.trade/assets/index-BbM64Zgz.js @ 189:7958 · “new EventSource(” · pattern scan

E10

The page called /api/traces on backed.trade (GET)

GET https://backed.trade/api/traces · fetch · network recording

E11

The page called /api/config on backed.trade (GET)

GET https://backed.trade/api/config · fetch · network recording

E12

The page called /api/stats on backed.trade (GET)

GET https://backed.trade/api/stats · fetch · network recording

E13

The page called /api/feed on backed.trade (GET)

GET https://backed.trade/api/feed · fetch · network recording

E14

The page called /official.json on backed.trade (GET)

GET https://backed.trade/official.json · fetch · network recording

E15

REA found the endpoint /official.json

how: call:fetch

backed.trade/assets/index-BbM64Zgz.js @ 189:7742 · “/official.json” · REA analyze-web-bundle 6.4.0

E16

REA found the endpoint /v3/*

how: property:path

s00-index-BbM64Zgz.js · “/v3/*” · REA analyze-javascript-application 6.4.0

E17

REA found the endpoint /v2/*

how: property:path

s00-index-BbM64Zgz.js · “/v2/*” · REA analyze-javascript-application 6.4.0

E18

REA found the endpoint /*

how: property:path

s00-index-BbM64Zgz.js · “/*” · REA analyze-javascript-application 6.4.0

E19

The code names the endpoint /api/stream

backed.trade/assets/index-BbM64Zgz.js @ 189:7975 · “/api/stream” · pattern scan

E20

The code names the endpoint /v1/config

backed.trade/assets/index-BbM64Zgz.js @ 191:1673 · “/v1/config” · pattern scan

E21

The code names the endpoint /v1/auth/challenge

backed.trade/assets/index-BbM64Zgz.js @ 191:1726 · “/v1/auth/challenge” · pattern scan

E22

The code names the endpoint /v1/auth/verify

backed.trade/assets/index-BbM64Zgz.js @ 191:1818 · “/v1/auth/verify” · pattern scan

E23

The code names the endpoint /v1/tokens

backed.trade/assets/index-BbM64Zgz.js @ 191:1934 · “/v1/tokens” · pattern scan

E24

The code names the endpoint /v1/tokens/stream

backed.trade/assets/index-BbM64Zgz.js @ 191:2343 · “/v1/tokens/stream” · pattern scan

E25

The code names the endpoint /v1/launch/prepare

backed.trade/assets/index-BbM64Zgz.js @ 191:2940 · “/v1/launch/prepare” · pattern scan

E26

The code names the endpoint /v1/launch/prepare-and-mint

backed.trade/assets/index-BbM64Zgz.js @ 191:3046 · “/v1/launch/prepare-and-mint” · pattern scan

E27

The code names the endpoint /v1/launch/submit

backed.trade/assets/index-BbM64Zgz.js @ 191:3466 · “/v1/launch/submit” · pattern scan

E28

The code names the endpoint /v1/launch/cosign

backed.trade/assets/index-BbM64Zgz.js @ 191:3619 · “/v1/launch/cosign” · pattern scan

E29

The code names the endpoint /v1/trade/quote

backed.trade/assets/index-BbM64Zgz.js @ 191:3791 · “/v1/trade/quote” · pattern scan

E30

The code names the endpoint /v1/trade/buy

backed.trade/assets/index-BbM64Zgz.js @ 191:3935 · “/v1/trade/buy” · pattern scan

E31

The code names the endpoint /v1/trade/sell

backed.trade/assets/index-BbM64Zgz.js @ 191:4087 · “/v1/trade/sell” · pattern scan

E32

The code names the endpoint /v1/tx/submit

backed.trade/assets/index-BbM64Zgz.js @ 191:4227 · “/v1/tx/submit” · pattern scan

E33

The code names the endpoint /v1/creator/claim

backed.trade/assets/index-BbM64Zgz.js @ 191:4353 · “/v1/creator/claim” · pattern scan

E34

The code names the endpoint /api/history

backed.trade/assets/index-BbM64Zgz.js @ 195:4163 · “/api/history” · pattern scan

E35

23 links to pages on the same site

page links · https://backed.trade/ · /, /explore, /back, /me, /rules, /b, /token

E36

REA found the route _film

backed.trade/assets/index-BbM64Zgz.js @ 193:14905 · “_film” · REA analyze-web-bundle 6.4.0

E37

REA found the route *

backed.trade/assets/index-BbM64Zgz.js @ 193:14951 · “*” · REA analyze-web-bundle 6.4.0

E38

REA found the route explore

backed.trade/assets/index-BbM64Zgz.js @ 193:15060 · “explore” · REA analyze-web-bundle 6.4.0

E39

REA found the route b/:id

backed.trade/assets/index-BbM64Zgz.js @ 193:15108 · “b/:id” · REA analyze-web-bundle 6.4.0

E40

REA found the route token/:mint

backed.trade/assets/index-BbM64Zgz.js @ 193:15154 · “token/:mint” · REA analyze-web-bundle 6.4.0

E41

REA found the route back

backed.trade/assets/index-BbM64Zgz.js @ 193:15206 · “back” · REA analyze-web-bundle 6.4.0

E42

REA found the route me

backed.trade/assets/index-BbM64Zgz.js @ 193:15251 · “me” · REA analyze-web-bundle 6.4.0

E43

REA found the route rules

backed.trade/assets/index-BbM64Zgz.js @ 193:15294 · “rules” · REA analyze-web-bundle 6.4.0

E44

REA found the route /v2/*

backed.trade/assets/index-BbM64Zgz.js @ 195:6452 · “/v2/*” · REA analyze-web-bundle 6.4.0

E45

REA found the route /v3/*

backed.trade/assets/index-BbM64Zgz.js @ 195:6498 · “/v3/*” · REA analyze-web-bundle 6.4.0

E46

REA found the route /*

backed.trade/assets/index-BbM64Zgz.js @ 195:6544 · “/*” · REA analyze-web-bundle 6.4.0

E47

Wallet request in code: signTransaction

asks a wallet to sign transactions (often Solana wallets)

backed.trade/assets/index-BbM64Zgz.js @ 191:4506 · “signTransaction” · pattern scan

E48

Wallet request in code: signMessage

asks a wallet to sign a message

backed.trade/assets/index-BbM64Zgz.js @ 191:8576 · “signMessage” · pattern scan

E49

The site says: “…itions Rules and custody $BACKED 7fRm…cZ49 The $BACKED contract address appears here at launch, and nowhere else first. Every…”

page text · https://backed.trade/ · …itions Rules and custody $BACKED 7fRm…cZ49 The $BACKED contract address appears here at launch, and nowhere else first. Every…

E50

The Internet Archive first saved backed.trade on 2018-08-21 and has snapshots from 8 different days

page web archive · https://web.archive.org/web/20180821002346/backed.trade

Limits

We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
Some trackers only load after you accept cookies or log in, so the real list can be longer.
We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
The tech check compares the site's own words with what its public page loads. Work done on servers, in private code or in separate apps isn't visible here, so 'nothing found' means not visible on the public page, not that it doesn't exist.
This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
REA hit its size budget on parts of 1 large bundle file(s); those parts weren't fully analysed.

Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id 6drrvVxx.