Grofty

Grofty provides wallet and market-data products for Canton. The browser wallet covers accounts, supported balances and transaction workflows. Grofty Lens is a separate live data service. The announced Grofty DEX is a forthcoming trading interface.

• Manage a Canton Party ID and supported balances, including CC and USDCx.
• Review recipient details, expected received amounts and fees before a transaction.
• Use locally authorised signing rather than handing a signing key to the transaction backend.
• Access documented transfer, onboarding, bridge and existing in-wallet swap workflows.

Canton accounts use Party IDs and asset-specific transaction workflows. Grofty’s network guide explains how recipient readiness and preapprovals affect transfers and onboarding. It also distinguishes a Party ID’s readable label from its full identifier. These details matter when checking where assets will go and whether a recipient can receive them.

Grofty exposes several Canton-specific steps within a wallet experience: account identification, recipient checks, preapproval requirements and a breakdown of transaction costs. Its documentation treats bridge fees, swap fees and direct CC-transfer fees as distinct categories, helping users understand which operation they are authorising instead of treating all movement of assets as the same transaction.

Grofty Lens

Grofty Lens provides market data and liquidity analytics. Its published tools include historical Excel/CSV exports, alerts, APIs and SDKs. See the changelog for release details.

Live Wallet & Transaction Tools

The wallet covers account setup, supported balances and transfers. Existing in-wallet CC/USDCx swaps and bridge flows are documented separately from the future DEX. The review screen is intended to show the recipient, fee asset, gross and net amounts and the type of action being submitted.

Getting Started

Setup involves creating or importing a recovery phrase and choosing a PIN. Keep the phrase offline: the quick-start guide makes clear that it is central to recovering the account. Depending on the release and environment, onboarding may also require an approved or whitelisted account.

Official Resources

• Read Grofty’s documentation
• Understand the transaction flow
• Review the signing architecture

Grofty describes a prepare, sign and execute sequence. The backend checks transaction inputs, recipient readiness and fees, then prepares the payload. The extension unlocks the recovery material with the user’s PIN, derives a signing key in memory and signs locally. The backend submits the signed transaction and follows its confirmation.

According to its architecture documentation, the recovery phrase is stored locally in encrypted form using a PIN-derived key, while the backend does not retain the seed or private signing key. This separates local signing from server-side preparation and submission. Users still depend on the wallet software and its supporting services; non-custodial signing is not a claim that every operational risk disappears.

The Grofty DEX preview describes comparing venue quotes, itemising fees and letting users select a route. This is separate from the live wallet and Lens products. Historical Excel/CSV exports are already available in Lens, not merely a future feature. No DEX launch date is asserted here.