ordpool-parser
v0.0.10-beta.4
Published
The parsing engine that detects Inscriptions, SRC-20 Stamps, CAT-21 Ordinals, and Runes in Bitcoin transactions.
Downloads
1,209
Maintainers
hans-cryptoReadme
ordpool-parser
The parsing engine that detects Inscriptions, SRC-20 Stamps, CAT-21 Ordinals, and Runes in Bitcoin transactions. The compiled code has zero dependencies and works in the Browser and in Node.js out of the box.
The latest version of this script is used by https://ordpool.space
🚀 Usage
This package has zero dependencies and should "just work". First, install it:
npm install ordpool-parserThen, you can use the parser in your project. It expects a transaction in JSON format from an Esplora API. (This format is different from the JSON returned by a Bitcoin Node RPC.)
To avoid confusion, here are the different kinds of "Electrum" servers explained:
- Electrum and ElectrumX are basic indexers for Bitcoin
- romanz/electrs (Electrum Server in Rust) is re-implementation Electrum
- "Esplora - Electrs backend API" is a fork by blockstream.info with a powerful REST API
Esplora is the backend mempool.space uses, and is also what powers blockstream.info! The ordpool-parser was only tested with this API.
import axios from 'axios';
import { InscriptionParserService } from 'ordpool-parser';
async function getInscriptions(txId: string) {
const response = await axios.get(`https://mempool.space/api/tx/${txId}`);
// OR
// const response = await axios.get(`https://blockstream.info/api/tx/${txId}`);
const transaction = response.data;
return InscriptionParserService.parse(transaction);
}
const parsedInscriptions = await getInscriptions('f1997166547da9784a3e7419d2b248551565211811d4f5e705b685efa244451f');
if (!parsedInscriptions.length) {
console.log('No inscriptions found!');
} else {
// Output: text/html;charset=utf-8
console.log(parsedInscriptions[0].contentType);
// UTF-8 encoded string (not intended for binary content like images or videos)
// Output: <html><!--cubes.haushoppe.art--><body> [...]
console.log(parsedInscriptions[0].getContent());
// Base64 encoded data URI that can be displayed in an iframe
// Output: data:text/html;charset=utf-8;base64,PGh0bWw+PCEtLWN1YmVzLmhhdXNob3BwZS5hcnQtLT48Ym9keT4 [...]
console.log(parsedInscriptions[0].getDataUri());
}
This example uses axios, a popular HTTP client for both browser and Node.js environments.
You can install it via npm install axios. Of course, any other compatible HTTP client will also work.
Note: This is a simplified example! Make sure to handle errors when making HTTP requests, as network issues can occur.
🧡 Contribute
Prerequisites
Node.js (Version 20 or later) to test & compile the TypeScript code to JavaScript.
Install
First, install Node.js version 20. Then, install the NPM dependencies and execute the tests with the following commands:
npm install
npm testHow to add a feature
Every feature must be tested in the browser and in the node environment! Use a mainnet transaction to create a test scenario. The goal of this parser is to parse byte-perfect inscriptions that are identical to ord.
Fetch Transaction Test Data: Save the raw transaction JSON to the
testdatafolder.npm run fetch-tx-testdataEnter the
transactionId(e.g.78fa9d6e9b2b49fbb9f4838e1792dba7c1ec836f22e3206561e2d52759708251) and check the results.Fetch Inscription Test Data: Save the reference inscription as a file in the
testdatafolder.npm run fetch-inscription-testdataEnter the
inscriptionId, which is thetransactionId+i+ theindex(e.g.78fa9d6e9b2b49fbb9f4838e1792dba7c1ec836f22e3206561e2d52759708251i0), and check the results!Contribute: Add your new feature, include meaningful tests, and submit a pull request if all tests pass.
Hint: Debug the unit tests using VS Code. The
launch.jsonfile is already prepared for this purpose.
Build
To build a version without the tests:
npm run buildTo publish a new version to NPM:
npm publish