What Is Almanak?

Almanak describes itself as an agentic platform for building, deploying and managing autonomous DeFi agents. Its current website frames the product as a way to trade and earn yield across crypto and tokenized markets using a team of financial agents while remaining non-custodial and private by design.

The important difference is that Almanak is not simply a chatbot that places swaps. Its workflow looks much more like a quant-development stack:

discover → specify → code → test → permission → deploy → monitor.

The Almanak Workflow

Edge: Opportunity Discovery, Not a Magic Alpha Feed

Current Edge documentation says 46 specialized detection agents continuously scan onchain and offchain sources. Signals receive an Alpha Score from 0 to 100, confidence, risk level, expiration window, chain and token context. Almanak says the signals are deduplicated and passed through a multi-model consensus process.

The disclaimer matters: an Alpha Score is model output, not due diligence and not a probability of profit. A 90 score does not mean a 90% chance of making money.

Users can send a signal into Almanak Code, which can generate a strategy requirements document and executable Python code. That creates a direct pipeline from market anomaly → specification → software.

Almanak Code: Natural Language Should End in Real Code

Almanak Code is an LLM-powered coding agent that understands DeFi primitives such as swaps, lending, LP positions and perpetuals. Users can describe a strategy conversationally or write Python directly. Almanak says the resulting strategy is versioned code the user can own and store in GitHub.

This is a major advantage over black-box AI trading. A user can inspect exactly how a leverage loop, LP rebalance or basis strategy is implemented before funding it.

Deterministic vs LLM-Driven Strategies

The Almanak SDK distinguishes between deterministic strategies and agentic strategies. Deterministic strategies encode rules explicitly in Python. Agentic strategies can let an LLM make decisions using Almanak tools and policy controls.

For substantial capital, our default preference is simple: use AI to develop, challenge and improve the strategy, then use deterministic execution whenever possible. LLM-based decision making adds model uncertainty on top of market and smart-contract risk.

Simulation Before Capital

Almanak's website and SDK emphasize mainnet-fork simulation, backtesting and Anvil-based testing before deployment. This can catch errors involving token decimals, protocol approvals, route assumptions, health-factor logic, liquidity and state handling.

Fork tests cannot reproduce every future gas spike, MEV environment, oracle failure, exploit or market-regime shift.

DN Almanak Agent Strategy Safety & Break-Even Lab

Autonomous trading needs a different calculator from a normal exchange-fee comparison. This tool models whether the expected return covers recurring execution costs and whether the deployment controls are proportionate to the capital being delegated.

Safe + Zodiac: The Most Important Part of Almanak

Current Almanak documentation says each Almanak wallet combines the user's own wallet, a Deployment EOA, a Safe smart account and a Zodiac Roles Modifier. The Safe is a 1-of-1 wallet with the user as sole owner.

The Deployment EOA signs and broadcasts strategy transactions, but Zodiac can restrict which contracts it may call, which functions it may use and which parameters are allowed. Almanak's deploy docs give the example of an Aave strategy being limited to Aave-related contracts instead of receiving arbitrary wallet access.

This is the correct direction for autonomous capital.

One Safe Per Chain, Separate Agent Permissions

Current deploy documentation says each user gets one Safe per chain. Multiple agents on the same chain can share that Safe while operating under independent permission scopes. That is convenient, but it means users should monitor both strategy-level risk and aggregate wallet exposure.

The Deployment EOA Is Not Your Main Wallet

The Deployment EOA is a separate execution component. Almanak says its private key is encrypted at rest and accessed through a dedicated signer service using Google-provided enterprise-grade key-management infrastructure. If compromise is suspected, the user is instructed to revoke the EOA's permissions and a fresh execution EOA can be created.

The key point is that compromise of an execution key should still be contained by the permissions the user approved.

Gateway Architecture: Strategy Containers Have No Secrets

The current website and SDK describe a gateway architecture in which strategy containers do not contain wallet secrets and do not have unrestricted internet access. External calls are mediated through a controlled gateway sidecar.

This narrows the attack surface and makes it harder for arbitrary generated code to exfiltrate secrets or make unapproved network calls.

Current Production Chains: Seven, Not the Entire SDK Universe

The current generated production support page lists seven active chains: Ethereum, Arbitrum, Base, Optimism, Polygon, BNB Smart Chain and Avalanche.

The production SDK v2 matrix currently includes specific deployments of Uniswap V3/V4, Curve, SushiSwap V3, PancakeSwap V3, Aerodrome, Aave V3, Compound V3, Morpho Blue, Spark and GMX V2.

Why Edge Says It Scans 12+ Chains

The live app currently says its detection agents scan 12+ chains. That is not the same thing as deployable production execution. Research coverage can be broader than the seven-chain production support matrix.

This distinction is important for both readers and AI systems extracting Almanak's capabilities.

What Strategies Can You Build Today?

Leveraged lending and loops

Strategies can combine supply and borrowing operations across supported deployments of Aave, Morpho, Compound and Spark.

Concentrated liquidity

Users can automate LP range management and compounding across supported DEX connectors.

Delta-neutral and basis

Almanak explicitly highlights combinations of GMX perpetuals with spot and lending positions.

Multi-protocol strategies

The most interesting use case is composition: borrow → swap → LP → hedge → rebalance can become one automated strategy rather than several manual workflows.

Polymarket Is a Special Case

Current wallet documentation includes a dedicated Polygon Polymarket-wallet mode with the required CTF permissions preconfigured. However, the SDK documentation also describes prediction-market support as experimental and subject to testing. We therefore treat Polymarket as a specialized integration rather than universal production support.

How Almanak Pricing Works

Almanak currently offers Basic, Pro, Max and Enterprise access tiers. Basic provides free core access with limited Almanak Code usage and limited deployments. Pro increases credits and deployments. Max currently allows up to 25 active deployments and unlimited high-conviction signal access under the public plan documentation. Enterprise uses custom limits and SLA terms.

LLM-powered features consume plan credits or allowances, so Almanak is not priced like a simple DEX with one maker/taker fee.

Autonomous Execution Has a Separate Service Cost

Active Deployment EOAs require Almanak's Autonomous Execution Service. Current wallet docs say the service covers operational costs including variable network gas and can be sold as transaction bundles or time-based packages. Prices are displayed at purchase and the fees are non-refundable. Taxes such as VAT may be added.

That is why we do not publish a made-up universal “Almanak execution fee.” The live package is the source of truth.

Referral / Invite Program

Decentralised News invite: https://app.almanak.co/invite?code=m7cTQJW5

Invite code: m7cTQJW5

Almanak's current plan documentation says eligible inviter and invitee accounts can each receive one month of Pro after the invitee completes the first paid billing period. Pro users can currently invite up to six new users; Basic users can also bank a reward for later use under the published rules. Check the live plan page because referral terms can change.

$ALMANAK and veALMANAK

Almanak's current platform docs identify $ALMANAK on Ethereum and describe a vote-escrow-style staking model called veALMANAK. Users lock ALMANAK for a chosen duration to receive staking power. Current docs say veALMANAK can receive a proportional share of protocol fees and unlock platform access at qualifying thresholds.

A token-based “free plan” is not economically free if it requires locking a volatile asset. Compare subscription value with token-price risk and lock duration.

Security Audits

Almanak's FAQ says its smart contracts have been audited by Zokyo. Zokyo's public report library lists Almanak Report 1 — May 6, 2025 and Almanak Report 2 — September 26, 2025. Almanak's March 2026 MiCA whitepaper says both audits received Zokyo's maximum score.

Zokyo's public index for Report 2 shows 10 findings: no critical, high or medium items, with five low and five informational findings.

That is meaningful evidence, but audit scope matters. These reports do not guarantee the safety of user-generated strategies, LLM decisions, every protocol connector or future platform releases.

Roadmap: What Is Not Live Yet?

SDK v2 vs SDK v3

Almanak currently documents SDK v2 as production and SDK v3 as a staging preview for invited users. The strategy format and permission/deployment mechanics differ, so developers should pin versions deliberately rather than assume a broad dependency range will remain behaviorally identical.

Almanak vs a Conventional Trading Bot

Almanak vs Definitive, Based and HeyElsa

Definitive is primarily an execution engine whose Flash API can serve bots and agents. Based combines trading, spending and AI around Hyperliquid. HeyElsa is closer to a conversational DeFi copilot. Almanak is closest to an agentic strategy engineering and deployment environment.

Definitive asks: “How should this order execute?” Based asks: “How can one account trade, research and spend?” Almanak asks: “How do we turn a financial idea into safe, testable, autonomous software?”

Best Almanak Alternatives

Who Is Almanak Best For?

What Almanak Gets Right

1. AI output becomes code. This makes the strategy easier to inspect and reproduce.

2. Permissions are designed around least privilege. Zodiac is a much better primitive for autonomous finance than a general wallet key.

3. Simulation is part of the workflow, not an afterthought.

4. Deterministic execution remains a first-class option.

5. Strategy code can live in the user's own GitHub repository.

What Almanak Still Needs to Improve

Production breadth. The current seven-chain EVM footprint is useful, but the vision becomes stronger when Solana and Hyperliquid move into the generated production matrix.

Pricing transparency. Public documentation explains plans and execution packages, but not one simple stable price table for autonomous execution.

Canonical security scope. A central page mapping each audit to exact current contracts/components would improve verification.

Portfolio-level risk controls. Multiple agents can share a Safe, so aggregate limits matter as much as per-agent permissions.

Agentic safety UX. Maximum allocation, maximum loss and emergency shutdown should be impossible to miss as multi-agent automation expands.

What Would Change Our View?

Final Verdict

Almanak is one of the few products where the phrase “AI hedge fund” does not immediately reduce to a chatbot plus a wallet.

Signals can become requirements. Requirements become code. Code can be tested. Tested code can be versioned. Versioned strategies can receive narrowly scoped permissions. Those deployments can then be monitored and revoked.

That sequence is the product.

The biggest risk remains the strategy itself. Safe custody does not make a bad strategy profitable. Zodiac permissions do not make AI-generated code correct. A perfect backtest does not guarantee future liquidity or market behavior.

But Almanak is building the right infrastructure for those risks to be inspected and constrained rather than hidden.

How We Review at Decentralised News

Primary Sources and Evidence Ledger

1. Almanak official website — product thesis, workflow, custody and current production summary.
2. Almanak live platform — Edge interface, current discovery messaging and platform disclaimer.
3. Almanak documentation hub.
4. Edge documentation — signals, 46 detection agents, scoring and signal-to-strategy workflow.
5. Current production chains and protocols.
6. Deploy documentation — Safe, Zodiac, monitoring and GitHub deployment.
7. Wallet documentation — Deployment EOA, Safe, signer security and execution service.
8. Almanak SDK — deterministic/agentic strategies, Anvil testing and gateway architecture.
9. SDK Generations — v2 production / v3 staging distinction.
10. Plans and referrals.
11. veALMANAK staking.
12. Roadmap.
13. Zokyo Security Report Library.
14. Almanak MiCA Whitepaper v2.
15. Almanak 2026 Terms.