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

zerodash

v0.2.2

Published

Library for utilizing Graffiti Feed with Personal Storage - FIP 62

Downloads

3

Readme

Zero Dash

This library facilitates to use Graffiti Feeds on Ethereum Swarm.

graffiti-feed-chart

Install

npm install zerodash --save

Usage

The library provides InformationSignal and PersonalStorageSignal classes that read/write GraffitiFeed according to the consensus and other configuration parameters.

The consensus consists of an arbitrary id and an assert function that validates records either in graffiti feed or in the personal storage, respectively.

const id = 'SampleDapp:v1'

export interface SampleDappRecord {
  /** text of the message */
  text: string
  /** creation time of the comment */
  timestamp: number
}

function assertRecord(value: unknown): asserts value is SampleDappRecord {
  if (
    value !== null &&
    typeof value === 'object' &&
    Object.keys(value).includes('text') &&
    Object.keys(value).includes('timestamp')
  ) {
    return
  }
  
  throw new Error('The given value is not a valid personal storage record')
}

With that, the rules have been created for a specific Graffit Feed.

The only architectural decision remaining is whether the information is backed up by the personal storage of the user or not. Both are supported by the library, but the Personal Storage Signal interface is recommended to use in favor of the proper aggregation.

Personal Storage Signal

For write operations, the personalStorageSigner and the postageBatchId must be set.

import { PersonalStorageSignal } from 'zerodash'
import { Wallet } from 'ethers'

const personalStorageWallet = Wallet.createRandom()
const beeUrl = 'http://localhost:1633' // Bee API URL to connect p2p storage network
const postageBatchId = '0000000000000000000000000000000000000000000000000000000000000000' // 64 chars length Bee Postage Batch Id
const resourceId = 'demo' // any string/content hash that represents the resource to which the Personal Storage record will be associated. 

const personalStorageSignal = new PersonalStorageSignal(beeUrl, {
  personalStorageSigner: personalStorageWallet.privateKey.slice(2),
  postageBatchId,
  consensus: {
    id,
    assertRecord,
  },
})

// write message to personal storage and advertise personal storage area in graffiti feed
await personalStorageSignal.write({ text: 'Hello World!', timestamp: 1675202470222 }, { resourceId })

The read operation gives back an async generator on the consensual graffiti feed that fetches all advertised Personal Storage identifiers and prepares their Personal Storage readers.

// ...
// read the graffiti feed and all personal storage records
for await (const personalStorage of personalStorageSignal.read({ resourceId: 'puffin' })) {
  console.log('Personal Storage address in the Graffiti Feed', personalStorage.iaasIdentifier)
  console.log('Personal Storage position in the Graffiti Feed', personalStorage.index)
  for await (const personalStorageRecord of personalStorage.iter) {
    console.log(/content hash
      'Personal Storage record in the Graffiti Feed',
      personalStorageRecord.index,
      personalStorageRecord.record,
    )
  }
}

Another examples can be found in the integration tests

Information Signal

For write operations, the postageBatchId must be set.

import { InformationSignal } from 'zerodash'

const beeUrl = 'http://localhost:1633' // Bee API URL to connect p2p storage network
const postageBatchId = '0000000000000000000000000000000000000000000000000000000000000000' // 64 chars length Bee Postage Batch Id
const resourceId = 'demo' // any string/content hash that represents the resource to which the Personal Storage record will be associated. 

const informationSignal = new InformationSignal(beeUrl, {
  postageBatchId,
  consensus: {
    id,
    assertRecord,
  },
})

// write message to personal storage and advertise personal storage area in graffiti feed
await informationSignal.write({ text: 'Hello there!', timestamp: 1676840715471 }, { resourceId })

The read operation gives back an async generator on the consensual graffiti feed that fetches all advertised infromation about the resourceId.

// ...
// read the graffiti feed and all personal storage records
for await (const personalStorage of informationSignal.read({ resourceId: 'puffin' })) {
  console.log('Record in the Graffiti Feed', personalStorage.index)
  console.log('Record position in the Graffiti Feed', personalStorage.index)
}

Another examples can be found in the integration tests

Compilation

In order to compile code run

npm run compile

You can find the resulted code under the dist folder.

For types compilation, run

npm run compile:types

Testing

The testing needs running Bee client node for integration testing. You must set BEE_POSTAGE environment variable with a valid Postage batch.

In order to test on different node than http://localhost:1633, set BEE_DEBUG_API_URL environment variable as well.

To run test execute

npm run test