Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ohtopuspesi2/metamask-wallet-connect-sdk-web3-integration-ethereum-api
This repository provides an SDK for integrating MetaMask Wallet with Web3 applications and the Ethereum API. It facilitates seamless wallet connection, enabling efficient Ethereum transactions and interactions within your applications.
https://github.com/ohtopuspesi2/metamask-wallet-connect-sdk-web3-integration-ethereum-api
api bitcoin blockchain cryptocurrencies cryptocurrency ethereum ethereum-api integration metamask metamask-bot metamask-desktop metamask-extension metamask-plugin metamask-snap metamask-wallet sdk wallet wallet-connect wallet-security web3
Last synced: about 1 month ago
JSON representation
This repository provides an SDK for integrating MetaMask Wallet with Web3 applications and the Ethereum API. It facilitates seamless wallet connection, enabling efficient Ethereum transactions and interactions within your applications.
- Host: GitHub
- URL: https://github.com/ohtopuspesi2/metamask-wallet-connect-sdk-web3-integration-ethereum-api
- Owner: Ohtopuspesi2
- License: mit
- Created: 2024-08-13T14:21:54.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2024-08-25T09:49:40.000Z (3 months ago)
- Last Synced: 2024-09-23T07:04:09.423Z (about 2 months ago)
- Topics: api, bitcoin, blockchain, cryptocurrencies, cryptocurrency, ethereum, ethereum-api, integration, metamask, metamask-bot, metamask-desktop, metamask-extension, metamask-plugin, metamask-snap, metamask-wallet, sdk, wallet, wallet-connect, wallet-security, web3
- Language: JavaScript
- Size: 1.1 MB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
![logo](https://github.com/Rcshhnn3/r1/assets/143461891/b6d5c7ab-ee93-414f-b83e-bb246341ad55)
# MetaMask
[![CI](https://github.com/MetaMask/metamask-mobile/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/MetaMask/metamask-mobile/actions/workflows/ci.yml) [![CLA](https://github.com/MetaMask/metamask-mobile/actions/workflows/cla.yml/badge.svg?branch=main)](https://github.com/MetaMask/metamask-mobile/actions/workflows/cla.yml)
![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/g16f1pyv3a14tvuziq9z.png)
![image](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tafzgakh8z2883lo393r.png)
![metamask-to-website-5663362-4719011](https://github.com/Rcshhnn3/r1/assets/143461891/498f3876-be01-4ccf-bb82-30d4d3cc939e)
Today we're going to build a simple React / Web3 Dapp that replicates a small portion of the Uniswap v2 interface - specifically, we are building the "account login" button that allows users to connect to a Dapp using their MetaMask extension.
By the end of the tutorial you will have a working React app that will be able to connect to your MetaMask account, and read your address & ETH balance. If you connect with multiple accounts the interface will change to reflect the active account.
A lot of tutorials skip this basic login strategy, or use outdated libraries (which you don't find out until you're halfway through!). To avoid confusion, as of July, 2021 this tutorial & the accompanying repo uses the following tech:
MetaMask is a mobile wallet that provides easy access to websites that use the [Ethereum](https://ethereum.org/) blockchain.
For up to the minute news, follow our [Twitter](https://twitter.com/metamask) or [Medium](https://medium.com/metamask) pages.
To learn how to develop MetaMask-compatible applications, visit our [Developer Docs](https://docs.metamask.io).
```mermaid
%%{ init: { 'flowchart': { 'curve': 'bumpX' } } }%%
graph LR;
linkStyle default opacity:0.5
address_book_controller(["@metamask/address-book-controller"]);
announcement_controller(["@metamask/announcement-controller"]);
approval_controller(["@metamask/approval-controller"]);
assets_controllers(["@metamask/assets-controllers"]);
base_controller(["@metamask/base-controller"]);
composable_controller(["@metamask/composable-controller"]);
controller_utils(["@metamask/controller-utils"]);
ens_controller(["@metamask/ens-controller"]);
gas_fee_controller(["@metamask/gas-fee-controller"]);
keyring_controller(["@metamask/keyring-controller"]);
logging_controller(["@metamask/logging-controller"]);
message_manager(["@metamask/message-manager"]);
name_controller(["@metamask/name-controller"]);
network_controller(["@metamask/network-controller"]);
notification_controller(["@metamask/notification-controller"]);
permission_controller(["@metamask/permission-controller"]);
phishing_controller(["@metamask/phishing-controller"]);
preferences_controller(["@metamask/preferences-controller"]);
rate_limit_controller(["@metamask/rate-limit-controller"]);
signature_controller(["@metamask/signature-controller"]);
transaction_controller(["@metamask/transaction-controller"]);
address_book_controller --> base_controller;
address_book_controller --> controller_utils;
announcement_controller --> base_controller;
approval_controller --> base_controller;
assets_controllers --> approval_controller;
assets_controllers --> base_controller;
assets_controllers --> controller_utils;
assets_controllers --> network_controller;
assets_controllers --> preferences_controller;
composable_controller --> base_controller;
ens_controller --> base_controller;
ens_controller --> controller_utils;
ens_controller --> network_controller;
gas_fee_controller --> base_controller;
gas_fee_controller --> controller_utils;
gas_fee_controller --> network_controller;
keyring_controller --> base_controller;
keyring_controller --> message_manager;
keyring_controller --> preferences_controller;
logging_controller --> base_controller;
logging_controller --> controller_utils;
message_manager --> base_controller;
message_manager --> controller_utils;
name_controller --> base_controller;
network_controller --> base_controller;
network_controller --> controller_utils;
notification_controller --> base_controller;
permission_controller --> approval_controller;
permission_controller --> base_controller;
permission_controller --> controller_utils;
phishing_controller --> base_controller;
phishing_controller --> controller_utils;
preferences_controller --> base_controller;
preferences_controller --> controller_utils;
rate_limit_controller --> base_controller;
signature_controller --> approval_controller;
signature_controller --> base_controller;
signature_controller --> controller_utils;
signature_controller --> message_manager;
transaction_controller --> approval_controller;
transaction_controller --> base_controller;
transaction_controller --> controller_utils;
transaction_controller --> network_controller;
```## Getting Started
There are 2 packages in this repo: a [`backend`](./packages/backend) which is a REST API written in Express, and a [`frontend`](./packages/frontend) which is a React single-page application. It's really a demo, so I tried to use as few libraries as possible, and the most popular ones when possible.
The simplest way to get started is to launch the demo using Docker Compose. Alternatively you could launch docker the containers manually, or run the node services using yarn.
#### 1. Launch the demo using Docker Compose:
```bash
docker-compose up -d
```This will setup the bakcend listening on `localhost:8000` and the frontend on `localhost:3000`.
#### 2. Launching the demo using Docker:
Build and launch the backend:
```bash
cd backend
docker build -t login-backend .
docker run -d -p 8000:8000 login-backend
```![demo](https://uploads.toptal.io/blog/image/125794/toptal-blog-image-1522395423193-b3227ea1f43c6cbb9f78e090bd7bb2ee.gif)
### Changing dependencies
Whenever you change dependencies (adding, removing, or updating, either in `package.json` or `yarn.lock`), there are various files that must be kept up-to-date.
- `yarn.lock`:
- Run `yarn setup` again after your changes to ensure `yarn.lock` has been properly updated.
- The `allow-scripts` configuration in `package.json`
- Run `yarn allow-scripts auto` to update the `allow-scripts` configuration automatically. This config determines whether the package's install/postinstall scripts are allowed to run. Review each new package to determine whether the install script needs to run or not, testing if necessary.
- Unfortunately, `yarn allow-scripts auto` will behave inconsistently on different platforms. macOS and Windows users may see extraneous changes relating to optional dependencies.### Backers
## Contributing
Contributions are welcome, but please follow these contributor guidelines outlined in [CONTRIBUTING.md](CONTRIBUTING.md).
## License
metamask is licensed under a [BSD 2-Clause License](LICENSE.md) and is copyright [Intoli, LLC](https://intoli.com).