Skip to main content

Everlyn (Lyn)

Everlyn (Lyn / Everlyn‑1) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Everlyn (Lyn) — an AI/Inference project on BNB Smart Chain, token (symbol: LYN).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: an ecosystem around an open‑source video model (Everlyn‑1) and the idea of a decentralized network of “video agents” (Lyn Protocol / Everworld); the website offers AI generation of video/images.
  • Who it’s for: for content/project creators and developers who need video generation/“video agents” and an API economy (AAPI/V‑API).
  • Why onchain/token: LYN is claimed as the settlement currency and gas for onchain accounting of actions/provenance, as well as a staking and governance token.
  • What you can actually touch (Tier‑1): the generation web app at everlyn.ai (text/image→video, text→image).

How it works (very briefly)

  1. The user does: enters a prompt (and/or uploads an image) in the web app.
  2. The system does: runs the generation (positioned as its own foundation video model Everlyn‑1 + an “agentic” layer/API economy).
  3. The user gets: the generated image/video.
  4. Where the blockchain is: the docs describe the idea of onchain accounting of agent activity and provenance; per Tier‑1, as of today only the token contract on BNB Smart Chain is unambiguously confirmed.
  5. Token role (if any): LYN is described as a token for payments/subscriptions/minting, gas for onchain actions, staking and DAO voting.

Quick links: AI thesis fit

Project passport

Field Value
Project name Everlyn (Lyn)
Also known as (aliases) Lyn, Everlyn‑1, $LYN
Logo (logo) ../assets/95_everlyn_logo.svg
Token symbol (ticker) LYN
Category AI/Inference
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2025-10-01
Project status (status) active
Token (standard) BEP-20
Token contract 0x302DFaF2CDbE51a18d97186A7384e87CF599877D
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance inflationary (10%→1% p.a.)
Tokenomics (tokenomics, brief) 1B genesis + unlock schedules; utility: payments/gas/staking/governance
Governance DAO (Lyn DAO)
Admins/keys owner (Ownable; can mint)
Audit —
Bug bounty —
Team (team) a team of generative AI researchers (academia + ex Big Tech)
Funding (investors/funding) —
AI component (ai_component) open-source video foundation model + video agents
Use‑case (use_case) video/image generation + video agents
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 1 / 3 / 3
Last verified 2026-02-11

General project overview

Everlyn (the docs also use the Lyn brand) is positioned as a Web3‑native ecosystem for video generation and “human‑centric” video agents. The base AI core is described as the open‑source foundation video model Everlyn‑1, with a protocol layer and an “Agent APIs” economy (AAPI/V‑API) on top for dApp/agent integrations and settlement for task execution.

In practice, Tier‑1 provides a web generation interface (text/image→video, text→image). The onchain part in public Tier‑1 sources is mostly described conceptually; the LYN token contract on BNB Smart Chain is confirmed by address.

Features/modules

  • Generation web app for images/video (public interface, wallet‑connect).
  • Lyn docs (GitBook): a description of Lyn Protocol as a decentralized video AI layer and of “agents”.
  • Open‑source repository Everlyn-1 (research directions: tokenization/VQ, autoregressive video generation, multimodal/hallucination reduction).
  • $LYN tokenomics/utility: payments/subscriptions/minting, gas for onchain accounting of actions, staking, DAO voting (as described in the docs).

Typical scenarios

  • Scenario 1 (creator): a user generates video/images in the web app → receives the content.
  • Scenario 2 (dev / integrations): a developer integrates the “video API / agent API” (per the docs) → a dApp/agent initiates generation/actions → settlement and activity accounting are planned via the protocol.
  • Scenario 3 (staker/participant): a LYN holder stakes tokens to participate in governance/delegation to AAPI (per the docs) → receives a share of rewards/access to features.

Getting started (wallet/network)

  • What you need: a browser and access to everlyn.ai (optionally — a web3 wallet for wallet‑connect).
  • Network/chain: the LYN token is on BNB Smart Chain (if actions require onchain — the BSC network will be needed).
  • Fees: if onchain operations are used (staking/voting/protocol actions) — BSC fees; in the docs LYN is also described as the unit of payment/gas within protocol operations.

Architecture/tech (non‑AI)

  • Components: the web app, an offchain inference/training layer (the Everlyn‑1 model), a protocol layer (described in the docs), the LYN token contract (BEP‑20) on BSC.
  • Participant roles: users/creators, “agent” owners, AAPI/V‑API developers, stakers/delegators, token holders (governance).
  • Where logic runs: content generation — offchain; the onchain part (per the docs) — accounting of actions/provenance/settlement; per Tier‑1, the token contract is confirmed by address.
  • Dependencies: BNB Smart Chain as the token’s network; external integrations/oracles/storage are mentioned at the concept level in the docs.

Token/economics (expanded, no forecasts)

  • Token utility: LYN is described as the currency for payments and subscriptions (minting/an “agent’s” operational subscription), gas for onchain accounting of actions and transactions, and a staking and DAO voting token.
  • Protocol necessity drivers: the docs describe “instant settlement/provenance/audit” and payment for AAPI/V‑API activities in LYN.
  • Who pays fees: users/agent owners/developers/AAPI buyers (per the docs).
  • Where fees go: the docs describe payouts to AAPI developers and a share to delegated stakers; a detailed “where exactly” economy in the form of formulas/contracts was not found in Tier‑1 sources.
  • Issuance/burn: the docs describe a supply of 1B at genesis, unlock schedules and inflation (10% p.a. with an annual decrease to 1%).
  • Security/incentive mechanisms: staking/delegation of LYN to AAPI/agents (per the docs); the onchain mechanics are not confirmed by addresses/contracts per Tier‑1 sources.
  • Distribution and token issuance schedule: the docs contain distribution schemes and an unlock schedule; exact tables/figures were not transferred to the passport.
  • Treasury: not established (—).

Governance

  • Who makes decisions: the docs claim a Lyn DAO (voting by LYN holders upon reaching a threshold).
  • How protocol parameters change: per the docs — via DAO voting; specific governance procedures/smart contracts were not found in Tier‑1 sources.
  • Where decisions are discussed/made: not established (—).
  • Keys/multisig: per the LYN token code, the contract is Ownable (there is an owner and a mint function for the owner only).

Security and incidents

  • Audits: no public reports were found in Tier‑1 sources.
  • Bug bounty: no official program was found in Tier‑1 sources.
  • Incidents: not established (—).
  • Threat model: the key risk — centralization of the token contract’s admin rights (mint) and the absence of publicly confirmed addresses/contracts of the protocol’s onchain logic.

Project status and timeline

  • Current status: the web app and docs are available; the token contract on BSC is active.
  • Key releases/milestones: there are no GitHub Releases; the repository’s commit history can be used as a “live changelog”.
  • Roadmap: no separate Roadmap page was found in the docs; links_* lists the Tier‑1 vision page.

Ecosystem/integrations

  • Integrations: the docs claim dApp/agent integrations via the API layer; no specific confirmed integrations were identified in Tier‑1 sources.
  • Partners: not established (—).
  • Where it’s actually used: the generation web app is confirmed; protocol usage in dApps/agents by addresses/transactions is not confirmed by Tier‑1 onchain artifacts (other than the token).

AI component of the project

  • What is real AI here? The Tier‑1 docs describe research and architectures in the field of video generation/multimodal models (Everlyn‑1) and “video agents”; there is also a generation web app.
  • What is truly onchain? Tier‑1 confirms the BEP‑20 token LYN on BNB Smart Chain; the protocol’s onchain logic (action registry/proof‑of‑execution, etc.) is described in the docs conceptually, but without addresses/contracts in Tier‑1 sources.
  • Why is a token needed? In the Tier‑1 docs, LYN is described as a token for payments/subscriptions/minting, gas for onchain accounting of activity and a staking/DAO governance token.
  • Red flags (based on the information found): possible onchain‑washing (many claims about “on‑chain recorded action”, but few address‑level artifacts); token‑washing (a broad utility list without a verifiable onchain implementation); what to double‑check: the protocol’s addresses/contracts and real onchain transactions other than the token.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): The AI component is confirmed (AI_1/AI_2/AI_4), so “intent only” does not apply.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn, https://www.everlyn.ai
  • Why sufficient / why not (one line): By definition, AI_0 is set only when AI_1..AI_4 = 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the project performs video/image generation and describes the foundation video model Everlyn‑1 + “video agents”.
  • Evidence: Tier‑1 — https://www.everlyn.ai, https://lynlabs.gitbook.io/lyn
  • Why sufficient / why not (one line): Tier‑1 has a direct product interface for generation and a description of the model/ecosystem.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): a generation web app (text/image→video, text→image) is available on the official website.
  • Evidence: Tier‑1 — https://www.everlyn.ai
  • Why sufficient / why not (one line): this is a reproducible Tier‑1 demo/product interface, “what you can touch”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.everlyn.ai
  • Why sufficient / why not (one line): the website has numbers, but without sufficient context (what/how was measured, version/data), so AI_3=0.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): the GitBook has technical sections (pipeline/architectures) and detailed descriptions of models/subsystems.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/lyn-docs/our-vision-for-video-ai-and-human-centric-agential-video, https://lynlabs.gitbook.io/lyn/lyn-docs/video-agent-generation-diffusion-based-model, https://lynlabs.gitbook.io/lyn/technical-designs/everlyns-data-pre-processing-pipeline
  • Why sufficient / why not (one line): this is a Tier‑1 technical description of the architecture and components, sufficient for AI_4=1.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: LYN token contract 0x302DFaF2CDbE51a18d97186A7384e87CF599877D
  • Evidence: Tier‑1 — https://bscscan.com/token/0x302DFaF2CDbE51a18d97186A7384e87CF599877D, https://bscscan.com/tx/0x6cbc8ac3320bed49cec55027ad567bbd8bf338f295c758d59b3bf390b2c1109f
  • Why sufficient / why not (one line): there is a verifiable onchain artifact (the contract + the creation transaction with a timestamp).
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: the docs describe onchain accounting of actions/provenance, but the addresses/contracts of the protocol logic are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/lyn-docs/decentralized-video-ai-layer
  • Why sufficient / why not (one line): without addresses/contracts, this remains a description of the architecture, not proof of implemented onchain logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without onchain, product generation (the web app) does not break down; the onchain value (audit/provenance/settlement) is not confirmed as a mandatory implementation.
  • Evidence: Tier‑1 — https://www.everlyn.ai, https://lynlabs.gitbook.io/lyn/lyn-docs/decentralized-video-ai-layer
  • Why sufficient / why not (one line): Tier‑1 has no proof that without the blockchain the key property is not achieved in practice (with addresses/rules).
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, LYN (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x302DFaF2CDbE51a18d97186A7384e87CF599877D
  • Why sufficient / why not (one line): the token and its parameters (max supply, contract) are publicly confirmed by the explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): LYN is used for agent minting, subscriptions and payment for activities/interactions in the network.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/technical-designs/usdlyn-overview
  • Why sufficient / why not (one line): Tier‑1 describes mint/subscription fees and settlement between participants in LYN.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): staking/delegation of LYN is described as a mechanism for security and participation in rewards (delegation to AAPI).
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/technical-designs/usdlyn-overview
  • Why sufficient / why not (one line): Tier‑1 directly describes staking LYN for network security and delegation to AAPI for a share of rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): LYN holders vote in the Lyn DAO on architectural/operational proposals.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/technical-designs/usdlyn-overview
  • Why sufficient / why not (one line): Tier‑1 describes governance and the access threshold for voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token (e.g., with a stablecoin) is not assessed/not proven per Tier‑1.
  • Evidence: Tier‑1 — https://lynlabs.gitbook.io/lyn/technical-designs/usdlyn-overview
  • Why sufficient / why not (one line): the docs describe the utility of LYN but do not prove that specifically the native token is irreplaceable.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.everlyn.ai A generation web app is available (AI_2 “what you can touch”: text/image→video, text→image).
Tier‑1 https://lynlabs.gitbook.io/lyn Description of Lyn/Everlyn‑1 as a video‑AI + “agential” ecosystem (AI_1).
Tier‑1 https://raw.githubusercontent.com/Everlyn-Labs/Everlyn-1/main/README.md The official Everlyn‑1 repository: open‑source research directions (AI reality, Tier‑1 repo).
Tier‑1 https://lynlabs.gitbook.io/lyn/lyn-docs/decentralized-video-ai-layer Tier‑1 description of the “decentralized video AI layer”, v‑API/agents, the idea of onchain provenance and the role of the token.
Tier‑1 https://lynlabs.gitbook.io/lyn/technical-designs/usdlyn-overview Tier‑1 tokenomics/utility: governance, staking, mint/subscription fees, gas fees, supply 1B, inflation.
Tier‑1 https://bscscan.com/token/0x302DFaF2CDbE51a18d97186A7384e87CF599877D Onchain fact: the LYN token, BEP‑20, max supply 1B, contract.
Tier‑1 https://bscscan.com/tx/0x6cbc8ac3320bed49cec55027ad567bbd8bf338f295c758d59b3bf390b2c1109f Timestamp of the contract creation (token launch/creation date: 2025‑10‑01).

No comments to display

Back to top