IC-650 Risk Module, Open-Source Commitment, and the Road to Mainnet TL;DR: - The last feature branch has been merged for IC Core, moving IC into the final test phase, v1.0. - Upcoming updates for the devnet and public testnet. - Mainnet deployment will begin after a successful testnet update. Risk Engine With the integration of the last feature branch, the IC-650 Risk Module, Crypto Factor Interchain now operates with a new extension called "The Risk Engine." This extension functions as a gatekeeper for cross-chain transaction execution, evaluating transaction content and assigning different tags and numerical attributes. Transactions that do not meet the required thresholds are reverted based on the final evaluation. The evaluation process is determined by a set of built-in on-chain modules running on the master chain, as well as pluggable components developed by protocol developers. This allows them to insert custom features or integrate their on-chain and off-chain AI models. The risk engine module is incorporated into the larger Master State validation stack of Crypto Factor Interchain, enhancing the chain's ability to verify multi-chain transactions and executions. A more detailed overview of the module and its operations will be provided in a separate in-depth post. Interchain Mainnet Our team has been tirelessly working for the past six months to bring us to this moment—the deployment of the Interchain Mainnet. With v1.0 of Interchain Core, EVM Chain, and Node features now complete, we have a few remaining steps on the path to Mainnet: 1. Deployment of v1.0 onto devnet: We will first launch the new version of IC as a fresh devnet on Partisia Blockchain (PBC) and DefiChain Metachain (DMC). The devnet will be used to verify and test all the new features, as well as to conduct necessary tests to confirm consensus rules. 2. Deployment of v1.0 onto testnet: After successfully testing and verifying consensus on the devnet, we will deploy the new version of IC as a fresh public testnet, deprecating the v0.1 testnet. The new testnet will be used to evaluate the initial set of protocols intended for the Interchain mainnet, such as the CFR Token Bridge. We will also run the testnet with mainnet settings to assess stability. 3. Deployment of IC Mainnet in beta phase: Following the successful testnet deployment and tests, we will begin the deployment of the IC Mainnet. The master chain will be deployed on PBC, with partial chains also on PBC and DMC. This initial deployment will occur in a beta phase, allowing limited access while we evaluate the stability and overall state of the chain. Upon successful deployment and verification of consensus, the first protocols will go live, marking the beginning of our journey toward seamless multi-chain execution. Open-Source Commitment As always, our team is committed to open-source software. Over time, the codebase for IC will be released as open-source software. The release will follow our standard schedule, with components continually re-evaluated under these guidelines: 1. Any integration layer components and repositories, such as smart contract interfaces, ABI definitions, and infrastructure client libraries, will be published as public open-source repositories under GPL 3.0. 2. Any infrastructure and service layer component that is not in the research and development phase or does not present long-term unique selling points will be published under BSL 1.1. These components will be regularly re-evaluated to ensure a continuous transition toward a fully open-source codebase. After the successful launch of the Mainnet, we will integrate additional components and transport libraries into our GitHub repository, facilitating protocol development around Interchain. We look forward to seeing you all on the chain!

@cfr_labs Feels good to get some extra content around here. 👀

@cfr_labs How about the usecase of CFR? Will CRF be needed for IC?