Hi guys, We're going to migrate to BAGS.
It's much better than pump nowadays, so weโve decided to fully align our infrastructure with their standards.
We are happy to announce that we have successfully finished building our token payment ecosystem, which is now fully compliant with the current BAGS Token Extension protocols.
Everything is ready for the new utility model.
Along with improvements to the liquidity pool nodes, we are finalizing enhancements to the overall node user experience.
Following this, we will publish the tokenomics and a brief roadmap.
We are currently updating the liquidity pool node.
Previously, it only checked for a pool's existence, but we are upgrading the structure to return actual pool values by leveraging the SDKs from Raydium, Meteora, and Pump.
Usually, purchased tokens are meant for immediate burning after a few checks.
We've finished testing and completed another burn.
In total, 35M+ tokens have been burned.
Additionally, we are considering a Marketplace feature where users can utilize automation nodes created by others, also powered by a pay-per-request model.
What value does $NEXT hold?
Deploying the "on-chain automation routines" youโve built with Next to a self-hosted server, and implementing real-time data via watcher servers and WebSockets, involves a steep learning curve and many tedious steps.
$NEXT streamlines this entire process. Functioning on a pay-per-request basis, the token is used to cover the server deployment and execution costs required to fully automate your on-chain routines.
Here's what I'm building right now:
I'm creating nodes to fetch token metadata, check token info, and check token holders.
I'm also creating more conditional nodes.
Here's what I'm building right now:
I'm creating nodes to fetch token metadata, check token info, and check token holders.
I'm also creating more conditional nodes.