Foreon Network Development Update: Edition 3 — (Road To MVP)
It’s been another two months since our last development update, and we’re excited to share the significant progress we’ve made on the Foreon Network.
To ensure transparency and community involvement, we will be making Bi-Monthly development updates as we progress with Foreon Network MVP Development and subsequent testnet release.
Team Expansion:
Foreon Network is growing!
We have added two more members, Andrey & Valentina to bolster our core development team.
As we inch closer to the launch of our MVP, we believe these new additions will ramp up our technical expertise and development capabilities, ensuring we meet our milestones on time and deliver a high-quality, user-friendly product.
Smart Contracts Update:
We’ve decided to rewrite our Foreon Smart Contracts using the Aiken language.
We initially started with plutus but after multiple discussions within the Cardano developer community, we decided to switch to Aiken Language.
Aiken is designed with the purpose of improving the clarity, correctness, and efficiency of smart contracts on the Cardano network.
This change is a major step towards improving the reliability and safety of our platform.
Furthermore, we’ve brought on board members from TXpipe, Santiago and Federico on a contractual basis to help guide us in this process.
Their in-depth knowledge and experience with Aiken will ensure that our contracts follow the best coding practices and standards.
The dialogues with the TXpipe team involve important discussions regarding the design of the interface, the choice of programming languages for backend development, and the mechanics of fees, among other topics.
One key topic of discussion has been the definition of the list of fact statement types from the Cardano decentralized oracles that we need to integrate for the Foreon MVP and also the decision to use TypeScript for the backend, considering the team’s familiarity with the language and its compatibility with our development requirements.
However, for the “Chain indexing” part, we’re considering using Scrolls, a tool developed in Rust by the TXpipe team, to ensure performance and efficiency.
In a critical decision, we’ve also opted to use a single Aiken codebase for all questions in the ForeOn protocol.
The codebase will contain a singular version of the validator logic but will feature parametrized validators.
What this means is that for each question, an automatic procedure will apply the necessary parameters, and the resulting bytecode (UPLC) will govern the question’s lifecycle on-chain.
This strategy simplifies our system architecture and makes it more efficient.
Architectural Decisions:
As we build our software system, we are keen on making architectural decisions that cater to the most significant requirements.
These decisions are about the organization or structure of the software system and entail the selection of structural elements and their interfaces, behavior specification in collaborations among those elements, composition of these structural and behavioral elements into larger subsystems, and an architectural style that guides this organization.
To illustrate our software architecture in a clear, comprehensive, and scalable way, we’re using C4 diagrams.
The context diagram, for example, provides a high-level overview of the system.
It portrays how the system fits into the broader system of systems and how users interact with it.
As we forge ahead in our development journey, we are deeply committed to transparency and open communication with our community.
We thank you for your continuous support and are excited to bring you more updates in the future as we continue building Foreon Network.
Foreon NFT Bonds Offering Is Still Ongoing
Our Initial NFT Bonds Offering is still ongoing, don’t miss out on a chance to become one of the early pioneers and adopters of Foreon Network.
Learn more about the NFT Bonds Offering
Stay tuned!
Keep up-to-date with Foreon Network:
Website: https://foreon.network
Blog: https://foreonnetwork.medium.com/
Twitter: https://twitter.com/foreonnetwork
Discord: https://discord.com/invite/zwPfBRGDEu
Telegram: https://t.me/ForeonNetwork
GitHub: https://github.com/Foreon-Network