JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 2171
  • Score
    100M100P100Q173179F
  • License MIT

IPRS Record implementation

Package Exports

  • libp2p-record

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (libp2p-record) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

node-libp2p-record

[ Build Status](https://travis-ci.org/diasdavid/node-lib2p-record) Dependency Status js-standard-style

Node.js libp2p record object follows specification(IPRS) implementation

Description

Usage

Example record

// Record is a IPLD object
{
  '@context': {
    mlink: 'http://merkle-link'
  },
  scheme: {
    mlink: <hash to validity scheme or identifier for hard coded validity scheme>
  },
  expires: <data>, // datetime at which record expires
  value: <data>, // the data that this Record Stores
}

Record types

A record type should be identified by its validity scheme and a record validity scheme should be a MerkleDAG object containing its validity checking rules, however, for simplicity, we have developed 4 types of records, in which their validity schemes are hardcoded in this module. To identify which validity scheme to use, we use a enum:

  • a - signed, valid within a datetime range
  • b - signed, expiring after a Time-To-Live
  • c - signed, based on ancestry (chain)
  • d - signed, with cryptographic freshness

Reference: https://github.com/ipfs/specs/tree/master/records#example-record-types