Mantra DAO & RWA-first wallet with native compliance

[Kihan1225]

I appreciate that open source development and external audits are highlighted so clearly in the proposal. For an official wallet, that level of transparency isn’t optional, it’s a baseline requirement. It gives the community a way to independently verify security assumptions instead of relying purely on trust. Over time, this also makes it easier for contributors and reviewers to spot issues early. That openness should help build long-term confidence in the wallet

[bananus1763]

The DID approach seems forward-looking, especially as regulation becomes more common across jurisdictions

[Arl12]

How do you plan to balance simplicity for newcomers with advanced controls for power users over time?

[Elava23]

The transaction previews and built-in scam warnings could save a lot of users from very costly mistakes. For newer users especially, it’s often unclear what they’re actually approving when signing a transaction. Clear, human-readable explanations can make a huge difference in preventing accidental losses. This kind of protection also reduces the fear of using DeFi for the first time. It’s a strong signal that user safety is being taken seriously

[Zalarcan768]

Account abstraction and social recovery as future features sound promising, even if they’re not part of the initial release

[soffije]

@gutmann

Idea makes sense, especially for RWA. Quick question though — if I pass KYC once in this wallet, do I need to repeat it every time I create a new address or restore the wallet on another device? Just trying to understand how “one-time” this really is in practice.

Hi, @gutmann !

Great question. If you restore the same seed phrase on another device, your existing DID (which represents your KYC verification) will still be valid and linked to your wallet address. You won’t need to repeat the KYC process unless:

• You create a completely new wallet (new seed = new address), or
• Your DID is explicitly revoked (e.g. due to expired documents or regulatory requirements).

So as long as you use the same seed, KYC remains one-time and portable across devices.

[soffije]

@Liefn

Focusing on compliance and RWA is a smart move to attract a more professional user base. For those users, security and operational features are non-negotiable. Beyond the mentioned hardware wallet support, are there plans to build in native support for multi-signature setups or role-based permissions? Furthermore, given the wallet’s role as a gateway to regulated assets, can we expect its core code and security model to undergo rigorous, public audits before any mainnet release? Trust for institutional adoption is built on that kind of transparency.

Hey, @Liefn !

Absolutely — both points are well aligned with our priorities.

1. Multisig and role-based permissions:
Yes, the architecture is being designed with institutional use cases in mind. Native support for multisig wallets (e.g., Cosmos LegacyMultisig and EVM-compatible contracts) is planned. We’re also exploring DAO-linked role-based access control — for example, allowing wallet users to act as signers or voters within permissioned DAOs based on their DID status and role (e.g., manager, auditor, investor delegate). These capabilities will be integrated once the DAO Factory layer is in place.

2. Audits and security transparency:
Yes, full public audits are a prerequisite before any production launch. All critical components — including key handling, transaction signing, DID validation logic, and bridge interactions — will undergo third-party audits. In addition, the codebase will be open-source under a permissive license, allowing independent verification. Transparency is non-negotiable, especially for RWA-facing infrastructure, and we’re committed to meeting that bar.

[soffije]

@os_creator

Does the ‘native compliance’ layer add any additional overhead to the seed phrase recovery process? For instance, if I recover my wallet on a new device, do I need to re-verify my identity, or is the compliance ‘badge’ tied to the address on-chain?

Hello, @os_creator !

No additional overhead. The compliance status (i.e., KYC verification) is tied to your on-chain address via a DID credential (typically a non-transferable NFT or attestation token). As long as you restore the same seed phrase — and therefore the same address — the wallet will automatically detect and reflect your verified status.

No need to re-verify identity unless the DID has expired or been revoked. So recovery is seamless, and compliance remains intact.

[soffije]

@evancaker

How would this handle users who already use multiple wallets today? Would migration be simple?

Hey, @evancaker !

Yes, migration is straightforward. Mantra Wallet supports standard BIP-39 seed phrases and derivation paths (e.g., m/44'/60'/0'/0/0 for EVM, m/44'/118'/0'/0/0 for Cosmos). If users already have wallets on other platforms, they can:

• Import their existing seed into Mantra Wallet to access the same addresses.
• Or, add multiple wallets (with separate seeds) for parallel account management.

There’s no vendor lock-in. The wallet is fully compatible with industry standards, so users can migrate in or out freely without needing to move funds or reconfigure identities.

[soffije]

@noface_0

Hardware wallet support on mobile is mentioned briefly. How mature do you expect that integration to be at launch?

Hi, @noface_0 !

At launch, hardware wallet support will focus on read-only portfolio visibility and transaction signing via external prompts, depending on the device.
Initially, hardware wallet users will be able to connect, view balances, and approve transactions with external confirmation. Full multisig + hardware flows will follow once the base is stable. Security and compatibility will be prioritized over feature breadth at v1.