ICO News

Shiba Inu Executive Clarifies TREAT Token Launch Status – Crypto Times


Lucie, Shiba Inu’s marketing lead, recently addressed the confusion surrounding the launch of their new token, TREAT. Despite circulating reports claiming its release, Lucie confirmed via a post on X that the TREAT token has not yet been officially launched.

This statement was aimed at dispelling rumors and ensuring the community relies only on verified updates.

The misinformation about TREAT’s launch was notably discussed in the latest issue of ‘The Shib,’ Shiba Inu’s dedicated magazine. This publication explored various upcoming projects within the Shiba Inu ecosystem, including the much-anticipated Layer-3 blockchain, developed in collaboration with Zama.

Shiba Inu’s L3 Blockchain and TREAT’s Role

The new blockchain aims to enhance scalability and support for complex applications within the Shiba Inu network. This development is part of an ongoing effort to expand the utility of the Shiba Inu ecosystem, which includes the Shibarium network. 

TREAT is expected to play a crucial role in this ecosystem, serving as a governance and utility token similar to BONE, which is currently used on Shibarium.

Shiba Inu developer team raised $12 million a couple of weeks ago to further develop this new Layer-3 blockchain. The round witnessed high levels of contributions from key crypto stakeholders and venture capital firms, signaling their support for Shiba Inu’s strategic path.

Recent Developments 

In addition to clarifying the TREAT token’s launch status, recent updates from the Shiba Inu team have highlighted progress in their blockchain technologies. The Shibarium network, for example, has completed important upgrades through the Bor and Heimdall hard forks. 

The exact timeline has not been disclosed, but the team’s continuous efforts in developing their privacy-focused Layer-3 blockchain suggest that the launch could occur sooner rather than later.

Read Also: K9 Finance Unveils Mobile Staking App ‘Bone Crusher’ for Shiba Inu Ecosystem







READ SOURCE

This website uses cookies. By continuing to use this site, you accept our use of cookies.