Create or import accounts in Keychain and manage their keys within the extension’s account workflow.
AN APPLICATION REQUEST
A connection. A choice about access.
Read which interface is requesting a connection. Connected sites can be reviewed in Keychain’s own settings.
REVIEW & AUTHORISE
The request. Your attention.
Compare the action presented by the interface with the request shown by Keychain before authorising it.
INTERFACE→REQUEST→KEYCHAIN
An account and signing tool for Namada. A separate place to manage keys and review the request.
Role
Account creation, key management and transaction signing.
Relationship
A separate product in Namada’s documented onboarding flow.
Your checkpoint
Read the request in the extension before authorising it.
Explore the signing workflow +
An interface can request a signature from Keychain. Compare the request in the signing tool with the action you intended, including the network, asset and destination.
Creating a website connection and authorising a transaction are different decisions. Keychain manages these requests within its own account and signing workflow.
THE INTERFACE PRESENTS THE ACTION.The signer authorises it.
Shielding moves assets into the network’s shielded context. Review the asset, route and request in the tools you use.
A view into network actions. The interface presents the journey; a signing tool authorises the request.
Role
Shielding, staking and governance workflows described in Namada’s guides.
Relationship
A community interface, with independently hosted instances.
Your checkpoint
Verify the host and the request shown by your signer.
Explore the interface workflow +
The interface helps present assets and actions, while the network defines protocol rules. The host you visit and the signing tool you use remain separate parts of the workflow.
Community operators host Namadillo independently. Choose the instance you use, review its publisher and follow the request through to your signing tool.
Ledger Nano S PlusManufacturer photograph. Documented Keychain context.
Hardware signing has specific requirements. The documented relationship is with Namada Keychain.
Role
A physical signing device in the documented Keychain workflow.
Compatibility
Depends on the exact model, operation, firmware and Namada application.
Scope
Ledger with Namada Keychain; requirements depend on the operation and device.
Read the device and operation context +
The detailed Keychain guide requires a Ledger Nano S Plus or newer for shielded MASP operations. It distinguishes these from transparent operations that older devices can perform. The network start page separately carries a Nano S exclusion.
Follow the current Keychain instructions for your device and intended operation, including firmware and the Namada Ledger application. Review the request on the device before signing.
A decentralised protocol and the applications used to reach it need not share the same operator. That independence makes the host, interface and signer separate decisions.
Begin with the network and intended action, choose the application source, then compare the final request in your signing tool. Explore the directory by role to build a clear path from interface to authorisation.
