The universal onchain payment rail. Support: support.relay.link
New York
- Tweets 11,138
- Following 29
- Followers 69,016
- Likes 8,055
Pinned Tweet
Announcing Relay's $17M Series B, led by @archetypevc & @USV.
And we're launching the Relay Chain — purpose-built infrastructure for instant crosschain settlement ⛓️
Any asset, any chain, instantly.
569
187
2,194
495,420
OUSD is now live on Relay.
Stablecoins are spreading across more chains. Getting between them should be the simplest part.
relay.link/bridge
13
5
97
5,743
X Layer is live on Relay.
Start from any chain Relay supports and receive USDC or OKB on @XLayerOfficial
relay.link/bridge/xlayer
24
12
144
10,558
Relay Chain is on track to post more data to Celestia in September than in the previous seven months combined.
This growth is driven by activity across apps using @RelayProtocol for crosschain swaps, including @fomo, which has over 1 million registered users.
38
65
342
51,478
Relay is live on @Arc.
Pay with what you already hold, on any chain Relay supports, and settle on Arc in seconds. No pre-funding, no separate step.
42
30
531
22,091
Building on Arc? One integration accepts payment from across the onchain economy and settles in the currency your application uses. No per-chain work.
Start here: docs.relay.link
1
1
9
4,842
Any chain in, one currency out.
@Mesh accepts payment from 300+ wallets and exchanges. The merchant gets one asset, on one network.
Wallet or deposit address: it's the same rail underneath.
15
5
449
9,992
"Fragmentation is diverging, not converging. More networks, more tokens, more assets."
@meshpay CTO Arjun Mukherjee on why the merchant still has to get paid in one currency, whatever the customer holds
2
1
13
3,337
We are always looking for smart people to join us at @RelayProtocol on the solving team.
If you like moving fast and working on novel problems in crypto value transfer, check out the job board in the replies for more details!
feel free to send over a DM if you fill it out!
32
11
335
23,130
You can now see exactly how your requests are performing on Relay 👀
The Observability tab charts request volume for each of your API keys, by endpoint and status code.
So you can:
→ See how much headroom you have on every endpoint
→ See which endpoint a change in traffic came from
→ Check what is happening now, minute by minute, not yesterday
How it works: relay.link/blog/request-obse…
18
6
119
10,195
Start from what you already hold.
Crosschain zaps are live on Portals Explorer, running on Relay ⚡️
Any token, any chain we support, into the position you picked.
Cross-chain is now live on the Portals Explorer, powered by @RelayProtocol
Move into any opportunity from almost any asset, across major blockchains, in one flow. No manual bridging needed.
18
2
137
12,021
Relay retweeted
TLDR:
Relay is not compromised, nor does it ever do unlimited approvals. But there is definitely heightened phishing activity that you need to watch out for.
More detail:
- There are phishing sites out there that send txs through our router (which is basically just a multicall contract), to try and trick people. Make sure you are on the correct domain for whichever app you are using!
- Because of an uptick in this activity, Blockaid is now showing a warning on our contract to try and warn people. They've whitelisted all the major legit sites, so it won't show on those sites. So if you're seeing the warning, you are either on phishing site, or another site needs to be added to the list (let us or Blockaid know)
- We are planning to update our router to make it harder for phishers to abuse. To be clear, there is no protocol or contract vulnerability. Any multicall contract is open ended by design, and can be used by an attacker to mask a malicious transaction. We will just limit what ours allows, to make harder for bad actors to piggyback on it. It won't stop people landing on phishing sites (which is the actual problem), but will minimize some of the confusion
9
11
76
7,490
$GRAM is live on Relay.
Swap GRAM to and from tokens on 85+ chains, in seconds.
Available now in the app and API.
relay.link/bridge/ton
41
14
384
20,995
Building on TON? The API supports $GRAM in both directions.
Docs: docs.relay.link/
3
20
6,198
A user sends 100 USDC. 99.80 USDT arrives.
Nothing failed. Fees came out in flight, and two dollar-pegged assets never trade at exactly 1:1. In payments, that reads as broken.
Relay supports exactly 1:1 stablecoin payments. Two mechanisms, run together:
43
17
371
51,211
Fee sponsorship: cover your users' fees from your own balance. All destination fees or specific components, capped per transaction.
Fixed rates: lock the quote so peg drift never reaches the user. The variance cuts both ways and is expected to net out.
Quote 1:1 in your product and mean it. One integration, 85+ chains, sub-3-second settlement.
How it works: relay.link/blog/one-to-one-s…
2
1
33
4,486
85+ chains, 186M transactions, $40B enabled volume ✨
Try it now:
relay.link/bridge/tron?toCur…
11
2,322
Complete visibility into your onchain payments with Requests v3
At real volume, the gap between what happened and what you can see is an operational problem. The Requests page in the Relay Dashboard now closes it: near real-time data on every request, filters you can compose across status, chains, currencies, amounts, addresses, and time.
Every USDC payment over $10k that landed this week? One query. Save it as a view and it's one click tomorrow.
On requests/v2? Migrate to requests/v3 by Nov 24, 2026 🧵
17
2
138
11,407
Under the hood: Requests v3, rebuilt on Elasticsearch.
One term finds any request: ID, wallet, deposit address, or any tx hash. Near real-time data that v2 couldn't give you. Cleaner responses with quoted vs actual on every fee. Per-key access, so heavy usage never slows anyone else.
Everything the Dashboard can do, your own tooling can do directly via GET /requests/v3.
1
2
15
2,387
requests/v2 is deprecated as of today, with a 4-month migration window before it retires.
The migration guide covers every change, and updated SDKs (RelayClient and RelayKit) do most of the work: docs.relay.link/references/a…
Note: Requests v3 authenticates with an API key. Create one in the Dashboard.
1
7
1,191