We are thrilled to announce a significant milestone in the development of Bitpost: the first of the platform’s smart contract subsystems – Version Manager – has been completed, tested, and successfully deployed on the BPX Chain mainnet.
What is the Version Manager?
The Version Manager is a unified system that oversees the deployment and updates of all smart contracts on the Bitpost platform. Instead of managing upgradeability individually within each contract, each contract is assigned a unique class identifier (CID), which the Version Manager resolves to the current implementation. When an update is required, the relevant record for the given CID is simply updated in the Version Manager, and the change is reflected across all contracts of that class without the need to transact individually with each instance. The ability to deploy updates this way is crucial for contracts that may have millions of identical instances, such as individual Bitpost shipments or members of the logistics network.
For more details, feel free to check out the full source code of the Bitpost Version Manager, now available on our GitHub: https://github.com/BitpostNetwork/contracts-vm.
Deployment details
The Bitpost Version Manager consists of a single contract, which has been deployed at the address 0x407B23Dad0bD32a3B1Ad184A2e61c206615F7771 in the transaction with the hash 0x9bea8a72ac881019ddfe50fa35ce9f2cbcab481cbae22d540ac196171949a87a.
The Bitpost developers created a special wallet dedicated to deploying Bitpost smart contracts: 0x331cdb44Ea19EAa26742bEd80c51faF3b909A67c. While the platform is still under development, this wallet acts as the owner of the Version Manager, giving the development team full control to deploy updates without restrictions. Once Bitpost is fully launched, ownership will be transferred to the decentralized governance system, ensuring that control over contract updates shifts away from the team into the hands of the community.
Conclusion
After yesterday’s deployment, the current state of Bitpost’s smart contracts is as follows (subsystems that are already operational are highlighted in color, while those still under development or awaiting deployment are marked in gray):
If this diagram doesn’t look familiar to you, be sure to check out this article: Bitpost smart contract subsystems – Bitpost Internals #3.
Since the BPG token launch is scheduled for January 1, 2025, there’s even more excitement ahead in the coming days. Stay tuned for the next development updates!