Package Exports

jswaxdispatcher
jswaxdispatcher/index.js

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 (jswaxdispatcher) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

jswaxdispatcher

Quickly integrate submitting WAX blockchain transactions in NodeJS projects

Installation

npm i jswaxdispatcher

Usage

const { jswaxdispatcher } = require('jswaxdispatcher')
const projectWallet = new jswaxdispatcher(privateKey, walletAddress, permission, customSignatureProvider)
//permission & customSignatureProvider optional but recommended.
//DEFAULTS permission = 'active', customSignatureProvider = JsSignatureProvider from eosjs

projectWallet.sendWax(quantity, recipient, memo) //memo optional
    .then((res) => {console.log(res)});

Functions

`.sendWax( quantity, recipient , memo )`

Send an address WAX with optional memo

`.sendTokens( quantity, symbol, tokenContractAcct, recipient, memo )`

Send an address a specified token with optional memo

`.sendAssets( assetIds[], recipient, memo )`

Send an address NFTs by specified asset_ids with optional memo

`.burnAssets( assetIds[] )`

Burn NFTs by specified asset_ids

`.mintFromTemplate( collectionName, schemaName, templateId, recipient, amount )`

Mint NFTs by specified template #, wallet must be authorized with the collection

WARNING

The default customSignatureProvider is JsSignatureProvider included with eosjs.

"Using the JsSignatureProvider in the browser is not secure and should only be used for development purposes. Use a secure vault outside of the context of the webpage to ensure security when signing transactions in production" ~eosjs documentation