ComposableFi · rjonczy · Apr 9, 2024 · Apr 8, 2024
diff --git a/docs/docs/concepts/definitions.md b/docs/docs/concepts/definitions.md
@@ -33,8 +33,6 @@ Entities responsible for executing off-chain software logic restaked from an AVS
 ### Restaking
 A new primitive in crypto-economic security that enables the rehypothecation of a token on the consensus layer.
 
-### Solvers 
-Entities that compete to determine an optimal solution (in the form of a transaction execution pathway) for a user's intent. See: intents.
-
 ### Sync Committee
-A committee of 512 validators that is randomly selected every sync committee period (~1 day). While a validator is part of the currently active sync committee, they are expected to continually sign the block header that is the new head of the chain at each slot.
+A committee of 512 validators that is randomly selected every sync committee period (~1 day). While a validator is part of the currently active sync committee, they are expected to continually sign the block header that is the new head of the chain at each slot.
+
diff --git a/docs/docs/develop/local-picasso-guide.md b/docs/docs/develop/local-picasso-guide.md
@@ -1,6 +1,6 @@
-# Picasso DevNet
+# Picasso Kusama DevNet
 
-To run a local network of Picasso with the Alice sudo key, run the following command:
+To run a local network of Picasso Kusama with the Alice sudo key, run the following command:
 
 ```shell
 nix run .#devnet-picasso

diff --git a/docs/docs/develop/solana-avs-testnet.md b/docs/docs/develop/solana-avs-testnet.md
@@ -1,25 +1,26 @@
 # Solana AVS Testnet Guide
 
 :::info
-This document serves as a guide for becoming a validator during the mainnet testing phase of the Solana IBC AVS powered by the Picasso Restaking layer. Operators of this AVS are essentially validators of the previously known 'Guest Blockchain'. Additional information can be found [here](../technology/solana-restaking/technical-overview.md).
+This document serves as a guide for onboarding as an operatior of the AVS for Solana IBC AVS powered by the Picasso Restaking layer. Operators of this AVS are essentially validators of the previously known 'Guest Blockchain'. Additional information can be found [here](../technology/restaking/sol-ibc-avs.md).
 :::
 
-### Validator Security Model
-The validator set of the Guest Blockchain will be directed by majority where it is the responsibility of active validators to maintain uptime and sign corresponding payloads of transactions.
+### Operator Security Model
+The operator set of the AVS will be directed by majority where it is the responsibility of active validators to maintain uptime and sign corresponding payloads of transactions.
 
 ### Bonding
 
-Joining as a validator will require a bonded stake to keep participation gated from malicious actors easily onboarding. The size of the bond will be 0.1 SOL.
+Joining as a validator will require a bonded stake to keep participation gated from malicious actors easily onboarding. The size of the bond will be 25 SOL.
 
 ### (Re) Staking
-The validator set will be able to utilize liquid staked derivatives of SOL, such as jitoSOL, mSOL, bSOL and LST.   
+The validator set will be able to utilize liquid staked derivatives of SOL, such as jitoSOL, mSOL, bSOL, LST and edgevanaSOL.   
 
 ### Oracles
-Pyth oracle will be used to access price feeds for LST assets staked to the platform. 
+The Pyth oracle will be used to access price feeds for LST assets staked to the platform. 
 
-## Validator Setup
+### Slashing 
+Slashing functionality will not be included during the initial launch stage. It will be implemented after the network is fully operational and IBC is live in production on Solana.
 
-Currently, slashing functionality and reward distribution are not available. These features are planned for implementation in the next stage. Additionally, we are in the process of releasing an explorer for this testnet.
+## Validator Setup
 
 1. Install the validator CLI using the following command (From `validator-testing` branch) 
 ```
@@ -46,4 +47,4 @@ optional and has higher preference than the default config file. Any of the argu
 all of them.
 ```
 validator run --rpc-url <RPC_URL> --ws-url <WS_URL> --program-id 7uvnkZxh7Z1wwVFMQ1ak7u4LXWx9f8tkgUnMMyiZrSZb --keypair-path <KEYPAIR_PATH>
-:::
+:::
diff --git a/docs/docs/faqs/disclaimers-disclosures-for-composable-tokens.md b/docs/docs/faqs/disclaimers-disclosures-for-composable-tokens.md
@@ -3,7 +3,7 @@
 As of December 21, 2022
 
 This Specific Disclaimers and Disclosures for the Composable Tokens (“Disclaimer”) relates to the PICA tokens, 
-LAYR tokens, financial non-fungible tokens (fNFTs), and other tokens or products (the “Composable Tokens”) issued or 
+MANTIS tokens, lsDOT and other tokens or products (the “Composable Tokens”) issued or 
 developed by Composable Foundation (the “Company”) that is found within the Ethereum, Polkadot, Kusama and Cosmos blockchain ecosystem. 
 The Disclaimers shall also apply, including without limitation, to the Company’s agents, representatives, 
 beneficial owners, directors, officers, employees, contractors, affiliates, and related persons.

diff --git a/docs/docs/faqs/risk-factors.md b/docs/docs/faqs/risk-factors.md
@@ -3,9 +3,7 @@
 As of December 21, 2022
 
 Without limiting the generality of the factors enumerated below, you are hereby informed and made aware of all the
-potential risks and liabilities relating to the PICA tokens, LAYR tokens, financial non-fungible tokens (fNFTs), 
-and other tokens or products (the “Composable Tokens”)  issued or developed by Composable Foundation 
-(the “Company”) that is found within the Ethereum, Polkadot, Kusama and Cosmos blockchain ecosystem.
+potential risks and liabilities relating to the PICA tokens, MANTIS tokens, lsDOT and other tokens or products (the “Composable Tokens”)  issued or developed by Composable Foundation (the “Company”) that is found within the Ethereum, Polkadot, Kusama and Cosmos blockchain ecosystem.
 
 In this regard, you assume, among others, 
 the following potential risks and liabilities with respect to the Composable Tokens, its performance or utility, 
@@ -19,47 +17,47 @@ The development or deployment of the Composable Token or its intended utility ma
 or be delayed for a number of reasons, including lack of funding, lack of commercial success or prospects, 
 or lack of use by advertisers, publishers, and/or users.
 
-2. **Regulatory risks.** 
+1. **Regulatory risks.** 
 Cryptocurrencies are the subject of regulatory scrutiny by government authorities and other regulatory bodies worldwide,
 and the Company could be adversely affected by one or more enquiries or actions.
 
-3. **No intrinsic Value.**
+1. **No intrinsic Value.**
 The Composable Token has no intrinsic value and is not collateralized.
 You should be aware that you may not be able to recover any amount or value that you exchange to acquire it. 
 All forms of participation in cryptocurrencies involve a substantial risk of loss and are not suitable for everyone.
 
-4. **No guarantee on utility.**
+1. **No guarantee on utility.**
 Expectations regarding the form and functionality of the Composable Tokens or its intended functionality and utility,
 may not be met upon its release for any number of reasons, including a change in the design and implementation of plans, 
 or delays or differences upon execution.
 
-5. **Delay.** 
+1. **Delay.** 
 The full functionality and utility of the Composable Tokens is not yet complete, 
 and no assurance that such can be completed in a timely manner or be completed at all. 
 The intended functionality and utility of the Composable Tokens is complex 
 and will require enhancements and product support over time, and full functionality may take longer than expected.
 
-6. **Not an investment.**
+1. **Not an investment.**
 The Composable Token, like all digital assets, are highly speculative and risky; 
 they should not be considered as an investment vehicle or a financial instrument in any way.
 
-7. **Reliability of information.**
+1. **Reliability of information.**
 Neither the Company, nor any related third party, provides any absolute guarantee as to the accuracy, 
 completeness, or suitability of the information and materials published relating to the Composable Tokens. 
 While the Company makes a conscious effort in providing only updated information.
 
-8. **Security risks.**
+1. **Security risks.**
 The Company plans on implementing security measures; 
 however, the Company cannot predict the success of any security precautions. 
 For instance, the Company may lose access to its private keys or be subject to data breach or data loss. 
 In such a case, the Company does not accept any liability for any loss or damage whatsoever 
 caused by the lost access to the private keys or due to data breach or data loss.
 
-9. **Advances in hacking capabilities.**
+1. **Advances in hacking capabilities.**
 Advances in code cracking, or technical advances such as the development of quantum computing, 
 may present risks to cryptocurrencies and the Company, which could result in the theft or loss of Composable Tokens.
 
-10. **Irreversibility.**
+1.  **Irreversibility.**
 Transactions involving Composable Tokens are not, from an administrative perspective, 
 reversible without the consent and active participation of the recipient of the transaction or, 
 in theory, control or consent of a majority of the processing power on the relevant blockchain. 
@@ -68,12 +66,12 @@ an incorrect transfer of Composable Tokens will not be reversible,
 and there may be no compensation for any such transfer or theft. 
 Such loss could adversely affect the value of the Composable Tokens.
 
-11. **Market disruptions.**
+1.  **Market disruptions.**
 Market events such as those that occurred during October of 1987 and on September 11, 2001,
 could have a global material effect on general conditions and market liquidity 
 which could result in substantial losses or total loss of value of the Composable Tokens.
 
-12. **No control.**
+1.  **No control.**
 The Composable Tokens are not securities or shares and do not represent any stake in the Company. 
 All decisions regarding the management and affairs of the Company will be made exclusively by the Company. 
 You will have no right or power to take part in the management, direction or control of the Company, 

diff --git a/docs/docs/faqs/terms-of-use.md b/docs/docs/faqs/terms-of-use.md
@@ -3,7 +3,7 @@ As of January 18, 2023
 
 These Terms of Use (“Terms”) constitute a binding and enforceable legal contract between Composable Foundation 
 and its affiliates (“Composable,” “we,” “us,” or the “Company”) and you, an end user of the services (“you” or “User”) 
-at https://www.composable.finance, https://picasso.xyz and https://tools.xcvm.dev/ (the “Services”).
+at https://www.composable.finance, https://picasso.xyz, https://games.mantis.app/ and https://app.pablo.finance/ (the “Services”).
 These Terms also include any guidelines, announcements, additional terms, policies, and disclaimers made available 
 or issued by us from time to time. 
 By accessing, using or clicking on our website (and all related subdomains) or its mobile applications (the “Site”) or

diff --git a/docs/docs/networks/composable/LAYR-tokenomics.md b/docs/docs/networks/composable/LAYR-tokenomics.md
diff --git a/docs/docs/technology/ibc/ethereum.md b/docs/docs/technology/ibc/ethereum.md
@@ -1,12 +1,12 @@
 # Ethereum IBC
 
-Ethereum's integration with the IBC protocol expands the ability to offer novel and valuable DeFi use cases and enhance opportunities for participants across diverse ecosystems.
-
-In line with prior IBC extensions, incorporating essential components such as a light client, relayer, and IBC implementation remains a prerequisite. However, when extending IBC compatibility to Ethereum, it became imperative to supplement the relayer with a ZK-Circuit. 
+:::tip
+The inaugral implementation of IBC on Ethereum is now live on mainnet. Users can utilise [Mantis.app](https://games.mantis.app/) to bridge between Ethereum and Cosmos chains via Picasso.
+:::
 
-Previous IBC extensions relied on ibc-rs, whereas, this particular integration utilises an IBC implementation in Solidity.
+Ethereum's integration with the IBC protocol expands the ability to offer novel and valuable DeFi use cases and enhance opportunities for participants across diverse ecosystems. In line with prior IBC extensions, incorporating essential components such as a light client, relayer, and IBC implementation remains a prerequisite. However, when extending IBC compatibility to Ethereum, it became imperative to supplement the relayer with a ZK-Circuit. 
 
-The essential components powering the Ethereum IBC connection are described in the following sections.
+Previous IBC extensions relied on ibc-rs, whereas, this particular integration utilises an IBC implementation in Solidity. The essential components powering the Ethereum IBC connection are described in the following sections.
 
 ## Light Clients
 Before Ethereum transitioned to Proof of Stake (PoS) from its former consensus mechanism, Proof of Work (PoW), developing a light client was notably challenging. Building a light client for any PoW blockchain presents difficulties due to the need for resource-intensive validation of PoW, storage requirements for large block sizes, slow and bandwidth-intensive syncing and having non-deterministic finality - this means that transactions are never truly finalised so there is always the potential for someone to create a longer chain originating from a block preceding the current one, excluding it from the valid chain. These challenges arise from PoW's computational complexity and resource demands, making it more intricate to implement a light client compared to blockchains using PoS consensus mechanisms.