Pinned Tweet
🔒 Staying safe around QDay
Every official QDay link, channel and contract is listed in one place: qday.io/official-links
We never DM first, and we never ask you to send tokens to "migrate" or "unlock" them. QDay will never ask for your private key or seed phrase.
Other projects may use a similar name. If it isn't on that page, it isn't us.
New on qday.io: The Q-Day Threat.
Q-Day years in headlines come from four kinds of source: a survey, a model, a hardware target, a migration deadline. Only the first two try to say when the machine will exist.
We sorted them, plus what would break on a chain. 👇
Thanks @DoraHacks for featuring us 🙌
Aevum Builder Challenge #1: ship a stablecoin payment app on the Aevum testnet using tUSD8.
💰 $1,500 USDT prize pool
🗓 Registration and starter kit open Nov 16
🛠 Build window Nov 16 → Dec 11
Pre-register 👇
dorahacks.io/hackathon/qday/…
Hackathon Newsletter, November Issue II: Catch the latest hackathons from @mozilla , @QDayOfficial , @Somnia_Network , @0xReactive, @binance , @bchbliss , and more!
Read more👇dorahacks.io/blog/news/dora-…
Some x402 servers answer V1 and V2 clients in one response.
In our Nov 4 sample, 40 listings on 8 hosts (two domains) put the V2 price in the PAYMENT-REQUIRED header and a V1 copy in the JSON body.
E.g. header: eip155:8453, amount. Body: "base", maxAmountRequired.
The sample, the method and its limits: qday.io/news/http-402-paymen…
60
One 402, two ways to pay.
In our Nov 4 sample of x402 listings, 6 hosts, Exa's search API among them, also sent an MPP challenge (WWW-Authenticate: Payment) on the same 402 as the x402 PAYMENT-REQUIRED header.
A client that speaks either protocol gets a challenge it can read.
3
3
197
How to tell the kinds of 402 apart: qday.io/news/http-402-paymen…
47
A real x402 price, captured Nov 4 and decoded:
network eip155:8453 is Base mainnet.
asset 0x8335…2913 is USDC, 6 decimals.
amount 5000 is $0.005.
One call, half a cent, quoted in a Base64 header on the 402.
1
4
200
How to read a 402 like this one, and what 157 live x402 endpoints sent back: qday.io/news/http-402-paymen…
1
36
Two kinds of HTTP 402 are in use: a price to pay, or a billing error. The headers tell you which.
PAYMENT-REQUIRED: an x402 price.
WWW-Authenticate: Payment: an MPP challenge.
No payment header at all, plus an error code in the body: billing. Fix the account.
2
75
The full explainer, with the history of 402 and live x402 data: qday.io/news/http-402-paymen…
34
A good rule for agents, from OpenRouter's docs on HTTP 402:
An OpenRouter 402 means the account or key has insufficient credits.
Without a Retry-After header, it is not a wait-and-retry case.
The OpenAI, Anthropic, Vercel AI and OpenRouter SDKs don't retry a 402 on their own.
2
6
224
What each kind of 402 means and how to fix it: qday.io/news/http-402-paymen…
1
41
We sent one unpaid request to each of 500 listings sampled from Coinbase's public x402 directory.
340 sat on one host that returned errors or nothing at all.
Of the other 160, 157 answered with a 402 and an x402 payment header.
A directory listing doesn't show a service is up.
3
1
110
How we sampled, what the 157 sent back, and the limits of the sample: qday.io/news/http-402-paymen…
54
On the screen at Booth 06 today: a walkthrough of Signet, from merchant withdrawals to agent identity. Signet is coming soon.
At Booth 06, Seaview Concourse, today for the Agentic Economy Summit at @cyberport_hk Venture & Capital Forum.
On the booth screen: a walkthrough of Signet, from merchant withdrawals to agent identity. Signet is coming soon; QDay is live on Aevum Testnet.
Visa says merchants' bot detection "can mistakenly block legitimate agentic transactions".
Its fix: agents sign their requests with HTTP Message Signatures, so a merchant can recognize them.
Onchain, ERC-8004, still a draft, gives each agent a portable identifier.
2
1
150
Visa, Oct 2025: usa.visa.com/about-visa/news…
ERC-8004: eips.ethereum.org/EIPS/eip-8…
Our guide: qday.io/news/agentic-payment…
42
In 1992, HTTP's status codes already had 402 Payment Required: the server named the charging schemes it accepts, the client retried with a ChargeTo header.
Since 1997 the spec has said only "reserved for future use."
x402 now puts it to work: price in the response, pay, retry.
What a 402 means today, how to tell a billing 402 from a payment request, and what 157 live x402 endpoints sent back: qday.io/news/http-402-paymen…
1
1
52
An AI agent pays in one of two ways today.
It carries a scoped token through a merchant's checkout, on card rails.
Or it pays per request: the server answers HTTP 402, the agent pays and retries, usually in stablecoins.
What each way needs before it works 👇
1
3
156
Agentic Payments: How AI Agents Pay, and What Has to Be True First
qday.io/news/agentic-payment…
51
An API charging AI agents $0.002 per call can't settle each call at Stripe's minimums.
Cards via shared payment tokens: 0.50 USD minimum, or 250 calls.
Stablecoins: 0.01 USDC minimum, or 5 calls.
Sub-cent pricing needs batching first, like x402's batch settlement on EVM chains.
3
6
216
Minimums: docs.stripe.com/payments/mac…
x402 batch settlement: github.com/x402-foundation/x…
55













