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

@windingtree/org.id-directories

v1.0.0

Published

Directory and DirectoryIndex smart contracts of the Winding Tree protocol

Downloads

25

Readme

Build Status Coverage Status

Directory and DirectoryIndex Smart Contracts

Smart contracts of the Winding Tree ORG.ID protocol

Initial setup

npm i

Tests

npm run test
npm run test ./<path_to_test_file>.js

Tests coverage

npm run coverage

Linting

npm run lint

Generated docs

Contracts ABIs

Install the package

$ npm i @windingtree/org.id-directories

Import ABIs in the your JavaScript code

const {
  DirectoryContract,
  DirectoryIndexContract,
  DirectoryInterfaceContract,
  DirectoryIndexInterfaceContract
} = require('@windingtree/org.id-directories');

Directory deployment

All deployments, upgrades, transactions and calls can be handled using @windingtree/smart-contracts-tools:

$ npx tools --network ropsten cmd=deploy name=Directory from=0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959 initMethod=initialize initArgs=0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959,hotel,0xc8fD300bE7e4613bCa573ad820a6F1f0b915CfcA

The result will look like:

Deployment of the contract:  Directory
Version:  0.11.1
Owner address:  0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959
Initializing method:  initialize
Initializing arguments:  [ '0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959',
  'hotel',
  '0xc8fD300bE7e4613bCa573ad820a6F1f0b915CfcA' ]
Contract deployed at address:  0xF1Dd1412189Ed1757200B08C3293f7a8f08DCdac

Auto-generated deployment configuration will be saved on the ./openzeppelin repository folder and will look like:

{
  "version": "0.11.1",
  "contract": {
    "name": "Directory",
    "implementation": "0xAFaEbFC3785416E9259B2a6F0ab62B07F21f5470",
    "proxy": "0xF1Dd1412189Ed1757200B08C3293f7a8f08DCdac"
  },
  "owner": "0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959",
  "proxyAdmin": "0x418547B504D4e2c64dE6fCd37BeD1Fd740416558",
  "blockNumber": 7461013
}

The filename of the configuration file is formed according to mask: ./<NETWORK_NAME>-<CONTRACT_NAME>.json

development network has private name, so the name of file will be private-Directory.json

DirectoryIndex deployment

$ orgid-tools --network ropsten cmd=deploy name=DirectoryIndex from=0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959 initMethod=initialize initArgs=0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959

The result will look like:

Deployment of the contract:  DirectoryIndex
Version:  0.11.1
Owner address:  0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959
Initializing method:  initialize
Initializing arguments:  [ '0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959' ]
Contract deployed at address:  0xeD0f263e005e306de3F8Af9d74D1B3F8edEb33A3

Auto-generated deployment configuration will be saved in the file ./openzeppelin/private-DirectoryIndex.json

{
  "version": "0.11.1",
  "contract": {
    "name": "DirectoryIndex",
    "implementation": "0x3662823F4a5bb045365f3d7424Ea8c8B5Cf7Ab49",
    "proxy": "0xeD0f263e005e306de3F8Af9d74D1B3F8edEb33A3"
  },
  "owner": "0xA0B74BFE28223c9e08d6DBFa74B5bf4Da763f959",
  "proxyAdmin": "0x7702e5E832d772fDD38C5d01B47651e4DfA2bfa2",
  "blockNumber": 7461027
}