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

@backpacker69/perpera

v1.0.2

Published

PeerAssets data audit protocol library

Downloads

11

Readme

perpera

usage

The browser bundle is built by running npm run bundle. The resulting dist/bundle.js file should be referenced using a <script> tag, which exposes the library interface through a global perpera object.

Available networks are accessible through the perpera.networks object: the keys are names and the values are instances of the perpera.Network class.

The central concept is the document.

const tag = 'foo';     // unique identifier of the document
const net = perpera.networks['peercoin'];     // the blockchain used to store the document's history
const doc = new perpera.Document(tag, net);
doc.sync().then(() => {
  // the document is now loaded from the underlying blockchain
});

After the promise returned by the sync() method is fulfilled, the document's transitions property may be inspected. It is an array of transitions, which make up the document's history. Refer to the src/model.ts file to understand the structure of these objects.

In order to modify a document, specially crafted transactions are inserted into the blockchain. Funds spent on these transactions are handled using instances of perpera.Spender.

const wif = '...';     // private key in WIF (wallet interchange format)
const spender = perpera.Spender.fromWIF(wif, 'peercoin');     // or perpera.Network instance
spender.sync().then(() => {
  // the UTXOs are now loaded into the spender instance
});

The document's content is updated by providing a collection of hash digests:

const hash = {
  'sha2-256': 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
};
doc.updateContent(hash, spender).then(() => {
  // the transactions have been sent to the network
});

This should only be performed after both the document and the spender have been synced. If the spender is not the current owner of the document, an error is thrown without broadcasting any transactions.

It is possible to attach URIs to a document:

doc.addUri('https://example.com/foo.txt', spender).then(() => {
  // the transactions have been sent to the network
});

If the given URI is too long to fit into a transaction, an error is thrown.