cryptosnif
1inch Token (1INCH)
Documentary contract0x111111111117dc0aa78b770fa6a738034120c302
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 evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
This dossier examines the pinned primary documentation for 1inch Token (1INCH). The documentary subject is token address 0x111111111117dc0aa78b770fa6a738034120c302 on Ethereum mainnet. Current deployment and operation remain unverified within this review.
Established facts
The Aave V3 Ethereum registry lists the 1INCH token at 0x111111111117dc0aa78b770fa6a738034120c302 under its ONE_INCH key. Its underlying-token entry identifies the asset associated with a documented reserve, separately from receipt and debt tokens.
The pinned OneInch Solidity source initializes a token named 1INCH Token, symbol 1INCH, and creates 1.5 billion units scaled by 10 to the power 18 for the supplied owner. It transfers ownership to that address and includes an additional mint function restricted to the owner. The initialization amount therefore establishes no immutable maximum or current circulating supply. The file imports token-permission, burning and ownership components whose behavior and deployed versions were not independently tested.
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
The source includes a further owner-restricted mint function. A supply assessment would need to identify the deployed implementation and current owner permissions before drawing conclusions from the initialization amount.
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.
Evidence that 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.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Voting concentration, delegations, timelocks and veto powers.
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 1inch Token (1INCH) as the ONE_INCH underlying-token entry at 0x111111111117dc0aa78b770fa6a738034120c302, 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 address book uses the ONE_INCH key for the 1INCH token. Token identity alone does not establish a swap-aggregation service or its current behavior. 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.
Inspect the primary source ↗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.
Inspect the primary source ↗1inch/1inch-token: contracts/OneInch.sol (6eb63e4b8477)
The pinned OneInch Solidity source imports ERC20Permit, ERC20Burnable and Ownable. Its constructor names the token 1INCH Token, uses symbol 1INCH, mints 1.5 billion units scaled by 10 to the power 18 to the supplied owner and transfers ownership to that owner. Its external mint method is restricted by onlyOwner. The constructor amount is not a verified current supply or an immutable maximum: the source contains that further owner-restricted mint method. Imported behavior and deployed bytecode were not independently verified. 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.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.