## 

```cv
gallery
{"layout":"hscroll","images":[{"src":"https://firebasestorage.googleapis.com/v0/b/maitake-project.appspot.com/o/pages%2FMhnXPqFKngV4steK9OSQtSsYopI2%2FDm0jeb9zd8A03qqhrU2i%2Fd1767d0f-7fd7-4f47-b12b-e3207f488ef9.png?alt=media&token=e559851a-4f88-4623-ba80-e81b6d88fe5c","id":"d1767d0f-7fd7-4f47-b12b-e3207f488ef9","width":1744,"height":1152,"filename":"Screenshot 2023-12-16 at 09.47.50.png","type":"image/png","caption":"","border":false}]}
```

Many crypto wallets are out on the market, but they don't all have the same capabilities. They may be specific to a particular ecosystem or lack dapp functionality. But what if there were a way to expand a wallet's abilities to surpass these limitations?

The Filecoin network has only a few native wallet clients. How can we increase the adoption of the Filecoin network so developers and users can access the ecosystem while also integrating the benefits of the EVM? [Metamask's Snaps](https://metamask.io/snaps/) are one way to add custom functionality to a widely used wallet.

### **Understanding Filecoin Wallet Addresses**

First, for clarity, let's review some [wallet terminology](https://fission.codes/blog/wallet-stack/). Wallets can contain multiple accounts. Each account has an address. Think of it like a bank account with a checking account number.

Getting more technical, wallets have Secret Recovery Phrases. Accounts are derived from SRPs, creating private keys that control the account. Addresses are public and are tied to the transactions executed over the blockchain.

Filecoin has five types of addresses. The ones we'll focus on are F1 and F4. F1 is the Filecoin native address for transactions done solely over the Filecoin network. F4 is the FEVM address. FEVM, or the Filecoin Ethereum Virtual Machine, allows developers to port any existing EVM-based smart contracts straight onto the FVM. The F4 address is a translation layer to the EVM ecosystem.

### **Introducing Filsnap**

Filsnap is a MetaMask plugin, or [snap](https://metamask.io/snaps/), that adds support for Filecoin native accounts and functionality. MetaMask only supports the EVM ecosystem, so Fission's plugin enables users to utilize MetaMask as a Filecoin wallet.

Filecoin native wallet: Filsnap can send transactions and receive assets using F1 addresses.

F1 to F4: Say a person has a wallet supporting only Filecoin native F1 addresses. The user could send their assets to Filsnap and, from there, send assets to F4 addresses. The same goes for exchanges like Coinbase, which doesn't support F4 addresses yet.

F4 to F1: Say a user wants to withdraw yield from a liquidity pool and put it in cold storage. They can send assets from an F4 address in the Filsnap wallet to the cold wallet that supports F1 addresses via a FilForwarder smart contract. This contract translates from FEVM to native.

### **The Filsnap Library**

Although Filecoin JS libraries were already available, we chose not to reuse them for a few reasons. First, MetaMask is constantly changing, and we wanted to ensure the code was as up-to-date as possible. Second, the existing libraries are big and weighed down by many dependencies. A lightweight wallet client is preferred for a better user experience when working with the blockchain. Third, because we take security so seriously, we had all of the cryptography dependencies in our library independently audited for peace of mind.

The new [Filecoin JavaScript Library - iso-filecoin](https://github.com/hugomrdias/iso-repo/tree/main/packages/iso-filecoin) is the foundation for three packages - Filsnap, Filsnap Adapter, and Filsnap Adapter React. [Filsnap](https://github.com/filecoin-project/filsnap/tree/master/packages/snap) is the snap installed in the MetaMask extension. [Filsnap Adapter](https://github.com/filecoin-project/filsnap/tree/master/packages/adapter) enables developers to interact with Filsnap from a dapp. Finally, [Filsnap Adapter React](https://github.com/filecoin-project/filsnap/tree/master/packages/adapter-react) includes React-specific hooks for dapp integration.

As mentioned, there are few native Filecoin wallets, and the existing ones don't expose their functionality to dapps. Filsnap, however, has an API for transactions on the native layer, enabling developers to build apps with native Filecoin functionality!

### **The Filsnap Demo**

The Filsnap demo supports Filecoin native and FEVM transactions using either Filsnap for native or Metamask for EVM. As mentioned above, it's a great way to manage your assets despite the current technical limitations in wallets and exchanges. [It used to be much more complicated](https://filecointldr.io/article/guide-how-to-transfer-fil-from-coinbase-to-a-metamask-wallet-0x), but now you can do it all in the Filsnap demo app.

Another benefit of using the Filsnap demo app is security through verifiability. Anyone can verify the snap installed in Metamask through [NPM Provenance](https://www.npmjs.com/package/filsnap/v/0.3.2#user-content-provenance) and the app code using [IPFS](https://bafybeihevfatvsypn35ywbloc4vrjpjpk5akhqv7yi4d7mrahzaaatcmp4.ipfs.dweb.link/) and [GitHub](https://github.com/filecoin-project/filsnap/actions/runs/5984204522/attempts/1#summary-16235152758).

```cv
gallery
{"layout":"hscroll","images":[{"src":"https://firebasestorage.googleapis.com/v0/b/maitake-project.appspot.com/o/pages%2FMhnXPqFKngV4steK9OSQtSsYopI2%2FDm0jeb9zd8A03qqhrU2i%2F7f1c6e37-1cba-45cf-b0fe-c71c2783b8d5.png?alt=media&token=bae956d2-5795-4c67-b9a9-af3deb218014","id":"7f1c6e37-1cba-45cf-b0fe-c71c2783b8d5","width":1614,"height":456,"filename":"Screenshot-2023-08-31-at-12.17.56.png","type":"image/png","caption":"","border":false}]}
```

Every app release and git tag is published to IPFS using [Fission apps](https://guide.fission.codes/developers/cli/working-with-apps) and can be cloned/forked from [GitHub](https://github.com/filecoin-project/filsnap) if a user wishes to self-host or verify integrity using content addressing.

### **Getting Started**

The Filsnap package has been audited, and the [MetaMask Snaps are now in open beta](https://metamask.io/snaps/).

The Fission team, lead by Hugo Dias, implemented the audited Filsnap as part of a contract with Protocol Labs. As part of this process, Hugo also wrote and open sourced the isomorphic filecoin utilities, which is now the recommended way to work with native Filecoin accounts and supporting cryptography.

* Isomorphic Filecoin abstractions for RPC, signatures, address, token and wallet. [`iso-filecoin`](https://github.com/fission-codes/filecoin)

* [API Docs](https://fission-codes.github.io/filecoin)

* [NPM package](https://www.npmjs.com/package/iso-filecoin) 

Please get in touch if you'd like to support long term maintenance of core open source Filecoin utilities.

Try the [Filsnap demo](https://filsnap.fission.app/) today, and let us know what you think! We'd love to hear your feedback. Join us in the `#filsnap` channel in Filecoin Slack, or drop by the [Fission Discord](https://fission.codes/discord).

Original [post](https://fission.codes/blog/introducing-filsnap-filecoin-wallet) on the Fission blog.

Introducing Filecoin Wallet

Software Engineer

Trainer's Pedagogical Aptitude Certificate

Connect to Filecoin dapps using Metamask. Manage Filecoin accounts, send FIL to Native and FEVM accounts and enable FEVM transaction insights.

Links:

[Metamask Snaps Directory](https://snaps.metamask.io/snap/npm/filsnap)

[Audit](https://consensys.io/diligence/audits/2023/08/metamask/partner-snaps-filsnap)

Filecoin Wallet on Metamask

User Controlled Authorization Networks (UCANs) are an extension of the popular [JSON Web Token](https://jwt.io/) format specifically designed to enable ways of authorizing offline-first apps and distributed systems.

UCAN

The JavaScript Implementation of libp2p networking stack.

A modular network stack.

Run your network applications free from runtime and address services, independently of their location.

This project has been used in production for years in Ethereum, IPFS, and more.

js-libp2p

The JavaScript implementation of the IPFS protocol

The InterPlanetary File System (IPFS) is a set of composable, peer-to-peer protocols for addressing, routing, and transferring [content-addressed](https://docs.ipfs.tech/concepts/glossary/#content-addressing) data in a decentralized file system.

js-ipfs

NFT Storage is a brand new service, built specifically for storing off-chain NFT data on IPFS and Filecoin.

NFT Storage

Run unit tests with several runners or benchmark inside real browsers with playwright.

playwright-test

Isomorphic filecoin abstractions for RPC, signatures, address, token and wallet. Used by the [Metamask Filecoin Wallet](https://github.com/filecoin-project/filsnap).

iso-filecoin

Built [NFT Storage](https://nft.storage/) and [Web3 Storage](https://web3.storage/) from 0 to [50M uploads](https://blog.nft.storage/posts/2022-03-29-50M-uploads).\
Core Engineer on ipfs, libp2p and multiformats.\
Created the [Filecoin Specification](https://spec.filecoin.io/).\
Helped bootstrap the [Filecoin Foundation](https://fil.org/).

Writing code for [UCAN](https://github.com/ucan-wg) and [IPVM](https://github.com/ipvm-wg)