npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

detect-evm-proxy

v1.0.1

Published

Detect proxy contract kinds and their target addresses using an EIP-1193 compatible JSON-RPC request function

Downloads

7

Readme

detect-evm-proxy

Detect proxy contracts and their target addresses using an EIP-1193 compatible JSON-RPC request function

This package offers a utility function for checking if a smart contract at a given address implements one of the known proxy patterns. It detects the following kinds of proxies:

  • EIP-1167 Minimal Proxy Contract
  • EIP-1967 Transparent Proxy Pattern
  • EIP-897 Delegate Proxy Pattern
  • EIP-1822 Universal Upgradeable Proxy Standard
  • OpenZeppelin Proxy Pattern
  • Gnosis Safe Proxy Contract

Installation

This module is distributed via npm. For adding it to your project, run:

npm install --save detect-evm-proxy

To install it using yarn, run:

yarn add detect-evm-proxy

How to use

The function requires an EIP-1193 compatible request function that it uses to make JSON-RPC requests to run a set of checks against the given address. It returns a promise that resolves to the proxy target address, i.e., the address of the contract implementing the logic. The promise resolves to null if no proxy can be detected.

Ethers with an adapter function

Using Infura:

import { InfuraProvider } from "@ethersproject/providers";
import detectProxyTarget from "detect-evm-proxy";

const infuraProvider = new InfuraProvider(1, process.env.INFURA_API_KEY);
const requestFunc = ({ method, params }) => infuraProvider.send(method, params);

const target = await detectProxyTarget(
  "0xA7AeFeaD2F25972D80516628417ac46b3F2604Af",
  requestFunc
);

// logs {contractAddress: "0x4bd844F72A8edD323056130A86FC624D0dbcF5b0", kind: "EIP-1967 Transparent Proxy Pattern"}
console.log(target);

Using ankr:

import { JsonRpcProvider } from "@ethersproject/providers";
import detectProxyTarget from "detect-evm-proxy";

const jsonRpcProvider = new JsonRpcProvider("https://rpc.ankr.com/eth");
const requestFunc: EIP1193ProviderRequestFunc = ({ method, params }) =>
  jsonRpcProvider.send(method, params);

const target = await detectProxyTarget(
  "0xA7AeFeaD2F25972D80516628417ac46b3F2604Af",
  requestFunc
);

// logs {contractAddress: "0x4bd844F72A8edD323056130A86FC624D0dbcF5b0", kind: "EIP-1967 Transparent Proxy Pattern"}
console.log(target);

Web3 with an EIP1193 provider

Web3.js doesn't have a way to export an EIP1193 provider, so you need to ensure that the underlying provider you use is EIP1193 compatible. Most Ethereum-supported browsers like MetaMask and TrustWallet have an EIP-1193 compliant provider. Otherwise, you can use providers like eip1193-provider.

import detectProxyTarget from "detect-evm-proxy";
import Web3 from "web3";

const web3 = new Web3(Web3.givenProvider || "ws://localhost:8545");

const target = await detectProxyTarget(
  "0xA7AeFeaD2F25972D80516628417ac46b3F2604Af",
  web3.currentProvider.request
);

// logs {contractAddress: "0x4bd844F72A8edD323056130A86FC624D0dbcF5b0", kind: "EIP-1967 Transparent Proxy Pattern"}
console.log(target);

API


detectProxyTarget(
  address: string,
  jsonRpcRequest: EIP1193ProviderRequestFunc,
  blockTag?: BlockTag
): Promise<DetectProxyTarget | null>

// where
DetectProxyTarget: {
  contractAddress: string,
  kind: ProxyKind, // ProxyKind: string
}

Arguments

  • address (string): The address of the proxy contract
  • jsonRpcRequest (EIP1193ProviderRequestFunc): A JSON-RPC request function, compatible with EIP-1193 ((method: string, params: any[]) => Promise<any>)
  • blockTag (optional: BlockTag): "earliest", "latest", "pending" or hex block number, default is "latest"

Returns

The function returns a promise that will generally resolve to either DetectProxyTarget(the detected target contract address (checksummed) and its kind) or null if it couldn't detect one.

Note

Directly modified from evm-proxy-detection