Website report · 17 Oct 2026

www.quid.markets

“Got Liq? $QUID · Quantitative Upside Desk — the max long on pump.fun × Hyperliquid”

Template-written 26 evidence items Code reader analysed 17 scripts
What this means for you

$QUID · Quantitative Upside Desk 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.E25E22E23E21
  • Tech check: the site mentions staking / yield, but we found nothing behind it in what its public page loads.E26
  • We saw no known analytics or advertising services load on the first visit.E1
  • Its code can ask your wallet to sign structured data (logins, orders or off-chain approvals) and sign transactions. Read every wallet pop-up before approving.E22E23

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

“…and HYPE — the two tokens behind the biggest merger in on-chain trading. Winning trades buy back and burn $QUID. No bu…”E25

Wallet requests in its code: eth_signTypedData, signTransaction, eth_requestAccountsE22E23E21

Nothing found on the public page

Staking / yield

“…Winning trades buy back and burn $QUID. No buttons, no staking, no babysitting. Just hold. Copy CA 5pA7micXgknYakGvPp…”E26

No matching code, calls or services in what loaded for us.

Calls its own backend /api/market, /api/deskE14E15
Wallet code PhantomE9E22E23E21
Contract calls in its code none seen
Talks to AI services none seen
Live connections none seen

What it is

  • The site describes itself as: “$QUID, the Quantitative Upside Desk, turns its own creator fees into 10× longs on PUMP and HYPE on Hyperliquid. Realized profit buys back an”E2
  • It's built with Next.js and React (common tools for building web apps).E7E8
  • In your browser it can copy text to your clipboard, saves small bits of data in your browser and runs compiled WebAssembly code in your browser.E10E11E12
  • It has sections such as /ride and /docs.E20
  • While loading, it called 2 endpoints on its own servers, such as /api/market and /api/desk.E14E15

Where your data goes

On a first visit the page only talked to its own servers (www.quid.markets).

Crypto and wallets

  • Wallet tools in the code: Phantom.E9
  • eth_signTypedData: asks you to sign structured data (can be a login, an order or an off-chain token approval).E22
  • signTransaction: asks a wallet to sign transactions (often Solana wallets).E23
  • eth_requestAccounts: asks to connect your wallet, which shows the site your address.E21
  • 1 contract or wallet addresses are written into the code.E24
1 addresses found in the code
0x206977946376bdf2cfc44dfd9e3c01d4aa421c2e

Paste any of these into the box on the home page to get the contract's report.

How key features work

What it can ask your wallet to sign

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

eth_signTypedDatasignTransaction

Connecting your wallet

It connects to crypto wallets using Phantom, eth_signTypedData, signTransaction and eth_requestAccounts. Connecting shows the site your wallet address; it doesn't move funds by itself.E9E21

Phantometh_signTypedDatasignTransactioneth_requestAccounts

Loading its content

Its content loads from its own API while you browse (/api/market and /api/desk).E14E15

/api/market/api/desk

Drawing and editing in the browser

The page draws and edits graphics in your browser using WebAssembly and the canvas.E12E13

webassemblycanvas

Saving data on your device

It saves data in your browser (localStorage), so some things persist between visits.E11E6

local_storagelocalStorage

Cookies and storage

Names only. We never store the values.

localStorageE6: liq-sfx-muted

Pages and API calls

Pages it links to

//ride/docs

Endpoints

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

www.quid.markets/api/marketseenE14
www.quid.markets/api/deskseenE15
/api/marketcodeE16
api.hyperliquid.xyz/infocodeE17
api.hyperliquid.xyz/exchangecodeE18
/api/deskcodeE19

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.

E1
Page title: Got Liq? $QUID · Quantitative Upside Desk — the max long on pump.fun × Hyperliquid
page title · https://www.quid.markets/
E2
Page description: $QUID, the Quantitative Upside Desk, turns its own creator fees into 10× longs on PUMP and HYPE on Hyperliquid. Realized profit buys back and burns $Q
page description · https://www.quid.markets/
E3
Site name: $QUID · Quantitative Upside Desk
page site_name · https://www.quid.markets/
E4
Main heading: Got Liq? The max long on pump.fun × Hyperliquid. 10× PUMP. 10× HYPE.
page h1 · https://www.quid.markets/
E5
37 request(s) to www.quid.markets
types: 15 fetch, 11 script, 6 image
GET https://www.quid.markets/ · fetch · 37 requests · network recording
E6
localStorage: 1 key(s) saved in your browser
localStorage keys: liq-sfx-muted · values not stored
E7
Next.js detected by the code reader (next-runtime)
confidence: high
www.quid.markets/ · “next-runtime” · the code reader
E8
React detected by the code reader (react-runtime)
confidence: medium
www.quid.markets/_next/static/chunks/0mstyq17cbf8-.js · “react-runtime” · the code reader
E9
Phantom found in the code
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:247020 · “window.phantom” · pattern scan
E10
Uses the browser ability: clipboard_write
can copy text to your clipboard
www.quid.markets/_next/static/chunks/09jw-f62nlm9q.js @ 1:13106 · “clipboard.writeText(” · pattern scan
E11
Uses the browser ability: local_storage
saves small bits of data in your browser
www.quid.markets/_next/static/chunks/09jw-f62nlm9q.js @ 1:5586 · “localStorage.setItem(” · pattern scan
E12
Uses the browser ability: webassembly
runs compiled WebAssembly code in your browser
www.quid.markets/_next/static/chunks/turbopack-0qlwfpvkl4oaz.js @ 1:10349 · “WebAssembly.instantiateStreaming(” · pattern scan
E13
Uses the browser ability: canvas
draws graphics on a canvas
www.quid.markets/_next/static/chunks/09jw-f62nlm9q.js @ 1:14074 · “getContext("2d"” · pattern scan
E14
The page called /api/market on www.quid.markets (GET)
GET https://www.quid.markets/api/market · fetch · network recording
E15
The page called /api/desk on www.quid.markets (GET)
GET https://www.quid.markets/api/desk · fetch · network recording
E16
Code reader found the endpoint /api/market
how: call:fetch
www.quid.markets/_next/static/chunks/0~j0hltmbhk_y.js @ 37:8072 · “/api/market” · the code reader
E17
Code reader found the endpoint api.hyperliquid.xyz/info
how: call:fetch
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:246224 · “api.hyperliquid.xyz/info” · the code reader
E18
Code reader found the endpoint api.hyperliquid.xyz/exchange
how: call:fetch
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:246481 · “api.hyperliquid.xyz/exchange” · the code reader
E19
Code reader found the endpoint /api/desk
how: call:fetch
www.quid.markets/_next/static/chunks/09jw-f62nlm9q.js @ 37:6782 · “/api/desk” · the code reader
E20
3 links to pages on the same site
page links · https://www.quid.markets/ · /, /ride, /docs
E21
Wallet request in code: eth_requestAccounts
asks to connect your wallet, which shows the site your address
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:250010 · “eth_requestAccounts” · pattern scan
E22
Wallet request in code: eth_signTypedData
asks you to sign structured data (can be a login, an order or an off-chain token approval)
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:250476 · “eth_signTypedData_v4” · pattern scan
E23
Wallet request in code: signTransaction
asks a wallet to sign transactions (often Solana wallets)
www.quid.markets/_next/static/chunks/13odppa46cd1k.js @ 7:159793 · “signTransaction” · pattern scan
E24
Address in code: 0x206977946376bdf2cfc44dfd9e3c01d4aa421c2e
www.quid.markets/ (page HTML) @ 1:18735 · “0x206977946376bdf2cfc44dfd9e3c01d4aa421c2e” · pattern scan
E25
The site says: “…and HYPE — the two tokens behind the biggest merger in on-chain trading. Winning trades buy back and burn $QUID. No bu…”
page text · https://www.quid.markets/ · …and HYPE — the two tokens behind the biggest merger in on-chain trading. Winning trades buy back and burn $QUID. No bu…
E26
The site says: “…Winning trades buy back and burn $QUID. No buttons, no staking, no babysitting. Just hold. Copy CA 5pA7micXgknYakGvPp…”
page text · https://www.quid.markets/ · …Winning trades buy back and burn $QUID. No buttons, no staking, no babysitting. Just hold. Copy CA 5pA7micXgknYakGvPp…

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.
  • The code reader hit its size budget on parts of 6 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 zPIxOuYb.