cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Governance / CT-CRV-001

Curve DAO Token (CRV)

Ethereum · Token contract · Documentation reviewed

Documentary contract0xd533a949740bb3306d119cc777fa900ba034cd52

The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

This dossier examines the pinned primary documentation for Curve DAO Token (CRV). The documentary subject is token address 0xd533a949740bb3306d119cc777fa900ba034cd52 on Ethereum mainnet. Current deployment and operation remain unverified within this review.

Established facts

The Aave V3 Ethereum registry records CRV at 0xd533a949740bb3306d119cc777fa900ba034cd52 as an underlying token, the asset associated with a documented reserve.

The Curve DAO README describes voting based on locking tokens. Its contract index assigns separate roles to the token, token-issuance contract, liquidity-gauge controller, vesting contracts and VotingEscrow, the contract used to lock CRV for governance. The pinned lock implementation defines a maximum interval of 4 times 365 days in seconds. Voting weight varies with time, and the implementation includes functions to add locked tokens and extend unlock times. Those code observations do not identify present lock holders, active releases or the implementation currently deployed.

Unknowns

This dossier contains no independently reproduced operational observations. Current deployed versions, controller identities, beneficial ownership, supply, concentration, usage, liquidity and the complete incident record remain unverified. Documentary review supplies no operational scoring coverage.

Consequences

Holding CRV and participating through the documented lock mechanism are different research questions. Assessing actual governance influence would require dated lock, voting and controller observations, alongside deployment checks.

Verdict

Unrated, with 0% scoring coverage. The captured documentation defines the scope of further research. Every operational scoring criterion remains unknown within this review, so the corpus supports no total score or investment-return forecast.

What would change it

A further review would compare documented identities with deployed code, identify current control powers and reproduce mechanism-specific observations with dates and test conditions. Supply, usage and incident evidence would require separate checks before method calibration and editorial review could support a score.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Voting concentration, delegations, timelocks and veto powers.

03 / Evidence

Inspect the evidence

Sources behind this analysis

bgd-labs/aave-address-book: src/ts/AaveV3Ethereum.ts (c8f1011decd0)

The pinned Aave V3 Ethereum address book records Curve DAO Token (CRV) as the CRV underlying-token entry at 0xd533a949740bb3306d119cc777fa900ba034cd52, with chain identifier 1. An underlying token is the asset associated with a documented pool reserve. The file lists distinct receipt-token and debt-token addresses; these must not be substituted for the underlying token identity. This registry establishes Aave's documented integration, without establishing present borrowing permissions, actual balances, issuer deployments or protocol activity. The catalogue has no CoinGecko ID for this record; its private subject ID preserves that absence. These are primary documentary observations from the pinned files. No deployed bytecode, live transaction, reserve backing, redemption, controller ownership, beneficial ownership, voting concentration, current liquidity or complete incident history was independently checked. No current market price, investment return or score is established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 59e703630555c1093264774cf7b787fd6dab41971a487ffcc9f71b0888145fe1

bgd-labs/aave-address-book: README.md (c8f1011decd0)

The Aave address book README describes a registry of ecosystem contract addresses for Solidity and JavaScript applications. Its Ethereum example pairs the AaveV3Ethereum module with chain identifier 1. Generated registries and published package versions identify what documentation is being read. This review did not run the advertised generation, sanity or verification tests. This review read the pinned primary files and their licence captures. No deployed bytecode, transaction, network node, controller balance or governance vote was independently inspected. Current ownership, concentration, operational activity, market conditions and complete incident history remain unknown. These documentary observations provide no scoring coverage or forecast of investment returns.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: c006e4dc135aa5704da385b02fc7fc9da5eb9aeb3aae6b8994a9d95df03c01e4

curvefi/curve-dao-contracts: README.md (fa127b1cb7bf)

The Curve DAO contract README describes CRV as the DAO token and explains that its modified Aragon voting mechanism weights votes using token locking. This distinguishes holding the ordinary token from participating through a lock. The README links audits and a bug bounty; this review did not read or reproduce those audit reports and assigns no audit coverage. These are primary documentary observations from the pinned files. No deployed bytecode, live transaction, reserve backing, redemption, controller ownership, beneficial ownership, voting concentration, current liquidity or complete incident history was independently checked. No current market price, investment return or score is established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 79ec9f84678bce7e0831077d8446af0c8320d3632578c82be6261d799dbc9f01

curvefi/curve-dao-contracts: contracts/README.md (fa127b1cb7bf)

The Curve contract index distinguishes the ERC20CRV token, Minter issuance contract, GaugeController liquidity-gauge controls and VotingEscrow for locking CRV to participate in governance. Separate vesting contracts manage token releases. Those named modules describe responsibilities without establishing present administrators, gauge allocations or active vesting positions. These are primary documentary observations from the pinned files. No deployed bytecode, live transaction, reserve backing, redemption, controller ownership, beneficial ownership, voting concentration, current liquidity or complete incident history was independently checked. No current market price, investment return or score is established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 73d7241e25cb18cc3f1cc3992072c25d526c32a42fb5cad7349311661c5c9d1f

curvefi/curve-dao-contracts: contracts/VotingEscrow.vy (fa127b1cb7bf)

The pinned VotingEscrow implementation gives voting weight a time-dependent slope and defines a maximum lock interval of 4 times 365 days in seconds. It includes methods to create locks, add tokens, extend unlock times and record checkpoints. This source-level time limit does not establish a current user lock, voting concentration or the code deployed at a live address. These are primary documentary observations from the pinned files. No deployed bytecode, live transaction, reserve backing, redemption, controller ownership, beneficial ownership, voting concentration, current liquidity or complete incident history was independently checked. No current market price, investment return or score is established.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 74155a1ffee9bed06b3b4f3bc89d840ef2e376675b9974520cd5860a9803dc43

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation