MicroPets was relaunched on October 19, 2023 as part of a major ecosystem upgrade, introducing updated infrastructure, NFTs, and token utility.
As part of its earlier version, MicroPets utilized a previous $PETS token on BNB Chain ([**0x2466858ab5edad0bb597fe9f008f568b00d25fe3**](https://www.coinscope.co/coin/dc-pets)), which operated as a proxy contract with transaction tax mechanisms.
Following further improvements to tokenomics and long-term sustainability, a new $PETS contract was deployed on BNB Chain with a significantly reduced and fixed supply of 1,485,912 tokens.
The new $PETS contract **(**[**0x610FD1A9601CF7b1d188dBF3264738Aecc9fC96C**](https://www.coinscope.co/coin/2-pets)) is fully renounced, immutable, and operates with zero transaction taxes.
### **Why a token relaunch?**
MicroPets: A Community-Driven Relaunch for a Secure Future
Following MicroPets’ all-time high in November 2021, concerns arose regarding the actions of the project’s former owner, Nick Sagliani A.K.A “Saint Nick” which highlighted risks to the project’s contracts and security. These issues necessitated a full relaunch to ensure the project’s integrity and protect its future.
On August 9, 2023, MicroPets embarked on a transformative journey as control of the project was officially transferred to a new team composed of dedicated, long-standing community members. Leading this effort is our new CEO, Jessus Zambrano, whose leadership has been pivotal in rebuilding trust and guiding MicroPets toward a stronger, more transparent future.
The relaunch was a critical, community-driven initiative designed to cut ties with the previous contract controlled by Nick. Through the collective effort of the community—voluntarily sending tokens to a recovery wallet from August 10, 2023 till December 21, 2023—we secured liquidity and empowered the new team with full control over the $PETS token, smart contracts, staking pools, and other key assets.
This relaunch marks the beginning of a new chapter for MicroPets, one that prioritizes transparency, security, and a renewed commitment to the community. Together, we are building a brighter future for the project.
#### Migration
When the new ownership and team took over MicroPets in August 2023, one of the first steps was to migrate the $PETS token to ensure a secure, transparent, and sustainable foundation for the project’s future.
The initial migration was conducted at a ratio of **1120:1** (old to new), resulting in a total supply of 10B $PETS. This transition corrected previous tokenomics and helped restore confidence within the community.
As part of MicroPets’ continued evolution, a second contract upgrade was introduced in 2026 to further improve tokenomics, enhance security, and simplify the ecosystem.
This upgrade introduced a new $PETS contract on BNB Chain **(**[**0x610FD1A9601CF7b1d188dBF3264738Aecc9fC96C**](https://www.coinscope.co/coin/2-pets)) with a significantly reduced and fixed supply of 1,485,912 tokens.
A new migration process is currently in place for holders of the previous $PETS token (proxy contract: [**0x2466858ab5edad0bb597fe9f008f568b00d25fe3**](https://www.coinscope.co/coin/dc-pets)). Tokens can be swapped at a fixed ratio of **1:4743** (old to new).
The migration window is open from March 25, 2026 to March 25, 2027, ensuring all holders have sufficient time to transition.
The new contract is fully renounced, immutable, and operates with zero transaction taxes. All legacy contracts are being phased out and are no longer supported.
This transition strengthens security, improves transparency through verifiable token locks, and aligns the ecosystem for long-term development, including the MicroPals Nexus.
### We are now in a NEW ERA for MICROPETS!
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://micropets.gitbook.io/whitepaper/micropets-relaunch.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
