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

@requestnetwork/ethereum-storage

v0.36.1

Published

Request Network storage layer based on ethereum.

Downloads

2,188

Readme

@requestnetwork/ethereum-storage

@requestnetwork/ethereum-storage is a package part of the Request Network protocol. It is an implementation of the Storage layer of Request Network protocol that uses IPFS to immutably store the data and uses the Ethereum network to persist the IPFS hash of the data and make them permanently available to everyone.

To use Infura to connect to an Ethereum node, get an Infura token on infura.io and use as provider "NETWORK_YOU_WANT.infura.io/v3/YOUR_INFURA_TOKEN".

Installation

npm install @requestnetwork/ethereum-storage

Usage

import {
  EthereumStorage,
  EthereumTransactionSubmitter,
  IpfsStorage,
} from '@requestnetwork/ethereum-storage';

const ethereumStorage = new EthereumStorage({
  ipfsStorage: new IpfsStorage(),
  txSubmitter: new EthereumTransactionSubmitter(),
});

const data = 'Some data';

await ethereumStorage.append(data);

Gas Limit

The gas limit defined as safeGasPriceLimit in /src/config.ts can be overridden with the environment variable GAS_PRICE_DEFAULT.

Smart Contract

ethereum-storage uses smart contracts to store IPFS hashes.

The smart contracts can be downloaded in order to deploy them on a local environment:

git clone https://github.com/RequestNetwork/requestNetwork.git
cd requestNetwork/packages/smart-contracts
yarn install
yarn run build
yarn run ganache

And in another terminal:

yarn run deploy

There are 3 smart contracts:

  • RequestHashStorage allows to declare a hash NewHash(hash, submitter, feesParameters). Only a whitelisted contract can declare hashes.
  • RequestOpenHashSubmitter entry point to add hashes in RequestHashStorage. It gives the rules to get the right to submit hashes and collect the fees. This contract must be whitelisted in RequestHashStorage. The only condition for adding hash is to pay the fees.
  • StorageFeeCollector parent contract (not deployed) of RequestOpenHashSubmitter, computes the fees and send them to the burner.

Configuring the provider using Truffle and the development network

When deploying the smart contracts for development you can manually set the provider host and port via env variables:

TRUFFLE_GANACHE_HOST="host" TRUFFLE_GANACHE_PORT=1010 yarn run deploy

IPFS

In order to use the package in a test environment, IPFS should be running locally. Local IPFS listening on port 5001 is used by default by the ethereum-storage package.

Setup IPFS private network

Request uses an IPFS private network to allow all nodes to connect to each other directly, instead of having to navigate through the public IPFS network.

You may use the Request IPFS docker image to setup your IPFS node to the private network. Make sure that docker is installed on your system and then run the following command:

docker run -p 4001:4001 -p 5001:5001 requestnetwork/request-ipfs

This will pull the request-ipfs docker image and run it locally.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Read the contributing guide

License

MIT