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

espend-lib-transactionparser

v0.3.1

Published

Parses transaction objects to a higher-level view

Downloads

3

Readme

espend-lib-transactionparser

NPM

Parses transaction objects to a higher-level view.

parseBalanceChanges(metadata)

Takes a transaction metadata object (as returned by a espend-lib response) and computes the balance changes that were caused by that transaction.

The return value is a javascript object in the following format:

{ RIPPLEADDRESS: [BALANCECHANGE, ...], ... }

where BALANCECHANGE is a javascript object in the following format:

{
    counterparty: RIPPLEADDRESS,
    currency: CURRENCYSTRING,
    value: DECIMALSTRING
}

The keys in this object are the Ripple addresses whose balances have changed and the values are arrays of objects that represent the balance changes. Each balance change has a counterparty, which is the opposite party on the trustline, except for XEC, where the counterparty is set to the empty string.

The CURRENCYSTRING is 'XEC' for XEC, a 3-letter ISO currency code, or a 160-bit hex string in the Currency format.

parseOrderBookChanges(metadata)

Takes a transaction metadata object and computes the changes in the order book caused by the transaction. Changes in the orderbook are analogous to changes in Offer entries in the ledger.

The return value is a javascript object in the following format:

{ RIPPLEADDRESS: [ORDERCHANGE, ...], ... }

where ORDERCHANGE is a javascript object with the following format:

{
    taker_pays: {
        currency: CURRENCYSTRING,
        counterparty: RIPPLEADDRESS,
        value: DECIMALSTRING
    },
    taker_gets: {
        currency: CURRENCYSTRING,
        counterparty: RIPPLEADDRESS,
        value: DECIMALSTRING
    },
    sequence: SEQUENCE,
    status: ORDER_STATUS
}

The keys in this object are the Ripple addresses whose orders have changed and the values are arrays of objects that represent the order changes.

The SEQUENCE is the sequence number of the transaction that created that create the orderbook change. (See: https://wiki.ripple.com/Ledger_Format#Offer) The CURRENCYSTRING is 'XEC' for XEC, a 3-letter ISO currency code, or a 160-bit hex string in the Currency format.

The ORDER_STATUS is a string that represents the status of the order in the ledger:

  • "created": The transaction created the order. The values of taker_pays and taker_gets represent the values of the order.
  • "open": The transaction modified the order (i.e., the order was partially consumed). The values of taker_pays and taker_gets represent the change in value of the order.
  • "closed": The transaction consumed the order. The values of taker_pays and taker_gets represent the change in value of the order.
  • "canceled": The transaction canceled the order. The values of taker_pays and taker_gets is zero.