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

divvy-lib-transactionparser

v0.7.1

Published

Parses transaction objects to a higher-level view

Downloads

15

Readme

divvy-lib-transactionparser

NPM

Parses transaction objects to a higher-level view.

parseBalanceChanges(metadata)

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

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

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

where BALANCECHANGE is a javascript object in the following format:

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

The keys in this object are the Divvy 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 XDV, where the counterparty is set to the empty string.

The CURRENCYSTRING is 'XDV' for XDV, 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:

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

where ORDERCHANGE is a javascript object with the following format:

{
    direction: 'buy' | 'sell',
    quantity: {
        currency: CURRENCYSTRING,
        counterparty: DIVVYADDRESS,  (omitted if currency is 'XDV')
        value: DECIMALSTRING
    },
    totalPrice: {
        currency: CURRENCYSTRING,
        counterparty: DIVVYADDRESS,  (omitted if currency is 'XDV')
        value: DECIMALSTRING
    },
    makerExchangeRate: DECIMALSTRING,
    sequence: SEQUENCE,
    status: ORDER_STATUS,
    expirationTime: EXPIRATION_TIME   (omitted if there is no expiration time)
}

The keys in this object are the Divvy 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.xdv.io/Ledger_Format#Offer) The CURRENCYSTRING is 'XDV' for XDV, a 3-letter ISO currency code, or a 160-bit hex string in the Currency format.

The makerExchangeRate field provides the original value of the ratio of what the taker pays over what the taker gets (also known as the "quality").

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 quantity and totalPrice represent the values of the order.
  • "partially-filled": The transaction modified the order (i.e., the order was partially consumed). The values of quantity and totalPrice represent the absolute value of change in value of the order.
  • "filled": The transaction consumed the order. The values of quantity and totalPrice represent the absolute value of change in value of the order.
  • "cancelled": The transaction canceled the order. The values of quantity and totalPrice are the values of the order prior to cancellation.

The EXPIRATION_TIME is an ISO 8601 timestamp representing the time at which the order expires (if there is an expiration time).

parseChannelChanges(metadata)

Takes a PayChannel metadata object and computes the changes to the payment channel caused by the transaction. It also returns additional details about the payment channel.

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

{
    status: 'created' | 'modified' | 'deleted',
    channelId: HEX_STRING,
    source: DIVVY_ADDRESS,
    destination: DIVVY_ADDRESS,
    channelAmountDrops: INTEGER_STRING,
    channelBalanceDrops: INTEGER_STRING,
    channelAmountChangeDrops?: INTEGER_STRING,
    channelBalanceChangeDrops?: INTEGER_STRING,
    previousTxnId?: TX_HASH_HEX_STRING
}
  • channelId indicates the Channel ID, which is necessary to sign claims.
  • source owns this payment channel. This comes from the sending address of the transaction that created the channel.
  • destination is the only address that can receive XDV from the channel. This comes from the Destination field of the transaction that created the channel.
  • channelAmountDrops is the amount of XDV drops that has been allocated to this channel. This includes XDV that has been paid to the destination address. This is initially set by the transaction that created the channel and can be increased if the source address sends a PaymentChannelFund transaction.
  • channelBalanceDrops is the total XDV, in drops, already paid out by the channel. The difference between this value and the Amount is how much XDV can still be paid tot he destination address with PaymentChannelClaim transactions. If the channel closes, the remaining difference is returned to the source address.
  • channelAmountChangeDrops is the change in the amount of XDV drops allocated to this channel. This is positive for a PaymentChannelFund transaction. Optional; may be omitted.
  • channelBalanceChangeDrops is the change in the amount of XDV drops already paid out by the channel. Optional; may be omitted.
  • previousTxnId is the previous transaction that affected this payment channel object. Optional; may be omitted.