# Starknet \<\> EVM JSON-RPC adapter

**URL:** <https://community.starknet.io/t/starknet-evm-json-rpc-adapter/797>\
**Category:** Starknet Technical Development\
**Created:** [March 6, 2022, 7:39pm UTC](https://community.starknet.io/t/starknet-evm-json-rpc-adapter/797 "2022-03-06T19:39:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankitchiplunkar](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/ankitchiplunkar/32/270_2.png) [@ankitchiplunkar](https://community.starknet.io/u/ankitchiplunkar)\
**Post date:** [March 6, 2022, 7:39pm UTC](https://community.starknet.io/t/starknet-evm-json-rpc-adapter/797/1 "2022-03-06T19:39:55Z")

</div>

EVM JSON-RPC standard is used by several Wallets (Metamask) and data providers (Infura, Nansen). When data providers and wallets need to support a new EVM chain the only thing they need to do is change the json-rpc url and chain-id in all their requests.

Starknet JSON-RPC API closely [resembles](https://github.com/starkware-libs/starknet-specs/blob/master/starknet_vs_ethereum_node_apis.md#mapping-of-methods) that of the EVM json-rpc but is not exact, this adds developer overhead for all the wallets and data providers when integrating starknet into their services.

There are two services which rely on the JSON-RPC url:

1. **Wallets** : Supporting ethereum wallets is a different [discussion](https://community.starknet.io/t/support-web3-wallets-in-starknet/192/7), since starknet supports abstract wallets the closest equivalent to this in ethereum are contract wallets (Gnosis safe), which don’t work straight away with Metamask anyways.

2. **Data providers** : We can reduce the infra overhead of data providers by writing a wrapper service which:

This approach is similar to `Warp` developed by Nethermind. Where `Warp` maps between solidity \<\> cairo, this adapter will map between EVM \<\> Starknet JSON-RPC’s.

---

<div class="post-metadata">

**Author:** ![xJonathanLEI](https://dub1.discourse-cdn.com/flex005/user_avatar/community.starknet.io/xjonathanlei/32/93_2.png) [@xJonathanLEI](https://community.starknet.io/u/xJonathanLEI)\
**Post date:** [March 8, 2022, 4:20pm UTC](https://community.starknet.io/t/starknet-evm-json-rpc-adapter/797/2 "2022-03-08T16:20:07Z")

</div>

Might be of interest:

> [@Support Web3 wallets in StarkNet](https://community.starknet.io/t/support-web3-wallets-in-starknet/192):
>
> Support Web3 wallets in StarkNet Goal Support Web3 wallets in StarkNet (SN) without applying any changes to the wallets themselves. The wallet will be configured with a custom RPC endpoint and work as usual without being aware of SN. What are the gaps today? Signature - Today SN only supports a [native signature](https://www.google.com/url?q=https://docs.starkware.co/starkex-v3/crypto/stark-curve&sa=D&source=docs&ust=1639305282893000&usg=AOvVaw2zcSy12hvdhcPwRwIxmYKr) while Web3 wallets are signing using an Ethereum signature (SECP256k1 curve). EOA address - Ethereum uses an EOA address while SN uses account abstraction and the address is calcul…