Architecture

Ivy has two layers. Everything that carries value is on chain; supporting data lives off chain for speed and experience.

#Onchain layer (Kaia Mainnet)

This is the source of truth:

• Identity and username. Who is who, usernames (ERC-721).
• Economic interactions. Likes, tips, transfers (KAIA movement).
• Channel, video, NFT. Ownership and payment records.
• SharePool. The pool where fees are collected and distributed.

#Offchain layer

For convenience and performance only; it carries no value:

• Post text, images, video files (media/CDN).
• Cached counters, search indexes, notifications.

A post itself may be stored off chain, but the like or tip on that post is onchain and irreversible. The chain references the post by its keccak256 digest (see Social Engines).

#Contract map

Area	Contracts
Identity	IvyRegistry, IvyUsername, IvyUsernameMarket
Social	LikeEngine, TipEngine, TransferEngine
Video	IvyChannelRegistry, IvyVideoRegistry
NFT	IvyNFT, IvyNFTMarketplace, IvyCuration
Economy	IvySharePool, IvyStakingPool, IvyToken

For all addresses: Contract Addresses.

#Integration model

• Reading: you read the contracts directly over a public RPC. No key required.
• Writing: transactions are signed with the user's wallet (embedded wallet, MetaMask and so on). Interactions generally require a verified account.