ATLASPROJECT

DATA COVERAGE

Know what the data can prove.

Atlas does not turn a planned integration into a green check. Every connector below separates tested contracts, product-only previews and work that has not been implemented.

Matrix connector-capabilities-v2
Published 2026-09-08
Current release boundary

Ten-chain address drafts and authenticated native-balance observations are implemented. Manual checks cover all ten target mainnets plus Sepolia through public sources, not tokens or history. Ownership proof, production provider agreements, automatic synchronization and payment execution remain unavailable.

01

FIRST PRODUCTION NETWORK TARGET

Ten chains. One honest starting point.

01

Bitcoin

BITCOIN

Check confirmed native BTC at a checksum-valid address. Pending activity is separate; provider chain-tip metadata is not a finality, wallet-ownership or spendability guarantee.

Contract testedManual native-balance check
02

Ethereum

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
03

Base

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
04

Arbitrum

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
05

Optimism

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
06

Polygon

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
07

BNB Chain

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
08

Avalanche

EVM

Save a public-wallet or Safe address, then sign in as Owner/Admin to check its native currency. Tokens, history, ownership proof and automatic sync are not included.

Contract testedManual native-balance check
09

Solana

SOLANA

Save a case-sensitive 32-byte public address, then check its native SOL balance at a provider-finalized context slot. Tokens, staking accounts, history and ownership proof are not included.

Contract testedManual native-balance check
10

Tron

TRON

Check native TRX from solidified account state after checksum validation. Missing accounts are not zero balances. Tokens, staked TRX and ownership are not included.

Contract testedManual native-balance check

Safe production drafts apply only to the seven EVM networks. Bitcoin, Solana and Tron are read-only public-address targets and are not presented as Safe execution rails.

02 / ISOLATED TEST RAIL

One Sepolia Safe. Zero production authority.

Development only · never send real funds
Safe address
0xC74038…ea0A38
Network
Ethereum Sepolia
Chain ID
11155111
Read-only verification
Checking public chain evidence

Atlas could not complete the public read-only check, so no ownership, balance or payment-readiness claim is made. The address stays outside reporting and every execution path.

CONTROL MODEL

Business approval is not a wallet signature.

Two independent control layers remain visible from preparation to chain evidence.
  1. 01
    Prepare

    Owner or Admin freezes the exact intent. The preparer cannot approve the same run.

  2. 02
    Approve

    Two distinct, strongly authenticated Atlas approvers satisfy business policy. They do not sign for the Safe.

  3. 03
    Sign

    Verified Safe owners sign externally under the Safe threshold. Atlas never receives their private keys.

  4. 04
    Submit + reconcile

    Disabled until simulation, nonce, finality, reorg and no-resend evidence pass in a live sandbox.

03

CONNECTOR MATRIX

Evidence before availability claims.

01

Public chain address

Direct public address only; no name resolution, wallet session or ownership signature

Ten-chain drafts and manual native-balance checks
Address validationContract tested

Network-aware EVM, Bitcoin, Solana and Tron validation rejects malformed or checksum-invalid inputs.

Draft persistenceContract tested

Owner/Admin writes are immutable, idempotent and remain DRAFT / UNVERIFIED / NOT_STARTED.

Native balance observationPreview only

Signed-in Owner/Admin can read EVM/Solana finalized contexts, Tron solidified accounts or confirmed Bitcoin address totals with pending activity excluded. Evidence is append-only; unavailable is not zero. Addresses remain excluded from net worth. Public sources have no production SLA.

Tokens and historyNot implemented

No token discovery, staking inventory, transaction ingestion, automatic sync job or reporting weight is created.

Ownership verificationNot implemented

No address is promoted to owned without a separately approved signature challenge.

Production evidence still required
  • Production RPC/indexer contracts
  • Per-chain finality and token registries
  • Signed ownership verification
  • Historical replay and statement reconciliation
02

Safe

Public EVM Safe address; no Safe credential, owner session or proposal authority

Seven production-network drafts plus one read-only verified Sepolia development rail; execution remains dormant
Address draftContract tested

Safe drafts are limited to seven production EVM networks plus an isolated Ethereum Sepolia test rail; every draft remains unverified/non-synced.

Transaction normalizationContract tested

A locked Safe golden fixture maps source evidence to balanced canonical output.

Development contract statusPreview only

Atlas cross-checks Sepolia contract code through JSON-RPC and reads owners, threshold, modules and guard state from the Safe Transaction Service without a signing credential.

Proposal and signaturesNot implemented

No route can propose, approve, sign or submit a Safe transaction.

Production evidence still required
  • Production Safe API/RPC contracts and authenticated quota
  • Approved production owner/threshold/module policy
  • Wallet connection and signature handoff
  • Live replacement, finality and reorg evidence
03

Binance

Read-only provider authorization is the target; no customer credential or provider application is configured

Named production target with no live adapter
Credential intakeNot implemented

The browser and API expose no provider token, API-key or secret submission path.

BalancesNot implemented

No provider response is fetched or represented as a customer balance.

Transaction historyNot implemented

No provider pagination, history range or rate-limit replay has passed.

Permission detectionNot implemented

Atlas does not claim a key is read-only until the provider verifies its effective permissions.

Production evidence still required
  • Provider contract and approved application
  • Encrypted credential storage and rotation
  • Read-only permission proof and revocation
  • Provider-approved history and statement reconciliation
04

OKX

Read-only provider authorization is the target; no customer credential or provider application is configured

Operator-only demo capture worker implemented and database-tested; live account validation pending
Demo REST request signingContract tested

A fixed HMAC vector covers OKX V5 GET signing and the required x-simulated-trading header.

Read-only permission gateContract tested

The offline contract fails closed unless account configuration reports read_only without trade or withdraw.

Credential intakeNot implemented

The product exposes no browser or API secret field; the operator check accepts three explicit secret-file paths only.

Balances and history captureContract tested

Twenty demo-only streams cover trading/funding balances, positions, bills, six instrument families and deposits/withdrawals. Controlled PostgreSQL tests verify per-page persistence, resume, tenant-scoped revision deduplication, audit rollback and rate-limit backoff. No customer account has passed live synchronization.

Source normalization and continuityContract tested

An exact-decimal derived report reads immutable capture pages, separates balances, bills, fills and transfers, detects conflicting revisions and balance/fee discrepancies, and preserves unknown valuations. It posts no ledger entries and proves neither opening balances nor full-account reconciliation.

Operator incremental cycleContract tested

An opt-in continuous worker resumes persisted jobs, uses a seven-day overlap anchored to the previous capture, revisits older unresolved transfers, preserves retention gaps and honors backoff/cancellation. Controlled database tests pass; no server worker or live customer cycle is enabled.

Complete history and reconciliationNot implemented

Capture does not post to the ledger. Quarterly archives, account subproducts, opening balances, pending-status refresh, valuation and reconciliation remain incomplete. The worker cannot report full synchronization success.

Production evidence still required
  • Rotated read-only demo key and Passphrase
  • Live provider, continuous-worker and history-window validation
  • Customer credential lifecycle and authenticated sync controls
  • Quarterly archive, subaccounts, Earn and bot coverage
  • Closed-record corrections outside overlap, canonical ledger posting and full reconciliation
05

Bybit

Read-only provider authorization is the target; no customer credential or provider application is configured

Named production target with no live adapter
Credential intakeNot implemented

The browser and API expose no provider token, API-key or secret submission path.

BalancesNot implemented

No provider response is fetched or represented as a customer balance.

Transaction historyNot implemented

No provider pagination, history range or rate-limit replay has passed.

Permission detectionNot implemented

Atlas does not claim a key is read-only until the provider verifies its effective permissions.

Production evidence still required
  • Provider contract and approved application
  • Encrypted credential storage and rotation
  • Read-only permission proof and revocation
  • Provider-approved history and statement reconciliation
06

Bitget

Read-only provider authorization is the target; no customer credential or provider application is configured

Named production target with no live adapter
Credential intakeNot implemented

The browser and API expose no provider token, API-key or secret submission path.

BalancesNot implemented

No provider response is fetched or represented as a customer balance.

Transaction historyNot implemented

No provider pagination, history range or rate-limit replay has passed.

Permission detectionNot implemented

Atlas does not claim a key is read-only until the provider verifies its effective permissions.

Production evidence still required
  • Provider contract and approved application
  • Encrypted credential storage and rotation
  • Read-only permission proof and revocation
  • Provider-approved history and statement reconciliation
07

Coinbase

Read-only provider authorization is the target; no customer credential or provider application is configured

Locked withdrawal-normalization fixture; no live adapter
Withdrawal normalizationContract tested

The locked Coinbase fixture isolates received amount and withdrawal fee without income double-counting.

Credential intakeNot implemented

No OAuth application, token or customer credential is configured.

Balances and historyNot implemented

Synthetic records are not represented as provider responses.

Permission detectionNot implemented

No token is described as verified read-only.

Production evidence still required
  • Provider contract and approved application
  • Encrypted credential storage and rotation
  • Read-only permission proof and revocation
  • Provider-approved history and statement reconciliation
08

Kraken

Read-only provider authorization is the target; no customer credential or provider application is configured

Named production target with no live adapter
Credential intakeNot implemented

The browser and API expose no provider token, API-key or secret submission path.

BalancesNot implemented

No provider response is fetched or represented as a customer balance.

Transaction historyNot implemented

No provider pagination, history range or rate-limit replay has passed.

Permission detectionNot implemented

Atlas does not claim a key is read-only until the provider verifies its effective permissions.

Production evidence still required
  • Provider contract and approved application
  • Encrypted credential storage and rotation
  • Read-only permission proof and revocation
  • Provider-approved history and statement reconciliation
09

Official CSV export

User-supplied provider export; uploads remain disabled

Parser contract without an upload surface
Transaction normalizationContract tested

A locked CSV income fixture produces exact-decimal canonical and ledger output.

Coverage metadataContract tested

The contract requires source, time zone, range and parser-version semantics.

Secure upload and storageNot implemented

User-controlled files are disabled until a reviewed upload pipeline exists.

Balance reconciliationNot implemented

No provider statement or end-balance file has been approved.

Production evidence still required
  • Malware/content scanning
  • Encrypted object storage
  • Provider-specific schema registry
  • Large-file and malformed-file security tests
10

Manual asset or liability

Explicit user-entered value and valuation date

Synthetic model only
Assets and liabilitiesPreview only

Exact-money and net-assets rules include liabilities in fixtures and tests.

Valuation provenanceNot implemented

The preview has no persisted manual valuation write route.

Review historyNot implemented

No close-period adjustment workflow is exposed.

Automatic refreshNot applicable

Manual values change only through an explicit audited user action.

Production evidence still required
  • Persisted audited write flow
  • Valuation source/date review
  • Close-period adjustment policy
  • Deletion and retention approval
04 / MACHINE-READABLE CONTRACT

The same boundary is available as versioned JSON.

Open capability API