Description: MetaMask add contact option only receives Ox and ENS contacts, my EVM on MetaMask has been connected to the NEAR Main Network hence I can send and receive $Near on my MetaMask but can’t add jmadao.near as a contact.
I am officially making a feature request on behalf of myself and NEAR Foundation to add .near contact in addition to Ox and ENS.
Purpose: 1. For easy transaction details filling.
2. To support the Creation of a Dev Envr logic for the purpose of implementing a hybrid smart contract between imported networks (.near + Ox + ENS) on my MetaMask.
3. For the purpose of viewing added contacts/contract of different networks associated with a transaction/Blocks.
This feature is an important prerequisite to the possibility of implementing hybrid smart contracts on all JMA DAO proposed APIs, particularly the JMA-DAO-WALLET; a native web3 community payment System.
Extension/Mobile/Both: Both
Images/Attachments:
The “swap in escrow” will be a hybrid contract call, packaged in an API plug-in to interact with added contacts associated with a single transaction.
Hence this feature request on my MetaMask Profile; MetaMask > Settings > Add Contact = {(.near, Ox, ENS,)}
