Public Mainsail EVM Testnet Launches - Ushering in a New Chapter

We’re thrilled to announce the launch of our first Public Mainsail EVM Testnet, built from the Core v3 Devnet Snapshot. After months of intense development and coordination, we’ve prepped everything, from infrastructure to tools, documentation, and user resources, so you can jump right in. This marks a major step forward in bringing EVM capabilities to ARK. And while we’ve come a long way, this is just the beginning. Over the next few months, we’ll be relying on your feedback, from the community and validators, to help us refine, secure, and polish Mainsail EVM into a production-ready product. So, whether you’re here to explore or help uncover the odd bug or two (we like to think of them as “undocumented features”), we welcome you aboard!

#A Few Key Notes Before You Set Sail

• Delegate(s) are now officially Validator(s). If you spot any “Delegate(s)” references lingering around our front-end products, please give us a nudge.
• What was previously known as Devnet is now Testnet. We’ve aligned the terminology with broader blockchain standards for better clarity.
• The Public Mainsail EVM Testnet is spun up from a snapshot of the Core v3 Devnet at block height 22,002,491 . That means:
  • Existing passphrases still work.
  • Delegates who previously registered a BLS key and made it into the top 51 will appear as Validators.
  • Validators will need to register again (using the new transaction type) to start producing blocks, unless they already did so on the previous Devnet.
  • We’re transitioning from addresses starting with 'D' to the familiar Ethereum-style 0x format. It’s a small change in characters, but a big step toward EVM compatibility.
• We now refer to wallets (e.g., ARK Vault) as software products. The term address(es) is used to identify user account(s) capable of sending/receiving tokens on the network.
• Mainsail EVM features a two-stage BFT consensus mechanism with instant block finality. (Because who likes waiting?)
• The Public API is now an optional, standalone process, giving node operators more flexibility.
• Transaction broadcasting has moved:
  • Old port: 4003 → New port: 4007
  • P2P moved from 4001 → 4000
• To avoid a three-way split, the number of validators has increased to a prime number 53, up from 51.
• On-chain usernames can now be registered to any address, thanks to a dedicated username registration transaction done via contract.
• The ChainID for this Public Testnet is: 11812

We invite you to dive in, test things out, and help shape the future of Mainsail EVM. Your feedback is the wind in our sails - let’s build something great together.

#Essential Resources to Get You Started

Ready to dive into Mainsail EVM? Whether you’re spinning up a node or aiming to become a validator, we’ve got you covered. Below is a curated list of essential documentation to help you get set up quickly and confidently:

• Node Requirements – Hardware, software, and system prep for running a Mainsail node.
• Network Details – Ports, files, and public API nodes for connecting to the testnet.
• TX Tester CLI Guide – Learn how to simulate transactions with our CLI testing tool as well as register a Validator.
• Registering as a Validator – Step-by-step guide to validator setup and registration.
• Install Script (Recommended) – The fastest and easiest way to install your node.
• Install from Source – Prefer to build it yourself? We’ve got the guide for that too.
• Docker Install Guide – Run your node in a containerized environment.

#General Information

Our internal testnet has been running behind the scenes for several months. During that time, we performed multiple resets as we ironed out bugs and collected feedback from developers working on companion products like Vault, Scan, and Connect.

Now, with the foundation solid, we’re inviting you to join the next phase of real-world testing. Your participation will help us fine-tune performance, squash lingering bugs, and make Mainsail EVM production ready.

Here’s what’s currently available (products are still considered as alpha, so a few rough edges may remain; please open GitHub issues if you spot any!):

• 🔍 ARK Scan – A full-featured blockchain explorer built for Mainsail EVM.
• 💼 ARK Vault – Your go-to wallet for managing tokens and interacting with the testnet.
• 📖 Mainsail & SDKs Documentation – Step-by-step setup guides, validator registration, SDKs, and more. (Note: this is a new site that will eventually replace ARK.dev)
• 🧪 Mainsail TX Tester CLI – A CLI tool to test transactions and validator flows.
• 💧 Public Testnet Faucet – Get free testnet tokens for testing transactions and registering as a validator.

This post outlines everything you need to begin your Mainsail journey and highlights what to expect in this early stage rollout.

We’re excited to have you onboard - test boldly, report issues, and help us shape what’s next!

#Supported Transactions in the Public Mainsail EVM Testnet

During this initial phase of the Public Mainsail EVM Testnet, the following transaction types are supported. All except for general transfers are now processed through EVM smart contracts, bringing flexibility, composability, and a future-proof foundation to the ARK ecosystem.

Here’s what’s currently available:

• Transfers – The classic: sending tokens from one address to another.
• Multipayments – Send tokens to multiple addresses in a single transaction. One click, many payouts.
• Vote – Cast your support for a validator using your address balance.
• Unvote – Remove your vote from a validator.
• Switch Vote – Change your vote from one validator to another, no need to unvote first.
• Validator Registration –Register your BLS public key to become a validator. You can update it at any time.
• Validator Resignation – Step down as a validator. The address becomes ineligible for new votes and block production.
• Username Registration – Claim a unique username for your address, adding a human touch to the chain.
• Username Resignation – Give up a previously registered username, much like a validator resignation, but for your alias.

This set of transactions forms the foundation for testing and interacting with Mainsail EVM. More functionality will follow as we expand and iterate based on your feedback!

#Have a Question or Found an Issue?

Running into setup hiccups or spotting something that’s not quite right during testing? We’re here for it and we’d love to hear from you.

You can reach us through these channels:

• Open an Issue on GitHub – Found a bug or something not behaving as expected? Drop us an issue and we’ll take a look.
• Join the ARK Community Discord – Swing by the community-run Discord and visit#mainsail_testnet channel to chat with the team and other community testers.

We encourage participation - whether it’s testing, providing feedback, or diving into the codebase itself. Your input is instrumental in making Mainsail EVM more resilient, efficient, and ready for prime time.

#A Note on Architecture & Experience

We know Mainsail introduces some big architectural changes compared to Core v3. Validators and node operators will especially notice some differences in how things are set up. It might take a little time to adjust, but we’re here to support you every step of the way.

That said, we’ve made sure that for everyday users, the UI and experience feel familiar. Interacting with the network, whether through ARK Vault or ARK Scan, should still feel intuitive and aligned with what you’re used to from the current Production Network.

Thanks for helping us test, tune, and shape the future of Mainsail EVM. Let’s build something rock solid together.

#What’s Next?

Over the coming weeks and months, we invite users to join the network and run public nodes. This will help us simulate real-world usage scenarios and test Mainsail EVM under broader network conditions.

On the development side, here’s what’s on the horizon:

• Expanded Documentation – We’ll continue refining and expanding Mainsail docs to make setup, usage, and development even more accessible.
• Ongoing Issue Resolution – As bugs surface on Testnet, we’ll be addressing them swiftly; your reports are key here.
• Ledger Hardware Wallet Support – Integration into the Ledger ecosystem is underway, bringing hardware-level support.
• Vault & ARK Connect Integration – Work is in progress to make Mainsail EVM fully compatible with ARK Vault and ARK Connect.
• SDK Enhancements – Expect improvements to our SDKs based on real-world usage and developer feedback.
• Ecosystem Integrations – We’ll continue exploring and implementing integrations that make Mainsail more useful, flexible, and developer-friendly.

We’re committed to refining the Mainsail codebase, improving performance across the stack, and delivering a seamless user experience, powered by community input and real-world testing.

Thanks for being part of the journey. We’re just getting started.

#Follow on Twitter (X)

Stay connected with us on X (formerly Twitter) and keep checking the blog to stay up-to-date on all of our new releases. We post a weekly development report so you can easily see what we’ve been up to and follow along our journey towards making your decentralized future a reality.