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

eip1167-spawner

v0.3.1

Published

Spawn EIP 1167 minimal proxies with an included initialization step during contract creation.

Downloads

18

Readme

Spawner (eip1167-spawner)

npm GitHub Build Status standard-readme compliant PRs Welcome

Spawn EIP 1167 minimal proxies with an included initialization step during contract creation.

These contracts demonstrate a technique for initializing and deploying EIP 1167 minimal proxies that point to designated logic contracts. Logic contracts should make an initialization function available that only allows it to be called during contract construction (i.e. assembly { if extcodesize(address) { revert(0, 0) } }).

Table of Contents

Install

To include Spawner as a dependency in your project:

$ yarn add eip1167-spawner

To install locally, you'll need Node.js 10+ and Yarn (or npm). To get everything set up:

$ git clone https://github.com/0age/Spawner.git
$ cd Spawner
$ yarn install
$ yarn build

Usage

Import Spawner and inherit it on a contract, then call _spawn with the desired logic contract and ABI-encoded initialization calldata:

pragma solidity ^0.5.0;

import "eip1167-spawner/contracts/Spawner.sol";
import "./MyLogicContract.sol";


contract MyFactory is Spawner {
  function spawnIt() public returns (address spawnedContract) {
    MyLogicContract logic = MyLogicContract(address(...));
    
    bytes memory myInitializationCalldata = abi.encodeWithSelector(
      logic.initialize.selector,
      "argumentOne",
      "argumentTwo"
    );
    
    spawnedContract =  _spawn(
      address(logicContract),
      myInitializationCalldata
    );
  }
}

You can also use _spawnCompact (for logic contracts with at least five leading zero bytes or ten zeroes), _spawnOldSchool (for deploying with CREATE rather than CREATE2), or _spawnCompactOldSchool. In addition, you can compute addresses spawned with CREATE2 ahead of time by using the supplied _computeNextAddress and _computeNextCompactAddress internal view functions.

Note: Spawner will be careful not to deploy to any address that already has code at it, but watch out - if the code that the minimal proxy points to can cause a SELFDESTRUCT, it is possible that Spawner may redeploy a minimal proxy to an address it has already deployed to in the past. This may or may not be the intended behavior, so feel free to put in extra safeguards if you're worried about this.

To run tests locally, start the testRPC, trigger the tests, and tear down the testRPC (you can do all of this at once via yarn all if you prefer):

$ yarn start
$ yarn test
$ yarn stop

Maintainers

@0age

Contribute

PRs accepted gladly - make sure the tests pass. (Changes to the contracts themselves should bump the version number and be marked as pre-release.)

License

MIT © 2019 0age