Skip to main content

Hathor MetaMask Snap

The Hathor MetaMask Snap brings native support for HTR and custom tokens directly inside MetaMask. With the Snap installed, users can manage their Hathor assets, create tokens, and interact with Nano Contracts without leaving the wallet.

You can install the Hathor Snap directly from the MetaMask Snaps Directory.

Prerequisites​

Before installing the Snap, make sure you have:

  • MetaMask (Flask or a Snaps-compatible release) installed in your browser.
  • A supported browser: Chrome, Firefox, or Brave.
  • An existing MetaMask account. The Snap derives Hathor keys from your MetaMask seed — no separate Hathor wallet seed is required.

Why use the Hathor Snap?​

Unlike typical EVM-based integrations, the Hathor Snap works with UTXO-based transactions (like Bitcoin), native token creation without smart contracts, and Nano Contracts for lightweight programmability. Instead of switching between wallets or tools, the Snap enables you to:

  • Manage HTR and custom tokens inside MetaMask.
  • Interact with Nano Contracts — Hathor's smart contracts.
  • Handle advanced transactions like time-locks and multisig.
  • Safely sign oracle data using your MetaMask identity.

The Snap is well-suited for developers building on Hathor, users managing multiple token types, and integrations requiring secure signing.

Key capabilities​

Wallet and asset management​

The Hathor Snap provides a complete set of tools to manage your assets directly within MetaMask, including:

  • Sending and receiving HTR and custom tokens.
  • Viewing balances and transaction addresses.
  • Generating new addresses.
  • Retrieving the extended public key (xpub) for integrations.
  • Read-only wallet support.
  • Accessing the full UTXO set.

Tokens and transactions​

The Snap also enables advanced transaction handling and token management, such as:

  • Creating custom tokens, including Fee-Based Tokens (FBT).
  • Sending transactions with timelock support.
  • Building and signing multisig transactions.
  • Previewing network fees before confirmation.

Nano Contracts​

The Snap supports lightweight programmability on Hathor Network through Nano Contracts, allowing you to:

  • Deploy and interact with Nano Contracts.
  • Create tokens via contract execution.
  • Sign oracle data securely.
  • Sign transactions with a specific address.

Network control​

You can control the active environment on Hathor Network, making it easy to:

  • Switch between mainnet and testnet.
  • Query the currently connected network.

Version history​

note

Version 0.4.2 is planned and not yet released. Features listed for that version are subject to change.

VersionReleasedHighlights
0.4.2Planned 2026Fee-Based Tokens, fee preview, time-locks, multisig improvements
0.3.0Dec 5, 2025Oracle signing, Nano Contract transactions, UTXO retrieval
0.2.0Oct 28, 2025Read-only wallet, network switching, xpub support
0.1.0Sep 24, 2025Initial release: tokens, transfers, Nano Contracts

FAQ​

What is the Hathor MetaMask Snap?​

The Snap is an extension to MetaMask that adds support for the Hathor Network. It allows you to send, receive, and manage HTR and tokens, as well as interact with Nano Contracts, directly inside MetaMask.

Which wallet does it work with?​

The Snap works together with the Hathor Web Wallet. You can use both together to manage your Hathor assets inside MetaMask.

What are Nano Contracts?​

Nano Contracts are Hathor's lightweight smart contracts. The Snap allows you to deploy and interact with them directly from MetaMask.

Can I create tokens with the Snap?​

Yes. The Snap includes the ability to create custom tokens on Hathor, including Fee-Based Tokens.

Will more features be added?​

Yes. Support for additional features is being worked on and updates will be released in future versions. See the version history above for planned additions.

Are my funds safe?​

Yes. Private keys remain securely managed by MetaMask. The Snap only interacts through approved permissions.

What permissions does the Snap require?​

The Snap requests access to display dialogs, manage local state, make network requests, and derive Hathor keys from your MetaMask seed using derivation paths m/44'/280'/0' and m/280'/280'. Private keys never leave MetaMask.

Next steps​