Pinned Tweet
The chain should call you. Not the other way around.
GetBlock Webhooks are live on Ethereum.
β£ Wallet activity, contract logs, tx confirmations
β£ Up to 250K addresses per webhook
β£ Signed, retried, reorg-corrected
25 CU per delivery. One HTTPS endpoint is the whole setup.
Crypto exchange puts the typical TRC20 sender fee at about 6.5 TRX burned, or far less with energy rental
and links straight to the GetBlock TRON Energy on how to get it π―
thanks for the reference, Zephyr[dot]Exchange π
#TRON #TGF #TronGlobalFriends
far less, in numbers:
1.95 TRX for 65k energy rented from GetBlock for 1 hour, against 6.5 TRX burned β getblock.io/tron-energy/
full read: zypher.exchange/en/blog/acceβ¦
If youβre still making repeated API calls just to check if something happened on-chain... thereβs a better way.
We just dropped a new tutorial on GetBlock Webhooks β real-time notifications pushed directly to your endpoint whenever:
π A wallet receives a transaction
π A contract emits an event
π A block is confirmed
In the video, we walk you through:
β Setting up your first webhook
β Choosing event types and filters
β Handling payloads at your endpoint
Whether youβre building alerts, transaction trackers, or real-time dashboards β webhooks change the game.
π¬ Link in next thread π
73% of stablecoin volume, $92.7B in USDT.
There's no second @trondao.
That's a monstrous number of transfers burning $TRX for energy
GetBlock TRON Energy Rental cuts the fee on each USDT transfer by up to 70%
Delivered in <2s, paid in USD, no $TRX to stake
#TRONGlobalFriends #TGF #TRON
TRONβs role in stablecoin settlement continues to grow.
According to @CoinDesk, TRON accounted for approximately 73% of stablecoin transaction volume in September 2026, while USDT on TRON reached over $92.7B in circulating supply during Q3.
Explore the full thread for more insights. π
Rent TRON energy via API or dashboard β getblock.io/tron-energy/
1961: the first industrial robot clocks in at a GM plant.
Today: @peaq is building infrastructure for machines to have onchain identities, wallets, and do business.
And now, they have RPC on GetBlock.
β peaq mainnet over JSON-RPC and WebSocket
β EVM, Substrate, and peaqβs native machine calls on one endpoint
β Shared nodes, ready from the dashboard
β Dedicated nodes in Frankfurt, New York, or Singapore
Get a peaq RPC endpoint: getblock.io/nodes/peaq/
Full announcement: getblock.io/blog/getblock-adβ¦
The next shift in machine work is taking shape onchain.
GM GM developers
If your dApp has steady traffic but a different RPC bill every month?
Limitless Node swaps compute units for a flat fee. Pick your requests-per-second tier and send unlimited requests inside it, with no per-request metering. It suits indexers, polling backends, and high-volume wallets.
Still prototyping? Stay on the free plan; check out the comments to get started. This one is for when you're live.
Still copying RPC URLs from a dashboard into your configs?
A couple of weeks ago we shipped the Platform API, so your pipeline (or your AI agent) can handle GetBlock RPC endpoints for you.
Things that no longer need the GetBlock dashboard π§΅
And for AI agents: connect the GetBlock MCP server to Claude, Cursor, or your own agent.
It can check limits, look up chains, and create or rotate endpoints with your approval.
Get started β docs.getblock.io/platform-apβ¦
OpenAPI spec β public-api.getblock.io/docs/β¦
Deep dive β getblock.io/blog/rpc-endpoinβ¦








