2gether vs BlueWallet

2gether operated as a mobile first financial ecosystem combining centralized digital asset trading with an integrated payment card. The application delivered a consumer oriented interface tailored for casual retail participants who wanted straightforward entry into digital asset markets without managing private cryptographic keys. Supported assets centered on major market capitalization tokens, including Bitcoin, Ethereum, Ripple, Litecoin, Bitcoin Cash, and Basic Attention Token, alongside the proprietary 2GT utility asset.

The central feature of the ecosystem was the prepaid Visa debit card, which interfaced directly with the customer custodial cryptocurrency balances and fiat euro accounts. When cardholders initiated transactions at physical or online merchant terminals, the backend payment engine liquidated the selected digital asset into euros in real time to settle with the card network. This structure allowed seamless retail payments without requiring manual trades beforehand.

Beyond standard payment routing, the application included portfolio tracking tools, recurring buy setups, and community governance features tied to 2GT token ownership. Users could participate in informal voting rounds regarding upcoming asset listings or app improvements. While the asset catalog covered essential large cap tokens, it lacked deep secondary market coverage, specialized decentralized finance tokens, and granular order placement options like limit orders or margin facilities.

BlueWallet is an open-source client application designed strictly for Bitcoin on-chain transactions and Lightning Network layer-two operations. Unlike multi-currency wallets that aggregate dozens of distinct blockchains, BlueWallet concentrates its feature set on Bitcoin script standards, including Native SegWit, Nested SegWit, and legacy address formats. Users can generate standalone single-signature wallets, import existing BIP39 recovery phrases, or coordinate complex multisignature vaults directly within the mobile application.

The software acts as a specialized user interface rather than a hosted service. In addition to active signing wallets, BlueWallet functions as a watch-only client. Holders can import public master keys, commonly known as xpub, ypub, or zpub strings, to monitor offline cold storage balances without exposing private keys to an internet-connected device. This architecture extends into Partially Signed Bitcoin Transactions, allowing the app to construct and export unfinalized transfers for offline verification by dedicated hardware devices.

For Lightning Network functionality, the application operates through the LndHub protocol. Users connect their personal lightning node or a third-party accounting backend to open payment channels and settle microtransactions. By restricting its scope to Bitcoin, the client avoids third-party token bloat, though individuals managing diversified digital asset holdings will need separate software solutions for other networks.

2gether adopted a zero explicit trading commission marketing narrative, meaning spot conversions between euro balances and digital assets did not carry visible transaction line item fees. Instead, trading expenses were incorporated into execution spreads. The backend system sourced liquidity from multiple external partner exchanges, adding a markup between 1.0 percent and 2.5 percent depending on market volatility, selected token pair liquidity, and client 2GT holding tiers.

Token utility rules allowed users who accumulated substantial amounts of 2GT to access tighter spread bands and waived monthly card management fees. Standard users who did not hold minimum staking thresholds encountered standard spread margins on buys and sells. Physical card issuance was initially free or subject to nominal delivery costs, while standard point of sale transactions in euros did not attract domestic surcharge fees.

Withdrawal costs presented notable friction points throughout the platform lifecycle. Transferring cryptocurrencies out of the app to external non custodial wallets incurred standard blockchain network fees alongside internal processing surcharges. When the company initiated shutdown procedures in 2022, management imposed an unexpected twenty euro account maintenance fee on inactive retail balances, which provoked significant client friction during the final migration and asset withdrawal period toward partnered exchange facilities.

BlueWallet does not impose application-level software fees, subscription charges, or platform commissions on standard on-chain transactions. The core financial cost of broadcasting transfers is determined strictly by the prevailing mempool conditions and block space demand on the Bitcoin blockchain. Because users control their transactions directly, they retain complete discretion over the satoshi-per-byte fee rate assigned to each broadcast.

The application provides dynamic fee estimation categorized by target confirmation speed, ranging from slow confirmation windows to high-priority settlement. For granular control, users can input manual fee rates down to single satoshis. If network congestion escalates after a transaction is broadcast, BlueWallet provides built-in support for Replace-By-Fee protocols, allowing senders to boost the fee rate of an unconfirmed transaction to accelerate confirmation.

Additionally, the client supports Child-Pays-For-Parent fee bumping, which enables recipients to attach a higher fee to an unspent output from a pending incoming transaction. When routing payments over the Lightning Network, routing fees depend entirely on the nodes handling intermediate hops and the terms established by the connected LndHub node. Third-party fiat on-ramp integrations that appear within the interface are operated by external providers, each applying distinct conversion spreads and payment processing surcharges.

2gether functioned as a purely custodial service provider, retaining full administrative control over cryptographic keys associated with user balances. Account holders did not hold private keys, passphrases, or individual seed backups. While this model simplified mobile onboarding for non technical consumers, it concentrated balance risks entirely within the corporate infrastructure and third party institutional wallet custodians.

Platform defenses relied on standard consumer authentication controls, including biometric authentication, mandatory two factor verification via SMS or authenticator apps, and algorithmic transaction monitoring for suspicious login locations. Cryptographic balances were primarily held in cold storage systems managed by institutional partners to mitigate online attack surfaces, with only small operational floats retained in warm wallets to settle daily card payments.

The limitations of this centralized custodial structure became evident during operational disruptions. In 2020, 2gether suffered a security compromise that resulted in the theft of approximately 1.2 million euros worth of digital assets from its operational hot reserves. Although the company sought to compensate affected users through 2GT token allocations rather than immediate liquid euro distributions, the event underscored the inherent risks associated with custodial multi asset mobile apps operating without comprehensive sovereign insurance coverage.

Security in BlueWallet is rooted in client-side key generation and non-custodial storage. Seed phrases and private keys are encrypted locally using the secure enclave or keychain mechanisms of the host operating system. The application codebase is published openly under the MIT license, permitting external review of the cryptographic implementations, key derivation paths, and network communication standards.

Beyond standard single-key BIP39 setups, BlueWallet incorporates advanced threshold security. Users can construct m-of-n multisignature vaults, distributing key shares across multiple hardware signers or separate physical locations. This design prevents an unauthorized transfer from occurring if a single device or seed backup is compromised. Plausible deniability is further enhanced through a decoy wallet feature, which presents an alternate wallet instance when an auxiliary unlock PIN is entered.

Privacy controls extend to network broadcasting. Users can route client traffic through the Tor network to obscure their IP address when communicating with Electrum servers. Furthermore, the application allows users to connect to their personal Bitcoin full node or private Electrum backend, ensuring transaction data and address queries remain decoupled from public infrastructure. These mechanisms provide protective controls against surveillance, though physical device security and seed phrase backups remain the sole responsibility of the user.

2gether focused its operational presence across member states of the European Economic Area, specifically targeting consumers residing within Eurozone markets such as Spain, Portugal, Italy, and France. Due to cross border financial regulations and card scheme limitations, the platform did not accept registrations from residents of the United States, Canada, the United Kingdom, or high risk jurisdictions identified by international anti money laundering taskforces.

Onboarding required standard customer verification procedures in compliance with European Anti Money Laundering directives. Users submitted official identity documentation, such as national identification cards or passports, alongside live biometric facial verification and proof of residential address. Account approval was generally processed within several hours through automated verification tools, allowing newly approved users to generate virtual payment cards immediately while physical cards arrived by postal mail.

Customer support channels operated primarily through an in app ticket system, direct email assistance, and moderated social messaging channels. Response times and query resolutions were acceptable during normal operations but deteriorated significantly during market volatility spikes and security incidents. When service closure was announced in July 2022, support bandwidth was overwhelmed, leaving many users dependent on community forums and Bit2Me transition documentation to clarify balance retrieval instructions.

BlueWallet is distributed globally as an open-source software application across major mobile and desktop operating systems, including iOS, iPadOS, macOS, and Android. Because it operates as a self-custody software client rather than a financial custodian, users are not required to complete identity verification, submit proof of address, or establish managed accounts to download and operate the wallet. Access is unrestricted by regional regulatory licensing frameworks that apply to custodial intermediaries.

Operating as an open-source community project, BlueWallet does not maintain a real-time customer service desk, telephone support line, or managed ticketing portal. User assistance is organized through decentralized channels, including official documentation, community forums on Telegram, and public issue tracking repositories on GitHub. Users navigating complex configurations, such as custom node linking or multisig recovery, rely primarily on published technical guides and community responses.

Regulatory obligations regarding asset ownership, tax reporting, and local reporting standards fall entirely on the individual user. Software updates are released regularly across public app marketplaces and source code repositories to address client-side stability, node protocol adjustments, and operating system compatibility. Users must exercise care to download official releases from recognized repositories and maintain secure offline seed backups before applying major system upgrades.