Support Cron Amendment (#32)

Co-authored-by: Chenna Keshava B S <21219765+ckeshava@users.noreply.github.com>
Co-authored-by: Denis Angell <dangell@transia.co>

.ci-config/getNewAmendments.js

@@ -0,0 +1,56 @@
+const xahau = require("xahau");
+const fs = require("fs");
+const path = require("path");
+
+const filePath = path.resolve(__dirname, "./rippled.cfg");
+const existingConfig = fs.readFileSync(filePath, "utf-8");
+
+const networkToEmulate = "wss://s.devnet.rippletest.net:51233/";
+
+const amendmentsToIgnore = [
+  "86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90", // CryptoConditionsSuite is obsolete
+];
+
+async function main() {
+  const client = new xahau.Client(networkToEmulate);
+  await client.connect();
+
+  // Looks up what amendments have been enabled via their hash
+  const request = {
+    command: "ledger_entry",
+    index: "7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4",
+    ledger_index: "validated",
+  };
+  const response = await client.request(request);
+
+  const amendments = response.result.node.Amendments;
+
+  const newAmendments = [];
+  amendments.forEach((amendment) => {
+    if (
+      !existingConfig.includes(amendment) &&
+      !amendmentsToIgnore.includes(amendment)
+    ) {
+      newAmendments.push(amendment);
+    }
+  });
+
+  if (newAmendments.length > 0) {
+    console.log(
+      "New Amendment Hashes - Look up their names on https://xrpl.org/known-amendments.html"
+    );
+    newAmendments.forEach((amendment) => {
+      console.log(amendment);
+    });
+  } else {
+    console.log(
+      `No new amendments to add!
+Looking at network: ${networkToEmulate}.
+Path to config: ${filePath}`
+    );
+  }
+
+  await client.disconnect();
+}
+
+main().catch((error) => console.log(error));

.ci-config/xahaud.cfg

@@ -0,0 +1,169 @@
+[server]
+port_rpc_admin_local
+port_ws_public
+port_ws_admin_local
+
+# port_peer
+# port_ws_admin_local
+# ssl_key = /etc/ssl/private/server.key
+# ssl_cert = /etc/ssl/certs/server.crt
+
+# IPs must be 0.0.0.0 instead of 127.0.0.1 to be accessed outside the docker container
+
+[port_rpc_admin_local]
+port = 5005
+ip = 0.0.0.0
+admin = 0.0.0.0
+protocol = http
+
+[port_ws_public]
+port = 80
+ip = 0.0.0.0
+protocol = ws
+
+# [port_peer]
+# port = 51235
+# ip = 0.0.0.0
+# protocol = peer
+
+[port_ws_admin_local]
+port = 6006
+ip = 0.0.0.0
+admin = 0.0.0.0
+protocol = ws
+
+[node_size]
+small
+
+# tiny
+# small
+# medium
+# large
+# huge
+
+[node_db]
+type=NuDB
+path=/var/lib/rippled/db/nudb
+advisory_delete=0
+
+# How many ledgers do we want to keep (history)?
+# Integer value that defines the number of ledgers
+# between online deletion events
+online_delete=256
+
+[ledger_history]
+# How many ledgers do we want to keep (history)?
+# Integer value (ledger count)
+# or (if you have lots of TB SSD storage): 'full'
+256
+
+[database_path]
+/var/lib/rippled/db
+
+[debug_logfile]
+/var/log/rippled/debug.log
+
+
+[ips]
+r.ripple.com 51235
+
+# [validators_file]
+# validators.txt
+
+[rpc_startup]
+{ "command": "log_level", "severity": "info" }
+
+# severity (order: lots of information .. only errors)
+# debug
+# info
+# warn
+# error
+# fatal
+
+[ssl_verify]
+1
+
+# The [features] stanza does not currently work for standalone mode: https://github.com/XRPLF/xrpl-dev-portal/issues/1762#issuecomment-1441252450
+
+
+# In order to enable an amendment which by default would vote "No", you must include its amendment id and name here.
+# To add amendments specifically from the latest releases of rippled:
+# 1. Go to https://xrpl.org/known-amendments.html
+# 2. Find the first amendment in the latest releases of rippled which are not already in the list below
+# 3. Click on each amendment to get their Amendment ID and name to add to this list manually.
+#    You will likely update the list with all amendments from a new release of rippled all at once.
+
+# To get the list of amendments on a network (e.g. devnet) follow the steps in xahau.js's CONTRIBUTING.md for "Updating the Docker container".
+# https://github.com/Xahau/xahau.js/blob/main/CONTRIBUTING.md
+# (Running the script `getNewAmendments.js` should help you identify any new amendments that should be added.)
+#
+# Note: The version of rippled you use this config with must have an implementation for the amendments you attempt to enable or it will crash.
+# If you need the version of rippled to be more up to date, you may need to make a comment on this repo: https://github.com/WietseWind/docker-rippled
+
+[features]
+# Amendments
+NegativeUNL
+fixRemoveNFTokenAutoTrustLine
+NonFungibleTokensV1
+CheckCashMakesTrustLine
+fixRmSmallIncreasedQOffers
+fixSTAmountCanonicalize
+FlowSortStrands
+TicketBatch
+fixQualityUpperBound
+FlowCross
+HardenedValidations
+DepositPreauth
+MultiSignReserve
+fix1623
+fix1513
+RequireFullyCanonicalSig
+fix1543
+fix1781
+fixCheckThreading
+fix1515
+CryptoConditionsSuite
+fixPayChanRecipientOwnerDir
+fix1578
+fix1571
+fixAmendmentMajorityCalc
+fixTakerDryOfferRemoval
+fixMasterKeyAsRegularKey
+Flow
+DeletableAccounts
+DepositAuth
+Checks
+NonFungibleTokensV1_1
+DisallowIncoming
+fixNonFungibleTokensV1_2
+fixUniversalNumber
+ImmediateOfferKilled
+XRPFees
+ExpandedSignerList
+fixNFTokenRemint
+# Additional Amendments
+BalanceRewards
+Hooks
+HooksUpdate1
+Import
+Remit
+URIToken
+XahauGenesis
+ZeroB2M
+fix240819
+fix240911
+fixFloatDivide
+fixNFTokenDirV1
+fixNFTokenNegOffer
+fixNSDelete
+fixPageCap
+fixReduceImport
+fixXahauV1
+fixXahauV2
+fixXahauV3
+PaychanAndEscrowForTokens
+DeepFreeze
+Clawback
+
+[network_id]
+21337

.coderabbit.yaml

@@ -0,0 +1,28 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+language: "en-US"
+reviews:
+  # Set the profile for reviews. Assertive profile yields more feedback, that may be considered nitpicky.
+  profile: "chill"
+  # Approve the review once CodeRabbit's comments are resolved. Note: In GitLab, all discussions must be resolved.
+  request_changes_workflow: false
+  # Generate a high level summary of the changes in the PR/MR description.
+  high_level_summary: false
+  # Generate a poem in the walkthrough comment.
+  poem: true
+  # Post review details on each review. Additionally, post a review status when a review is skipped in certain cases.
+  review_status: true
+  # Generate walkthrough in a markdown collapsible section.
+  collapse_walkthrough: false
+  # Abort the in-progress review if the pull request is closed or merged.
+  abort_on_close: true
+  auto_review:
+    # Automatic Review | Automatic code review
+    enabled: true
+    # Review draft PRs/MRs.
+    drafts: false
+    # Ignore reviewing if the title of the pull request contains any of these keywords (case-insensitive).
+    ignore_title_keywords:
+      - build(
+chat:
+  # Enable the bot to reply automatically without requiring the user to tag it.
+  auto_reply: true

.eslintrc.json

@@ -1,26 +0,0 @@
-{
-  "env": {
-    "browser": true,
-    "es6": true,
-    "node": true,
-    "mocha": true
-  },
-  "extends": [
-    "eslint:recommended"
-  ],
-  "parser": "@typescript-eslint/parser",
-  "parserOptions": {
-    "ecmaVersion": 2018,
-    "sourceType": "module"
-  },
-  "plugins": [
-    "@typescript-eslint"
-  ],
-  "rules": {
-    "no-useless-constructor": 0,
-    "no-unused-vars": 0,
-    "no-prototype-builtins": 0,
-    "require-atomic-updates": 0,
-    "no-dupe-class-members": 0
-  }
-}

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: weekly
+    time: "15:00"
+  open-pull-requests-limit: 10

.github/pull_request_template.md

@@ -0,0 +1,48 @@
+## High Level Overview of Change
+
+<!--
+Please include a summary/list of the changes.
+If too broad, please consider splitting into multiple PRs.
+If a relevant Asana task, please link it here.
+-->
+
+### Context of Change
+
+<!--
+Please include the context of a change.
+If a bug fix, when was the bug introduced? What was the behavior?
+If a new feature, why was this architecture chosen? What were the alternatives?
+If a refactor, how is this better than the previous implementation?
+
+If there is a design document for this feature, please link it here.
+-->
+
+### Type of Change
+
+<!--
+Please check relevant options, delete irrelevant ones.
+-->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Refactor (non-breaking change that only restructures code)
+- [ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
+- [ ] Documentation Updates
+- [ ] Release
+
+### Did you update HISTORY.md?
+
+- [ ] Yes
+- [ ] No, this change does not impact library users
+
+## Test Plan
+
+<!--
+Please describe the tests that you ran to verify your changes and provide instructions so that others can reproduce.
+-->
+
+<!--
+## Future Tasks
+For future tasks related to PR.
+-->

.github/workflows/codeql-analysis.yml

@@ -0,0 +1,65 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: "CodeQL"
+
+on:
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches: [main]
+  schedule:
+    - cron: "44 5 * * 6"
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ["javascript"]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
+        # Learn more:
+        # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      # Initializes the CodeQL tools for scanning.
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v2
+        with:
+          languages: ${{ matrix.language }}
+          # If you wish to specify custom queries, you can do so here or in a config file.
+          # By default, queries listed here will override any specified in a config file.
+          # Prefix the list here with "+" to use these queries and those in the config file.
+          # queries: ./path/to/local/query, your-org/your-repo/queries@main
+
+      # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+      # If this step fails, then you should remove it and run the build manually (see below)
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@v2
+
+      # ℹ️ Command-line programs to run using the OS shell.
+      # 📚 https://git.io/JvXDl
+
+      # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
+      #    and modify them (or add more) to build your code if your project
+      #    uses a compiled language
+
+      #- run: |
+      #   make bootstrap
+      #   make release
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v2

.github/workflows/nodejs.yml

@@ -0,0 +1,200 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Node.js CI
+
+env:
+  XAHAUD_DOCKER_IMAGE: xahauci/xahaud:2025.2.6
+
+on:
+  push:
+    branches: [main-xahau, 1.x]
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build-and-lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    strategy:
+      matrix:
+        node-version: [18.x]
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Setup npm version 9
+        run: |
+          npm i -g npm@9 --registry=https://registry.npmjs.org
+
+      - name: Cache node modules
+        id: cache-nodemodules
+        uses: actions/cache@v3
+        env:
+          cache-name: cache-node-modules
+        with:
+          # caching node_modules
+          path: |
+            node_modules
+            */*/node_modules
+          key: ${{ runner.os }}-deps-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-deps-${{ matrix.node-version }}-
+            ${{ runner.os }}-deps-
+
+      - name: Install Dependencies
+        if: steps.cache-nodemodules.outputs.cache-hit != 'true'
+        run: npm ci
+
+      - run: npm run build
+      - run: npm run lint
+
+  unit:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x]
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Setup npm version 9
+        run: |
+          npm i -g npm@9 --registry=https://registry.npmjs.org
+
+      - name: Cache node modules
+        id: cache-nodemodules
+        uses: actions/cache@v3
+        env:
+          cache-name: cache-node-modules
+        with:
+          # caching node_modules
+          path: |
+            node_modules
+            */*/node_modules
+          key: ${{ runner.os }}-deps-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-deps-${{ matrix.node-version }}-
+            ${{ runner.os }}-deps-
+
+      - name: Install Dependencies
+        if: steps.cache-nodemodules.outputs.cache-hit != 'true'
+        run: npm ci
+
+      - run: npm run build
+      - run: npm test
+
+  integration:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    strategy:
+      matrix:
+        node-version: [18.x, 20.x]
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Run docker in background
+        run: |
+          docker run --detach --rm --name xahaud-service -p 6006:6006 --volume "${{ github.workspace }}/.ci-config/":"/opt/xahau/etc/" --health-cmd="wget localhost:6006 || exit 1" --health-interval=5s --health-retries=10 --health-timeout=2s --env GITHUB_ACTIONS=true --env CI=true ${{ env.XAHAUD_DOCKER_IMAGE }} /opt/xahau/bin/xahaud -a --conf /opt/xahau/etc/xahaud.cfg
+
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Setup npm version 9
+        run: |
+          npm i -g npm@9 --registry=https://registry.npmjs.org
+
+      - name: Cache node modules
+        id: cache-nodemodules
+        uses: actions/cache@v3
+        env:
+          cache-name: cache-node-modules
+        with:
+          # caching node_modules
+          path: |
+            node_modules
+            */*/node_modules
+          key: ${{ runner.os }}-deps-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-deps-${{ matrix.node-version }}-
+            ${{ runner.os }}-deps-
+
+      - name: Install Dependencies
+        if: steps.cache-nodemodules.outputs.cache-hit != 'true'
+        run: npm ci
+
+      - run: npm run build
+
+      - name: Run integration test
+        run: npm run test:integration
+
+      - name: Stop docker container
+        if: always()
+        run: docker stop xahaud-service
+
+  browser:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    strategy:
+      matrix:
+        node-version: [18.x]
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Use Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+
+      - name: Run docker in background
+        run: |
+          docker run --detach --rm --name xahaud-service -p 6006:6006 --volume "${{ github.workspace }}/.ci-config/":"/opt/xahau/etc/" --health-cmd="wget localhost:6006 || exit 1" --health-interval=5s --health-retries=10 --health-timeout=2s --env GITHUB_ACTIONS=true --env CI=true ${{ env.XAHAUD_DOCKER_IMAGE }} /opt/xahau/bin/xahaud -a --conf /opt/xahau/etc/xahaud.cfg
+
+      - name: Setup npm version 9
+        run: |
+          npm i -g npm@9 --registry=https://registry.npmjs.org
+
+      - name: Cache node modules
+        id: cache-nodemodules
+        uses: actions/cache@v3
+        env:
+          cache-name: cache-node-modules
+        with:
+          # caching node_modules
+          path: |
+            node_modules
+            */*/node_modules
+          key: ${{ runner.os }}-deps-${{ matrix.node-version }}-${{ hashFiles('**/package-lock.json') }}
+          restore-keys: |
+            ${{ runner.os }}-deps-${{ matrix.node-version }}-
+            ${{ runner.os }}-deps-
+
+      - name: Install Dependencies
+        if: steps.cache-nodemodules.outputs.cache-hit != 'true'
+        run: npm ci
+
+      - run: npm run build
+
+      - name: Run integration test
+        run: npm run test:browser
+
+      - name: Stop docker container
+        if: always()
+        run: docker stop xahaud-service

.gitignore

@@ -1,7 +1,7 @@
 # .gitignore
 
-# Ignore package locks other than Yarn.
-package-lock.json
+# Ignore package locks other than npm.
+yarn.lock
 npm-shrinkwrap.json
 
 # Ignore vim swap files.
@@ -22,6 +22,7 @@ npm-shrinkwrap.json
 # Ignore object files.
 *.o
 build/
+coverage/
 tags
 bin/rippled
 Debug/*.*
@@ -39,8 +40,6 @@ db/*.db
 db/*.db-*
 
 # Ignore customized configs
-rippled.cfg
-validators.txt
 test/config.js
 
 # Ignore coverage files
@@ -51,6 +50,7 @@ test/config.js
 
 # Ignore IntelliJ files
 .idea
+*.iml
 
 # Ignore npm-debug
 npm-debug.log
@@ -68,3 +68,9 @@ scripts/cache
 
 # nyc (istanbul)
 .nyc_output
+
+# browser tests
+testCompiledForWeb
+
+# lerna debug
+lerna-debug.log

.ncurc.json

@@ -0,0 +1,4 @@
+{
+  "reject": [
+  ]
+}

.nvmrc

@@ -1 +1 @@
-v12
+v18

.nycrc

@@ -1,10 +0,0 @@
-{
-  "include": ["src/**/*.ts"],
-  "exclude": ["src/**/*.d.ts"],
-  "extension": [".ts"],
-  "require": ["ts-node/register"],
-  "reporter": ["text-summary", "html"],
-  "sourceMap": true,
-  "instrument": true,
-  "cache": true
-}

.prettierignore

@@ -0,0 +1 @@
+*.md

.prettierrc

@@ -1,10 +0,0 @@
-{
-  "parser": "typescript",
-  "printWidth": 80,
-  "tabWidth": 2,
-  "semi": false,
-  "singleQuote": true,
-  "trailingComma": "none",
-  "quoteProps": "consistent",
-  "bracketSpacing": false
-}

.travis.yml

@@ -1,9 +0,0 @@
-language: node_js
-node_js:
-  - 10
-  - 12
-  - 13
-script:
-  - yarn test
-  - yarn build
-  - yarn lint

.vscode/extensions.json

@@ -0,0 +1,6 @@
+{
+    "recommendations": [
+      "dbaeumer.vscode-eslint",
+      "esbenp.prettier-vscode"
+    ]
+  }

.vscode/settings.json

@@ -0,0 +1,60 @@
+{
+    "editor.tabSize": 2,
+    "cSpell.words": [
+        "altnet",
+        "Autofills",
+        "Clawback",
+        "hostid",
+        "keypair",
+        "keypairs",
+        "multisign",
+        "multisigned",
+        "multisigning",
+        "preauthorization",
+        "rippletest",
+        "secp256k1",
+        "Setf",
+        "Sidechains",
+        "xchain"
+    ],
+    "[javascript]": {
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "editor.formatOnSave": true
+    },
+    "[javascriptreact]": {
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "editor.formatOnSave": true
+    },
+    "[typescript]": {
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "editor.formatOnSave": true
+    },
+    "[typescriptreact]": {
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "editor.formatOnSave": true
+    },
+    "eslint.alwaysShowStatus": true,
+    "eslint.lintTask.enable": true,
+    "eslint.codeAction.showDocumentation": {
+        "enable": true
+    },
+    "editor.codeActionsOnSave": {
+        "source.fixAll.eslint": "explicit"
+    },
+    "files.insertFinalNewline": true,
+    "files.trimFinalNewlines": true,
+    "files.trimTrailingWhitespace": true,
+    "files.watcherExclude": {
+        "**/.git/objects/**": true,
+        "**/.git/subtree-cache/**": true,
+        "**/.hg/store/**": true
+    },
+    "search.exclude": {
+        "**/.git": true,
+        "**/node_modules": true,
+        "**/tmp": true,
+        "**/docs/**/*.html": true,
+        "**/fixtures/**/*.json": true,
+        "**/docs/assets": true
+    },
+}

APPLICATIONS.md

@@ -1,157 +0,0 @@
-# Applications using ripple-lib (RippleAPI)
-
-A curated list of some of the projects and apps that leverage `ripple-lib` in some way.
-
-**Have one to add?** Please edit this file and open a PR!
-
-## Notice (disclaimer)
-
-These sites are independent of Ripple and have not been authorized, endorsed, sponsored or otherwise approved by Ripple or its affiliates.
-
-Warning: Use at your own risk.
-
-## Exchanges
-
-- **[The World Exchange](https://www.theworldexchange.net/)**
-
-  Trade, issue, and send directly on the XRP Ledger. A user interface for the XRPL's decentralized exchange.
-
-- **[Bitso](https://bitso.com/)**
-
-  Exchange allowing clients to buy and sell XRP, based in Mexico.
-
-## Data and visualizations
-
-- **[xrpintel - XRP Intelligence](https://xrpintel.com/)**
-
-  Monitor the XRP Network in real time and explore historical statistics.
-
-- **[XRP Charts](https://xrpcharts.ripple.com/)** (xrpcharts.ripple.com)
-
-  XRP Charts provides information based on public data, including trade volume, top markets, metrics, transactions, and more.
-
-- **[Ripple Live](https://gatehub.net/live)** (gatehub.net/live)
-
-  Visualize XRP network transactions.
-
-- **[XRPL Dev. Dashboard](https://xrp.fans/)** (xrp.fans)
-
-  Debugging dashboard for `rippled-ws-client-pool`, transaction and query explorer, and transaction signing and submission tool.
-
-- **[XRP Value](http://xrpvalue.com/)**
-
-  Real-time XRP price, trades, and orderbook data from the XRP Ledger.
-
-- **[Bithomp - XRP Explorer](https://bithomp.com/explorer/)**
-
-  Look up information by entering an address, transaction hash, username, or PayID.
-
-- **[Bithomp - XRPL validators](https://bithomp.com/validators)**
-
-  List of XRPL validators, nodes, and testnet validators.
-
-- **[XRP Scan - XRP Ledger explorer](https://xrpscan.com)**
-
-  XRP Ledger explorer, metrics and analytics.
-  
-- **[xrplorer](https://xrplorer.com)**
-
-  XRP Ledger explorer, API, metrics, and analytics using a graph database that is synchronized live with the XRPL.
-
-- **[zerptracker](https://zerptracker.com)**
-
-  Monitor the XRPL using powerful JSONPath expressions, and receive notifications via email, SMS, webhooks, and more.
-
-## Wallets and wallet tools
-
-- **[XUMM](https://xumm.app/)**
-
-  Users can use the xumm application to track their accounts, balances and transactions. The true power of xumm is the platform available for developers.
-
-- **[Xpring Wallet](https://xpring.io)** (uses `ripple-keypairs`)
-
-  Non-custodial XRP wallet.
-
-- **[XRP Toolkit](https://www.xrptoolkit.com)**
-
-  A web interface to the XRP Ledger, supporting both hardware and software wallets.
-
-- **[Toast Wallet](https://toastwallet.com/)**
-
-  A free, open source XRP Wallet for iOS, Android, Windows, Mac and Linux.
-
-- **[Toastify Ledger](https://github.com/WietseWind/toastify-ledger)** (uses `ripple-keypairs`)
-
-  Add a Regular Key to a mnemonic XRP Wallet (e.g. Ledger Nano S) to use the account with a Family Seed (secret).
-
-- **[Bithomp-submit](https://github.com/Bithomp/bithomp-submit)** (GitHub)
-
-  A tool to submit an offline-signed XRPL transaction.
-
-- **[Kyte](https://kyteapp.co/)** (kyteapp.co) ([Source](https://github.com/WietseWind/Zerp-Wallet)) (Deprecated)
-
-  Web-based XRP wallet.
-
-- **[XRP Vanity Address Generator](https://github.com/WietseWind/xrp-vanity-generator)** (Node.js)
-
-  A vanity address is a wallet address containing a few characters you like at the beginning or the end of the wallet address.
-
-- **[XRP Account Mnemonic Recovery](https://github.com/WietseWind/xrp-mnemonic-recovery)** (uses `ripple-keypairs`)
-
-  Recover a 24 word mnemonic if one word is wrong or one word is missing.
-
-## Send and request payments
-
-- **[XRP Tip Bot](https://www.xrptipbot.com/)**
-
-  A bot that enables users on reddit, Twitter and Discord to send XRP to each other through reddit comments and Twitter tweets.
-
-- **[XRP Text](https://xrptext.com/)**
-
-  Send XRP using SMS text messages.
-
-- **[XRParrot](https://xrparrot.com/)** (uses `ripple-address-codec`)
-
-  Easy EUR (SEPA) to XRP transfer (currency conversion).
-
-- **[XRP Payment](https://xrpayments.co/)** (xrpayments.co)
-
-  Tool for generating a XRP payment request URI in a QR code, with currency converter.
-
-## Development tools
-
-- **[XRP Faucets for Testnet and Devnet](https://xrpl.org/xrp-testnet-faucet.html)**
-
-  Get some test funds for development on the test network. The faucet uses `ripple-lib`.
-
-## Code samples and libraries
-
-- **[ilp-plugin-xrp-paychan](https://github.com/interledgerjs/ilp-plugin-xrp-paychan)**
-
-  Send ILP payments using XRP and payment channels (PayChan).
-
-- **[RunKit: WietseWind](https://runkit.com/wietsewind/)**
-
-  XRP Ledger code samples for Node.js.
-
-- **[GitHub Gist: WietseWind](https://gist.github.com/WietseWind)**
-
-  XRP Ledger code samples for Node.js and the web (mostly).
-
-- **[rippled-ws-client-sign](https://github.com/WietseWind/rippled-ws-client-sign)**
-
-  Sign transactions, with support for MultiSign.
-
-- **[ILP-enabled power switch](https://xrpcommunity.blog/raspberry-pi-interledger-xp-powerswitch-howto/)** ([video](https://www.youtube.com/watch?v=c-eS0HQUuJg)) (uses [`moneyd-uplink-xrp`](https://github.com/interledgerjs/moneyd-uplink-xrp))
-
-  For about $30 in parts (Raspberry Pi, 3.3V Relay board and a few wires) you can build your own power switch that will switch on if a streaming ILP payment comes in. When the payment stream stops, the power turns off.
-
-## Related apps that do not appear to use ripple-lib
-
-- **[XRP Stats](https://ledger.exposed/)** (ledger.exposed)
-
-  Rich list, live ledger stats and XRP distribution. Visualize escrows and flow of funds.
-
-- **[XRP Vanity](https://xrpvanity.com/)** (xrpvanity.com)
-
-  Custom XRP addresses for sale, delivered by SetRegularKey.

CONTRIBUTING.md

@@ -0,0 +1,280 @@
+# Contributing
+
+### High Level Process to Contribute Code
+
+- You should open a PR against `main` and ensure that all CI passes.
+- Your changes should have [unit](#unit-tests) and/or [integration tests](#integration-tests).
+- Your changes should [pass the linter](#run-the-linter).
+- You should get a full code review from two of the maintainers.
+- Then you can merge your changes. (Which will then be included in the next release)
+
+## Set up your dev environment
+
+### Requirements
+
+We use Node v18 for development - that is the version that our linters require.
+You must also use `npm` v7. You can check your `npm` version with:
+
+```bash
+npm -v
+```
+
+If your `npm` version is too old, use this command to update it:
+
+```bash
+npm -g i npm@7
+```
+
+### Set up
+
+1. Clone the repository
+2. `cd` into the repository
+3. Install dependencies with `npm install`
+
+### Build
+
+```bash
+npm run build
+```
+
+## Run the linter
+
+```bash
+npm install
+npm run build
+npm run lint
+```
+
+## Running Tests
+
+For integration and browser tests, we use a `xahaud` node in standalone mode to test xahau.js code against. To set this up, you can either configure and run `xahaud` locally, or set up the Docker container `xahauci/xahaud` by [following these instructions](#integration-tests). The latter will require you to [install Docker](https://docs.docker.com/get-docker/).
+
+### Unit Tests
+
+```bash
+npm install
+npm run build
+npm test
+```
+
+### Integration Tests
+
+From the top-level xahau.js folder (one level above `packages`), run the following commands:
+
+```bash
+npm install
+# sets up the xahaud standalone Docker container - you can skip this step if you already have it set up
+docker run -p 6006:6006 --interactive -t --volume $PWD/.ci-config:/opt/xahau/etc/ --platform linux/amd64 xahauci/xahaud:2025.2.6 /opt/xahau/bin/xahaud -a --conf /opt/xahau/etc/xahaud.cfg
+npm run build
+npm run test:integration
+```
+
+Breaking down the command:
+* `docker run -p 6006:6006` starts a Docker container with an open port for admin WebSocket requests.
+* `--interactive` allows you to interact with the container.
+* `-t` starts a terminal in the container for you to send commands to.
+* `--volume $PWD/.ci-config:/config/` identifies the `xahaud.cfg` and `validators.txt` to import. It must be an absolute path, so we use `$PWD` instead of `./`.
+* `xahauci/xahaud` is an image that is regularly updated with the latest `xahaud` releases
+* `/opt/xahau/bin/xahaud -a --conf /opt/xahau/etc/xahaud.cfg` starts `xahaud` in standalone mode
+
+### Browser Tests
+
+There are two ways to run browser tests.
+
+One is in the browser - run `npm run build:browserTests` and open `test/localIntegrationRunner.html` in your browser.
+
+The other is in the command line (this is what we use for CI) -
+
+This should be run from the `xahau.js` top level folder (one above the `packages` folder).
+
+```bash
+npm run build
+# sets up the xahaud standalone Docker container - you can skip this step if you already have it set up
+docker run -p 6006:6006 --interactive -t --volume $PWD/.ci-config:/opt/xahau/etc/ --platform linux/amd64 xahauci/xahaud:2025.2.6 /opt/xahau/bin/xahaud -a --conf /opt/xahau/etc/xahaud.cfg
+npm run test:browser
+```
+
+## High Level Architecture
+
+This is a monorepo, which means that there are multiple packages in a single GitHub repository using [Lerna](https://lerna.js.org/).
+
+The 4 packages currently here are:
+
+1. xahau.js - The client library for interacting with the ledger.
+2. xahau-binary-codec - A library for serializing and deserializing transactions for the ledger.
+3. xahau-keypairs - A library for generating and using cryptographic keypairs.
+4. xahau-address-codec - A library for encoding and decoding Xahau Ledger addresses and seeds.
+5. isomorphic - A collection of isomorphic implementations of crypto and utility functions.
+6. secret-numbers - Generate XRPL Accounts with a number-based secret: 8 chunks of 6 digits.
+
+Each package has it's own README which dives deeper into what it's main purpose is, and the core functionality it offers.
+They also run tests independently as they were originally in separate repositories.
+
+These are managed in a monorepo because often a change in a lower-level library will also require a change in xahau.js, and so it makes sense to be able to allow for modifications of all packages at once without coordinating versions across multiple repositories.
+
+Let's dive a bit into how xahau.js is structured!
+
+### The File Structure
+
+Within the xrpl package, each folder has a specific purpose:
+
+**Client** - This contains logic for handling the websocket connection to xahaud servers.
+**Models** - These types model LedgerObjects, Requests/Methods, and Transactions in order to give type hints and nice errors for users.
+**Sugar** - This is where handy helper functions end up, like `submit`, `autofill`, and `getXAHBalance` amongst others.
+**Utils** - These are shared functions which are useful for conversions, or internal implementation details within the library.
+**Wallet** - This logic handles managing keys, addresses, and signing within xahau.js
+
+### Writing Tests for xahau.js
+
+For every file in `src`, we try to have a corresponding file in `test` with unit tests.
+
+The goal is to maintain above 80% code coverage, and generally any new feature or bug fix should be accompanied by unit tests, and integration tests if applicable.
+
+For an example of a unit test, check out the [autofill tests here](./packages/xahau/test/client/autofill.ts).
+
+If your code connects to the ledger (ex. Adding a new transaction type) it's handy to write integration tests to ensure that you can successfully interact with the ledger. Integration tests are generally run against a docker instance of xahaud which contains the latest updates. Since standalone mode allows us to manually close ledgers, this allows us to run integration tests at a much faster rate than if we had to wait 4-5 seconds per transaction for the ledger to validate the transaction. [See above](#running-tests) for how to start up the docker container to run integration tests.
+
+All integration tests should be written in the `test/integration` folder, with new `Requests` and `Transactions` tests being in their respective folders.
+
+For an example of how to write an integration test for `xahau.js`, you can look at the [Payment integration test](./packages/xahau/test/integration/transactions/payment.ts).
+
+## Generate reference docs
+
+You can see the complete reference documentation at [`xahau.js` docs](https://js.xrpl.org). You can also generate them locally using `typedoc`:
+
+```bash
+npm run docgen
+```
+
+This updates `docs/` at the top level, where GitHub Pages looks for the docs.
+
+## Update `definitions.json`
+
+Use [this repo](https://github.com/RichardAH/xrpl-codec-gen) to generate a new `definitions.json` file from the xahaud source code. Instructions are available in that README.
+
+## Adding and removing packages
+
+`xahau.js` uses `lerna` and `npm`'s workspaces features to manage a monorepo.
+Adding and removing packages requires a slightly different process than normal
+as a result.
+
+### Adding or removing development dependencies
+
+`xahau.js` strives to use the same development dependencies in all packages.
+You may add and remove dev dependencies like normal:
+
+```bash
+### adding a new dependency
+npm install --save-dev abbrev
+### removing a dependency
+npm uninstall --save-dev abbrev
+```
+
+### Adding or removing runtime dependencies
+
+You need to specify which package is changing using the `-w` flag:
+
+```bash
+### adding a new dependency to `xahau`
+npm install abbrev -w xahau
+### adding a new dependency to `xahau-keypairs`
+npm install abbrev -w xahau-keypairs
+### removing a dependency
+npm uninstall abbrev -w xahau
+```
+
+## Updating the Docker container for CI
+
+In order to test the library, we need to enable the latest amendments in the docker container.
+This requires updating the `/.ci-config/xahaud.cfg` file with the hashes and names of new amendments.
+
+In order to update the list, follow these steps from the top level of the library:
+1. Run `node ./.ci-config/getNewAmendments.js`
+2. If there are any new amendment hashes, add a comment to the end of `/.ci-config/xahaud.cfg` with the date
+   - `Ex. "# Added August 9th, 2023"`
+3. For each hash printed out by the script, add the hash and name to the config file.
+   - Ex. `B2A4DB846F0891BF2C76AB2F2ACC8F5B4EC64437135C6E56F3F859DE5FFD5856 ExpandedSignerList`
+   - You can look up the name by searching for the hash on https://xrpl.org/known-amendments.html
+4. Push your changes
+
+Note: The same updated config can be used to update xahau-py's CI as well.
+
+## Updating `definitions.json`
+
+This should almost always be done using the [`xrpl-codec-gen`](https://github.com/RichardAH/xrpl-codec-gen) script - if the output needs manual intervention afterwards, consider updating the script instead.
+
+1. Clone / pull the latest changes from [xahaud](https://github.com/XRPLF/xahaud) - Specifically the `develop` branch is usually the right one.
+2. Clone / pull the latest changes from [`xrpl-codec-gen`](https://github.com/RichardAH/xrpl-codec-gen)
+3. From the `xrpl-codec-gen` tool, follow the steps in the `README.md` to generate a new `definitions.json` file.
+4. Replace the `definitions.json` file in the `xahau-binary-codec` with the newly generated file.
+5. Verify that the changes make sense by inspection before submitting, as there may be updates required for the `xrpl-codec-gen` tool depending on the latest amendments we're updating to match.
+
+
+## Release process + checklist
+
+## PR process
+
+- [ ] Your changes should be on a branch.
+- [ ] Your changes should have unit tests.
+- [ ] Lint the code with `npm lint`
+- [ ] Build your code with `npm build`
+- [ ] Run the unit tests with `npm test`
+- [ ] Get a full code review.
+- [ ] Merge your branch into `main` and push to github.
+- [ ] Ensure that all tests passed on the last CI that ran on `main`.
+
+## Release
+
+1. Checkout `main` (or your beta branch) and `git pull`.
+1. Create a new branch (`git checkout -b <BRANCH_NAME>`) to capture updates that take place during this process.
+1. Update `HISTORY.md` to reflect release changes.
+
+   - [ ] Update the version number and release date, and ensure it lists the changes since the previous release.
+
+1. Run `npm run docgen` if the docs were modified in this release to update them (skip this step for a beta).
+1. Run `npm run build` to triple check the build still works
+1. Run `npx lerna version --no-git-tag-version` - This bumps the package versions.
+
+   - For each changed package, pick what the new version should be. Lerna will bump the versions, commit version bumps to `main`, and create a new git tag for each published package.
+   - If you do NOT want to update the package number, choose "Custom Version" and set the version to be the same as the existing version. Lerna will not publish any changes in this case.
+   - If publishing a beta, make sure that the versions are all of the form `a.b.c-beta.d`, where `a`, `b`, and `c` are identical to the last normal release except for one, which has been incremented by 1.
+
+1. Run `npm i` to update the package-lock with the updated versions.
+1. Create a new PR from this branch into `main` and merge it (you can directly merge into the beta branch for a beta).
+1. Checkout `main` and `git pull` (you can skip this step for a beta since you already have the latest version of the beta branch).
+1. Actually publish the packages with one of the following:
+
+   - Stable release: Run `npx lerna publish from-package --yes`
+   - Beta release: Run `npx lerna publish from-package --dist-tag beta --yes`
+     Notice this allows developers to install the package with `npm add xahau@beta`
+
+1. If requested, enter your [npmjs.com](https://npmjs.com) OTP (one-time password) to complete publication.
+
+   NOW YOU HAVE PUBLISHED! But you're not done; we have to notify people!
+
+1. Run `git tag <tagname> -m <tagname>`, where `<tagname>` is the new package and version (e.g. `xahau@2.1.1`), for each version released.
+1. Run `git push --follow-tags`, to push the tags to Github.
+1. On GitHub, click the "Releases" link on the right-hand side of the page.
+
+1. Repeat for each release:
+
+   1. Click "Draft a new release"
+   1. Click "Choose a tag", and choose a tag that you just created.
+   1. Edit the name of the release to match the tag (IE \<package\>@\<version\>) and edit the description as you see fit.
+
+1. Send an email to [xahau-announce](https://groups.google.com/g/xahau-announce).
+1. Lastly, send a similar message to the Xahau Discord in the [`javascript` channel](https://discord.com/channels/1085202760548499486/1085203623111295068). The message should include:
+   1. The version changes for xahau libraries
+   1. A link to the more detailed changes
+   1. Highlights of important changes
+
+
+## Mailing Lists
+
+We have a low-traffic mailing list for announcements of new `xahau.js` releases. (About 1 email every couple of weeks)
+
+- [Subscribe to xahau-announce](https://groups.google.com/g/xahau-announce)
+
+If you're using the Xahau Ledger in production, you should run a [xahaud server](https://github.com/xahau/xahaud) and subscribe to the xahau-server mailing list as well.
+
+- [Subscribe to xahau-server](https://groups.google.com/g/xahau-server)

README.md

@@ -1,96 +1,99 @@
-# ripple-lib (RippleAPI)
+# xahau.js
 
-A JavaScript/TypeScript API for interacting with the XRP Ledger
+A JavaScript/TypeScript library for interacting with the Xahau Ledger
 
-[![NPM](https://nodei.co/npm/ripple-lib.png)](https://www.npmjs.org/package/ripple-lib)
+[![NPM](https://nodei.co/npm/xahau.png)](https://www.npmjs.org/package/xahau)
+![npm bundle size](https://img.shields.io/bundlephobia/min/xahau)
 
-This is the recommended library for integrating a JavaScript/TypeScript app with the XRP Ledger, especially if you intend to use advanced functionality such as IOUs, payment paths, the decentralized exchange, account settings, payment channels, escrows, multi-signing, and more.
+This is the recommended library for integrating a JavaScript/TypeScript app with the Xahau Ledger, especially if you intend to use advanced functionality such as IOUs, payment paths, the decentralized exchange, account settings, payment channels, escrows, multi-signing, and more.
 
-## [➡️ Reference Documentation](https://xrpl.org/rippleapi-reference.html)
+<!-- ## [➡️ Reference Documentation](http://js.xahau.org)
 
-See the full reference documentation on the XRP Ledger Dev Portal.
+See the full reference documentation for all classes, methods, and utilities.
 
-## [➡️ Applications and Projects](APPLICATIONS.md)
+## Features
 
-What is ripple-lib used for? The applications on the list linked above use `ripple-lib`. Open a PR to add your app or project to the list!
+1. Managing keys & creating test credentials ([`Wallet`](https://js.xahau.org/classes/Wallet.html) && [`Client.fundWallet()`](https://js.xahau.org/classes/Client.html#fundWallet))
+2. Submitting transactions to the Xahau Ledger ([`Client.submit(...)`](https://js.xahau.org/classes/Client.html#submit) & [transaction types](https://xahau.org/transaction-types.html))
+3. Sending requests to observe the ledger ([`Client.request(...)`](https://js.xahau.org/classes/Client.html#request) using [public API methods](https://xahau.org/public-api-methods.html))
+4. Subscribing to changes in the ledger ([Ex. ledger, transactions, & more...](https://xahau.org/subscribe.html))
+5. Parsing ledger data into more convenient formats ([`xrpToDrops`](https://js.xahau.org/functions/xrpToDrops.html) and [`rippleTimeToISOTime`](https://js.xahau.org/functions/rippleTimeToISOTime.html))
 
-### Features
+All of which works in Node.js (tested for v18+) & web browsers (tested for Chrome). -->
 
-+ Connect to a `rippled` server from Node.js or a web browser
-+ Helpers for creating requests and parsing responses for the [rippled API](https://developers.ripple.com/rippled-api.html)
-+ Listen to events on the XRP Ledger (transactions, ledger, validations, etc.)
-+ Sign and submit transactions to the XRP Ledger
-+ Type definitions for TypeScript
+# Quickstart
 
 ### Requirements
 
-+ **[Node.js v14](https://nodejs.org/)** is recommended. Other versions may work but are not frequently tested.
-+ **[Yarn](https://yarnpkg.com/)** is recommended. `npm` may work but we use `yarn.lock`.
++ **[Node.js v18](https://nodejs.org/)** is recommended. We also support v20. Other versions may work but are not frequently tested.
 
-## Getting Started
+### Installing xahau.js
 
-See also: [RippleAPI Beginners Guide](https://xrpl.org/get-started-with-rippleapi-for-javascript.html)
+In an existing project (with package.json), install xahau.js with:
 
-In an existing project (with `package.json`), install `ripple-lib`:
 ```
-$ yarn add ripple-lib
+$ npm install --save xahau
 ```
 
-Then see the documentation:
+Or with `yarn`:
+
+```
+$ yarn add xahau
+```
+
+Example usage:
+
+```js
+const xahau = require("xahau");
+async function main() {
+  const client = new xahau.Client("wss://xahau-test.net");
+  await client.connect();
+
+  const response = await client.request({
+    command: "account_info",
+    account: "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe",
+    ledger_index: "validated",
+  });
+  console.log(response);
+
+  await client.disconnect();
+}
+main();
+```
+
+It goes through:
+
+1. Creating a new test account
+2. Sending a payment transaction
+3. And sending requests to see your account balance!
+
+### Case by Case Setup Steps
+
+If you're using xahau.js with React or Deno, you'll need to do a couple extra steps to set it up:
+
+- [Using xahau.js with a CDN](https://github.com/XRPLF/xahau.js/blob/main/UNIQUE_SETUPS.md#using-xahaujs-from-a-cdn)
+- [Using xahau.js with `create-react-app`](https://github.com/XRPLF/xahau.js/blob/main/UNIQUE_SETUPS.md#using-xahaujs-with-create-react-app)
+- [Using xahau.js with `React Native`](https://github.com/XRPLF/xahau.js/blob/main/UNIQUE_SETUPS.md#using-xahaujs-with-react-native)
+- [Using xahau.js with `Vite React`](https://github.com/XRPLF/xahau.js/blob/main/UNIQUE_SETUPS.md#using-xahaujs-with-vite-react)
+- [Using xahau.js with `Deno`](https://github.com/XRPLF/xahau.js/blob/main/UNIQUE_SETUPS.md#using-xahaujs-with-deno)
 
 ## Documentation
 
-+ [RippleAPI Beginners Guide](https://xrpl.org/get-started-with-rippleapi-for-javascript.html)
-+ [RippleAPI Full Reference Documentation](https://xrpl.org/rippleapi-reference.html) ([in this repo](https://github.com/ripple/ripple-lib/blob/develop/docs/index.md))
-+ [Code Samples](https://github.com/ripple/ripple-lib/tree/develop/docs/samples)
+As you develop with xahau.js, there's two sites you'll use extensively:
+
+1. [docs.xahau.network](https://docs.xahau.network/technical/protocol-reference) is the primary source for:
+   - How the ledger works ([See Concepts](https://docs.xahau.network/))
+   - What kinds of transactions there are ([Transaction Types](https://docs.xahau.network/technical/protocol-reference/transactions/transaction-types))
+   - Requests you can send ([Public API Methods](https://docs.xahau.network/features/http-websocket-apis))
 
 ### Mailing Lists
 
-We have a low-traffic mailing list for announcements of new ripple-lib releases. (About 1 email per week)
+If you want to hear when we release new versions of xahau.js, you can join our low-traffic mailing list (About 1 email per week):
 
-+ [Subscribe to ripple-lib-announce](https://groups.google.com/forum/#!forum/ripple-lib-announce)
+- [Subscribe to xahau-announce](https://groups.google.com/g/xahau-announce)
 
-If you're using the XRP Ledger in production, you should run a [rippled server](https://github.com/ripple/rippled) and subscribe to the ripple-server mailing list as well.
+If you're using the Xahau Ledger in production, you should run a [xahaud server](https://github.com/Xahau/xahaud) and subscribe to the xahau-server mailing list as well.
 
-+ [Subscribe to ripple-server](https://groups.google.com/forum/#!forum/ripple-server)
+- [Subscribe to xahau-server](https://groups.google.com/g/xahau-server)
 
-## Development
-
-To build the library for Node.js and the browser:
-```
-$ yarn build
-```
-
-The TypeScript compiler will [output](./tsconfig.json#L7) the resulting JS files in `./dist/npm/`.
-
-webpack will output the resulting JS files in `./build/`.
-
-For details, see the `scripts` in `package.json`.
-
-## Running Tests
-
-### Unit Tests
-
-1. Clone the repository
-2. `cd` into the repository and install dependencies with `yarn install`
-3. `yarn test`
-
-### Linting
-
-Run `yarn lint` to lint the code with `eslint`.
-
-## Generating Documentation
-
-Do not edit `./docs/index.md` directly because it is a generated file.
-
-Instead, edit the appropriate `.md.ejs` files in `./docs/src/`.
-
-If you make changes to the JSON schemas, fixtures, or documentation sources, update the documentation by running `yarn run docgen`.
-
-## More Information
-
-+ [ripple-lib-announce mailing list](https://groups.google.com/forum/#!forum/ripple-lib-announce) - subscribe for release announcements
-+ [RippleAPI Reference](https://xrpl.org/rippleapi-reference.html) - XRP Ledger Dev Portal
-+ [XRP Ledger Dev Portal](https://xrpl.org/)
-
- [![Build Status](https://travis-ci.org/ripple/ripple-lib.svg?branch=master)](https://travis-ci.org/ripple/ripple-lib)
+You are also welcome to create an [issue](https://github.com/Xahau/xahau.js/issues) here and we'll do our best to respond within 3 days.

SECURITY.md

@@ -1,29 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-This table shows which versions of ripple-lib are currently supported with security updates:
-
-| Version | Supported              |
-| ------- | ---------------------- |
-| 1.x     | :white_check_mark: Yes |
-| 0.x     | :x:                No  |
-
-## Responsible disclosure security policy
-
-The responsible disclosure of vulnerabilities helps to protect users of the project. Vulnerabilities are first triaged in a private manner, and only publicly disclosed after a reasonable time period that allows patching the vulnerability and provides an upgrade path for users.
-
-When contacting us directly via email, we will do our best to respond in a reasonable time to resolve the issue. Do not disclose the vulnerability until it has been patched and users have been given time to upgrade.
-
-We kindly ask you to refrain from malicious acts that put our users, the project, or any of the project’s team members at risk.
-
-## Reporting a security issue
-
-Security is a top priority. But no matter how much effort we put into security, there can still be vulnerabilities present.
-
-If you discover a security vulnerability, please use the following means of communications to report it to us:
-
-- Report the security issue to bugs@ripple.com
-- [Ripple Bug Bounty](https://ripple.com/bug-bounty/)
-
-Your efforts to responsibly disclose your findings are sincerely appreciated and will be taken into account to acknowledge your contributions.

UNIQUE_SETUPS.md

@@ -0,0 +1,81 @@
+# Unique Setup Steps for Xahau.js
+
+Starting in 3.0 xahau and all the packages in this repo no longer require custom configurations (ex. polyfills) to run.
+
+### Using xahau.js from a CDN
+
+You can avoid setting up your build system to handle `xahau.js` by using a cdn version that is prebuilt for the browser.
+
+- unpkg `<script src="https://unpkg.com/xahau@2.3.0/build/xahau-latest-min.js"></script>`
+- jsdelivr `<script src="https://cdn.jsdelivr.net/npm/xahau@2.3.0/build/xahau-latest-min.js"></script>`
+
+Ensure that the full path is provided so the browser can find the sourcemaps.
+
+### Using xahau.js with `create-react-app`
+
+Starting in 3.0 xahau and its related packages no longer require custom configurations (ex. polyfills) to run.
+
+This online template uses these steps to run xahau.js with React in the browser:
+https://codesandbox.io/s/xahau-intro-pxgdjr?file=/src/App.js
+
+### Using xahau.js with React Native
+
+If you want to use `xahau.js` with React Native you will need to install polyfills for core NodeJS modules.
+
+1. Install dependencies (you can use `yarn` as well):
+
+   ```shell
+   npm install xahau \
+       fast-text-encoding \
+       react-native-get-random-values
+   ```
+
+2. After that, run the following commands:
+
+   ```shell
+   # compile `react-native-get-random-values` pods see https://www.npmjs.com/package/react-native-get-random-values#installation
+   npx pod-install
+   ```
+   
+3. Create `polyfills.js` and add
+
+```javascript
+// Required for TextEncoder/TextDecoder
+import 'fast-text-encoding'
+// Required for `crypto.getRandomValues`
+import 'react-native-get-random-values'
+```
+
+4. Import `polyfills` in index file your project (it must be the first line):
+
+```javascript
+import './polyfills'
+...
+```
+
+### Using xahau.js with Vite React
+
+Starting in 3.0 xahau and all the packages in this repo no longer require custom configurations (ex. polyfills) to run.
+
+### Using xahau.js with Deno
+
+Until official support for [Deno](https://deno.land) is added, you can use the following work-around to use `xahau.js` with Deno:
+
+> [!NOTE]
+> The following is currently broken due to https://github.com/denoland/deno/issues/20516.
+> Once that is fixed there could be other issues as well.
+
+```javascript
+import xahau from 'https://dev.jspm.io/npm:xahau';
+
+(async () => {
+  const api = new (xahau as any).Client('wss://xahau-test.net');
+  const address = 'rH8NxV12EuV...khfJ5uw9kT';
+
+  api.connect().then(() => {
+    api.getBalances(address).then((balances: any) => {
+      console.log(JSON.stringify(balances, null, 2));
+    });
+  });
+})();
+```

circle.yml

@@ -1,18 +0,0 @@
-machine:
-  node:
-    version: 6.11.3
-  hosts:
-    testripple.circleci.com: 127.0.0.1
-dependencies:
-  pre:
-    - wget https://s3-us-west-2.amazonaws.com/ripple-debs/rippled_0.30.1-b11-1.deb
-    - sudo dpkg -i rippled_0.30.1-b11-1.deb
-test:
-  pre:
-    - rippled -a --start --conf "$HOME/$CIRCLE_PROJECT_REPONAME/test/integration/rippled.cfg":
-        background: true
-  override:
-    - scripts/ci.sh "$CIRCLE_NODE_INDEX" "$CIRCLE_NODE_TOTAL":
-        parallel: true
-  post:
-    - killall /usr/bin/rippled

docs/samples/README.md

@@ -1,5 +0,0 @@
-Usage:
-babel-node balances.js
-babel-node cancelall.js (requires setting address and secret in source file first)
-babel-node payment.js (requires setting address and secret in source file first)
-babel-node ticket.js (requires setting address and secret in source file first)

docs/samples/balances.js

@@ -1,12 +0,0 @@
-'use strict';
-const RippleAPI = require('../../src').RippleAPI; // require('ripple-lib')
-
-const api = new RippleAPI({server: 'wss://s1.ripple.com:443'});
-const address = 'r3kmLJN5D28dHuH8vZNUZpMC43pEHpaocV';
-
-api.connect().then(() => {
-  api.getBalances(address).then(balances => {
-    console.log(JSON.stringify(balances, null, 2));
-    process.exit();
-  });
-});

docs/samples/cancelall.js

@@ -1,38 +0,0 @@
-'use strict';
-const RippleAPI = require('../../dist/npm').RippleAPI; // require('ripple-lib')
-
-const address = 'rLDYrujdKUfVx28T9vRDAbyJ7G2WVXKo4K';
-const secret = '';
-
-const api = new RippleAPI({server: 'wss://s1.ripple.com:443'});
-const instructions = {maxLedgerVersionOffset: 5};
-
-function fail(message) {
-  console.error(message);
-  process.exit(1);
-}
-
-function cancelOrder(orderSequence) {
-  console.log('Cancelling order: ' + orderSequence.toString());
-  return api.prepareOrderCancellation(address, {orderSequence}, instructions)
-  .then(prepared => {
-    const signing = api.sign(prepared.txJSON, secret);
-    return api.submit(signing.signedTransaction);
-  });
-}
-
-function cancelAllOrders(orderSequences) {
-  if (orderSequences.length === 0) {
-    return Promise.resolve();
-  }
-  const orderSequence = orderSequences.pop();
-  return cancelOrder(orderSequence).then(() => cancelAllOrders(orderSequences));
-}
-
-api.connect().then(() => {
-  console.log('Connected...');
-  return api.getOrders(address).then(orders => {
-    const orderSequences = orders.map(order => order.properties.sequence);
-    return cancelAllOrders(orderSequences);
-  }).then(() => process.exit(0));
-}).catch(fail);

docs/samples/payment.js

@@ -1,45 +0,0 @@
-'use strict';
-const RippleAPI = require('../../src').RippleAPI; // require('ripple-lib')
-
-const address = 'INSERT ADDRESS HERE';
-const secret = 'INSERT SECRET HERE';
-
-const api = new RippleAPI({server: 'wss://s1.ripple.com:443'});
-const instructions = {maxLedgerVersionOffset: 5};
-
-const payment = {
-  source: {
-    address: address,
-    maxAmount: {
-      value: '0.01',
-      currency: 'XRP'
-    }
-  },
-  destination: {
-    address: 'rKmBGxocj9Abgy25J51Mk1iqFzW9aVF9Tc',
-    amount: {
-      value: '0.01',
-      currency: 'XRP'
-    }
-  }
-};
-
-function quit(message) {
-  console.log(message);
-  process.exit(0);
-}
-
-function fail(message) {
-  console.error(message);
-  process.exit(1);
-}
-
-api.connect().then(() => {
-  console.log('Connected...');
-  return api.preparePayment(address, payment, instructions).then(prepared => {
-    console.log('Payment transaction prepared...');
-    const {signedTransaction} = api.sign(prepared.txJSON, secret);
-    console.log('Payment transaction signed...');
-    api.submit(signedTransaction).then(quit, fail);
-  });
-}).catch(fail);

docs/samples/ticket.js

@@ -1,31 +0,0 @@
-'use strict';
-const RippleAPI = require('../../src').RippleAPI; // require('ripple-lib')
-
-const address = 'INSERT ADDRESS HERE';
-const secret = 'INSERT SECRET HERE';
-
-const api = new RippleAPI({server: 'wss://s1.ripple.com:443'});
-const instructions = {
-  maxLedgerVersionOffset: 5
-};
-const numberOfTickets = 1;
-
-function quit(message) {
-  console.log(message);
-  process.exit(0);
-}
-
-function fail(message) {
-  console.error(message);
-  process.exit(1);
-}
-
-api.connect().then(() => {
-  console.log('Connected...');
-  return api.prepareTicketCreate(address, numberOfTickets, instructions).then(prepared => {
-    console.log('Ticket transaction prepared...');
-    const {signedTransaction} = api.sign(prepared.txJSON, secret);
-    console.log('Ticket transaction signed...');
-    api.submit(signedTransaction).then(quit, fail);
-  });
-}).catch(fail);

docs/src/basictypes.md.ejs

@@ -1,67 +0,0 @@
-# Basic Types
-
-## Address
-
-```json
-"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59"
-```
-
-```json
-"X7AcgcsBL6XDcUb289X4mJ8djcdyKaB5hJDWMArnXr61cqZ"
-```
-
-An *address* refers to a specific XRP Ledger account. It is a base-58 encoding of a hash of the account's public key. There are two kinds of addresses in common use:
-
-### Classic Address
-
-A *classic address* encodes a hash of the account's public key and a checksum. It has no other data. This kind of address always starts with the lowercase letter `r`.
-
-### X-address
-
-An *X-address* encodes a hash of the account's public key, a tag, and a checksum. This kind of address starts with the uppercase letter `X` if it is intended for use on the production XRP Ledger (mainnet). It starts with the uppercase letter `T` if it is intended for use on a test network such as Testnet or Devnet.
-
-## Account Sequence Number
-
-Every XRP Ledger account has a *sequence number* that is used to keep transactions in order. Every transaction must have a sequence or a ticketSequence number. A transaction can only be executed if it has the next sequence number in order, of the account sending it, or uses a previously generated ticketSequence number. This prevents one transaction from executing twice and transactions executing out of order. The sequence number starts at `1` and increments for each transaction that the account makes.
-
-## Currency
-
-Currencies are represented as either 3-character currency codes or 40-character uppercase hexadecimal strings. We recommend using uppercase [ISO 4217 Currency Codes](http://www.xe.com/iso4217.php) only. The string "XRP" is disallowed on trustlines because it is reserved for the XRP Ledger's native currency. The following characters are permitted: all uppercase and lowercase letters, digits, as well as the symbols `?`, `!`, `@`, `#`, `$`, `%`, `^`, `&`, `*`, `<`, `>`, `(`, `)`, `{`, `}`, `[`, `]`, and `|`.
-
-## Value
-A *value* is a quantity of a currency represented as a decimal string. Be careful: JavaScript's native number format does not have sufficient precision to represent all values. XRP has different precision from other currencies.
-
-**XRP** has 6 significant digits past the decimal point. In other words, XRP cannot be divided into positive values smaller than `0.000001` (1e-6). This smallest unit is called a "drop". XRP has a maximum value of `100000000000` (1e11). Some RippleAPI methods accept XRP in order to maintain compatibility with older versions of the API. For consistency with the `rippled` APIs, we recommend formally specifying XRP values in *drops* in all API requests, and converting them to XRP for display. This is similar to Bitcoin's *satoshis* and Ethereum's *wei*. 1 XRP = 1,000,000 drops.
-
-**Non-XRP values** have 16 decimal digits of precision, with a maximum value of `9999999999999999e80`. The smallest positive non-XRP value is `1e-81`.
-
-## Amount
-
-Example 100.00 USD amount:
-
-```json
-{
-  "currency": "USD",
-  "counterparty": "rMH4UxPrbuMa1spCBR98hLLyNJp4d8p4tM",
-  "value": "100"
-}
-```
-
-Example 3.0 XRP amount, in drops:
-```json
-{
-  "currency": "drops",
-  "value": "3000000"
-}
-```
-(Requires `ripple-lib` version 1.0.0 or higher.)
-
-An *amount* is an object specifying a currency, a quantity of that currency, and the counterparty (issuer) on the trustline that holds the value. For XRP, there is no counterparty.
-
-A *lax amount* allows the counterparty to be omitted for all currencies. If the counterparty is not specified in an amount within a transaction specification, then any counterparty may be used for that amount.
-
-A *lax lax amount* allows either or both the counterparty and value to be omitted.
-
-A *balance* is an amount than can have a negative value.
-
-<%- renderSchema('objects/amountbase.json') %>

docs/src/boilerplate.md.ejs

@@ -1,62 +0,0 @@
-## Boilerplate
-
-Use the following [boilerplate code](https://en.wikipedia.org/wiki/Boilerplate_code) to wrap your custom code using RippleAPI.
-
-```javascript
-const RippleAPI = require('ripple-lib').RippleAPI;
-
-const api = new RippleAPI({
-  server: 'wss://s1.ripple.com' // Public rippled server hosted by Ripple, Inc.
-});
-api.on('error', (errorCode, errorMessage) => {
-  console.log(errorCode + ': ' + errorMessage);
-});
-api.on('connected', () => {
-  console.log('connected');
-});
-api.on('disconnected', (code) => {
-  // code - [close code](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent) sent by the server
-  // will be 1000 if this was normal closure
-  console.log('disconnected, code:', code);
-});
-api.connect().then(() => {
-  /* insert code here */
-}).then(() => {
-  return api.disconnect();
-}).catch(console.error);
-```
-
-RippleAPI is designed to work in [Node.js](https://nodejs.org) version 6 or higher. Ripple recommends Node.js v10 LTS.
-
-The code samples in this documentation are written with ECMAScript 6 (ES6) features, but `RippleAPI` also works with ECMAScript 5 (ES5). Regardless of whether you use ES5 or ES6, the methods that return Promises return [ES6-style promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
-
-<aside class="notice">
-All the code snippets in this documentation assume that you have surrounded them with this boilerplate.
-</aside>
-
-<aside class="notice">
-If you omit the "catch" section, errors may not be visible.
-</aside>
-
-<aside class="notice">
-The "error" event is emitted whenever an error occurs that cannot be associated with a specific request. If the listener is not registered, an exception will be thrown whenever the event is emitted.
-</aside>
-
-### Parameters
-
-The RippleAPI constructor optionally takes one argument, an object with the following options:
-
-<%- renderSchema('input/api-options.json') %>
-
-If you omit the `server` parameter, RippleAPI operates [offline](#offline-functionality).
-
-
-### Installation ###
-
-1. Install [Node.js](https://nodejs.org) and [Yarn](https://yarnpkg.com/en/docs/install). Most Linux distros have a package for Node.js; check that it's the version you want.
-2. Use yarn to install RippleAPI:
-      `yarn add ripple-lib`
-
-After you have installed ripple-lib, you can create scripts using the [boilerplate](#boilerplate) and run them using the Node.js executable, typically named `node`:
-
-      `node script.js`

docs/src/combine.md.ejs

@@ -1,24 +0,0 @@
-## combine
-
-`combine(signedTransactions: Array<string>): {signedTransaction: string, id: string}`
-
-Combines signed transactions from multiple accounts for a multisignature transaction. The signed transaction must subsequently be [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema("input/combine.json") %>
-
-### Return Value
-
-This method returns an object with the following structure:
-
-<%- renderSchema("output/sign.json") %>
-
-### Example
-
-```javascript
-const signedTransactions = <%- importFile('test/fixtures/requests/combine.json') %>;
-return api.combine(signedTransactions);
-```
-
-<%- renderFixture("responses/combine.json") %>

docs/src/computeLedgerHash.md.ejs

@@ -1,28 +0,0 @@
-## computeLedgerHash
-
-`computeLedgerHash(ledger: object): string`
-
-Compute the hash of a ledger.
-
-### Parameters
-
-<aside class="notice">
-The parameter to this method has the same structure as the return value of getLedger.
-</aside>
-
-<%- renderSchema('input/compute-ledger-hash.json') %>
-
-### Return Value
-
-This method returns an uppercase hexadecimal string representing the hash of the ledger.
-
-### Example
-
-```javascript
-const ledger = <%- importFile('test/fixtures/requests/compute-ledger-hash.json') %>;
-return api.computeLedgerHash(ledger);
-```
-
-```json
-"F4D865D83EB88C1A1911B9E90641919A1314F36E1B099F8E95FE3B7C77BE3349"
-```

docs/src/connect.md.ejs

@@ -1,17 +0,0 @@
-## connect
-
-`connect(): Promise<void>`
-
-Tells the RippleAPI instance to connect to its rippled server.
-
-### Parameters
-
-This method has no parameters.
-
-### Return Value
-
-This method returns a promise that resolves with a void value when a connection is established.
-
-### Example
-
-See [Boilerplate](#boilerplate) for code sample.

docs/src/deriveAddress.md.ejs

@@ -1,19 +0,0 @@
-## deriveAddress
-
-`deriveAddress(publicKey: string): string`
-
-Derive an XRP Ledger address from a public key.
-
-### Parameters
-
-This method takes one parameter, the public key from which to derive the address.
-
-### Return Value
-
-This method returns a string corresponding to the address derived from the public key.
-
-### Example
-
-```javascript
-var address = api.deriveAddress(public_key);
-```

docs/src/deriveKeypair.md.ejs

@@ -1,21 +0,0 @@
-## deriveKeypair
-
-`deriveKeypair(seed: string): {privateKey: string, publicKey: string}`
-
-Derive a public and private key from a seed.
-
-### Parameters
-
-This method takes one parameter, the seed from which to derive the public and private key.
-
-### Return Value
-
-This method returns an object containing the public and private components of the keypair corresponding to the seed.
-
-### Example
-
-```javascript
-var keypair = api.deriveKeypair(seed)
-var public_key = keypair.publicKey;
-var private_key = keypair.privateKey;
-```

docs/src/disconnect.md.ejs

@@ -1,17 +0,0 @@
-## disconnect
-
-`disconnect(): Promise<void>`
-
-Tells the RippleAPI instance to disconnect from its rippled server.
-
-### Parameters
-
-This method has no parameters.
-
-### Return Value
-
-This method returns a promise that resolves with a void value when a connection is destroyed.
-
-### Example
-
-See [Boilerplate](#boilerplate) for code sample

docs/src/events.md.ejs

@@ -1,81 +0,0 @@
-# API Events
-
-## ledger
-
-This event is emitted whenever a new ledger version is validated on the connected server.
-
-### Return Value
-
-<%- renderSchema('output/ledger-event.json') %>
-
-### Example
-
-```javascript
-api.on('ledger', ledger => {
-  console.log(JSON.stringify(ledger, null, 2));
-});
-```
-
-<%- renderFixture('responses/ledger-event.json') %>
-
-## error
-
-This event is emitted when there is an error on the connection to the server that cannot be associated to a specific request.
-
-### Return Value
-
-The first parameter is a string indicating the error type:
-* `badMessage` - rippled returned a malformed message
-* `websocket` - the websocket library emitted an error
-* one of the error codes found in the [rippled Universal Errors](https://ripple.com/build/rippled-apis/#universal-errors).
-
-The second parameter is a message explaining the error.
-
-The third parameter is:
-* the message that caused the error for `badMessage`
-* the error object emitted for `websocket`
-* the parsed response for rippled errors
-
-### Example
-
-```javascript
-api.on('error', (errorCode, errorMessage, data) => {
-  console.log(errorCode + ': ' + errorMessage);
-});
-```
-
-```
-tooBusy: The server is too busy to help you now.
-```
-
-## connected
-
-This event is emitted after connection successfully opened.
-
-### Example
-
-```javascript
-api.on('connected', () => {
-  console.log('Connection is open now.');
-});
-```
-
-## disconnected
-
-This event is emitted when connection is closed.
-
-### Return Value
-
-The only parameter is a number containing the [close code](https://developer.mozilla.org/en-US/docs/Web/API/CloseEvent) send by the server.
-
-### Example
-
-```javascript
-api.on('disconnected', (code) => {
-  if (code !== 1000) {
-    console.log('Connection is closed due to error.');
-  } else {
-    console.log('Connection is closed normally.');
-  }
-});
-```

docs/src/formatBidsAndAsks.md.ejs

@@ -1,254 +0,0 @@
-## formatBidsAndAsks
-
-`formatBidsAndAsks(orderbookInfo: {base: Issue, counter: Issue}, offers: BookOffer[]): orderbook`
-
-Returns formatted bids and asks, which make up an orderbook.
-
-This is a static method on the `RippleAPI` class.
-
-### Parameters
-
-This method takes two parameters.
-
-1. An `OrderbookInfo` object: `{ base: Issue, counter: Issue }`.
-2. An array of `BookOffer` objects.
-
-### Return Value
-
-This method returns an object with two properties: `bids` and `asks`, each of which is an array of bids (buy orders) or asks (sell orders), respectively. (Note: the structures of `bids` and `asks` are identical.)
-
-Object structure:
-
-<%- renderSchema('output/get-orderbook.json') %>
-
-**Raw order data:** The response includes a `data` property containing the raw order data. This may include `owner_funds`, `Flags`, and other fields.
-
-For details, see the rippled method [book_offers](https://ripple.com/build/rippled-apis/#book-offers).
-
-### Example
-
-```javascript
-const orderbookInfo = {
-  "base": {
-    "currency": "USD",
-    "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-  },
-  "counter": {
-    "currency": "BTC",
-    "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-  }
-};
-
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-
-return Promise.all(
-  [
-    this.api.request('book_offers', {
-      taker_gets: RippleAPI.renameCounterpartyToIssuer(orderbookInfo.base),
-      taker_pays: RippleAPI.renameCounterpartyToIssuer(orderbookInfo.counter),
-      ledger_index: 'validated',
-      limit: 20,
-      taker: address
-    }),
-    this.api.request('book_offers', {
-      taker_gets: RippleAPI.renameCounterpartyToIssuer(orderbookInfo.counter),
-      taker_pays: RippleAPI.renameCounterpartyToIssuer(orderbookInfo.base),
-      ledger_index: 'validated',
-      limit: 20,
-      taker: address
-    })
-  ]
-).then((directOfferResults, reverseOfferResults) => {
-  const directOffers = (directOfferResults ? directOfferResults : []).reduce((acc, res) => acc.concat(res.offers), [])
-  const reverseOffers = (reverseOfferResults ? reverseOfferResults : []).reduce((acc, res) => acc.concat(res.offers), [])
-  const orderbook = RippleAPI.formatBidsAndAsks(orderbookInfo, [...directOffers, ...reverseOffers]);
-  console.log(JSON.stringify(orderbook, null, 2));
-});
-```
-
-```
-{
-  "bids": [
-    {
-      "specification": {
-        "direction": "buy",
-        "quantity": {
-          "currency": "USD",
-          "value": "0.71800168",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        },
-        "totalPrice": {
-          "currency": "BTC",
-          "value": "0.00016708342",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        }
-      },
-      "properties": {
-        "maker": "rUKoQ1Zhn6c8EfPsaVa2Yx5NqaKN1JQSvq",
-        "sequence": 262660,
-        "makerExchangeRate": "4297.264683713081"
-      },
-      "data": {
-        "Account": "rUKoQ1Zhn6c8EfPsaVa2Yx5NqaKN1JQSvq",
-        "BookDirectory": "6EAB7C172DEFA430DBFAD120FDC373B5F5AF8B191649EC98580F4456E6FA8239",
-        "BookNode": "0000000000000000",
-        "Flags": 0,
-        "LedgerEntryType": "Offer",
-        "OwnerNode": "000000000000001D",
-        "PreviousTxnID": "16D75506C6317723FC03543130B5E0AAB13E8AD22514C1DB098BE05771C90447",
-        "PreviousTxnLgrSeq": 43127860,
-        "Sequence": 262660,
-        "TakerGets": {
-          "currency": "BTC",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.00016708342"
-        },
-        "TakerPays": {
-          "currency": "USD",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.71800168"
-        },
-        "index": "DE877FB94EF892A4BCC58DB8CDE063D97AB5133201905DE6C8650B5DEA19E11B",
-        "owner_funds": "0.03358376764081196",
-        "quality": "4297.264683713081"
-      }
-    },
-    {
-      "specification": {
-        "direction": "buy",
-        "quantity": {
-          "currency": "USD",
-          "value": "1.6770875",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        },
-        "totalPrice": {
-          "currency": "BTC",
-          "value": "0.00038681218",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        }
-      },
-      "properties": {
-        "maker": "rpmL45YbZWKgp8AH8EjBSknWo5c8dNuuBM",
-        "sequence": 231459,
-        "makerExchangeRate": "4335.663628792661"
-      },
-      "data": {
-        "Account": "rpmL45YbZWKgp8AH8EjBSknWo5c8dNuuBM",
-        "BookDirectory": "6EAB7C172DEFA430DBFAD120FDC373B5F5AF8B191649EC98580F67435A75B355",
-        "BookNode": "0000000000000000",
-        "Flags": 0,
-        "LedgerEntryType": "Offer",
-        "OwnerNode": "0000000000000001",
-        "PreviousTxnID": "F049EAFDDDA7B99970F77533743D95C9E12A16FE6C56215A0B09C32C4D23163F",
-        "PreviousTxnLgrSeq": 43127094,
-        "Sequence": 231459,
-        "TakerGets": {
-          "currency": "BTC",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.00038681218"
-        },
-        "TakerPays": {
-          "currency": "USD",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "1.6770875"
-        },
-        "index": "3B314A51BD57601CA1509834DF9462037BF4B05AFCC1E1EFD334DB4E2D7B2AA6",
-        "owner_funds": "0.03906802968738533",
-        "quality": "4335.663628792661"
-      }
-    },
-    // ... trimmed for brevity ...
-  ],
-  "asks": [
-    {
-      "specification": {
-        "direction": "sell",
-        "quantity": {
-          "currency": "USD",
-          "value": "0.71085738",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        },
-        "totalPrice": {
-          "currency": "BTC",
-          "value": "0.00016876265",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        }
-      },
-      "properties": {
-        "maker": "rUKoQ1Zhn6c8EfPsaVa2Yx5NqaKN1JQSvq",
-        "sequence": 262664,
-        "makerExchangeRate": "0.0002374071856720401"
-      },
-      "data": {
-        "Account": "rUKoQ1Zhn6c8EfPsaVa2Yx5NqaKN1JQSvq",
-        "BookDirectory": "20294C923E80A51B487EB9547B3835FD483748B170D2D0A451086F34ADB0EA11",
-        "BookNode": "0000000000000000",
-        "Flags": 0,
-        "LedgerEntryType": "Offer",
-        "OwnerNode": "000000000000001D",
-        "PreviousTxnID": "54CE0B2783AF973718FAFA35E864A3C172BE488EBBB6F2852611C6DAC8893BDF",
-        "PreviousTxnLgrSeq": 43127875,
-        "Sequence": 262664,
-        "TakerGets": {
-          "currency": "USD",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.71085738"
-        },
-        "TakerPays": {
-          "currency": "BTC",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.00016876265"
-        },
-        "index": "2D4ED103D6B3FEFA21BC385C53B63359F5678E5AA5429DDE6E1D8FE8B41CD6A8",
-        "owner_funds": "142.8821425048244",
-        "quality": "0.0002374071856720401"
-      }
-    },
-    {
-      "specification": {
-        "direction": "sell",
-        "quantity": {
-          "currency": "USD",
-          "value": "1.6438778",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        },
-        "totalPrice": {
-          "currency": "BTC",
-          "value": "0.00039462656",
-          "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-        }
-      },
-      "properties": {
-        "maker": "rpmL45YbZWKgp8AH8EjBSknWo5c8dNuuBM",
-        "sequence": 231483,
-        "makerExchangeRate": "0.0002400583303698121"
-      },
-      "data": {
-        "Account": "rpmL45YbZWKgp8AH8EjBSknWo5c8dNuuBM",
-        "BookDirectory": "20294C923E80A51B487EB9547B3835FD483748B170D2D0A4510887515B1216C9",
-        "BookNode": "0000000000000000",
-        "Flags": 0,
-        "LedgerEntryType": "Offer",
-        "OwnerNode": "0000000000000001",
-        "PreviousTxnID": "6FA370F52C45F6149482156FF7B4226713AECE991FB7D053F74172CB0B8F24E9",
-        "PreviousTxnLgrSeq": 43127158,
-        "Sequence": 231483,
-        "TakerGets": {
-          "currency": "USD",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "1.6438778"
-        },
-        "TakerPays": {
-          "currency": "BTC",
-          "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
-          "value": "0.00039462656"
-        },
-        "index": "735F9661AD006BA0776859BE371D445555FC0815604603AC056469C16AC84AE3",
-        "owner_funds": "166.0316626329364",
-        "quality": "0.0002400583303698121"
-      }
-    },
-    // ... trimmed for brevity ...
-  ]
-}
-```

docs/src/generateAddress.md.ejs

@@ -1,25 +0,0 @@
-## generateAddress
-
-`generateAddress(options?: object): {address: string, secret: string}`
-
-Deprecated: This method returns a classic address. If you do not need the classic address, use `generateXAddress` instead.
-
-Generate a new XRP Ledger address and corresponding secret.
-
-### Parameters
-
-<%- renderSchema('input/generate-address.json') %>
-
-### Return Value
-
-This method returns an object with the following structure:
-
-<%- renderSchema('output/generate-address.json') %>
-
-### Example
-
-```javascript
-return api.generateAddress();
-```
-
-<%- renderFixture('responses/generate-address.json') %>

docs/src/generateXAddress.md.ejs

@@ -1,23 +0,0 @@
-## generateXAddress
-
-`generateXAddress(options?: object): {address: string, secret: string}`
-
-Generate a new XRP Ledger address and corresponding secret.
-
-### Parameters
-
-<%- renderSchema('input/generate-x-address.json') %>
-
-### Return Value
-
-This method returns an object with the following structure:
-
-<%- renderSchema('output/generate-x-address.json') %>
-
-### Example
-
-```javascript
-return api.generateXAddress();
-```
-
-<%- renderFixture('responses/generate-x-address.json') %>

docs/src/getAccountInfo.md.ejs

@@ -1,25 +0,0 @@
-## getAccountInfo
-
-`getAccountInfo(address: string, options: object): Promise<object>`
-
-Returns information for the specified account. Note: For account data that is modifiable by the user, see [getSettings](#getsettings).
-
-### Parameters
-
-<%- renderSchema('input/get-account-info.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-account-info.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getAccountInfo(address).then(info =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-account-info.json') %>

docs/src/getAccountObjects.md.ejs

@@ -1,34 +0,0 @@
-## getAccountObjects
-
-`getAccountObjects(address: string, options: object): Promise<AccountObjectsResponse>`
-
-Returns objects owned by an account. For an account's trust lines and balances, see `getTrustlines` and `getBalances`.
-
-### Parameters
-
-<%- renderSchema('input/get-account-objects.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-account-objects.json') %>
-
-The types of objects that may be returned include:
-
-* `Offer` objects for orders that are currently live, unfunded, or expired but not yet removed.
-* `RippleState` objects for trust lines where this account's side is not in the default state.
-* A `SignerList` object if the account has multi-signing enabled.
-* `Escrow` objects for held payments that have not yet been executed or canceled.
-* `PayChannel` objects for open payment channels.
-* `Check` objects for pending checks.
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getAccountObjects(address: address).then(objects =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-account-objects.json') %>

docs/src/getBalanceSheet.md.ejs

@@ -1,25 +0,0 @@
-## getBalanceSheet
-
-`getBalanceSheet(address: string, options: object): Promise<object>`
-
-Returns aggregate balances by currency plus a breakdown of assets and obligations for a specified account.
-
-### Parameters
-
-<%- renderSchema('input/get-balance-sheet.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-balance-sheet.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getBalanceSheet(address).then(balanceSheet =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-balance-sheet.json') %>

docs/src/getBalances.md.ejs

@@ -1,25 +0,0 @@
-## getBalances
-
-`getBalances(address: string, options: object): Promise<Array<object>>`
-
-Returns balances for a specified account.
-
-### Parameters
-
-<%- renderSchema('input/get-balances.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of objects with the following structure:
-
-<%- renderSchema('output/get-balances.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getBalances(address).then(balances =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-balances.json') %>

docs/src/getFee.md.ejs

@@ -1,25 +0,0 @@
-## getFee
-
-`getFee(): Promise<string>`
-
-Returns the estimated transaction fee for the rippled server the RippleAPI instance is connected to.
-
-This will use the [feeCushion parameter](#parameters) provided to the RippleAPI constructor, or the default value of `1.2`.
-
-### Parameters
-
-<%- renderSchema('input/get-fee.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with a string-encoded floating point value representing the estimated fee to submit a transaction, expressed in XRP.
-
-### Example
-
-```javascript
-return api.getFee().then(fee => {/* ... */});
-```
-
-```json
-"0.000012"
-```

docs/src/getLedger.md.ejs

@@ -1,24 +0,0 @@
-## getLedger
-
-`getLedger(options: object): Promise<object>`
-
-Returns header information for the specified ledger (or the most recent validated ledger if no ledger is specified). Optionally, all the transactions that were validated in the ledger or the account state information can be returned with the ledger header.
-
-### Parameters
-
-<%- renderSchema('input/get-ledger.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-ledger.json') %>
-
-### Example
-
-```javascript
-return api.getLedger()
-  .then(ledger => {/* ... */});
-```
-
-<%- renderFixture('responses/get-ledger.json') %>

docs/src/getLedgerVersion.md.ejs

@@ -1,26 +0,0 @@
-## getLedgerVersion
-
-`getLedgerVersion(): Promise<number>`
-
-Returns the most recent validated ledger version number known to the connected server.
-
-### Parameters
-
-This method has no parameters.
-
-### Return Value
-
-This method returns a promise that resolves with a positive integer representing the most recent validated ledger version number known to the connected server.
-
-### Example
-
-```javascript
-return api.getLedgerVersion().then(ledgerVersion => {
-  /* ... */
-});
-```
-
-```json
-16869039
-```
-

docs/src/getOrderbook.md.ejs

@@ -1,34 +0,0 @@
-## getOrderbook
-
-`getOrderbook(address: string, orderbook: object, options: object): Promise<object>`
-
-Returns open orders for the specified account. Open orders are orders that have not yet been fully executed and are still in the order book.
-
-**Breaking change:** In ripple-lib 1.1.0 and earlier, orders returned by this method were not sorted correctly. Orders are now sorted correctly, from best to worst.
-
-**See also:** An alternative way to get orderbooks is with `request` and [`formatBidsAndAsks`](#formatbidsandasks).
-
-### Parameters
-
-<%- renderSchema('input/get-orderbook.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure (Note: the structures of `bids` and `asks` are identical):
-
-<%- renderSchema('output/get-orderbook.json') %>
-
-**Raw order data:** The response includes a `data` property containing the raw order data. This may include `owner_funds`, `Flags`, and other fields.
-
-For details, see the rippled method [book_offers](https://ripple.com/build/rippled-apis/#book-offers).
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const orderbook = <%- importFile('test/fixtures/requests/get-orderbook.json') %>;
-return api.getOrderbook(address, orderbook)
-  .then(orderbook => {/* ... */});
-```
-
-<%- renderFixture('responses/get-orderbook.json') %>

docs/src/getOrders.md.ejs

@@ -1,25 +0,0 @@
-## getOrders
-
-`getOrders(address: string, options: object): Promise<Array<object>>`
-
-Returns open orders for the specified account. Open orders are orders that have not yet been fully executed and are still in the order book.
-
-### Parameters
-
-<%- renderSchema('input/get-orders.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of objects with the following structure:
-
-<%- renderSchema('output/get-orders.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getOrders(address).then(orders =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-orders.json') %>

docs/src/getPaths.md.ejs

@@ -1,25 +0,0 @@
-## getPaths
-
-`getPaths(pathfind: object): Promise<Array<object>>`
-
-Finds paths to send a payment. Paths are options for how to route a payment.
-
-### Parameters
-
-<%- renderSchema("input/get-paths.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of objects with the following structure:
-
-<%- renderSchema("output/get-paths.json") %>
-
-### Example
-
-```javascript
-const pathfind = <%- importFile('test/fixtures/requests/getpaths/normal.json') %>;
-return api.getPaths(pathfind)
-  .then(paths => {/* ... */});
-```
-
-<%- renderFixture("responses/get-paths.json") %>

docs/src/getPaymentChannel.md.ejs

@@ -1,26 +0,0 @@
-## getPaymentChannel
-
-`getPaymentChannel(id: string): Promise<object>`
-
-Returns specified payment channel.
-
-### Parameters
-
-<%- renderSchema('input/get-payment-channel.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-payment-channel.json') %>
-
-### Example
-
-```javascript
-const channelId =
-  'E30E709CF009A1F26E0E5C48F7AA1BFB79393764F15FB108BDC6E06D3CBD8415';
-return api.getPaymentChannel(channelId).then(channel =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-payment-channel.json') %>

docs/src/getServerInfo.md.ejs

@@ -1,23 +0,0 @@
-## getServerInfo
-
-`getServerInfo(): Promise<object>`
-
-Get status information about the server that the RippleAPI instance is connected to.
-
-### Parameters
-
-This method has no parameters.
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<%- renderSchema('output/get-server-info.json') %>
-
-### Example
-
-```javascript
-return api.getServerInfo().then(info => {/* ... */});
-```
-
-<%- renderFixture('responses/get-server-info.json') %>

docs/src/getSettings.md.ejs

@@ -1,25 +0,0 @@
-## getSettings
-
-`getSettings(address: string, options: object): Promise<object>`
-
-Returns settings for the specified account. Note: For account data that is not modifiable by the user, see [getAccountInfo](#getaccountinfo).
-
-### Parameters
-
-<%- renderSchema('input/get-settings.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of objects with the following structure (Note: all fields are optional as they will not be shown if they are set to their default value):
-
-<%- renderSchema('output/get-settings.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getSettings(address).then(settings =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/get-settings.json') %>

docs/src/getTransaction.md.ejs

@@ -1,26 +0,0 @@
-## getTransaction
-
-`getTransaction(id: string, options: object): Promise<object>`
-
-Retrieves a transaction by its [Transaction ID](#transaction-id).
-
-### Parameters
-
-<%- renderSchema('input/get-transaction.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with a transaction object containing the following fields.
-
-<%- renderSchema('output/get-transaction.json') %>
-
-### Example
-
-```javascript
-const id = '01CDEAA89BF99D97DFD47F79A0477E1DCC0989D39F70E8AACBFE68CC83BD1E94';
-return api.getTransaction(id).then(transaction => {
-  /* ... */
-});
-```
-
-<%- renderFixture('responses/get-transaction-payment.json') %>

docs/src/getTransactions.md.ejs

@@ -1,24 +0,0 @@
-## getTransactions
-
-`getTransactions(address: string, options: object): Promise<Array<object>>`
-
-Retrieves historical transactions of an account.
-
-### Parameters
-
-<%- renderSchema('input/get-transactions.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of transaction object in the same format as [getTransaction](#gettransaction).
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getTransactions(address).then(transaction => {
-  /* ... */
-});
-```
-
-<%- renderFixture('responses/get-transactions.json') %>

docs/src/getTrustlines.md.ejs

@@ -1,25 +0,0 @@
-## getTrustlines
-
-`getTrustlines(address: string, options: object): Promise<Array<object>>`
-
-Returns trustlines for a specified account.
-
-### Parameters
-
-<%- renderSchema("input/get-trustlines.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an array of objects with the following structure.
-
-<%- renderSchema("output/get-trustlines.json") %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.getTrustlines(address).then(trustlines =>
-  {/* ... */});
-```
-
-<%- renderFixture("responses/get-trustlines.json") %>

docs/src/hasNextPage.md.ejs

@@ -1,27 +0,0 @@
-## hasNextPage
-
-`hasNextPage(currentResponse): boolean`
-
-Returns `true` when there are more pages available.
-
-When there are more results than contained in the response, the response includes a `marker` field. You can use this convenience method, or check for `marker` yourself.
-
-See [Markers and Pagination](https://ripple.com/build/rippled-apis/#markers-and-pagination).
-
-### Return Value
-
-This method returns `true` if `currentResponse` includes a `marker`.
-
-### Example
-
-```javascript
-return api.request('ledger_data', {
-  ledger_index: 'validated'
-}).then(response => {
-  /* Do something useful with response */
-
-  if (api.hasNextPage(response)) {
-    /* There are more pages available */
-  }
-}).catch(console.error);
-```

docs/src/index.md.ejs

@@ -1,70 +0,0 @@
-<%- include('introduction.md.ejs') %>
-<%- include('boilerplate.md.ejs') %>
-<%- include('offline.md.ejs') %>
-<%- include('basictypes.md.ejs') %>
-<%- include('transactions.md.ejs') %>
-<%- include('specifications.md.ejs') %>
-<%- include('rippledAPIs.md.ejs') %>
-<%- include('request.md.ejs') %>
-<%- include('hasNextPage.md.ejs') %>
-<%- include('requestNextPage.md.ejs') %>
-
-<%- include('staticMethods.md.ejs') %>
-<%- include('renameCounterpartyToIssuer.md.ejs') %>
-<%- include('formatBidsAndAsks.md.ejs') %>
-
-<%- include('methods.md.ejs') %>
-<%- include('connect.md.ejs') %>
-<%- include('disconnect.md.ejs') %>
-<%- include('isConnected.md.ejs') %>
-<%- include('getServerInfo.md.ejs') %>
-<%- include('getFee.md.ejs') %>
-<%- include('getLedgerVersion.md.ejs') %>
-<%- include('getTransaction.md.ejs') %>
-<%- include('getTransactions.md.ejs') %>
-<%- include('getTrustlines.md.ejs') %>
-<%- include('getBalances.md.ejs') %>
-<%- include('getBalanceSheet.md.ejs') %>
-<%- include('getPaths.md.ejs') %>
-<%- include('getOrders.md.ejs') %>
-<%- include('getOrderbook.md.ejs') %>
-<%- include('getSettings.md.ejs') %>
-<%- include('getAccountInfo.md.ejs') %>
-<%- include('getAccountObjects.md.ejs') %>
-<%- include('getPaymentChannel.md.ejs') %>
-<%- include('getLedger.md.ejs') %>
-<%- include('parseAccountFlags.md.ejs') %>
-<%- include('prepareTransaction.md.ejs') %>
-<%- include('preparePayment.md.ejs') %>
-<%- include('prepareTrustline.md.ejs') %>
-<%- include('prepareOrder.md.ejs') %>
-<%- include('prepareOrderCancellation.md.ejs') %>
-<%- include('prepareSettings.md.ejs') %>
-<%- include('prepareEscrowCreation.md.ejs') %>
-<%- include('prepareEscrowCancellation.md.ejs') %>
-<%- include('prepareEscrowExecution.md.ejs') %>
-<%- include('preparePaymentChannelCreate.md.ejs') %>
-<%- include('preparePaymentChannelClaim.md.ejs') %>
-<%- include('preparePaymentChannelFund.md.ejs') %>
-<%- include('prepareCheckCreate.md.ejs') %>
-<%- include('prepareCheckCancel.md.ejs') %>
-<%- include('prepareCheckCash.md.ejs') %>
-<%- include('prepareTicketCreate.md.ejs') %>
-<%- include('sign.md.ejs') %>
-<%- include('combine.md.ejs') %>
-<%- include('submit.md.ejs') %>
-<%- include('generateXAddress.md.ejs') %>
-<%- include('generateAddress.md.ejs') %>
-<%- include('isValidAddress.md.ejs') %>
-<%- include('isValidSecret.md.ejs') %>
-<%- include('deriveKeypair.md.ejs') %>
-<%- include('deriveAddress.md.ejs') %>
-<%- include('signPaymentChannelClaim.md.ejs') %>
-<%- include('verifyPaymentChannelClaim.md.ejs') %>
-<%- include('computeLedgerHash.md.ejs') %>
-<%- include('xrpToDropsAndDropsToXrp.md.ejs') %>
-<%- include('iso8601ToRippleTime.md.ejs') %>
-<%- include('rippleTimeToISO8601.md.ejs') %>
-<%- include('txFlags.md.ejs') %>
-<%- include('schemaValidator.md.ejs') %>
-<%- include('events.md.ejs') %>

docs/src/introduction.md.ejs

@@ -1,15 +0,0 @@
-# Introduction
-
-RippleAPI (ripple-lib) is the official client library to the XRP Ledger. Currently, RippleAPI is only available in JavaScript/TypeScript.
-
-Using RippleAPI, you can:
-
-* [Query transactions from the XRP Ledger history](#gettransaction)
-* [Sign](#sign) transactions securely without connecting to any server
-* [Submit](#submit) transactions to the XRP Ledger, including [Payments](#payment), [Orders](#order), [Settings changes](#settings), and [other types](#transaction-types)
-* [Generate a new XRP Ledger Address](#generateaddress)
-* ... and [much more](#api-methods).
-
-This page contains documentation for ripple-lib. To use ripple-lib with npm/yarn, begin with the [Getting Started](https://github.com/ripple/ripple-lib#getting-started) steps.
-
-**What is ripple-lib used for?** Here's a [list of applications that use `ripple-lib`](https://github.com/ripple/ripple-lib/blob/develop/APPLICATIONS.md). Open a PR to add your app or project to the list!

docs/src/isConnected.md.ejs

@@ -1,23 +0,0 @@
-## isConnected
-
-`isConnected(): boolean`
-
-Checks if the RippleAPI instance is connected to its rippled server.
-
-### Parameters
-
-This method has no parameters.
-
-### Return Value
-
-This method returns `true` if connected and `false` if not connected.
-
-### Example
-
-```javascript
-return api.isConnected();
-```
-
-```json
-true
-```

docs/src/isValidAddress.md.ejs

@@ -1,19 +0,0 @@
-## isValidAddress
-
-`isValidAddress(address: string): boolean`
-
-Checks if the specified string contains a valid address. X-addresses are considered valid with ripple-lib v1.4.0 and higher.
-
-### Parameters
-
-This method takes one parameter, the address to validate.
-
-### Return Value
-
-This method returns `true` if the address is valid and `false` if it is not.
-
-### Example
-
-```javascript
-return api.isValidAddress("address")
-```

docs/src/isValidSecret.md.ejs

@@ -1,19 +0,0 @@
-## isValidSecret
-
-`isValidSecret(secret: string): boolean`
-
-Checks if the specified string contains a valid secret.
-
-### Parameters
-
-This method takes one parameter, the secret which to validate.
-
-### Return Value
-
-This method returns `true` if the secret is valid and `false` if it is not.
-
-### Example
-
-```javascript
-return api.isValidSecret("secret")
-```

docs/src/iso8601ToRippleTime.md.ejs

@@ -1,27 +0,0 @@
-## iso8601ToRippleTime
-
-`iso8601ToRippleTime(iso8601: string): number`
-
-This method parses a string representation of a date, and returns the number of seconds since the "Ripple Epoch" of January 1, 2000 (00:00 UTC).
-
-The Ripple Epoch is 946684800 seconds after the Unix Epoch.
-
-This method is useful for creating timestamps to use with the rippled APIs. The rippled APIs represent time as an unsigned integer of the number of seconds since the Ripple Epoch.
-
-### Parameters
-
-`iso8601`: A string representing a date and time. This string is parsed using JavaScript's `Date.parse()` method.
-
-### Return Value
-
-The number of seconds since the Ripple Epoch.
-
-### Example
-
-```javascript
-api.iso8601ToRippleTime('2017-02-17T15:04:57Z');
-```
-
-```json
-540659097
-```

docs/src/methods.md.ejs

@@ -1 +0,0 @@
-# API Methods

docs/src/offline.md.ejs

@@ -1,27 +0,0 @@
-## Offline functionality
-
-RippleAPI can also function without internet connectivity. This can be useful in order to generate secrets and sign transactions from a secure, isolated machine.
-
-To instantiate RippleAPI in offline mode, use the following boilerplate code:
-
-```javascript
-const RippleAPI = require('ripple-lib').RippleAPI;
-
-const api = new RippleAPI();
-/* insert code here */
-```
-
-Methods that depend on the state of the XRP Ledger are unavailable in offline mode. To prepare transactions offline, you **must** specify  the `fee`, `sequence`, and `maxLedgerVersion` parameters in the [transaction instructions](#transaction-instructions). You can use the following methods while offline:
-
-* [preparePayment](#preparepayment)
-* [prepareTrustline](#preparetrustline)
-* [prepareOrder](#prepareorder)
-* [prepareOrderCancellation](#prepareordercancellation)
-* [prepareSettings](#preparesettings)
-* [prepareEscrowCreation](#prepareescrowcreation)
-* [prepareEscrowCancellation](#prepareescrowcancellation)
-* [prepareEscrowExecution](#prepareescrowexecution)
-* [sign](#sign)
-* [generateAddress](#generateaddress)
-* [generateXAddress](#generatexaddress)
-* [computeLedgerHash](#computeledgerhash)

docs/src/parseAccountFlags.md.ejs

@@ -1,35 +0,0 @@
-## parseAccountFlags
-
-`parseAccountFlags(Flags: number): object`
-
-Parse an `AccountRoot` object's [`Flags`](https://developers.ripple.com/accountroot.html#accountroot-flags).
-
-### Parameters
-
-This method takes one parameter, the AccountRoot `Flags` number to parse. Note that flags have different mappings on other types of objects or in transactions such as AccountSet.
-
-### Return Value
-
-This method returns an object with containing a key for each AccountRoot flag known to this version of RippleAPI. Each flag has a boolean value of `true` or `false`.
-
-### Example
-
-```javascript
-const account_info = await api.request('account_info', {account: 'rKsdkGhyZH6b2Zzd5hNnEqSv2wpznn4n6N'})
-const flags = api.parseAccountFlags(account_info.account_data.Flags)
-console.log(JSON.stringify(flags, null, 2))
-```
-
-```json
-{
-  "passwordSpent": false,
-  "requireDestinationTag": false,
-  "requireAuthorization": false,
-  "depositAuth": true,
-  "disallowIncomingXRP": false,
-  "disableMasterKey": false,
-  "noFreeze": false,
-  "globalFreeze": false,
-  "defaultRipple": false
-}
-```

docs/src/prepareCheckCancel.md.ejs

@@ -1,30 +0,0 @@
-## prepareCheckCancel
-
-`prepareCheckCancel(address: string, checkCancel: object, instructions: object): Promise<object>`
-
-Prepare a Check cancellation transaction. This cancels an unredeemed Check, removing it from the ledger without sending any money. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-check-cancel.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const checkCancel = <%- importFile('test/fixtures/requests/prepare-check-cancel.json') %>;
-return api.prepareCheckCancel(address, checkCancel).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-check-cancel.json') %>

docs/src/prepareCheckCash.md.ejs

@@ -1,30 +0,0 @@
-## prepareCheckCash
-
-`prepareCheckCash(address: string, checkCash: object, instructions: object): Promise<object>`
-
-Prepare a Check cashing transaction. This redeems a Check to receive up to the amount authorized by the corresponding CheckCreate transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-check-cash.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const checkCash = <%- importFile('test/fixtures/requests/prepare-check-cash-amount.json') %>;
-return api.prepareCheckCash(address, checkCash).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-check-cash-amount.json') %>

docs/src/prepareCheckCreate.md.ejs

@@ -1,30 +0,0 @@
-## prepareCheckCreate
-
-`prepareCheckCreate(address: string, checkCreate: object, instructions: object): Promise<object>`
-
-Prepare a Check creation transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-check-create.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const checkCreate = <%- importFile('test/fixtures/requests/prepare-check-create.json') %>;
-return api.prepareCheckCreate(address, checkCreate).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-check-create.json') %>

docs/src/prepareEscrowCancellation.md.ejs

@@ -1,30 +0,0 @@
-## prepareEscrowCancellation
-
-`prepareEscrowCancellation(address: string, escrowCancellation: object, instructions: object): Promise<object>`
-
-Prepare an escrow cancellation transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-escrow-cancellation.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const escrowCancellation = <%- importFile('test/fixtures/requests/prepare-escrow-cancellation.json') %>;
-return api.prepareEscrowCancellation(address, escrowCancellation).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-escrow-cancellation.json') %>

docs/src/prepareEscrowCreation.md.ejs

@@ -1,36 +0,0 @@
-## prepareEscrowCreation
-
-`prepareEscrowCreation(address: string, escrowCreation: object, instructions: object): Promise<object>`
-
-Prepare an escrow creation transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-escrow-creation.json') %>
-
-This is a convenience method for generating the EscrowCreate JSON used by rippled, so the same restrictions apply.
-
-Field mapping: `allowCancelAfter` is equivalent to rippled's `CancelAfter`; `allowExecuteAfter` is equivalent to `FinishAfter`. At the `allowCancelAfter` time, the escrow is considered expired. This means that the funds can only be returned to the sender. At the `allowExecuteAfter` time, the escrow is permitted to be released to the recipient (if the `condition` is fulfilled).
-
-Note that `allowCancelAfter` must be chronologically later than `allowExecuteAfter`.
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const escrowCreation = <%- importFile('test/fixtures/requests/prepare-escrow-creation.json') %>;
-return api.prepareEscrowCreation(address, escrowCreation).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-escrow-creation.json') %>

docs/src/prepareEscrowExecution.md.ejs

@@ -1,30 +0,0 @@
-## prepareEscrowExecution
-
-`prepareEscrowExecution(address: string, escrowExecution: object, instructions: object): Promise<object>`
-
-Prepare an escrow execution transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-escrow-execution.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const escrowExecution = <%- importFile('test/fixtures/requests/prepare-escrow-execution.json') %>;
-return api.prepareEscrowExecution(address, escrowExecution).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-escrow-execution.json') %>

docs/src/prepareOrder.md.ejs

@@ -1,32 +0,0 @@
-## prepareOrder
-
-`prepareOrder(address: string, order: object, instructions: object): Promise<object>`
-
-Prepare an order transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-order.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-
-// Buy 10.10 USD (of the specified issuer) for 2.0 XRP (2000000 drops), fill or kill.
-const order = <%- importFile('test/fixtures/requests/prepare-order.json') %>;
-return api.prepareOrder(address, order)
-  .then(prepared => {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-order.json') %>

docs/src/prepareOrderCancellation.md.ejs

@@ -1,30 +0,0 @@
-## prepareOrderCancellation
-
-`prepareOrderCancellation(address: string, orderCancellation: object, instructions: object): Promise<object>`
-
-Prepare an order cancellation transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema("input/prepare-order-cancellation.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema("output/prepare.json") %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const orderCancellation = {orderSequence: 123};
-return api.prepareOrderCancellation(address, orderCancellation)
-  .then(prepared => {/* ... */});
-```
-
-<%- renderFixture("responses/prepare-order-cancellation.json") %>

docs/src/preparePayment.md.ejs

@@ -1,33 +0,0 @@
-## preparePayment
-
-`preparePayment(address: string, payment: object, instructions: object): Promise<object>`
-
-Prepare a payment transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema("input/prepare-payment.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema("output/prepare.json") %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const payment = <%- importFile('test/fixtures/requests/prepare-payment.json') %>;
-return api.preparePayment(address, payment).then(prepared => {
-    /* ... */
-  }).catch(error => {
-    /* ... as with all prepare* methods, use a Promise catch block to handle errors ... */
-  })
-```
-
-<%- renderFixture("responses/prepare-payment.json") %>

docs/src/preparePaymentChannelClaim.md.ejs

@@ -1,30 +0,0 @@
-## preparePaymentChannelClaim
-
-`preparePaymentChannelClaim(address: string, paymentChannelClaim: object, instructions: object): Promise<object>`
-
-Prepare a payment channel claim transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-payment-channel-claim.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const paymentChannelClaim = <%- importFile('test/fixtures/requests/prepare-payment-channel-claim.json') %>;
-return api.preparePaymentChannelClaim(address, paymentChannelClaim).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-payment-channel-claim.json') %>

docs/src/preparePaymentChannelCreate.md.ejs

@@ -1,30 +0,0 @@
-## preparePaymentChannelCreate
-
-`preparePaymentChannelCreate(address: string, paymentChannelCreate: object, instructions: object): Promise<object>`
-
-Prepare a payment channel creation transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-payment-channel-create.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const paymentChannelCreate = <%- importFile('test/fixtures/requests/prepare-payment-channel-create.json') %>;
-return api.preparePaymentChannelCreate(address, paymentChannelCreate).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-payment-channel-create.json') %>

docs/src/preparePaymentChannelFund.md.ejs

@@ -1,30 +0,0 @@
-## preparePaymentChannelFund
-
-`preparePaymentChannelFund(address: string, paymentChannelFund: object, instructions: object): Promise<object>`
-
-Prepare a payment channel fund transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-payment-channel-fund.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const paymentChannelFund = <%- importFile('test/fixtures/requests/prepare-payment-channel-fund.json') %>;
-return api.preparePaymentChannelFund(address, paymentChannelFund).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture('responses/prepare-payment-channel-fund.json') %>

docs/src/prepareSettings.md.ejs

@@ -1,30 +0,0 @@
-## prepareSettings
-
-`prepareSettings(address: string, settings: object, instructions: object): Promise<object>`
-
-Prepare a settings transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema('input/prepare-settings.json') %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema('output/prepare.json') %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const settings = <%- importFile('test/fixtures/requests/prepare-settings.json') %>;
-return api.prepareSettings(address, settings)
-  .then(prepared => {/* ... */});
-```
-
-<%- renderFixture('requests/prepare-settings.json') %>

docs/src/prepareTicketCreate.md.ejs

@@ -1,34 +0,0 @@
-## prepareTicketCreate
-
-`prepareTicketCreate(address: string, ticketCount: number, instructions: object): Promise<object>`
-
-Prepare a ticket transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-Ticket functionality requires the [TicketBatch amendment](https://github.com/ripple/xrpl-dev-portal/issues/898). As of 2020-11-24, this amendment is not activated on the Mainnet, Testnet, or Devnet.
-
-### Parameters
-
-<%- renderSchema("input/prepare-ticket-create.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema("output/prepare.json") %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-return api.prepareTicketCreate(address, 2).then(prepared => {
-    /* ... */
-  }).catch(error => {
-    /* ... as with all prepare* methods, use a Promise catch block to handle errors ... */
-  })
-```
-
-<%- renderFixture("responses/prepare-ticket-create.json") %>

docs/src/prepareTransaction.md.ejs

@@ -1,50 +0,0 @@
-## prepareTransaction
-
-`prepareTransaction(transaction: object, instructions: object): Promise<object>`
-
-Prepare a transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-This method works with any of [the transaction types supported by rippled](https://developers.ripple.com/transaction-types.html).
-
-Notably, this is the preferred method for preparing `DepositPreauth` or `AccountDelete` transactions.
-
-### Parameters
-
-Name | Type | Description
----- | ---- | -----------
-transaction | [transaction](https://developers.ripple.com/transaction-formats.html) | The specification (JSON) of the transaction to prepare. Set `Account` to the address of the account that is creating the transaction. You may omit auto-fillable fields like `Fee`, `Flags`, and `Sequence` to have them set automatically.
-instructions | [instructions](#transaction-instructions) | *Optional* Instructions for executing the transaction.
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema("output/prepare.json") %>
-
-### Example
-
-```javascript
-async function preparedPreauth() {
-  const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-  return api.prepareTransaction({
-    TransactionType: 'DepositPreauth',
-    Account: address,
-    Authorize: 'rMyVso4p83khNyHdV1m1PggV9QNadCj8wM'
-  });
-}
-```
-
-```javascript
-{
-  txJSON: '{"TransactionType":"DepositPreauth","Account":"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59","Authorize":"rMyVso4p83khNyHdV1m1PggV9QNadCj8wM","Flags":2147483648,"LastLedgerSequence":13561714,"Fee":"12","Sequence":1}',
-  instructions: {
-    fee: '0.000012',
-    sequence: 1,
-    maxLedgerVersion: 13561714
-  }
-}
-```

docs/src/prepareTrustline.md.ejs

@@ -1,30 +0,0 @@
-## prepareTrustline
-
-`prepareTrustline(address: string, trustline: object, instructions: object): Promise<object>`
-
-Prepare a trustline transaction. The prepared transaction must subsequently be [signed](#sign) and [submitted](#submit).
-
-### Parameters
-
-<%- renderSchema("input/prepare-trustline.json") %>
-
-### Return Value
-
-This method returns a promise that resolves with an object with the following structure:
-
-<aside class="notice">
-All "prepare*" methods have the same return type.
-</aside>
-
-<%- renderSchema("output/prepare.json") %>
-
-### Example
-
-```javascript
-const address = 'r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59';
-const trustline = <%- importFile('test/fixtures/requests/prepare-trustline.json') %>;
-return api.prepareTrustline(address, trustline).then(prepared =>
-  {/* ... */});
-```
-
-<%- renderFixture("responses/prepare-trustline.json") %>

docs/src/renameCounterpartyToIssuer.md.ejs

@@ -1,37 +0,0 @@
-## renameCounterpartyToIssuer
-
-`renameCounterpartyToIssuer(issue: {currency: string, counterparty: address}): {currency: string, issuer: address}`
-
-Returns an object with the `counterparty` field renamed to `issuer`. This is useful because RippleAPI generally uses the name `counterparty` while the rippled API generally uses the name `issuer`.
-
-This is a static method on the `RippleAPI` class.
-
-### Parameters
-
-This method takes one parameter, an object with a `counterparty` field.
-
-### Return Value
-
-This method returns a new object similar to the source object, but with `issuer` instead of `counterparty`.
-
-### Example
-
-```javascript
-const orderbookInfo = {
-  "base": {
-    "currency": "USD",
-    "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-  },
-  "counter": {
-    "currency": "BTC",
-    "counterparty": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
-  }
-};
-console.log(RippleAPI.renameCounterpartyToIssuer(orderbookInfo.base))
-console.log(RippleAPI.renameCounterpartyToIssuer(orderbookInfo.counter))
-```
-
-```
-{ currency: 'USD', issuer: 'rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' }
-{ currency: 'BTC', issuer: 'rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B' }
-```

docs/src/request.md.ejs

@@ -1,27 +0,0 @@
-## request
-
-`request(command: string, options: object): Promise<object>`
-
-Returns the response from invoking the specified command, with the specified options, on the connected rippled server.
-
-Refer to [rippled APIs](https://ripple.com/build/rippled-apis/) for commands and options. All XRP amounts must be specified in drops. One drop is equal to 0.000001 XRP. See [Specifying Currency Amounts](https://ripple.com/build/rippled-apis/#specifying-currency-amounts).
-
-Most commands return data for the `current` (in-progress, open) ledger by default. Do not rely on this. Always specify a ledger version in your request. In the example below, the 'validated' ledger is requested, which is the most recent ledger that has been validated by the whole network. See [Specifying Ledgers](https://xrpl.org/basic-data-types.html#specifying-ledgers).
-
-### Return Value
-
-This method returns a promise that resolves with the response from rippled.
-
-### Example
-
-```javascript
-// Replace 'ledger' with your desired rippled command
-return api.request('ledger', {
-  ledger_index: 'validated'
-}).then(response => {
-  /* Do something useful with response */
-  console.log(JSON.stringify(response, null, 2))
-}).catch(console.error);
-```
-
-<%- renderFixture('responses/ledger.json') %>

docs/src/requestNextPage.md.ejs

@@ -1,29 +0,0 @@
-## requestNextPage
-
-`requestNextPage(command: string, params: object = {}, currentResponse: object): Promise<object>`
-
-Requests the next page of data.
-
-You can use this convenience method, or include `currentResponse.marker` in `params` yourself, when using `request`.
-
-See [Markers and Pagination](https://ripple.com/build/rippled-apis/#markers-and-pagination).
-
-### Return Value
-
-This method returns a promise that resolves with the next page of data from rippled.
-
-If the response does not have a next page, the promise will reject with `new errors.NotFoundError('response does not have a next page')`.
-
-### Example
-
-```javascript
-const command = 'ledger_data'
-const params = {
-  ledger_index: 'validated'
-}
-return api.request(command, params).then(response => {
-  return api.requestNextPage(command, params, response)
-}).then(response_page_2 => {
-  /* Do something useful with second page of response */
-}).catch(console.error);
-```

docs/src/rippleTimeToISO8601.md.ejs

@@ -1,27 +0,0 @@
-## rippleTimeToISO8601
-
-`rippleTimeToISO8601(rippleTime: number): string`
-
-This method takes the number of seconds since the "Ripple Epoch" of January 1, 2000 (00:00 UTC) and returns a string representation of a date.
-
-The Ripple Epoch is 946684800 seconds after the Unix Epoch.
-
-This method is useful for interpreting timestamps returned by the rippled APIs. The rippled APIs represent time as an unsigned integer of the number of seconds since the Ripple Epoch.
-
-### Parameters
-
-`rippleTime`: A number of seconds since the Ripple Epoch.
-
-### Return Value
-
-A string representing a date and time, created by calling a `Date` object's `toISOString()` method.
-
-### Example
-
-```javascript
-api.rippleTimeToISO8601(540659097);
-```
-
-```json
-'2017-02-17T15:04:57.000Z'
-```

docs/src/rippledAPIs.md.ejs

@@ -1,70 +0,0 @@
-# rippled APIs
-
-ripple-lib relies on [rippled APIs](https://ripple.com/build/rippled-apis/) for online functionality. In addition to ripple-lib's own methods, you can also access rippled APIs through ripple-lib. Use the `request()`, `hasNextPage()`, and `requestNextPage()` methods:
-
-* Use `request()` to issue any `rippled` command, including `account_currencies`, `subscribe`, and `unsubscribe`. [Full list of API Methods](https://ripple.com/build/rippled-apis/#api-methods).
-* Use `hasNextPage()` to determine whether a response has more pages. This is true when the response includes a [`marker` field](https://ripple.com/build/rippled-apis/#markers-and-pagination).
-* Use `requestNextPage()` to request the next page of data.
-
-When using rippled APIs:
-
-* [Specify XRP amounts in drops](https://developers.ripple.com/basic-data-types.html#specifying-currency-amounts).
-* [Specify timestamps as the number of seconds since the "Ripple Epoch"](https://developers.ripple.com/basic-data-types.html#specifying-time).
-* Instead of `counterparty`, use `issuer`.
-
-## Listening to streams
-
-The `rippled` server can push updates to your client when various events happen. Refer to [Subscriptions in the `rippled` API docs](https://developers.ripple.com/subscription-methods.html) for details.
-
-Note that the `streams` parameter for generic streams takes an array. For example, to subscribe to the `validations` stream, use `{ streams: [ 'validations' ] }`.
-
-The string names of some generic streams to subscribe to are in the table below. (Refer to `rippled` for an up-to-date list of streams.)
-
-Type | Description
----- | -----------
-`server` | Sends a message whenever the status of the `rippled` server (for example, network connectivity) changes.
-`ledger` | Sends a message whenever the consensus process declares a new validated ledger.
-`transactions` | Sends a message whenever a transaction is included in a closed ledger.
-`transactions_proposed` | Sends a message whenever a transaction is included in a closed ledger, as well as some transactions that have not yet been included in a validated ledger and may never be. Not all proposed transactions appear before validation. Even some transactions that don't succeed are included in validated ledgers because they take the anti-spam transaction fee.
-`validations` | Sends a message whenever the server receives a validation message, also called a validation vote, regardless of whether the server trusts the validator.
-`manifests` | Sends a message whenever the server receives a manifest.
-`peer_status` | (Admin-only) Information about connected peer `rippled` servers, especially with regards to the consensus process.
-
-When you subscribe to a stream, you must also listen to the relevant message type(s). Some of the available message types are in the table below. (Refer to `rippled` for an up-to-date list of message types.)
-
-Type | Description
----- | -----------
-`ledgerClosed` | Sent by the `ledger` stream when the consensus process declares a new fully validated ledger. The message identifies the ledger and provides some information about its contents.
-`validationReceived` | Sent by the `validations` stream when the server receives a validation message, also called a validation vote, regardless of whether the server trusts the validator.
-`manifestReceived` | Sent by the `manifests` stream when the server receives a manifest.
-`transaction` | Sent by many subscriptions including `transactions`, `transactions_proposed`, `accounts`, `accounts_proposed`, and `book` (Order Book). See [Transaction Streams](https://xrpl.org/subscribe.html#transaction-streams) for details.
-`peerStatusChange` | (Admin-only) Reports a large amount of information on the activities of other `rippled` servers to which the server is connected.
-`path_find` | Asynchronous follow-up response to the currently open path\_find request. See [rippled path\_find method](https://xrpl.org/path_find.html) for details.
-
-To register your listener function, use `connection.on(type, handler)`.
-
-Here is an example of listening for transactions on given account(s):
-```
-const account = 'rf1BiGeXwwQoi8Z2ueFYTEXSwuJYfV2Jpn' // Replace with the account you want notifications for
-api.connect().then(() => {
-
-  // 'transaction' can be replaced with the relevant `type` from the table above
-  api.connection.on('transaction', (event) => {
-
-      // Do something useful with `event`
-      console.log(JSON.stringify(event, null, 2))
-  })
-
-  api.request('subscribe', {
-      accounts: [ account ]
-  }).then(response => {
-      console.log('Successfully subscribed')
-  }).catch(error => {
-      // Handle `error`
-  })
-})
-```
-
-The subscription ends when you unsubscribe or the WebSocket connection is closed.
-
-For full details, see [rippled Subscriptions](https://ripple.com/build/rippled-apis/#subscriptions).

docs/src/schemaValidator.md.ejs

@@ -1,35 +0,0 @@
-## schemaValidator
-
-Unlike the rest of the ripple-lib API, schemaValidator is a static object on RippleAPI. It provides utility methods that do not use a server.
-
-## schemaValidate
-
-`RippleAPI.schemaValidator.schemaValidate(schemaName: string, object: any): void`
-
-This method checks an object for conformance to a specified schema. It does not return anything, but will throw a `ValidationError` if the object does not conform to the schema.
-
-### Example
-
-```javascript
-RippleAPI.schemaValidator.schemaValidate('sign', {
-    signedTransaction: '12000322800000002400000017201B0086955368400000000000000C732102F89EAEC7667B30F33D0687BBA86C3FE2A08CCA40A9186C5BDE2DAA6FA97A37D874473045022100BDE09A1F6670403F341C21A77CF35BA47E45CDE974096E1AA5FC39811D8269E702203D60291B9A27F1DCABA9CF5DED307B4F23223E0B6F156991DB601DFB9C41CE1C770A726970706C652E636F6D81145E7B112523F68D2F5E879DB4EAC51C6698A69304',
-    id: '02ACE87F1996E3A23690A5BB7F1774BF71CCBA68F79805831B42ABAD5913D6F4'
-})
-```
-
-```json
-undefined
-```
-
-If the object is valid (conforms to the schema), nothing is returned. Otherwise, `schemaValidate` throws an error:
-
-```javascript
-RippleAPI.schemaValidator.schemaValidate('sign', {
-    signedTransaction: '12000322800000002400000017201B0086955368400000000000000C732102F89EAEC7667B30F33D0687BBA86C3FE2A08CCA40A9186C5BDE2DAA6FA97A37D874473045022100BDE09A1F6670403F341C21A77CF35BA47E45CDE974096E1AA5FC39811D8269E702203D60291B9A27F1DCABA9CF5DED307B4F23223E0B6F156991DB601DFB9C41CE1C770A726970706C652E636F6D81145E7B112523F68D2F5E879DB4EAC51C6698A69304',
-    id: '123'
-})
-```
-
-```
-[ValidationError(instance.id does not match pattern "^[A-F0-9]{64}$")]
-```

docs/src/sign.md.ejs

@@ -1,123 +0,0 @@
-## sign
-
-```
-sign(txJSON: string, secret: string, options: object): {signedTransaction: string, id: string}
-sign(txJSON: string, keypair: object, options: object): {signedTransaction: string, id: string}
-```
-
-Sign a prepared transaction. The signed transaction must subsequently be [submitted](#submit).
-
-This method can sign any of [the transaction types supported by ripple-binary-codec](https://github.com/ripple/ripple-binary-codec/blob/cfcde79c19c359e9a0466d7bc3dc9a3aef47bb99/src/enums/definitions.json#L1637). When a new transaction type is added to the XRP Ledger, it will be unrecognized until `ripple-binary-codec` is updated. If you try to sign an unrecognized transaction type, this method throws an error similar to the following:
-
-`Error: [TRANSACTION_TYPE] is not a valid name or ordinal for TransactionType`
-
-### Parameters
-
-<%- renderSchema("input/sign.json") %>
-
-When this method is used for multisigning, the `options` parameter is required. See the multisigning example in this section for more details.
-
-### Return Value
-
-This method returns an object with the following structure:
-
-<%- renderSchema("output/sign.json") %>
-
-### Example
-
-```javascript
-const txJSON = '{"Flags":2147483648,"TransactionType":"AccountSet","Account":"r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59","Domain":"726970706C652E636F6D","LastLedgerSequence":8820051,"Fee":"12","Sequence":23}';
-const secret = 'shsWGZcmZz6YsWWmcnpfr6fLTdtFV';
-const keypair = { privateKey: '00ACCD3309DB14D1A4FC9B1DAE608031F4408C85C73EE05E035B7DC8B25840107A', publicKey: '02F89EAEC7667B30F33D0687BBA86C3FE2A08CCA40A9186C5BDE2DAA6FA97A37D8' };
-return api.sign(txJSON, secret); // or: api.sign(txJSON, keypair);
-```
-
-<%- renderFixture("responses/sign.json") %>
-
-### Example (multisigning)
-
-```javascript
-const RippleAPI = require('ripple-lib').RippleAPI;
-
-// jon's address will have a multi-signing setup with a quorum of 2
-const jon = {
-    account: 'rJKpme4m2zBQceBuU89d7vLMzgoUw2Ptj',
-    secret: 'sh4Va7b1wQof8knHFV2sxwX12fSgK'
-};
-const aya = {
-    account: 'rnrPdBjs98fFFfmRpL6hM7exT788SWQPFN',
-    secret: 'snaMuMrXeVc2Vd4NYvHofeGNjgYoe'
-};
-const bran = {
-    account: 'rJ93RLnT1t5A8fCr7HTScw7WtfKJMRXodH',
-    secret: 'shQtQ8Um5MS218yvEU3Ehy1eZQKqH'
-};
-
-// Setup the signers list with a quorum of 2
-const multiSignSetupTransaction = {
-    "Flags": 0,
-    "TransactionType": "SignerListSet",
-    "Account": "rJKpme4m2zBQceBuU89d7vLMzgoUw2Ptj",
-    "Fee": "120",
-    "SignerQuorum": 2,
-    "SignerEntries": [
-        {
-            "SignerEntry": {
-                "Account": "rnrPdBjs98fFFfmRpL6hM7exT788SWQPFN",
-                "SignerWeight": 2
-            }
-        },
-        {
-            "SignerEntry": {
-                "Account": "rJ93RLnT1t5A8fCr7HTScw7WtfKJMRXodH",
-                "SignerWeight": 1
-            }
-        },
-    ]
-};
-
-// a transaction which requires multi signing
-const multiSignPaymentTransaction = {
-    TransactionType: 'Payment',
-    Account: 'rJKpme4m2zBQceBuU89d7vLMzgoUw2Ptj',
-    Destination: 'rJ93RLnT1t5A8fCr7HTScw7WtfKJMRXodH',
-    Amount: '88000000'
-};
-
-const api = new RippleAPI({
-    server: 'wss://s.altnet.rippletest.net:51233'
-});
-
-api.connect().then(() => {
-    // adding the multi signing feature to jon's account
-    api.prepareTransaction(multiSignSetupTransaction).then((prepared) => {
-        console.log(prepared);
-        jonSign = api.sign(prepared.txJSON, jon.secret).signedTransaction;
-        api.submit(jonSign).then( response => {
-            console.log(response.resultCode, response.resultMessage);
-
-            // multi sign a transaction
-            api.prepareTransaction(multiSignPaymentTransaction).then(prepared => {
-                console.log(prepared);
-
-                // Aya and Bran sign it too but with 'signAs' set to their own account
-                let ayaSign = api.sign(prepared.txJSON, aya.secret, {'signAs': aya.account}).signedTransaction;
-                let branSign = api.sign(prepared.txJSON, bran.secret, {'signAs': bran.account}).signedTransaction;
-
-                // signatures are combined and submitted
-                let combinedTx = api.combine([ayaSign, branSign]);
-                api.submit(combinedTx.signedTransaction).then(response => {
-                    console.log(response.tx_json.hash);
-                    return api.disconnect();
-                }).catch(console.error);
-            }).catch(console.error);
-        }).catch(console.error)
-    }).catch(console.error);
-}).catch(console.error);
-```
-
-Assuming the multisigning account was setup properly, the above example will respond with `resultCode: 'tesSUCCESS'` and the hash for the transaction.
-If any of `{signAs: some_address}` options were missing the code will return a validation error as follow:
-```
-[ValidationError(txJSON is not the same for all signedTransactions)]
-```

docs/src/signPaymentChannelClaim.md.ejs

@@ -1,28 +0,0 @@
-## signPaymentChannelClaim
-
-`signPaymentChannelClaim(channel: string, amount: string, privateKey: string): string`
-
-Sign a payment channel claim. The signature can be submitted in a subsequent [PaymentChannelClaim](#preparepaymentchannelclaim) transaction.
-
-### Parameters
-
-<%- renderSchema("input/sign-payment-channel-claim.json") %>
-
-### Return Value
-
-This method returns a signature string:
-
-<%- renderSchema("output/sign-payment-channel-claim.json") %>
-
-### Example
-
-```javascript
-const channel =
-  '3E18C05AD40319B809520F1A136370C4075321B285217323396D6FD9EE1E9037';
-const amount = '.00001';
-const privateKey =
-  'ACCD3309DB14D1A4FC9B1DAE608031F4408C85C73EE05E035B7DC8B25840107A';
-return api.signPaymentChannelClaim(channel, amount, privateKey);
-```
-
-<%- renderFixture("responses/sign-payment-channel-claim.json") %>

docs/src/specifications.md.ejs

@@ -1,145 +0,0 @@
-# Transaction Specifications
-
-A *transaction specification* specifies what a transaction should do. Each [Transaction Type](#transaction-types) has its own type of specification.
-
-## Payment
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/payment.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-payment.json') %>
-
-## Trustline
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/trustline.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-trustline.json') %>
-
-## Order
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/order.json') %>
-
-The following invalid flag combination causes a `ValidationError`: `immediateOrCancel` and `fillOrKill`. These fields are mutually exclusive, and cannot both be set at the same time.
-
-### Example
-
-<%- renderFixture('requests/prepare-order.json') %>
-
-## Order Cancellation
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/order-cancellation.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-order-cancellation.json') %>
-
-## Settings
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('output/get-settings.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-settings.json') %>
-
-## Escrow Creation
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/escrow-creation.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-escrow-creation.json') %>
-
-## Escrow Cancellation
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/escrow-cancellation.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-escrow-cancellation.json') %>
-
-## Escrow Execution
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/escrow-execution.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-escrow-execution.json') %>
-
-## Check Create
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/check-create.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-check-create.json') %>
-
-## Check Cancel
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/check-cancel.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-check-cancel.json') %>
-
-## Check Cash
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/check-cash.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-check-cash-amount.json') %>
-
-## Payment Channel Create
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/payment-channel-create.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-payment-channel-create.json') %>
-
-## Payment Channel Fund
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/payment-channel-fund.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-payment-channel-fund.json') %>
-
-## Payment Channel Claim
-
-See [Transaction Types](#transaction-types) for a description.
-
-<%- renderSchema('specifications/payment-channel-claim.json') %>
-
-### Example
-
-<%- renderFixture('requests/prepare-payment-channel-claim.json') %>

docs/src/staticMethods.md.ejs

@@ -1,35 +0,0 @@
-# Static Methods
-
-ripple-lib features a number of static methods that you can access directly on the `RippleAPI` object. The most commonly-used one is `computeBinaryTransactionHash`, described below. For the full list, see the [XRP Ledger Hashes README](https://github.com/ripple/ripple-lib/blob/develop/src/common/hashes/README.md).
-
-## computeBinaryTransactionHash
-
-`computeBinaryTransactionHash(txBlobHex: string): string`
-
-Returns the hash (id) of a binary transaction blob.
-
-This is a static method on the `RippleAPI` class.
-
-### Parameters
-
-This method takes one parameter, a string containing a binary transaction in hex.
-
-### Return Value
-
-This method returns a string representing the transaction's id (hash).
-
-### Example
-
-```javascript
-const signed_blob = '120000228000000024000B2E5A201B0066374B61400000003B9ACA0068400000000000000C732102356E89059A75438887F9FEE2056A2890DB82A68353BE9C0C0C8F89C0018B37FC74473045022100B3721EEB1ED6DFF29FB8B209E2DE6B54A0A6E44D52D926342F3D334BE98F08640220367A74107AD5DEAEFA3AB2984C161FC23F30B2704BB5CC984358BA262177A4568114F667B0CA50CC7709A220B0561B85E53A48461FA883142B71D8B09B4EE8DAA68FB936C23E3A974713BDAC'
-if (typeof signed_blob === 'string' && signed_blob.match(/^[A-F0-9]+$/)) {
-  const id = RippleAPI.computeBinaryTransactionHash(signed_blob)
-  console.log('Transaction hash:', id')
-}
-```
-
-```
-Transaction hash: 80C5E11E1A21A626759D6CB944B33DBAAC66BD704A289C86E330B847904F5C13
-```
-
-[RunKit Example: computeBinaryTransactionHash](https://runkit.com/intelliot/computebinarytransactionhash-example)

docs/src/submit.md.ejs

@@ -1,83 +0,0 @@
-## submit
-
-`request('submit', {tx_blob: string, fail_hard: boolean}): Promise<object>`
-
-The `submit` method applies a transaction and sends it to the network to be confirmed and included in future ledgers.
-
-This method takes a signed, serialized transaction as a binary blob, and submits it to the network as-is. Since signed transaction objects are immutable, no part of the transaction can be modified or automatically filled in after submission.
-
-To send a transaction as robustly as possible, you should construct and sign it in advance, persist it somewhere that you can access even after a power outage, then `submit` it as a `tx_blob`. After submission, monitor the network with the `tx` method to see if the transaction was successfully applied; if a restart or other problem occurs, you can safely re-submit the `tx_blob` transaction: it won't be applied twice since it has the same sequence number as the old transaction.
-
-### Parameters
-
-| `Field`     | Type    | Description                                          |
-|:------------|:--------|:-----------------------------------------------------|
-| `tx_blob`   | String  | Hex representation of the signed transaction to submit. This can be a multi-signed transaction. |
-| `fail_hard` | Boolean | (Optional, defaults to false) If true, and the transaction fails locally, do not retry or relay the transaction to other servers |
-
-### Return Value
-
-When successful, this method returns an object containing the following fields:
-
-| `Field`                 | Type    | Description                              |
-|:------------------------|:--------|:-----------------------------------------|
-| `engine_result`         | String  | Text [result code](https://xrpl.org/transaction-results.html) indicating the preliminary result of the transaction, for example `tesSUCCESS` |
-| `engine_result_code`    | Integer | Numeric version of the [result code](https://xrpl.org/transaction-results.html). **Not recommended.** |
-| `engine_result_message` | String  | Human-readable explanation of the transaction's preliminary result |
-| `tx_blob`               | String  | The complete transaction in hex string format |
-| `tx_json`               | Object  | The complete transaction in JSON format  |
-| `accepted`              | Boolean | The value `true` indicates that the transaction was applied, queued, broadcast, or kept for later. The value `false` indicates that none of those happened, so the transaction cannot possibly succeed as long as you do not submit it again and have not already submitted it another time. [New in: rippled 1.5.0] |
-| `account_sequence_available` | Number | The next [Sequence Number](https://xrpl.org/basic-data-types.html#account-sequence) available for the sending account after all pending and [queued](https://xrpl.org/transaction-queue.html) transactions. [New in: rippled 1.5.0] |
-| `account_sequence_next` | number  | The next [Sequence Number](https://xrpl.org/basic-data-types.html#account-sequence) for the sending account after all transactions that have been provisionally applied, but not transactions in the [queue](https://xrpl.org/transaction-queue.html). [New in: rippled 1.5.0] |
-| `applied`               | Boolean | The value `true` indicates that this transaction was applied to the open ledger. In this case, the transaction is likely, but not guaranteed, to be validated in the next ledger version. [New in: rippled 1.5.0] |
-| `broadcast`             | Boolean | The value `true` indicates this transaction was broadcast to peer servers in the peer-to-peer XRP Ledger network. (Note: if the server has no peers, such as in [stand-alone mode](https://xrpl.org/rippled-server-modes.html#reasons-to-run-a-rippled-server-in-stand-alone-mode), the server uses the value `true` for cases where it _would_ have broadcast the transaction.) The value `false` indicates the transaction was not broadcast to any other servers. [New in: rippled 1.5.0] |
-| `kept`                  | Boolean | The value `true` indicates that the transaction was kept to be retried later. [New in: rippled 1.5.0] |
-| `queued`                | Boolean | The value `true` indicates the transaction was put in the [Transaction Queue](https://xrpl.org/transaction-queue.html), which means it is likely to be included in a future ledger version. [New in: rippled 1.5.0] |
-| `open_ledger_cost`      | String  | The current [open ledger cost](https://xrpl.org/transaction-cost.html#open-ledger-cost) before processing this transaction. Transactions with a lower cost are likely to be [queued](https://xrpl.org/transaction-queue.html). [New in: rippled 1.5.0] |
-| `validated_ledger_index` | Integer  | The [ledger index](https://xrpl.org/basic-data-types.html#ledger-index) of the newest validated ledger at the time of submission. This provides a lower bound on the ledger versions that the transaction can appear in as a result of this request. (The transaction could only have been validated in this ledger version or earlier if it had already been submitted before.) |
-
-Note: Many situations can prevent a transaction from processing successfully, such as a lack of trust lines connecting the two accounts in a payment, or changes in the state of the ledger since the time the transaction was constructed. Even if nothing is wrong, it may take several seconds to close and validate the ledger version that includes the transaction. Do not consider the transaction's results final until they appear in a validated ledger version.
-
-### Example
-
-```javascript
-const signedTransaction = '12000022800000002400000007201B007008BC61400000000754D4C068400000000000000C732103E8110048477E60F292DEDA67CF518511E70A15E1E3771B3C024026E1F824832874473045022100D659C836C24FF346A87054E463078D805B19EFE9F10348FD4C6ED6C3F3C4D750022060BE0BFD5E2C4963A1B0E0F21D5BA800969863BA486F71E75C08D76D77C45B22811492F80A3F3849DBB5714A4F2C691CE7D47BEED58083141266204CFBC657E65D9B4D30301FF98644693935';
-const failHard = false;
-const result = await api.request('submit', {
-  tx_blob: signedTransaction,
-  fail_hard: failHard // optional
-});
-```
-
-```json
-{
-  "accepted": true,
-  "account_sequence_available": 8,
-  "account_sequence_next": 8,
-  "applied": true,
-  "broadcast": true,
-  "engine_result": "tesSUCCESS",
-  "engine_result_code": 0,
-  "engine_result_message": "The transaction was applied. Only final in a validated ledger.",
-  "kept": true,
-  "open_ledger_cost": "10",
-  "queued": false,
-  "tx_blob": "12000022800000002400000007201B007008BC61400000000754D4C068400000000000000C732103E8110048477E60F292DEDA67CF518511E70A15E1E3771B3C024026E1F824832874473045022100D659C836C24FF346A87054E463078D805B19EFE9F10348FD4C6ED6C3F3C4D750022060BE0BFD5E2C4963A1B0E0F21D5BA800969863BA486F71E75C08D76D77C45B22811492F80A3F3849DBB5714A4F2C691CE7D47BEED58083141266204CFBC657E65D9B4D30301FF98644693935",
-  "tx_json": {
-      "Account": "rNQao3Z1irwRjKWSs8heL4a8WKLPKfLrXs",
-      "Amount": "123000000",
-      "Destination": "rpgHWJdXkSvvzikdJCpuMzU7zWnuqsJRCZ",
-      "Fee": "12",
-      "Flags": 2147483648,
-      "LastLedgerSequence": 7342268,
-      "Sequence": 7,
-      "SigningPubKey": "03E8110048477E60F292DEDA67CF518511E70A15E1E3771B3C024026E1F8248328",
-      "TransactionType": "Payment",
-      "TxnSignature": "3045022100D659C836C24FF346A87054E463078D805B19EFE9F10348FD4C6ED6C3F3C4D750022060BE0BFD5E2C4963A1B0E0F21D5BA800969863BA486F71E75C08D76D77C45B22",
-      "hash": "FE8D68D7FF5805EB07AF15A1ADF07FB5463CCD2C6C0A15981EB3D26A02E1551C"
-  },
-  "validated_ledger_index": 7341775
-}
-```
-
-(In ripple-lib 1.8.0, [the old `submit` method](https://github.com/ripple/ripple-lib/blob/1.7.0/docs/index.md#submit) was deprecated.)

docs/src/transactions.md.ejs

@@ -1,76 +0,0 @@
-# Transaction Overview
-
-## Transaction Types
-
-A transaction type is specified by the strings in the first column in the table below.
-
-Type | Description
----- | -----------
-[payment](#payment) | A `payment` transaction represents a transfer of value from one account to another. Depending on the [path](https://ripple.com/build/paths/) taken, additional exchanges of value may occur atomically to facilitate the payment.
-[order](#order) | An `order` transaction creates a limit order. It defines an intent to exchange currencies, and creates an order in the XRP Ledger's order book if not completely fulfilled when placed. Orders can be partially fulfilled.
-[orderCancellation](#order-cancellation) | An `orderCancellation` transaction cancels an order in the XRP Ledger's order book.
-[trustline](#trustline) | A `trustline` transactions creates or modifies a trust line between two accounts.
-[settings](#settings) | A `settings` transaction modifies the settings of an account in the XRP Ledger.
-[escrowCreation](#escrow-creation) | An `escrowCreation` transaction creates an escrow on the ledger, which locks XRP until a cryptographic condition is met or it expires. It is like an escrow service where the XRP Ledger acts as the escrow agent.
-[escrowCancellation](#escrow-cancellation) | An `escrowCancellation` transaction unlocks the funds in an escrow and sends them back to the creator of the escrow, but it will only work after the escrow expires.
-[escrowExecution](#escrow-execution) | An `escrowExecution` transaction unlocks the funds in an escrow and sends them to the destination of the escrow, but it will only work if the cryptographic condition is provided.
-[checkCreate](#check-create) | A `checkCreate` transaction creates a check on the ledger, which is a deferred payment that can be cashed by its intended destination.
-[checkCancel](#check-cancel) | A `checkCancel` transaction cancels an unredeemed Check, removing it from the ledger without sending any money.
-[checkCash](#check-cash) | A `checkCash` transaction redeems a Check to receive up to the amount authorized by the corresponding `checkCreate` transaction. Only the `destination` address of a Check can cash it.
-[paymentChannelCreate](#payment-channel-create) | A `paymentChannelCreate` transaction opens a payment channel between two addresses with XRP set aside for asynchronous payments.
-[paymentChannelFund](#payment-channel-fund) | A `paymentChannelFund` transaction adds XRP to a payment channel and optionally sets a new expiration for the channel.
-[paymentChannelClaim](#payment-channel-claim) | A `paymentChannelClaim` transaction withdraws XRP from a channel and optionally requests to close it.
-[ticketCreate](#ticket-create) | A successful `ticketCreate` transaction adds a Ticket in the directory of the owning account.
-
-## Transaction Flow
-
-Executing a transaction with `RippleAPI` requires the following four steps:
-
-1. Prepare - Create an unsigned transaction based on a [specification](#transaction-specifications) and [instructions](#transaction-instructions). There is a method to prepare each type of transaction:
-    * [preparePayment](#preparepayment)
-    * [prepareTrustline](#preparetrustline)
-    * [prepareOrder](#prepareorder)
-    * [prepareOrderCancellation](#prepareordercancellation)
-    * [prepareSettings](#preparesettings)
-    * [prepareEscrowCreation](#prepareescrowcreation)
-    * [prepareEscrowCancellation](#prepareescrowcancellation)
-    * [prepareEscrowExecution](#prepareescrowexecution)
-    * [prepareCheckCreate](#preparecheckcreate)
-    * [prepareCheckCancel](#preparecheckcancel)
-    * [prepareCheckCash](#preparecheckcash)
-    * [prepareTicketCreate](#prepareticketcreate)
-2. [Sign](#sign) - Cryptographically sign the transaction locally and save the [transaction ID](#transaction-id). Signing is how the owner of an account authorizes a transaction to take place. For multisignature transactions, the `signedTransaction` fields returned by `sign` must be collected and passed to the [combine](#combine) method.
-3. [Submit](#submit) - Submit the transaction to the connected server.
-4. Verify - Verify that the transaction got validated by querying with [getTransaction](#gettransaction). This is necessary because transactions may fail even if they were successfully submitted.
-
-## Transaction Fees
-
-Every transaction must destroy a small amount of XRP as a cost to apply the transaction to the ledger. This is also called a *transaction fee*. The transaction cost is designed to increase along with the load on the XRP Ledger, making it very expensive to deliberately or inadvertently overload the peer-to-peer network that powers the XRP Ledger.
-
-You can choose the size of the fee you want to pay or let a default be used. You can get an estimate of the fee required to be included in the next ledger closing with the [getFee](#getfee) method.
-
-For a multi-signed transaction, ripple-lib automatically multiplies the `fee` by (1 + Number of Signatures Provided). For example, if you set `instructions.fee = '0.000020'` and `instructions.signersCount = 2`, the prepared transaction's `Fee` will be 20 drops × (1 + 2 Signatures) = 60 drops. See [Transaction Cost](https://developers.ripple.com/transaction-cost.html).
-
-## Transaction Instructions
-
-Transaction instructions indicate how to execute a transaction, complementary with the [transaction specification](#transaction-specifications).
-
-<%- renderSchema("objects/instructions.json") %>
-
-We recommend that you specify a `maxLedgerVersion` so that you can quickly determine that a failed transaction will never succeed in the future. It is impossible for a transaction to succeed after the XRP Ledger's consensus-validated ledger version exceeds the transaction's `maxLedgerVersion`. If you omit `maxLedgerVersion`, the "prepare\*" method automatically supplies a `maxLedgerVersion` equal to the current ledger plus 3, which it includes in the return value from the "prepare\*" method.
-
-## Transaction ID
-
-```json
-"F4AB442A6D4CBB935D66E1DA7309A5FC71C7143ED4049053EC14E3875B0CF9BF"
-```
-
-A transaction ID is a 64-bit hexadecimal string that uniquely identifies the transaction. The transaction ID is derived from the transaction instruction and specifications, using a strong hash function.
-
-You can look up a transaction by ID using the [getTransaction](#gettransaction) method.
-
-## Transaction Memos
-
-Every transaction can optionally have an array of memos for user applications. The `memos` field in each [transaction specification](#transaction-specifications) is an array of objects with the following structure:
-
-<%- renderSchema('objects/memos.json') %>

docs/src/txFlags.md.ejs

@@ -1,81 +0,0 @@
-## txFlags
-
-`txFlags.TRANSACTION_TYPE.FLAG`
-
-This object provides constants for use when creating or interpreting transaction flags. Most transactions have a set of bit-flags that represent various options that affect how a transaction should behave. These options are represented as binary values that can be combined with bitwise-or operations to encode multiple flags at once.
-
-Most flags only have meaning for a specific transaction type. The same bitwise value may be reused for flags on different transaction types, so it is important to pay attention to the transaction type when setting and reading flags.
-
-Bits that are not defined as flags MUST be 0.
-
-### Global Flag
-
-Applies globally to all transactions.
-
-`txFlags.Universal.FullyCanonicalSig`: Require a fully-canonical signature. When preparing transactions, ripple-lib enables this flag for you.
-
-### Payment Flags
-
-`txFlags.Payment.NoRippleDirect`: Do not use the default path; only use specified paths. This is intended to force the transaction to take arbitrage opportunities. Most clients do not need this.
-
-`txFlags.Payment.PartialPayment`: If the specified destination amount cannot be sent without spending more than the source maxAmount, reduce the received amount instead of failing outright. See [Partial Payments](https://developers.ripple.com/partial-payments.html) for more details.
-
-`txFlags.Payment.LimitQuality`: Only take paths where all the conversions have an input:output ratio that is equal or better than the ratio of `destination.amount`:`source.maxAmount`. See [Limit Quality](https://developers.ripple.com/payment.html#limit-quality) for details.
-
-### OfferCreate Flags
-
-`txFlags.OfferCreate.Passive`: If enabled, the offer does not consume offers that exactly match it, and instead becomes an Offer object in the ledger. It still consumes offers that cross it.
-
-`txFlags.OfferCreate.ImmediateOrCancel`: Treat the offer as an Immediate or Cancel order. If enabled, the offer never becomes a ledger object: it only tries to match existing offers in the ledger.
-
-`txFlags.OfferCreate.FillOrKill`: Treat the offer as a Fill or Kill order.
-
-`txFlags.OfferCreate.Sell`: Treat the offer as a Sell order. With `order.direction = 'sell'`, exchange the entire `order.quantity`, even if it means obtaining more than the `order.totalPrice` amount in exchange. If using `prepareOrder`, ripple-lib sets this flag for you.
-
-### TrustSet Flags
-
-`txFlags.TrustSet.SetAuth`: Authorize the other party to hold issuances from this account. (No effect unless using the AccountSet.RequireAuth flag.) Cannot be unset.
-
-`txFlags.TrustSet.NoRipple`:  Obsolete.
-
-`txFlags.TrustSet.SetNoRipple`: Blocks [rippling](https://developers.ripple.com/rippling.html) between two trustlines of the same currency, if this flag is set on both.
-
-`txFlags.TrustSet.ClearNoRipple`: Clears the No-[Rippling](https://developers.ripple.com/rippling.html) flag.
-
-`txFlags.TrustSet.SetFreeze`: Freeze the trustline. A non-XRP currency can be frozen by the exchange or gateway that issued it. XRP cannot be frozen.
-
-`txFlags.TrustSet.ClearFreeze`: Unfreeze the trustline.
-
-### AccountSet Flags
-
-You can use the `prepareSettings` method to change your account flags. This method uses AccountSet flags internally.
-
-In the rippled API, Account Flags can be enabled and disabled with the SetFlag and ClearFlag parameters. See [AccountSet Flags](https://developers.ripple.com/accountset.html#accountset-flags).
-
-The AccountSet transaction type has some transaction flags, but their use is discouraged.
-
-* `txFlags.AccountSet.RequireDestTag`
-* `txFlags.AccountSet.OptionalDestTag`
-* `txFlags.AccountSet.RequireAuth`
-* `txFlags.AccountSet.OptionalAuth`
-* `txFlags.AccountSet.DisallowXRP`
-* `txFlags.AccountSet.AllowXRP`
-
-### PaymentChannelClaim Flags
-
-`txFlags.PaymentChannelClaim.Renew`: Clear the channel's Expiration time. (Expiration is different from the channel's immutable CancelAfter time.) Only the source address of the payment channel can use this flag.
-
-`txFlags.PaymentChannelClaim.Close`: Request to close the channel. Only the channel source and destination addresses can use this flag. This flag closes the channel immediately if it has no more XRP allocated to it after processing the current claim, or if the destination address uses it. If the source address uses this flag when the channel still holds XRP, this schedules the channel to close after SettleDelay seconds have passed. (Specifically, this sets the Expiration of the channel to the close time of the previous ledger plus the channel's SettleDelay time, unless the channel already has an earlier Expiration time.) If the destination address uses this flag when the channel still holds XRP, any XRP that remains after processing the claim is returned to the source address.
-
-### Other Transaction Types
-
-The remaining transaction types do not have any flags at this time.
-
-* OfferCancel
-* SetRegularKey
-* SignerListSet
-* EscrowCreate
-* EscrowFinish
-* EscrowCancel
-* PaymentChannelCreate
-* PaymentChannelFund

docs/src/verifyPaymentChannelClaim.md.ejs

@@ -1,31 +0,0 @@
-## verifyPaymentChannelClaim
-
-`verifyPaymentChannelClaim(channel: string, amount: string, signature: string, publicKey: string): boolean`
-
-Verify a payment channel claim signature.
-
-### Parameters
-
-<%- renderSchema("input/verify-payment-channel-claim.json") %>
-
-### Return Value
-
-This method returns `true` if the claim signature is valid.
-
-<%- renderSchema("output/verify-payment-channel-claim.json") %>
-
-### Example
-
-```javascript
-const channel =
-  '3E18C05AD40319B809520F1A136370C4075321B285217323396D6FD9EE1E9037';
-const amount = '.00001';
-const signature = <%- importFile("test/fixtures/responses/sign-payment-channel-claim.json") %>;
-const publicKey =
-  '02F89EAEC7667B30F33D0687BBA86C3FE2A08CCA40A9186C5BDE2DAA6FA97A37D8';
-return api.verifyPaymentChannelClaim(channel, amount, signature, publicKey);
-```
-
-```json
-true
-```

docs/src/xrpToDropsAndDropsToXrp.md.ejs

@@ -1,47 +0,0 @@
-## xrpToDrops
-
-`xrpToDrops(xrp: string | BigNumber): string`
-
-Converts an XRP amount to drops. 1 XRP = 1,000,000 drops, so 1 drop = 0.000001 XRP. This method is useful when converting amounts for use with the rippled API, which requires XRP amounts to be specified in drops.
-
-### Parameters
-
-`xrp`: A string or BigNumber representing an amount of XRP. If `xrp` is a string, it may start with `-`, must contain at least one number, and may contain up to one `.`. This method throws a `ValidationError` for invalid input.
-
-### Return Value
-
-A string representing an equivalent amount of drops.
-
-### Example
-
-```javascript
-return api.xrpToDrops('1');
-```
-
-```json
-'1000000'
-```
-
-## dropsToXrp
-
-`dropsToXrp(drops: string | BigNumber): string`
-
-Converts an amount of drops to XRP. 1 drop = 0.000001 XRP, so 1 XRP = 1,000,000 drops. This method is useful when converting amounts from the rippled API, which describes XRP amounts in drops.
-
-### Parameters
-
-`drops`: A string or BigNumber representing an amount of drops. If `drops` is a string, it may start with `-` and must contain at least one number. This method throws a `ValidationError` for invalid input.
-
-### Return Value
-
-A string representing an equivalent amount of XRP.
-
-### Example
-
-```javascript
-return api.dropsToXrp('1');
-```
-
-```json
-'0.000001'
-```

jest.config.base.js

@@ -0,0 +1,20 @@
+const { TextDecoder, TextEncoder } = require("util");
+
+module.exports = {
+  roots: ["<rootDir>/src"],
+  transform: {
+    "^.+\\.ts$": "ts-jest",
+  },
+  moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
+  collectCoverage: true,
+  verbose: true,
+  testEnvironment: "node",
+  globals: {
+    TextDecoder: TextDecoder,
+    TextEncoder: TextEncoder,
+    error: console.error,
+    warn: console.warn,
+    info: console.info,
+    debug: console.debug,
+  },
+};