Release Of Chaingateway V2.1 Beta

Dear Chaingateway Community,

We are thrilled to announce the release of Chaingateway V2.1! After thousands of hours of development, we’ve completely revamped our software, reengineering nearly every API function, redesigning the UI, and overhauling the entire webhooks system. This upgrade marks a significant leap forward in both functionality and user experience.

If you are intrested in our Beta, please feel free to join our Beta Telegram Community

How to Access the Beta

The beta version is now available to all customers and trial users. You can access it at beta.chaingateway.io.

V2.1 is designed to be fully compatible with the previous version, meaning you can switch from api.chaingateway.io/v2 to beta.chaingateway.io/api/v2 seamlessly.** Please refer to the How to Migrate section for details on migrating your existing implementation.**

If your trial has expired or you’re new to Chaingateway, feel free to create an account. Alternatively, contact us and we’ll be happy to extend your trial for the new version.

What’s New in Chaingateway V2.1

We’re excited to share the key features and improvements introduced in this update:

1. TESTNET Support (Finally!)

We now support testnets across all chains. Here’s the breakdown:

Ethereum: Sepolia testnet
Tron: Nile testnet
BSC: Testnet
Polygon: Amoy testnet
Bitcoin: Testnet3

To enable testnet usage, simply add X-Network: testnet to your request header. For mainnet, you can use X-Network: mainnet or leave it as is. Everything you can do on mainnet can now also be done on testnets. Additionally, our new Paymaster feature incurs no fees on testnet, allowing unlimited testing.

You can also switch networks easily via the UI—just use the switch in the header section.

Testnet Support

2. Tron Paymaster

Tired of managing TRX for moving TRC20 tokens? Our new Tron Paymaster feature has you covered! With Paymaster, we handle all the transaction fees, ensuring your wallet has enough bandwidth and energy to process transactions, saving you approximately 6 TRX per transaction.

This service is separate from your normal subscription and requires funding your account to cover energy broker costs. Learn more about it in our Tron Paymaster Tutorial or by browsing the API Docs

3. Improved API Documentation with Tryout Feature

We’ve significantly enhanced our API Docs, providing more detailed request and response examples. Plus, you can now try out the API directly in the documentation.

We’ve also added code generation for hundreds of tech stacks, making it easy to integrate Chaingateway into your projects. If you find anything missing, please don’t hesitate to contact us.

4. Improved Developer Portal

Our Developer Portal now features a revamped getting started guide and tutorials for core functionality. Whether you’re new to Chaingateway or an experienced user, this is the best place to start.

5. Redesigned UI

The new User Interface has been completely redesigned for enhanced usability, making it easier to manage and debug your data. Check it out on beta.chaingateway.io. Please note that while search functionality in webhooks and notifications is currently slow, we’re working on implementing a more efficient search engine.

Dashboard Screenshot

6. Enhanced Billing System

If you’re using Stripe, you can now switch to a higher plan instantly, without waiting for the next billing cycle. This means if you hit your API limits, simply click “Change Plan” in the billing dashboard, and your API limits will increase immediately. Your invoice will only reflect the difference between the old and new plan price.

We’re also working on extending this functionality for crypto payments soon.

7. Live Chat Support

We’ve introduced live chat support to assist you in real-time. Whether you’re troubleshooting or need help, we’re just a message away.

Technical Improvements

API Refactoring

We’ve migrated to a completely new tech stack, improving response times, error handling, and overall system resilience. While we’ve tested extensively, there may still be some differences in API responses compared to V2. If you encounter any issues, please contact our support team.

Better Fee Handling

We’ve optimized our fee-handling process, addressing issues many of you faced in the past. If your requests currently define gasPrice, MaxFeePerGas, or MaxPriorityFeePerGas, you may no longer need to include them in V2.1.

Enhanced Webhook System

We’ve made the webhook system faster and more resilient against spam, attacks, and outages.

In recent weeks, we experienced several outages in our webhook systems, which led to blocks not being processed. However, we can now put that issue behind us. Our new webhook system is massively scalable and can handle thousands of blocks in minutes. We no longer need to worry about this problem.

We also introducing a new security feature to save the webhook system against spammers. If a webhook has too many faild notifications in case of an invalid host or too much sent notifications, you’ll receive an email notification with the webhook ID and reason for invalidation. To reactivate, either use the UI or repost them with the same ID.

Additionally, the Webhook Monitor in the UI now allows you to inspect sent payloads and filter by specific values, making it easier to troubleshoot.

Webhooks reactivation

What’s Next?

Looking ahead, we’ve already begun development on the next version of Chaingateway. This will include support for Solana, expanded blockchain support for our Paymaster feature, and several API response fixes. Stay tuned for more updates!

How to Migrate to V2.1

Switching to V2.1 should be smooth, but here’s a quick guide:

Change the base URL from api.chaingateway.io/v2 to beta.chaingateway.io/api/v2.
Optional but recommended: Add the Bearer prefix in front of your API key so it looks like Authorization: Bearer XXXxxxXXXxxxXXX.
Test everything to ensure it works as expected.
As soon as you are not fully migrated, please use the old dashboard on app.chaingateway.io to manage your subscription!

All user data, addresses, and API keys will automatically be migrated from V2 to V2.1 every minute. However, please note that addresses created in V2.1 cannot be used in V2. Webhooks are migrated every 10 minutes but won’t trigger any notifications during the migration process. If you’d like assistance migrating your webhooks, feel free to contact us.

Thank you for your continued support, and we look forward to hearing your feedback! Please subscribe to our Newsletter to stay up to date!

Blog Post