Reading Twine Data

Use the javascript library to access twine data from an HTTP api

We are going to walk through a basic way of interacting with a Twine HTTP api. For this example we'll use the api hosted by the CURBy project.

Prerequisites

You need a javascript runtime such as node.js, or bun to begin.

Create a project

Follow your package manager's instructions for creating a project. For node.js this looks like:

mkdir hello-twine && cd hello-twine
npm init

This tutorial will use ES Module syntax. To enable it we need to edit the package.json file and set the module type as shown on line 6:

package.json

{
  "name": "hello-twine",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

Install twine libraries

To read twine data we need the twine-core package and to interact with an HTTP api we need the twine-http-store package.

npm install @twine-protocol/twine-core \
    @twine-protocol/twine-http-store

Code

Open up the index.js file in a code editor and input the following:

index.js

import { HttpStore } from '@twine-protocol/twine-http-store'

const API_URL = 'https://random.colorado.edu/api'
const store = new HttpStore(API_URL)

async function listChains(){
  console.log(`Found the following twine chains at ${API_URL}`)
  for await (const chain of store.chains()){
    console.log(`  > ${chain.cid}`)
  }
}

listChains()

Explanation:

• Line 1: imports the HttpStore

• Line 5: Creates an instance of the store and points it to the API

• Line 8: Loops through the AsyncIterator returned by the call to .chains()

• Line 9: Prints the CID of each chain

By default, all twine data is verified upon retrieval. So if this succeeds without error, then both the hashes and signatures are valid.

Now you can run this script and see the output.

node index.js

Let's now modify the code to fetch the last 10 pulses on a specific chain. We'll use node.js commandline arguments to specify the chain.

We create a new function to fetch the last n pulses from a specified chain:

async function fetchPulses(chainCid, count = 10){
  console.log(`Fetching the last ${count} pulses from chain ${chainCid}`)
  for await (const pulse of store.pulses(chainCid)){
    console.log(`\npulse ${pulse.cid}:`)
    console.log(JSON.stringify(pulse.value.content.payload, null, 2))
    count--
    if(count <= 0) break
  }
}

Explanation:

• Line 1: declares a function to fetch a specified number of pulses from a chain. With a default of 10 pulses

• Line 3: Loops through the AsyncIterable of pulses on the chain

• Line 6 & 7: keep track of the number of listed pulses and breaks out of the loop

Notice that on line 5 we access the .value.content.payload property. The .value property holds the twine data and the .content.payload is the pulse payload as a javascript object.

All that is left is to detect when a command line argument is present:

if (process.argv.length === 2){
  listChains()
} else if (process.argv.length === 3){
  fetchPulses(process.argv[2])
}

Now we can again run our script:

node index.js "<PUT CHAIN CID HERE>"

And you should see a list of pulse CIDs with their payloads.

Whole script

import { HttpStore } from '@twine-protocol/twine-http-store'

const API_URL = 'https://random.colorado.edu/api'
const store = new HttpStore(API_URL)

async function listChains(){
  console.log(`Found the following twine chains at ${API_URL}`)
  for await (const chain of store.chains()){
    console.log(`  > ${chain.cid}`)
  }
}

async function fetchPulses(chainCid, count = 10){
  console.log(`Fetching the last ${count} pulses from chain ${chainCid}`)
  for await (const pulse of store.pulses(chainCid)){
    console.log(`\npulse ${pulse.cid}:`)
    console.log(JSON.stringify(pulse.value.content.payload, null, 2))
    count--
    if(count <= 0) break
  }
}

if (process.argv.length === 2){
  listChains()
} else if (process.argv.length === 3){
  fetchPulses(process.argv[2])
}