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 🙏

© 2026 – Pkg Stats / Ryan Hefner

syscoinjs-lib

v1.0.268

Published

A transaction creation library interfacing with coin selection for Syscoin.

Readme

SyscoinJS (syscoinjs-lib)

Build Status NPM

code style: prettier

A javascript Syscoin library for node.js and browsers.

Released under the terms of the MIT LICENSE.

Should I use this in production?

If you are thinking of using the master branch of this library in production, stop. Master is not stable; it is our development branch, and only tagged releases may be classified as stable.

Can I trust this code?

Don't trust. Verify.

We recommend every user of this library and the syscoin ecosystem audit and verify any underlying code for its validity and suitability, including reviewing any and all of your project's dependencies.

Mistakes and bugs happen, but with your help in resolving and reporting issues, together we can produce open source software that is:

  • Easy to audit and verify,
  • Tested, with test coverage >95%,
  • Advanced and feature rich,
  • Standardized, using prettier and Node Buffer's throughout, and
  • Friendly, with a strong and helpful community, ready to answer questions.

Documentation

Presently, we do not have any formal documentation other than our examples, please ask for help if our examples aren't enough to guide you.

Installation

npm install syscoinjs-lib

Typically we support the Node Maintenance LTS version. If in doubt, see the .travis.yml for what versions are used by our continuous integration tests.

WARNING: We presently don't provide any tooling to verify that the release on npm matches GitHub. As such, you should verify anything downloaded by npm against your own verified copy.

Usage

Crypto is hard.

When working with private keys, the random number generator is fundamentally one of the most important parts of any software you write. For random number generation, we default to the randombytes module, which uses window.crypto.getRandomValues in the browser, or Node js' crypto.randomBytes, depending on your build system. Although this default is ~OK, there is no simple way to detect if the underlying RNG provided is good enough, or if it is catastrophically bad. You should always verify this yourself to your own standards.

This library uses bitcoinjs-lib with the ECC backend @bitcoinerlab/secp256k1, which uses RFC6979 to help prevent k re-use and exploitation. Unfortunately, this isn't a silver bullet. Often, Javascript itself is working against us by bypassing these counter-measures.

Problems in Buffer (UInt8Array), for example, can trivially result in catastrophic fund loss without any warning. It can do this through undermining your random number generation, accidentally producing a duplicate k value, sending Bitcoin to a malformed output script, or any of a million different ways. Running tests in your target environment is important and a recommended step to verify continuously.

Finally, adhere to best practice. We are not an authorative source of best practice, but, at the very least:

Browser

The recommended method of using syscoinjs-lib in your browser is through Browserify. If you're familiar with how to use browserify, ignore this and carry on, otherwise, it is recommended to read the tutorial at https://browserify.org/.

NOTE: We use Node Maintenance LTS features, if you need strict ES5, use --transform babelify in conjunction with your browserify step (using an es2015 preset).

WARNING: iOS devices have problems, use atleast [email protected] or greater, and enforce the test suites (for Buffer, and any other dependency) pass before use.

SyscoinJS exported functions

These are the functions available on SyscoinJS library with links to the code which has commenting on the function itself:

These are some supporting functions used to support the library like working with backend providers (Blockbook) and sanitizing data from the providers:

These are the HDSigner exported functions, HDSigner is used to manage creating addresses and sign transactions internally using your XPUB (HD wallets). BIP44/BIP84 are supported. P2WPKH, P2WSH, P2PKH, P2SH:

Examples

If you are looking to generate addresses, use WIFs or anything specific around crafting or doing blockchainy things not related to transaction creation, you may use bitcoinjs-lib and use the Syscoin network parameters (see utils.js for the exported syscoinNetworks parameters).

The below examples are implemented as example tests, they should be very easy to understand. Otherwise, pull requests are appreciated.

If you have a use case that you feel could be listed here, please ask for it!

New Features

Subtract Fee From Output

The createTransaction method now supports the subtractFeeFrom option in outputs. This allows you to subtract the transaction fee from specific outputs instead of requiring additional inputs for fees.

const outputs = [
  {
    address: 'sys1q6f2053q2fnlqpxrwrrqpkhnutwemu984p4vjzm',
    value: new BN(100000000), // 1 SYS
    subtractFeeFrom: true // Fee will be deducted from this output
  }
];

// Fee is automatically subtracted from outputs marked with subtractFeeFrom
const result = await syscoinjs.createTransaction(txOpts, changeAddress, outputs, feeRate);

When using multiple outputs with subtractFeeFrom, the fee is deducted sequentially:

const outputs = [
  {
    address: 'sys1q6f2053q2fnlqpxrwrrqpkhnutwemu984p4vjzm',
    value: new BN(50000000), // 0.5 SYS
    subtractFeeFrom: true // Fee deducted from here first
  },
  {
    address: 'sys1q9vza2e8x573nczrlzms0wvx3gsqjx7vavgkx0l',
    value: new BN(50000000), // 0.5 SYS
    subtractFeeFrom: true // Only used if first output can't cover full fee
  }
];

Enhanced Error Handling

All transaction creation methods now provide better error handling with structured error objects containing:

  • error: Boolean indicating an error occurred
  • code: Error code (e.g., 'INVALID_MEMO', 'INSUFFICIENT_FUNDS', etc.)
  • message: Human-readable error message
  • fee: Fee information when available
  • remainingFee: Remaining fee for subtractFeeFrom errors
  • shortfall: Amount short for insufficient funds errors
  • details: Additional error details when available
Error Codes
  • INSUFFICIENT_FUNDS: Not enough funds to complete the transaction
  • INVALID_MEMO: Memo field validation errors
  • INVALID_BLOB: Blob data validation errors for PoDA transactions
  • INVALID_OUTPUT_COUNT: When asset allocation outputs exceed limits
  • INVALID_ASSET_ALLOCATION: Asset allocation validation errors
  • INVALID_PARENT_NODES: SPV proof validation errors
  • INVALID_TX_VALUE: Transaction value validation errors
  • INVALID_RECEIPT_VALUE: Receipt validation errors
  • TRANSACTION_CREATION_FAILED: Generic failure during transaction creation

Example error handling:

try {
  const result = await syscoinjs.createTransaction(txOpts, changeAddress, outputs, feeRate);
  console.log('Transaction created successfully');
  console.log('Fee spent:', result.fee);
} catch (error) {
  console.error('Transaction creation failed:', error.message);
  
  // Access structured error data
  if (error.code === 'INSUFFICIENT_FUNDS' && error.shortfall) {
    console.error('Short by:', error.shortfall, 'satoshis');
  }
  
  if (error.remainingFee) {
    console.error('Remaining fee that could not be deducted:', error.remainingFee);
  }
}

Return Values

All transaction creation methods now return an object containing:

  • psbt: The created/signed PSBT object
  • fee: The transaction fee in satoshis

Example:

const result = await syscoinjs.createTransaction(txOpts, changeAddress, outputs, feeRate);
console.log('PSBT:', result.psbt);
console.log('Transaction fee:', result.fee, 'satoshis');

Contributing

See CONTRIBUTING.md.

Running the test suite

npm test
npm run-script coverage

Complementing Libraries

This library consumes syscointx-js for raw transaction serializing and deserializing, that library consumes coinselectsyscoin for the UTXO selection and transaction funding algorithms. Other supporting libraries are:

  • bn.js - BigNum in pure javascript.
  • bitcoinjs-lib - A javascript Bitcoin library for node.js and browsers. Configurable with Syscoin network settings to work with Syscoin addresses and message signing.
  • bitcoin-ops - A javascript Bitcoin OP code library for referencing script OP codes for Bitcoin's script
  • varuint-bitcoin - encode/decode number as bitcoin variable length integer
  • BIP84 - P2WPKH/P2WSH HD wallet derivation library for BECH32 addresses
  • axios - Promise based HTTP client for the browser and node.js. Used for backend communication with a Blockbook API
  • eth-object - Ethereum Trie / LevelDB data from hex, buffers and rpc.
  • eth-proof - Generalized merkle-patricia-proof module that supports ethereum state proofs. Used for Eth SPV proofs.
  • rlp - Recursive Length Prefix Encoding for node.js.
  • web3 - Ethereum JavaScript API which connects to the Generic JSON-RPC spec.

LICENSE MIT