Skip to main content

Singularry

Singularry — 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).

Singularry — a project positioned per Tier‑1 sources (GitHub + whitepaper) as an AI‑powered DeFi platform: a smart‑contract wallet + a set of onchain strategies/modules and an LLM‑based chat interface for launching operations.

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: a DeFi platform with a smart‑contract wallet (Diamond/EIP‑2535) and “playbooks” (a set of onchain operations/strategies) that can be launched via the UI and/or chat interface.
  • Who it’s for: users who want to manage DeFi operations/strategies via a single interface; developers/integrators (per the description in the repository).
  • Why onchain/token: onchain is for executing operations via smart contracts and integrations with protocols; the project token’s role as utility/gov is not established per Tier‑1 sources in this card.
  • What you can actually touch (Tier‑1): the web app in links_*: https://app.singularry.org/ (the presence of the link is confirmed; functionality requires separate verification).

How it works (very briefly)

  1. The user does: connects a wallet, selects an action in the UI or formulates a command in the chat interface.
  2. The system does: classifies intent (swap/bridge/lend/borrow/stake), builds steps and forms transactions.
  3. The user gets: execution of onchain operations (via the smart‑contract wallet and integrated protocols) and state monitoring/control.
  4. Where the blockchain is: the Tier‑1 README specifies priority for BNB Smart Chain mainnet and compatibility with other EVM networks; it also provides a list of infrastructure/strategy contract addresses.
  5. Token role (if any): the existence of the token is visible via the BscScan link; the practical role of the token is not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Singularry
Also known as (aliases) Singularry DeFi
Logo (logo) ../assets/908_singularry_logo.png
Token symbol (ticker) —
Category DeFi
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x18ea4df6a9cde2472f2321a4ec77da106498a66e
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The practical role of the token (utility/gov/fees) is not established per Tier‑1 sources.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) LLM chat + tool-use (intent classification + on-chain ops execution)
Use‑case (use_case) AI management of DeFi operations/strategies via smart-contract wallet
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Per the repository’s Tier‑1 README, the project describes a DeFi platform with a smart‑contract wallet (Diamond proxy per EIP‑2535) and a set of modular “facets” for different operations/strategies. The same Tier‑1 source claims an LLM‑based chat interface (Claude/GPT via SDK) and a tool‑use architecture for intent recognition and execution of multi‑step actions.

The whitepaper (Tier‑1 PDF) describes an “autonomous AI system” and a high‑level architecture (model, memory, tool ecosystem). In this card, the whitepaper is used as a source of claims/intents; verification of the actual implementation relies on the repository and onchain artifacts.

AI component of the project

  • What is real AI here? an LLM‑based chat interface with intent classification and generation of steps/transactions (described in the Tier‑1 README); the whitepaper additionally describes memory/integration components.
  • What is truly onchain? infrastructure/strategy smart contracts and the contract addresses listed in the Tier‑1 README; integrations with DeFi protocols.
  • Why is a token needed? how the token is used in the product is not established per Tier‑1 sources; we record it as “not established”.
  • Red flags (based on the information found): the whitepaper contains a strong narrative about autonomy/financial goals; without a link to verifiable onchain/code artifacts, such claims should not raise the flags.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The AI chat interface accepts user requests (swap/bridge/lend/borrow/stake), classifies intent and launches multi‑step onchain operations.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry
  • Why sufficient / why not (one line): The Tier‑1 README lists the features of the AI chat interface and the expected actions.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The project has a public web app link (demo/interface) that can be used as an entry point.
  • Evidence: Tier‑1 — https://app.singularry.org/
  • Why sufficient / why not (one line): The presence of a public app link records a demo surface; functionality requires separate verification.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/singularry/singularry
  • Why sufficient / why not (one line): Quality metrics are not recorded per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): Tier‑1 sources describe the stack/architectural components (tool‑use, intent classification; in the whitepaper — agent/memory architecture).
  • Evidence: Tier‑1 — https://github.com/singularry/singularry ; Tier‑1 — https://singularry.org/singularry-whitepaper.pdf
  • Why sufficient / why not (one line): There is a Tier‑1 description of the architecture/stack sufficient to set 1.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain (BSC), EVM
  • Addresses/identifiers: the Tier‑1 README provides infrastructure/facet contract addresses on BSC; links_* also gives the token address on BSC: 0x18ea4df6a9cde2472f2321a4ec77da106498a66e
  • Evidence: Tier‑1 — https://github.com/singularry/singularry ; Tier‑1 — https://bscscan.com/token/0x18ea4df6a9cde2472f2321a4ec77da106498a66e
  • Why sufficient / why not (one line): The Tier‑1 README records the network and specific contract addresses; the explorer link records the token contract.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: a smart‑contract wallet (Diamond proxy) and a set of facets/strategies for operations with DeFi protocols.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry
  • Why sufficient / why not (one line): The Tier‑1 README describes the wallet/facets and lists contract addresses for infrastructure and strategies.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the blockchain, execution of DeFi operations/strategies via smart contracts and protocols is impossible; only another blockchain can be a replacement, not a centralized DB.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry
  • Why sufficient / why not (one line): The described functionality is directly tied to onchain integrations and smart contracts.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token (per the BscScan link).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x18ea4df6a9cde2472f2321a4ec77da106498a66e
  • Why sufficient / why not (one line): The Explorer page confirms the existence of the token contract.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Per Tier‑1, it is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry ; Tier‑1 — https://singularry.org/singularry-whitepaper.pdf
  • Why sufficient / why not (one line): Tier‑1 terms/docs describing payment with the token are required.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties involving the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry ; Tier‑1 — https://singularry.org/singularry-whitepaper.pdf
  • Why sufficient / why not (one line): Tier‑1 artifacts describing incentive mechanics are required.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1.
  • Evidence: Tier‑1 — https://github.com/singularry/singularry ; Tier‑1 — https://singularry.org/singularry-whitepaper.pdf
  • Why sufficient / why not (one line): A Tier‑1 description of the governance process is required.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token has not been assessed (the role of the token in the product is not established).
  • Evidence: Tier‑1 — https://github.com/singularry/singularry
  • Why sufficient / why not (one line): Without a Tier‑1 description of the utility/gov role, replaceability cannot be assessed correctly.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/singularry/singularry Tier‑1 description of the product, AI chat interface, stack, supported networks and contract addresses.
Tier‑1 https://singularry.org/singularry-whitepaper.pdf Tier‑1 whitepaper: claimed AI goals/architecture (intent/roadmap/concept).
Tier‑1 https://app.singularry.org/ Public web app surface (demo/interface).
Tier‑1 https://bscscan.com/token/0x18ea4df6a9cde2472f2321a4ec77da106498a66e The existence of the token contract in the BSC explorer.
Tier‑1 https://github.com/singularry/sly-audits Repository with audit materials (the presence of the source).
Tier‑2 https://coinmarketcap.com/currencies/singularry/ Aggregator profile (context).
Tier‑2 https://www.coingecko.com/en/coins/singularry Aggregator profile (context).