Technical Reference

Smart Contract Architecture

• Modular design: Each protocol can be deployed and upgraded independently.

• No upgradeability proxies: All logic is immutable after deployment, ensuring auditability and trust.

• Role-based permissions: Only DAO or governance multisig can update certain parameters.

• Transparent fee logic: All fees, shares, and distributions are visible on-chain.

(Diagrams or contract flowcharts can be added as images or mermaid code.)

---

Supported Networks

Network	Testnet Address	Mainnet Address	Explorer Link
Ethereum	0x...	0x...	Etherscan
Polygon	0x...	0x...	Polygonscan
BNB Chain	0x...	0x...	BscScan

---

ABI & Interface Files

• All contract ABIs are available in the /abis folder of each repository.

• Example: RevampDeFi.json

• To fetch programmatically:

  jsCopyEditimport RevampABI from './abis/RevampDeFi.json'

---

Core Data Flows

• Deposit: User → Revamp Contract (tokens locked)

• Burn event: Event emitted, tokens marked as burned

• Claim: User claims native token from pool

• Governance: DAO votes on parameter updates