Create your account, save project drafts and explore the controls. Trading release coming soon.
The Arc candidate brings project settings, restricted vault permissions, automatic strategy controls and transaction monitoring into one platform. The v1.9.4 integration combines reviewed BTDP checkout controls, automatic price and inventory checks, and a paused local package. One private project passed real checkout acceptance on 8 October 2026; public checkout and trading remain coming soon.
The full app is paused. Public trading acceptance remains pending.
The private backend remains on Drive D. This public website provides progress, documentation and the isolated prerelease portal.
On 8 October 2026, a private project’s BTDP payment matched its reviewed quote and two-day subscription coverage was verified. Emergency Stop remained ON and earlier payment and subscription records were preserved. Public checkout remains coming soon.
Smart Market checks prices and inventory on its own timer. Outside trades can strengthen a signal. BUY and SELL quantities are calculated independently; a flat or costly market can produce HOLD.
The integrated package keeps signing, trading and new checkout off while the existing project records remain in their original database. Wallet permissions and later financial tests require current reviewed limits.
These features are implemented in the candidate. Their availability does not remove the requirement for current permissions, limits and release acceptance.
A project owner connects one Main Wallet and manages up to 20 project-bound smart vaults. Owner permissions set the trading budgets, price bounds, cooldown and expiry.
Authenticated project settings, token and pool inspection, and protocol-specific validation support the Arc workflow. The completed all-vault rehearsal used an Arc Uniswap V4 market.
The v1.8.2 test package includes subscription checks. BTDP is the service subscription token for the updated model; BTDP subscriptions are priced at $5, $20 or $69 worth of BTDP. A fresh token quote and verified checkout are required before payment; public checkout and trading activation remain pending. A payment alone does not bypass execution checks.
Action and daily limits, gas budgets, trade frequency, price bounds and permissions constrain eligible transactions. Emergency Stop pauses new automatic operations.
The monitor shows current status, completed and pending transactions, individual vault progress and confirmed receipts. Historical errors remain separate from the current status.
Receipt reconciliation and persisted counters let the test coordinator resume after a restart without repeating confirmed work. Existing holdings and earlier trade records are preserved.
Strategies evaluate the market within owner permissions and project limits. A signal can be held when price, inventory, cost or safety conditions are not satisfied.
Price Band uses configured price conditions. Auto Rebalance compares token and quote inventory against a target allocation and its permitted band.
The multi-vault worker can evaluate outside pool activity. Smart Market combines price signals, inventory and costs; the current design targets 50% token inventory within a flexible 20–80% range.
Verification recorded on 7 October 2026 for the v1.8.2 candidate.
The historical fork sent no public transactions. Earlier bounded public BUY/SELL tests are separate evidence; the public all-20 test has not been completed.
Token and pool inspection is implemented for the networks below. Inspection does not enable live trading or establish token safety.
Read-only inspection is available in the candidate. Live venue integration, wallet permissions, execution testing and production acceptance remain roadmap work.
Read-only inspection is available in the candidate. Live adapters, network-specific costs, owner controls and execution acceptance must be verified before release.
Read-only inspection is available in the candidate. Live routing, chain-specific controls and end-to-end acceptance remain pending.
Read-only inspection support is implemented. Live operation remains dependent on supported deployments, integration verification and a separate release decision.
