Build / Dubhe Wallet

A production wallet for Move apps and high-value execution

Dubhe Wallet is not framed as a broad consumer wallet. It is designed for complex Move applications, permission-sensitive flows, and execution paths where risk, recovery, and operational control matter.

Positioning

Others optimize for onboarding, trading, or distribution.

Dubhe Wallet optimizes for execution, control, and production readiness.

Control permissions, not just signatures

Dubhe Wallet is built around authorization review, risky capability handling, session cleanup, and threat-aware execution.

Support multi-step onchain workflows

Send, swap, bridge, and order flows are treated as recoverable execution paths instead of one-off wallet prompts.

Operate beyond a personal wallet

Sponsored gas, hardware-backed signing, institutional approval policy, and recovery drills push the product toward team and treasury use cases.

Why this wallet exists

The real gap is not wallet access. It is production execution.

Many wallets already solve onboarding, asset display, and generic dApp connect. Dubhe Wallet is aimed at what happens after that: multi-step workflows, long-lived permissions, sensitive sessions, and partial execution states that need recovery rather than guesswork.

Risk and permissions

Control Surface

Authorization Center for reviewing and revoking risky capabilities

Transaction risk guard for high-value or suspicious execution

Threat and phishing policy checks on sensitive approval flows

Complex flow support

Execution Surface

Bridge status, advanced orders, and activity reconciliation

Execution-aware notifications and runtime visibility

Sponsored gas preference and fallback handling

Security and recovery

Operations Surface

Hardware / OWS signing paths

Session Manager for runtime cleanup and control

Recovery drills for passkey, mnemonic, and key-based recovery

Built for

Not a mass-market wallet pitch

The right audience is narrower and more valuable: applications and operators that need execution confidence, clearer control, and operational safety.

Move apps

Applications with complex state, persistent permissions, and execution paths that need more than a basic wallet modal.

Power users

Operators who care about recoverability, high-value transaction review, and reliable execution across swap, bridge, and permissions.

Teams and treasury

Groups that need approval policy, hardware-backed control, sponsored execution, and stronger operational safety.

Security and control

Wallet UX is only part of the product

Dubhe Wallet should eventually present a tighter control plane for sensitive flows: permission review, execution visibility, session cleanup, hardware-backed signing, and recovery readiness. That is where it separates from a generic wallet landing page.

Hardware and recovery

OWS / hardware signing and recovery drills should be visible product promises, not buried settings.

Execution state

Bridge tracking, order state, activity reconciliation, and execution history are core UX for non-trivial workflows.

Operational visibility

Notifications and runtime controls matter when the wallet is used as an execution surface, not just an identity surface.

Team controls

Institutional approval policy and sponsored execution are how the product starts to move past pure consumer wallet territory.

Platform status

A real product page should make release state explicit

This is the section that can later absorb app store badges, extension links, and release notes. For now, it should tell visitors what is active and what is still being phased in.

Web Surface

Active

Current active product surface and the right place to explain the wallet today.

Mobile / Extension

Phased rollout

Planned product surfaces that should be introduced here as release status becomes public.

Distribution

Preparing

Use this page as the canonical pre-launch product page before app store and public download CTAs are finalized.

When to add app store CTAs

Add direct download badges only when release state, surface support, and support channels are stable enough to own publicly. Until then, this page should focus on explaining the product clearly.

FAQ

Keep the product story crisp

This is where the landing page should resolve confusion between Dubhe Wallet, Dubhe Engine, and the broader Dubhe stack.

Is Dubhe Wallet a general-purpose Sui wallet?

No. The positioning is narrower and more deliberate: a production wallet for Move apps, permission-sensitive workflows, and high-value onchain execution.

Who should evaluate it first?

Teams building complex Move applications, operators handling non-trivial execution flows, and treasury-like environments where control and recovery matter.

What makes it different from onboarding-first wallets?

Most onboarding-first wallets optimize for fast setup and clean daily usage. Dubhe Wallet is optimized for control, execution confidence, and operational readiness.

Should this page already include app store links?

Only once the release state is stable. Before that, it should explain the product, the intended users, and the execution-oriented capabilities clearly.

Next step

Use this as the dedicated wallet page inside Build

The next iteration should add release screenshots, supported surfaces, and real distribution links. The important part is already in place: the wallet now has a proper narrative home instead of being buried behind a generic site link.