Introduction

MNET (Metaverse.Network) stands tall as an innovative blockchain ecosystem equipped with a rich social layer. This versatile framework supports both Ethereum Virtual Machine (EVM) and WebAssembly (WASM) smart contracts, empowering developers to harness its capabilities to craft decentralized applications (dApps) with unprecedented functionality and flexibility. Think of it as a vast open market where developers can thrive, engaging in all sorts of transactions and interactions freely.

Overview

The MNET network, built using the Substrate framework, is a work in progress that encompasses a vibrant community devoted to creating a robust environment for blockchain development. With features tailored for both existing EVM applications and those inclined towards WASM, the future looks bright for MNET.

Building

To build both WASM and native code for MNET, execute the following command:

make build

Run

Starting a development Metaverse Network Chain is straightforward. Follow these steps:

Start a Dev Metaverse Network Chain

Use this command to initiate the Dev Metaverse Chain:

make run-dev

For those wanting more detailed logs, you can run the node with refined environment variables:

set RUST_LOG=debug RUST_BACKTRACE=1 cargo run -- --dev

This command will spin up a development Metaverse Chain with Alice and Bob as the initial authorities.

Multi-Node Metaverse Network Chain

If you’d like to witness the multi-node consensus algorithm in a local setting, you can set up a local testnet with two validator nodes for Alice and Bob. Each of these nodes will be the initial authorities of the genesis chain and will be granted testnet units.

For this operation, you’ll need to have two terminal windows open. Start Alice’s node first on the default TCP port (30333):

cargo run -- --base-path tmpalice --chain=local --alice --node-key 0000000000000000000000000000000000000000000000000000000000000001 --telemetry-url wss://telemetry.polkadot.io/submit 0 --validator

Next, launch Bob’s node on a different TCP port (30334) with his chain database stored locally at tmpbob. Use this command:

cargo run -- --base-path tmpbob --bootnodes ip4/127.0.0.1/tcp/30333/p2p/QmRpheLN4JWdAnY7HGJfWFNbfkQCb6tFf4vvA6hgjMZKrR --chain=local --bob --port 30334 --telemetry-url wss://telemetry.polkadot.io/submit 0 --validator

Troubleshooting

While the setup process for MNET might seem complex, you can troubleshoot common issues with the following tips:

• Issue: Error messages during ‘make build’?
• Solution: Ensure you have all dependencies installed correctly. Sometimes libraries may require specific versions that are essential for compatibility.
• Issue: Nodes not connecting?
• Solution: Check your port configurations and ensure no firewall settings are blocking your nodes from communicating.

If you require additional insights or updates, feel free to reach out or collaborate on AI development projects by staying connected with fxis.ai.

Conclusion

At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.