2gether vs Cobo

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.

Cobo structures its offering around three primary custody architectures: Cobo Custody, Cobo MPC Co-Managed, and Cobo Argus. The fully custodial branch operates as a traditional regulated custodian where Cobo manages private key storage, cold vaults, and on-chain settlement. For teams requiring sovereign control without single points of failure, the MPC solution uses threshold signature schemes to distribute key shares across the customer, Cobo, and an independent recovery party. The Argus solution extends custody logic directly to Ethereum virtual machine chains, enabling automated decentralized finance permissions, strategy automation, and role-based access to on-chain protocols without relinquishing core administrative rights.

Across these architectures, Cobo supports more than 80 layer-1 and layer-2 blockchains alongside thousands of fungible tokens and digital assets. This breadth covers major ecosystems including Bitcoin, Ethereum, Solana, Cosmos, Avalanche, and modern rollup networks. In addition to raw key management, Cobo integrates Wallet-as-a-Service APIs that let fintech applications, exchanges, and gaming platforms programmatically provision deposit addresses, automate withdrawal lifecycles, and handle sweeping operations across heterogeneous blockchain protocols without maintaining standalone full node fleets.

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.

Pricing at Cobo follows institutional convention rather than a uniform retail rate card. Costs are determined through commercial proposals based on chosen custody models, monthly transaction volumes, developer API thresholds, and total assets under custody. Fully custodial cold-storage setups generally incur recurring asset-based basis-point fees paired with standard transaction processing charges. In contrast, the MPC Wallet-as-a-Service tier often blends fixed monthly infrastructure licensing tiers with variable consumption fees pegged to active monthly wallet addresses, API call volumes, or signature generations.

Network transaction fees for deposits, transfers, and sweeping remain subject to underlying blockchain conditions. Cobo allows administrators to configure automated gas management and transaction acceleration routines across supported networks. Withdrawals undergo structured multi-step approvals based on organizational policies before broadcast to the network. Organizations running high-throughput payment gateways or exchange deposit sweeping can optimize gas expenditures through Cobo batching routines, though high on-chain congestion will naturally elevate base network settlement costs regardless of internal infrastructure efficiency.

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.

Cobo builds its security posture on independent technical certifications, hardware security modules, and advanced cryptography. The provider maintains SOC 2 Type II attestation and adheres to ISO 27001 data management protocols. Within its MPC infrastructure, key shares are generated and held across isolated environments, ensuring no single entity possesses the complete private key at any stage during generation, signing, or rotation. Hardware isolation mechanisms and secure enclaves further restrict unauthorized extraction of sensitive runtime memory or cryptographic components.

Organizational governance is enforced through a granular rule engine. Administrators can construct conditional approval workflows involving multi-person quorums, geographic restrictions, IP address allowlists, time locks, and per-token spending limits. Smart contract interactions can be restricted to verified protocol contracts, blocking arbitrary smart contract executions. For disaster recovery, Cobo provides clear disaster contingency protocols, allowing clients to reconstruct key pairs independently if primary service connectivity becomes compromised, though recovery speed depends on client key share integrity.

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.

Headquartered in Singapore and founded in 2017, Cobo operates globally while navigating jurisdictional compliance mandates. The company maintains regulatory registrations in relevant operating hubs and enforces comprehensive Know Your Business screening before provisioning production environments. Prospective clients must submit verifiable corporate formation documents, ownership charts, and compliance identity verifications for authorized signatories and system administrators. Organizations domiciled in sanctioned regions or non-compliant jurisdictions are excluded from onboarding under global anti-money laundering frameworks.

Enterprise clients receive structured technical support through dedicated account managers, engineering integration channels, and round-the-clock emergency escalation pathways. Cobo provides software development kits across major programming languages, detailed REST API documentation, and staging sandbox environments for integration testing. While developer resources are robust, routine inquiries require navigating enterprise ticketing systems, making real-time troubleshooting reliant on the specific service tier negotiated in the commercial service agreement.

The closure of 2gether highlights critical counterparty risks inherent in custodial fintech platforms that rely on private venture funding and native token economics. Because cryptocurrency balances deposited on centralized consumer platforms do not benefit from national bank deposit protection schemes, customers remain exposed to company insolvency and sudden liquidity halts.

When 2gether encountered unsustainable operational costs and bear market contraction in mid 2022, management chose to shutter retail consumer operations rather than maintain expensive custodial reserves. The subsequent transfer of account data and remaining token balances to Bit2Me offered an alternative recovery path, but users who did not accept the commercial migration faced account liquidation charges. Prospective crypto consumers must weigh the convenience of combined debit cards against the structural safety of holding assets in private, self custodial hardware devices.

Engaging an institutional custodian involves balancing operational flexibility against counterparty exposure. In the full custody tier, digital assets depend directly on custodian solvency, operational controls, and segregated legal structures. In the co-managed MPC model, counterparty risk is distributed across separate key share participants, preventing any single entity from executing unauthorized transfers. However, governance risks persist if client-side signing credentials or internal access controls are compromised by operational lapses. Business continuity requires maintaining strict internal discipline around off-site key share backups, routine credential rotation cycles, and authorized signing quorums. Institutional administrators must also implement secondary approval layers and network allowlists to protect programmatic API endpoints from unauthorized exploitation during routine daily operations.