A web3 user interacts with certain set of wallets for most of the payment, they can be family, friends, work colleagues etc. They pay each other frequently and need to repeat the same process of copying/pasting that address again and again but not anymore

Fetcch is launching the most requested feature by wallet - Synchronized Address Books, now user can save frequently saved address in a wallet, and it will be accessible on each of your other wallets, instantly.

Think of address books as contact lists. They are like frequently contacted numbers, instead of numbers, here that will be address or an ID like satyam@metamask or satyam.eth

They help users to speed up their transaction process, as they don’t need to remember or copy/paste addresses, they can just select a contact/address from the list and transact with them easily.

This features enables Fetcch powered wallets to have a globally shared address books that is fast, expandable, and enables wallets to up their UX by a lot.

Users do a lot of transactions between people they know, like their family members, friends, work colleagues etc. But if a user is paying a person lots of times over a day or month, its better to save that contact somewhere, so users can directly access it while doing a transaction reducing the number of clicks.

In some surveys, it is shown that having an address books inside payment app has help increase volume, as now for doing a payment, users don’t need to copy/paste identifiers or remember them.

Web2 payments apps like Cashapp, Venom and UPI apps did a very great job of building address books directly inside their respective apps. Web3 wallets/payments app have followed the same process but somethings are very different in web3 than web2. In web3 a user can access same account through multiple payment apps, but current address books are siloed to a single payment app, this is the main issue where UX is lacking, even though transactions are onchain, publicly available, still wallets don’t have an synchronized address books among themselves.

We enable wallets to access global address books for a user. There can be multiple sub address books which a user can manage. So, users can manage their address books more effectively. A example, satyam@metamask wants to segregate addresses in the address book based on categories like home, work, friends etc, they can easily create sub-address books inside their wallet which will use Fetcch APIs.

Each Fetcch Identity can have multiple sub-address books, like one for work, another for personal etc. This will help them segregate addresses/identities based on their relation with them.

If someone wants to share their address book(s) with other identity, they can invite that identity to that particular address book, this invite can be scoped to read, read-write, so if the receiver identity accepts the request, they will now be able

All of the address books of a user are encrypted and stored on storage solutions like IPFS/Arweave and their merkle root onchain to easily verify if those books are tampered with or not.