Rooted in open gaming

Overview

As part of Mainnet Update v11.79.0, we are upgrading how NFT ownership data is stored on The Root Network. This change is a technical refactor of the NFT Pallet and introduces a new data structure to support improved performance, greater scalability, and better system clarity when managing large-scale collections.

This upgrade will require brief downtime on mainnet (approx 24 hours), scheduled for July 23/24. During this period, core NFT-related operations including minting, bridging, transferring, and marketplace activity will be temporarily paused. Builders are encouraged to test their dApps and services during and after the Porcini (testnet) migration window to ensure continued compatibility.

Why This Upgrade Matters

The Root Network is designed to support immersive, large-scale content and gaming ecosystems. To meet growing demand and optimize for upcoming launches, we are implementing a more efficient storage model for NFTs.

This change provides a more stable foundation for future growth and enables:

• More efficient performance for large collections
• Simplified and maintainable data structures
• Improved support for complex token use cases
• Accurate gas modeling for multi-token operations

What’s Changing

The upgrade restructures the NFT pallet by splitting ownership and token info into two separate maps:

1. Token Info Map (TokenInfo)

This map links each token_id to its current owner and includes token locks and utility flags.

Useful for: Querying who owns a specific token

2. Owner Map (OwnedTokens)

This map tracks which serials are owned by each account.

Useful for: Querying which tokens are owned by an address

Key benefits of this structure:

• Faster query performance
• More consistent storage logic across token features
• Sets the foundation for future enhancements to token logic

Note: This upgrade does not affect how metadata is stored or accessed. The metadata URI and collection-level metadata scheme will remain intact.

What Builders Need to Do

If your experience interacts with NFTs on The Root Network, we recommend testing the following flows:

• Standard ownership queries (ownerOf, balanceOf, etc.)
• NFT minting and transfer flows
• Marketplace listing, offers, and auctions
• NFT bridging (to and from The Root Network)
• Token approvals and ERC721 compatibility
• Any custom logic or scripts that directly reference NFT storage structures

Most integrations using RPC endpoints or the TRN SDK should not be impacted. Projects accessing data directly from storage will need to review the new structure.

Testing and Migration Timeline

Porcini Testnet Migration

Migration Date: July 17 UTC‍

Live Testing Window: July 17 during migration, and July 21 to 22 for post-migration regression

Porcini migration will only take a few hours, so we encourage projects to have test plans ready. This will be the most accurate preview of what to expect during the mainnet transition.

Mainnet Migration

Scheduled Window: July 23 to 24 UTC

NFT operations will be offline for approximately 24 hours. This includes:

• NFT minting
• NFT marketplace activity
• NFT bridging

FAQs

Is metadata affected?

No. All metadata and metadata_uri endpoints will continue to function as before.

Will this change affect EVM compatibility?

The NFT pallet is being upgraded, but the EVM layer remains the same. EVM transactions for precompile based collections (that use the NFT Pallet under the hood) will be down during the migration. Interactions through EVM contracts should behave as expected once migration is complete.

Will gas costs change?

Yes. Transactions involving multiple NFTs in a single call (such as batch minting) will now reflect slightly higher gas usage, aligned to on-chain computational and memory usage.

What extrinsics are impacted?

Many extrinsics are touched by this change. The most important ones to validate include:

• Every Extrinsic in the NFT pallet
• All NFT based Marketing extrinsics
• NFT bridging extrinsics

Below are all extrinsics that will have internal changes from this migration:

• NFT.create_collection
• NFT.transfer
• NFT.mint
• NFT.burn
• EthBridge.submit_event
• XRPL-Bridge.submit_transaction
• XRPL-Bridge.withdraw_nft
• NFT-Pegwithdraw
• Marketplace.sell
• Marketplace.buy
• Marketplace.auction
• Marketplace.make_simple_offer
• Marketplace.accept_offer
• XLS20.enable_xls20_compatibility
• XLS20.re_requestxls20_mint
• XLS20.fulfill_xls20_mint
• Crowdsale.initialize
• Crowdsale.distribute_crowdsale_rewards
• Crowdsale.claim_voucher
• Crowdsale.redeem_voucher
• Nfi.manual_data_request
• NFI.submit_nfi_data
• NFT.set_utility_flags
• NFT.set_royalties_schedule
• NFT.set_name
• NFT.set_mint_fee
• NFT.toggle_public_mint
• NFT.set_base_uri
• NFT.set_max_issuance
• NFT.set_owner
• NFT.set_token_transferable_flag
• NFT.issue_soulbound
• NFT.accept_soulbound_issuance
• NFT.set_additional_data
• NFT.min_with_additional_data

This update ensures The Root Network remains robust and performant as the ecosystem continues to grow. We appreciate the support from builders helping us test during the Porcini phase and encourage everyone to review their integrations ahead of the Mainnet migration window.

Let’s build the future, together.

As part of The Root Network’s latest mainnet update, we’re excited to announce the launch of the Sylo Action Permission Pallet – a key component in the suite of Sylo Protocols for the open metaverse.

This pallet introduces revocable, programmable on-chain permissions, starting with the ability to grant another wallet permission to perform specific extrinsics on your behalf.

It’s a powerful tool for developers, platforms, and partners looking to deliver smoother UX and scalable automation, without compromising user control or security.

Why Action Permissions Matter

In Ethereum and other EVM chains, token approvals have long allowed users to grant third-party contracts the ability to spend ERC20 tokens on their behalf. While useful, these approvals are narrow in scope and often pose security risks if not managed carefully.

The Sylo Action Permission Pallet moves beyond that model.

It enables programmable, revocable access to specific extrinsics – such as minting, transferring NFTs, staking, or creating collections – without needing to share private keys.

And it doesn’t stop at what actions can be taken – it also lets you choose who covers gas when those actions are executed.

All permissions are:

• Set by the account owner
• Recorded and enforced on-chain
• Fully revocable at any time
• With granular permissions coming soon

A Better UX Without the Risk

This unlocks a new layer of user-friendly, scalable experiences – especially for brands, platforms, and builders managing automated or high-volume on-chain operations.

Example:

A brand minting thousands of NFTs as part of a launch campaign could grant a trusted third-party platform permission to handle all on-chain minting transactions.

They could also agree that the platform – not the end-user – covers the gas fees, creating a completely seamless, frictionless experience.

No key sharing. No repetitive wallet confirmations. No unexpected gas prompts. Full control, always revocable.

This allows partners to move faster and scale, while a offering smoother UX to user, and maintaining full control over their assets and permissions.

Powering Agentic Workflows

Beyond traditional web3 platforms, these permissions also create a foundation for agent-based systems – where AI agents can act on behalf of users or brands.

With Sylo Permissions, an agent could be granted the ability to:

• Mint a character when certain conditions are met
• Rebalance liquidity positions on behalf of a partner
• Stake assets automatically as part of a scheduled action
• Or even initiate a series of multi-step interactions across contracts

Combined with the upcoming granular control layer, developers will be able to define what actions can be taken, against what assets, and under what circumstances – all without centralized intermediaries.

Built on The Root Network. Powered by $SYLO.

Setting permissions is handled on-chain via the Sylo Permissions Protocol, and every permission set requires a transaction powered by $SYLO, the native utility token of the Sylo Network.

As with other Sylo Protocols like Verification and Asset Register, this work builds the foundation for open, interoperable systems – where data and actions are portable, programmable, and secure.

What’s Next

This launch marks phase one of the Sylo Action Permissions Pallet. In future updates, developers will gain access to:

• Granular Permissions – restrict access to specific NFTs, tokens, or extrinsics
• Agent-first Tools – platforms, like Futureverse, will build SDKs to empower safe delegation to AI agents and systems

The goal: to help you build more intelligent, responsive, and automated experiences – across web3, gaming, and the open metaverse.

Links

Sylo Action Permissions Pallet Docs

Sylo Website

Follow on X

‍

We’re excited to welcome RapidNode to The Root Network ecosystem, a team removing the friction from running blockchain infrastructure. With native Root Network support now live, developers and builders can launch a full node in minutes. No servers. No CLI. Just one-click deployment, fully managed.

This integration makes it easier than ever to contribute to the network – whether you’re validating, testing on-chain interactions, or building dApps that rely on a robust local node connection.

From Denarii Labs to Mainnet

RapidNode’s roots trace back to the Denarii x Futureverse Accelerator, where they set out to simplify validator operations for web3 networks. Their focus? Infrastructure-as-a-service – with zero devops burden for the end user.

For builders on The Root Network, this unlocks a faster path to participation. You no longer need to provision hardware or write scripts just to run a node – and can instead focus on building, testing, or integrating with the chain directly.

“The Root Network’s modular design and clear tooling made it effortless to integrate and launch one-click deployment on RapidNode.” Tanishq Mehta, Founder, RapidNode.

Why Run a Full Node?

Running a full node on The Root Network gives you:

• A direct connection to the network for dApp development or real-time data access
• The ability to secure the network and earn staking rewards
• A foundation for more advanced integrations or custom tooling
• A deeper understanding of the chain’s mechanics and runtime

Until now, this came with a cost: devops complexity. RapidNode removes that barrier.

What the integration delivers

Rapid Node’s integration with The Root Network includes:

• One-click full node deployment
  ‍Set up a full node on The Root Network in just a few clicks – no CLI, no infrastructure setup.

• Fully managed‍
  Automatic updates, performance monitoring, and issue resolution are handled for you.

• Scalable by design
  ‍From first-time to seasoned builders managing multiple nodes, the platform grows with your needs.

• Transparent analytics‍
  Get insights into uptime, performance, and activity via an intuitive dashboard.

This setup gives developers full-node access without infrastructure overhead – so you can move faster, with fewer moving parts.

How to get started

Launching a node on The Root Network via RapidNode is simple:

1. Log in at app.rapidnode.xyz
2. From the dashboard, select The Root Network
3. Click on Credits to top up your account
4. Confirm the purchase and complete the transaction
5. Go to Active Nodes
6. Wait for the status to move from Setup Pending to Deployed

Your node is now live – fully managed with performance monitoring and analytics ready to go.

Links

Website: rapidnode.xyz

Dashboard: app.rapidnode.xyz

Follow RapidNode on X: x.com/rapidnodexyz

‍