Skip to main content

Locked.Money

Locked.Money — 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).

Locked.Money — an application/set of smart contracts on the Base network (EVM), token (symbol: LMY). The project’s docs claim self‑custody vaults and AI components for verifying/automating actions (see Evidence).

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: self‑custody “vaults” (multi‑sig) and related contracts/tools described in the project’s GitBook.
  • Who it’s for: users who need self‑custody and asset management via a vault approach (per the docs).
  • Why onchain/token: onchain is used for vault contracts/access; the LMY token — for staking/distribution of incentives (per the tokenomics).

How it works (very briefly)

  1. The user does: creates a vault and adds signers (per the docs).
  2. The system does: stores/enforces the access rules via the onchain contracts of the vault system (for addresses, see Evidence).
  3. The user gets: asset management via the vault mechanics.
  4. Where the blockchain is: Base; the onchain contracts include vault factory/vault, staking, vesting and the subscription payment contract (per the docs).
  5. Token role (if any): LMY participates in staking distributions and, per the tokenomics, is linked to the distribution of a share of fees (see Evidence).

Quick links: AI thesis fit

Project passport

Field Value
Project name Locked.Money
Also known as (aliases) Locked Money; locked.money; LMY
Logo (logo) ../assets/334_locked-money_logo.png
Token symbol (ticker) LMY
Category Infra | DeFi
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Base on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x739f93504a9e26D5973862Dbc4A44178cC264852
Token model (token_type) utility (staking + rewards)
Max supply 10,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) distribution to staking/LP staking/reserve (see the docs)
Governance —
Admins/keys multisig (vaults; as claimed)
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI co-signer + automation assistant
Use‑case (use_case) self-custody vaults + tools
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 2 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Locked.Money, per the GitBook documentation, describes a self‑custody vault approach: “vaults” with multi‑sig and onchain access control, as well as additional tools (swap, staking, etc.). The documentation also claims AI components: an AI co‑signer for transaction verification and an AI assistant for automation (partly — in future plans/pricing tiers; for details, see the docs).

In this card, the onchain part is confirmed via the Contract Addresses page in the GitBook (addresses of vault factory/vault, staking, vesting, etc.) and via the token page on BaseScan.

Features/modules

  • Vaults: seedless multi‑sig vaults (per the description in the docs).
  • AI co‑signer / assistant: transaction verification and automation (per the description in the docs).
  • Onchain contracts: vault factory/vault, staking, vesting, subscription payment (per the docs).

Typical scenarios

  • Scenario 1: a user creates a vault → adds signers → manages assets via the vault rules.
  • Scenario 2: a user initiates a transaction → the AI co‑signer (per the description) checks the risks → the transaction is either confirmed or rejected.

Getting started (wallet/network)

  • What you need: follow the Quickstart/Guides in the project’s GitBook documentation.
  • Network/chain: Base.
  • Fees: Base network fees apply to onchain operations.

Architecture/tech (non‑AI)

  • Components: a set of onchain contracts on the Base network (vault factory, vault, staking, vesting, subscription payment) + the application/interface (per the docs).
  • Where logic runs: ownership/access rules — onchain; the interface and automation — outside the chain (by implication; the AI implementation details are not disclosed per Tier‑1).

Token/economics (expanded, no forecasts)

  • Utility and incentives: the tokenomics describes the distribution and staking categories.
  • Distribution/vesting: the tokenomics describes the allocation breakdown and schedules.
  • Contracts: the GitBook provides the addresses of the staking and vesting contracts.

Governance

  • Governance: an explicit governance model is not recorded per Tier‑1 (re‑checking against primary sources is needed).

Security and incidents

  • Security: the docs mention multi‑sig vaults and AI transaction verification; no public audit reports were found per Tier‑1.

Project status and timeline

  • Current status: the product/docs are available.
  • Roadmap: see links_*.

Ecosystem/integrations

  • Integrations: the docs describe tools and plans; details require a separate review.

AI component of the project

  • What is real AI here? The docs claim an AI co‑signer (transaction verification) and an AI assistant (automation/insights), but this card has no tech details/metrics per Tier‑1.
  • What is truly onchain? The GitBook publishes a list of smart contract addresses on Base (vault factory/vault, staking, vesting, subscription payment).
  • Why is a token needed? The tokenomics describes staking/distributions and a link to “fees recycled back into the system” (per Tier‑1).
  • Red flags / what to double‑check: (1) how exactly the AI co‑signer is implemented (model/rules/limitations), (2) confirmation of audits, (3) which operations are critical onchain and which remain offchain.

DecAI Fit flags (0/1) and calculation

  • AI: AI_0=0; AI_1=1; AI_2 (decision): 0; AI_3=0; AI_4=0 → ai_score=1
  • Onchain: OC_1=1; OC_2=1; OC_3=0 → onchain_score=2
  • Token: TK_0=0; TK_1=0; TK_2=1; TK_3=0; TK_4=0 → token_score=1
  • Evidence: E_AI_T1=1; E_OC_T1=1; E_TK_T1=1; E_only_T3=0 → evidence_score=3
  • Summary: S=7 → decai_fit_base=4 → AI cap=3 → DecAI Fit=3/6

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity medium 2
Token necessity low 1
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 docs contain statements about AI features, but a separate roadmap intent as “plans without proof” is not singled out.
  • Evidence: Tier‑1 — https://locked-money.gitbook.io/locked-money-guide/the-why-and-what-of-locked-money/how-locked-money-works
  • Why sufficient / why not (one line): AI is described as part of the product, so we count AI_1, not AI_0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the docs describe an AI co‑signer (checking transactions for scams/risks) and an AI assistant for automation/insights.
  • Evidence: Tier‑1 — https://locked-money.gitbook.io/locked-money-guide/the-why-and-what-of-locked-money/how-locked-money-works
  • Why sufficient / why not (one line): this is a Tier‑1 description of the AI features and their purpose.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): no Tier‑1 demo/guide with reproducible steps for the AI features is recorded.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 demo/quickstart for the AI part, the flag remains 0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no measurable quality metrics/accuracy metrics of the AI verification were found in Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the tech description/architecture of the AI part is not recorded per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without Tier‑1 tech docs on the AI component, the flag is 0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: the LMY token and the system contracts (vesting, staking, vault factory/vault) are published in the docs.
  • Evidence: Tier‑1 — https://locked-money.gitbook.io/locked-money-guide/tokenomics/contract-addresses
  • Why sufficient / why not (one line): the official list of contracts provides Tier‑1 confirmation of the onchain addresses.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: onchain vaults with multi‑sig/access and the related system contracts (not just the token).
  • Evidence: Tier‑1 — https://locked-money.gitbook.io/locked-money-guide/tokenomics/contract-addresses
  • Why sufficient / why not (one line): the addresses of vault factory/vault and other contracts are published, which confirms the onchain logic of the product.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: this card has no Tier‑1 argument that replacing the blockchain breaks a key property per the SSOT criteria.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 “blockchain‑critical” justification, we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the LMY token exists.
  • Evidence: Tier‑1 — https://basescan.org/token/0x739f93504a9e26D5973862Dbc4A44178cC264852
  • Why sufficient / why not (one line): the onchain token page confirms the existence of the token.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): mandatory payment for the basic service in the LMY token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the tokenomics describes distributions/staking, but does not record LMY as a mandatory “payment for the service”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the tokenomics describes staking categories and the redistribution of a share of Pro Plan fees to stakers.
  • Evidence: Tier‑1 — https://locked-money.gitbook.io/locked-money-guide/tokenomics/tokenomics
  • Why sufficient / why not (one line): the Tier‑1 tokenomics describes incentives and distributions in favor of stakers.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance use of the token is not recorded in the Tier‑1 tokenomics.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 description of governance mechanics, the flag is 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): No Tier‑1 argument about the replaceability of the token was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a Tier‑1 justification of replaceability/irreplaceability, we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://locked-money.gitbook.io/locked-money-guide/the-why-and-what-of-locked-money/how-locked-money-works The vault approach and the AI co‑signer/assistant are claimed as product features.
Tier‑1 https://locked-money.gitbook.io/locked-money-guide/tokenomics/contract-addresses The addresses of smart contracts on Base are published (vault factory/vault, staking, vesting, subscription payment).
Tier‑1 https://basescan.org/token/0x739f93504a9e26D5973862Dbc4A44178cC264852 Onchain fact: the Locked Money (LMY) token, contract and max total supply.
Tier‑1 https://locked-money.gitbook.io/locked-money-guide/tokenomics/tokenomics Tokenomics: distribution and staking categories (allocation breakdown) and the described link to the distribution of a share of fees.

No comments to display

Back to top