DigiByte Wallet is a fully self-custodial, open-source Progressive Web App (PWA) available at dgbwallet.app. Built as a Blazor WebAssembly application, it runs entirely in the browser. Your private keys never leave your device, there is no account signup, and no third-party server holds your funds.
You can create a new wallet with a 24-word BIP39 recovery phrase, recover an existing one, or import a WIF private key. A 6-digit PIN (with exponential lockout protection) secures access. The wallet supports native SegWit (dgb1…) and legacy addresses, real-time fiat conversion across multiple currencies, contacts, BIP21 payment requests, Digi-ID passwordless login, configurable fees, remittances with fee comparisons against traditional services, NFC tap-to-pay, multisig, biometrics, and more.
All cryptographic operations (key derivation, signing, encryption with AES-256-GCM) happen locally. Blockchain data uses a resilient fallback chain (public explorers plus the project’s own pruned node), while transaction broadcasting prioritizes reliability.
The Roadmap: From Solid Core to Full Ecosystem Features
The project’s public roadmap shows steady, phased progress:
Completed
- Phase 1 – Wallet Core: BIP39/BIP84 HD wallets, encrypted seed storage, send/receive with QR, multi-network support (mainnet/testnet/regtest), themes.
- Phase 2 – Features: Contacts, payment requests, Digi-ID, fiat toggles, multi-currency, remittances, NFC.
- Phase 4 – Infrastructure: Full Node API, Docker setups for regtest/testnet/mainnet, resilient backends, production deployment.
- Phase 5 – Multisig: Full M-of-N multisig wallets, co-signer management, P2SH-P2WSH and P2WSH addresses, PSBT signing workflow (create → sign → combine → finalize → broadcast). This is critical infrastructure for the marketplace.
- Extensive security hardening, UX polish, documentation, help center, and open-source practices.
In Progress / Near-term
- Multi-language support.
- Additional documentation and polish for broader alpha/beta readiness.
Planned – Phase 3: P2P Exchange (the standout upcoming feature)
- Order book with buy/sell offers.
- Complete trade flow (initiate → pay → release).
- Real-time trade chat via SignalR.
- Reputation system (ratings and badges).
- Backend with EF Core + PostgreSQL.
- Leverages the already-completed multisig system for escrow.
Other longer-term items include DigiAssets support, hardware wallet integration, deeper offline capabilities, and more export tools.
The roadmap page itself (https://dgbwallet.app/roadmap) is designed as a visual timeline with status indicators, reflecting transparent, community-oriented development.
Spotlight: The Built-in P2P Marketplace — How Users Will Trade
The P2P Marketplace (accessible at https://dgbwallet.app/p2p) is currently marked “Coming soon,” but the architecture and completed building blocks make the intended user experience clear.
It is designed as a native, non-custodial peer-to-peer trading experience for DigiByte (and potentially related assets) living directly inside the wallet. Users will not need external platforms or centralized intermediaries for matching or holding funds.
Expected user flow for trading:
1. Browse or create orders
Open the P2P section. Tabs will cover Buy DGB, Sell DGB, and My Orders. Sellers post offers (amount of DGB, price in preferred fiat or crypto, payment methods, limits). Buyers browse the order book and select matching offers.
2. Initiate a trade
A buyer accepts an offer (or a seller responds to a buy request). The system creates a trade session. Both parties are connected for real-time communication via SignalR-powered trade chat so they can coordinate payment details, confirmations, or resolve minor questions.
3. Secure escrow with multisig
Funds move into a 2-of-3 multisig escrow address (or similar M-of-N setup) constructed using the wallet’s already-complete multisig engine. Typical participants: buyer, seller, and an optional arbiter/reputation layer. Neither party can unilaterally take the funds. The escrow is non-custodial—keys remain under user control according to the multisig rules.
4. Off-chain or on-chain payment & confirmation
The buyer sends the agreed fiat (bank transfer, cash app, etc.) or other crypto. Once the seller confirms receipt (via chat or in-app status), both parties (or the required threshold) sign the release transaction. DigiByte’s ~15-second block times make on-chain settlement fast and low-cost.
5. Release or dispute
- Successful trade → funds release to the buyer; reputation scores update.
- Dispute → the third key (arbiter) can be used according to clear rules, or the parties negotiate in chat.
Reputation (ratings, badges, trade history) helps users choose reliable counterparties over time.
6. My Orders dashboard
Users track open, completed, and disputed trades in one place, all while remaining in full control of their main wallet balances.
Because everything runs inside the self-custodial wallet, private keys never leave the user’s device for ordinary sends, and the marketplace escrow uses the same transparent multisig tools already available for personal use. The backend (order matching, chat, reputation) is intended to support the experience without ever taking custody.
Why This Matters
Most crypto wallets stop at send/receive. DigiByte Wallet aims higher: a complete, privacy-respecting environment where users can hold, send, receive, authenticate, and eventually trade DigiByte peer-to-peer without leaving the app or trusting a centralized exchange with their funds.
The combination of a mature core wallet, production-grade infrastructure, finished multisig, and a clear Phase 3 plan for order books, escrow, chat, and reputation positions dgbwallet.app as a serious contender in the DigiByte ecosystem. As the P2P marketplace moves from “Coming soon” to live, users will gain a seamless way to buy and sell DGB directly with other people—fast, low-cost, and under their own keys.
Explore the wallet today at dgbwallet.app, check the live roadmap, and watch the P2P section. The foundation is already solid; the marketplace is the next major leap.
