How it works

You pay, you plug in your wallet, you sign your limits, you press play. Here is every step, with what gets executed, what gets refused, and what comes back to you.

  1. You connect your wallet

    Two paths. The one that works today for everyone: you connect the wallet you already have, the way you would on a decentralised application (MetaMask, Ledger, Rabby, or any WalletConnect-compatible mobile wallet, by QR code). And the one we keep deliberately closed for now: a guided creation from your e-mail, keys on your side, which will only open once four non-custody guarantees have been verified in writing; the product screen names them rather than showing a button that would not keep its promise. In both cases the service only sees the public address.

    The address fields actively reject 12-to-24-word sequences and 64-character hexadecimal keys: entering one triggers a security alert and is never stored.

  2. You sign the policy envelope

    It is the agent’s employment contract, and you set every line of it: cap per operation, cap per day, cumulative budget, allowed chains, allowed contracts, expiry date. In FULL AUTO you also accept a risk waiver, statement by statement, never a single box. In SEMI-AUTO the envelope exists too, but every transaction waits for your signature. Going back to SEMI-AUTO is free and immediate; widening the envelope requires a fresh signature from your hand.

  3. The fleet searches and qualifies, continuously

    Discovery covers every family: airdrops, incentivised testnets, on-chain quests, points programmes, learn-and-earn, games, bounties, liquidity incentives, staking and restaking, lending, yield farming, arbitrage, paid missions and surveys. Every lead is tied to a dated primary source, broken into verifiable conditions, and given a verdict from a closed list: execute, present, abstain, refuse. A blocking check always wins.

    A discarded opportunity is not a loss: nothing proved it sound. The exact reason is always journalled, with its sources.

  4. Execution, then collection, checked twice

    Before committing anything, the fleet replays the checks at the moment of signing: is the contract still the one analysed, is the requested approval the one planned, does the simulation produce the expected outcome, does the envelope cover the operation. In FULL AUTO it then executes and collects to your wallet; in SEMI-AUTO it hands you the transaction and waits. Afterwards it compares what happened on chain with what was planned: a gap becomes a visible incident, never a silent display adjustment.

The signed envelope

Why your keys never move

The question to ask any product that automates crypto: who holds the keys, and what bounds what the automaton can commit? Here are our two answers, both verifiable.

Your wallet: keys cannot be delegated

Created or connected by you, in your browser or your application. We generate no key, store none and can reconstruct none: our systems only see public addresses and operations that were already authorised. Your funds leave when you decide, to where you decide.

The agent’s authority: a document, not a power

What the fleet may commit fits in the envelope you signed: caps per operation and per day, a cumulative budget, named chains and contracts, expiry. It is checked at proposal and checked again at signing, it can only be widened by you, and it dies at its expiry date or at your first click of revocation.

What this changes in practice

  • An abused approval or a boobytrapped contract cannot reach more than your caps cover: the worst case reads off the envelope, not off an incident report.
  • Two simultaneous operations cannot spend the same cap twice: the reservation is atomic, and an overrun is refused before it exists.
  • The full stop withdraws the delegated authority in one move and returns the account to SEMI-AUTO; resuming, on the other hand, requires strong confirmation.
  • What the fleet collects lands on your address, at the operation itself: there is no intermediate account, no balance held with us, nothing to claim back.
  • Every refusal is journalled with its reason: you can audit what the agent did not do, not only what it did.

None of the keys are ours, and no screen will ever ask you for one. So we cannot move your funds, nor recover them for you if you lost your access. The same technical property, read in both directions: it is what makes the rest credible.

What programmes reward

What actually counts, and what is folklore

Past distributions have been studied, family by family. The fleet plays what the documented criteria measure, not the recipes that circulate.

  • What keeps appearing in observed criteria

    Seniority, counted in distinct months of activity rather than cumulative days; the number of distinct interactions and contracts; volume; capital bridged; the time-weighted average balance; and retention, meaning having stayed after the event. That is exactly what the fleet builds, week after week, on every family where those criteria apply.

  • What is folklore

    The gas price at transaction time, the hour of the day, the roundness of amounts: no analysis of past distributions gives them any weight. The fleet never executes on the strength of a recipe, and will never ask you to act at a precise hour.

  • Where regularity comes from, when it exists

    A one-off distribution is not a regular income. What settles on short cycles comes from paid tasks, quests and learn-and-earn; what accrues comes from staking and continuous incentives, which carry their own risks (lock-ups, operator penalties, variable rewards). The fleet keeps these horizons apart instead of blending them.

  • On one major documented distribution, 41 % of early recipients had sold everything within 24 hours. A distribution is an event, not an annuity, and the fleet treats it as one.
  • No protocol commits to distributing, and many never do. That is the reason a fleet exists: to cover enough families that nothing rests on a single promise.
  • Retention and seniority in distinct months are also the reason for the quarterly prepayment: an agent that works for two weeks has built nothing measurable.

Billing unit

What exactly a "deep analysis" is

It is the unit that consumes your quota: the casework that precedes any execution. It is defined precisely so the quota means something.

  • A deep analysis is a case file on one pair (your wallet × one identified opportunity): identification of the on-chain object, security checks, eligibility conditions one by one, estimated costs, a verdict from a closed list, a verifiable receipt.
  • The execution that follows, in FULL AUTO as in SEMI-AUTO, consumes no extra quota: the casework counts, not the act.
  • Never counted: shared general discovery, re-reading a delivered file, the re-check at signing time, and any analysis interrupted by an early blocking check.
  • An analysis that fails because of an outage on our side is re-credited automatically, and counting happens when the file is delivered, never at submission.

See pricing

Evidence

What a receipt contains

A receipt exists to answer, months later, the question "why did the fleet do that?". It is built to be re-read by someone other than you: a partner, an accountant, an auditor.

  1. The sources used, with their origin address, their authority (official, auditor, community) and the exact time they were read.

  2. The checks executed, with their result: passed, failed, not applicable, or impossible to establish.

  3. The verdict and its reason, expressed as a stable code and not as free text.

  4. For every executed operation: the envelope in force at that instant, what the simulation announced, and the reference of the signature.

  5. Afterwards: what actually happened on chain, and any gap with what was planned.

Limits

What these checks do not prove

We would rather write it ourselves than let you find out.

  • The checks reduce a class of known risks. They do not prove a contract is safe, a project honest, or that an opportunity will produce anything.
  • On-chain data is exact at the block where it was read; that is why everything is re-checked at signing time, and why, in FULL AUTO, doubt means refusal.
  • A platform can change its terms, close a programme, exclude participants or block a withdrawal without notice. The fleet keeps a dated extract of the terms; it cannot enforce a third party’s rules.
  • When a step requires a human (identity verification, proof of humanity, judgement), the fleet prepares it and presents it to you. It does not circumvent it, and a vendor promising otherwise is putting you at risk.
  • Broad coverage does not mean exhaustive coverage: a lead without a usable primary source does not enter the feed, and there will always be windows the fleet has not seen.

Risk information

Read this before any decision. This information is part of the service itself.

  • Risk of total loss: crypto-assets are extremely volatile. You can lose the entire amount you commit.
  • Illiquidity: some positions cannot be sold or withdrawn when you want to, sometimes never.
  • No guarantee of result: the software searches, qualifies, verifies and tracks. No protocol commits to distributing anything, and past activity creates no entitlement. No gain, no yield and no future performance is promised.
  • No insured deposit: we neither receive nor hold your funds, and no amount is covered by any deposit protection scheme. Paying a software subscription is not a deposit.
  • Fees: network fees, platform fees, price spreads and conversion costs add up and reduce any result.
  • Taxation: reporting and paying taxes is your responsibility, according to your country of residence. We provide no tax advice.
  • Exact scope: the agents search, qualify, verify, prepare, track, and only act inside the mode you chose. In SEMI-AUTO (assisted) you sign every operation yourself; in FULL AUTO (delegated) the agent acts only inside the envelope you signed (caps, duration, immediate revocation), once that mode is open and activated. The service receives only public addresses and holds no key.
  • Non-custodial: you are the sole holder of your keys. The app never asks for your recovery phrase and has no field able to receive one.
  • Separation of roles: a separate agent wallet, whose key only you hold, carries the activity on a short budget, away from the wallet that receives. That separation bounds in advance what can be reached if an operation goes wrong.
  • No recovery by us: because we hold none of your keys, we cannot move your funds, and we cannot give them back to you either. Backing up your recovery phrase is yours alone.
  • We sell software. We do not manage your money and give no personalised investment advice. The agent never owns your assets: at most it holds an authority of use bounded by the envelope you sign, which you can revoke at any time.
  • Conflicts of interest: we may receive affiliate compensation on software subscriptions taken out or referred. It never applies to your capital and never influences a qualification or a security refusal.
  • The budget you declare is not a plan, not a deposit with us and not a promise of gain: it only calibrates your limits, your alerts and your risk scenarios. The funds stay on your own wallet.

Watch a full cycle

The public demonstration shows a mission feed, a casework dossier and the execution journal, on sample data clearly labelled as such.