Product Documentation

Understand every step
before you sign.

Learn how wallet connection, cross-chain execution, costs, safety checks and transaction states are intended to work in Biti.

Search is local to this page. No query is sent to a remote service.

Documentation

01

Getting Started

What Biti is

Biti is a pre-launch self-custody product concept focused on making cross-chain movement easier to understand before a user approves a transaction.

One journey, one understandable path

  1. 01User intent
  2. 02Biti
  3. 03Cross-chain execution
  4. 04Destination action

Supported environments

Pending

Approved app, browser extension, operating system and browser support details will be published once production distribution is confirmed.

Before you connect

  • Confirm that you are using an official Biti surface.
  • Review the wallet account and network shown in the connection request.
  • Never share a seed phrase or private key with a website or support contact.
02

How to Connect a Wallet

Connection flow

  1. 01Open Biti
  2. 02Choose wallet
  3. 03Review connection
  4. 04Confirm
  5. 05Connected
Connection requestReview account, network and permissionsConnecting should not move assets.
  1. Open Biti.

    Use the approved app or Chrome extension entry point once production distribution URLs are available.

  2. Choose a supported wallet.

    The final supported-wallet list is pending technical confirmation.

  3. Review the connection request.

    Check the requesting product, account and permissions shown by your wallet.

  4. Confirm the connection.

    Approve only when the request matches the action you initiated.

  5. Check the connected state.

    Verify that Biti shows the intended account and current network.

Connection is not a transaction

Connecting a wallet should not by itself move assets. Review every later approval and signature separately.

03

How a Swap Works

Cross-chain execution journey

  1. 01Choose source
  2. 02Choose destination
  3. 03Enter amount
  4. 04Review route
  5. 05Approve / Sign
  6. 06Track execution
  7. 07Destination action
  1. Choose the source wallet and network.
  2. Choose the destination asset and network.
  3. Enter the amount.
  4. Review the execution summary.

    Check the proposed route, total expected cost, ETA and minimum received before signing.

  5. Approve and sign.

    Read the wallet prompt and confirm that it matches the Biti summary.

  6. Track execution.

    Keep the transaction timeline available while source and destination steps settle.

  7. Confirm completion.

    Verify the destination balance before continuing to an optional destination action.

Routes can change

A quote is time-sensitive. Recheck minimum received and total expected cost whenever the quote refreshes.

04

Fees Explained

Conceptual cost breakdown — no live values

Amount sentExample amount
  • KnownEntered amount
  • EstimatedNetwork fee
  • If applicableProtocol / service fee
  • VariablePrice impact / slippage
Expected amount receivedShown before signing
Network fee

Cost paid to the network for processing relevant transactions.

Protocol or service fee

If applicableMust be disclosed only after the fee model is approved.

Price impact and slippage

The difference between the displayed market expectation and the minimum acceptable execution outcome.

Total expected cost

The combined estimate that should be reviewed before signing.

Why the final amount may change

Network conditions, liquidity and quote freshness can change during review. Biti should surface refreshed values before a new signature is requested.

Pending

Exact fee names, formulas and fee-recipient language are awaiting approval and are not final.

05

Supported Chains

This section is ready to present source networks, destination networks, supported assets, route availability and temporarily unavailable routes.

Network scope — production availability pending confirmation

  1. Source ecosystemEVM NetworksTo confirm
  2. Execution layerBiti
  3. Destination ecosystemSolanaTo confirm
Source networks

PendingThe approved production list has not been published yet.

Destination networks

PendingThe approved production list has not been published yet.

Supported assets

PendingThe approved asset and token-contract list has not been published yet.

Route availability

Availability should reflect current product state rather than a static marketing promise.

Temporarily unavailable routes

The interface should clearly distinguish unsupported routes from routes that are temporarily unavailable.

06

Safety Before Signing

Pre-sign review

Confirm transaction intent
Review
  1. 1
    TokenMatch your intent
  2. 2
    NetworkMatch your intent
  3. 3
    RouteMatch your intent
  4. 4
    PermissionsReview before confirming
  5. 5
    Estimated costReview before confirming
  6. 6
    Expected outcomeReview before confirming

Compare this summary with the final wallet prompt.

  • Verify the token, spender, destination account and network.
  • Review wallet permissions and limit allowances when supported.
  • Treat transaction simulation as a forecast, not a guarantee.
  • Stop when the wallet or Biti displays an unknown-risk or warning state.
  • Do not approve a prompt that differs from the summary you reviewed.
Keep the summary visible

Compare the Biti pre-sign summary with the final wallet prompt before confirming.

07

Frequently Asked Questions

Is Biti custodial?

No. Biti is designed as a self-custody product: your private keys and recovery phrase are generated and stored on your device, and every signature is computed locally.

Where are private keys stored?

On your device only. The recovery phrase is encrypted before it touches disk using AES-256-GCM, with the encryption key derived from your password using PBKDF2 with 310,000 iterations.

How long does a cross-chain swap take?

It depends on the route, the source network and destination settlement. Biti should show an estimated completion time with each quote and keep the transaction timeline visible until both sides settle.

What happens if a route is delayed or fails?

The transaction timeline should keep reporting state rather than going silent. Failed steps should offer a clear next action — retry, or a safe unwind — instead of leaving funds in an unknown state.

Can a transaction be canceled?

Once a transaction is signed and broadcast it cannot be recalled. That is why the pre-sign summary exists: review the token, route, permissions and expected outcome before you approve.

Why did the quote change?

Quotes are time-sensitive. Network conditions, liquidity and route availability move between the moment a quote is fetched and the moment you sign, so Biti should refresh the values and ask again.

Which wallets and chains are supported?

The final supported-wallet and production network lists are pending confirmation. The planned direction is EVM networks as the source ecosystem and Solana as the primary destination.

How do I contact support?

Biti is pre-launch and the approved support channel has not been published yet. Join the waitlist and support details will be shared alongside the app and extension release.

08

Support and Next Action

Biti is currently in a pre-launch state.

App & Chrome extension coming soon
Pending

The approved support channel, app download URL and Chrome extension URL have not been published yet.

Product Vision

01

Product Vision

Biti is a self-custody wallet built for people who move value across chains. The vision rests on four pillars:

  • Hold assets safely across multiple networks.
  • Move value anywhere with reviewed, transparent routes.
  • Enable staking workflows at the destination chain.
  • Make cost, route, and risk visible before every signature.

Ease of use should never come at the cost of self-custody or onchain transparency. Biti pairs both.

02

Mission

Enable anyone to use multichain crypto without becoming a protocol expert.

03

Target Users

  • Primary: retail users who hold assets on major EVM chains and want simpler cross-chain movement.
  • Secondary: power users who value execution quality, route control, and transparent fees.
  • Tertiary: global users in underbanked regions who rely on crypto rails for everyday value transfer.
04

Core Problems

  • Fragmented UX across chains, bridges, and DEXs.
  • Hidden fees and unclear slippage or MEV risk.
  • Confusing approvals and signing flows.
  • Poor handling of cross-chain failures and stuck transactions.
  • Security fatigue: it is hard to tell safe actions from unsafe ones.
05

Product Principles

  • Safety first: simulation, risk signals, and explicit approval by default.
  • Clarity over cleverness: plain-language summaries for every action.
  • Best execution: routes ranked by real net outcome, not marketing.
  • Progressive disclosure: simple by default, powerful when needed.
  • Open ecosystem: integrate the best providers rather than lock users in.
  • Reliability as a feature: predictable behavior across the full lifecycle.
06

Value Proposition

  • One wallet for multiple chains.
  • One swap interface for same-chain and cross-chain trades.
  • A bridge-to-staking pathway that completes the user journey.
  • Human-readable signing with risk flags before approval.
  • A unified portfolio view across networks.
6.1

Why Staking Matters

For many users, swapping is not the end goal. They move capital across chains because they want to hold, deploy, or earn on the destination network. On Solana especially, staking is one of the clearest post-swap actions.

  • Users should not need to piece together a separate staking workflow after landing on the destination chain.
  • Biti can turn cross-chain movement into a complete intent flow: swap, settle, then stake.
  • That creates a stronger product story than generic routing alone, because it connects asset movement with asset utility.
07

Product Scope (V1)

In scope

  • Non-custodial wallet with local key management
  • Multi-chain account management (EVM-first)
  • Token transfers and same-chain swaps
  • Cross-chain swaps via external aggregators
  • Staking handoffs at the destination chain
  • Real-time quotes with full fee breakdowns
  • Transaction simulation with warnings
  • Transaction lifecycle tracking
  • Address book and portfolio dashboard

Out of scope

  • Perpetuals and options trading
  • Comprehensive tax tooling
  • Global fiat onramps
  • A fully custom smart routing engine
08

UX North Star

One intent, one confirmation.

Before any signature, the user sees a single readable summary:

  • Amount paid and minimum received
  • Full fee breakdown
  • Estimated completion time
  • Route providers involved
  • Risk indicators, if any

After signing: a legible timeline, recovery across app restarts, and one-tap retry when a step fails.

09

Trust & Security Vision

  • Local key management—keys never leave the device.
  • Mandatory transaction simulation before signing.
  • Contract and spender risk scoring.
  • Allowance management with revoke recommendations.
  • Anti-phishing signals on addresses and domains.
  • Emergency incident protocols with clear user communication.
10

Chain Strategy

Phase 1

  • Ethereum
  • Base
  • Arbitrum
  • Optimism
  • BNB Chain
  • Polygon

Phase 2

  • Solana as the first non-EVM destination
  • Additional ecosystems based on liquidity and demand
11

Liquidity & Routing Strategy

  • External aggregators behind a clean abstraction layer.
  • Routes ranked by net output, reliability, and completion time.
  • Continuous provider health tracking.
  • Provider-agnostic routing—no single point of dependence.
12

Differentiation

  • Radical execution transparency: no hidden spreads.
  • Cross-chain state observability throughout the swap lifecycle.
  • A complete destination experience connecting movement to staking.
  • Human-readable signing and risk-first design.
  • Reliability treated as a product feature, not an afterthought.
13

Business Model Hypothesis

  • Primary: a transparent take-rate on swap fees.
  • Secondary: a premium tier for analytics, alerts, automation, and API access.
  • Optional: partner revenue share with routing providers.
14

Success Metrics

User

  • Monthly active wallets
  • 30-day retention
  • Time to first swap

Execution

  • Quote-to-completion rate
  • Median completion time
  • Effective price vs. benchmarks
  • Failure rate by chain and provider

Trust

  • Security incident rate
  • Simulation coverage
  • Allowance risk reduction
15

Product Roadmap

Stage 1 · Launch (3 months)

  • Month 1: wallet core, chain abstraction, signing, EVM baseline
  • Month 2: multi-provider quotes, cross-chain flows, fee transparency
  • Month 3: transaction timeline UX, security warnings, allowance manager, launch hardening

Stage 2 · Expansion

  • Additional chains, with Solana as the priority
  • Provider reliability scoring
  • Advanced controls: slippage, gas presets, route preferences
  • Power features: alerts, automation, team wallets, portfolio intelligence
16

Technical Vision

  • Mobile-first product with a web companion.
  • Deterministic account abstraction over chain-specific signing.
  • A unified intent-to-execution pipeline.
  • Event-sourced transaction tracker for multi-step lifecycles.
  • Simulation plus heuristic risk scoring on every action.
  • Structured observability and SLA dashboards.
17

Key Risks & Mitigations

  • Bridge or provider failures → multi-provider fallback and health-based routing.
  • Security exploits → contract allowlisting and rapid revoke UX.
  • Regulatory shifts → modular regional feature flags.
  • Complexity creep → strict scope control and progressive disclosure.
18

Vision Statement

Biti becomes the default rail for value movement across crypto networks: secure by design, transparent by default, and simple enough for mainstream users without compromising power for experts.

Back to top ↑