Adina Protocol Documentation
Core infrastructure, smart contract architecture, and integration guides for developers building on Ethereum L2.
Overview
Adina is a next-generation decentralized talent protocol built on Ethereum L2. This documentation covers core infrastructure, smart contract architecture, and integration guides for developers.
Getting Started
Contact Team
Reach out for integration support or partnership inquiries.
community@adinalabs.comJoin Community
Connect with developers and early adopters on Discord.
discord.gg/pKKUmyzxVgCore Concepts
Why Ethereum and the EVM
We chose the EVM over building a bespoke chain for three reasons: it's the most battle-tested smart contract environment, it has the deepest pool of experienced developers and audited libraries, and it lets enterprise integrators work with tooling they already trust. For a platform whose thesis is real-world adoption, proven foundations matter more than novel ones.
Why Layer 2, and why Arbitrum
Running an employment or payments platform directly on Ethereum L1 is too slow and expensive for everyday actions like posting jobs, releasing escrow, or settling micro-payments. Arbitrum is an optimistic rollup with EVM-equivalence, so contracts and tooling behave exactly as on Ethereum. It has the deepest liquidity and widest adoption among Ethereum L2s, and its transaction costs are a fraction of L1 — making high-frequency escrows, payouts, and swaps economically viable. The tradeoff is a challenge window on withdrawals to L1, which suits a design where activity lives on L2 and only settlement and governance touch L1.
Why a Dual-Chain Split
We don't treat L2 as a replacement for Ethereum, but as a division of labor. Ethereum L1 handles what must be maximally secure and permanent: governance, treasury, and the settlement anchor. Arbitrum L2 handles what must be fast and cheap: everyday platform activity. This gives enterprise users L1-grade security for the things that matter, without paying L1 costs on every interaction.
Why Non-Custodial and Read-Only
The Dashboard is deliberately read-only and never takes custody of funds. This is both an architectural and a regulatory choice: a system that only displays information and never holds or moves value carries a fundamentally different risk profile than a custodial one. Users' own wallets execute every transaction.
Why a Utility Token with a Usage Burn
ADINA is designed so that demand for the token comes from platform activity, not from holding for its own sake. Services are priced in stable credits, settled in ADINA, and a share of activity permanently burns supply. The token's role is functional: it's what the ecosystem runs on.
FAQ
Still have questions?
Reach the team at community@adinalabs.com