protocol-bg
Protocol Web4Lit is paving the way for a future where you control your digital identity
Contact Sales
Architecture Identity Aggregation & storage Identity Import & storage Identity Parametization Web4Lit TEE-based sidechain Native: ZKP Prover AI Agent Cloud computation service External: Runtime/pallet logic EVM/WASM smart contract Interoperable cross-chain (XCM/Bridge) On-chain computation Off-chain computation Identity Data Processor Unit Input Output Actions Smart contract callback On-chain state mutation Off-chain notification Proofs (VC & ZKP) Identity ownership Identity qualification Personhood recognition
Key Features User Sovereignty Enhanced Privacy Streamlined Onboarding Improved Trust and Reputation
Tokenomics Token: Web4Lit $W4L Total Supply:7,111,777,000 W4L Presale Allocation: 35% Liquidity Pool: 35% Team Allocation: 10% (Locked for 12 months) Marketing & Rewards: 20%
Processor Unit The Web4Lit Identity 's data flow involves multiple stages from input to processing, with distinct paths for on-chain and off-chain computation. As shown in the flow diagram above, The offchain computation can either be native via Web4Lit’s TEE-based Sidechain or externally via ZKP prover, AI-agent, or other cloud computation platform.
protocol-f4-card2-icon
protocol-f4-card3-icon
Processor Logic (how is computation logic defined) The Web4Lit Identity processes identity data using a combination of on-chain and off-chain computation logic. The on-chain logic is primarily handled by the pallet/runtime logic and smart contracts (EVM/WASM), while off-chain computation involves the trusted execution environment and external computational resources. The can leverage both Ethereum Virtual Machine (EVM) and WebAssembly (WASM) based smart contracts and pallets - a modular piece of runtime logic.
protocol-f4-card4-icon
Output The produces various outputs that serve as proofs and actions based on the processed identity data. These outputs ensure the integrity, validity, and utility of identity information within the ecosystem. Proofs generated by the Web4Lit Identity provide verifiable evidence of identity-related claims such as Identity ownership, Identity qualification, and recognition. Actions triggered by the Web4Lit Identity are responses to certain events or conditions. These actions can automate processes and improve the functionality of dApps. Examples are Post SBT (Soulbound Token) and trigger notification.
How it works The Web4Lit service serves as the source of identity-related data to dApps. It is designed with identity-linking functionalities and allows user identity to be processed and stored in a privacy-preserving environment called the Trusted Execution Environment (TEE).
Protocol Web4Lit is paving the way for a future where you control your digital identity
Contact Sales
Identity Aggregation & storage Identity Import & storage Identity Parametization Web4Lit TEE-based sidechain Native: ZKP Prover AI Agent Cloud computation service External: Runtime/pallet logic EVM/WASM smart contract Interoperable cross-chain (XCM/Bridge) On-chain computation Off-chain computation Identity Data Processor Unit Input Output Actions Smart contract callback On-chain state mutation Off-chain notification Proofs (VC & ZKP) Identity ownership Identity qualification Personhood recognition
Architecture
Key Features Strenths of the Web4Lit Protocol User Sovereignty Enhanced Privacy Streamlined Onboarding Improved Trust and Reputation
How it works The Web4Lit service serves as the source of identity-related data to dApps. It is designed with identity-linking functionalities and allows user identity to be processed and stored in a privacy-preserving environment called the Trusted Execution Environment (TEE).
Tokenomics: Token: Web4Lit $W4L Total Supply:7,111,777,000 W4L Presale Allocation: 35% Liquidity Pool: 35% Team Allocation: 10% (Locked for 12 months) Marketing & Rewards: 20% Buy/Sell Tax: 0% Presale Start: 14 December 2024 Presale End: 28 December 2024 15:00 UTC+0 Launch Date: 28 December 2024 16:00 UTC+0
Processor Unit The Web4Lit Identity 's data flow involves multiple stages from input to processing, with distinct paths for on-chain and off-chain computation. As shown in the flow diagram above, The offchain computation can either be native via Web4Lit’s TEE-based Sidechain or externally via ZKP prover, AI-agent, or other cloud computation platform.
protocol-f4-card2-icon
Processor Logic (how is computation logic defined) The Web4Lit Identity processes identity data using a combination of on-chain and off-chain computation logic. The on-chain logic is primarily handled by the pallet/runtime logic and smart contracts (EVM/WASM), while off-chain computation involves the trusted execution environment and external computational resources. The can leverage both Ethereum Virtual Machine (EVM) and WebAssembly (WASM) based smart contracts and pallets - a modular piece of runtime logic.
protocol-f4-card3-icon
Output The produces various outputs that serve as proofs and actions based on the processed identity data. These outputs ensure the integrity, validity, and utility of identity information within the ecosystem. Proofs generated by the Web4Lit Identity provide verifiable evidence of identity-related claims such as Identity ownership, Identity qualification, and recognition. Actions triggered by the Web4Lit Identity are responses to certain events or conditions. These actions can automate processes and improve the functionality of dApps. Examples are Post SBT (Soulbound Token) and trigger notification.
protocol-f4-card4-icon