Splinterlands has had the idea of creating its own Blockchain network for a while now, starting with the sale of Nodes, but some complications ended up causing the project to extend much longer than planned. However, with the Token Cleanup proposal 196 and validator testing already starting to be done, the SPS Chain is being launched soon. Come check out the details of this news!
I'll be much appreaciated if you Upvote, Reblogs or give any Tips ( PIZZA 🍕, PGM 🎮, LOLZ 😆, ALIVE ❤️, etc ). Thanks and have good reading! 🍀
[ENGLISH VERSION]
What is SPS Chain?
I believe that since the creation of Splinterlands as a Web3 Game, the owners have always had the idea that it would be truly decentralized, so a long way has been taken to achieve this goal. Initially, the SPS DAO was created so that decisions regarding the Splinterlands Ecosystem could be made through proposals, thus seeking a consensus among players. Now the next step is the creation of the SPS Chain, a decentralized blockchain network that will have the Hive Blockchain as its base, being Layer 1, while the tokens and smart contracts related to Splinterlands will be managed on Layer 2.
The initial plan is to start with transactions related to tokens (SPS, Voucher, License) and over time expand to other Splinterlands assets, such as Cards, Lands and Marketplaces. This change could bring more utility to the SPS token and work as it did with Axie and Ronin, that is, making the SPS Chain something bigger and start receiving other games that use the SPS token and Splinterlands assets.
Validator Node Tests have started!
On the official discord of the game Splinterlands, in the chat “Validator-Nodes” it was announced by Clayboyn, responsible for SPS DAO, that the public tests for Validators would begin and together some platforms that provide the hosting service so that it is possible to run the nodes.
The interesting thing is that these tests have already started and several users have already shared their doubts, mistakes, successes and recently there are even some guides on how to set up the SPS Validator. The important thing about this is that the idea of a Splinterlands Decentralized Network is being put into practice, it is already possible to test and you can see from the comments. Now it's a matter of fixing possible bugs and improving the system and resolving the SPS token situation, which is also being resolved, and the Splinterlands game will have its own Blockchain network, which will have the SPS as its main token.
Token Cleanup Proposal & Future of SPS

Source: Splinterlands Proposal 196
Proposal 196 made by Clayboyn passed with the vast majority of votes (94%) and its objective was to prepare the SPS token for the migration from the BSC Blockchain to the SPS Validators Network (SPS Chain). The idea of the proposal is to mint all remaining SPS tokens and divide them into “buckets” that will be allocated to certain functions. This was the best way the team found to facilitate control over the distribution of tokens. In a future audit, only the “buckets” that hold the tokens will need to be audited, and from there, the DAO and the treasurer will define where they will go.
It is worth remembering that this transition ended up being more “smooth” to carry out because Clayboyn, together with the SPS DAO and Splinterlands teams, had already been taking actions to help with this process, such as a complete audit that took months and began in early 2024.
With the approval of the Proposal, the remaining SPS tokens that have not yet been minted, around 45%, have already been minted and separated into allocations that will be up to the DAO and the Treasurer to decide how future distributions will occur. I just had doubts because 2% still appears as unminted, maybe there are still some tokens missing.
In any case, this is a big step that was taken towards the SPS Chain and a possible listing of the SPS Token on an Exchange, since one of the requirements is a complete audit of the Token, which was difficult to perform because there were tokens spread across several blockchains and the validators were not ready.

