This guide provides a technical overview for developers looking to integrate with Lynex Official Site, focusing on its core Lynex ve(3,3) DEX architecture and how to interact with its liquidity and governance mechanisms on the Lynex on Linea network.
Step 1: Understanding the ve(3,3) Architecture
Lynex is a powerful DEX built on the "ve(3,3)" model, a game-theoretic design for incentivizing liquidity, specifically tailored for the Linea network.
Tokenomics: It uses a dual-token system: LYNX Token Staking (the utility token) and veLYNX (vote-escrowed LYNX).
Mechanism: Users lock LYNX to receive veLYNX. veLYNX holders receive protocol fees, bribes, and the power to direct Lynex Emissions to specific Lynex Liquidity Pools through Lynex Gauge Voting.
Step 2: Providing Liquidity and Earning Emissions
Developers can build interfaces for users to become liquidity providers (LPs).
Deposit: Users deposit an equivalent value of two tokens into a chosen pool.
Receive LP Tokens: They receive LP tokens, which must then be staked in the corresponding "Gauge" contract.
Gauge Rewards: The amount of LYNX emissions earned by LPs in a specific pool is directly proportional to the votes (veLYNX weight) that pool receives. Your dApp can query the gauge contracts to display current emission rates (APRs).
Step 3: Interacting with veLYNX Governance
For developers building governance-focused dApps or analytics tools, veLYNX is the key.
Locking LYNX: Users lock their LYNX for a chosen duration to receive veLYNX.
Voting: veLYNX holders vote weekly on which gauges should receive LYNX emissions. This is the core of the ve(3,3) model.
Bribes: Protocols can attach "bribes" to gauges to incentivize veLYNX holders to vote for their pools. Your dApp can display these bribes to inform voters.
Step 4: Swaps and Security
To Trade on Lynex, users interact with its AMM router contracts. The security model, a key part of answering "Is Lynex Safe?", relies on its audited codebase and the transparent, on-chain nature of the ve(3,3) system.
For all smart contract ABIs, gauge addresses, and SDK documentation, refer to the Full Official Documentation.
Top comments (0)