Axyl Consensus Protocol Code is open

We're making Axyl fully verifiable. The source code and Halborn security audit are officially live and available to the public.

You can access the repository, inspect the code, and review the comprehensive audit right now at: https://github.com/raylsnetwork/axyl 

Axyl is the consensus engine powering the Rayls Public Chain, delivering 15,000+ TPS and sub-second finality, secured by validators around the world.

Why we are opening the code

Trust in a decentralised network requires radical transparency. We want developers, researchers, and blockchain enthusiasts to independently verify our work.

By making the code available, you don't just have to take our word for it: you can read the Halborn security audits, inspect the underlying architecture, run the code locally, and see exactly how Rayls achieves consensus under the hood.

The licence: sustainable innovation with the BSL

To release this code while ensuring continued ecosystem growth, we've chosen the Business Source License (BSL) 1.1.

The BSL is a massive positive for the community. It empowers you to run the code locally, inspect it for security, and build hobby projects freely, whilst providing a four-year protection period for the commercial rights and significant investment Rayls has made in developing this technology. By safeguarding our commercial interests in the short term, we can continue to fund the relentless innovation that makes Axyl world-class.

This commercial protection has a strict expiration date. Exactly four years from each version's release, its licence automatically converts to the fully open-source Apache License, Version 2.0.

Other prominent Web3 projects have adopted the BSL to balance open-source principles with sustainable development, most notably Uniswap v3.

What does this mean for you today?

Under the current BSL 1.1 terms, here's exactly what you can and cannot do:

What You Can Do (Freely)

• Inspect, Learn, and Tinker: Copy, modify, create derivative works, and redistribute the code for any non-production use, including local testing and hobby development.

• Run a Rayls Node: Through our "Additional Use Grant," you're explicitly permitted to use the Licensed Work in production if operating a node on the Rayls Public Chain mainnet or official test networks.

• Support the Network: This production exception fully covers running validator, observer, relayer, and RPC nodes.

What Requires a Commercial Licence

If you wish to use the Axyl Consensus Protocol in production outside of the Rayls ecosystem, you must secure a commercial agreement with Rayls Core Ltd. This includes:

• Operating any independent blockchain network or consensus mechanism

• Offering Axyl as a hosted, managed, or cloud service to third parties

• Any production use for the benefit of third parties outside your own organisation

(Note: Third-party software incorporated into Axyl remains governed by its respective original licences, listed in the repository's NOTICE.md file.)

A New Chapter for Transparency and Innovation

Opening our code marks a pivotal milestone for our project where the protocol we’ve been making is now viewable by everyone. We hope this provides further trust in what we’re building and invites critical feedback on where we can improve. By sharing our core technology, we invite a new era of collaborative growth and collective security, ensuring that the innovations driving the Rayls ecosystem become a shared foundation for the entire industry. 

Get involved

Head over to the GitHub repository today to dig into the code and review the Halborn security audit. For the exact legal terms, review the full License.md file in the repository.

Questions? Join the conversation in our Discord or on X.

‍