5.5 Smart Contract Explanation

Interactions between DApps and Verified Nodes are handled by Solana smart contracts. Here’s an overview of the smart contract structure:

// #[account]
pub struct VerifiedNode {
    pub node_id: String,
    pub risk_type: String,
    pub is_active: bool,
    pub premium_rate: u64, // Premium rate for the coverage
}

#[account]
pub struct StakedAssets {
    pub user: Pubkey,
    pub node_id: String,
    pub staked_amount: u64, // Amount staked in the node
}

#[program]
pub mod insurance_dao {
    use super::*;

    pub fn submit_dapp(ctx: Context<SubmitDApp>, dapp_id: String, insurance_pool_id: String) -> Result<()> {
        // Logic to register the DApp
    }

    pub fn purchase_verified_node(ctx: Context<PurchaseVerifiedNode>, node_id: String, stake_amount: u64) -> Result<()> {
        // Logic to stake assets and purchase node coverage
    }

    pub fn validate_node_coverage(ctx: Context<ValidateNodeCoverage>, node_id: String) -> Result<()> {
        // Logic to validate if coverage is active
    }
}rust

Explanation:

• VerifiedNode: Contains details about each Verified Node, such as the node ID, risk type, and whether it is active.

• StakedAssets: Tracks the amount staked by a user in each node.

• Functions like submit_dapp, purchase_verified_node, and validate_node_coverage handle the core actions of registration, staking, and coverage validation.