Gathering detailed insights and metrics for coinparams
Gathering detailed insights and metrics for coinparams
Gathering detailed insights and metrics for coinparams
Gathering detailed insights and metrics for coinparams
provides crypto currency specific information such as key prefixes, DNS seeds, bip32, bip44, etc, available in JSON format.
npm install coinparams
Typescript
Module System
Node Version
NPM Version
PHP (96.81%)
JavaScript (3.02%)
Shell (0.17%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
35 Stars
136 Commits
28 Forks
5 Watchers
2 Branches
4 Contributors
Updated on Jun 14, 2025
Latest Version
0.2.9
Package Id
coinparams@0.2.9
Unpacked Size
1.50 MB
Size
111.11 kB
File Count
6
NPM Version
3.5.2
Node Version
4.2.6
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
No dependencies detected.
This project provides crypto currency specific information such as key prefixes, DNS seeds, network ports, etc.
Data is available in JSON format and human readable tables. Language bindings are available for JS and PHP.
It is intended for use as a quick reference or in any software that is working with multiple cryptocurrencies, no matter the programming language.
Meta | Prefixes | Networking | Genesis Blocks | JSON |
The above files contain data mainly for bitcoin-derived coins.
Some additional metadata for coins and tokens not listed can be found in coinmeta.json.
Just copy coinparams.json into your project and read it as you would read any JSON file.
First, install the package using npm:
npm install coinparams --save
Then, require the package and use it like so:
var coinparams = require('coinparams');
console.log(coinparams.get_coin('BTC'));
console.log(coinparams.get_coin_network('DASH', 'test'));
// console.log(coinparams.get_all_coins());
// console.log(coinparams.get_raw_json());
$ cd yourproject
$ composer require dan-da/coinparams
include in your code and use via:
require_once 'path/to/vendor/autoload.php';
// get all info for single coin
$info = coinParams::get_coin('BTC');
// get info for a coin + network (main, test, regest)
$info = coinParams::get_coin_network('DOGE', 'main');
// get info for all coins
$info = coinParams::get_all_coins();
// get raw json text for all coins
$buf = coinParams::get_raw_json();
For bitcoin and bitcoin derivates, values have been automatically parsed directly from the original source code of each cryptocurrency repo on github. The script gen-masters-from-coin-src.php performs this task.
For non bitcoin derivates (eg eth, monero, decred, etc) the values are manually obtained.
Metadata such as website urls and max supply have been scraped from coinmarketcap.com.
There is a simple validation script that checks for any problems in the json tree structure, ie missing or empty fields. It does not ensure correctness of values.
Advanced testing such as generating addresses or connecting to a a running instance of each altcoin has not been attempted.
If you wish to add new coins or update an existing one, please submit a pull request. There is one file per coin in the ./coins directory. Just use an existing file such as BTC.json as a template.
If you are adding a bitcoin derivative, you can try adding it to the list in gen-masters-from-coin-src.php. Then run the script. If successful, validate with check-masters-valid.php then submit a pull request for the script and the new coin.json file.
If you wish to add new language bindings, please see the example under bindings/php or bindings/js and try to keep the api similar. Also, please try to use no more than one file (eg for package manager) in the project root directory per language.
Please include the output of running:
$ ./check-masters-valid.php <yourcoin-symbol>
The file should fully validate (main, test, regtest) for the pull request to be accepted.
The author makes no claims or guarantees of correctness.
By using this software you agree to take full responsibility for any losses incurred before, during, or after the usage, whatsoever the cause, and not to hold the software author liable in any manner.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 6/21 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More