Skip to main content

Almanak

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

Almanak — an AI/Agents + DeFi project on Ethereum, token (symbol: ALMANAK).

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 platform for creating and running automated DeFi strategies (strategies/“agents”), with a non‑custodial model and onchain components (including vault tokens).
  • Who it’s for: users and teams who want to automate the management of DeFi strategies and issue “packaged” strategies via onchain vaults.
  • Why onchain/token: onchain is used for contracts (including vaults/accounting) and for the ALMANAK utility token (access/payment for certain features, incentives, as described in the whitepaper).
  • What you can actually touch (Tier‑1): the Vaults web interface at app.almanak.co + onboarding/guides in the official docs.

How it works (very briefly)

  1. The user does: configures a strategy and deploys it as a Deployment (per the project documentation).
  2. The system does: runs the automated execution of the strategy and manages permissions via non‑custodial wallets.
  3. The user gets: automatic execution of the strategy and (if the vault mode is used) a tokenized strategy product.
  4. Where the blockchain is: the ALMANAK token and the onchain components (including vaults) run on EVM networks; the fact of the token is confirmed by the contract on Ethereum.
  5. Token role (if any): a utility token for platform features (compute/discounts/incentives; details — in the whitepaper).

Quick links: AI thesis fit

Project passport

Field Value
Project name Almanak
Also known as (aliases) ALMANAK
Logo (logo) —
Token symbol (ticker) ALMANAK
Category AI/Agents | DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xDeFA1D21c5F1cbeac00eeB54B44C7D86467cc3a3
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000
Issuance fixed
Tokenomics (tokenomics, brief) utility token for platform features; staking/incentive program are described in the whitepaper
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI-assisted DeFi strategies/agents
Use‑case (use_case) DeFi strategy automation
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

In its official documentation, Almanak describes itself as a platform for creating and running automated strategies in DeFi (Deployments/Strategies) with a non‑custodial model (Safe/Zodiac‑based wallets) and onchain components (vaults).

Features/modules

  • Deployments: deployed strategies that perform actions on behalf of the user within the specified permissions.
  • Strategies: Python strategies that define the decision logic and the parameters of the risk model.
  • Wallets: non‑custodial wallets with limited permissions (Safe/Zodiac).
  • Vaults: onchain vaults that can tokenize a strategy and issue vault tokens.

Typical scenarios

  • Scenario 1: a user configures a strategy → deploys a Deployment → the strategy is executed automatically.
  • Scenario 2: a user/strategy creator connects the vault mechanics → issues a tokenized strategy (vault token) → other users can interact with the strategy product via the vault.

Getting started (wallet/network)

  • What you need: follow the Quickstart/onboarding in the official Almanak docs.
  • Network/chain: EVM networks (the ALMANAK token is confirmed on Ethereum).
  • Fees: network fees and platform fees (if applicable) — details depend on the specific scenario and are described in the docs/in the app.

Architecture/tech (non‑AI)

  • Components: offchain strategy execution/infrastructure + onchain contracts (vaults, token) + non‑custodial wallets/permissions.
  • Where logic runs: strategy execution is predominantly offchain; accounting/tokenization/part of the rules — onchain (within the scope of the description in the docs).

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): in the whitepaper, ALMANAK is described as a utility token for access to/use of the platform, including payments/discounts for compute and participation in the incentive program (staking/lock).
  • Supply parameters (Tier‑1): max supply is given as 1,000,000,000 (Etherscan).
  • What to double‑check for “token necessity”: which platform features require specifically ALMANAK (rather than alternative ways of payment/access), and which features are already active vs. “planned” per the roadmap.

Governance

  • Per Tier‑1 (whitepaper), a governance utility of the token is mentioned, but specific processes/parameters/procedures of onchain/offchain governance are not recorded.

Security and incidents

  • Audits: a third‑party audit report has been published (the link is in links_*).
  • Bug bounty / incidents: not established per Tier‑1.

Project status and timeline

  • Current status: active (there is a working token and up‑to‑date documentation/roadmap).
  • Roadmap: https://docs.almanak.co/docs/roadmap

Ecosystem/integrations

  • Integrations (Tier‑1): Safe and Zodiac are listed in the official docs as part of the security/permission model of the wallets.

AI component of the project

  • What is real AI here? In the Tier‑1 docs/whitepaper, the project describes an AI‑assisted/AI‑driven approach to automating and adapting strategies; at the same time, a Tier‑1 tech description of specific models and quality metrics of the AI models are not recorded.
  • What is truly onchain? The ALMANAK token on Ethereum; the docs describe onchain vaults and the tokenization of strategies via vault tokens.
  • Why is a token needed? In the whitepaper, ALMANAK is described as a utility token for access to platform features (payments/discounts for compute) and participation in incentive mechanisms.
  • Red flags (based on the information found): there is no verified Tier‑1 breakdown of specific AI models/metrics (AI_3=0); the list of key protocol contracts other than the token has not been compiled (the onchain part requires an inventory of addresses).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is not only claimed as an intent but is described as part of the current platform (an AI‑assisted approach).
  • Evidence: Tier‑1 — https://docs.almanak.co/
  • Why sufficient / why not (one line): in the Tier‑1 source, AI is described as a component of the platform, so this is more than “intent”.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI‑assisted solving of strategy analysis/adaptation and risk management tasks (as positioned in the docs).
  • Evidence: Tier‑1 — https://docs.almanak.co/
  • Why sufficient / why not (one line): “what it does” is described at the level of a feature (AI‑assisted analysis/adaptation), but without specific metrics/models.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public web interface app.almanak.co (Vaults) and Tier‑1 documentation/onboarding.
  • Evidence: Tier‑1 — https://app.almanak.co/ ; https://docs.almanak.co/
  • Why sufficient / why not (one line): there is a reproducible “touch surface” + official documentation.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.almanak.co/docs/strategies/metrics
  • Why sufficient / why not (one line): Tier‑1 describes metrics of strategy/action execution, but quality metrics of the AI models as such are not recorded → the decision remains 0 (conservatively).

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

  • AI_4 (decision): 0
  • Claim (one line): A Tier‑1 tech description of the AI models/versions (architecture of the AI part) is not recorded.
  • Evidence: Tier‑1 — https://docs.almanak.co/
  • Why sufficient / why not (one line): there is a tech description of the platform/strategies, but without specifics on AI models/versions.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the ALMANAK token: 0xDeFA1D21c5F1cbeac00eeB54B44C7D86467cc3a3
  • Evidence: Tier‑1 — https://etherscan.io/token/0xDeFA1D21c5F1cbeac00eeB54B44C7D86467cc3a3
  • Why sufficient / why not (one line): the onchain fact of the token and the network is confirmed by the explorer.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: vaults (tokenization of strategies via vault tokens) are described as an onchain component.
  • Evidence: Tier‑1 — https://docs.almanak.co/
  • Why sufficient / why not (one line): the Tier‑1 docs describe onchain vaults as part of the product, not just the issuance of a token.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established per Tier‑1 that a key property of the product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without an explicit justification of the “trustless criticality” of onchain — we set 0.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a utility token, ALMANAK.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xDeFA1D21c5F1cbeac00eeB54B44C7D86467cc3a3
  • Why sufficient / why not (one line): the name/symbol of the token and the contract are confirmed by the explorer.

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): ALMANAK is described as a token for payments/discounts for compute/platform resources.
  • Evidence: Tier‑1 — https://almanak.co/almanak-mica-wp.pdf
  • Why sufficient / why not (one line): the payment/discount utility is described in the whitepaper (Tier‑1).

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

  • TK_2 (decision): 1
  • Claim (one line): the whitepaper describes staking/locking and participation in a community‑emissions rewards program.
  • Evidence: Tier‑1 — https://almanak.co/almanak-mica-wp.pdf
  • Why sufficient / why not (one line): the incentive program is described as part of the token utility in Tier‑1.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): a governance utility of the token is described as part of the model, but the specific implementation/procedures require separate verification.
  • Evidence: Tier‑1 — https://almanak.co/almanak-mica-wp.pdf
  • Why sufficient / why not (one line): without specific governance parameters/a governance process, the flag remains 0 (conservatively).

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token with alternative payment/access models is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without an explicit Tier‑1 comparison “token only vs. subscription/stablecoins”, we do not raise the flag.

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.almanak.co/ Description of the product and components (Deployments/Strategies/Wallets/Vaults), including the AI‑assisted positioning and the existence of onchain vaults.
Tier‑1 https://almanak.co/almanak-mica-wp.pdf ALMANAK token utility (access to/use of the platform; compute payments/discounts; staking/incentive program) and the general model of the token.
Tier‑1 https://etherscan.io/token/0xDeFA1D21c5F1cbeac00eeB54B44C7D86467cc3a3 Onchain fact of the ALMANAK token: name/symbol, max supply and contract on Ethereum.
Tier‑1 https://github.com/zokyo-sec/audit-reports/tree/main/Almanak Existence of a published audit report (third‑party audit).
Tier‑1 https://app.almanak.co/ Public Vaults interface (App/Demo surface).
Tier‑1 https://docs.almanak.co/docs/strategies/metrics Tier‑1: documentation on the metrics of strategy/action execution (context for the product’s “metrics layer”).
Tier‑2 https://www.coingecko.com/en/coins/almanak Reference token profile and link navigation.
Tier‑2 https://coinmarketcap.com/currencies/almanak/ Reference token profile and link navigation.

No comments to display

Back to top