How DCA.family works

DCA.family supports market, limit, TWAP, stop buy, stop-loss and take-profit, with an optional take-profit / stop-loss pair on a buy.

Orders run on 13 networks: Robinhood Chain, Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, HyperEVM, Plasma, Monad, Ink and Arc. Pick the network next to search; your wallet is switched to it before anything is signed.

A recurring buy is one scheduled order where each buy is one equal-time bucket (daily, weekly or every 30 days). You sign once; funds stay in your wallet until each buy executes. You can request cancellation of the remaining buys at any time.

An order signature authorizes an input debit: which token leaves your wallet, the total amount, the recipient and a deadline. It does not encode a minimum output. Price limits, slippage bounds and the execution schedule are enforced by the offchain executor.

One signature can back multiple onchain debits up to the signed total. The review screen states this in plain language before any signing request, and the app refuses to submit typed data whose domain chain id, verifying contract, recipient or deadline does not match the connected wallet and the plan under review.

DCA.family checks the allowance requested for your authorized spend. If an approval is unlimited, the app flags it before you sign so you can decide whether to continue.

Approval details are checked before they reach your wallet: the spender, token and amount must match the review. Cancelling or completing a plan does not revoke an allowance; use Revoke separately when your remaining orders no longer need it.

Cancelling requires signing an order-specific cancellation message for a specific order id. Until the executor confirms, the plan sits in a stopping state. Slices already in flight may still fill.

If a submission response is ambiguous — a network failure after the request was sent, or a response the app cannot interpret — DCA.family treats the order as possibly live, surfaces it as unknown, and asks you to check its live order status. It never silently retries a submission that may have succeeded.

Before any live order, DCA.family checks your wallet, the quote and your signature:

• A server-verified wallet session: you sign a one-time challenge, so a submission is bound to a proven wallet owner rather than a client-supplied address.
• Quote binding: the exact quote you reviewed is stored server-side and claimed once, so the submitted order is the order you saw.
• An idempotency key on every submission, so a retry can never place a second order, and reconciliation for ambiguous responses.
• Your wallet signature on the order itself — nothing is submitted unattended.

When a request cannot be served, the app shows the failure. Quotes and planned times are estimates; completed fills and transactions come from actual order records.

Quick-pick asset addresses are convenience entries, not a verified route list. Stock-token metadata must come from the official Robinhood Chain registry endpoint documented at docs.robinhood.com/chain/stock-token-apis; presence in a registry is not the same as a verified tradable route on the venue.

Tokenized stock tokens are exposure instruments, not shares. They carry no shareholder rights and are subject to a corporate-action multiplier. DCA.family is not affiliated with, endorsed by, or partnered with Robinhood.

Plans are single-chain: funding and target assets must live on the same chain, so no cross-chain scheduling is implied. The app verifies the connected wallet's chain id before preparing any request, and invalidates prepared state whenever the account or chain changes.

• Robinhood Chain — chain id 4663
• Base — chain id 8453
• Ethereum — chain id 1
• Arbitrum — chain id 42161
• Optimism — chain id 10
• Polygon — chain id 137
• Avalanche — chain id 43114
• BNB Chain — chain id 56
• HyperEVM — chain id 999
• Plasma — chain id 9745
• Monad — chain id 143
• Ink — chain id 57073
• Arc — chain id 5042