Introduction

Ēnosys Global is the original, and longest lasting, DeFi provider on the Flare Networks (Songbird and Flare). We run a suite of DeFi and infrastructure products on the Songbird and Flare Networks which are all tied into a central Yield aggregator - the APY Cloud. On Flare, this ecosystem is governed by a bicameral governance system with a primary (Apsis) and secondary (Helion) governance token. Proper governance is incentivized through yield collected by the APY Cloud and paid out to governance participants at a bounded variable rate.

Development Funnel

The development cycle within Ēnosys follows these steps:

1. A developer or team receives the specifications and design (if applicable) from one of the project managers.

2. The developer(s) define tasks/deliverables based on number 1.

3. Local development work begins.

4. As deliverables are completed, the changes are deployed to the development environment.

5. In the development environment, these deliverables are tested by the project manager and other team members.

6. If the deliverables are approved to be correct and stable, they are then deployed to the staging environment where these changes are further tested by our team of moderators. If the deliverables are not approved, they head back to the developer and repeat step 3. It takes only one objection from any team member for the development to revert.

7. If all criteria are successfully covered and the deliverable passes testing by the Project Manager, team members and moderators, the deliverable is scheduled for a production release on the next release date.

8. The deliverable is released to the users to further improve the Enosys product suite.

This process can be summarized in 3 main steps: Development, Staging, and Production. This gives us the ability to minimize the chance of error, anomaly or unexpected edge case.

In the blockchain world, each network allows for its own version of this development process. On the Flare Network, we break it down as follows:

Coston, the valueless development network, where developers are free to test things out and deploy new technology more easily due to no real token value.

Songbird, the staging network, where ideas and concepts are tested in a live environment, with real value at stake; a check for anyone who needs to see how an idea and product will hold up against market forces.

Flare Network (Mainnet), the production network, where all the efforts from the above are brought together to live long and prosper. This will be the culmination of all the above efforts taking their final shape as the community have tested, voted on, changed and finally accepted them.

All of our products go through their own iterations of the 8 step development process listed above, on each of these networks. This means that by the time a change is made to our product suite on the Flare Network mainnet, it will have gone through a 24 step development process.

Experimental Finance Ecosystem (ExFi)

Although the Songbird instance of Ēnosys is deemed experimental and is a separate ecosystem from the mainnet instance, it is a fully functional ecosystem with real value at stake. All products and features that are introduced to ExFi will remain. It will also have its own Governance, APYCloud, Governance Staking and Governance tokens - EXFI & SFIN.

The purpose of ExFi is to replicate what is intended for the production-ready instance on mainnet, therefore both ecosystems share many similarities in product information and tokenomics.

SFIN is the primary governance and reward token on Songbird, whereas Apsis(APS) is the primary governance and reward token on mainnet.

EXFI is the secondary governance token on Songbird, whereas Helion(HLN) is the secondary governance token on mainnet.

There may be differences in rewards, allocations and distributions between the two ecosystems due to experiences on ExFi that have influenced recommended or necessary changes for the mainnet ecosystem.