Today was a big day for us at Kaddex and the Kadena Ecosystem. For the first time, our very own simplified and gas-free trading experience went live, signaling the start of scalable DeFi, as it has never been seen before.

The dedicated work that our engineers and the entire team at Kaddex has put in over many months has brought our vision for a new DeFi ecosystem into reality.

We have learned so much through the creation of Kaddex, and we expected that the learnings would continue today. But the level of activity and attention we saw today had us learning more than anticipated. After all is said and done, the team has learned a tremendous amount about how to make a more robust infrastructure set up that will help us scale into the future easily and without hiccup.

Below is a synopsis of what occurred 👇

Right before launch and leading into the smart contracts going live, there was a large uptick of cross-chain transactions. Many of these transactions were failing or were trying to complete an already completed cross-chain transfer. This caused a lot of unanticipated network congestion leading into the initial launch.

Once we launched, a misconfiguration on our load balancer (which routes traffic to our then 3 nodes) caused a “false health check”, making it think a healthy node was failing. This crippled our ability to handle traffic at the first critical moments at launch. This was very unexpected for our team, as this load balancer has been working fine with this configuration on the beta for months. This was quickly fixed.

Right after this, the node response time very quickly shot up to 10 seconds or more per request. This usually happens where there are too many /local calls (queries to the blockchain state) being made at once. To fix this, we tried spinning up more nodes (going up to 9 nodes) but the response time remained high. This will require a bit more investigation as it only affected chain 2 and not other chains.

This was exacerbated with some inefficient calls on our website attached to the analytics and pool statistics which very quickly overloaded our nodes with a flood of calls. This has been fixed, and the front end is much more call efficient.

This also impacted X-Wallet users, specifically checking for balances and switching between chains, which kept some users from connecting to the DEX, if they were able to gain access.

In the end, we transitioned our node support to Flux, whose decentralized node network quickly came in to save the day.

We thank you all for your patience and support on this momentous day. We celebrate the start of Kaddex, and the future of DeFi on Kadena. And as a result of these changes, we are now better positioned to run the world’s most incredible DEX.

Today was a big day for us at Kaddex and the Kadena Ecosystem. For the first time, our very own simplified and gas-free trading experience went live, signaling the start of scalable DeFi, as it has never been seen before.

The dedicated work that our engineers and the entire team at Kaddex has put in over many months has brought our vision for a new DeFi ecosystem into reality.

We have learned so much through the creation of Kaddex, and we expected that the learnings would continue today. But the level of activity and attention we saw today had us learning more than anticipated. After all is said and done, the team has learned a tremendous amount about how to make a more robust infrastructure set up that will help us scale into the future easily and without hiccup.

Below is a synopsis of what occurred 👇

Right before launch and leading into the smart contracts going live, there was a large uptick of cross-chain transactions. Many of these transactions were failing or were trying to complete an already completed cross-chain transfer. This caused a lot of unanticipated network congestion leading into the initial launch.

Once we launched, a misconfiguration on our load balancer (which routes traffic to our then 3 nodes) caused a “false health check”, making it think a healthy node was failing. This crippled our ability to handle traffic at the first critical moments at launch. This was very unexpected for our team, as this load balancer has been working fine with this configuration on the beta for months. This was quickly fixed.

Right after this, the node response time very quickly shot up to 10 seconds or more per request. This usually happens where there are too many /local calls (queries to the blockchain state) being made at once. To fix this, we tried spinning up more nodes (going up to 9 nodes) but the response time remained high. This will require a bit more investigation as it only affected chain 2 and not other chains.

This was exacerbated with some inefficient calls on our website attached to the analytics and pool statistics which very quickly overloaded our nodes with a flood of calls. This has been fixed, and the front end is much more call efficient.

This also impacted X-Wallet users, specifically checking for balances and switching between chains, which kept some users from connecting to the DEX, if they were able to gain access.

In the end, we transitioned our node support to Flux, whose decentralized node network quickly came in to save the day.

We thank you all for your patience and support on this momentous day. We celebrate the start of Kaddex, and the future of DeFi on Kadena. And as a result of these changes, we are now better positioned to run the world’s most incredible DEX.