We’re excited to announce full xlayer support in Tatum’s Blockchain Gateway. Developers can now build on xlayer using standard Ethereum-compatible JSON-RPC methods, backed by Tatum’s scalable, production-ready RPC infrastructure.
Xlayer is an EVM-compatible Layer 2 blockchain developed by OKX and powered by OKB. It is designed for fast, low-cost smart contract execution, Ethereum tooling compatibility, and scalable decentralized application development. With support for standard JSON-RPC methods and familiar developer workflows, Xlayer makes it easier to build, test, and scale dApps on reliable infrastructure.
The Tezos ecosystem is sunsetting the Ghostnet test network. In alignment with official Tezos recommendations, Tatum is decommissioning support for Ghostnet infrastructure. All developers currently using Ghostnet are required to migrate their integrations to Shadownet, the new standard for Tezos protocol testing.
Ghostnet has reached its End of Life (EOL) and is no longer operational. Connectivity to Ghostnet nodes will return connection errors, and all associated Tatum RPC endpoints are being deactivated.
Deprecated Endpoints
The following URL patterns are being decommissioned:
To continue testing your Tezos applications, you must update your connection strings to point to Shadownet.
Migration Steps
Ghostnet Status:Deprecated.
Shadownet Availability:Live. Shadownet is available for immediate use.
Connection Endpoints
Please update your application configuration to use the following Shadownet endpoint:
Network
Gateway URL
Tezos Shadownet
https://tezos-shadownet.gateway.tatum.io
Important Notice
Because Ghostnet is already unresponsive, this migration is mandatory and immediate. Applications that do not update their RPC URLs will experience service interruptions for Tezos testnet functionality.
Polygon Labs has announced that support for the 0xpolygon/erigon node implementation on the Polygon PoS network (Mainnet and Amoy) will be sunset on August 1, 2026. In alignment with Polygon Labs’ recommendations, Tatum is migrating all archive-node infrastructure to Bor with PBSS (Path-Based State Scheme) configuration.
While Bor provides the same historical ledger data, there are significant differences in supported RPC namespaces between Erigon and Bor.
Deprecated Methods
The following Parity-style trace_* methods are exclusive to Erigon and will not be available on the new Bor infrastructure: trace_block, trace_call, trace_callMany, trace_replayBlockTransactions, trace_replayTransaction, trace_filter.
Available Alternatives
Bor supports the standard Geth debug_trace* namespace. For most tracing use cases, you should transition to: debug_traceTransaction, debug_traceBlockByNumber, debug_traceBlockByHash, debug_traceCall.
🚧
Additional Compatibility Notes
Bor follows Geth-compatible behavior for debug and txpool namespaces. Customers relying on exact Erigon response schemas should validate their integrations before migration.
For debug_trace* methods, the memory field is not returned by default. To include EVM memory in trace output, pass enableMemory: true in the trace configuration.
For txpool_* methods, response schemas may differ from Erigon. For example, Bor may omit fields such as baseFee in txpool responses.
Historical eth_getProof Support: Bor currently serves eth_getProof requests only for the latest 128 blocks. Requests for older historical proofs are not currently supported by the Bor client.
Migration Timeline
Polygon Amoy (Testnet): Migration is scheduled for May 11, 2026.
Polygon Mainnet: Migration will follow the Amoy deployment (to be announced).
End of Life: All legacy Erigon nodes will be fully decommissioned by August 1, 2026.
Connection Endpoints
No endpoint URL changes are required. Your existing Polygon Mainnet and Polygon Amoy Gateway URLs will remain the same, but the underlying infrastructure will be migrated to Bor-based nodes.
Important Notice
If your application relies on the trace_ namespace (specifically for range queries via trace_filter), you must refactor your logic to use indexed logs (eth_getLogs) or the debug namespace before the deadline to avoid service interruption.
Keep your mission-critical workloads isolated and say goodbye to credit limits. Create your dedicated key in the Tatum Dashboard to get predictable RPS, better reliability, and clear pricing.
No Credit Consumption: Base plan usage remains unchanged.
Predictable Infrastructure Cost: No usage spikes. No surprise billing.
💡
Availability: Dedicated API Keys are currently available for the RPC Nodes product only. Each key is provisioned for one specific blockchain (one chain per key) and a selected throughput tier (RPS).
We’ve introduced Notifications Conditions & Filters to the Tatum Notifications system across all supported EVM chains and Tron. You can now define custom conditions that control when a webhook is triggered. This ensures you only receive notifications for relevant events, reducing unnecessary traffic and improving processing efficiency.
Receive alerts only when your defined conditions are met.
Why it matters
Reduce noise: filter out irrelevant events before they reach your system
Improve performance: process only meaningful data
Lower costs: minimize webhook volume and downstream processing
Sui gRPC is available on Tatum for teams that want a faster, more structured, and type-safe way to access chain data than legacy JSON-RPC over HTTP. With Sui gRPC, you work with strongly typed Protocol Buffers request and response messages across ledger, state, Move package, name service, signature verification, and transaction execution methods. That makes Sui a strong fit for backends, indexers, explorers, wallets, and internal services that value predictable schemas, generated client code, and efficient binary transport.
Typed APIs: Sui gRPC exposes strongly typed Protobuf request and response messages across services such as LedgerService, MovePackageService, NameService, SignatureVerificationService, State methods, and TransactionExecutionService.
Smaller payloads: gRPC uses Protocol Buffers, which are generally more compact and structured than JSON.
Cleaner integrations: Generated gRPC clients reduce manual request building and response parsing across supported languages.
Good fit for backend workloads: Ideal for objects, transactions, checkpoints, balances, Move package metadata, SuiNS queries, signature verification, and transaction execution or simulation.
Live checkpoint streaming: Sui gRPC also supports real-time checkpoint subscription streaming through SubscriptionService.
The Sui Foundation has officially deprecated JSON-RPC. To ensure network performance and scalability, Tatum is transitioning the Sui infrastructure to a high-performance gRPC architecture.
Migration Path
To avoid service interruptions, please transition your applications to the new standard:
Key Benefit: gRPC offers significantly lower latency and improved streaming capabilities compared to legacy JSON-RPC.
🚧
Attention
After the July 2026 End of Life date, JSON-RPC endpoints will be decommissioned and will no longer return data. We strongly recommend prioritizing this migration in your current development cycle.
We’re excited to announce full Katana support in Tatum’s Blockchain Gateway. Developers can now build on Katana using standard Ethereum-compatible JSON-RPC methods, backed by Tatum’s scalable, production-ready RPC infrastructure.
Katana is an EVM-compatible blockchain designed for fast, efficient smart contract execution and smooth integration with Ethereum tooling. With support for standard JSON-RPC methods and familiar developer workflows, Katana makes it easier to build, test, and scale decentralized applications on reliable infrastructure.
We’re introducing the Tatum Liquid Staking API, enabling developers to retrieve liquid staking balances and supported staking pools across major staking ecosystems (Solana, Ethereum).
Liquid Staking APIs
📘
Get Liquid Staking Current Assets
GET /v4/data/staking/liquid/current-assets
Retrieve all liquid staking tokens held by a wallet address across supported liquid staking protocols. Explore Docs →
📚
Get Liquid Staking Pools
GET /v4/data/staking/liquid/pools Explore Docs →
Retrieve all supported liquid staking pools and tokens for a blockchain, including major protocols like Lido, Rocket Pool, Marinade, and Jito.
With the Liquid Staking APIs, developers can:
Detect liquid staking token balances held by wallets
Discover supported liquid staking protocols and pools
Build staking dashboards and portfolio trackers
Power wallets and DeFi analytics platforms
These APIs simplify building applications that surface liquid staking positions across Ethereum and Solana ecosystems. Read more about this feature on Tatum website - Staking APIs.
Search any wallet address to view active stakes, validator details, and rewards in one place.
Search any wallet address to view staking assets and rewards directly in the Tatum Dashboard.
Ethereum Staking API Support
These endpoints are now available for Ethereum, allowing you to track validator activity, rewards, and staking transactions.
📘
Get Current Staked Assets
GET /v4/data/staking/native/current-assets
Returns all current staked assets for a given Ethereum address, including active stake details. Explore Docs →
📚
Get Current Staked Assets by Validator
GET /v4/data/staking/native/current-assets-by-validator Explore Docs →
Returns staked assets grouped by validator, including delegated amounts and validator details.
📚
Get Staked Account Rewards
GET /v4/data/staking/native/rewards Explore Docs →
Returns historical staking rewards for Ethereum staking accounts.
📚
Get Staking Transactions
GET /v4/data/staking/native/transactions Explore Docs →
Returns staking-related transactions, including stake, withdraw, and validator interactions.
