2gether vs Hashkey Cloud

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.

HashKey Cloud operates validator and node hosting services across more than 80 major Proof of Stake blockchains. The platform covers Tier 1 networks such as Ethereum, Solana, Polkadot, Cosmos, Avalanche, Near, and Polygon, alongside emerging Layer 1 and Layer 2 ecosystems. Rather than bundling customer funds into centralized commingled lending pools, HashKey Cloud delivers infrastructure that enables direct on chain delegation and white label validator operations with complete transparency.

In addition to basic staking validation, the provider delivers dedicated RPC node access, enterprise API connectivity, and specialized liquid staking integration rails. Organizations running decentralized applications or institutional index products can deploy custom validator setups that integrate directly with existing treasury software. This multi network scope allows digital asset funds to consolidate their staking operations under a single infrastructure provider without needing to maintain separate internal engineering pipelines for every blockchain protocol they support.

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 HashKey Cloud is structured around validator commission percentages and customized enterprise service level agreements. For standard public validator nodes, the platform collects a programmatic commission taken directly from gross on chain staking rewards, typically ranging between 3 percent and 10 percent depending on the specific protocol and network economics. These fees are deducted automatically at the protocol layer before network rewards are distributed to delegators.

For bespoke institutional deployments, such as dedicated private validators or white label staking setups, HashKey Cloud offers custom commercial contracts. These agreements may combine fixed monthly node management fees with variable performance incentives. Asset withdrawal timing and unbonding periods are strictly governed by underlying blockchain protocol rules rather than HashKey Cloud internal discretion. Delegators must account for protocol native unbonding queues, which can range from several days on networks like Polygon to several weeks on Polkadot or Ethereum.

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 architecture at HashKey Cloud centers on a strict non custodial framework. Clients maintain control of their underlying principal assets and private withdrawal keys, delegating only validation signing authority to HashKey Cloud node clusters. This setup helps verify that validator operational failures or provider insolvencies do not expose principal balances to direct custodial seizure or balance sheet rehypothecation. Stakers retain independent governance rights and native protocol withdrawal powers throughout the entire delegation lifecycle.

To mitigate the technical risks of validator slashing, HashKey Cloud employs multi region server redundancy, automated failover systems, and dual validation monitoring protocols. The organization maintains SOC 2 Type II audit compliance and ISO 27001 certifications, reflecting rigorous information security management. Node infrastructure is integrated with qualified institutional custodians and multi party computation wallet providers, enabling treasury managers to implement multi signature authorization rules and role based governance over all delegation and withdrawal transactions across multiple operational tiers.

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.

HashKey Cloud operates out of Hong Kong and Singapore under the broader compliance framework of HashKey Group, aligning institutional services with regional regulatory requirements. While public validator nodes accept decentralized on chain delegations globally without geographic gating, direct enterprise contracts and bespoke white label services require institutional onboarding, corporate entity identity verification, and anti money laundering screening. Institutional clients across Asia, Europe, and other supported international regions can establish formal commercial service agreements tailored to their operational footprints and internal compliance mandates.

Customer support for enterprise clients includes dedicated technical account managers, around the clock infrastructure monitoring, and customized service level agreements covering node uptime metrics and operational incident management. Organizations deploying dedicated node clusters receive direct communication channels to engineering staff for protocol upgrades and hard fork coordination. Smaller delegators utilizing public validators can access comprehensive technical documentation, performance dashboards, and open developer resources, though individual retail ticketing remains secondary to high touch enterprise relationship management.

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.

Proof of Stake validation inherently involves protocol level operational hazards, primarily validator downtime penalties and double signing slashing events. If an infrastructure provider suffers extended connectivity loss or misconfigured failovers, the blockchain protocol may deduct a portion of the bonded collateral as an economic penalty.

HashKey Cloud addresses these hazards through redundant sentry node architectures, hardware security modules for validator signing keys, and automated monitoring systems. While these technical helps protect significantly lower the probability of infrastructure failure, institutional participants must recognize that on chain protocol risks cannot be completely eliminated. Treasury policies should evaluate protocol specific unbonding delays, governance fork risks, and reward volatility when allocating capital to network delegation.