acquire.ipynb

{
 "cells": [
  {
   "cell_type": "code",
   "execution_count": 34,
   "id": "8b55fe2f",
   "metadata": {},
   "outputs": [],
   "source": [
    "import os\n",
    "import json\n",
    "from typing import Dict, List, Optional, Union, cast\n",
    "\n",
    "from env import github_token, github_username\n",
    "\n",
    "from bs4 import BeautifulSoup\n",
    "import pandas as pd\n",
    "import numpy as np\n",
    "import re\n",
    "import requests\n",
    "\n",
    "# TODO: Make a github personal access token.\n",
    "#     1. Go here and generate a personal access token: https://github.com/settings/tokens\n",
    "#        You do _not_ need select any scopes, i.e. leave all the checkboxes unchecked\n",
    "#     2. Save it in your env.py file under the variable `github_token`\n",
    "# TODO: Add your github username to your env.py file under the variable `github_username`\n",
    "# TODO: Add more repositories to the `REPOS` list below.\n",
    "\n",
    "def web_scrape_repos():\n",
    "    \n",
    "    search_topics = \"https://github.com/search?p=\"\n",
    "\n",
    "    REPOS = []\n",
    "    \n",
    "    for page in range(1, 20):\n",
    "\n",
    "        req = requests.get(search_topics + str(page) + \"&q=\" + 'bitcoin' + \"&type=Repositories\")\n",
    "        soup = BeautifulSoup(req.text, 'html.parser')\n",
    "\n",
    "        repos = soup.find_all('a', class_='v-align-middle')\n",
    "        for link in repos:\n",
    "            REPOS.append(link['href'][1:])\n",
    "    \n",
    "    return REPOS\n",
    "\n",
    "REPOS = web_scrape_repos()\n",
    "\n",
    "headers = {\"Authorization\": f\"token {github_token}\", \"User-Agent\": github_username}\n",
    "\n",
    "if headers[\"Authorization\"] == \"token \" or headers[\"User-Agent\"] == \"\":\n",
    "    raise Exception(\n",
    "        \"You need to follow the instructions marked TODO in this script before trying to use it\"\n",
    "    )\n",
    "\n",
    "\n",
    "def github_api_request(url: str) -> Union[List, Dict]:\n",
    "    response = requests.get(url, headers=headers)\n",
    "    response_data = response.json()\n",
    "    if response.status_code != 200:\n",
    "        raise Exception(\n",
    "            f\"Error response from github api! status code: {response.status_code}, \"\n",
    "            f\"response: {json.dumps(response_data)}\"\n",
    "        )\n",
    "    return response_data\n",
    "\n",
    "\n",
    "def get_repo_language(repo: str) -> str:\n",
    "    url = f\"https://api.github.com/repos/{repo}\"\n",
    "    repo_info = github_api_request(url)\n",
    "    if type(repo_info) is dict:\n",
    "        repo_info = cast(Dict, repo_info)\n",
    "        if \"language\" not in repo_info:\n",
    "            raise Exception(\n",
    "                \"'language' key not round in response\\n{}\".format(json.dumps(repo_info))\n",
    "            )\n",
    "        return repo_info[\"language\"]\n",
    "    raise Exception(\n",
    "        f\"Expecting a dictionary response from {url}, instead got {json.dumps(repo_info)}\"\n",
    "    )\n",
    "\n",
    "\n",
    "def get_repo_contents(repo: str) -> List[Dict[str, str]]:\n",
    "    url = f\"https://api.github.com/repos/{repo}/contents/\"\n",
    "    contents = github_api_request(url)\n",
    "    if type(contents) is list:\n",
    "        contents = cast(List, contents)\n",
    "        return contents\n",
    "    raise Exception(\n",
    "        f\"Expecting a list response from {url}, instead got {json.dumps(contents)}\"\n",
    "    )\n",
    "\n",
    "\n",
    "def get_readme_download_url(files: List[Dict[str, str]]) -> str:\n",
    "    \"\"\"\n",
    "    Takes in a response from the github api that lists the files in a repo and\n",
    "    returns the url that can be used to download the repo's README file.\n",
    "    \"\"\"\n",
    "    for file in files:\n",
    "        if file[\"name\"].lower().startswith(\"readme\"):\n",
    "            return file[\"download_url\"]\n",
    "    return \"\"\n",
    "\n",
    "\n",
    "def process_repo(repo: str) -> Dict[str, str]:\n",
    "    \"\"\"\n",
    "    Takes a repo name like \"gocodeup/codeup-setup-script\" and returns a\n",
    "    dictionary with the language of the repo and the readme contents.\n",
    "    \"\"\"\n",
    "    contents = get_repo_contents(repo)\n",
    "    readme_download_url = get_readme_download_url(contents)\n",
    "    if readme_download_url == \"\":\n",
    "        readme_contents = \"\"\n",
    "    else:\n",
    "        readme_contents = requests.get(readme_download_url).text\n",
    "    return {\n",
    "        \"repo\": repo,\n",
    "        \"language\": get_repo_language(repo),\n",
    "        \"readme_contents\": readme_contents,\n",
    "    }\n",
    "\n",
    "\n",
    "def scrape_github_data() -> List[Dict[str, str]]:\n",
    "    \"\"\"\n",
    "    Loop through all of the repos and process them. Returns the processed data.\n",
    "    \"\"\"\n",
    "    lst = []\n",
    "    total = len(REPOS)\n",
    "    for repo in REPOS:\n",
    "        total -= 1\n",
    "        lst.append(process_repo(repo))\n",
    "        print(total)\n",
    "    # return lst\n",
    "    return [process_repo(repo) for repo in REPOS]\n",
    "\n",
    "\n",
    "if __name__ == \"__main__\":\n",
    "    data = scrape_github_data()\n",
    "    json.dump(data, open(\"data2.json\", \"w\"), indent=1)"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": null,
   "id": "3bedfd07",
   "metadata": {},
   "outputs": [],
   "source": []
  },
  {
   "cell_type": "code",
   "execution_count": 33,
   "id": "61c24a82",
   "metadata": {},
   "outputs": [
    {
     "name": "stdout",
     "output_type": "stream",
     "text": [
      "89\n",
      "88\n",
      "87\n",
      "86\n",
      "85\n",
      "84\n",
      "83\n",
      "82\n",
      "81\n",
      "80\n",
      "79\n",
      "78\n",
      "77\n",
      "76\n",
      "75\n",
      "74\n",
      "73\n",
      "72\n",
      "71\n",
      "70\n",
      "69\n",
      "68\n",
      "67\n",
      "66\n",
      "65\n",
      "64\n",
      "63\n",
      "62\n",
      "61\n",
      "60\n",
      "59\n",
      "58\n",
      "57\n",
      "56\n",
      "55\n",
      "54\n",
      "53\n",
      "52\n",
      "51\n",
      "50\n",
      "49\n",
      "48\n",
      "47\n",
      "46\n",
      "45\n",
      "44\n",
      "43\n",
      "42\n",
      "41\n",
      "40\n",
      "39\n",
      "38\n",
      "37\n",
      "36\n",
      "35\n",
      "34\n",
      "33\n",
      "32\n",
      "31\n",
      "30\n",
      "29\n",
      "28\n",
      "27\n",
      "26\n",
      "25\n",
      "24\n",
      "23\n",
      "22\n",
      "21\n",
      "20\n",
      "19\n",
      "18\n",
      "17\n",
      "16\n",
      "15\n",
      "14\n",
      "13\n",
      "12\n",
      "11\n",
      "10\n",
      "9\n",
      "8\n",
      "7\n",
      "6\n",
      "5\n",
      "4\n",
      "3\n",
      "2\n",
      "1\n",
      "0\n"
     ]
    },
    {
     "data": {
      "text/plain": [
       "[{'repo': 'bitcoin/bitcoin',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': \"Bitcoin Core integration/staging tree\\n=====================================\\n\\nhttps://bitcoincore.org\\n\\nFor an immediately usable, binary version of the Bitcoin Core software, see\\nhttps://bitcoincore.org/en/download/.\\n\\nWhat is Bitcoin Core?\\n---------------------\\n\\nBitcoin Core connects to the Bitcoin peer-to-peer network to download and fully\\nvalidate blocks and transactions. It also includes a wallet and graphical user\\ninterface, which can be optionally built.\\n\\nFurther information about Bitcoin Core is available in the [doc folder](/doc).\\n\\nLicense\\n-------\\n\\nBitcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more\\ninformation or see https://opensource.org/licenses/MIT.\\n\\nDevelopment Process\\n-------------------\\n\\nThe `master` branch is regularly built (see `doc/build-*.md` for instructions) and tested, but it is not guaranteed to be\\ncompletely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created\\nregularly from release branches to indicate new official, stable release versions of Bitcoin Core.\\n\\nThe https://github.com/bitcoin-core/gui repository is used exclusively for the\\ndevelopment of the GUI. Its master branch is identical in all monotree\\nrepositories. Release branches and tags do not exist, so please do not fork\\nthat repository unless it is for development reasons.\\n\\nThe contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md)\\nand useful hints for developers can be found in [doc/developer-notes.md](doc/developer-notes.md).\\n\\nTesting\\n-------\\n\\nTesting and code review is the bottleneck for development; we get more pull\\nrequests than we can review and test on short notice. Please be patient and help out by testing\\nother people's pull requests, and remember this is a security-critical project where any mistake might cost people\\nlots of money.\\n\\n### Automated Testing\\n\\nDevelopers are strongly encouraged to write [unit tests](src/test/README.md) for new code, and to\\nsubmit new unit tests for old code. Unit tests can be compiled and run\\n(assuming they weren't disabled in configure) with: `make check`. Further details on running\\nand extending unit tests can be found in [/src/test/README.md](/src/test/README.md).\\n\\nThere are also [regression and integration tests](/test), written\\nin Python.\\nThese tests can be run (if the [test dependencies](/test) are installed) with: `test/functional/test_runner.py`\\n\\nThe CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS,\\nand that unit/sanity tests are run automatically.\\n\\n### Manual Quality Assurance (QA) Testing\\n\\nChanges should be tested by somebody other than the developer who wrote the\\ncode. This is especially important for large or high-risk changes. It is useful\\nto add a test plan to the pull request description if testing the changes is\\nnot straightforward.\\n\\nTranslations\\n------------\\n\\nChanges to translations as well as new translations can be submitted to\\n[Bitcoin Core's Transifex page](https://www.transifex.com/bitcoin/bitcoin/).\\n\\nTranslations are periodically pulled from Transifex and merged into the git repository. See the\\n[translation process](doc/translation_process.md) for details on how this works.\\n\\n**Important**: We do not accept translation changes as GitHub pull requests because the next\\npull from Transifex would automatically overwrite them again.\\n\"},\n",
       " {'repo': 'bitcoinbook/bitcoinbook',\n",
       "  'language': 'AsciiDoc',\n",
       "  'readme_contents': 'Code Examples: ![travis_ci](https://travis-ci.org/bitcoinbook/bitcoinbook.svg?branch=develop)\\n\\n# Mastering Bitcoin\\n\\nMastering Bitcoin is a book for developers, although the first two chapters cover bitcoin at a level that is also approachable to non-programmers. Anyone with a basic understanding of technology can read the first two chapters to get a great understanding of bitcoin.\\n\\nThis repository contains the complete [first edition, second print](https://github.com/bitcoinbook/bitcoinbook/releases/tag/Edition1Print2), published in December 2014, and the complete [second edition, third print](https://github.com/bitcoinbook/bitcoinbook/releases/tag/second_edition_print3_rc1), published in March 2018, as published by O\\'Reilly Media in paperback and ebook formats.\\n\\n# Issues, Errors, Comments, Contributions\\n\\nIf you know how to make a pull request to contribute a fix, please write the correction and use a pull request to submit it for consideration against the [develop branch](https://github.com/bitcoinbook/bitcoinbook/tree/develop). If you are making several changes, please use a separate commit for each to make it easier to cherry-pick or resolve conflicts. Otherwise, please submit an issue, explaining the error or comment. If you would like to contribute extensive changes or new material, please coordinate with the author first; contact information can be found on his website: https://antonopoulos.com/\\n\\n# Reading this book\\n\\nTo read this book, see [book.asciidoc](https://github.com/bitcoinbook/bitcoinbook/blob/develop/book.asciidoc). Click on each of the chapters to read in your browser. Other parties may choose to release PDFs of the book online.\\n\\n## Chapters\\n\\n+ Chapter 1: \\'[Introduction](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch01.asciidoc)\\'\\n+ Chapter 2: \\'[How Bitcoin Works](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch02.asciidoc)\\'\\n+ Chapter 3: \\'[Bitcoin Core: The Reference Implementation](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch03.asciidoc)\\'\\n+ Chapter 4: \\'[Keys, Addresses](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch04.asciidoc)\\'\\n+ Chapter 5: \\'[Wallets](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch05.asciidoc)\\'\\n+ Chapter 6: \\'[Transactions](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch06.asciidoc)\\'\\n+ Chapter 7: \\'[Advanced Transactions and Scripting](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch07.asciidoc)\\'\\n+ Chapter 8: \\'[The Bitcoin Network](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch08.asciidoc)\\'\\n+ Chapter 9: \\'[The Blockchain](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch09.asciidoc)\\'\\n+ Chapter 10: \\'[Mining and Consensus](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch10.asciidoc)\\'\\n+ Chapter 11: \\'[Bitcoin Security](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch11.asciidoc)\\'\\n+ Chapter 12: \\'[Blockchain Applications](https://github.com/bitcoinbook/bitcoinbook/blob/develop/ch12.asciidoc)\\'\\n\\n# Published\\n\\n\"Mastering Bitcoin (Second Edition, Second Print): Programming the Open Blockchain\" is now available in paperback and ebook formats by many booksellers worldwide:\\n\\n* [Amazon](https://www.amazon.com/Mastering-Bitcoin-Programming-Open-Blockchain/dp/1491954388)\\n\\nMastering Bitcoin (First Edition Second Print) is also published in Japanese, Korean, and Chinese (Simplified) by publishers in the respective countries.\\n\\nMastering Bitcoin (Open Edition), based on the First Edition, has been translated by volunteers into more than a dozen languages. Translations are available for free under CC-BY-SA license at: https://bitcoinbook.info\\n\\n# Source\\n\\nThe book\\'s source code, found in this repository, is kept synchronized with the print and ebook editions.\\n\\n## Mastering Bitcoin - First Edition\\n\\nThe tags [Edition1Print1](https://github.com/bitcoinbook/bitcoinbook/releases/tag/Edition1Print1), [Edition1Print2](https://github.com/bitcoinbook/bitcoinbook/releases/tag/Edition1Print2) correspond to the two existing prints of Mastering Bitcoin (First Edition) as published by O\\'Reilly Media.\\n\\n<a rel=\"license\" href=\"http://creativecommons.org/licenses/by-sa/4.0/\"><img alt=\"Creative Commons License\" style=\"border-width:0\" src=\"https://i.creativecommons.org/l/by-sa/4.0/88x31.png\" /></a><br /><span xmlns:dct=\"http://purl.org/dc/terms/\" href=\"http://purl.org/dc/dcmitype/Text\" property=\"dct:title\" rel=\"dct:type\">Mastering Bitcoin - First Edition</span> by <a xmlns:cc=\"http://creativecommons.org/ns#\" href=\"https://antonopoulos.com/\" property=\"cc:attributionName\" rel=\"cc:attributionURL\">Andreas M. Antonopoulos LLC</a> is licensed under a <a rel=\"license\" href=\"http://creativecommons.org/licenses/by-sa/4.0/\">Creative Commons Attribution-ShareAlike 4.0 International License</a>.\\n\\nThis \"Free Culture\" compliant license was approved by my publisher O\\'Reilly Media (http://oreilly.com), who understands the value of open source. O\\'Reilly Media is not just the world\\'s best publisher of technical books, but is also a strong supporter of this open culture and the sharing of knowledge.\\n\\nThank you O\\'Reilly Media!\\n\\n## Mastering Bitcoin - Second Edition\\n\\nThe tags, [second_edition_print_1](https://github.com/bitcoinbook/bitcoinbook/releases/tag/second_edition_print_1) and  [second_edition_print2](https://github.com/bitcoinbook/bitcoinbook/releases/tag/second_edition_print2), correspond to the first (June 8th, 2017) and second (July 20th, 2017) print of Mastering Bitcoin (Second Edition), as published by O\\'Reilly Media.\\n\\n<a rel=\"license\" href=\"http://creativecommons.org/licenses/by-sa/4.0/\"><img alt=\"Creative Commons License\" style=\"border-width:0\" src=\"https://i.creativecommons.org/l/by-sa/4.0/88x31.png\" /></a><br /><span xmlns:dct=\"http://purl.org/dc/terms/\" href=\"http://purl.org/dc/dcmitype/Text\" property=\"dct:title\" rel=\"dct:type\">Mastering Bitcoin - Second Edition</span> by <a xmlns:cc=\"http://creativecommons.org/ns#\" href=\"https://antonopoulos.com/\" property=\"cc:attributionName\" rel=\"cc:attributionURL\">Andreas M. Antonopoulos LLC</a> is licensed under a <a rel=\"license\" href=\"http://creativecommons.org/licenses/by-sa/4.0/\">Creative Commons Attribution-ShareAlike 4.0 International License</a>.\\n\\n# Translations\\n\\nIf you are interested in translating this book, please join our team of volunteers at: https://www.transifex.com/aantonop/mastering-bitcoin\\n\\nFree copies of \"Mastering Bitcoin Open Edition,\" translated in many languages, can be downloaded from: https://bitcoinbook.info\\n'},\n",
       " {'repo': 'bitcoinj/bitcoinj',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': \"image:https://github.com/bitcoinj/bitcoinj/workflows/Java%20CI/badge.svg[GitHub Build Status,link=https://github.com/bitcoinj/bitcoinj/actions]\\nimage:https://gitlab.com/bitcoinj/bitcoinj/badges/master/pipeline.svg[GitLab Build Status,link=https://gitlab.com/bitcoinj/bitcoinj/pipelines]\\nimage:https://coveralls.io/repos/bitcoinj/bitcoinj/badge.png?branch=master[Coverage Status,link=https://coveralls.io/r/bitcoinj/bitcoinj?branch=master]\\n\\nimage::https://kiwiirc.com/buttons/irc.freenode.net/bitcoinj.png[Visit our IRC channel,link=https://kiwiirc.com/client/irc.freenode.net/bitcoinj]\\n\\n### Welcome to bitcoinj\\n\\nThe bitcoinj library is a Java implementation of the Bitcoin protocol, which allows it to maintain a wallet and send/receive transactions without needing a local copy of Bitcoin Core. It comes with full documentation and some example apps showing how to use it.\\n\\n### Technologies\\n\\n* Java 8+ (needs Java 8 API or Android 8.0 API, compiles to Java 8 bytecode) and Gradle 4.4+ for the `core` module\\n* Java 11+ and Gradle 4.4+ for `tools`, `wallettool` and `examples`\\n* Java 11+ and Gradle 4.10+ for the JavaFX-based `wallettemplate`\\n* https://gradle.org/[Gradle] - for building the project\\n* https://github.com/google/protobuf[Google Protocol Buffers] - for use with serialization and hardware communications\\n\\n### Getting started\\n\\nTo get started, it is best to have the latest JDK and Gradle installed. The HEAD of the `master` branch contains the latest development code and various production releases are provided on feature branches.\\n\\n#### Building from the command line\\n\\nOfficial builds are currently using JDK 11. Our GitHub Actions build and test with JDK 11 and JDK 17.\\n\\nTo perform a full build (_including_ JavaDocs and unit/integration _tests_) use JDK 11+.\\n\\n```\\ngradle clean build\\n```\\nIf you are using Gradle 4.10 or later, the build will automatically include the JavaFX-based `wallettemplate` module. The outputs are under the `build` directory.\\n\\nTo perform a full build _without_ unit/integration _tests_ use:\\n```\\ngradle clean assemble\\n```\\n\\n#### Building from an IDE\\n\\nAlternatively, just import the project using your IDE. http://www.jetbrains.com/idea/download/[IntelliJ] has Gradle integration built-in and has a free Community Edition. Simply use `File | New | Project from Existing Sources` and locate the `build.gradle` in the root of the cloned project source tree.\\n\\n### Building and Using the Wallet Tool\\n\\nThe *bitcoinj* `wallettool` subproject includes a command-line Wallet Tool (`wallet-tool`) that can be used to create and manage *bitcoinj*-based wallets (both the HD keychain and SPV blockchain state.) Using `wallet-tool` on Bitcoin's test net is a great way to learn about Bitcoin and *bitcoinj*.\\n\\nTo build an executable shell script that runs the command-line Wallet Tool, use:\\n```\\ngradle bitcoinj-wallettool:installDist\\n```\\n\\nYou can now run the `wallet-tool` without parameters to get help on its operation:\\n```\\n./wallettool/build/install/wallet-tool/bin/wallet-tool\\n```\\n\\nTo create a test net wallet file in `~/bitcoinj/bitcoinj-test.wallet`, you would use:\\n```\\nmkdir ~/bitcoinj\\n```\\n```\\n./wallettool/build/install/wallet-tool/bin/wallet-tool --net=TESTNET --wallet=$HOME/bitcoinj/bitcoinj-test.wallet create\\n```\\n\\nTo sync the newly created wallet in `~/bitcoinj/bitcoinj-test.wallet` with the test net, you would use:\\n```\\n./wallettool/build/install/wallet-tool/bin/wallet-tool --net=TESTNET --wallet=$HOME/bitcoinj/bitcoinj-test.wallet sync\\n```\\n\\nTo dump the state of the wallet in `~/bitcoinj/bitcoinj-test.wallet` with the test net, you would use:\\n```\\n./wallettool/build/install/wallet-tool/bin/wallet-tool --net=TESTNET --wallet=$HOME/bitcoinj/bitcoinj-test.wallet dump\\n```\\n\\nNOTE: These instructions are for macOS/Linux, for Windows use the `wallettool/build/install/wallet-tool/bin/wallet-tool.bat` batch file with the equivalent Windows command-line commands and options.\\n\\n### Example applications\\n\\nThese are found in the `examples` module.\\n\\n### Where next?\\n\\nNow you are ready to https://bitcoinj.github.io/getting-started[follow the tutorial].\\n\\n### Testing a SNAPSHOT build\\n\\nBuilding apps with official releases of *bitcoinj* is covered in the https://bitcoinj.github.io/getting-started[tutorial].\\n\\nIf you want to develop or test your app with a https://jitpack.io[Jitpack]-powered build of the latest `master` or `release-0.15` branch of *bitcoinj* follow the dynamically-generated instructions for that branch by following the correct link.\\n\\n* https://jitpack.io/#bitcoinj/bitcoinj/master-SNAPSHOT[master] branch\\n* https://jitpack.io/#bitcoinj/bitcoinj/release-0.15-SNAPSHOT[release-0.15] branch\\n\"},\n",
       " {'repo': 'bitcoin/bips',\n",
       "  'language': 'Wikitext',\n",
       "  'readme_contents': 'People wishing to submit BIPs, first should propose their idea or document to the [https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev bitcoin-dev@lists.linuxfoundation.org] mailing list (do <em>not</em> assign a number - read <a href=\"bip-0002.mediawiki\">BIP 2</a> for the full process). After discussion, please open a PR. After copy-editing and acceptance, it will be published here.\\n\\nWe are fairly liberal with approving BIPs, and try not to be too involved in decision making on behalf of the community. The exception is in very rare cases of dispute resolution when a decision is contentious and cannot be agreed upon. In those cases, the conservative option will always be preferred.\\n\\nHaving a BIP here does not make it a formally accepted standard until its status becomes Final or Active.\\n\\nThose proposing changes should consider that ultimately consent may rest with the consensus of the Bitcoin users (see also: [https://en.bitcoin.it/wiki/Economic_majority economic majority]).\\n\\n{| class=\"wikitable sortable\" style=\"width: auto; text-align: center; font-size: smaller; table-layout: fixed;\"\\n!Number\\n!Layer\\n!Title\\n!Owner\\n!Type\\n!Status\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0001.mediawiki|1]]\\n|\\n| BIP Purpose and Guidelines\\n| Amir Taaki\\n| Process\\n| Replaced\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0002.mediawiki|2]]\\n|\\n| BIP process, revised\\n| Luke Dashjr\\n| Process\\n| Active\\n|-\\n| [[bip-0008.mediawiki|8]]\\n|\\n| Version bits with lock-in by height\\n| Shaolin Fry, Luke Dashjr\\n| Informational\\n| Draft\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0009.mediawiki|9]]\\n|\\n| Version bits with timeout and delay\\n| Pieter Wuille, Peter Todd, Greg Maxwell, Rusty Russell\\n| Informational\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0010.mediawiki|10]]\\n| Applications\\n| Multi-Sig Transaction Distribution\\n| Alan Reiner\\n| Informational\\n| Withdrawn\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0011.mediawiki|11]]\\n| Applications\\n| M-of-N Standard Transactions\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0012.mediawiki|12]]\\n| Consensus (soft fork)\\n| OP_EVAL\\n| Gavin Andresen\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0013.mediawiki|13]]\\n| Applications\\n| Address Format for pay-to-script-hash\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0014.mediawiki|14]]\\n| Peer Services\\n| Protocol Version and User Agent\\n| Amir Taaki, Patrick Strateman\\n| Standard\\n| Final\\n|-\\n| [[bip-0015.mediawiki|15]]\\n| Applications\\n| Aliases\\n| Amir Taaki\\n| Standard\\n| Deferred\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0016.mediawiki|16]]\\n| Consensus (soft fork)\\n| Pay to Script Hash\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0017.mediawiki|17]]\\n| Consensus (soft fork)\\n| OP_CHECKHASHVERIFY (CHV)\\n| Luke Dashjr\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0018.mediawiki|18]]\\n| Consensus (soft fork)\\n| hashScriptCheck\\n| Luke Dashjr\\n| Standard\\n| Proposed\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0019.mediawiki|19]]\\n| Applications\\n| M-of-N Standard Transactions (Low SigOp)\\n| Luke Dashjr\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0020.mediawiki|20]]\\n| Applications\\n| URI Scheme\\n| Luke Dashjr\\n| Standard\\n| Replaced\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0021.mediawiki|21]]\\n| Applications\\n| URI Scheme\\n| Nils Schneider, Matt Corallo\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0022.mediawiki|22]]\\n| API/RPC\\n| getblocktemplate - Fundamentals\\n| Luke Dashjr\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0023.mediawiki|23]]\\n| API/RPC\\n| getblocktemplate - Pooled Mining\\n| Luke Dashjr\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0030.mediawiki|30]]\\n| Consensus (soft fork)\\n| Duplicate transactions\\n| Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0031.mediawiki|31]]\\n| Peer Services\\n| Pong message\\n| Mike Hearn\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0032.mediawiki|32]]\\n| Applications\\n| Hierarchical Deterministic Wallets\\n| Pieter Wuille\\n| Informational\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0033.mediawiki|33]]\\n| Peer Services\\n| Stratized Nodes\\n| Amir Taaki\\n| Standard\\n| Rejected\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0034.mediawiki|34]]\\n| Consensus (soft fork)\\n| Block v2, Height in Coinbase\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0035.mediawiki|35]]\\n| Peer Services\\n| mempool message\\n| Jeff Garzik\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0036.mediawiki|36]]\\n| Peer Services\\n| Custom Services\\n| Stefan Thomas\\n| Standard\\n| Rejected\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0037.mediawiki|37]]\\n| Peer Services\\n| Connection Bloom filtering\\n| Mike Hearn, Matt Corallo\\n| Standard\\n| Final\\n|-\\n| [[bip-0038.mediawiki|38]]\\n| Applications\\n| Passphrase-protected private key\\n| Mike Caldwell, Aaron Voisine\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0039.mediawiki|39]]\\n| Applications\\n| Mnemonic code for generating deterministic keys\\n| Marek Palatinus, Pavol Rusnak, Aaron Voisine, Sean Bowe\\n| Standard\\n| Proposed\\n|-\\n| 40\\n| API/RPC\\n| Stratum wire protocol\\n| Marek Palatinus\\n| Standard\\n| BIP number allocated\\n|-\\n| 41\\n| API/RPC\\n| Stratum mining protocol\\n| Marek Palatinus\\n| Standard\\n| BIP number allocated\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0042.mediawiki|42]]\\n| Consensus (soft fork)\\n| A finite monetary supply for Bitcoin\\n| Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0043.mediawiki|43]]\\n| Applications\\n| Purpose Field for Deterministic Wallets\\n| Marek Palatinus, Pavol Rusnak\\n| Informational\\n| Final\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0044.mediawiki|44]]\\n| Applications\\n| Multi-Account Hierarchy for Deterministic Wallets\\n| Marek Palatinus, Pavol Rusnak\\n| Standard\\n| Proposed\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0045.mediawiki|45]]\\n| Applications\\n| Structure for Deterministic P2SH Multisignature Wallets\\n| Manuel Araoz, Ryan X. Charles, Matias Alejo Garcia\\n| Standard\\n| Proposed\\n|-\\n| [[bip-0047.mediawiki|47]]\\n| Applications\\n| Reusable Payment Codes for Hierarchical Deterministic Wallets\\n| Justus Ranvier\\n| Informational\\n| Draft\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0048.mediawiki|48]]\\n| Applications\\n| Multi-Script Hierarchy for Multi-Sig Wallets\\n| Fontaine\\n| Standard\\n| Proposed\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0049.mediawiki|49]]\\n| Applications\\n| Derivation scheme for P2WPKH-nested-in-P2SH based accounts\\n| Daniel Weigl\\n| Informational\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0050.mediawiki|50]]\\n|\\n| March 2013 Chain Fork Post-Mortem\\n| Gavin Andresen\\n| Informational\\n| Final\\n|-\\n| [[bip-0052.mediawiki|52]]\\n| Consensus (hard fork)\\n| Durable, Low Energy Bitcoin PoW\\n| Michael Dubrovsky, Bogdan Penkovsky\\n| Standard\\n| Draft\\n<!-- 50 series reserved for a group of post-mortems -->\\n|-\\n| [[bip-0060.mediawiki|60]]\\n| Peer Services\\n| Fixed Length \"version\" Message (Relay-Transactions Field)\\n| Amir Taaki\\n| Standard\\n| Draft\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0061.mediawiki|61]]\\n| Peer Services\\n| Reject P2P message\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0062.mediawiki|62]]\\n| Consensus (soft fork)\\n| Dealing with malleability\\n| Pieter Wuille\\n| Standard\\n| Withdrawn\\n|-\\n| 63\\n| Applications\\n| Stealth Addresses\\n| Peter Todd\\n| Standard\\n| BIP number allocated\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0064.mediawiki|64]]\\n| Peer Services\\n| getutxo message\\n| Mike Hearn\\n| Standard\\n| Obsolete\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0065.mediawiki|65]]\\n| Consensus (soft fork)\\n| OP_CHECKLOCKTIMEVERIFY\\n| Peter Todd\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0066.mediawiki|66]]\\n| Consensus (soft fork)\\n| Strict DER signatures\\n| Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0067.mediawiki|67]]\\n| Applications\\n| Deterministic Pay-to-script-hash multi-signature addresses through public key sorting\\n| Thomas Kerin, Jean-Pierre Rupp, Ruben de Vries\\n| Standard\\n| Proposed\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0068.mediawiki|68]]\\n| Consensus (soft fork)\\n| Relative lock-time using consensus-enforced sequence numbers\\n| Mark Friedenbach, BtcDrak, Nicolas Dorier, kinoshitajona\\n| Standard\\n| Final\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0069.mediawiki|69]]\\n| Applications\\n| Lexicographical Indexing of Transaction Inputs and Outputs\\n| Kristov Atlas\\n| Informational\\n| Proposed\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0070.mediawiki|70]]\\n| Applications\\n| Payment Protocol\\n| Gavin Andresen, Mike Hearn\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0071.mediawiki|71]]\\n| Applications\\n| Payment Protocol MIME types\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0072.mediawiki|72]]\\n| Applications\\n| bitcoin: uri extensions for Payment Protocol\\n| Gavin Andresen\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0073.mediawiki|73]]\\n| Applications\\n| Use \"Accept\" header for response type negotiation with Payment Request URLs\\n| Stephen Pair\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0074.mediawiki|74]]\\n| Applications\\n| Allow zero value OP_RETURN in Payment Protocol\\n| Toby Padilla\\n| Standard\\n| Rejected\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0075.mediawiki|75]]\\n| Applications\\n| Out of Band Address Exchange using Payment Protocol Encryption\\n| Justin Newton, Matt David, Aaron Voisine, James MacWhyte\\n| Standard\\n| Final\\n|-\\n| [[bip-0078.mediawiki|78]]\\n| Applications\\n| A Simple Payjoin Proposal\\n| Nicolas Dorier\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0079.mediawiki|79]]\\n| Applications\\n| Bustapay :: a practical coinjoin protocol\\n| Ryan Havar\\n| Informational\\n| Replaced\\n|-\\n| [[bip-0080.mediawiki|80]]\\n|\\n| Hierarchy for Non-Colored Voting Pool Deterministic Multisig Wallets\\n| Justus Ranvier, Jimmy Song\\n| Informational\\n| Deferred\\n|-\\n| [[bip-0081.mediawiki|81]]\\n|\\n| Hierarchy for Colored Voting Pool Deterministic Multisig Wallets\\n| Justus Ranvier, Jimmy Song\\n| Informational\\n| Deferred\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0083.mediawiki|83]]\\n| Applications\\n| Dynamic Hierarchical Deterministic Key Trees\\n| Eric Lombrozo\\n| Standard\\n| Rejected\\n|-\\n| [[bip-0084.mediawiki|84]]\\n| Applications\\n| Derivation scheme for P2WPKH based accounts\\n| Pavol Rusnak\\n| Informational\\n| Draft\\n|-\\n| [[bip-0085.mediawiki|85]]\\n| Applications\\n| Deterministic Entropy From BIP32 Keychains\\n| Ethan Kosakovsky\\n| Informational\\n| Draft\\n|-\\n| [[bip-0086.mediawiki|86]]\\n| Applications\\n| Key Derivation for Single Key P2TR Outputs\\n| Andrew Chow\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0087.mediawiki|87]]\\n| Applications\\n| Hierarchy for Deterministic Multisig Wallets\\n| Robert Spigler\\n| Standard\\n| Proposed\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0088.mediawiki|88]]\\n| Applications\\n| Hierarchical Deterministic Path Templates\\n| Dmitry Petukhov\\n| Informational\\n| Proposed\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0090.mediawiki|90]]\\n|\\n| Buried Deployments\\n| Suhas Daftuar\\n| Informational\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0091.mediawiki|91]]\\n| Consensus (soft fork)\\n| Reduced threshold Segwit MASF\\n| James Hilliard\\n| Standard\\n| Final\\n|-\\n| [[bip-0098.mediawiki|98]]\\n| Consensus (soft fork)\\n| Fast Merkle Trees\\n| Mark Friedenbach, Kalle Alm, BtcDrak\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0099.mediawiki|99]]\\n|\\n| Motivation and deployment of consensus rule changes ([soft/hard]forks)\\n| Jorge Timón\\n| Informational\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0100.mediawiki|100]]\\n| Consensus (hard fork)\\n| Dynamic maximum block size by miner vote\\n| Jeff Garzik, Tom Harding, Dagur Valberg Johannsson\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0101.mediawiki|101]]\\n| Consensus (hard fork)\\n| Increase maximum block size\\n| Gavin Andresen\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0102.mediawiki|102]]\\n| Consensus (hard fork)\\n| Block size increase to 2MB\\n| Jeff Garzik\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0103.mediawiki|103]]\\n| Consensus (hard fork)\\n| Block size following technological growth\\n| Pieter Wuille\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0104.mediawiki|104]]\\n| Consensus (hard fork)\\n| \\'Block75\\' - Max block size like difficulty\\n| t.khan\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0105.mediawiki|105]]\\n| Consensus (hard fork)\\n| Consensus based block size retargeting algorithm\\n| BtcDrak\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0106.mediawiki|106]]\\n| Consensus (hard fork)\\n| Dynamically Controlled Bitcoin Block Size Max Cap\\n| Upal Chakraborty\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0107.mediawiki|107]]\\n| Consensus (hard fork)\\n| Dynamic limit on the block size\\n| Washington Y. Sanchez\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0109.mediawiki|109]]\\n| Consensus (hard fork)\\n| Two million byte size limit with sigop and sighash limits\\n| Gavin Andresen\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0111.mediawiki|111]]\\n| Peer Services\\n| NODE_BLOOM service bit\\n| Matt Corallo, Peter Todd\\n| Standard\\n| Proposed\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0112.mediawiki|112]]\\n| Consensus (soft fork)\\n| CHECKSEQUENCEVERIFY\\n| BtcDrak, Mark Friedenbach, Eric Lombrozo\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0113.mediawiki|113]]\\n| Consensus (soft fork)\\n| Median time-past as endpoint for lock-time calculations\\n| Thomas Kerin, Mark Friedenbach\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0114.mediawiki|114]]\\n| Consensus (soft fork)\\n| Merkelized Abstract Syntax Tree\\n| Johnson Lau\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0115.mediawiki|115]]\\n| Consensus (soft fork)\\n| Generic anti-replay protection using Script\\n| Luke Dashjr\\n| Standard\\n| Rejected\\n|-\\n| [[bip-0116.mediawiki|116]]\\n| Consensus (soft fork)\\n| MERKLEBRANCHVERIFY\\n| Mark Friedenbach, Kalle Alm, BtcDrak\\n| Standard\\n| Draft\\n|-\\n| [[bip-0117.mediawiki|117]]\\n| Consensus (soft fork)\\n| Tail Call Execution Semantics\\n| Mark Friedenbach, Kalle Alm, BtcDrak\\n| Standard\\n| Draft\\n|-\\n| [[bip-0118.mediawiki|118]]\\n| Consensus (soft fork)\\n| SIGHASH_ANYPREVOUT for Taproot Scripts\\n| Christian Decker, Anthony Towns\\n| Standard\\n| Draft\\n|-\\n| [[bip-0119.mediawiki|119]]\\n| Consensus (soft fork)\\n| CHECKTEMPLATEVERIFY\\n| Jeremy Rubin\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0120.mediawiki|120]]\\n| Applications\\n| Proof of Payment\\n| Kalle Rosenbaum\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0121.mediawiki|121]]\\n| Applications\\n| Proof of Payment URI scheme\\n| Kalle Rosenbaum\\n| Standard\\n| Withdrawn\\n|-\\n| [[bip-0122.mediawiki|122]]\\n| Applications\\n| URI scheme for Blockchain references / exploration\\n| Marco Pontello\\n| Standard\\n| Draft\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0123.mediawiki|123]]\\n|\\n| BIP Classification\\n| Eric Lombrozo\\n| Process\\n| Active\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0124.mediawiki|124]]\\n| Applications\\n| Hierarchical Deterministic Script Templates\\n| Eric Lombrozo, William Swanson\\n| Informational\\n| Rejected\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0125.mediawiki|125]]\\n| Applications\\n| Opt-in Full Replace-by-Fee Signaling\\n| David A. Harding, Peter Todd\\n| Standard\\n| Proposed\\n|-\\n| [[bip-0126.mediawiki|126]]\\n|\\n| Best Practices for Heterogeneous Input Script Transactions\\n| Kristov Atlas\\n| Informational\\n| Draft\\n|-\\n| [[bip-0127.mediawiki|127]]\\n| Applications\\n| Simple Proof-of-Reserves Transactions\\n| Steven Roose\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0129.mediawiki|129]]\\n| Applications\\n| Bitcoin Secure Multisig Setup (BSMS)\\n| Hugo Nguyen, Peter Gray, Marko Bencun, Aaron Chen, Rodolfo Novak\\n| Standard\\n| Proposed\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0130.mediawiki|130]]\\n| Peer Services\\n| sendheaders message\\n| Suhas Daftuar\\n| Standard\\n| Proposed\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0131.mediawiki|131]]\\n| Consensus (hard fork)\\n| \"Coalescing Transaction\" Specification (wildcard inputs)\\n| Chris Priest\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0132.mediawiki|132]]\\n|\\n| Committee-based BIP Acceptance Process\\n| Andy Chase\\n| Process\\n| Withdrawn\\n|-\\n| [[bip-0133.mediawiki|133]]\\n| Peer Services\\n| feefilter message\\n| Alex Morcos\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0134.mediawiki|134]]\\n| Consensus (hard fork)\\n| Flexible Transactions\\n| Tom Zander\\n| Standard\\n| Rejected\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0135.mediawiki|135]]\\n|\\n| Generalized version bits voting\\n| Sancho Panza\\n| Informational\\n| Rejected\\n|-\\n| [[bip-0136.mediawiki|136]]\\n| Applications\\n| Bech32 Encoded Tx Position References\\n| Велеслав, Jonas Schnelli, Daniel Pape\\n| Informational\\n| Draft\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0137.mediawiki|137]]\\n| Applications\\n| Signatures of Messages using Private Keys\\n| Christopher Gilliard\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0140.mediawiki|140]]\\n| Consensus (soft fork)\\n| Normalized TXID\\n| Christian Decker\\n| Standard\\n| Rejected\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0141.mediawiki|141]]\\n| Consensus (soft fork)\\n| Segregated Witness (Consensus layer)\\n| Eric Lombrozo, Johnson Lau, Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0142.mediawiki|142]]\\n| Applications\\n| Address Format for Segregated Witness\\n| Johnson Lau\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0143.mediawiki|143]]\\n| Consensus (soft fork)\\n| Transaction Signature Verification for Version 0 Witness Program\\n| Johnson Lau, Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0144.mediawiki|144]]\\n| Peer Services\\n| Segregated Witness (Peer Services)\\n| Eric Lombrozo, Pieter Wuille\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0145.mediawiki|145]]\\n| API/RPC\\n| getblocktemplate Updates for Segregated Witness\\n| Luke Dashjr\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0146.mediawiki|146]]\\n| Consensus (soft fork)\\n| Dealing with signature encoding malleability\\n| Johnson Lau, Pieter Wuille\\n| Standard\\n| Withdrawn\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0147.mediawiki|147]]\\n| Consensus (soft fork)\\n| Dealing with dummy stack element malleability\\n| Johnson Lau\\n| Standard\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0148.mediawiki|148]]\\n| Consensus (soft fork)\\n| Mandatory activation of segwit deployment\\n| Shaolin Fry\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0149.mediawiki|149]]\\n| Consensus (soft fork)\\n| Segregated Witness (second deployment)\\n| Shaolin Fry\\n| Standard\\n| Withdrawn\\n|-\\n| [[bip-0150.mediawiki|150]]\\n| Peer Services\\n| Peer Authentication\\n| Jonas Schnelli\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0151.mediawiki|151]]\\n| Peer Services\\n| Peer-to-Peer Communication Encryption\\n| Jonas Schnelli\\n| Standard\\n| Replaced\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0152.mediawiki|152]]\\n| Peer Services\\n| Compact Block Relay\\n| Matt Corallo\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0154.mediawiki|154]]\\n| Peer Services\\n| Rate Limiting via peer specified challenges\\n| Karl-Johan Alm\\n| Standard\\n| Withdrawn\\n|-\\n| [[bip-0155.mediawiki|155]]\\n| Peer Services\\n| addrv2 message\\n| Wladimir J. van der Laan\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0156.mediawiki|156]]\\n| Peer Services\\n| Dandelion - Privacy Enhancing Routing\\n| Brad Denby, Andrew Miller, Giulia Fanti, Surya Bakshi, Shaileshh Bojja Venkatakrishnan, Pramod Viswanath\\n| Standard\\n| Rejected\\n|-\\n| [[bip-0157.mediawiki|157]]\\n| Peer Services\\n| Client Side Block Filtering\\n| Olaoluwa Osuntokun, Alex Akselrod, Jim Posen\\n| Standard\\n| Draft\\n|-\\n| [[bip-0158.mediawiki|158]]\\n| Peer Services\\n| Compact Block Filters for Light Clients\\n| Olaoluwa Osuntokun, Alex Akselrod\\n| Standard\\n| Draft\\n|-\\n| [[bip-0159.mediawiki|159]]\\n| Peer Services\\n| NODE_NETWORK_LIMITED service bit\\n| Jonas Schnelli\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0171.mediawiki|171]]\\n| Applications\\n| Currency/exchange rate information API\\n| Luke Dashjr\\n| Standard\\n| Rejected\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0173.mediawiki|173]]\\n| Applications\\n| Base32 address format for native v0-16 witness outputs\\n| Pieter Wuille, Greg Maxwell\\n| Informational\\n| Final\\n|- style=\"background-color: #cfffcf\"\\n| [[bip-0174.mediawiki|174]]\\n| Applications\\n| Partially Signed Bitcoin Transaction Format\\n| Andrew Chow\\n| Standard\\n| Final\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0175.mediawiki|175]]\\n| Applications\\n| Pay to Contract Protocol\\n| Omar Shibli, Nicholas Gregory\\n| Informational\\n| Rejected\\n|-\\n| [[bip-0176.mediawiki|176]]\\n|\\n| Bits Denomination\\n| Jimmy Song\\n| Informational\\n| Draft\\n|-\\n| [[bip-0178.mediawiki|178]]\\n| Applications\\n| Version Extended WIF\\n| Karl-Johan Alm\\n| Standard\\n| Draft\\n|-\\n| [[bip-0179.mediawiki|179]]\\n|\\n| Name for payment recipient identifiers\\n| Emil Engler, Luke Dashjr\\n| Informational\\n| Draft\\n|- style=\"background-color: #ffcfcf\"\\n| [[bip-0180.mediawiki|180]]\\n| Peer Services\\n| Block size/weight fraud proof\\n| Luke Dashjr\\n| Standard\\n| Rejected\\n|-\\n| [[bip-0197.mediawiki|197]]\\n| Applications\\n| Hashed Time-Locked Collateral Contract\\n| Matthew Black, Tony Cai\\n| Standard\\n| Draft\\n|-\\n| [[bip-0199.mediawiki|199]]\\n| Applications\\n| Hashed Time-Locked Contract transactions\\n| Sean Bowe, Daira Hopwood\\n| Standard\\n| Draft\\n|-\\n| [[bip-0300.mediawiki|300]]\\n| Consensus (soft fork)\\n| Hashrate Escrows (Consensus layer)\\n| Paul Sztorc, CryptAxe\\n| Standard\\n| Draft\\n|-\\n| [[bip-0301.mediawiki|301]]\\n| Consensus (soft fork)\\n| Blind Merged Mining (Consensus layer)\\n| Paul Sztorc, CryptAxe\\n| Standard\\n| Draft\\n|-\\n| [[bip-0310.mediawiki|310]]\\n| Applications\\n| Stratum protocol extensions\\n| Pavel Moravec, Jan Čapek\\n| Informational\\n| Draft\\n|-\\n| [[bip-0320.mediawiki|320]]\\n|\\n| nVersion bits for general purpose use\\n| BtcDrak\\n| Standard\\n| Draft\\n|-\\n| [[bip-0322.mediawiki|322]]\\n| Applications\\n| Generic Signed Message Format\\n| Karl-Johan Alm\\n| Standard\\n| Draft\\n|-\\n| [[bip-0324.mediawiki|324]]\\n| Peer Services\\n| Version 2 P2P Encrypted Transport Protocol\\n| Dhruv Mehta, Tim Ruffing, Jonas Schnelli, Pieter Wuille\\n| Standard\\n| Draft\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0325.mediawiki|325]]\\n| Applications\\n| Signet\\n| Karl-Johan Alm, Anthony Towns\\n| Standard\\n| Proposed\\n|-\\n| [[bip-0326.mediawiki|326]]\\n| Applications\\n| Anti-fee-sniping protection in taproot transactions\\n| Chris Belcher\\n| Informational\\n| Draft\\n|-\\n| [[bip-0329.mediawiki|329]]\\n| Applications\\n| Wallet Labels Export Format\\n| Craig Raw\\n| Informational\\n| Draft\\n|-\\n| [[bip-0330.mediawiki|330]]\\n| Peer Services\\n| Transaction announcements reconciliation\\n| Gleb Naumenko, Pieter Wuille\\n| Standard\\n| Draft\\n|-\\n| [[bip-0338.mediawiki|338]]\\n| Peer Services\\n| Disable transaction relay message\\n| Suhas Daftuar\\n| Standard\\n| Draft\\n|-\\n| [[bip-0339.mediawiki|339]]\\n| Peer Services\\n| WTXID-based transaction relay\\n| Suhas Daftuar\\n| Standard\\n| Draft\\n|-\\n| [[bip-0340.mediawiki|340]]\\n|\\n| Schnorr Signatures for secp256k1\\n| Pieter Wuille, Jonas Nick, Tim Ruffing\\n| Standard\\n| Final\\n|-\\n| [[bip-0341.mediawiki|341]]\\n| Consensus (soft fork)\\n| Taproot: SegWit version 1 spending rules\\n| Pieter Wuille, Jonas Nick, Anthony Towns\\n| Standard\\n| Final\\n|-\\n| [[bip-0342.mediawiki|342]]\\n| Consensus (soft fork)\\n| Validation of Taproot Scripts\\n| Pieter Wuille, Jonas Nick, Anthony Towns\\n| Standard\\n| Final\\n|- style=\"background-color: #ffffcf\"\\n| [[bip-0343.mediawiki|343]]\\n| Consensus (soft fork)\\n| Mandatory activation of taproot deployment\\n| Shinobius, Michael Folkson\\n| Standard\\n| Final\\n|-\\n| [[bip-0350.mediawiki|350]]\\n| Applications\\n| Bech32m format for v1+ witness addresses\\n| Pieter Wuille\\n| Standard\\n| Draft\\n|-\\n| [[bip-0351.mediawiki|351]]\\n| Applications\\n| Private Payments\\n| Alfred Hodler, Clark Moody\\n| Informational\\n| Draft\\n|-\\n| [[bip-0370.mediawiki|370]]\\n| Applications\\n| PSBT Version 2\\n| Andrew Chow\\n| Standard\\n| Draft\\n|-\\n| [[bip-0371.mediawiki|371]]\\n| Applications\\n| Taproot Fields for PSBT\\n| Andrew Chow\\n| Standard\\n| Draft\\n|-\\n| [[bip-0372.mediawiki|372]]\\n| Applications\\n| Pay-to-contract tweak fields for PSBT\\n| Maxim Orlovsky\\n| Standard\\n| Draft\\n|-\\n| [[bip-0380.mediawiki|380]]\\n| Applications\\n| Output Script Descriptors General Operation\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0381.mediawiki|381]]\\n| Applications\\n| Non-Segwit Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0382.mediawiki|382]]\\n| Applications\\n| Segwit Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0383.mediawiki|383]]\\n| Applications\\n| Multisig Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0384.mediawiki|384]]\\n| Applications\\n| combo() Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0385.mediawiki|385]]\\n| Applications\\n| raw() and addr() Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|-\\n| [[bip-0386.mediawiki|386]]\\n| Applications\\n| tr() Output Script Descriptors\\n| Pieter Wuille, Andrew Chow\\n| Informational\\n| Draft\\n|}\\n\\n<!-- IMPORTANT!  See the instructions at the top of this page, do NOT JUST add BIPs here! -->\\n'},\n",
       " {'repo': 'bitcoinjs/bitcoinjs-lib',\n",
       "  'language': 'TypeScript',\n",
       "  'readme_contents': '# BitcoinJS (bitcoinjs-lib)\\n[![Github CI](https://github.com/bitcoinjs/bitcoinjs-lib/actions/workflows/main_ci.yml/badge.svg)](https://github.com/bitcoinjs/bitcoinjs-lib/actions/workflows/main_ci.yml) [![NPM](https://img.shields.io/npm/v/bitcoinjs-lib.svg)](https://www.npmjs.org/package/bitcoinjs-lib) [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)\\n\\nA javascript Bitcoin library for node.js and browsers. Written in TypeScript, but committing the JS files to verify.\\n\\nReleased under the terms of the [MIT LICENSE](LICENSE).\\n\\n## Should I use this in production?\\nIf you are thinking of using the *master* branch of this library in production, **stop**.\\nMaster is not stable; it is our development branch, and [only tagged releases may be classified as stable](https://github.com/bitcoinjs/bitcoinjs-lib/tags).\\n\\n\\n## Can I trust this code?\\n> Don\\'t trust. Verify.\\n\\nWe recommend every user of this library and the [bitcoinjs](https://github.com/bitcoinjs) ecosystem audit and verify any underlying code for its validity and suitability,  including reviewing any and all of your project\\'s dependencies.\\n\\nMistakes and bugs happen, but with your help in resolving and reporting [issues](https://github.com/bitcoinjs/bitcoinjs-lib/issues), together we can produce open source software that is:\\n\\n- Easy to audit and verify,\\n- Tested, with test coverage >95%,\\n- Advanced and feature rich,\\n- Standardized, using [prettier](https://github.com/prettier/prettier) and Node `Buffer`\\'s throughout, and\\n- Friendly, with a strong and helpful community, ready to answer questions.\\n\\n\\n## Documentation\\nPresently,  we do not have any formal documentation other than our [examples](#examples), please [ask for help](https://github.com/bitcoinjs/bitcoinjs-lib/issues/new) if our examples aren\\'t enough to guide you.\\n\\nYou can find a [Web UI](https://bitcoincore.tech/apps/bitcoinjs-ui/index.html) that covers most of the `psbt.ts`, `transaction.ts` and `p2*.ts` APIs [here](https://bitcoincore.tech/apps/bitcoinjs-ui/index.html).\\n\\n## Installation\\n``` bash\\nnpm install bitcoinjs-lib\\n# optionally, install a key derivation library as well\\nnpm install ecpair bip32\\n# ecpair is the ECPair class for single keys\\n# bip32 is for generating HD keys\\n```\\n\\nPrevious versions of the library included classes for key management (ECPair, HDNode(->\"bip32\")) but now these have been separated into different libraries. This lowers the bundle size significantly if you don\\'t need to perform any crypto functions (converting private to public keys and deriving HD keys).\\n\\nTypically we support the [Node Maintenance LTS version](https://github.com/nodejs/Release). TypeScript target will be set\\nto the ECMAScript version in which all features are fully supported by current Active Node LTS.\\nHowever, depending on adoption among other environments (browsers etc.) we may keep the target back a year or two.\\nIf in doubt, see the [main_ci.yml](.github/workflows/main_ci.yml) for what versions are used by our continuous integration tests.\\n\\n**WARNING**: We presently don\\'t provide any tooling to verify that the release on `npm` matches GitHub.  As such, you should verify anything downloaded by `npm` against your own verified copy.\\n\\n\\n## Usage\\nCrypto is hard.\\n\\nWhen working with private keys, the random number generator is fundamentally one of the most important parts of any software you write.\\nFor random number generation, we *default* to the [`randombytes`](https://github.com/crypto-browserify/randombytes) module, which uses [`window.crypto.getRandomValues`](https://developer.mozilla.org/en-US/docs/Web/API/window.crypto.getRandomValues) in the browser, or Node js\\' [`crypto.randomBytes`](https://nodejs.org/api/crypto.html#crypto_crypto_randombytes_size_callback), depending on your build system.\\nAlthough this default is ~OK, there is no simple way to detect if the underlying RNG provided is good enough, or if it is **catastrophically bad**.\\nYou should always verify this yourself to your own standards.\\n\\nThis library uses [tiny-secp256k1](https://github.com/bitcoinjs/tiny-secp256k1), which uses [RFC6979](https://tools.ietf.org/html/rfc6979) to help prevent `k` re-use and exploitation.\\nUnfortunately, this isn\\'t a silver bullet.\\nOften, Javascript itself is working against us by bypassing these counter-measures.\\n\\nProblems in [`Buffer (UInt8Array)`](https://github.com/feross/buffer), for example, can trivially result in **catastrophic fund loss** without any warning.\\nIt can do this through undermining your random number generation, accidentally producing a [duplicate `k` value](https://www.nilsschneider.net/2013/01/28/recovering-bitcoin-private-keys.html), sending Bitcoin to a malformed output script, or any of a million different ways.\\nRunning tests in your target environment is important and a recommended step to verify continuously.\\n\\nFinally, **adhere to best practice**.\\nWe are not an authoritative source of best practice, but, at the very least:\\n\\n* [Don\\'t reuse addresses](https://en.bitcoin.it/wiki/Address_reuse).\\n* Don\\'t share BIP32 extended public keys (\\'xpubs\\'). [They are a liability](https://bitcoin.stackexchange.com/questions/56916/derivation-of-parent-private-key-from-non-hardened-child), and it only takes 1 misplaced private key (or a buggy implementation!) and you are vulnerable to **catastrophic fund loss**.\\n* [Don\\'t use `Math.random`](https://security.stackexchange.com/questions/181580/why-is-math-random-not-designed-to-be-cryptographically-secure) - in any way - don\\'t.\\n* Enforce that users always verify (manually) a freshly-decoded human-readable version of their intended transaction before broadcast.\\n* [Don\\'t *ask* users to generate mnemonics](https://en.bitcoin.it/wiki/Brainwallet#cite_note-1), or \\'brain wallets\\',  humans are terrible random number generators.\\n* Lastly, if you can, use [Typescript](https://www.typescriptlang.org/) or similar.\\n\\n\\n### Browser\\nThe recommended method of using `bitcoinjs-lib` in your browser is through [browserify](http://browserify.org/).\\n\\nIf you\\'d like to use a different (more modern) build tool than `browserify`, you can compile just this library and its dependencies into a single JavaScript file:\\n\\n```sh\\n$ npm install bitcoinjs-lib browserify\\n$ npx browserify --standalone bitcoin - -o bitcoinjs-lib.js <<<\"module.exports = require(\\'bitcoinjs-lib\\');\"\\n```\\n\\nWhich you can then import as an ESM module:\\n\\n```javascript\\n<script type=\"module\">import \"/scripts/bitcoinjs-lib.js\"</script>\\n````\\n\\n**NOTE**: We use Node Maintenance LTS features, if you need strict ES5, use [`--transform babelify`](https://github.com/babel/babelify) in conjunction with your `browserify` step (using an [`es2015`](https://babeljs.io/docs/plugins/preset-es2015/) preset).\\n\\n**WARNING**: iOS devices have [problems](https://github.com/feross/buffer/issues/136), use at least [buffer@5.0.5](https://github.com/feross/buffer/pull/155) or greater,  and enforce the test suites (for `Buffer`, and any other dependency) pass before use.\\n\\n### Typescript or VSCode users\\nType declarations for Typescript are included in this library. Normal installation should include all the needed type information.\\n\\n## Examples\\nThe below examples are implemented as integration tests, they should be very easy to understand.\\nOtherwise, pull requests are appreciated.\\nSome examples interact (via HTTPS) with a 3rd Party Blockchain Provider (3PBP).\\n\\n\\n- [Taproot Key Spend](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/taproot.spec.ts)\\n- [Generate a random address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Import an address via WIF](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a 2-of-3 P2SH multisig address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a SegWit address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a SegWit P2SH address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a SegWit 3-of-4 multisig address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a SegWit 2-of-2 P2SH multisig address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Support the retrieval of transactions for an address (3rd party blockchain)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a Testnet address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Generate a Litecoin address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/addresses.spec.ts)\\n- [Create a 1-to-1 Transaction](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a typical Transaction](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with an OP\\\\_RETURN output](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with a 2-of-4 P2SH(multisig) input](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with a SegWit P2SH(P2WPKH) input](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with a SegWit P2WPKH input](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with a SegWit P2PK input](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction with a SegWit 3-of-4 P2SH(P2WSH(multisig)) input](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction and sign with an HDSigner interface (bip32)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/transactions.spec.ts)\\n- [Import a BIP32 testnet xpriv and export to WIF](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Export a BIP32 xpriv, then import it](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Export a BIP32 xpub](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Create a BIP32, bitcoin, account 0, external address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Create a BIP44, bitcoin, account 0, external address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Create a BIP49, bitcoin testnet, account 0, external address](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Use BIP39 to generate BIP32 addresses](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/bip32.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice can redeem the output after the expiry (in the past)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/cltv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice can redeem the output after the expiry (in the future)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/cltv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice and Bob can redeem the output at any time](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/cltv.spec.ts)\\n- [Create (but fail to broadcast via 3PBP) a Transaction where Alice attempts to redeem before the expiry](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/cltv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice can redeem the output after the expiry (in the future) (simple CHECKSEQUENCEVERIFY)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/csv.spec.ts)\\n- [Create (but fail to broadcast via 3PBP) a Transaction where Alice attempts to redeem before the expiry (simple CHECKSEQUENCEVERIFY)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/csv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Bob and Charles can send (complex CHECKSEQUENCEVERIFY)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/csv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice (mediator) and Bob can send after 2 blocks (complex CHECKSEQUENCEVERIFY)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/csv.spec.ts)\\n- [Create (and broadcast via 3PBP) a Transaction where Alice (mediator) can send after 5 blocks (complex CHECKSEQUENCEVERIFY)](https://github.com/bitcoinjs/bitcoinjs-lib/blob/master/test/integration/csv.spec.ts)\\n\\nIf you have a use case that you feel could be listed here, please [ask for it](https://github.com/bitcoinjs/bitcoinjs-lib/issues/new)!\\n\\n\\n## Contributing\\nSee [CONTRIBUTING.md](CONTRIBUTING.md).\\n\\n\\n### Running the test suite\\n\\n``` bash\\nnpm test\\nnpm run-script coverage\\n```\\n\\n## Complementing Libraries\\n- [BIP21](https://github.com/bitcoinjs/bip21) - A BIP21 compatible URL encoding library\\n- [BIP38](https://github.com/bitcoinjs/bip38) - Passphrase-protected private keys\\n- [BIP39](https://github.com/bitcoinjs/bip39) - Mnemonic generation for deterministic keys\\n- [BIP32-Utils](https://github.com/bitcoinjs/bip32-utils) - A set of utilities for working with BIP32\\n- [BIP66](https://github.com/bitcoinjs/bip66) - Strict DER signature decoding\\n- [BIP68](https://github.com/bitcoinjs/bip68) - Relative lock-time encoding library\\n- [BIP69](https://github.com/bitcoinjs/bip69) - Lexicographical Indexing of Transaction Inputs and Outputs\\n- [Base58](https://github.com/cryptocoinjs/bs58) - Base58 encoding/decoding\\n- [Base58 Check](https://github.com/bitcoinjs/bs58check) - Base58 check encoding/decoding\\n- [Bech32](https://github.com/bitcoinjs/bech32) - A BIP173/BIP350 compliant Bech32/Bech32m encoding library\\n- [coinselect](https://github.com/bitcoinjs/coinselect) - A fee-optimizing, transaction input selection module for bitcoinjs-lib.\\n- [merkle-lib](https://github.com/bitcoinjs/merkle-lib) - A performance conscious library for merkle root and tree calculations.\\n- [minimaldata](https://github.com/bitcoinjs/minimaldata) - A module to check bitcoin policy: SCRIPT_VERIFY_MINIMALDATA\\n\\n\\n## Alternatives\\n- [BCoin](https://github.com/indutny/bcoin)\\n- [Bitcore](https://github.com/bitpay/bitcore)\\n- [Cryptocoin](https://github.com/cryptocoinjs/cryptocoin)\\n\\n\\n## LICENSE [MIT](LICENSE)\\n'},\n",
       " {'repo': 'spesmilo/electrum',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '# Electrum - Lightweight Bitcoin client\\n\\n```\\nLicence: MIT Licence\\nAuthor: Thomas Voegtlin\\nLanguage: Python (>= 3.8)\\nHomepage: https://electrum.org/\\n```\\n\\n[![Build Status](https://api.cirrus-ci.com/github/spesmilo/electrum.svg?branch=master)](https://cirrus-ci.com/github/spesmilo/electrum)\\n[![Test coverage statistics](https://coveralls.io/repos/github/spesmilo/electrum/badge.svg?branch=master)](https://coveralls.io/github/spesmilo/electrum?branch=master)\\n[![Help translate Electrum online](https://d322cqt584bo4o.cloudfront.net/electrum/localized.svg)](https://crowdin.com/project/electrum)\\n\\n\\n## Getting started\\n\\n_(If you\\'ve come here looking to simply run Electrum,\\n[you may download it here](https://electrum.org/#download).)_\\n\\nElectrum itself is pure Python, and so are most of the required dependencies,\\nbut not everything. The following sections describe how to run from source, but here\\nis a TL;DR:\\n\\n```\\n$ sudo apt-get install libsecp256k1-0\\n$ python3 -m pip install --user \".[gui,crypto]\"\\n```\\n\\n### Not pure-python dependencies\\n\\nIf you want to use the Qt interface, install the Qt dependencies:\\n```\\n$ sudo apt-get install python3-pyqt5\\n```\\n\\nFor elliptic curve operations,\\n[libsecp256k1](https://github.com/bitcoin-core/secp256k1)\\nis a required dependency:\\n```\\n$ sudo apt-get install libsecp256k1-0\\n```\\n\\nAlternatively, when running from a cloned repository, a script is provided to build\\nlibsecp256k1 yourself:\\n```\\n$ sudo apt-get install automake libtool\\n$ ./contrib/make_libsecp256k1.sh\\n```\\n\\nDue to the need for fast symmetric ciphers,\\n[cryptography](https://github.com/pyca/cryptography) is required.\\nInstall from your package manager (or from pip):\\n```\\n$ sudo apt-get install python3-cryptography\\n```\\n\\nIf you would like hardware wallet support,\\n[see this](https://github.com/spesmilo/electrum-docs/blob/master/hardware-linux.rst).\\n\\n\\n### Running from tar.gz\\n\\nIf you downloaded the official package (tar.gz), you can run\\nElectrum from its root directory without installing it on your\\nsystem; all the pure python dependencies are included in the \\'packages\\'\\ndirectory. To run Electrum from its root directory, just do:\\n```\\n$ ./run_electrum\\n```\\n\\nYou can also install Electrum on your system, by running this command:\\n```\\n$ sudo apt-get install python3-setuptools python3-pip\\n$ python3 -m pip install --user .\\n```\\n\\nThis will download and install the Python dependencies used by\\nElectrum instead of using the \\'packages\\' directory.\\nIt will also place an executable named `electrum` in `~/.local/bin`,\\nso make sure that is on your `PATH` variable.\\n\\n\\n### Development version (git clone)\\n\\n_(For OS-specific instructions, see [here for Windows](contrib/build-wine/README_windows.md),\\nand [for macOS](contrib/osx/README_macos.md))_\\n\\nCheck out the code from GitHub:\\n```\\n$ git clone https://github.com/spesmilo/electrum.git\\n$ cd electrum\\n$ git submodule update --init\\n```\\n\\nRun install (this should install dependencies):\\n```\\n$ python3 -m pip install --user -e .\\n```\\n\\nCreate translations (optional):\\n```\\n$ sudo apt-get install python3-requests gettext qttools5-dev-tools\\n$ ./contrib/pull_locale\\n```\\n\\nFinally, to start Electrum:\\n```\\n$ ./run_electrum\\n```\\n\\n### Run tests\\n\\nRun unit tests with `pytest`:\\n```\\n$ pytest electrum/tests -v\\n```\\n\\nTo run a single file, specify it directly like this:\\n```\\n$ pytest electrum/tests/test_bitcoin.py -v\\n```\\n\\n## Creating Binaries\\n\\n- [Linux (tarball)](contrib/build-linux/sdist/README.md)\\n- [Linux (AppImage)](contrib/build-linux/appimage/README.md)\\n- [macOS](contrib/osx/README.md)\\n- [Windows](contrib/build-wine/README.md)\\n- [Android](contrib/android/Readme.md)\\n\\n\\n## Contributing\\n\\nAny help testing the software, reporting or fixing bugs, reviewing pull requests\\nand recent changes, writing tests, or helping with outstanding issues is very welcome.\\nImplementing new features, or improving/refactoring the codebase, is of course\\nalso welcome, but to avoid wasted effort, especially for larger changes,\\nwe encourage discussing these on the issue tracker or IRC first.\\n\\nBesides [GitHub](https://github.com/spesmilo/electrum),\\nmost communication about Electrum development happens on IRC, in the\\n`#electrum` channel on Libera Chat. The easiest way to participate on IRC is\\nwith the web client, [web.libera.chat](https://web.libera.chat/#electrum).\\n'},\n",
       " {'repo': 'bitcoin-wallet/bitcoin-wallet',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': \"# BITCOIN WALLET\\n\\nWelcome to _Bitcoin Wallet_, a standalone Bitcoin payment app for your Android device!\\n\\nThis project contains several sub-projects:\\n\\n * __wallet__:\\n     The Android app itself. This is probably what you're searching for.\\n * __market__:\\n     App description and promo material for the Google Play app store.\\n\\n\\n### PREREQUISITES FOR BUILDING\\n\\nYou'll need git, a Java 11 SDK and Gradle between 4.4 and 6.9.x for this. We'll assume Ubuntu 22.04 LTS (Jammy Jellyfish)\\nfor the package installs, which comes with OpenJDK 11 and Gradle 4.4.1 out of the box.\\n\\n    # first time only\\n    sudo apt install git gradle openjdk-11-jdk\\n\\nCreate a directory for the Android SDK (e.g. `android-sdk`) and point the `ANDROID_HOME` variable to it.\\n\\nDownload the [Android SDK Tools](https://developer.android.com/studio/index.html#command-tools)\\nand unpack it to `$ANDROID_HOME/`.\\n\\nFinally, the last preparative step is acquiring the source code. Again in your workspace, use:\\n\\n    # first time only\\n    git clone -b master https://github.com/bitcoin-wallet/bitcoin-wallet.git bitcoin-wallet\\n    cd bitcoin-wallet\\n\\n\\n### BUILDING\\n\\nYou can build all sub-projects in all flavors at once using Gradle:\\n\\n    # each time\\n    gradle clean build\\n\\nFor details about building the wallet see the [specific README](wallet/README.md).\\n\"},\n",
       " {'repo': 'etotheipi/BitcoinArmory',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '##Armory\\n\\n**Created by Alan Reiner on 13 July, 2011**\\n\\n[Armory](https://github.com/etotheipi/BitcoinArmory) is a full-featured Bitcoin client, offering a dozen innovative features not found in any other client software! Manage multiple wallets (deterministic and watching-only), print paper backups that work forever, import or sweep private keys, and keep your savings in a computer that never touches the internet, while still being able to manage incoming payments, and create outgoing payments with the help of a USB key.\\n\\nMulti-signature transactions are accommodated under-the-hood about 80%, and will be completed and integrated into the UI soon.\\n\\n**Armory has no independent networking components built in.** Instead, it relies on on the Satoshi client to securely connect to peers, validate blockchain data, and broadcast transactions for us.  Although it was initially planned to cut the umbilical cord to the Satoshi client and implement independent networking, it has turned out to be an inconvenience worth having. Reimplementing all the networking code would be fraught with bugs, security holes, and possible blockchain forking.  The reliance on Bitcoin-Qt right now is actually making Armory more secure!\\n\\n##Donations\\n\\nPlease take a moment to donate! 1ArmoryXcfq7TnCSuZa9fQjRYwJ4bkRKfv\\n\\n![bitcoin:1ArmoryXcfq7TnCSuZa9fQjRYwJ4bkRKfv][Donation Image]\\n\\n##Building Armory From Source\\n\\nSee instructions [here][Armory Build Instructions]\\n\\n\\n##Dependencies\\n\\n* GNU Compiler Collection  \\n Linux:   Install package `g++`\\n\\n* Crypto++  \\n Linux:   Install package `libcrypto++-dev`  \\n Windows: [Download][Windows Crypto Download]    \\n  \\n* SWIG  \\n Linux:   Install package `swig`  \\n Windows: [Download][Windows SWIG Download]  \\n MSVS: Copy swigwin-2.x directory next to cryptopp as `swigwin`  \\n  \\n* Python 2.6/2.7  \\n Linux:   Install package `python-dev`  \\n Windows: [Download][Windows Python Download]  \\n  \\n* Python Twisted -- asynchronous networking  \\n Linux:   Install package `python-twisted`  \\n Windows: [Download][Windows Twisted Download]  \\n  \\n* PyQt 4 (for Python 2.X)  \\n Linux:   Install packages `libqtcore4`, `libqt4-dev`, `python-qt4`, and `pyqt4-dev-tools`  \\n Windows: [Download][Windows QT Download]  \\n  \\n* qt4reactor.py -- combined eventloop for PyQt and Twisted  \\n All OS:  [Download][QT4 Reactor Download]  \\n\\n* pywin32  \\n Windows Only:  qt4reactor relies on pywin32 (for win32event module). [Download][Windows PyWin Download]  \\n  \\n* py2exe  \\n (OPTIONAL - if you want to make a standalone executable in Windows)  \\n Windows: [Download][Windows Py2Exe Download]  \\n\\n##Sample Code\\n\\nArmory contains over 25,000 lines of code, between the C++ and python libraries.  This can be very confusing for someone unfamiliar with the code (you).  Below I have attempted to illustrate the CONOPS (concept of operations) that the library was designed for, so you know how to use it in your own development activities.  There is a TON of sample code in the following:\\n\\n* C++ -   [BlockUtilsTest.cpp](cppForSwig/BlockUtilsTest.cpp)\\n* Python -   [Unit Tests](pytest/), [sample_armory_code.py](extras/sample_armory_code.py)\\n\\n\\n##License\\n\\nDistributed under the GNU Affero General Public License (AGPL v3)  \\nSee [LICENSE file](LICENSE) or [here][License]\\n\\n##Copyright\\n\\nCopyright (C) 2011-2015, Armory Technologies, Inc.\\n\\n\\n[Armory Build Instructions]: https://bitcoinarmory.com/building-from-source\\n[Windows Crypto Download]: http://www.cryptopp.com/#download\\n[Windows SWIG Download]: http://www.swig.org/download.html\\n[Windows Python Download]: http://www.python.org/getit/\\n[Windows Twisted Download]: http://twistedmatrix.com/trac/wiki/Downloads\\n[Windows QT Download]: http://www.riverbankcomputing.co.uk/software/pyqt/download\\n[QT4 Reactor Download]: https://launchpad.net/qt4reactor\\n[Windows PyWin Download]: http://sourceforge.net/projects/pywin32/files/pywin32/\\n[Windows Py2Exe Download]:  http://www.py2exe.org/\\n[License]: http://www.gnu.org/licenses/agpl.html\\n[Donation Image]: https://chart.googleapis.com/chart?chs=250x250&cht=qr&chl=bitcoin:1ArmoryXcfq7TnCSuZa9fQjRYwJ4bkRKfv?&label=Armory+Donation'},\n",
       " {'repo': 'bitcoin-dot-org/Bitcoin.org',\n",
       "  'language': 'HTML',\n",
       "  'readme_contents': '# Welcome to Bitcoin.org\\'s Codebase\\n\\nCurrent Build Status: ![Build Status](https://travis-ci.org/bitcoin-dot-org/bitcoin.org.svg?branch=master)\\n\\nLive site: [Bitcoin.org](https://bitcoin.org)\\n\\nReport problems or help improve the site by opening a [new issue](https://github.com/bitcoin-dot-org/bitcoin.org/issues/new) or [pull request](https://github.com/bitcoin-dot-org/bitcoin.org/compare).\\n\\n## Earn Bitcoin for Contributing\\nOpen issues [labeled with \"Bounty\"](https://github.com/bitcoin-dot-org/bitcoin.org/labels/Bounty)\\nhave bounties on them. Viewing the issue will reveal the value of the bounty.\\nSubmit a pull request resolving the issue along with an accompanying note or\\ncomment containing a bitcoin address and automatically receive a payment in the\\namount of the bounty if it gets merged.\\n\\n## How to Participate\\nThe following quick guides will help you get started:\\n\\n+ [Becoming a Contributor](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/become-a-contributor.md)\\n+ [Working with GitHub](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/working-with-github.md)\\n+ [Setting Up Your Environment](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/setting-up-your-environment.md)\\n+ [Improving Developer Documentation](https://github.com/bitcoin-dot-org/developer.bitcoin.org/)\\n+ [Assisting with Translations](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/assisting-with-translations.md)\\n+ [Adding Exchanges](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-exchanges.md)\\n+ [Managing Wallets](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/managing-wallets.md)\\n+ [Adding Events, Release Notes and Alerts](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-events-release-notes-and-alerts.md)\\n+ [Adding Blog Posts](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-blog-posts.md)\\n+ [Miscellaneous / Other](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/miscellaneous.md)\\n\\n### Code of Conduct\\n\\nParticipation in this project is subject to a [Code of Conduct](https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/CODE_OF_CONDUCT.md).\\n'},\n",
       " {'repo': 'jgarzik/cpuminer',\n",
       "  'language': 'C',\n",
       "  'readme_contents': '\\nThis is a multi-threaded CPU miner for bitcoin.\\n\\nLicense: See COPYING for details.\\n\\nDependencies:\\n\\tlibcurl\\t\\t\\thttp://curl.haxx.se/libcurl/\\n\\tjansson\\t\\t\\thttp://www.digip.org/jansson/\\n\\t\\t(jansson is optional, and is included in-tree)\\n\\nBasic *nix build instructions:\\n\\t./autogen.sh\\t# only needed if building from git repo\\n\\tCFLAGS=\"-O3 -Wall -msse2\" ./configure\\n\\tmake\\n\\nBasic WIN32 build instructions (on Fedora 13; requires mingw32):\\n\\t./autogen.sh\\t# only needed if building from git repo\\n\\trm -f mingw32-config.cache\\n\\tMINGW32_CFLAGS=\"-O3 -Wall -msse2\" mingw32-configure\\n\\tmake\\n\\t./mknsis.sh\\n\\nUsage instructions:  Run \"minerd --help\" to see options.\\n\\nAlso many issues and FAQs are covered in the forum thread\\ndedicated to this program,\\n\\thttps://bitcointalk.org/?topic=1925.0;all\\n\\n'},\n",
       " {'repo': 'yenom/BitcoinKit',\n",
       "  'language': 'Swift',\n",
       "  'readme_contents': '<p align=\"center\">\\n    <img src=\"https://user-images.githubusercontent.com/23519083/44261174-cc64aa00-a251-11e8-85b6-145e0bcae102.jpg\" alt=\"BitcoinKit: Let’s Play with Bitcoin in Swift!\">\\n    <a href=\"https://travis-ci.org/yenom/BitcoinKit\">\\n      <img src=\"http://img.shields.io/travis/yenom/BitcoinKit.svg\" alt=\"TravisCI\">\\n    </a>\\n    <a href=\"https://codecov.io/gh/yenom/BitcoinKit\">\\n      <img src=\"https://codecov.io/gh/yenom/BitcoinKit/branch/master/graph/badge.svg\" />\\n    </a>\\n    <a href=\"https://swift.org\">\\n        <img src=\"http://img.shields.io/badge/swift-5.0+-brightgreen.svg\" alt=\"Swift 5.0+\">\\n    </a>\\n    <a href=\"https://github.com/Carthage/Carthage\">\\n        <img src=\"https://img.shields.io/badge/Carthage-compatible-4BC51D.svg?style=flat\" alt=\"Carthage\">\\n    </a>\\n    <a href=\"https://swift.org/package-manager\">\\n        <img src=\"https://img.shields.io/badge/spm-compatible-brightgreen.svg?style=flat\" alt=\"Swift Package Manager\" />\\n    </a>\\n    <a href=\"http://cocoadocs.org/docsets/BitcoinKit\">\\n        <img src=\"https://img.shields.io/cocoapods/v/BitcoinKit.svg\" alt=\"CococaPods\" />\\n    </a>\\n</p>\\n\\n\\n### Welcome to BitcoinKit\\n\\nThe BitcoinKit library is a Swift implementation of the Bitcoin protocol which support both BCH and BTC. Improving the mobile ecosystem for Bitcoin developers is our mission.\\n\\nBitcoinKit allows maintaining a wallet, sending or receiving transactions without a full blockchain node. Following is a wallet app that demonstrates the way to use it.\\n\\nRelease notes are [here](CHANGELOG.md).\\n\\n<img src=\"https://user-images.githubusercontent.com/24402451/43367286-8753b4cc-9385-11e8-9fba-78e5283c1158.png\" width=\"320px\" />&nbsp;<img src=\"https://user-images.githubusercontent.com/24402451/43367196-523d5f46-9384-11e8-9fee-10e72318e67b.png\" width=\"319px\" />\\n\\nFeatures\\n--------\\n\\n- Encoding/decoding addresses: base58, Cashaddr, P2PKH, P2SH, WIF format.\\n- Transaction building blocks: inputs, outputs, scripts.\\n- EC keys and signatures.\\n- BIP32, BIP44 hierarchical deterministic wallets.\\n- BIP39 implementation.\\n- SPV features **are under construction**. The following functions cannot work well sometimes.\\n  - Send/receive transactions.\\n  - See current balance in a wallet.\\n\\n\\nRequirements\\n------------\\n- iOS 9.0+ / Mac OS X 10.11+ / tvOS 9.0+ / watchOS 2.0+\\n- Xcode 10.0+\\n- Swift 5.0+\\n\\n\\nInstallation\\n------------\\n\\n### [CocoaPods](https://guides.cocoapods.org/using/using-cocoapods.html)\\n\\n```bash\\n$ gem install cocoapods\\n```\\n\\n> CocoaPods 1.5.0+ is required to build BitcoinKit.\\n\\nTo integrate BitcoinKit into your Xcode project using CocoaPods, specify it in your `Podfile`:\\n\\n```ruby\\nsource \\'https://github.com/CocoaPods/Specs.git\\'\\nplatform :ios, \\'13.0\\'\\nuse_frameworks!\\n\\ntarget \\'<Your Target Name>\\' do\\n    pod \\'BitcoinKit\\', \\'~> 1.1.0\\'\\nend\\n```\\n\\nThen, run the following command:\\n```bash\\n$ pod install\\n```\\n\\n### [Carthage](https://github.com/Carthage/Carthage)\\nAdd this to `Cartfile`\\n\\n```ogdl\\ngithub \"yenom/BitcoinKit\" ~> 1.1.0\\n```\\n\\nRun `carthage update` to build the framework and drag the built `BitcoinKit.framework` into your Xcode project.\\n\\n\\n### [Swift Package Manager](https://github.com/apple/swift-package-manager)\\n\\nSimply add the following lines to dependencies of your Package.swift:\\n\\n```swift\\n.package(url: \"https://github.com/yenom/BitcoinKit.git\", .upToNextMinor(from: \"1.1.0\"))\\n```\\n\\nNote that following data types and features are currently not supported on Linux platform.  \\n\\n* `Peer` and `PeerGroup`\\n* SQLite based BlockStore\\n\\nContribute\\n----------\\nContributions to BitcoinKit are welcome and encouraged!\\nFeel free to open issues, drop us pull requests.\\n\\n## Authors & Maintainers\\n - [usatie](https://github.com/usatie)\\n\\n ## About\\n\\n <img width=220 src=\"https://user-images.githubusercontent.com/24402451/44437525-9169ca00-a5f5-11e8-8a77-9c1b906fb864.jpg\"></img>\\n\\n BitcoinKit is maintained and funded by Yenom.\\n Visit our [website](https://yenom.tech) or say hi on twitter ([@Yenom_wallet_en](https://twitter.com/Yenom_wallet_en))\\n\\nLicense\\n-------\\n\\nBitcoinKit is available under the MIT license. See the LICENSE file for more info.\\n\\n## Contributors\\n\\nThis project exists thanks to all the people who contribute. \\n<a href=\"graphs/contributors\"><img src=\"https://opencollective.com/BitcoinKit/contributors.svg?width=890&button=false\" /></a>\\n\\n\\n## Backers\\n\\nThank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/BitcoinKit#backer)]\\n\\n<a href=\"https://opencollective.com/BitcoinKit#backers\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/backers.svg?width=890\"></a>\\n\\n\\n## Sponsors\\n\\nSupport this project by becoming a sponsor. Your logo will show up here with a link to your website. [[Become a sponsor](https://opencollective.com/BitcoinKit#sponsor)]\\n\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/0/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/0/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/1/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/1/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/2/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/2/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/3/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/3/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/4/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/4/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/5/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/5/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/6/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/6/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/7/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/7/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/8/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/8/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/BitcoinKit/sponsor/9/website\" target=\"_blank\"><img src=\"https://opencollective.com/BitcoinKit/sponsor/9/avatar.svg\"></a>\\n\\n\\n'},\n",
       " {'repo': 'BitcoinExchangeFH/BitcoinExchangeFH',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '<p align=\"center\">\\n  <img src=\"docs/images/icon.jpg\">\\n</p>\\n\\n# BitcoinExchangeFH - Cryptocurrency exchange market data feed handler\\n\\nBitcoinExchangeFH is a slim application to record the price depth and trades in various exchanges. You can set it up quickly and record the all the exchange data in a few minutes!\\n\\nUsers can\\n\\n1. Streaming market data to a target application (via ZeroMQ)\\n2. Recording market data for backtesting and analysis.\\n3. Recording market data to a in-memory database and other applications can quickly access to it.\\n4. Customize the project for trading use.\\n\\n### MySQL\\n\\n<p align=\"center\">\\n  <img src=\"docs/images/sample.jpg\">\\n</p>\\n\\n### Kdb+\\n\\n<p align=\"center\">\\n  <img src=\"docs/images/sample2.jpg\">\\n</p>\\n\\n## Supported exchanges\\n\\nAll exchanges supported by [ccxt](https://github.com/ccxt/ccxt). Currently more than 130 exchanges are supported.\\n\\nWebsocket feeds of the following exchanges are supported by [cryptofeed](https://github.com/bmoscon/cryptofeed)\\n\\n- Bitfinex\\n\\n- Coinbase\\n\\n- Poloniex\\n\\n- Gemini\\n\\n- HitBTC\\n\\n- Bitstamp\\n\\n- BitMEX\\n\\n- Kraken\\n\\n- Binance\\n\\n- EXX\\n\\n- Huobi\\n\\n- OKCoin\\n\\n- OKEx\\n\\n\\nIf the exchange is not supported with websocket API feed, it will automatically fall into using its REST API feed.\\n\\n\\n## Supported database/channel\\n\\n- RDMBS (e.g. sqlite, MySQL, PostgreSQL)\\n\\n- ZeroMQ\\n\\n- Kdb+ (Coming soon)\\n\\n## Getting started\\n\\n```\\npip install bitcoinexchangefh\\nbitcoinexchangefh --configuration example/configuration.yaml\\n```\\n\\n## Configuration\\n\\nThe configuration follows [YAML](https://pyyaml.org/wiki/PyYAMLDocumentation) syntax and contains two sections\\n\\n- subscriptions\\n\\n- handlers\\n\\n\\n### Subscriptions\\n\\nSubscription section specifies the exchange and instruments to subscribe. \\n\\nThe first key is the exchange name and then follows the exchange details, \\n    \\n- instruments \\n\\n- number of depth (default is 5 if not specified)\\n\\n\\nFor example, \\n\\n```\\nsubscription:\\n    Binance:\\n        instruments:\\n            - XRP/BTC\\n            - BCH/BTC\\n        depth\\n    Poloniex:\\n        instruments:\\n            - ETH/BTC\\n        depth: 10\\n```\\n\\n### Handlers\\n\\nAfter receiving the order book or trade update, each handler is updated. For example, for SQL database handler, it is updated with the corresponding SQl statements.\\n\\nFor example,\\n\\n```\\nhandlers:\\n    sql: \\n        connection: \"sqlite://\"\\n    \\n```\\n\\n#### SQL handler\\n\\nThe following settings can be customized\\n\\n|Parameter|Description|\\n|---|---|\\n|connection|Database connection string required by [SQLAlchemy](https://docs.sqlalchemy.org/en/latest/core/engines.html)|\\n|is_rotate|Boolean indicating whether to rotate to record the table.|\\n|rotate_frequency|String in [format](https://docs.python.org/2/library/datetime.html#strftime-strptime-behavior) same as `strftime` and `strptime`|\\n\\n#### ZeroMQ handler\\n\\nThe feed handler acts as a [publisher](https://learning-0mq-with-pyzmq.readthedocs.io/en/latest/pyzmq/patterns/pubsub.html) in ZeroMQ. To receive the feed, please follow ZeroMQ instructions to start a [subscriber](tests/zmq/zmq_subscriber.py).\\n\\nThe following settings can be customized\\n\\n|Parameter|Description|\\n|---|---|\\n|connection|Connection [format](http://api.zeromq.org/3-2:zmq-connect) in ZeroMQ. For example, \"tcp://127.0.0.1:3456\"|\\n\\n\\n## Examples\\n\\nYou can first create a directory `.data` and run the command\\n\\n```\\n$ bitcoinexchangefh --configuration example/configuration.yaml \\n2020-08-07 23:33:32,110 INFO Loading runner\\n2020-08-07 23:33:32,110 INFO Creating handler sql\\n2020-08-07 23:33:32,205 INFO Loading handler SqlHandler\\n2020-08-07 23:33:32,710 INFO Loading exchange Binance\\n2020-08-07 23:33:34,062 INFO Loading exchange Bitmex\\n2020-08-07 23:33:40,203 INFO Start running the feed handler\\n2020-08-07 23:33:40,203 INFO Running handler sql\\n2020-08-07 23:33:40,210 INFO Running exchange Binance\\n2020-08-07 23:33:40,215 INFO Running SqlHandler\\n2020-08-07 23:33:40,219 INFO Running exchange Bitmex\\n2020-08-07 23:33:40,231 INFO Joining all the processes\\n2020-08-07 23:33:40,232 INFO Creating table binance_ethbtc_order\\n2020-08-07 23:33:40,263 INFO Created table binance_ethbtc_order\\n2020-08-07 23:33:40,265 INFO Creating table binance_xrpbtc_order\\n2020-08-07 23:33:40,294 INFO Created table binance_xrpbtc_order\\n2020-08-07 23:33:40,297 INFO Creating table bitmex_ethusd_order\\n2020-08-07 23:33:40,322 INFO Created table bitmex_ethusd_order\\n```\\n\\nAfter a while, the data is streamed into the file `.data/order_book.db`. You can terminate the process and the database contains the following tables.\\n\\n```\\n$ python -c \"import sqlite3; print(sqlite3.connect(\\'.data/order_book.db\\').execute(\\'SELECT name from sqlite_master where type= \\\\\"table\\\\\"\\').fetchall())\"\\n[(\\'binance_ethbtc_order\\',), (\\'binance_xrpbtc_order\\',), (\\'bitmex_ethusd_order\\',)]\\n\\n```\\n\\n\\n## Inquiries\\n\\nYou can first look up to the page [FAQ](https://github.com/gavincyi/BitcoinExchangeFH/wiki/FAQ). For more inquiries, you can either leave it in issues or drop me an email. I will get you back as soon as possible.\\n\\n## Compatibility\\nThe application is compatible with version higher or equal to python 3.0.\\n\\n## Contributions\\nAlways welcome for any contribution. Please fork the project, make the changes, and submit the merge request. :)\\n\\nFor any questions and comment, please feel free to contact me through email (gavincyi at gmail)\\n\\nYour comment will be a huge contribution to the project!\\n\\n## Continuity\\nIf you are not satisified with python performance, you can contact me to discuss migrating the project into other languages, e.g. C++.\\n'},\n",
       " {'repo': 'maxme/bitcoin-arbitrage',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '# bitcoin-arbitrage - opportunity detector and automated trading\\n\\nIt gets order books from supported exchanges and calculate arbitrage\\nopportunities between each markets. It takes market depth into account.\\n\\nCurrently supported exchanges to get data:\\n\\n- Bitstamp (USD, EUR)\\n- Paymium (EUR)\\n- Bitfinex (USD, EUR)\\n- bitFlyer (USD, EUR)\\n- Kraken (USD, EUR)\\n- OkCoin (CNY)\\n- Gemini (USD)\\n- BTCC (CNY)\\n- GDAX (USD, EUR)\\n- CEX.io (USD, EUR)\\n- Binance (USD)\\n\\nCurrently supported exchanges to automate trade:\\n\\n- Bitstamp (USD)\\n- Paymium (EUR)\\n\\n## WARNING\\n\\n**Real trading bots are included. Don\\'t put your API keys in config.py\\nif you don\\'t know what you are doing.**\\n\\n## Installation And Configuration\\n\\n```sh\\ncp arbitrage/config.py-example arbitrage/config.py\\n```\\n\\nThen edit config.py file to setup your preferences: watched markets\\nand observers\\n\\nYou need Python3 to run this program. To install on Debian, Ubuntu, or\\nvariants of them, use:\\n\\n```sh\\nsudo apt-get install python3 python3-pip python-nose\\n```\\n\\nTo use the observer XMPPMessager you will need to install sleekxmpp:\\n\\n```sh\\npip3 install sleekxmpp\\n```\\n\\n## Run\\n\\nTo run the opportunity watcher:\\n\\n```sh\\n$ python3 -m arbitrage -v\\n2013-03-12 03:52:14,341 [INFO] profit: 30.539722 EUR with volume: 10 BTC - buy at 29.3410 (MtGoxEUR) sell at29.4670 (Bitcoin24EUR) ~10.41%\\n2013-03-12 03:52:14,356 [INFO] profit: 66.283642 EUR with volume: 10 BTC - buy at 29.3410 (MtGoxEUR) sell at30.0000 (PaymiumEUR) ~22.59%\\n2013-03-12 03:52:14,357 [INFO] profit: 31.811390 EUR with volume: 10 BTC - buy at 29.3410 (MtGoxEUR) sell at30.0000 (IntersangoEUR) ~10.84%\\n2013-03-12 03:52:45,090 [INFO] profit: 9.774324 EUR with volume: 10 BTC - buy at 35.3630 (Bitcoin24EUR) sellat 35.4300 (PaymiumEUR) ~2.76%\\n```\\n\\nTo check your balance on an exchange (also a good way to check your accounts configuration):\\n\\n```sh\\npython3 -m arbitrage -m Paymium get-balance\\npython3 -m arbitrage -m Paymium,BitstampUSD get-balance\\n```\\n\\nRun tests\\n\\n```sh\\nnosetests arbitrage/\\n```\\n\\n### Alternative usage\\n\\nList supported public markets:\\n\\n```sh\\npython3 -m arbitrage list-public-markets\\n```\\n\\nHelp:\\n\\n```sh\\npython3 -m arbitrage -h\\n```\\n\\n## TODO\\n\\n- Tests\\n- Write documentation\\n- Add other exchanges:\\n  - icbit\\n- Update order books with a WebSocket client for supported exchanges\\n  (Kraken, Bitfinex, Paymium)\\n- Better history handling for observer \"HistoryDumper\" (Redis ?)\\n- Move EUR / USD from a market to an other:\\n  - Coupons\\n  - Ripple ?\\n  - Stable coins\\n  - Negative Operations\\n  - Add support for other cryptocurrencies and triangular arbitrage\\n\\n## LICENSE\\n\\nMIT\\n\\nCopyright (c) 2013 Maxime Biais <firstname.lastname@gmail.com>\\n\\nPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\\n\\nThe above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\\n\\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\\n'},\n",
       " {'repo': 'BitcoinUnlimited/BitcoinUnlimited',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '[Website](https://www.bitcoinunlimited.info)  | [Download](https://www.bitcoinunlimited.info/download) | [Setup](README.md)   |   [Miner](doc/miner.md)  |  [ElectronCash](doc/bu-electrum-integration.md)  |  [UnconfirmedChains](doc/unconfirmedTxChainLimits.md)\\n\\n[![Build Status](https://gitlab.com/bitcoinunlimited/BCHUnlimited/badges/dev/pipeline.svg?key_text=Build%20Status%20%28dev%29&key_width=110)](https://gitlab.com/bitcoinunlimited/BCHUnlimited/-/pipelines)\\n\\n# What is Bitcoin Cash?\\n\\nBitcoin Cash is an experimental new digital currency that enables instant payments to\\nanyone, anywhere in the world. Bitcoin Cash uses peer-to-peer technology to operate\\nwith no central authority: managing transactions and issuing money are carried\\nout collectively by the network. Bitcoin Unlimited is the name of open source\\nsoftware which enables the use of this currency.\\n\\nFor more information, as well as an immediately useable, binary version of\\nthe Bitcoin Unlimited software, see https://www.bitcoinunlimited.info/download, or read the\\n[original whitepaper](https://www.bitcoinunlimited.info/resources/bitcoin.pdf).\\n\\n\\n\\n# What is Bitcoin Unlimited?\\n\\nBitcoin Unlimited is an implementation of the Bitcoin client software that is based on Bitcoin Core.\\nHowever, Bitcoin Unlimited has a very different philosophy than Core.\\n\\nIt follows a philosophy and is administered by a formal process described in the [Articles of Federation](https://www.bitcoinunlimited.info/resources/BUarticles.pdf).\\nIn short, we believe in market-driven decision making, emergent consensus, and giving our users choices.\\n\\n\\n# Installing\\n\\nFor info on installing Bitcoin Unlimited see [INSTALL.md](INSTALL.md)\\n\\n# Building\\n\\nFor info on building Bitcoin Unlimited from sources, see\\n- [Dependencies](doc/dependencies.md)\\n- [Unix Build Notes](doc/build-unix.md)\\n- [Unix Build Notes (RPM)](doc/build-unix-rpm.md)\\n- [Windows Build Notes](doc/build-windows.md)\\n- [OpenBSD Build Notes](doc/build-openbsd.md)\\n- [macOS Build Notes](doc/build-macos.md)\\n- [Deterministic macOS DMG Notes](doc/README_macos.md)\\n- [Gitian Building Guide](doc/gitian-building.md)\\n\\nThey are not complete guides, but include notes on the necessary libraries, compile flags, etc.\\n\\n# Running / setup\\n\\n- [Running large unconfirmed transaction chain limits](doc/unconfirmedTxChainLimits.md)\\n- [Running an electron cash protocol server](doc/bu-electrum-integration.md)\\n- [Getting the most out of Xtreme thinblocks](bu-xthin.md)\\n- [Setting up an Xpedited Relay Network](bu-xpedited-forwarding.md)\\n- [Tor Support](doc/tor.md)\\n- [Init Scripts (systemd/upstart/openrc)](doc/init.md)\\n- [Using Bitcoin Unlimited for Mining](doc/miner.md)\\n\\n# Development\\n\\n- [Developer Notes](doc/developer-notes.md)\\n- [Contributing](CONTRIBUTING.md)\\n- [BUIP, BIP and Bitcoin Cash Specifications](doc/bips-buips-specifications.md)\\n- [Bitcoin Unlimited Improvement Proposal Archive](https://github.com/BitcoinUnlimited/BUIP)\\n- [Multiwallet Qt Development](doc/multiwallet-qt.md)\\n- [Release Notes](doc/release-notes.md)\\n- [Release Process](doc/release-process.md)\\n- [Translation Process](doc/translation_process.md)\\n- [Translation Strings Policy](doc/translation_strings_policy.md)\\n- [Unit Tests](doc/unit-tests.md)\\n- [Unauthenticated REST Interface](doc/REST-interface.md)\\n- [Shared Libraries](doc/shared-libraries.md)\\n- [Assets Attribution](contrib/debian/copyright)\\n- [Files](doc/files.md)\\n- [Fuzz-testing](doc/fuzzing.md)\\n\\n\\n# Online resources\\n\\n - [Issue Tracker](https://github.com/BitcoinUnlimited/BitcoinUnlimited/issues)\\n - [The Bitcoin Forum](https://www.bitco.in/forum)\\n - [Reddit /r/btc](https://www.reddit.com/r/btc)\\n - [Reddit /r/bitcoin_unlimited](https://www.reddit.com/r/bitcoin_unlimited)\\n - [Slack Channel](https://bitcoinunlimited.slack.com/)\\n\\n\\n\\n# License\\n\\nBitcoin Unlimited is released under the terms of the [MIT software license](http://www.opensource.org/licenses/mit-license.php). See [COPYING](COPYING) for more\\ninformation.\\nThis product includes software developed by the OpenSSL Project for use in the [OpenSSL Toolkit](https://www.openssl.org/). This product includes\\ncryptographic software written by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)), and UPnP software written by Thomas Bernard.\\n'},\n",
       " {'repo': 'Bitcoin-ABC/bitcoin-abc',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '[![Bitcoin ABC Logo](share/pixmaps/bitcoinabclogo.png \"Bitcoin ABC\")](https://www.bitcoinabc.org)\\n\\nThe goal of Bitcoin ABC is to create sound money that is usable by everyone in\\nthe world. This is a civilization-changing technology which will dramatically\\nincrease human flourishing, freedom, and prosperity. The project aims to\\nachieve this goal by implementing a series of optimizations and protocol\\nupgrades that will enable peer-to-peer digital cash to succeed at mankind scale.\\n\\nWhat is eCash?\\n---------------------\\n\\n[eCash](https://e.cash/) is a digital currency that enables instant payments to\\nanyone, anywhere in the world. It uses peer-to-peer technology to operate with\\nno central authority: managing transactions and issuing money are carried out\\ncollectively by the network. eCash is a descendant of Bitcoin.\\n\\nWhat is Bitcoin ABC?\\n--------------------\\n\\nBitcoin ABC is the name of open-source software which enables the use of\\neCash. It is a fork of the [Bitcoin Core](https://bitcoincore.org)\\nsoftware project.\\n\\nLicense\\n-------\\n\\nBitcoin ABC is released under the terms of the MIT license. See\\n[COPYING](COPYING) for more information or see\\n<https://opensource.org/licenses/MIT>.\\n\\nDevelopment Process\\n-------------------\\n\\nThis Github repository contains only source code of releases.\\n\\nBitcoin ABC development takes place at [reviews.bitcoinabc.org](https://reviews.bitcoinabc.org/)\\n\\nIf you would like to contribute, please read [CONTRIBUTING](CONTRIBUTING.md).\\n\\nDisclosure Policy\\n-----------------\\n\\nSee [DISCLOSURE_POLICY](DISCLOSURE_POLICY.md)\\n'},\n",
       " {'repo': 'petertodd/python-bitcoinlib',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '# python-bitcoinlib\\n\\nThis Python3 library provides an easy interface to the bitcoin data\\nstructures and protocol. The approach is low-level and \"ground up\", with a\\nfocus on providing tools to manipulate the internals of how Bitcoin works.\\n\\n\"The Swiss Army Knife of the Bitcoin protocol.\" - Wladimir J. van der Laan\\n\\n\\n## Requirements\\n\\n    sudo apt-get install libssl-dev\\n\\nThe RPC interface, `bitcoin.rpc`, is designed to work with Bitcoin Core v0.16.0.\\nOlder versions may work but there do exist some incompatibilities.\\n\\n\\n## Structure\\n\\nEverything consensus critical is found in the modules under bitcoin.core. This\\nrule is followed pretty strictly, for instance chain parameters are split into\\nconsensus critical and non-consensus-critical.\\n\\n    bitcoin.core            - Basic core definitions, datastructures, and\\n                              (context-independent) validation\\n    bitcoin.core.key        - ECC pubkeys\\n    bitcoin.core.script     - Scripts and opcodes\\n    bitcoin.core.scripteval - Script evaluation/verification\\n    bitcoin.core.serialize  - Serialization\\n\\nIn the future the bitcoin.core may use the Satoshi sourcecode directly as a\\nlibrary. Non-consensus critical modules include the following:\\n\\n    bitcoin          - Chain selection\\n    bitcoin.base58   - Base58 encoding\\n    bitcoin.bloom    - Bloom filters (incomplete)\\n    bitcoin.net      - Network communication (in flux)\\n    bitcoin.messages - Network messages (in flux)\\n    bitcoin.rpc      - Bitcoin Core RPC interface support\\n    bitcoin.wallet   - Wallet-related code, currently Bitcoin address and\\n                       private key support\\n\\nEffort has been made to follow the Satoshi source relatively closely, for\\ninstance Python code and classes that duplicate the functionality of\\ncorresponding Satoshi C++ code uses the same naming conventions: CTransaction,\\nCBlockHeader, nValue etc. Otherwise Python naming conventions are followed.\\n\\n\\n## Mutable vs. Immutable objects\\n\\nLike the Bitcoin Core codebase CTransaction is immutable and\\nCMutableTransaction is mutable; unlike the Bitcoin Core codebase this\\ndistinction also applies to COutPoint, CTxIn, CTxOut, and CBlock.\\n\\n\\n## Endianness Gotchas\\n\\nRather confusingly Bitcoin Core shows transaction and block hashes as\\nlittle-endian hex rather than the big-endian the rest of the world uses for\\nSHA256. python-bitcoinlib provides the convenience functions x() and lx() in\\nbitcoin.core to convert from big-endian and little-endian hex to raw bytes to\\naccommodate this. In addition see b2x() and b2lx() for conversion from bytes to\\nbig/little-endian hex.\\n\\n\\n## Module import style\\n\\nWhile not always good style, it\\'s often convenient for quick scripts if\\n`import *` can be used. To support that all the modules have `__all__` defined\\nappropriately.\\n\\n\\n# Example Code\\n\\nSee `examples/` directory. For instance this example creates a transaction\\nspending a pay-to-script-hash transaction output:\\n\\n    $ PYTHONPATH=. examples/spend-p2sh-txout.py\\n    <hex-encoded transaction>\\n\\n\\n## Selecting the chain to use\\n\\nDo the following:\\n\\n    import bitcoin\\n    bitcoin.SelectParams(NAME)\\n\\nWhere NAME is one of \\'testnet\\', \\'mainnet\\', \\'signet\\', or \\'regtest\\'. The chain currently\\nselected is a global variable that changes behavior everywhere, just like in\\nthe Satoshi codebase.\\n\\n\\n## Unit tests\\n\\nUnder bitcoin/tests using test data from Bitcoin Core. To run them:\\n\\n    python3 -m unittest discover\\n\\nAlternately, if Tox (see https://tox.readthedocs.org/) is available on your\\nsystem, you can run unit tests for multiple Python versions:\\n\\n    ./runtests.sh\\n\\nHTML coverage reports can then be found in the htmlcov/ subdirectory.\\n\\n## Documentation\\n\\nSphinx documentation is in the \"doc\" subdirectory. Run \"make help\" from there\\nto see how to build. You will need the Python \"sphinx\" package installed.\\n\\nCurrently this is just API documentation generated from the code and\\ndocstrings. Higher level written docs would be useful, perhaps starting with\\nmuch of this README. Pages are written in reStructuredText and linked from\\nindex.rst.\\n'},\n",
       " {'repo': 'mobnetic/BitcoinChecker',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': '# Bitcoin Checker\\r\\n\\r\\n__Bitcoin Checker__ is a FREE app to track the most recent prices of your favourite currency pairs (on over 80 supported exchanges) in many customizable ways (such as rich notifications, TTS voice announcements, Home and Lockscreen widget or multiple alarms).\\r\\n\\r\\nAs you know, the number of virtual currencies is increasing very fast. Currency pairs set on existing exchanges change almost every day and there is also a need to add newer and newer exchanges over time.\\r\\n_We proudly announce_ that [DataModule](dataModule) (containing exchanges and currency pairs) for Bitcoin Checker app is now _OPEN_ for our users to make this application _even better_! This means that _anyone_ can now:\\r\\n* Add support for a new exchange\\r\\n* Update currency pairs on their favourite exchange\\r\\n\\r\\n### Issues\\r\\nPlease submit all requests for new exchanges/currency pairs or bugs in Bitcoin Checker apps in the [Issues](https://github.com/mobnetic/BitcoinChecker/issues) section.\\r\\n\\r\\n##### Bitcoin Checker on Google Play Store:\\r\\nhttps://play.google.com/store/apps/details?id=com.mobnetic.coinguardian\\r\\n\\r\\n### Donate to Bitcoin Checker project:\\r\\n\\r\\n♥ __BTC__: 1KyLY5sT1Ffa6ctFPFpdL2bxhSAxNqfvMA\\r\\n\\r\\n♥ __DOGE__: D81kyZ49E132enb7ct7RcPGpjgsrN7bsd7\\r\\n\\r\\n♥ __LTC__: LZ3EiK42o5nbDW3cwiaKUptFQ9eBA3x1vw\\r\\n\\r\\n<!-- START doctoc generated TOC please keep comment here to allow auto update -->\\r\\n<!-- DON\\'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->\\r\\n## Table of Contents\\r\\n\\r\\n- [Introduction](#introduction)\\r\\n  - [Updating currency pairs on existing exchange:](#updating-currency-pairs-on-existing-exchange)\\r\\n    - [Adding new pair on Cryptsy?](#adding-new-pair-on-cryptsy)\\r\\n    - [Good practise:](#good-practise)\\r\\n    - [Some currencies are missing?](#some-currencies-are-missing)\\r\\n  - [Adding new exchange:](#adding-new-exchange)\\r\\n      - [Example:](#example)\\r\\n    - [1. New exchange configuration:](#1-new-exchange-configuration)\\r\\n    - [2. Providing currency pairs:](#2-providing-currency-pairs)\\r\\n    - [3. Providing API Url:](#3-providing-api-url)\\r\\n      - [3a. Providing other parameters in URL (advanced):](#3a-providing-other-parameters-in-url-advanced)\\r\\n    - [4. Parsing API response:](#4-parsing-api-response)\\r\\n      - [4a. Parsing non JSONObject responses (advanced):](#4a-parsing-non-jsonobject-responses-advanced)\\r\\n    - [5. Parsing error (not required):](#5-parsing-error-not-required)\\r\\n    - [6. Fetching currency pairs directly from exchange:](#6-fetching-currency-pairs-directly-from-exchange)\\r\\n    - [7. Enabling exchange:](#7-enabling-exchange)\\r\\n  - [Advanced things](#advanced-things)\\r\\n    - [Multiple requests per exchange:](#multiple-requests-per-exchange)\\r\\n    - [Multiple requests while fetching currency pairs](#multiple-requests-while-fetching-currency-pairs)\\r\\n\\r\\n<!-- END doctoc generated TOC please keep comment here to allow auto update -->\\r\\n<!-- To regenerate doctoc, run `doctoc --title \"## Table of Contents\" README.md` -->\\r\\n<!-- https://github.com/thlorenz/doctoc -->\\r\\n\\r\\n# Introduction\\r\\nTo start working, you should fork this repo. It basically contains two projects:\\r\\n* [DataModule](/dataModule): Library project that stores information about exchanges and currencies used in Bitcoin Checker. This is the project that you will work with.\\r\\n* [DataModuleTester](/dataModuleTester): Simple project that provides minimal interface in order to launch and test your changes - to see if they will work :)\\r\\n\\r\\nThe whole tutorial described below refers to the [DataModule](dataModule) project because only this project is meant to be edited by users. After making your changes, please create a pull request to the original repo.\\r\\n\\r\\n\\r\\n## Updating currency pairs on existing exchange:\\r\\n*__Note if particular exchange supports dynamic currency pairs syncing mechanism there is NO need to add pairs manually here.__ *\\r\\n\\r\\nTo update currency pairs on your favourite exchange, you have to find the corresponding exchange class file in the [com.mobnetic.coinguardian.model.market](dataModule/src/main/java/com/mobnetic/coinguardian/model/market) package.\\r\\nIn every exchange file there is a `CURRENCY_PAIRS` HashMap that contains a base currency (as a key) and a list of counter currencies. Every combination of base and counter currency represents one currency pair.\\r\\n\\r\\n```java\\r\\nCURRENCY_PAIRS.put(VirtualCurrency.LTC,  // Base currency\\r\\n  new String[]{\\r\\n    VirtualCurrency.BTC,             // Counter currency\\r\\n    Currency.USD,                    // Counter currency\\r\\n    Currency.RUR,                    // Counter currency\\r\\n    Currency.EUR                     // Counter currency\\r\\n  }\\r\\n);\\r\\n```\\r\\nThis example from [BTC-e](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Btce.java) represents 4 pairs: `LTC/BTC`, `LTC/USD`, `LTC/RUR` and `LTC/EUR`.\\r\\n\\r\\n### Adding new pair on Cryptsy?\\r\\nThis is generally enough, but while adding a new currency pair on [Cryptsy](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Cryptsy.java) you also need to provide a special pair ID. Please include it in a map called `CURRENCY_PAIRS_IDS`, as shown here:\\r\\n\\r\\n```java\\r\\n[...]\\r\\nCURRENCY_PAIRS_IDS.put(\"DOGE_BTC\", 132);\\r\\nCURRENCY_PAIRS_IDS.put(\"DOGE_LTC\", 135);\\r\\n[...]\\r\\n```\\r\\n\\r\\nThe simplest way to find the pair ID is to click or hover on that particular pair in the trading section on the Cryptsy website. The number at the end of the page url represents the ID of that particular pair: https://www.cryptsy.com/markets/view/132\\r\\n\\r\\n### Good practise:\\r\\nTry to keep alphabetical order of base currencies (or even with counter currencies) but sometimes it\\'s also good to mirror the order from the exchange site.\\r\\n\\r\\nWhile adding new pairs, you should use currency names from these two classes:\\r\\n- [Currency](dataModule/src/main/java/com/mobnetic/coinguardian/model/currency/Currency.java) - where you can find fiat currencies\\r\\n- [VirtualCurrency](dataModule/src/main/java/com/mobnetic/coinguardian/model/currency/VirtualCurrency.java) - where all of the crypto/virtual currencies are stored\\r\\n\\r\\n### Some currencies are missing?\\r\\nYou want to add some currency pairs but one currency (or both) is missing in Currency or VirtualCurrency class?\\r\\nJust add them to the Currency or VirtualCurrency class. Please put all fiat/normal currencies in the Currency.java file and all crypto/virtual currencies in VirtualCurrency.java.\\r\\n\\r\\n\\r\\n## Adding new exchange:\\r\\n#### Example:\\r\\nPlease see the example of a class that represents a single exchange here - [MarketExample](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/example/MarketExample.java)\\r\\n\\r\\n### 1. New exchange configuration:\\r\\nTo add support for a new exchange, you have to provide some constants describing that particular exchange:\\r\\n* `NAME` - name of the exchange that will be displayed in the app.\\r\\n* `TTS_NAME` - name of the exchange that will be used in spoken announements. Sometimes it\\'s just fine to put `NAME` here (see [Kraken](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Kraken.java)), but sometimes it\\'s better to provide a more spoken friendly version (like on [McxNOW](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/McxNOW.java) - \"MCX now\").\\r\\n* `URL` - this field stores the Url for the Ticker API. Most often it contains two parameters, but sometimes it has one (`%1$s` and `%2$s`). These parameters are replaced with currency names or the selected currency pair. Providing a URL is described in the next section.\\r\\n* `CURRENCY_PAIRS` - map of all currencies supported by this exchange - described later.\\r\\n\\r\\nThese constants (without `URL`) should be provided in the default constructor:\\r\\n\\r\\n```java\\r\\npublic MarketExample() {\\r\\n  super(NAME, TTS_NAME, CURRENCY_PAIRS);\\r\\n}\\r\\n```\\r\\n\\r\\n### 2. Providing currency pairs:\\r\\nIf given exchanges provides a mechanism to fetch currency pairs dynamically, there is no need to specify them manually then.   Please see [this section](# 6-fetching-currency-pairs-directly-from-exchange).\\r\\n\\r\\nOtherwise you have to specify which currency pairs are supported by your new exchange. Description for this is done above, in the [Updating currency pairs on existing exchange](https://github.com/mobnetic/BitcoinCheckerDataModule# updating-currency-pairs-on-existing-exchange) section.\\r\\n\\r\\n### 3. Providing API Url:\\r\\nThe API Url is provided by the getUrl method. The simplest implementation is to just return the URL field. Sometimes, the Url requires some additional parameters (like currency names) - then you have to provide them using ```String.format()``` method.\\r\\nSee examples below:\\r\\n\\r\\n##### Example without parameters:\\r\\n* API example: https://www.bitstamp.net/api/ticker/\\r\\n* URL field: https://www.bitstamp.net/api/ticker/\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic String getUrl(int requestId, CheckerInfo checkerInfo) {\\r\\n  return URL;\\r\\n}\\r\\n```\\r\\n\\r\\n##### Example with arguments - for given currency pair:\\r\\n* API example: https://anxpro.com/main/stats?ccyPair=BTCUSD\\r\\n* URL field: https://anxpro.com/main/stats?ccyPair=%1$s%2$s\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic String getUrl(int requestId, CheckerInfo checkerInfo) {\\r\\n  return String.format(URL, checkerInfo.getCurrencyBase(), checkerInfo.getCurrencyCounter());\\r\\n}\\r\\n```\\r\\n\\r\\n\\r\\nNote that currency names are always in uppercase; however, some APIs requires them to be in lowercase.\\r\\n\\r\\n##### Example with lowercase currency parameters:\\r\\n* API example: https://bter.com/api/1/ticker/btc_cny\\r\\n* URL field: https://bter.com/api/1/ticker/%1$s_%2$s\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic String getUrl(int requestId, CheckerInfo checkerInfo) {\\r\\n  return String.format(URL, checkerInfo.getCurrencyBaseLowerCase(), checkerInfo.getCurrencyCounterLowerCase());\\r\\n}\\r\\n```\\r\\n\\r\\n#### 3a. Providing other parameters in URL (advanced):\\r\\nSometimes there is a need to include some kind of pair ID instead of just currency names. Please see [Cryptsy](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Cryptsy.java) as an example. There is a separate `CURRENCY_PAIRS_IDS` map that holds pair ids:\\r\\n\\r\\n```java\\r\\n[...]\\r\\nCURRENCY_PAIRS_IDS.put(\"DMD_BTC\", 72);\\r\\nCURRENCY_PAIRS_IDS.put(\"DOGE_BTC\", 132);\\r\\nCURRENCY_PAIRS_IDS.put(\"DOGE_LTC\", 135);\\r\\nCURRENCY_PAIRS_IDS.put(\"DVC_BTC\", 40);\\r\\n[...]\\r\\n```\\r\\n\\r\\nWhile providing the URL, we need to obtain the proper ID that is associated with this pair:\\r\\n\\r\\n##### Example for DOGE/BTC (id=132) on Cryptsy:\\r\\n* API example: http://pubapi.cryptsy.com/api.php?method=singlemarketdata&marketid=132\\r\\n* URL field: http://pubapi.cryptsy.com/api.php?method=singlemarketdata&marketid=%1$s\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic String getUrl(int requestId, CheckerInfo checkerInfo) {\\r\\n  final String pairString = String.format(\"%1$s_%2$s\", checkerInfo.getCurrencyBase(), checkerInfo.getCurrencyCounter());\\r\\n  if(CURRENCY_PAIRS_IDS.containsKey(pairString))\\r\\n    return String.format(URL, String.valueOf(CURRENCY_PAIRS_IDS.get(pairString)));\\r\\n  return URL;\\r\\n}\\r\\n```\\r\\n\\r\\n### 4. Parsing API response:\\r\\nWhile parsing the response from the exchange you have to fill the fieds of [Ticker](dataModule/src/main/java/com/mobnetic/coinguardian/model/Ticker.java) object.\\r\\nIf the API response is just in plain JSON object, you can parse it in the parseTickerFromJsonObject method:\\r\\n\\r\\n```java\\r\\n@Override\\r\\nprotected void parseTickerFromJsonObject(int requestId, JSONObject jsonObject, Ticker ticker, CheckerInfo checkerRecord) throws Exception {\\r\\n  ticker.bid = jsonObject.getDouble(\"bid\");\\r\\n  ticker.ask = jsonObject.getDouble(\"ask\");\\r\\n  ticker.vol = jsonObject.getDouble(\"volume\");\\r\\n  ticker.high = jsonObject.getDouble(\"high\");\\r\\n  ticker.low = jsonObject.getDouble(\"low\");\\r\\n  ticker.last = jsonObject.getDouble(\"last\");\\r\\n  ticker.timestamp = jsonObject.getLong(\"timestamp\");\\r\\n}\\r\\n```\\r\\n\\r\\n__IMPORTANT:__ The ticker.last field is mandatory; the rest of the fields are optional.\\r\\n__NOTE:__ Parsing the `timestamp` field (in millis) is not required. If omitted, Bitcoin Checker will fill it with `now` date. If you want to parse this information, please note that some exchanges provide time in different formats (like seconds or nanos) so you have to multiply or divide it to get the time in millis format. You can use `TimeUtils.NANOS_IN_MILLIS` or `TimeUtils.MILLIS_IN_SECOND` constants from [TimeUtils](dataModule/src/main/java/com/mobnetic/coinguardian/util/TimeUtils.java) for that.\\r\\n\\r\\n#### 4a. Parsing non JSONObject responses (advanced):\\r\\nSometimes responses are more complicated than plain JSON, then you should use the `parseTicker` method. The default implementation try to parse received response as a `JSONObject`, but you can parse also other formats by overriding this method:\\r\\n\\r\\n```java\\r\\nprotected void parseTicker(int requestId, String responseString, Ticker ticker, CheckerInfo checkerInfo) throws Exception {\\r\\n  parseTickerFromJsonObject(requestId, new JSONObject(responseString), ticker, checkerInfo);\\r\\n}\\r\\n```\\r\\n\\r\\nHere you can find examples of usage:\\r\\n* [Huobi](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Huobi.java): \"almost\" JSON object response, there is a need to trim some characters at the begining and at the end of the response\\r\\n* [MintPal](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/MintPal.java): JSON array response (instead of JSON object)\\r\\n* [McxNOW](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/McxNOW.java): XML based response\\r\\n\\r\\n### 5. Parsing error (not required):\\r\\nSometimes an exchange is down but with some error message in their API (See [Crypto-Trade](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/CryptoTrade.java) as an example). You can also handle this situation and display an error message directly from the exchange to the user. There are two methods related with it and they are designed in a similar way to parsing a normal response:\\r\\n\\r\\n```java\\r\\nprotected String parseErrorFromJsonObject(int requestId, JSONObject jsonObject, CheckerInfo checkerInfo);\\r\\n```\\r\\nor if JSONObject is not suitable, you can override following method:\\r\\n```java\\r\\nprotected String parseError(int requestId, String responseString, CheckerInfo checkerInfo);\\r\\n```\\r\\n\\r\\n### 6. Fetching currency pairs directly from exchange:\\r\\nIf there is any API (or other way) to obtain currency pairs directly from exchange (without need to update them manually) you should implement currency pairs fetching functionality instead of providing a static set of currency pairs.\\r\\nSee example on  [Basebit](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Basebit.java).\\r\\nBecause there are no static currency pairs defined - you should pass a `null` as a last argument in the constructor and do NOT initialize `CURRENCY_PAIRS` at all. You need to provide the url to fetch currency pairs instead:\\r\\n\\r\\n```java\\r\\nprivate final static String URL_CURRENCY_PAIRS = \"http://pubapi.cryptsy.com/api.php?method=marketdatav2\";\\r\\n\\r\\npublic SampleExchange() {\\r\\n  super(NAME, TTS_NAME, null);  // <- null intead of CURRENCY_PAIRS map\\r\\n}\\r\\n\\r\\n[...]\\r\\n\\r\\n@Override\\r\\npublic String getCurrencyPairsUrl(int requestId) {\\r\\n  return URL_CURRENCY_PAIRS;\\r\\n}\\r\\n```\\r\\nThen you need to do parsing in:\\r\\n\\r\\n```java\\r\\nprotected void parseCurrencyPairsFromJsonObject(int requestId, JSONObject jsonObject, List<CurrencyPairInfo> pairs)\\r\\nor\\r\\nprotected void parseCurrencyPairs(int requestId, String responseString, List<CurrencyPairInfo> pairs)\\r\\n```\\r\\n\\r\\nWhile parsing currency pairs you need to create [CurrencyPairInfo](dataModule/src/main/java/com/mobnetic/coinguardian/model/CurrencyPairInfo.java) and add it to `List<CurrencyPairInfo> pairs`. The last argument `pairId` is a unique pair id used on some exchanges. You can just pass `null` if there is no such thing on given exchange.\\r\\n\\r\\nYou can also use multiple requests to fetch currency pairs from exchange - it is described in section [Multiple requests while fetching currency pairs](# multiple-requests-while-fetching-currency-pairs).\\r\\n\\r\\n### 7. Enabling exchange:\\r\\nTo enable a newly created exchange, you should add the corresponding line at the bottom of `MarketsConfig` file:\\r\\n\\r\\n```java\\r\\nstatic {\\r\\n  [...]\\r\\n  addMarket(new MyNewExchangeClass());\\r\\n}\\r\\n```\\r\\n\\r\\n## Advanced things\\r\\n### Multiple requests per exchange:\\r\\nSome exchanges do not provide a nice ticker api with the all important information (bid, ask, vol, high, low, last), so there is a need to perform a few requests (for example 2) to acquire as much information as possible.\\r\\nThese requests will be performed in a sequense and a new price notification will appear when all of these requests are finished.\\r\\nSee the [Poloniex](dataModule/src/main/java/com/mobnetic/coinguardian/model/market/Poloniex.java) exchange as a good example. In order to perform 2 requests you have to override `getNumOfRequests` method:\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic int getNumOfRequests(CheckerInfo checkerRecord) {\\r\\n  return 2;\\r\\n}\\r\\n```\\r\\n\\r\\nThen make use of requestId variable passed to `getUrl` and `parseTickerFromJsonObject` methods.\\r\\n`requestId` variable is incremented from `0` to `numOfRequests-1` for every new request made.\\r\\nFrom the first request, we are able to obtain only the `last` price. We want to obtain also the `bid` and `ask` values, so we do another request for the orders list:\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic String getUrl(int requestId, CheckerInfo checkerInfo) {\\r\\n  if(requestId==0)\\r\\n    return URL;\\r\\n  else\\r\\n    return String.format(URL_ORDERS, checkerInfo.getCurrencyCounter(), checkerInfo.getCurrencyBase()); // Reversed currencies\\r\\n}\\r\\n\\r\\n@Override\\r\\nprotected void parseTickerFromJsonObject(int requestId, JSONObject jsonObject, Ticker ticker, CheckerInfo checkerInfo) throws Exception {\\r\\n  if(requestId==0) {\\r\\n    ticker.last = jsonObject.getDouble(checkerInfo.getCurrencyCounter()+\"_\"+checkerInfo.getCurrencyBase());  // Reversed currencies\\r\\n  } else {\\r\\n    ticker.bid = getFirstPriceFromOrder(jsonObject, \"bids\");\\r\\n    ticker.ask = getFirstPriceFromOrder(jsonObject, \"asks\");\\r\\n  }\\r\\n}\\r\\n```\\r\\n\\r\\n### Multiple requests while fetching currency pairs\\r\\nYou can also use multiple requests support for fetching currency pairs from exchange. The implementation is almost identical - just override following method:\\r\\n\\r\\n```java\\r\\n@Override\\r\\npublic int getCurrencyPairsNumOfRequests() {\\r\\n  return 2;\\r\\n}\\r\\n```\\r\\nThen use the `requestId` argument in the same way as in previous section.\\r\\n'},\n",
       " {'repo': 'bisq-network/bisq',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': '<p align=\"center\">\\n  <a href=\"https://bisq.network\">\\n    <img src=\"https://bisq.network/images/bisq-logo.svg\"/>\\n  </a>\\n</p>\\n\\n<h3 align=\"center\">\\n    \\n![Actions Status](https://github.com/bisq-network/bisq/workflows/Build%20Bisq/badge.svg)\\n\\n\\n## What is Bisq?\\n\\nBisq is a safe, private and decentralized way to exchange bitcoin for national currencies and other digital assets. Bisq uses peer-to-peer networking and multi-signature escrow to facilitate trading without a third party. Bisq is non-custodial and incorporates a human arbitration system to resolve disputes.\\n\\nTo learn more, see the doc and video at https://bisq.network/intro.\\n\\n\\n## Get started using Bisq\\n\\nFollow the step-by-step instructions at https://bisq.network/get-started.\\n\\n\\n## Contribute to Bisq\\n\\nSee [CONTRIBUTING.md](CONTRIBUTING.md) and the [developer docs](docs/README.md).\\n'},\n",
       " {'repo': 'bitcoin-abe/bitcoin-abe',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': 'Apache 2 FastCGI setup on Debian/Ubuntu\\r\\n=======================================\\r\\n\\r\\nThis document describes how to install and run Abe as a FastCGI\\r\\nprocess under Apache 2 on a Debian GNU/Linux or Ubuntu system.\\r\\nAdvantages of FastCGI over the built-in HTTP server include:\\r\\n\\r\\n    * lets browsers cache static content for better performance;\\r\\n    * can integrate with an existing website, no :2750 in URLs.\\r\\n\\r\\nThese instructions assume root privileges.  To begin a privileged\\r\\nsession in a terminal window, issue \"sudo -i\" (Ubuntu) or \"su -\"\\r\\n(Debian).\\r\\n\\r\\nInstall required packages:\\r\\n\\r\\n    apt-get install apache2 libapache2-mod-fcgid python-flup\\r\\n    apt-get install python-crypto\\r\\n\\r\\nChange directory to the Abe distribution and install Abe:\\r\\n\\r\\n    cd bitcoin-abe\\r\\n    python setup.py install\\r\\n\\r\\nReplace YOUR.ABE.DOMAIN below with a domain that resolves to this\\r\\nhost.  The site will be http://YOUR.ABE.DOMAIN/.  To embed Abe in an\\r\\nexisting site (e.g., http://YOUR.DOMAIN/abe/) prepend a path (e.g.,\\r\\n\"/abe\") in the Alias directives, place them in your existing\\r\\nsites-available file instead of a new VirtualHost, and merge or create\\r\\nyour site\\'s /robots.txt with adjusted paths from Abe/htdocs/robots.txt.\\r\\n\\r\\nReplace HTDOCS/DIRECTORY below with the directory containing abe.css;\\r\\nthe Apache process must have permission to read it.  The following\\r\\ncommand displays the correct value:\\r\\n\\r\\n    python -m Abe.abe --print-htdocs-directory\\r\\n\\r\\nOptionally, replace \"/usr/lib/cgi-bin\" below with another directory;\\r\\nApache must have the directory configured with Options +ExecCGI.\\r\\n\\r\\nCreate file /etc/apache2/sites-available/abe with these contents:\\r\\n\\r\\n    <VirtualHost *:80>\\r\\n        ServerName YOUR.ABE.DOMAIN\\r\\n        Alias /static/ HTDOCS/DIRECTORY/\\r\\n        Alias /robots.txt HTDOCS/DIRECTORY/robots.txt\\r\\n        Alias /favicon.ico HTDOCS/DIRECTORY/favicon.ico\\r\\n        Alias / /usr/lib/cgi-bin/abe.fcgi/\\r\\n\\r\\n        # Raise this if you get server errors mentioning \"mod_fcgid:\\r\\n        # read data timeout in 40 seconds\"\\r\\n        #FcgidIOTimeout 40\\r\\n\\r\\n        # Uncomment to log Abe requests.\\r\\n        #ErrorLog /var/log/abe_error.log\\r\\n        #LogLevel info\\r\\n        #CustomLog /var/log/abe_access.log combined\\r\\n    </VirtualHost>\\r\\n\\r\\nEnable the new configuration:\\r\\n\\r\\n    a2ensite abe\\r\\n    service apache2 reload\\r\\n\\r\\nReplace USER with your Unix user name and create file\\r\\n/usr/lib/cgi-bin/abe.fcgi with these contents:\\r\\n\\r\\n    #! /usr/bin/python\\r\\n    import subprocess, sys, os\\r\\n    command=[\"sudo\", \"-u\", \"USER\", \"/home/USER/cgi-bin/abe\", str(os.getpid())]\\r\\n    subprocess.Popen(command, stdin=sys.stdin).wait()\\r\\n\\r\\nMake the file executable:\\r\\n\\r\\n    chmod +x /usr/lib/cgi-bin/abe.fcgi\\r\\n\\r\\nReplace USER with your Unix user name and use visudo(1) to append\\r\\nthe following to /etc/sudoers:\\r\\n\\r\\n    # This allows the Apache account (www-data) to run Abe as USER.\\r\\n    www-data ALL=(USER) NOPASSWD: /home/USER/cgi-bin/abe\\r\\n\\r\\nPut configuration such as database connection parameters in\\r\\n/home/USER/abe.conf or change the location below.  See the sample\\r\\nabe.conf in the Abe distribution for file format.  IMPORTANT: Make\\r\\nsure the configuration does NOT contain a \"host\" or \"port\" option.\\r\\n\\r\\nCreate file /home/USER/cgi-bin/abe with these contents:\\r\\n\\r\\n    #! /bin/sh\\r\\n    PYTHONUNBUFFERED=1 exec python -m Abe.abe \\\\\\r\\n    --config /home/USER/abe.conf --static-path static/ --watch-pid=\"$1\"\\r\\n\\r\\nMake the file executable:\\r\\n\\r\\n    chmod +x /home/USER/cgi-bin/abe\\r\\n\\r\\nAbe should be reachable at http://YOUR.ABE.DOMAIN/.  Exit the\\r\\nprivileged session:\\r\\n\\r\\n    exit\\r\\n'},\n",
       " {'repo': 'sipa/bitcoin-seeder',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': \"bitcoin-seeder\\n==============\\n\\nBitcoin-seeder is a crawler for the Bitcoin network, which exposes a list\\nof reliable nodes via a built-in DNS server.\\n\\nFeatures:\\n* regularly revisits known nodes to check their availability\\n* bans nodes after enough failures, or bad behaviour\\n* accepts nodes down to v0.3.19 to request new IP addresses from,\\n  but only reports good post-v0.3.24 nodes.\\n* keeps statistics over (exponential) windows of 2 hours, 8 hours,\\n  1 day and 1 week, to base decisions on.\\n* very low memory (a few tens of megabytes) and cpu requirements.\\n* crawlers run in parallel (by default 24 threads simultaneously).\\n\\nREQUIREMENTS\\n------------\\n\\n$ sudo apt-get install build-essential libboost-all-dev libssl-dev\\n\\nUSAGE\\n-----\\n\\nAssuming you want to run a dns seed on dnsseed.example.com, you will\\nneed an authorative NS record in example.com's domain record, pointing\\nto for example vps.example.com:\\n\\n$ dig -t NS dnsseed.example.com\\n\\n;; ANSWER SECTION\\ndnsseed.example.com.   86400    IN      NS     vps.example.com.\\n\\nOn the system vps.example.com, you can now run dnsseed:\\n\\n./dnsseed -h dnsseed.example.com -n vps.example.com\\n\\nIf you want the DNS server to report SOA records, please provide an\\ne-mail address (with the @ part replaced by .) using -m.\\n\\nCOMPILING\\n---------\\n\\nCompiling will require boost and ssl.  On debian systems, these are provided\\nby `libboost-dev` and `libssl-dev` respectively.\\n\\n$ make\\n\\nThis will produce the `dnsseed` binary.\\n\\nTESTING\\n-------\\n\\nIt's sometimes useful to test `dnsseed` locally to ensure it's giving good\\noutput (either as part of development or sanity checking). You can inspect\\n`dnsseed.dump` to inspect all nodes being tracked for crawling, or you can\\nissue DNS requests directly. Example:\\n\\n$ dig @:: -p 15353 dnsseed.example.com\\n       ^       ^    ^\\n       |       |    |__ Should match the host (-h) argument supplied to dnsseed\\n       |       |\\n       |       |_______ Port number (example uses the user space port; see below)\\n       |\\n       |_______________ Explicitly call the DNS server on localhost\\n\\n\\nRUNNING AS NON-ROOT\\n-------------------\\n\\nTypically, you'll need root privileges to listen to port 53 (name service).\\n\\nOne solution is using an iptables rule (Linux only) to redirect it to\\na non-privileged port:\\n\\n$ iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 15353\\n\\nIf properly configured, this will allow you to run dnsseed in userspace, using\\nthe -p 15353 option.\\n\\nAnother solution is allowing a binary to bind to ports < 1024 with setcap (IPv6 access-safe)\\n\\n$ setcap 'cap_net_bind_service=+ep' /path/to/dnsseed\\n\"},\n",
       " {'repo': 'imfly/bitcoin-on-nodejs',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# 《Node.js区块链开发》\\n\\n**【注】本书停更了很久，但是仍然获得众多小伙伴的持续关注，应大家要求，更新了其中的链接，后续也会慢慢分享亿书的新发展，并将技术和思考全部分享出来！**\\n\\n交流欢迎加我微信（请注明 `我是xx，来自github，申请加入俱乐部`，请务必告知实名，不加无名无姓陌生人，见谅），拉你进中国区块链俱乐部群：\\n\\n<img src=\"./styles/images/third/club.png\" alt=\"中国区块链俱乐部\" width=\"50%\" height=\"50%\">\\n\\n## 关于（About）\\n\\n亿书，让有知识的人富起来。我们的产品，将全部基于P2P网络进行开发设计，面向未来进行技术研发。\\n\\n本书可以作为区块链开发的入门书籍（正式出版《Node.js区块链开发》），也可以作为亿书的官方开发文档。\\n\\n**无论您是研究区块链，或者学习Node.js前后端开发技术，本书都值得参考。**\\n\\n亿书的目标是打造人人可用的去中心化软件，促进人类知识分享。与其他区块链产品不同，我们以提供落地可用的软件为核心，力争成为人类第一个“零门槛”的区块链产品。更多详情，请看[关于亿书](./5-%E9%99%84%E5%BD%95/6-%E5%85%B3%E4%BA%8E%E4%BA%BF%E4%B9%A6.md)\\n\\n本书写作，也是亿书的最佳实践，从写到发布，简单、快捷。文章暂时在[github](https://github.com/imfly/bitcoin-on-nodejs)上免费发布，永久免费访问地址: <http://bitcoin-on-nodejs.ebookchain.org>\\n\\n**注**: 本书永久`免费`访问地址: <http://bitcoin-on-nodejs.ebookchain.org> 。\\n\\n**但是该版本与《Node.js区块链开发》并不同步，保持了编程出版之前的原始状态。因为出版社三审三校，历时数月，修改和调整太多，为了沟通方便，都是word格式，同步需要耗费太多时间。另外，保持原貌，让读者有机会对比了解，任何东西都不是简单为之。**\\n\\n亿书技术已经全部用在新产品，请关注：<https://datm.link>\\n\\n## 日志（Log）\\n\\n- [x] 2021-12-06 修改升级信息，将旧的链接进行修正，方便大家参阅\\n- [x] 2016-10-15 收录巴比特创始人兼CEO @长侠 的荐序。\\n- [x] 2016-10-14 整体校对交稿，交付印刷\\n- [x] 2016-10-12 完成第30篇: 完成致谢\\n- [x] 2016-10-10 完成第29篇: 完成后记\\n- [x] 2016-10-08 完成第28篇: 生产环境下的pm2部署，补充部分名词解释\\n- [x] 2016-10-06 完成第27篇: 测试\\n- [x] 2016-09-21 完成第26篇: 区块链架构设计简介\\n- [x] 2016-09-14 发布第25篇: 开发通用的HTML组件\\n- [x] 2016-09-02 发布第24篇: 轻松从Js文件生成UML类图\\n- [x] 2016-08-18 发布第23篇: 学点函数式编程\\n- [x] 2016-08-10 发布第22篇: DPoS机制\\n- [x] 2016-07-28 发布第21篇: 区块链\\n- [x] 2016-07-14 发布第20篇: 自序\\n- [x] 2016-07-08 发布第19篇: 交易\\n- [x] 2016-07-02 发布第18篇: 关于时间戳及相关问题（优化补充）\\n- [x] 2016-06-27 发布第17篇: 签名和多重签名\\n- [x] 2016-06-23 发布第16篇: 地址\\n- [x] 2016-06-06 发布第15篇: 共识机制，可编程的利益转移规则\\n- [x] 2016-05-29 发布第14篇: 利益，魔鬼与天使的共同目标\\n- [x] 2016-05-23 完成第13篇: 加密货币就是货币\\n- [x] 2016-04-28 `书链`更名为`亿书`，撰写第13篇\\n- [x] 2016-04-17 发布第12篇：Ember深“坑”浅出\\n- [x] 2016-03-26 发布第11篇：一张图学会使用Async组件进行异步流程控制\\n- [x] 2016-03-17 发布第10篇\\n- [x] 2016-03-10 发布第9篇\\n- [x] 完成1-8篇\\n\\n## 使用（Usage)\\n\\n目录由命令行工具 [gitbook-summary](https://github.com/imfly/gitbook-summary) 自动生成。自由写作、发布，搭建自出版平台的方法，请[点击这里](https://github.com/imfly/how-to-create-self-publishing-platform)\\n\\n简要介绍如下：\\n\\n(1)克隆源文\\n\\n```\\n$ git clone https://github.com/imfly/bitcoin-on-nodejs.git\\n```\\n\\n(2)安装gitbook\\n\\n```\\n$ npm install -g gitbook-cli\\n```\\n\\n(3)安装依赖包\\n\\n```\\ncd bitcoin-on-nodejs\\nnpm install\\ngitbook install\\n```\\n\\n(4)写作构建\\n\\n写作，并开启服务（构建）\\n\\n```\\n$ gitbook serve\\n```\\n\\n通过`http://localhost:4000`实时浏览\\n\\n(5)生成目录\\n\\n只要修改了文章标题和文件夹，就应该重新生成目录文件\\n\\n```\\n$ npm run summary\\n```\\n\\n(6)一键发布\\n\\n```\\n$ npm run deploy\\n```\\n\\n以后，只要4-6的过程就是了。\\n\\n## 反馈（Feedback）\\n\\n随时告诉我您的阅读体验和问题，也可以直接fork修改，提交PR。\\n\\n## 贡献者（Contributors）\\n\\n@imfly @Tailor @火鼎 @珍惜 @一 @Mojie @cyio @zbinlin\\n\\n## 协议\\n\\n原创作品许可 [署名-非商业性使用-禁止演绎 3.0 未本地化版本 (CC BY-NC-ND 3.0)](http://creativecommons.org/licenses/by-nc-nd/3.0/deed.zh)'},\n",
       " {'repo': 'rust-bitcoin/rust-bitcoin',\n",
       "  'language': 'Rust',\n",
       "  'readme_contents': '<div align=\"center\">\\n  <h1>Rust Bitcoin</h1>\\n\\n  <img alt=\"Rust Bitcoin logo by Hunter Trujillo, see license and source files under /logo\" src=\"./logo/rust-bitcoin.png\" width=\"300\" />\\n\\n  <p>Library with support for de/serialization, parsing and executing on data-structures\\n    and network messages related to Bitcoin.\\n  </p>\\n\\n  <p>\\n    <a href=\"https://crates.io/crates/bitcoin\"><img alt=\"Crate Info\" src=\"https://img.shields.io/crates/v/bitcoin.svg\"/></a>\\n    <a href=\"https://github.com/rust-bitcoin/rust-bitcoin/blob/master/LICENSE\"><img alt=\"CC0 1.0 Universal Licensed\" src=\"https://img.shields.io/badge/license-CC0--1.0-blue.svg\"/></a>\\n    <a href=\"https://github.com/rust-bitcoin/rust-bitcoin/actions?query=workflow%3AContinuous%20integration\"><img alt=\"CI Status\" src=\"https://github.com/rust-bitcoin/rust-bitcoin/workflows/Continuous%20integration/badge.svg\"></a>\\n    <a href=\"https://docs.rs/bitcoin\"><img alt=\"API Docs\" src=\"https://img.shields.io/badge/docs.rs-bitcoin-green\"/></a>\\n    <a href=\"https://blog.rust-lang.org/2020/02/27/Rust-1.41.1.html\"><img alt=\"Rustc Version 1.41.1+\" src=\"https://img.shields.io/badge/rustc-1.41.1%2B-lightgrey.svg\"/></a>\\n    <a href=\"https://gnusha.org/bitcoin-rust/\"><img alt=\"Chat on IRC\" src=\"https://img.shields.io/badge/irc-%23bitcoin--rust%20on%20libera.chat-blue\"></a>\\n    <a href=\"https://github.com/model-checking/kani\"><imp alt=\"kani\" src=\"https://github.com/rust-bitcoin/rust-bitcoin/actions/workflows/kani.yaml/badge.svg\"></a>\\n    <img alt=\"Lines of code\" src=\"https://img.shields.io/tokei/lines/github/rust-bitcoin/rust-bitcoin\">\\n  </p>\\n</div>\\n\\n[Documentation](https://docs.rs/bitcoin/)\\n\\nSupports (or should support)\\n\\n* De/serialization of Bitcoin protocol network messages\\n* De/serialization of blocks and transactions\\n* Script de/serialization\\n* Private keys and address creation, de/serialization and validation (including full BIP32 support)\\n* PSBT v0 de/serialization and all but the Input Finalizer role. Use [rust-miniscript](https://docs.rs/miniscript/latest/miniscript/psbt/index.html) to finalize.\\n\\nFor JSONRPC interaction with Bitcoin Core, it is recommended to use\\n[rust-bitcoincore-rpc](https://github.com/rust-bitcoin/rust-bitcoincore-rpc).\\n\\nIt is recommended to always use [cargo-crev](https://github.com/crev-dev/cargo-crev)\\nto verify the trustworthiness of each of your dependencies, including this one.\\n\\n## Known limitations\\n\\n### Consensus\\n\\nThis library **must not** be used for consensus code (i.e. fully validating\\nblockchain data). It technically supports doing this, but doing so is very\\nill-advised because there are many deviations, known and unknown, between\\nthis library and the Bitcoin Core reference implementation. In a consensus\\nbased cryptocurrency such as Bitcoin it is critical that all parties are\\nusing the same rules to validate data, and this library is simply unable\\nto implement the same rules as Core.\\n\\nGiven the complexity of both C++ and Rust, it is unlikely that this will\\never be fixed, and there are no plans to do so. Of course, patches to\\nfix specific consensus incompatibilities are welcome.\\n\\n### Support for 16-bit pointer sizes\\n\\n16-bit pointer sizes are not supported and we can\\'t promise they will be.\\nIf you care about them please let us know, so we can know how large the interest\\nis and possibly decide to support them.\\n\\n## Documentation\\n\\nCurrently can be found on [docs.rs/bitcoin](https://docs.rs/bitcoin/).\\nPatches to add usage examples and to expand on existing docs would be extremely\\nappreciated.\\n\\n## Contributing\\n\\nContributions are generally welcome. If you intend to make larger changes please\\ndiscuss them in an issue before PRing them to avoid duplicate work and\\narchitectural mismatches. If you have any questions or ideas you want to discuss\\nplease join us in\\n[#bitcoin-rust](https://web.libera.chat/?channel=#bitcoin-rust) on\\n[libera.chat](https://libera.chat).\\n\\nFor more information please see `./CONTRIBUTING.md`.\\n\\n## Minimum Supported Rust Version (MSRV)\\n\\nThis library should always compile with any combination of features (minus\\n`no-std`) on **Rust 1.41.1** or **Rust 1.47** with `no-std`.\\n\\nTo build with the MSRV you will need to pin some dependencies, currently this is\\nonly `syn`, and can be achieved using `cargo update -p syn --precise 1.0.107`.\\n\\n## Installing Rust\\n\\nRust can be installed using your package manager of choice or\\n[rustup.rs](https://rustup.rs). The former way is considered more secure since\\nit typically doesn\\'t involve trust in the CA system. But you should be aware\\nthat the version of Rust shipped by your distribution might be out of date.\\nGenerally this isn\\'t a problem for `rust-bitcoin` since we support much older\\nversions than the current stable one (see MSRV section).\\n\\n## Building\\n\\nThe library can be built and tested using [`cargo`](https://github.com/rust-lang/cargo/):\\n\\n```\\ngit clone git@github.com:rust-bitcoin/rust-bitcoin.git\\ncd rust-bitcoin\\ncargo build\\n```\\n\\nYou can run tests with:\\n\\n```\\ncargo test\\n```\\n\\nPlease refer to the [`cargo` documentation](https://doc.rust-lang.org/stable/cargo/) for more detailed instructions.\\n\\n### Building the docs\\n\\nWe build docs with the nightly toolchain, you may wish to use the following\\nshell alias to check your documentation changes build correctly.\\n\\n```\\nalias build-docs=\\'RUSTDOCFLAGS=\"--cfg docsrs\" cargo +nightly rustdoc --features=\"$FEATURES\" -- -D rustdoc::broken-intra-doc-links\\'\\n```\\n\\n## Testing\\n\\nUnit and integration tests are available for those interested, along with benchmarks. For project\\ndevelopers, especially new contributors looking for something to work on, we do:\\n\\n- Fuzz testing with [`Hongfuzz`](https://github.com/rust-fuzz/honggfuzz-rs)\\n- Mutation testing with [`Mutagen`](https://github.com/llogiq/mutagen)\\n- Code verification with [`Kani`](https://github.com/model-checking/kani)\\n\\nThere are always more tests to write and more bugs to find, contributions to our testing efforts\\nextremely welcomed. Please consider testing code a first class citizen, we definitely do take PRs\\nimproving and cleaning up test code.\\n\\n### Unit/Integration tests\\n\\nRun as for any other Rust project `cargo test --all-features`.\\n\\n### Benchmarks\\n\\nWe use a custom Rust compiler configuration conditional to guard the bench mark code. To run the\\nbench marks use: `RUSTFLAGS=\\'--cfg=bench\\' cargo +nightly bench`.\\n\\n### Mutation tests\\n\\nWe have started doing mutation testing with [mutagen](https://github.com/llogiq/mutagen). To run\\nthese tests first install the latest dev version with `cargo +nightly install --git https://github.com/llogiq/mutagen`\\nthen run with `RUSTFLAGS=\\'--cfg=mutate\\' cargo +nightly mutagen`.\\n\\n### Code verification\\n\\nWe have started using [kani](https://github.com/model-checking/kani), install with `cargo install\\n--locked kani-verifier` (no need to run `cargo kani setup`). Run the tests with `cargo kani`.\\n\\n## Pull Requests\\n\\nEvery PR needs at least two reviews to get merged. During the review phase\\nmaintainers and contributors are likely to leave comments and request changes.\\nPlease try to address them, otherwise your PR might get closed without merging\\nafter a longer time of inactivity. If your PR isn\\'t ready for review yet please\\nmark it by prefixing the title with `WIP: `.\\n\\n### CI Pipeline\\n\\nThe CI pipeline requires approval before being run on each MR.\\n\\nIn order to speed up the review process the CI pipeline can be run locally using\\n[act](https://github.com/nektos/act). The `fuzz` and `Cross` jobs will be\\nskipped when using `act` due to caching being unsupported at this time. We do\\nnot *actively* support `act` but will merge PRs fixing `act` issues.\\n\\n### Githooks\\n\\nTo assist devs in catching errors _before_ running CI we provide some githooks. If you do not\\nalready have locally configured githooks you can use the ones in this repository by running, in the\\nroot directory of the repository:\\n```\\ngit config --local core.hooksPath githooks/\\n```\\n\\nAlternatively add symlinks in your `.git/hooks` directory to any of the githooks we provide.\\n\\n## Policy on Altcoins/Altchains\\n\\nPatches which add support for non-Bitcoin cryptocurrencies by adding constants\\nto existing enums (e.g. to set the network message magic-byte sequence) are\\nwelcome. Anything more involved will be considered on a case-by-case basis,\\nas the altcoin landscape includes projects which [frequently appear and\\ndisappear, and are poorly designed anyway](https://download.wpsoftware.net/bitcoin/alts.pdf)\\nand keeping the codebase maintainable is a large priority.\\n\\nIn general, things that improve cross-chain compatibility (e.g. support for\\ncross-chain atomic swaps) are more likely to be accepted than things which\\nsupport only a single blockchain.\\n\\n\\n## Release Notes\\n\\nSee [CHANGELOG.md](CHANGELOG.md).\\n\\n\\n## Licensing\\n\\nThe code in this project is licensed under the [Creative Commons CC0 1.0\\nUniversal license](LICENSE). We use the [SPDX license list](https://spdx.org/licenses/) and [SPDX\\nIDs](https://spdx.dev/ids/).\\n'},\n",
       " {'repo': 'michaelliao/cryptocurrency',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# cryptocurrency\\n\\n'},\n",
       " {'repo': 'btcpayserver/btcpayserver',\n",
       "  'language': 'C#',\n",
       "  'readme_contents': '# BTCPay Server\\n\\n![BTCPay Server](BTCPayServer/wwwroot/img/btc_pay_BG_twitter.png)\\n\\n<h3 align=\"center\">\\n  Accept Bitcoin payments ₿\\n</h3>\\n<p align=\"center\"> BTCPay Server is a free and open-source Bitcoin payment processor which allows you to accept bitcoin without fees or intermediaries.\\n</p>\\n<p align=\"center\">\\n  <a href=\"https://circleci.com/gh/btcpayserver/btcpayserver\">\\n    <img src=\"https://img.shields.io/circleci/build/github/btcpayserver/btcpayserver\"/>\\n  </a>\\n  <a href=\"https://github.com/btcpayserver/btcpayserver/releases/\">\\n    <img src=\"https://img.shields.io/github/v/release/btcpayserver/btcpayserver\"/>\\n  </a>\\n  <a href=\"https://github.com/btcpayserver/btcpayserver/blob/master/LICENSE\">\\n      <img src=\"https://img.shields.io/github/license/btcpayserver/btcpayserver\"/>\\n  </a>\\n  <a href=\"https://docs.btcpayserver.org/Contribute/\">\\n    <img src=\"https://img.shields.io/badge/PRs-welcome-brightgreen.svg\"/>\\n  </a>\\n  <a href=\"https://chat.btcpayserver.org/\">\\n    <img src=\"https://img.shields.io/badge/Community%20Chat-Mattermost-%230058cc\"/>\\n  </a>\\n  <a href=\"https://twitter.com/intent/follow?screen_name=btcpayserver\">\\n    <img src=\"https://img.shields.io/twitter/follow/btcpayserver.svg?label=Follow%20@btcpayserver\"/>\\n  </a>\\n</p>\\n\\n<div align=\"center\">\\n  <h3>\\n    <a href=\"https://btcpayserver.org\">\\n      Website\\n    </a>\\n    <span> | </span>\\n    <a href=\"https://docs.btcpayserver.org\">\\n      Documentation\\n    </a>\\n    <span> | </span>\\n    <a href=\"https://docs.btcpayserver.org/API/Greenfield/v1/\">\\n      API\\n    </a>\\n    <span> | </span>\\n    <a href=\"https://docs.btcpayserver.org/Contribute/\">\\n      Contribute\\n    </a>\\n    <span> | </span>\\n    <a href=\"https://www.youtube.com/btcpayserver/\">\\n      YouTube\\n    </a>\\n    <span> | </span>\\n    <a href=\"https://chat.btcpayserver.org/\">\\n      Chat\\n    </a>\\n  </h3>\\n</div>\\n\\n<div align=\"center\">\\n  <sub>\"This is lies, my trust in you is broken, I will make you obsolete\" 💚\\n  </a>\\n</div>\\n<br/>\\n\\n<p align=\"center\">\\n  <a href=\"https://mainnet.demo.btcpayserver.org\">View Demo</a>\\n  ·\\n  <a href=\"https://github.com/btcpayserver/btcpayserver/issues/new/choose\">Report a bug</a>\\n  ·\\n  <a href=\"https://github.com/btcpayserver/btcpayserver/discussions/new\">Request a feature</a>\\n  ·\\n  <a href=\"https://docs.btcpayserver.org/FAQ/\">FAQ</a>\\n</p>\\n\\n## 💼 Table of Contents\\n\\n* [Features](#-features)\\n* [Getting Started](#-getting-started)\\n* [Documentation](#-documentation)\\n* [Contributing](#-contributing)\\n* [Developing](#-developing)\\n  * [API](#-api)\\n* [Community](#-community)\\n* [License](#-license)\\n* [Supporters](#-supporters)\\n\\n![](https://raw.githubusercontent.com/btcpayserver/btcpayserver-doc/master/docs/img/BTCPayServerScreenshot.png)\\n\\n## 🎨 Features\\n\\n* Direct, peer-to-peer Bitcoin payments\\n* No transaction fees (other than the [network fee](https://en.bitcoin.it/wiki/Miner_fees))\\n* No fees, middleman or KYC\\n* Non-custodial (complete control over the private key)\\n* Enhanced privacy & security\\n* Self-hosted\\n* SegWit support\\n* Lightning Network support (LND, c-lightning, Eclair, and Ptarmigan)\\n* Tor support\\n* Share your instance with friends (multi-tenant)\\n* Invoice management and Payment requests\\n* Apps: Point of sale, crowdfunding, donation button\\n* Full-node reliant wallet with [hardware wallet integration](https://docs.btcpayserver.org/Vault/) and SegWit support\\n* Bitcoin-only build, separate community-maintained altcoin build ([supported altcoins](https://docs.btcpayserver.org/FAQ/FAQ-Altcoin/))\\n\\n## 🚀 Getting Started\\n\\nFirstly, decide if you want to host an instance yourself or use a [third-party host](https://docs.btcpayserver.org/ThirdPartyHosting/). If you\\'ve chosen to self-host, there are plenty of documented [ways to deploy BTCPay Server](https://docs.btcpayserver.org/Deployment/).\\n\\nAfter successful deployment, make sure to check our [getting started](https://docs.btcpayserver.org/RegisterAccount/) and [walkthrough](https://docs.btcpayserver.org/Walkthrough/) guides. In case you would like to use Lightning Network, see [Lightning guide](https://docs.btcpayserver.org/LightningNetwork/).\\n\\n## 📗 Documentation\\n\\nPlease check out our [official website](https://btcpayserver.org/), [complete documentation](https://docs.btcpayserver.org/) and [FAQ](https://docs.btcpayserver.org/FAQ/) for more details.\\n\\nIf you have trouble using BTCPay Server, consider joining [communities listed on the official website](https://btcpayserver.org/#communityCTA) to get help from other contributors. Only create a [GitHub issue](https://github.com/btcpayserver/btcpayserver/issues/new/choose) for technical issues you can\\'t resolve through other channels or feature requests you\\'ve validated with other members of the community.\\n\\n## 🤝 Contributing\\n\\nBTCPay Server is built and maintained entirely by volunteer contributors around the internet. We welcome and appreciate new contributions.\\n\\nIf you\\'re a developer looking to help, but you\\'re not sure where to begin, check the [good first issue label](https://github.com/btcpayserver/btcpayserver/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22), which contains small pieces of work that have been specifically flagged as being friendly to new contributors.\\n\\nContributors looking to do something a bit more challenging, before opening a pull request, please join [our community chat](https://chat.btcpayserver.org/) or [start a GitHub discussion](https://github.com/btcpayserver/btcpayserver/discussions) to get early feedback, discuss the best ways to tackle the problem, and ensure there is no work duplication.\\n\\nThere are many other ways to get involved with the project. Check our [contribution guidelines](https://docs.btcpayserver.org/Contribute/). To get the big-picture of the project development, visit our [evolving roadmap](https://github.com/orgs/btcpayserver/projects/9). We organize different types of community calls several times a month. [Subscribe to our calendar](https://github.com/btcpayserver/organization#calendar) and feel free to join our calls to discuss development, design, documentation, and more.\\n\\n## 🧑\\u200d💻 Developing\\n\\nTo begin developing locally, visit our [local development guide](https://docs.btcpayserver.org/Development/LocalDevelopment/). There are also several video-tutorials:\\n\\n* [Setting up development environment on Windows](https://www.youtube.com/watch?v=ZePbMPSIvHM)\\n* [Setting up development environment Linux (Ubuntu)](https://www.youtube.com/watch?v=j486T_Rk-yw&t)\\n* [Setting up development environment MacOS](https://www.youtube.com/watch?v=GWR_CcMsEV0)\\n\\n### How to build\\n\\nWhile the documentation advises using docker-compose, you may want to build BTCPay Server yourself.\\n\\nFirst, install .NET Core SDK v6.0 as specified by the [Microsoft website](https://dotnet.microsoft.com/download/dotnet-core/6.0).\\n\\nOn Powershell:\\n\\n```powershell\\n.\\\\build.ps1\\n```\\n\\nOn linux:\\n\\n```sh\\n./build.sh\\n```\\n\\n### How to run\\n\\nUse the `run` scripts to run BTCPay Server, this example shows how to print the available command-line arguments of BTCPay Server.\\n\\nOn Powershell:\\n\\n```powershell\\n.\\\\run.ps1 --help\\n```\\n\\nOn linux:\\n\\n```sh\\n./run.sh --help\\n```\\n\\n### How to debug\\n\\nIf you want to debug, use Jetbrain\\'s Rider or Visual Studio 2022.\\n\\nYou need to run the development time docker-compose as described [in the test guide](./BTCPayServer.Tests/README.md).\\n\\nYou can then run the debugger by using the Launch Profile `Docker-Regtest`.\\n\\nIf you need to debug ledger wallet interaction, install the development time certificate with:\\n\\n```bash\\n# Install development time certificate in the trust store\\ndotnet dev-certs https --trust\\n```\\n\\nThen use the `Docker-Regtest-https` debug profile.\\n\\n### Other dependencies\\n\\nFor more information, see the documentation:\\n[How to deploy a BTCPay Server instance](https://docs.btcpayserver.org/Deployment/).\\n\\n### 🧪 API\\n\\nBTCPay Server has two APIs:\\n\\n- **Greenfield API (New)**\\n  - [Greenfield API documentation](https://docs.btcpayserver.org/API/Greenfield/v1/)\\n  - [Greenfield API examples with CURL](https://docs.btcpayserver.org/GreenFieldExample/)\\n- **Legacy API**\\n\\nThe **Greenfield API** is our brand-new API which is still in development. Once complete, it will allow you to run BTCPay Server headlessly.\\nThe **Legacy API**, is fully compatible with [BitPay\\'s API](https://bitpay.com/api/). It has limited features, but allows instant migration from BitPay.\\n\\n## 💚 Community\\n\\nOur community is the ❤️ of the project. To chat with other community members in real-time, join our [Mattermost chat](https://chat.btcpayserver.org). We\\'re also on [GitHub discussions](https://github.com/btcpayserver/btcpayserver/discussions).\\n\\n## 📝 License\\n\\nBTCPay Server software, logo and designs are provided under [MIT License](https://github.com/btcpayserver/btcpayserver/blob/master/LICENSE).\\n\\n## 🙏 Supporters\\n\\nThe BTCPay Server Project is proudly supported by these entities through the [BTCPay Server Foundation](https://foundation.btcpayserver.org/).\\n\\n[![Spiral](BTCPayServer/wwwroot/img/readme/supporter_spiral.svg)](https://spiral.xyz)\\n[![Baillie Gifford](BTCPayServer/wwwroot/img/readme/supporter_bailliegifford.svg)](https://www.bailliegifford.com)\\n[![Strike](BTCPayServer/wwwroot/img/readme/supporter_strike.svg)](https://strike.me)\\n[![Human Rights Foundation](BTCPayServer/wwwroot/img/readme/supporter_hrf.svg)](https://hrf.org)\\n[![LunaNode](BTCPayServer/wwwroot/img/readme/supporter_lunanode.svg)](https://lunanode.com)\\n[![Wallet of Satoshi](BTCPayServer/wwwroot/img/readme/supporter_walletofsatoshi.svg)](https://walletofsatoshi.com/)\\n[![Coincards](BTCPayServer/wwwroot/img/readme/supporter_coincards.svg)](https://coincards.com/)\\n[![IVPN](BTCPayServer/wwwroot/img/readme/supporter_ivpn.svg)](https://ivpn.net/)\\n\\nIf you\\'d like to support the project, please visit the [donation page](https://btcpayserver.org/donate/).\\n'},\n",
       " {'repo': 'trottier/original-bitcoin',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': \"original-bitcoin\\n================\\n\\nThis is a historical repository of Satoshi Nakamoto's original bitcoin sourcecode\"},\n",
       " {'repo': 'PiSimo/BitcoinForecast',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '# BitcoinForecast \\n\\nPredict bitcoin value for the next 9minutes, with Recurrental Neural Network GRU.\\n<br />\\n<h1>Requirements:</h1>\\n<br/>\\n\\n<ul>\\n<li>Python3</li>\\n<li><a href=\"http://keras.io/\">Keras 2</a></li>\\n<li><a href=\"http://www.numpy.org/\">numpy</a></li>\\n<li><a href=\"http://matplotlib.org/\">MatploitLib</a></li>\\n</ul>\\n<br />\\n<h1> Data </h1>\\nYou can download data through the <code>grabber.py</code> \\n<br/>\\n<h1>Model:</h1>\\n<div style=\"margin-left:auto;margin-right:auto;\"><img width=550 height=800 src=\"https://cloud.githubusercontent.com/assets/17238972/25303841/4945f448-275b-11e7-8ad9-e4c9601a7d3a.png\"></div>\\n<p>Generated with <a href=\"https://pisimo.github.io/DeepChart/\">deepchart</a></p>\\n<h1>Instructions</h1>\\n<p>Clone the repo:</p>\\n<code>\\ngit clone https://github.com/PiSimo/BitcoinForecast.git\\n</code>\\n<br />\\n<br />\\n<b>Training on new data:</b><br />\\n<code>python3 network.py -train <i>dataset_path</i> -iterations <i>number_of_training_iterations</i></code>\\n<p>To finetune the new model with an old one just add <code>-finetune <i>base_model_path</i></code> to the line above.</p>\\n<p>At the end of the training you will have an updated model.h5 with the new weights and you will see a plot with the test results.</p>\\n<br />\\n<b>Running:</b><br />\\n<code>python3 network.py -run <i>dataset_path</i> -model <i>model_path</i></code>\\n<p>The dataset is also required when you run, to perform normalization.</p>\\n<p>To visualize a plot with the real and predicted results enter Crtl-C and type no ,the program will create chart.png with the results.</p>\\n\\n<br/>\\nWorking example with <a href=\"https://github.com/PiSimo/BitcoinForecast/blob/master/model.h5\">this model</a>:\\n<br/>\\n(Red:Predicted,Green:Real values)\\n<img src=\"https://cloud.githubusercontent.com/assets/17238972/24326997/630cf3c2-11bc-11e7-8edb-07be895e16ea.png\" />\\n\\n'},\n",
       " {'repo': 'Bit-Wasp/bitcoin-php',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': '  \\n## Bitcoin\\n\\n[![Build Status](https://scrutinizer-ci.com/g/bit-wasp/bitcoin-php/badges/build.png?b=master)](https://scrutinizer-ci.com/g/bit-wasp/bitcoin-php/build-status/master)\\n[![Code Coverage](https://scrutinizer-ci.com/g/bit-wasp/bitcoin-php/badges/coverage.png?b=master)](https://scrutinizer-ci.com/g/bit-wasp/bitcoin-php/?branch=master)\\n[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/Bit-Wasp/bitcoin-php/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/Bit-Wasp/bitcoin-php/?branch=master)\\n[![Latest Stable Version](https://poser.pugx.org/bitwasp/bitcoin/v/stable.png)](https://packagist.org/packages/bitwasp/bitcoin)\\n\\nThis repository contains an implementation of Bitcoin using mostly pure PHP.\\n\\n*Warning*: This library does not support 32-bit installs of PHP. Please also note that composer is the only supported installation method.\\n\\n## Installation\\n\\nYou can install this library via Composer: `composer require bitwasp/bitcoin`\\n\\n## Contributing\\n\\nAll contributions are welcome. Please see [[this page](https://github.com/Bit-Wasp/bitcoin-php/blob/master/CONTRIBUTING.md)] before you get started\\n\\n## Documentation\\n\\n Check out the beginnings of the documentation for the library: [[Introduction](doc/documentation/Introduction.md)]\\n\\n## Presently supported:\\n\\n - Blocks, headers, and merkle blocks and bloom filters\\n - P2SH & Segregated witness scripts\\n - An adaptable elliptic-curve library, using [[PhpEcc](https://github.com/mdanter/phpecc)] by default, or libsecp256k1 if the bindings are found\\n - Support for building, parsing, signing/validating transactions\\n - Deterministic signatures (RFC6979)\\n - BIP32 and electrum (older type I) deterministic key algorithms\\n - BIP39, and the older electrum seed format.\\n - ScriptFactory for common input/output types, parser, interpreter, and classifiers\\n - Supports bindings to libbitcoinconsensus\\n - Bindings to Stratum (electrum) servers\\n\\n# Other projects\\n\\n - [buffertools-php](https://github.com/Bit-Wasp/buffertools-php) - Toolkit for working with binary data in PHP\\n - [ext-secp256k1](https://github.com/Bit-Wasp/secp256k1-php) - PHP bindings to libsecp256k1\\n - [ext-bitcoinconsensus](https://github.com/Bit-Wasp/bitcoinconsensus-php) - PHP bindings to libbitcoinconsensus\\n - [bitcoin-p2p-php](https://github.com/Bit-Wasp/bitcoin-p2p-php) - PHP implementation of bitcoin P2P messaging using reactphp\\n - [stratum-php](https://github.com/Bit-Wasp/stratum-php) - PHP implementation of the stratum protocol using reactphp\\n - [electrum-discovery-php](https://github.com/Bit-Wasp/electrum-discovery-php) - Electrum server discovery (over IRC) using reactphp\\n - [node-php](https://github.com/Bit-Wasp/node-php) - A toy project (really just for fun) a full node using bitcoin-p2p-php\\n - [bip70-php](https://github.com/bip70/bip70-php) - A BIP70 (payment requests) implementation for PHP\\n\\n## Supporters\\n\\nThis library is a 100% open source project. We do not receive any funding from the industry, nor provide paid support or development of features. That said, we are grateful for our supporters who provide free access for open source projects:\\n\\n[![JetBrains](https://avatars0.githubusercontent.com/u/878437?s=200&v=4)](https://www.jetbrains.com/)\\n\\nThanks to [JetBrains](https://www.jetbrains.com/) for supporting the project through sponsoring some [All Products Packs](https://www.jetbrains.com/products.html) within their [Free Open Source License](https://www.jetbrains.com/buy/opensource/) program.\\n'},\n",
       " {'repo': 'bitcoin-core/bitcoincore.org',\n",
       "  'language': 'HTML',\n",
       "  'readme_contents': '# [bitcoincore.org](https://bitcoincore.org)\\n\\nThis repository is the source code of the Bitcoin Core project website built with Jekyll.\\n\\n## Directory structure\\n\\n  - `_posts/<lang>/posts` for blog articles.\\n  - `_posts/<lang>/pages` for static pages.\\n  - `_posts/<lang>/releases` for Bitcoin Core release notes\\n\\nFile names *must* be in the format `Y-m-d-title.md`, e.g. `2015-12-31-title.md`. File names can be translated.\\n\\n## Translations\\n\\nSee [CONTRIBUTING.md](/CONTRIBUTING.md#translation-process) for more information.\\n\\n## Front Matter notes\\n\\nThe following `Front Matter` is required for the multilingual setup in all files. The required fields are as follows:\\n\\n  - `name:`      group name for unique article. Each translation must share the same group name, e.g. `october15-report`\\n  - `id:`        each article translation must have a unique ID. Use the language code + `-name` field. e.g. `en-october15-report`\\n  - `permalink:` the must include the language code, end a trailing slash, e.g. `/en/2015/12/31/report/`.\\n  - `title:`     the translated title of the article\\n  - `type:`      the content type (`pages`, `posts`, `releases`, `meetings`, etc.)\\n  - `layout:`    the layout template (`page`, `post`, etc.)\\n  - `lang:`      the language code (`en`, `fr`, etc.)\\n\\n```\\n---\\ntitle: Short Title\\nname: short-title\\nlayout: post\\ntype: posts\\nlang: en\\nid: en-short-title\\npermalink: /en/2016/01/01/short-title\\n---\\n```\\n\\n## Building\\n\\nThis website is based on [Jekyll](https://jekyllrb.com/).  To build\\nlocally, [install Ruby 2.5.5](https://gorails.com/setup) using system\\npackages, [rvm](https://rvm.io), [rbenv](https://github.com/rbenv/rbenv), or another method.\\nThen clone this repository and change directory into it:\\n\\n    git clone https://github.com/bitcoin-core/bitcoincore.org.git\\n    cd bitcoincore.org\\n\\nInstall the `bundle` utility using the Ruby package manager, `gem`, and\\nthen use `bundle` to install the rest of the Ruby packages needed to\\nbuild this site.  Note, depending on your system configuration, you may\\nneed to run `gem` as the superuser by putting \"sudo\" followed by a space\\nbefore the `gem` command.  You shouldn\\'t need to use `sudo` with the\\n`bundle` command.\\n\\n    gem update --system\\n    gem install bundler\\n    bundle install\\n\\nTo preview the site (this will launch a tiny webserver on port 4000):\\n\\n    bundle exec jekyll server --future\\n\\nTo simply build the site (output placed in the `_site` directory):\\n\\n    bundle exec jekyll build --future\\n\\nNote that the `--future` parameter is only required if you\\'re adding any\\npages dated in the future (such as prepared release announcements).\\n\\nTo test the site:\\n\\n    bundle exec jekyll build --future --drafts --unpublished\\n    bundle exec htmlproofer --check-html --disable-external --url-ignore \\'/^\\\\/bin/.*/\\' ./_site\\n\\nThe additional parameters to `jekyll build` ensure that all possible\\npages are built and checked.\\n\\n## Contributing\\n\\nContributions welcome. Please see [CONTRIBUTING.md](/CONTRIBUTING.md) for details.\\n\\n## References\\n\\nThe website uses an old version of the [Minimal Mistakes theme][].  The\\ntheme\\'s website provides [documentation][mm docs], including information\\nabout [configuration variables][mm config], creating [pages and posts][mm\\ncontent], adding [new Javascript][mm js], and more.  Note that\\ncurrent documentation may describe features not available in the old\\nversion of the theme used by the website.\\n\\n[minimal mistakes theme]: https://mmistakes.github.io/minimal-mistakes/\\n[mm docs]: https://mmistakes.github.io/minimal-mistakes/docs/quick-start-guide/\\n[mm config]: https://mmistakes.github.io/minimal-mistakes/docs/configuration/\\n[mm content]: https://mmistakes.github.io/minimal-mistakes/docs/posts/\\n[mm js]: https://mmistakes.github.io/minimal-mistakes/docs/javascript/\\n'},\n",
       " {'repo': 'tianmingyun/MasterBitcoin2CN',\n",
       "  'language': None,\n",
       "  'readme_contents': \"郎咸平说过：比特币白给我都不要\\n\\n巴菲特：比特币是泡沫，不是一种能够生产价值的资产\\n\\n紫色的股：为什么说比特币是典型的泡沫\\n\\n......\\n\\n也有人说，区块链是最伟大的发明，堪比互联网。\\n\\n到底比特币是什么？如何判断？难道我们能做的就是人云亦云？\\n\\n如何能有自己的独立判断？\\n\\n每个人都有自己的“全知遮蔽”，就像每个人都看不见自己的后脑勺一样。在自己的视野内，在自己的舒适区，如鱼得水，但是就是这种感觉最容易让自己以为“自己以为的”就是客观事实。\\n\\n正确的态度是研究搞懂，之后才有资格做判断。\\n\\n这本书就能帮助您全面了解比特币，而且有助于理解其他数字货币。\\n\\n本书翻译过程中得到了higer（区块链研习社社长）的支持和鼓励，特此致谢。\\n\\n本书部分段落内容参考摘录了《精通比特币》知笔墨版本，在此特别声明并致谢。\\n\\n本书附录A比特币白皮书，其中附录A-1全文引自[【巴比特】](https://www.8btc.com/wiki/bitcoin-a-peer-to-peer-electronic-cash-system) ，附录A-2全文引自[【李笑来英中文对照版】](http://lixiaolai.com/#/bitcoin-whitepaper-cn-en-translation/Bitcoin-Whitepaper-EN-CN.html)。在此特别声明并致谢。\\n\\n以下朋友对本书做出巨大贡献：\\n\\n菜菜子：翻译了英文版序言，第二版更新说明，词汇表，附录2交易脚本语言操作符，常量和符号等章节\\n\\n柴春燕和格林怪物：联合翻译附录隔离见证部分\\n\\nRobbie_英语翻译：第4章审核校对\\n\\n吴迪：第5章，第9章审核校对\\n\\n格林怪物：第6章审核校对\\n\\n阿龙：第7章，第11章审核校对\\n\\n阮立志和冯锦炜：第10章审核校对\\n\\n琳：第12章审核校对\\n\\n黄豆：封面封底扉页以及其他内容设计\\n\\n特别感谢赵斌锋，在本书最后出版前校对过程中付出了巨大的努力，修正了一些瑕疵。\\n\\n由于时间原因和个人水平能力原因，初稿中有许多格式和理解翻译错误。以上各位朋友在审核校过程中修正了初稿中许多错误，甚至部分章节兼职了翻译工作，在此表示致歉和感谢。\\n\\n即便如此，当前版本还可能存在部分错误，欢迎读者在github上提交勘误，也可以发至邮箱：yuntianming@aliyun.com\\n\\n乔延宏 2017.11.11\\n\\n*** 正版书购买链接***\\n\\n本书经过多方努力，历时一年，终于付梓，欢迎购买正版图书。京东购买链接：\\n\\nhttps://item.jd.com/12620946.html\\n\\n*** 2019年下半年校对说明 ***\\n\\n2019年10月开始到2019年12月底，对github上的第二版进行了一次全面的校对，更新了下面的内容：\\n\\n1、格式方面：增加章节名称。所有“提示”，“警告”，“注意”等全部改为引用。引用章节增加链接和中文括号。\\n\\n2、图片：图片未做翻译，链接全部改用英文版链接。\\n\\n3、与英文版内容同步更新至2019年9月。修正部分章节的明确错误，翻译不准确，表达琐碎之处。增加了可执行文件的源代码。\\n\\n4、增加比特币白皮书的李笑来翻译版本，附其他版本链接。\\n\\n乔延宏   2019.12.22\\n\\n*** 2020年上半年校对说明 ***\\n\\n2020年7月跟随原版进行了更新。主要内容有：\\n\\n1、删除失效链接；\\n\\n2、增加2020年5月减半相关内容；\\n\\n3、删除染色币（Colored Coin）相关内容;\\n\\n4、更新附录部分内容；\\n\\n5、更新目录。\\n\\n乔延宏  2020.7.30\\n\\n\\n\\n鸣谢:\\n\\n区块链研习社\\n\\n[![云天明区块链数据导航](http://ytm.ltd/zb_users/upload/ytm.ltd.png)](http://ytm.ltd)\\n\\n\\n\\n\\n## Mastering Bitcoin - Second Edition 版权说明\\n\\nThe tags, [second_edition_print_1](https://github.com/bitcoinbook/bitcoinbook/releases/tag/second_edition_print_1) and [second_edition_print2](https://github.com/bitcoinbook/bitcoinbook/releases/tag/second_edition_print2), correspond to the first (June 8th, 2017) and second (July 20th, 2017) print of Mastering Bitcoin (Second Edition), as published by O'Reilly Media.\\n\\n[![Creative Commons License](../../qukuailian/%E7%B2%BE%E9%80%9A%E6%96%B0%E7%BF%BB%E8%AF%91/images/68747470733a2f2f692e6372656174697665636f6d6d6f6e732e6f72672f6c2f62792d73612f342e302f38387833312e706e67.png)](http://creativecommons.org/licenses/by-sa/4.0/)\\n\\nMastering Bitcoin - Second Edition by [Andreas M. Antonopoulos LLC](https://antonopoulos.com/) is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0/).\\n\\n\"},\n",
       " {'repo': 'lian/bitcoin-ruby',\n",
       "  'language': 'Ruby',\n",
       "  'readme_contents': '= Bitcoin-ruby {<img src=\"https://api.travis-ci.org/lian/bitcoin-ruby.svg?branch=master\" />}[http://travis-ci.org/lian/bitcoin-ruby] {<img src=\"http://inch-ci.org/github/lian/bitcoin-ruby.svg?branch=master\" alt=\"Inline docs\" />}[http://inch-ci.org/github/lian/bitcoin-ruby] {<img src=\"https://tip4commit.com/projects/108.svg\" alt=\"tip for next commit\" />}[https://tip4commit.com/github/lian/bitcoin-ruby]\\n\\nThis is a ruby library for interacting with the bitcoin protocol/network.\\n\\nSome of the main features are:\\n\\n* Bitcoin::Key provides a high-level API for creating and handling keys/addresses\\n* Bitcoin::Util provides the basic bitcoin utility functions for base58, ECC, etc.\\n* Bitcoin::Protocol can parse/create all protocol messages\\n* Bitcoin::Script implementation, create/run scripts and verify signatures\\n* Bitcoin::Builder provides a high-level API for creating transactions (and blocks)\\n* Bitcoin::Litecoin implements all the litecoin-specific differences\\n\\n== Compatible with...\\n\\n* ruby 2.4.x\\n* ruby 2.5.x\\n* ruby 2.6.x\\n\\n== Installation\\n\\n gem install bitcoin-ruby\\n # OR\\n git clone https://github.com/lian/bitcoin-ruby.git; cd bitcoin-ruby; bundle install\\n\\nNote that some aspects of the library (such as networking, storage, etc.) need\\nadditional dependencies which are not specified in the gemspec. The core requirements are\\nintentionally kept to a minimum, so nobody has to install unneeded dependencies.\\n\\n* +rspec+ to run the specs\\n* +scrypt+ to use a much faster scrypt hash implementation for Litecoin\\n\\nIf you would like to install using Bundler, put it in your Gemfile and run bundle install\\n gem \\'bitcoin-ruby\\', git: \\'https://github.com/lian/bitcoin-ruby\\', branch: \\'master\\', require: \\'bitcoin\\'\\n\\n== Library Usage\\n\\nThere are different aspects to the library which can be used separately or in combination.\\nHere are some ideas of what you could do. There are also some demo scripts in examples/,\\nsee EXAMPLES.\\n\\n=== Keys/Addresses\\n\\nGenerate a Bitcoin::Key\\n\\n key = Bitcoin::Key.generate\\n key.priv\\n key.pub\\n key.addr\\n sig = key.sign(\"data\")\\n key.verify(\"data\", sig)\\n recovered_key = Bitcoin::Key.from_base58(key.to_base58)\\n\\n=== Blocks / Transactions parsing\\n\\nParse a Bitcoin::Protocol::Block\\n\\n raw_block = File.open(\\'spec/bitcoin/fixtures/rawblock-0.bin\\', \\'rb\\') {|f| f.read}\\n blk = Bitcoin::Protocol::Block.new(raw_block)\\n blk.hash #=> 00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048\\n blk.tx.count #=> 1\\n blk.to_hash #=> ...\\n Bitcoin::Protocol::Block.from_json( blk.to_json )\\n\\nParse a Bitcoin::Protocol::Tx\\n\\n raw_tx = File.open(\\'spec/bitcoin/fixtures/rawtx-01.bin\\', \\'rb\\') {|f| f.read}\\n tx = Bitcoin::Protocol::Tx.new(raw_tx)\\n tx.hash #=> 6e9dd16625b62cfcd4bf02edb89ca1f5a8c30c4b1601507090fb28e59f2d02b4\\n tx.in.size #=> 1\\n tx.out.size #=> 2\\n tx.to_hash #=> ...\\n Bitcoin::Protocol::Tx.from_json( tx.to_json )\\n\\n Bitcoin::Script.new(tx.out[0].pk_script).to_string\\n #=> \"OP_DUP OP_HASH160 b2e21c1db922e3bdc529de7b38b4c401399e9afd OP_EQUALVERIFY OP_CHECKSIG\"\\n\\n=== Transaction verification / Scripts\\n\\nGet the matching transactions (in this example tx1 is the spending transaction)\\n\\n rawtx1 = File.open(\"spec/bitcoin/fixtures/rawtx-f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16.bin\", \\'rb\\') {|f| f.read}\\n rawtx2 = File.open(\"spec/bitcoin/fixtures/rawtx-0437cd7f8525ceed2324359c2d0ba26006d92d856a9c20fa0241106ee5a597c9.bin\", \\'rb\\') {|f| f.read}\\n tx1 = Bitcoin::Protocol::Tx.new(rawtx1)\\n tx2 = Bitcoin::Protocol::Tx.new(rawtx2)\\n\\nThen simply ask the transaction to verify an input\\n\\n tx1.verify_input_signature(0, tx2) #=> true\\n\\n=== Scripts\\n\\nIf you want to control the Bitcoin::Script yourself, you can do so\\n\\n txin = tx1.in.first\\n txout = tx2.out[txin.prev_out_index]\\n script = Bitcoin::Script.new(txin.script_sig + txout.pk_script)\\n\\n result = script.run do |pubkey, sig, hash_type|\\n   hash = tx1.signature_hash_for_input(0, nil, txout.pk_script)\\n   Bitcoin.verify_signature(hash, sig, pubkey.unpack(\"H*\")[0])\\n end\\n result #=> true\\n\\n=== Create Transactions\\n\\nYou need to know the previous output you want to spend (tx hash and output index),\\nas well as the private key for the address required to sign for it.\\n\\n # use testnet so you don\\'t accidentally blow your whole money!\\n Bitcoin.network = :testnet3\\n \\n # make the DSL methods available in your scope\\n include Bitcoin::Builder\\n \\n # the previous transaction that has an output to your address\\n prev_hash = \"6c44b284c20fa22bd69c57a9dbff91fb71deddc8c54fb2f5aa41fc78c96c1ad1\"\\n \\n # the number of the output you want to use\\n prev_out_index = 0\\n \\n # fetch the tx from whereever you like and parse it\\n prev_tx = Bitcoin::P::Tx.from_json(open(\"http://test.webbtc.com/tx/#{prev_hash}.json\"))\\n \\n # the key needed to sign an input that spends the previous output\\n key = Bitcoin::Key.from_base58(\"92ZRu28m2GHSKaaF2W7RswJ2iJYpTzVhBaN6ZLs7TENCs4b7ML8\")\\n \\n # create a new transaction (and sign the inputs)\\n new_tx = build_tx do |t|\\n \\n   # add the input you picked out earlier\\n   t.input do |i|\\n     i.prev_out prev_tx\\n     i.prev_out_index prev_out_index\\n     i.signature_key key\\n   end\\n \\n   # add an output that sends some bitcoins to another address\\n   t.output do |o|\\n     o.value 50000000 # 0.5 BTC in satoshis\\n     o.script {|s| s.recipient \"mugwYJ1sKyr8EDDgXtoh8sdDQuNWKYNf88\" }\\n   end\\n \\n   # add another output spending the remaining amount back to yourself\\n   # if you want to pay a tx fee, reduce the value of this output accordingly\\n   # if you want to keep your financial history private, use a different address\\n   t.output do |o|\\n     o.value 49000000 # 0.49 BTC, leave 0.01 BTC as fee\\n     o.script {|s| s.recipient key.addr }\\n   end\\n \\n end\\n \\n # examine your transaction. you can relay it through http://test.webbtc.com/relay_tx\\n # that will also give you a hint on the error if something goes wrong\\n puts new_tx.to_json\\n\\n== Documentation\\n\\nAlways trying to improve, any help appreciated! If anything is unclear to you, let us know!\\n\\nDocumentation is generated using yardoc:\\n\\n rake doc\\n\\nThe specs are also a good place to see how something works.\\n\\n== Specs\\n\\nSpecs require libsecp256k1 in order to be fully run. Therefore, the first step\\nin running the specs is to build this library if you haven\\'t already:\\n\\n  rake build_libsecp256k1\\n\\nThe majority of specs can be run with\\n\\n rake rspec\\n\\nor, if you want to run a single spec\\n\\n bundle exec rspec spec/bitcoin/bitcoin_spec.rb\\n\\nIf you make changes to the code or add functionality, please also add specs.\\n\\nTo run specs for changes that monkey patch significant functionality, you\\nshould run the specs individually. For example, to run the Dogecoin specs:\\n\\n  rake coin_spec[dogecoin]\\n\\nIf support is added for any new coins a corresponding coin spec should also be\\nadded to test specific functionality of that coin.\\n\\n== Development\\n\\nAny help or feedback is greatly appreciated! From getting knee-deep into elliptic-curve acrobatics,\\nto cleaning up high-level naming conventions, there is something for everyone to do.\\nEven if you are completely lost, just pointing out what is unclear helps a lot!\\n\\nIf you are curious or like to participate in development, drop by \\\\#bitcoin-ruby on irc.freenode.net!\\n\\n== License\\n\\nAvailable here: [link:COPYING]\\n'},\n",
       " {'repo': 'kylemanna/docker-bitcoind',\n",
       "  'language': 'Shell',\n",
       "  'readme_contents': 'Bitcoind for Docker\\n===================\\n\\n[![Docker Stars](https://img.shields.io/docker/stars/kylemanna/bitcoind.svg)](https://hub.docker.com/r/kylemanna/bitcoind/)\\n[![Docker Pulls](https://img.shields.io/docker/pulls/kylemanna/bitcoind.svg)](https://hub.docker.com/r/kylemanna/bitcoind/)\\n[![Build Status](https://travis-ci.org/kylemanna/docker-bitcoind.svg?branch=master)](https://travis-ci.org/kylemanna/docker-bitcoind/)\\n\\nDocker image that runs the Bitcoin bitcoind node in a container for easy deployment.\\n\\n\\nRequirements\\n------------\\n\\n* Physical machine, cloud instance, or VPS that supports Docker (i.e. [Vultr](http://bit.ly/1HngXg0), [Digital Ocean](http://bit.ly/18AykdD), KVM or XEN based VMs) running Ubuntu 14.04 or later (*not OpenVZ containers!*)\\n* At least 500 GB to store the block chain files (and always growing!)\\n* At least 1 GB RAM + 2 GB swap file\\n\\nRecommended and tested on unadvertised (only shown within control panel) [Vultr SATA Storage 1024 MB RAM/250 GB disk instance @ $10/mo](http://bit.ly/vultrbitcoind).  Vultr also *accepts Bitcoin payments*!\\n\\n\\nReally Fast Quick Start\\n-----------------------\\n\\nOne liner for Ubuntu 14.04 LTS machines with JSON-RPC enabled on localhost and adds upstart init script:\\n\\n    curl https://raw.githubusercontent.com/kylemanna/docker-bitcoind/master/bootstrap-host.sh | sh -s trusty\\n\\n\\nQuick Start\\n-----------\\n\\n1. Create a `bitcoind-data` volume to persist the bitcoind blockchain data, should exit immediately.  The `bitcoind-data` container will store the blockchain when the node container is recreated (software upgrade, reboot, etc):\\n\\n        docker volume create --name=bitcoind-data\\n        docker run -v bitcoind-data:/bitcoin/.bitcoin --name=bitcoind-node -d \\\\\\n            -p 8333:8333 \\\\\\n            -p 127.0.0.1:8332:8332 \\\\\\n            kylemanna/bitcoind\\n\\n2. Verify that the container is running and bitcoind node is downloading the blockchain\\n\\n        $ docker ps\\n        CONTAINER ID        IMAGE                         COMMAND             CREATED             STATUS              PORTS                                              NAMES\\n        d0e1076b2dca        kylemanna/bitcoind:latest     \"btc_oneshot\"       2 seconds ago       Up 1 seconds        127.0.0.1:8332->8332/tcp, 0.0.0.0:8333->8333/tcp   bitcoind-node\\n\\n3. You can then access the daemon\\'s output thanks to the [docker logs command]( https://docs.docker.com/reference/commandline/cli/#logs)\\n\\n        docker logs -f bitcoind-node\\n\\n4. Install optional init scripts for upstart and systemd are in the `init` directory.\\n\\n\\nDocumentation\\n-------------\\n\\n* Additional documentation in the [docs folder](docs).\\n'},\n",
       " {'repo': 'GammaGao/bitcoinwhitepaper',\n",
       "  'language': None,\n",
       "  'readme_contents': '# 中本聪(Satoshi Nakamoto)比特币白皮书英文版\\n* [白皮书英文版PDF](https://github.com/GammaGao/bitcoinwhitepaper/blob/master/bitcoin_en.pdf)\\n\\n# 中本聪(Satoshi Nakamoto)比特币白皮书中文版\\n* [白皮书中文版PDF](https://github.com/GammaGao/bitcoinwhitepaper/blob/master/bitcoin_cn.pdf)\\n\\n# 比特币开发者指南英文版\\n* [开发者指南英文版](https://bitcoin.org/en/developer-guide)\\n\\n# 比特币开发者指南中文版\\n* [开发者指南中文版](https://www.yiyibooks.cn/Gamma/bitcoin/developer-guide.html)\\n\\n'},\n",
       " {'repo': 'pointbiz/bitaddress.org',\n",
       "  'language': 'HTML',\n",
       "  'readme_contents': '# bitaddress.org\\r\\nJavaScript Client-Side Bitcoin Wallet Generator\\r\\n\\r\\nNow Bitcoin addresses and their corresponding private key can be conveniently \\r\\ngenerated in a web browser.\\r\\n\\r\\nThe bitaddress.org project provides an all-in-one HTML document with embedded\\r\\nJavaScript/Css/Images. The JavaScript is readable not minified and contains no\\r\\nXMLHttpRequest\\'s (no AJAX). The benefit of this technique is you can load the \\r\\nJavaScript locally and trust that the JavaScript did not change after being \\r\\nloaded. \\r\\n\\r\\nHere is a link to the BitcoinTalk.org forum topic discussing this project:\\r\\nhttps://bitcointalk.org/index.php?topic=43496.0\\r\\n\\r\\n\\r\\nPlease send DONATIONS for this project to Bitcoin Address: \\r\\n1NiNja1bUmhSoTXozBRBEtR8LeF9TGbZBN\\r\\n\\r\\n\\r\\nEND USER NOTES:\\r\\n\\r\\n 1) For Bulk Wallet I recommended using Google Chrome, it\\'s the fastest.\\r\\n\\r\\n 2) Requires IE9+, Firefox, Chrome or sufficient JavaScript support.\\r\\n\\r\\n 3) Mobile Safari only works with iPhone4 or newer devices.\\r\\n    Older devices timeout while executing JavaScript.\\r\\n\\r\\n 4) DO NOT use Opera Mini it renders JavaScript output server side, therefore\\r\\n    they might record the private key you generated.\\r\\n\\r\\n 5) BIP38 most likely will not work on mobile devices due to hardware limitations.\\r\\n\\r\\n\\r\\nNotice of Copyrights and Licenses:\\r\\n---------------------------------------\\r\\nThe bitaddress.org project, software and embedded resources are\\r\\ncopyright bitaddress.org.\\r\\n\\r\\nThe bitaddress.org name and logo are not part of the open source\\r\\nlicense.\\r\\n\\r\\nPortions of the all-in-one HTML document contain JavaScript codes that\\r\\nare the copyrights of others. The individual copyrights are included\\r\\nthroughout the document along with their licenses. Included JavaScript\\r\\nlibraries are separated with HTML script tags.\\r\\n\\r\\nSummary of JavaScript functions with a redistributable license:\\r\\n\\r\\nJavaScript function\\t|\\tLicense\\r\\n-------------------\\t|\\t--------------\\r\\nArray.prototype.map\\t|\\tPublic Domain\\r\\nwindow.Crypto | BSD License\\r\\nwindow.SecureRandom\\t| BSD License\\r\\nwindow.EllipticCurve\\t|\\tBSD License\\r\\nwindow.BigInteger |\\tBSD License\\r\\nwindow.QRCode | MIT License\\r\\nwindow.Bitcoin | MIT License\\r\\n\\r\\nThe bitaddress.org software is available under The MIT License (MIT)\\r\\nCopyright (c) 2011-2013 bitaddress.org\\r\\n\\r\\nPermission is hereby granted, free of charge, to any person obtaining\\r\\na copy of this software and associated documentation files (the\\r\\n\"Software\"), to deal in the Software without restriction, including\\r\\nwithout limitation the rights to use, copy, modify, merge, publish,\\r\\ndistribute, sublicense, and/or sell copies of the Software, and to\\r\\npermit persons to whom the Software is furnished to do so, subject to\\r\\nthe following conditions:\\r\\n\\r\\nThe above copyright notice and this permission notice shall be\\r\\nincluded in all copies or substantial portions of the Software.\\r\\n\\r\\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\\r\\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF\\r\\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND\\r\\nNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE\\r\\nLIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION\\r\\nOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION\\r\\nWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\\r\\n'},\n",
       " {'repo': 'jgarzik/python-bitcoinrpc',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '=================\\npython-bitcoinrpc\\n=================\\n\\nAuthServiceProxy is an improved version of python-jsonrpc.\\n\\nIt includes the following generic improvements:\\n\\n* HTTP connections persist for the life of the AuthServiceProxy object\\n* sends protocol \\'version\\', per JSON-RPC 1.1\\n* sends proper, incrementing \\'id\\'\\n* uses standard Python json lib\\n* can optionally log all RPC calls and results\\n* JSON-2.0 batch support\\n\\nIt also includes the following bitcoin-specific details:\\n\\n* sends Basic HTTP authentication headers\\n* parses all JSON numbers that look like floats as Decimal,\\n  and serializes Decimal values to JSON-RPC connections.\\n\\nInstallation\\n============\\n\\n1. change the first line of setup.py to point to the directory of your installation of python 2.*\\n2. run setup.py\\n\\nNote: This will only install bitcoinrpc. If you also want to install jsonrpc to preserve \\nbackwards compatibility, you have to replace \\'bitcoinrpc\\' with \\'jsonrpc\\' in setup.py and run it again.\\n\\nOr simply install the library using pip::\\n\\n    pip install python-bitcoinrpc\\n\\nExample\\n=======\\n.. code:: python\\n\\n    from bitcoinrpc.authproxy import AuthServiceProxy, JSONRPCException\\n\\n    # rpc_user and rpc_password are set in the bitcoin.conf file\\n    rpc_connection = AuthServiceProxy(\"http://%s:%s@127.0.0.1:8332\"%(rpc_user, rpc_password))\\n    best_block_hash = rpc_connection.getbestblockhash()\\n    print(rpc_connection.getblock(best_block_hash))\\n\\n    # batch support : print timestamps of blocks 0 to 99 in 2 RPC round-trips:\\n    commands = [ [ \"getblockhash\", height] for height in range(100) ]\\n    block_hashes = rpc_connection.batch_(commands)\\n    blocks = rpc_connection.batch_([ [ \"getblock\", h ] for h in block_hashes ])\\n    block_times = [ block[\"time\"] for block in blocks ]\\n    print(block_times)\\n\\nLogging all RPC calls to stderr\\n===============================\\n.. code:: python\\n\\n    from bitcoinrpc.authproxy import AuthServiceProxy, JSONRPCException\\n    import logging\\n\\n    logging.basicConfig()\\n    logging.getLogger(\"BitcoinRPC\").setLevel(logging.DEBUG)\\n\\n    rpc_connection = AuthServiceProxy(\"http://%s:%s@127.0.0.1:8332\"%(rpc_user, rpc_password))\\n    print(rpc_connection.getinfo())\\n\\nProduces output on stderr like\\n\\n    DEBUG:BitcoinRPC:-1-> getinfo []\\n    DEBUG:BitcoinRPC:<-1- {\"connections\": 8, ...etc }\\n\\nSocket timeouts under heavy load\\n================================\\nPass the timeout argument to prevent \"socket timed out\" exceptions:\\n\\n.. code:: python\\n\\n    rpc_connection = AuthServiceProxy(\\n        \"http://%s:%s@%s:%s\"%(rpc_user, rpc_password, rpc_host, rpc_port),\\n        timeout=120)\\n'},\n",
       " {'repo': 'BTCPrivate/BitcoinPrivate-legacy',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': 'Bitcoin Private\\n----------------\\n** 10/8/2020 - Current chain offline - New code and chain coming soon **\\n\\n\\n**Bitcoin Private v1.0.15**\\n\\nP2P Port: 7933\\n\\nRPC Port: 7932\\n\\nBitcoin Private is a fork of Zclassic, merging in a snapshotted UTXO set of Bitcoin. BTCP is financial freedom.\\n\\nBuild\\n-----------------\\n### Linux\\n\\nGet dependencies:\\n```{r, engine=\\'bash\\'}\\nsudo apt-get install \\\\\\n      build-essential pkg-config libc6-dev m4 g++-multilib \\\\\\n      autoconf libtool ncurses-dev unzip git python \\\\\\n      zlib1g-dev wget bsdmainutils automake\\n```\\n\\nBuild:\\n```{r, engine=\\'bash\\'}\\n# Checkout\\ngit clone https://github.com/BTCPrivate/BitcoinPrivate.git\\ncd BitcoinPrivate\\n# Build\\n./btcputil/build.sh -j$(nproc)\\n# Fetch Zcash ceremony keys\\n./btcputil/fetch-params.sh\\n```\\n\\nCreate Config File:\\n```\\nmkdir ~/.btcprivate\\ntouch ~/.btcprivate/btcprivate.conf\\nvi ~/.btcprivate/btcprivate.conf\\n```\\n\\nAdd following lines to `btcprivate.conf` and be sure to change the rpcpassword:\\n```\\nrpcuser=btcprivaterpc\\nrpcpassword=set-a-password\\nrpcallowip=127.0.0.1\\n#addnode=dnsseed.btcprivate.org\\n#addnode=dnsseed.btcprivate.co\\n```\\n\\nGet backup chain parameters (this will speed up syncing and is optional)\\n(Ideally this step would be skipped to ensure integrity throughout the network)\\n(However, this is a backup from the official Electrumx server 29th September 2019)\\n``` \\ncd ~/.btcprivate \\nwget https://params.btcprivate.org/chainstate.tar.gz \\ntar -zxvf chainstate.tar.gz \\ncd ~/BitcoinPrivate \\n```\\n\\nRun:\\n```\\n./src/btcpd\\n```\\n\\n### Windows\\nWindows is not a fully supported build - however there are two ways to build BTCP for Windows:\\n\\n* On Linux using [Mingw-w64](https://mingw-w64.org/doku.php) cross compiler tool chain. Ubuntu 16.04 Xenial is proven to work and the instructions is for such release.\\n* On Windows 10 (64-bit version) using [Windows Subsystem for Linux (WSL)](https://msdn.microsoft.com/commandline/wsl/about) and Mingw-w64 cross compiler tool chain.\\n\\nWith Windows 10, Microsoft released a feature called WSL. It basically allows you to run a bash shell directly on Windows in an ubuntu environment. WSL can be installed with other Linux variants, but as mentioned before, the distro proven to work is Ubuntu.\\nFollow this [link](https://msdn.microsoft.com/en-us/commandline/wsl/install_guide) for installing WSL first\\n\\n### Building for Windows 64-Bit\\n1. Get the usual dependencies:\\n```{r, engine=\\'bash\\'}\\nsudo apt-get install \\\\\\n      build-essential pkg-config libc6-dev m4 g++-multilib \\\\\\n      autoconf libtool ncurses-dev unzip git python \\\\\\n      zlib1g-dev wget bsdmainutils automake make cmake mingw-w64\\n```\\n\\n2. Set the default mingw32 gcc/g++ compiler option to posix, fix problem with packages in Xenial\\n```{r, engine=\\'bash\\'}\\nsudo apt install software-properties-common\\nsudo add-apt-repository \"deb http://archive.ubuntu.com/ubuntu zesty universe\"\\nsudo apt update\\nsudo apt upgrade\\nsudo update-alternatives --config x86_64-w64-mingw32-gcc\\nsudo update-alternatives --config x86_64-w64-mingw32-g++\\n```\\n\\n3. Install Rust\\n```{r, engine=\\'bash\\'}\\ncurl https://sh.rustup.rs -sSf | sh\\nsource ~/.cargo/env\\nrustup install stable-x86_64-unknown-linux-gnu\\nrustup install stable-x86_64-pc-windows-gnu\\nrustup target add x86_64-pc-windows-gnu\\nvi  ~/.cargo/config\\n```\\nand add:\\n```\\n[target.x86_64-pc-windows-gnu]\\nlinker = \"/usr/bin/x86_64-w64-mingw32-gcc\"\\n```\\n\\nNote that in WSL, the BTCPrivate source code must be somewhere in the default mount file system. i.e /usr/src/BTCPrivate, and not on /mnt/d/. What this means is that you cannot build directly on the windows system\\n\\n4. Build for Windows\\n\\n```{r, engine=\\'bash\\'}\\nPATH=$(echo \"$PATH\" | sed -e \\'s/:\\\\/mnt.*//g\\') # strip out problematic Windows %PATH% imported var\\n./btcputil/build-win.sh -j$(nproc)\\n```\\n\\n5. Installation\\n\\nIf compiling on linux, use the following command to build the executables in `./depends/x86_64-w64-mingw32/bin/\\n\\n```{r, engine=\\'bash\\'}\\nsudo make install DESTDIR=\\n```\\n\\nIf compiling using WSL, use the following command to build the executables in `c:\\\\btcp\\\\BTCPrivate\\n\\n```{r, engine=\\'bash\\'}\\nsudo make install DESTDIR=/mnt/c/btcp/BTCPrivate\\n```\\n\\n### Building for Mac\\n1. Install xcode.\\n```{r, engine=\\'bash\\'}\\nxcode-select --install\\n```\\n2. Install HomeBrew.\\n```{r, engine=\\'bash\\'}\\n/usr/bin/ruby -e \"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)\"\\n```\\n3. Install Dependencies with HomeBrew.\\n```{r, engine=\\'bash\\'}\\nbrew install cmake autoconf libtool automake coreutils pkgconfig gmp wget\\n```\\n4. Install gcc5 with HomeBrew. (** IF USING XCODE 10+ remove --without-multilib flag**)\\n```{r, engine=\\'bash\\'}\\nbrew install gcc5 --without-multilib\\n```\\n5. Clone the Bitcoin Private repo to your computer.\\n```{r, engine=\\'bash\\'}\\ngit clone https://github.com/BTCPrivate/BitcoinPrivate.git\\n```\\n6. Change to BitcoinPrivate Directory.\\n```{r, engine=\\'bash\\'}\\ncd BitcoinPrivate\\n```\\n7. Build Bitcoin Private Daemon code.\\n```{r, engine=\\'bash\\'}\\n./btcputil/build-mac.sh -j$(sysctl -n hw.physicalcpu)\\n```\\n8. Fetch key & Params.\\n```{r, engine=\\'bash\\'}\\n./btcputil/fetch-params.sh\\n```\\n9. Run the Bitcoin Private Daemon that was just built.\\n```{r, engine=\\'bash\\'}\\n./src/btcpd\\n```\\n\\n### Additional notes\\n\\nIf you plan to build for windows and linux at the same time, be sure to delete all the built files for whatever you build first. An easy way to do this is by taking the binaries out of the repo, delete all files except the .git folder and then do a git hard reset.\\n\\n### Testnet\\n\\nBuild the latest version of BTCP using the instructions below, then follow the [testnet guide](doc/testnet.md)\\n\\nAbout\\n--------------\\n\\n[Bitcoin Private](http://zclassic.org/), like [Zclassic](https://zclassic.org/) and [Zcash](https://z.cash/), is an implementation of the \"Zerocash\" protocol.\\nBased on Zclassic\\'s code, it intends to offer a far higher standard of privacy\\nthrough a sophisticated zero-knowledge proving scheme that preserves\\nconfidentiality of transaction metadata. Technical details are available\\nin the Zcash [Protocol Specification](https://github.com/zcash/zips/raw/master/protocol/protocol.pdf).\\n\\nThis software is the Bitcoin Private client. It downloads and stores the entire history\\nof Bitcoin Private transactions. Depending on the speed of your computer and network\\nconnection, the synchronization process could take a day or more once the\\nblockchain has reached a significant size.\\n\\nIt includes both `btcpd` (the daemon) and `btcp-cli` (the command line tools).\\n\\nSecurity Warnings\\n-----------------\\n\\nSee important security warnings in\\n[doc/security-warnings.md](doc/security-warnings.md).\\n\\n**Bitcoin Private is unfinished and highly experimental.** Use at your own risk.\\n\\nDeprecation Policy\\n------------------\\n\\nThis release is considered deprecated 16 weeks after the release day. There\\nis an automatic deprecation shutdown feature which will halt the node some\\ntime after this 16 week time period. The automatic feature is based on block\\nheight and can be explicitly disabled.\\n\\nWhere do I begin?\\n-----------------\\nWe have a guide for joining the main Bitcoin Private network:\\nhttps://github.com/zcash/zcash/wiki/1.0-User-Guide\\n\\n### Need Help?\\n\\n* See documentation at the [Zcash Wiki](https://github.com/zcash/zcash/wiki) and the [Zclassic Wiki](https://github.com/z-classic/zclassic/wiki)\\n  for help and more information.\\n\\n### Want to participate in development?\\n\\n* Code review is welcome!\\n* If you want to get to know us join our Discord: https://discord.gg/9xezcaK\\n* We have a brief guide for joining the Bitcoin private testnet [here](doc/testnet.md)\\n\\n\\nParticipation in the Bitcoin Private project is subject to a\\n[Code of Conduct](code_of_conduct.md).\\n\\nBuilding\\n--------\\n\\nBuild BTCP along with most dependencies from source by running\\n`./btcputil/build.sh`. Currently only Linux is officially supported.\\n\\nLicense\\n-------\\n\\nFor license information see the file [COPYING](COPYING).\\n'},\n",
       " {'repo': 'xiaolai/bitcoin-whitepaper-chinese-translation',\n",
       "  'language': 'HTML',\n",
       "  'readme_contents': '# 比特币白皮书中文版\\n\\n2008 年 10 月 31 日，中本聪发布了《[比特币白皮书](https://bitcoin.org/bitcoin.pdf)》。\\n\\n网上有若干个版本的《比特币白皮书》中文翻译版本：\\n\\n> - [tiehexue 翻译版本](https://github.com/wbnns/bitcoinwhitepaper/blob/master/bitcoin_cn.pdf)\\n> - [shdxiang 翻译版本](https://github.com/wbnns/bitcoinwhitepaper/blob/master/bitcoin_zh_cn.pdf)\\n> - [QQagent（吴忌寒）翻译版本](https://www.8btc.com/wiki/bitcoin-a-peer-to-peer-electronic-cash-system)\\n> - [金晓翻译版本（含注解）](https://zhuanlan.zhihu.com/p/25039679)\\n\\n若干年来，《比特币白皮书》我不知道读了多少遍，但在自己动手翻译之前，从未在网上阅读过中文版 —— 因为对我来说没有这个必要。2018 年 10 月 31 日的几天前，我动手翻译了一遍，放在这里。\\n\\n翻译这个事情，从来都没有“最好的” —— 信达雅也通常只不过是一厢情愿而已。我之所以动手翻译，并非出自于自认为翻译得更好，仅仅是出于一时兴起而已，前后耗费一整天的时间。翻译过程中也参照了以上提到的几个版本，期间，霍炬（[@virushuo](https://github.com/virushuo)）和老猫提供了大量的帮助。发布之后，很快 [@x1angli](https://github.com/x1angli) 提交了几处很好的更正……\\n\\n白皮书中所使用的 svg 格式图片，来自 [dhimmel 的代码仓库](https://github.com/dhimmel/bitcoin-whitepaper)，@dhimmel 为 Bitcoin Whitepaper 重新制作了版式更好的英文版 [html 版本](http://git.dhimmel.com/bitcoin-whitepaper/)和 [pdf 版本](http://git.dhimmel.com/bitcoin-whitepaper/manuscript.pdf)。\\n\\n《比特币白皮书英中对照版》一共有三个文件格式：\\n\\n> - [markdown](Bitcoin-Whitepaper-EN-CN.md)\\n> - [html](Bitcoin-Whitepaper-EN-CN.html)\\n> - [pdf](Bitcoin-Whitepaper-EN-CN.pdf)\\n\\n很遗憾，在 github 上直接浏览 markdown 文件时，其中的数学公式不能正确显示。本页面右上部有绿色的按钮```Clone or download```，下载 ZIP 之后解压缩在本地电脑，即可正常翻阅。MacOS 上比较好用的 Markdown 编辑器是：[Typora](https://typora.io/)，*.md* 文件可以用它阅读，以上的 pdf/html 版本就是使用 Typora 导出的。\\n\\n您也可以直接[点击这里在线阅读](http://lixiaolai.com/#/bitcoin-whitepaper-cn-en-translation/Bitcoin-Whitepaper-EN-CN.html)。\\n\\n希望对大家有所帮助！\\n\\n其实吧，我知道，这东西真没几个人认真看的…… 十年过来，一如既往地如此。\\n'},\n",
       " {'repo': 'pooler/cpuminer',\n",
       "  'language': 'Assembly',\n",
       "  'readme_contents': 'This is a multi-threaded CPU miner for Litecoin and Bitcoin,\\nfork of Jeff Garzik\\'s reference cpuminer.\\n\\nLicense: GPLv2.  See COPYING for details.\\n\\nDownloads:  https://sourceforge.net/projects/cpuminer/files/\\nGit tree:   https://github.com/pooler/cpuminer\\n\\nDependencies:\\n\\tlibcurl\\t\\t\\thttp://curl.haxx.se/libcurl/\\n\\tjansson\\t\\t\\thttp://www.digip.org/jansson/\\n\\t\\t(jansson is included in-tree)\\n\\nBasic *nix build instructions:\\n\\t./autogen.sh\\t# only needed if building from git repo\\n\\t./nomacro.pl\\t# in case the assembler doesn\\'t support macros\\n\\t./configure CFLAGS=\"-O3\" # make sure -O3 is an O and not a zero!\\n\\tmake\\n\\nNotes for AIX users:\\n\\t* To build a 64-bit binary, export OBJECT_MODE=64\\n\\t* GNU-style long options are not supported, but are accessible\\n\\t  via configuration file\\n\\nBasic Windows build instructions, using MinGW:\\n\\tInstall MinGW and the MSYS Developer Tool Kit (http://www.mingw.org/)\\n\\t\\t* Make sure you have mstcpip.h in MinGW\\\\include\\n\\tIf using MinGW-w64, install pthreads-w64\\n\\tInstall libcurl devel (http://curl.haxx.se/download.html)\\n\\t\\t* Make sure you have libcurl.m4 in MinGW\\\\share\\\\aclocal\\n\\t\\t* Make sure you have curl-config in MinGW\\\\bin\\n\\tIn the MSYS shell, run:\\n\\t\\t./autogen.sh\\t# only needed if building from git repo\\n\\t\\tLIBCURL=\"-lcurldll\" ./configure CFLAGS=\"-O3\"\\n\\t\\tmake\\n\\nArchitecture-specific notes:\\n\\tARM:\\tNo runtime CPU detection. The miner can take advantage\\n\\t\\tof some instructions specific to ARMv5E and later processors,\\n\\t\\tbut the decision whether to use them is made at compile time,\\n\\t\\tbased on compiler-defined macros.\\n\\t\\tTo use NEON instructions, add \"-mfpu=neon\" to CFLAGS.\\n\\tPowerPC: No runtime CPU detection.\\n\\t\\tTo use AltiVec instructions, add \"-maltivec\" to CFLAGS.\\n\\tx86:\\tThe miner checks for SSE2 instructions support at runtime,\\n\\t\\tand uses them if they are available.\\n\\tx86-64:\\tThe miner can take advantage of AVX, AVX2 and XOP instructions,\\n\\t\\tbut only if both the CPU and the operating system support them.\\n\\t\\t    * Linux supports AVX starting from kernel version 2.6.30.\\n\\t\\t    * FreeBSD supports AVX starting with 9.1-RELEASE.\\n\\t\\t    * Mac OS X added AVX support in the 10.6.8 update.\\n\\t\\t    * Windows supports AVX starting from Windows 7 SP1 and\\n\\t\\t      Windows Server 2008 R2 SP1.\\n\\t\\tThe configure script outputs a warning if the assembler\\n\\t\\tdoesn\\'t support some instruction sets. In that case, the miner\\n\\t\\tcan still be built, but unavailable optimizations are left off.\\n\\t\\tThe miner uses the VIA Padlock Hash Engine where available.\\n\\nUsage instructions:  Run \"minerd --help\" to see options.\\n\\nConnecting through a proxy:  Use the --proxy option.\\nTo use a SOCKS proxy, add a socks4:// or socks5:// prefix to the proxy host.\\nProtocols socks4a and socks5h, allowing remote name resolving, are also\\navailable since libcurl 7.18.0.\\nIf no protocol is specified, the proxy is assumed to be a HTTP proxy.\\nWhen the --proxy option is not used, the program honors the http_proxy\\nand all_proxy environment variables.\\n\\nAlso many issues and FAQs are covered in the forum thread\\ndedicated to this program,\\n\\thttps://bitcointalk.org/index.php?topic=55038.0\\n'},\n",
       " {'repo': 'HelloZeroNet/ZeroNet',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# ZeroNet [![Build Status](https://travis-ci.org/HelloZeroNet/ZeroNet.svg?branch=master)](https://travis-ci.org/HelloZeroNet/ZeroNet) [![Documentation](https://img.shields.io/badge/docs-faq-brightgreen.svg)](https://zeronet.io/docs/faq/) [![Help](https://img.shields.io/badge/keep_this_project_alive-donate-yellow.svg)](https://zeronet.io/docs/help_zeronet/donate/)\\n\\n[简体中文](./README-zh-cn.md)\\n[English](./README.md)\\n\\nДецентрализованные вебсайты использующие Bitcoin криптографию и BitTorrent сеть - https://zeronet.io\\n\\n\\n## Зачем?\\n\\n* Мы верим в открытую, свободную, и не отцензуренную сеть и коммуникацию.\\n* Нет единой точки отказа: Сайт онлайн пока по крайней мере 1 пир обслуживает его.\\n* Никаких затрат на хостинг: Сайты обслуживаются посетителями.\\n* Невозможно отключить: Он нигде, потому что он везде.\\n* Быстр и работает оффлайн: Вы можете получить доступ к сайту, даже если Интернет недоступен.\\n\\n\\n## Особенности\\n * Обновляемые в реальном времени сайты\\n * Поддержка Namecoin .bit доменов\\n * Лёгок в установке: распаковал & запустил\\n * Клонирование вебсайтов в один клик\\n * Password-less [BIP32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki)\\n   based authorization: Ваша учетная запись защищена той же криптографией, что и ваш Bitcoin-кошелек\\n * Встроенный SQL-сервер с синхронизацией данных P2P: Позволяет упростить разработку сайта и ускорить загрузку страницы\\n * Анонимность: Полная поддержка сети Tor с помощью скрытых служб .onion вместо адресов IPv4\\n * TLS зашифрованные связи\\n * Автоматическое открытие uPnP порта\\n * Плагин для поддержки многопользовательской (openproxy)\\n * Работает с любыми браузерами и операционными системами\\n\\n\\n## Как это работает?\\n\\n* После запуска `zeronet.py` вы сможете посетить зайты (zeronet сайты) используя адрес\\n  `http://127.0.0.1:43110/{zeronet_address}`\\n(например. `http://127.0.0.1:43110/1HeLLo4uzjaLetFx6NH3PMwFP3qbRbTf3D`).\\n* Когда вы посещаете новый сайт zeronet, он пытается найти пиров с помощью BitTorrent\\n  чтобы загрузить файлы сайтов (html, css, js ...) из них.\\n* Каждый посещенный зайт также обслуживается вами. (Т.е хранится у вас на компьютере)\\n* Каждый сайт содержит файл `content.json`, который содержит все остальные файлы в хэше sha512\\n  и подпись, созданную с использованием частного ключа сайта.\\n* Если владелец сайта (у которого есть закрытый ключ для адреса сайта) изменяет сайт, то он/она\\n  подписывает новый `content.json` и публикует его для пиров. После этого пиры проверяют целостность `content.json`\\n  (используя подпись), они загружают измененные файлы и публикуют новый контент для других пиров.\\n\\n####  [Слайд-шоу о криптографии ZeroNet, обновлениях сайтов, многопользовательских сайтах »](https://docs.google.com/presentation/d/1_2qK1IuOKJ51pgBvllZ9Yu7Au2l551t3XBgyTSvilew/pub?start=false&loop=false&delayms=3000)\\n####  [Часто задаваемые вопросы »](https://zeronet.io/docs/faq/)\\n\\n####  [Документация разработчика ZeroNet »](https://zeronet.io/docs/site_development/getting_started/)\\n\\n\\n## Скриншоты\\n\\n![Screenshot](https://i.imgur.com/H60OAHY.png)\\n![ZeroTalk](https://zeronet.io/docs/img/zerotalk.png)\\n\\n#### [Больше скриншотов в ZeroNet документации »](https://zeronet.io/docs/using_zeronet/sample_sites/)\\n\\n\\n## Как вступить\\n\\n* Скачайте ZeroBundle пакет:\\n  * [Microsoft Windows](https://github.com/HelloZeroNet/ZeroNet-win/archive/dist/ZeroNet-win.zip)\\n  * [Apple macOS](https://github.com/HelloZeroNet/ZeroNet-mac/archive/dist/ZeroNet-mac.zip)\\n  * [Linux 64-bit](https://github.com/HelloZeroNet/ZeroBundle/raw/master/dist/ZeroBundle-linux64.tar.gz)\\n  * [Linux 32-bit](https://github.com/HelloZeroNet/ZeroBundle/raw/master/dist/ZeroBundle-linux32.tar.gz)\\n* Распакуйте где угодно\\n* Запустите `ZeroNet.exe` (win), `ZeroNet(.app)` (osx), `ZeroNet.sh` (linux)\\n\\n### Linux терминал\\n\\n* `wget https://github.com/HelloZeroNet/ZeroBundle/raw/master/dist/ZeroBundle-linux64.tar.gz`\\n* `tar xvpfz ZeroBundle-linux64.tar.gz`\\n* `cd ZeroBundle`\\n* Запустите с помощью `./ZeroNet.sh`\\n\\nОн загружает последнюю версию ZeroNet, затем запускает её автоматически.\\n\\n#### Ручная установка для Debian Linux\\n\\n* `sudo apt-get update`\\n* `sudo apt-get install msgpack-python python-gevent`\\n* `wget https://github.com/HelloZeroNet/ZeroNet/archive/master.tar.gz`\\n* `tar xvpfz master.tar.gz`\\n* `cd ZeroNet-master`\\n* Запустите с помощью `python2 zeronet.py`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\n### [Arch Linux](https://www.archlinux.org)\\n\\n* `git clone https://aur.archlinux.org/zeronet.git`\\n* `cd zeronet`\\n* `makepkg -srci`\\n* `systemctl start zeronet`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\nСмотрите [ArchWiki](https://wiki.archlinux.org)\\'s [ZeroNet\\narticle](https://wiki.archlinux.org/index.php/ZeroNet) для дальнейшей помощи.\\n\\n### [Gentoo Linux](https://www.gentoo.org)\\n\\n* [`layman -a raiagent`](https://github.com/leycec/raiagent)\\n* `echo \\'>=net-vpn/zeronet-0.5.4\\' >> /etc/portage/package.accept_keywords`\\n* *(Опционально)* Включить поддержку Tor: `echo \\'net-vpn/zeronet tor\\' >>\\n  /etc/portage/package.use`\\n* `emerge zeronet`\\n* `rc-service zeronet start`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\nСмотрите `/usr/share/doc/zeronet-*/README.gentoo.bz2` для дальнейшей помощи.\\n\\n### [FreeBSD](https://www.freebsd.org/)\\n\\n* `pkg install zeronet` or `cd /usr/ports/security/zeronet/ && make install clean`\\n* `sysrc zeronet_enable=\"YES\"`\\n* `service zeronet start`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\n### [Vagrant](https://www.vagrantup.com/)\\n\\n* `vagrant up`\\n* Подключитесь к VM с помощью `vagrant ssh`\\n* `cd /vagrant`\\n* Запустите `python2 zeronet.py --ui_ip 0.0.0.0`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\n### [Docker](https://www.docker.com/)\\n* `docker run -d -v <local_data_folder>:/root/data -p 15441:15441 -p 127.0.0.1:43110:43110 nofish/zeronet`\\n* Это изображение Docker включает в себя прокси-сервер Tor, который по умолчанию отключён.\\n  Остерегайтесь что некоторые хостинг-провайдеры могут не позволить вам запускать Tor на своих серверах.\\n  Если вы хотите включить его,установите переменную среды `ENABLE_TOR` в` true` (по умолчанию: `false`) Например:\\n\\n `docker run -d -e \"ENABLE_TOR=true\" -v <local_data_folder>:/root/data -p 15441:15441 -p 127.0.0.1:43110:43110 nofish/zeronet`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\n### [Virtualenv](https://virtualenv.readthedocs.org/en/latest/)\\n\\n* `virtualenv env`\\n* `source env/bin/activate`\\n* `pip install msgpack gevent`\\n* `python2 zeronet.py`\\n* Откройте http://127.0.0.1:43110/ в вашем браузере.\\n\\n## Текущие ограничения\\n\\n* ~~Нет torrent-похожего файла разделения для поддержки больших файлов~~ (поддержка больших файлов добавлена)\\n* ~~Не анонимнее чем Bittorrent~~ (добавлена встроенная поддержка Tor)\\n* Файловые транзакции не сжаты ~~ или незашифрованы еще ~~ (добавлено шифрование TLS)\\n* Нет приватных сайтов\\n\\n\\n## Как я могу создать сайт в Zeronet?\\n\\nЗавершите работу zeronet, если он запущен\\n\\n```bash\\n$ zeronet.py siteCreate\\n...\\n- Site private key (Приватный ключ сайта): 23DKQpzxhbVBrAtvLEc2uvk7DZweh4qL3fn3jpM3LgHDczMK2TtYUq\\n- Site address (Адрес сайта): 13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2\\n...\\n- Site created! (Сайт создан)\\n$ zeronet.py\\n...\\n```\\n\\nПоздравляем, вы закончили! Теперь каждый может получить доступ к вашему зайту используя\\n`http://localhost:43110/13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2`\\n\\nСледующие шаги: [ZeroNet Developer Documentation](https://zeronet.io/docs/site_development/getting_started/)\\n\\n\\n## Как я могу модифицировать Zeronet сайт?\\n\\n* Измените файлы расположенные в data/13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2 директории.\\n  Когда закончите с изменением:\\n\\n```bash\\n$ zeronet.py siteSign 13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2\\n- Signing site (Подпись сайта): 13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2...\\nPrivate key (Приватный ключ) (input hidden):\\n```\\n\\n* Введите секретный ключ, который вы получили при создании сайта, потом:\\n\\n```bash\\n$ zeronet.py sitePublish 13DNDkMUExRf9Xa9ogwPKqp7zyHFEqbhC2\\n...\\nSite:13DNDk..bhC2 Publishing to 3/10 peers...\\nSite:13DNDk..bhC2 Successfuly published to 3 peers\\n- Serving files....\\n```\\n\\n* Вот и всё! Вы успешно подписали и опубликовали свои изменения.\\n\\n\\n## Поддержите проект\\n\\n- Bitcoin: 1QDhxQ6PraUZa21ET5fYUCPgdrwBomnFgX\\n- Paypal: https://zeronet.io/docs/help_zeronet/donate/\\n\\n### Спонсоры\\n\\n* Улучшенная совместимость с MacOS / Safari стала возможной благодаря [BrowserStack.com](https://www.browserstack.com)\\n\\n#### Спасибо!\\n\\n* Больше информации, помощь, журнал изменений, zeronet сайты: https://www.reddit.com/r/zeronet/\\n* Приходите, пообщайтесь с нами: [#zeronet @ FreeNode](https://kiwiirc.com/client/irc.freenode.net/zeronet) или на [gitter](https://gitter.im/HelloZeroNet/ZeroNet)\\n* Email: hello@zeronet.io (PGP: CB9613AE)\\n'},\n",
       " {'repo': 'cryptean/bitcoinlib',\n",
       "  'language': 'C#',\n",
       "  'readme_contents': '\\ufeff# BitcoinLib\\n\\n**.NET Bitcoin & Altcoins library**\\n\\n## Features\\n\\n- Compatible with [Bitcoin Core](https://bitcoin.org/en/download) RPC API.\\n- Strongly-typed structures for complex RPC requests and responses.\\n- Implicit JSON casting for all RPC messages.\\n- Extended methods for every-day scenarios where the built-in methods fall short.\\n- Exposure of all [RPC API\\'s functionality](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list) as well as the extended methods through a single interface.\\n- Custom RPC exceptions.\\n- Supports all Bitcoin clones.\\n- Can operate on unlimited daemons with a single library reference.\\n- [Bitcoin](http://en.wikipedia.org/wiki/Bitcoin), [Litecoin](http://en.wikipedia.org/wiki/Litecoin), [Dogecoin](http://en.wikipedia.org/wiki/Dogecoin), SmartCash, Dash and other Altcoins included.\\n- Each coin instance can be fully parametrized at run-time and implement its own constants.\\n- Demo client included.\\n- Disconnected raw RPC connector included for quick\\'n\\'dirty debugging.\\n- Handles and relays RPC internal server errors along with their error code.\\n- Can work without a `.config` file.\\n- Fully compatible with [Mono](http://www.mono-project.com/).\\n- [Test Network (testnet)](https://bitcoin.org/en/developer-examples#testnet) and [Regression Test Mode (regtest)](https://bitcoin.org/en/developer-examples#regtest-mode) ready.\\n- Fully configurable.\\n\\n## Support\\n\\nPremium Support is available by our team of experts at: [support@cryptean.com](mailto:support@cryptean.com).\\n\\n## License\\n\\nSee [LICENSE](LICENSE).\\n\\n## NuGet packages\\n\\nBitcoinLib is available on NuGet:\\n\\n* [BitcoinLib](https://www.nuget.org/packages/BitcoinLib/)\\n\\n## Versioning\\n\\nFrom version 1.4.0, BitcoinLib follows [Semantic Versioning 2.0.0](http://semver.org/spec/v2.0.0.html).\\n\\n## Building from source\\n\\nTo build BitcoinLib from source, you will need either the\\n[.NET Core SDK or Visual Studio](https://www.microsoft.com/net/download/).\\n\\n### Building & running tests\\n\\nWith Visual Studio you can build BitcoinLib and run the tests\\nfrom inside the IDE, otherwise with the `dotnet` command-line\\ntool you can execute:\\n\\n```sh\\ndotnet build\\n```\\n\\n## Instructions for Bitcoin\\n\\n- Locate your `bitcoin.conf` file (in Windows it\\'s under: `%AppData%\\\\Roaming\\\\Bitcoin`, if it\\'s not there just go ahead and create it) and add these lines:\\n  ```\\n  rpcuser = MyRpcUsername\\n  rpcpassword = MyRpcPassword\\n  server=1\\n  txindex=1\\n  ```\\n- Edit the `app.config` file in the Console test client to best fit your needs. Make sure you also update the `bitcoin.conf` file when you alter the `Bitcoin_RpcUsername` and `Bitcoin_RpcPassword` parameters.\\n\\n## Instructions for Litecoin and other Bitcoin clones\\n\\n- Perform the same steps as those mentioned above for Bitcoin.\\n- Litecoin configuration file is: `litecoin.conf` under: `%AppData%\\\\Roaming\\\\Litecoin` and its daemon is: `litecoind`.\\n- Each coin can be initialized by its own interface specification:\\n  - `IBitcoinService BitcoinService = new BitcoinService();`\\n  - `ILitecoinService LitecoinService = new LitecoinService();`\\n- Any bitcoin clone can be adopted without any further installation steps with the use of the generic `ICryptocoinService`:\\n  - `ICryptocoinService cryptocoinService = new CryptocoinService(\"daemonUrl\", \"rpcUsername\", \"rpcPassword\", \"walletPassword\");`\\n- Use `(ICryptocoinService).Parameters` to fully configure each coin pointer at run-time.\\n\\n## Configuration\\n\\nSample configuration:\\n\\n```xml\\n\\ufeff<?xml version=\"1.0\" encoding=\"utf-8\"?>\\n<configuration>\\n  <appSettings>\\n    <!-- BitcoinLib settings start -->\\n\\n      <!-- Shared RPC settings start -->\\n      <add key=\"RpcRequestTimeoutInSeconds\" value=\"10\" />\\n      <!-- Shared RPC settings end -->\\n\\n      <!-- Bitcoin settings start -->\\n      <add key=\"Bitcoin_DaemonUrl\" value=\"http://localhost:8332\" />\\n      <add key=\"Bitcoin_DaemonUrl_Testnet\" value=\"http://localhost:18332\" />\\n      <add key=\"Bitcoin_WalletPassword\" value=\"MyWalletPassword\" />\\n      <add key=\"Bitcoin_RpcUsername\" value=\"MyRpcUsername\" />\\n      <add key=\"Bitcoin_RpcPassword\" value=\"MyRpcPassword\" />\\n      <!-- Bitcoin settings end -->\\n\\n    <!-- BitcoinLib settings end -->\\n  </appSettings>\\n</configuration>\\n```\\n\\n## Bitcoin Core resources\\n\\n* [Bitcoin Core releases](https://bitcoincore.org/en/releases/)\\n* [Bitcoin Core lifecycle schedule](https://bitcoincore.org/en/lifecycle/#schedule)\\n* [Bitcoin Core RPC documentation](https://bitcoincore.org/en/doc/)\\n'},\n",
       " {'repo': 'progranism/Open-Source-FPGA-Bitcoin-Miner',\n",
       "  'language': 'VHDL',\n",
       "  'readme_contents': \"Open-Source FPGA Bitcoin Miner\\n==============================================\\n\\n--------------------------------------------------------------------------------\\nCopyright (C) 2011 fpgaminer@bitcoin-mining.com\\n\\nSee LICENSE.txt\\n\\n\\nPurpose\\n-------\\n\\nTo promote the free and open development of an FPGA based Bitcoin mining solution.\\n\\nhttp://www.weusecoins.com/\\n\\nhttp://bitcoin.org/\\n\\n\\nProject Status\\n--------------\\n\\nProject is fully functional and allows mining of Bitcoins both in a Pool and Solo.\\nIt also supports Namecoins.\\n\\n**Current Performance:** 109 MHash/s\\n*On a Terasic DE2-115 Development Board*\\n\\n*Note: The included default configuration file, and source files, are built for\\n50 MHash/s performance (downclocked). This is meant to prevent damage to your valuable\\nchip if you don't provide an appropriate cooling solution.*\\n\\n\\nContributors\\n------------\\n\\nThese people have worked hard to enhance and promote the Open-Source FPGA Bitcoin Miner\\nproject:\\n*Not listed in any particular order*\\n\\n**teknohog**\\n1HkL2iLLQe3KJuNCgKPc8ViZs83NJyyQDM\\n\\n**OrphanedGland**\\n1PioyqqFWXbKryxysGqoq5XAu9MTRANCEP\\n\\n**udif**\\n\\n**TheSeven**\\n14Jc8vWq1mPv7vWnP5VquZZgpLEtzW2vja\\n\\n**makomk**\\n15XX7BhQcZFUg47S4VKyiLygPTHTs9234J\\n\\n**newMeat1**\\n1LbqTCA1cnpbbdKbXzZZfHYMe7teiczQc2\\n\\n\\nSupported Devices\\n------------------\\n\\nBoth Xilinx and Altera devices are currently supported. A binary configuration file and tools\\nare provided for the Terasic DE2-115 Development Board, so it is easy to get up and running\\nwith that board. For other devices, you can modify and compile the correct projects for your\\nspecific development board.\\n\\n\\nInstallation Instructions (for Terasic DE2-115)\\n-------------------------\\n\\n\\n### Required Equipment:\\n* DE2-115 Development Kit (this is *not* a DE2. It has a Cyclone IV EP4CE115.)\\n* USB Cable\\n* Windows PC (Linux is also supported, but not documented)\\n* Altera's Quartus II (installed on PC)\\n\\n\\n###Instructions:\\n\\n####Do These Once:\\n\\n1) *IMPORTANT*: Please remove the clear acrylic cover on your DE2-115 board. This will restrict\\nair flow and may cause the chip to overheat.\\n\\n2) Navigate to 'scripts/mine' and follow the instructions in 'config.example.tcl' (open in Notepad or other text editor)\\n\\n####Do these each time you want to run the miner:\\n\\n1) Connect the DE2-115 Development Kit to your PC through USB, connect its power, and turn it on.\\n\\n2) Ensure that the DE2-115's drivers have been installed successfully on your PC.\\nConsult the DE2-115 User Guide for more information on setting up the DE2-115.\\n\\n3) Navigate to 'scripts/program' and run 'program-fpga-board.bat'.\\n\\n4) Follow the instructions provided by the program-fpga-board script.\\nSelect the correct cable and programming file.\\nOnce programming has succeeded, the DE2-115 is now ready to mine!\\n\\n*Note: This script sometimes fails immediately upon execution. Please try running it again.*\\n\\n5) Run 'mine.bat'\\n\\n6) If working correctly, 'mine.bat' will leave a console window open where it reports hashing rate, estimated hashing rate and accepted/rejected share information.\\n\\n7) Profit!\\n\\n\\n####Notes:\\n* You need to re-program the DE2-115 every time it is powered off and on again. Repeat steps 1 through 7 for subsequent uses.\\n* Your PC needs to stay on and connected to the internet. It is acting like a controller for the FPGA,\\nfeeding it data and getting back valid hashes.\\n\\n\\nThank You!\\n--------------------\\n\\n--------------------\\n\\n\\n\\n```\\n-----BEGIN PGP SIGNED MESSAGE-----\\nHash: SHA1\\n\\nfpgaminer@bitcoin-mining.com\\nDonation Address: 1E1XgiJAzm1Wn7ZWuhkryzBoViBJ7CcRCQ\\n\\nDonations are most welcome! They will be used to buy more equipment. I'm currently trying to get\\nan ethernet module up and running so the miner can run all on its own.\\n-----BEGIN PGP SIGNATURE-----\\nVersion: GnuPG v1.4.11 (MingW32)\\n\\niQIcBAEBAgAGBQJN1dAzAAoJEFFoGj2A5YKRt/IP/3LaZlEWvdUpAxcs5ANS3fcA\\nNdKFiIycfnBKtmXjXiHQk4DZY+tbvuPPggzFHBA7k+3wV3WBOF2rjQiorODZff6q\\nxb6gSVINUXucv/+SDzqx8CtjMa17wzSayiczC03t+IICYs2/atdLAFvbr0LwdbqZ\\noBQRgYK4hD39fQzD8v/L26glh3va72ZibuO043uH/WMFgcQseTFHF7QPLJm0k0A/\\nnx5p0cTtqqSf4g9MQICnNU8MGVrXXOGZU4DeItbJjNcvsomzmibha+9jQ2K8XD8F\\nKzbdTK+YzvdzcDMaeOgs70SnVEFfUS1ykbdDC850M6qkRP79HBqH7Neq1Rld5ktj\\nMrd2hHC4NC0fgMD3hUbTjfIcCZOPwKYvp5oCLYYO1CqzV64Ag0o9qZDr8FS+9Npv\\nPEbWQpQuZqqtkhppVcCmOv4bl8XWTuQJEoxP8rWkJdfhkDUt5hwQsFrMQB7goXDc\\npJZu1wnWdzpgcDyNjkNDp6sqnJGzCgft7o3hPiZO79BZZRLtdRSMHa0RdJJK5zLv\\n8JqOJCJUFhVZHSKsHyGdJHppjKk/yZbBGLuJUTAfrMk5I/X5b/V9TGiWKoPN3zce\\nHdd5LQF5Z881wCgrnPz2dwR5oXMUcWqd//ZAs7Jcnvp6Bz5HWrFH5FBgpfg0K3c6\\nqBmd3GhQgxnFsBW62dAJ\\n=Lvja\\n-----END PGP SIGNATURE-----\\n```\\n\\n\\n\"},\n",
       " {'repo': 'bitcoin-sv/bitcoin-sv',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': \"Bitcoin SV\\n===========\\n\\nWhat is Bitcoin SV?\\n-------------------\\n\\n[Bitcoin SV (Satoshi Vision)](https://bitcoinsv.io/) is the original Bitcoin.  It restores the original Bitcoin \\nprotocol, will keep it stable, and allow it to massively scale.  Bitcoin SV will maintain the vision set out by Satoshi \\nNakamoto’s white paper in 2008.  This Github repository provides open-source software to enable use of Bitcoin SV.\\n\\nLicense\\n-------\\n\\nBitcoin SV is released under the terms of the Open BSV license. See [LICENSE](LICENSE) for more information.\\n\\nSecurity\\n--------\\nSecurity is core to our values, and we value the input of security researchers acting in good faith to help us maintain \\nhigh standards of security and privacy for our users and the Bitcoin SV blockchain.\\n\\nTo encourage ethical and responsible research into security vulnerabilities, the Bitcoin SV team, with support from \\nCoingeek Mining, has instituted a [Responsible Disclosure Policy](doc/rdp.md).\\n\\nDevelopment Process\\n-------------------\\n\\nThis Github repository contains the source code of releases.\\n\\nAt this early stage in Bitcoin SV's development, we are not accepting contributions to the project. We expect this to \\nchange in the future.\\n\\nContacting the Bitcoin SV Team\\n------------------------------\\n\\nIf you want to report a non-confidential issue with Bitcoin SV, please use the \\n[GitHub issue system](https://github.com/bitcoin-sv/bitcoin-sv/issues).\\n\\nIf you want to report a security vulnerability, please review the [Responsible Disclosure Policy](doc/rdp.md) and send\\ne-mail to <security@bitcoinsv.io>.\\n\\nFor any other questions or issues, please send e-mail to <support@bitcoinsv.io>.\\n\"},\n",
       " {'repo': 'oleganza/CoreBitcoin',\n",
       "  'language': 'C',\n",
       "  'readme_contents': 'CoreBitcoin\\n===========\\n\\nCoreBitcoin implements Bitcoin protocol in Objective-C and provides many additional APIs to make great apps.\\n\\nCoreBitcoin deliberately implements as much as possible directly in Objective-C with limited dependency on OpenSSL. This gives everyone an opportunity to learn Bitcoin on a clean codebase and enables all Mac and iOS developers to extend and improve Bitcoin protocol.\\n\\nDo not confuse this with \"Bitcoin Core\" (previously known as BitcoinQT or \"Satoshi client\") — the CoreBitcoin is stylized after Apple frameworks (like CoreAnimation and CoreFoundation), and was named this way in 2013, while Bitcoin-QT was renamed into Bitcoin Core in 2014.\\n\\n\\nProjects using CoreBitcoin\\n--------------------------\\n\\n- [Chain-iOS SDK](https://github.com/chain-engineering/chain-ios) (written by Oleg Andreev)\\n- [Mycelium iOS Wallet](https://itunes.apple.com/us/app/mycelium-bitcoin-wallet/id943912290) (written by Oleg Andreev)\\n- [bitWallet](https://itunes.apple.com/us/app/bitwallet-bitcoin-wallet/id777634714)\\n- [Yallet](https://www.yallet.com)\\n- [BitStore](http://bitstoreapp.com)\\n- [ArcBit](http://arcbit.io)\\n\\nFeatures\\n--------\\n\\nSee also [Release Notes](ReleaseNotes.md).\\n\\n- Encoding/decoding addresses: P2PK, P2PKH, P2SH, WIF format ([BTCAddress](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCAddress.h)).\\n- Transaction building blocks: inputs, outputs, scripts ([BTCTransaction](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCTransaction.h), [BTCScript](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCScript.h)).\\n- EC keys and signatures ([BTCKey](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCKey.h)).\\n- High-level convenient and safe transaction builder ([BTCTransactionBuilder](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCTransactionBuilder.h)).\\n- Parsing and composing bitcoin URLs and payment requests ([BTCBitcoinURL](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCBitcoinURL.h)).\\n- QR Code generator and scanner in a unified API (iOS only for now; [BTCQRCode](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCQRCode.h)).\\n- BIP32, BIP44 hierarchical deterministic wallets ([BTCKeychain](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCKeychain.h)).\\n- BIP39 implementation ([BTCMnemonic](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCMnemonic.h)).\\n- BIP70 implementation ([BTCPaymentProtocol](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCPaymentProtocol.h)).\\n- [Automatic Encrypted Wallet Backup](https://github.com/oleganza/bitcoin-papers/blob/master/AutomaticEncryptedWalletBackups.md) scheme ([BTCEncryptedBackup](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCEncryptedBackup.h)).\\n\\nCurrency tools\\n--------------\\n\\n- Bitcoin currency formatter with support for BTC, mBTC, bits ([BTCNumberFormatter](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCNumberFormatter.h)).\\n- Currency converter (not linked to any exchange) with support for various methods to calculate exchange rate ([BTCCurrencyConverter](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCCurrencyConverter.h)).\\n- Various price sources and abstract interface for adding new ones ([BTCPriceSource](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCPriceSource.h) with support for Winkdex, Coindesk, Coinbase, Paymium).\\n\\nAdvanced features\\n-----------------\\n\\n- Deterministic [RFC6979](https://tools.ietf.org/html/rfc6979#section-3.2)-compliant ECDSA signatures.\\n- Script evaluation machine to actually validate individual transactions ([BTCScriptMachine](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCScriptMachine.h)).\\n- Blind signatures implementation ([BTCBlindSignature](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCBlindSignature.h)).\\n- Math on elliptic curves: big numbers, curve points, conversion between keys, numbers and points ([BTCBigNumber](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCBigNumber.h), [BTCCurvePoint](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCCurvePoint.h)).\\n- Various cryptographic primitives like hash functions and AES encryption (see [BTCData.h](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCData.h)).\\n\\n\\nOn the roadmap\\n--------------\\n\\nSee [all todo items](https://github.com/oleganza/CoreBitcoin/issues).\\n\\n- Complete support for blocks and block headers.\\n- SPV mode and P2P communication with other nodes.\\n- Full blockchain verification procedure and storage.\\n- Importing BitcoinQT, Electrum and Blockchain.info wallets.\\n- Support for [libsecp256k1](https://github.com/bitcoin/secp256k1) in addition to OpenSSL.\\n- Eventual support for libconsensus as it gets more mature and feature-complete.\\n\\nThe goal is to implement everything useful related to Bitcoin and organize it nicely in a single powerful library. Pull requests are welcome.\\n\\n\\nStarting points\\n---------------\\n\\nTo encode/decode addresses see [BTCAddress](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCAddress.h).\\n\\nTo perform cryptographic operations, use [BTCKey](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCKey.h), [BTCBigNumber](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCBigNumber.h) and [BTCCurvePoint](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCCurvePoint). [BTCKeychain](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCKeychain.h) implements BIP32 (hierarchical deterministic wallet).\\n\\nTo fetch unspent coins and broadcast transactions use one of the 3rd party APIs: [BTCBlockchainInfo](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCBlockchainInfo.h) (blockchain.info) or [Chain-iOS](https://github.com/chain-engineering/chain-ios) (recommended).\\n\\nFor full wallet workflow see [BTCTransaction+Tests.m](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCTransaction+Tests.m) (fetch unspent outputs, compose a transaction, sign inputs, verify and broadcast).\\n\\nFor multisignature scripts usage see [BTCScript+Tests.m](https://github.com/oleganza/CoreBitcoin/blob/master/CoreBitcoin/BTCScript+Tests.m): compose and unlock multisig output.\\n\\nAll other files with `+Tests` in their name are worth checking out as they contain useful sample code.\\n\\n\\nUsing CoreBitcoin CocoaPod (recommended)\\n----------------------------------------\\n\\nAdd this to your Podfile:\\n\\n    pod \\'CoreBitcoin\\', :podspec => \\'https://raw.github.com/oleganza/CoreBitcoin/master/CoreBitcoin.podspec\\'\\n\\nRun in Terminal:\\n\\n    $ pod install\\n\\nInclude headers:\\n\\n\\t#import <CoreBitcoin/CoreBitcoin.h>\\n\\nIf you\\'d like to use categories, include different header:\\n\\n\\t#import <CoreBitcoin/CoreBitcoin+Categories.h>\\n\\n\\nUsing CoreBitcoin.framework\\n---------------------------\\n\\nClone this repository and build all libraries:\\n\\n\\t$ ./update_openssl.sh\\n\\t$ ./build_libraries.sh\\n\\nCopy iOS or OS X framework located in binaries/iOS or binaries/OSX to your project.\\n\\nInclude headers:\\n\\n\\t#import <CoreBitcoin/CoreBitcoin.h>\\n\\t\\nThere are also raw universal libraries (.a) with headers located in binaries/include, if you happen to need them for some reason. Frameworks and binary libraries have OpenSSL built-in. If you have different version of OpenSSL in your project, consider using CocoaPods or raw sources of CoreBitcoin.\\n\\n\\nSwift\\n-----\\n\\nWe love Swift and design the code to be compatible with Swift. That means using modern enums, favoring initializers over factory methods, avoiding obscure C features etc. You are welcome to try using CoreBitcoin from Swift, please file bugs if you have problems.\\n\\nSwift is awesome to write crypto in it (due to explicit optionals, generics and first-class structs) and we would love to rewrite the entire CoreBitcoin and even relevant portions of OpenSSL in it. Unfortunately, for a year or two it\\'s just out of the question due to instability. And then, using Swift-only features on the API level would mean that Objective-C code wouldn\\'t be able to use CoreBitcoin. Given that, in the medium term we will focus solely on Objective-C implementation compatible with Swift. When everyone jumps exclusively on Swift, we\\'ll make a complete rewrite.\\n\\n\\nContribute\\n----------\\n\\nFeel free to open issues, drop us pull requests or contact us to discuss how to do things.\\n\\nFollow existing code style and use 4 spaces instead of tabs. Methods have opening braces on a new line. There\\'s no line width limit.\\n\\nEmail: [oleganza@gmail.com](mailto:oleganza@gmail.com)\\n\\nTwitter: [@oleganza](http://twitter.com/oleganza)\\n\\nTo publish on CocoaPods:\\n\\n    $ pod trunk push --verbose --use-libraries\\n\\n\\nLicense\\n-------\\n\\nReleased under [WTFPL](http://www.wtfpl.net) (except for OpenSSL). Have a nice day.\\n\\n'},\n",
       " {'repo': 'janoside/btc-rpc-explorer',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# BTC RPC Explorer\\n\\n## Self-Hosted Bitcoin explorer for everyone running [Bitcoin Core](https://github.com/bitcoin/bitcoin).\\n\\n[![npm version][npm-ver-img]][npm-ver-url] [![NPM downloads][npm-dl-alltime-img]][npm-dl-url]\\n\\n\\n---\\n\\n\\n![homepage](./public/img/screenshots/homepage.png)\\n\\n\\n\\nThis is a self-hosted explorer for the Bitcoin blockchain, driven by RPC calls to your own [Bitcoin](https://github.com/bitcoin/bitcoin) node. It is easy to run and can be connected to other tools (like Electrum servers) to achieve a full-featured explorer.\\n\\nWhatever reasons you may have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it\\'s valuable to appreciate the *fullness* of your node. With this explorer, you can explore not just the blockchain database, but also explore all of the functional capabilities of your own node.\\n\\nLive demos:\\n\\n* [BitcoinExplorer.org](https://bitcoinexplorer.org) / [testnet](https://testnet.bitcoinexplorer.org) / [signet](https://signet.bitcoinexplorer.org)\\n\\n\\n# Features\\n\\n* Network Summary dashboard\\n* View details of blocks, transactions, and addresses\\n* Analysis tools for viewing stats on blocks, transactions, and miner activity\\n* JSON REST API\\n* See raw JSON content from bitcoind used to generate most pages\\n* Search by transaction ID, block hash/height, and address\\n* Optional transaction history for addresses by querying from Electrum-protocol servers (e.g. Electrs, ElectrumX), blockchain.com, blockchair.com, or blockcypher.com\\n* Mempool summary, with fee, size, and age breakdowns\\n* RPC command browser and terminal\\n\\n\\n# Changelog / Release notes\\n\\nSee [CHANGELOG.md](/CHANGELOG.md).\\n\\n\\n# Getting started\\n\\n## Prerequisites\\n\\n1. Install `Bitcoin Core` - [instructions](https://bitcoin.org/en/full-node). Ensure that `Bitcoin Core`\\'s\\' RPC server is enabled (`server=1`).\\n2. Allow `Bitcoin Core` to synchronize with the Bitcoin network (you *can* use this tool while sychronizing, but some pages may fail).\\n3. Install Node.js (12.9+ required, 16+ recommended).\\n\\n### Note about pruning and indexing configurations\\n\\nThis tool is designed to work best with full transaction indexing enabled (`txindex=1`) and pruning **disabled**. \\nHowever, if you\\'re running Bitcoin Core v0.21+ you can run *without* `txindex` enabled and/or *with* `pruning` enabled and this tool will continue to function, but some data will be incomplete or missing. Also note that such Bitcoin Core configurations receive less thorough testing.\\n\\nIn particular, with `pruning` enabled and/or `txindex` disabled, the following functionality is altered:\\n\\n* You will only be able to search for mempool, recently confirmed, and wallet transactions by their txid. Searching for non-wallet transactions that were confirmed over 3 blocks ago is only possible if you provide the confirmed block height in addition to the txid.\\n* Pruned blocks will display basic header information, without the list of transactions. Transactions in pruned blocks will not be available, unless they\\'re wallet-related. Block stats will only work for unpruned blocks.\\n* The address and amount of previous transaction outputs will not be shown, only the txid:vout.\\n* The mining fee will only be available for unconfirmed transactions.\\n\\n\\n## Install / Run\\n\\nIf you\\'re running on mainnet with the default datadir and port, the default configuration should *Just Work*. Otherwise, see the **Configuration** section below.\\n\\n#### Install via `npm`:\\n\\n*Note: npm v7+ is required*\\n\\n```bash\\nnpm install -g btc-rpc-explorer\\nbtc-rpc-explorer\\n```\\n\\n#### Run from source:\\n\\n1. `git clone https://github.com/janoside/btc-rpc-explorer`\\n2. `cd btc-rpc-explorer`\\n3. `npm install`\\n4. `npm start`\\n\\n\\n#### Install via AUR Arch Linux:\\n\\n###### Note: The below AUR package was created and is maintained by [@dougEfresh](https://github.com/dougEfresh). The details and history of the package can be seen [here](https://aur.archlinux.org/packages/btc-rpc-explorer/).\\n\\n1. `git clone https://aur.archlinux.org/btc-rpc-explorer.git`\\n2. `cd btc-rpc-explorer`\\n3. `makepkg -csi`\\n4. `systemctl enable --now btc-rpc-explorer`\\n\\n\\n\\nAfter a default installation+startup using any of the above methods, the app can be viewed at [http://127.0.0.1:3002/](http://127.0.0.1:3002/)\\n\\n\\n## Configuration\\n\\nConfiguration options may be set via environment variables or CLI arguments.\\n\\n#### Configuration with environment variables\\n\\nTo configure with environment variables, you need to create one of the 2 following files and enter values in it:\\n\\n1. `~/.config/btc-rpc-explorer.env`\\n2. `.env` in the working directory for btc-rpc-explorer\\n\\nIn either case, refer to [.env-sample](.env-sample) for a list of the options and formatting details.\\n\\n#### Configuration with CLI args\\n\\nFor configuring with CLI arguments, run `btc-rpc-explorer --help` for the full list of options. An example execution is:\\n\\n```bash\\nbtc-rpc-explorer --port 8080 --bitcoind-port 18443 --bitcoind-cookie ~/.bitcoin/regtest/.cookie\\n```\\n\\n#### Demo site settings\\n\\nTo match the features visible on the demo site at [BitcoinExplorer.org](https://bitcoinexplorer.org) you\\'ll need to set the following non-default configuration values:\\n\\n    BTCEXP_DEMO=true \\t\\t# enables some demo/informational aspects of the site\\n    BTCEXP_NO_RATES=false\\t\\t# enables querying of exchange rate data\\n    BTCEXP_SLOW_DEVICE_MODE=false\\t# enables resource-intensive tasks (UTXO set query, 24hr volume querying) that are inappropriate for \"slow\" devices\\n    BTCEXP_ADDRESS_API=electrum \\t# use electrum-protocol servers for address lookups\\n    BTCEXP_ELECTRUM_SERVERS=tcp://your-electrum-protocol-server-host:50001\\t\\t# address(es) for my electrum-protocol server(s)\\n    BTCEXP_IPSTACK_APIKEY=your-api-key\\t\\t# enable peer ip geo-location\\n    BTCEXP_MAPBOX_APIKEY=your-api-key\\t\\t# enable map of peer locations\\n\\n#### SSO authentication\\n\\nYou can configure SSO authentication similar to what ThunderHub and RTL provide.\\nTo enable it, make sure `BTCEXP_BASIC_AUTH_PASSWORD` is **not** set and set `BTCEXP_SSO_TOKEN_FILE` to point to a file write-accessible by btc-rpc-explorer.\\nThen to access btc-rpc-explorer, your SSO provider needs to read the token from this file and set it in URL parameter `token`.\\nFor security reasons the token changes with each login, so the SSO provider needs to read it each time!\\n\\nAfter successful access with the token, a cookie is set for authentication, so you don\\'t need to worry about it anymore.\\nTo improve user experience you can set `BTCEXP_SSO_LOGIN_REDIRECT_URL` to the URL of your SSO provider.\\nThis will cause users to be redirected to your login page if needed.\\n\\n## Run via Docker\\n\\n1. `docker build -t btc-rpc-explorer .`\\n2. `docker run -it -p 3002:3002 -e BTCEXP_HOST=0.0.0.0 btc-rpc-explorer`\\n\\n\\n## Reverse proxy with HTTPS\\n\\nSee [instructions here](docs/nginx-reverse-proxy.md) for using nginx+certbot (letsencrypt) for an HTTPS-accessible, reverse-proxied site.\\n\\n\\n# Support\\n\\nIf you get value from this project, please consider supporting my work with a donation. All donations are truly appreciated.\\n\\nDonate via BTC Pay Server:\\n\\n* [https://donate.bitcoinexplorer.org](https://donate.bitcoinexplorer.org)\\n\\nOr, via a lightning address:\\n\\nthanks@donate.btc21.org\\n\\n\\n[npm-ver-img]: https://img.shields.io/npm/v/btc-rpc-explorer.svg?style=flat\\n[npm-ver-url]: https://www.npmjs.com/package/btc-rpc-explorer\\n[npm-dl-img]: http://img.shields.io/npm/dm/btc-rpc-explorer.svg?style=flat\\n[npm-dl-url]: https://npmcharts.com/compare/btc-rpc-explorer?minimal=true\\n\\n[npm-dl-weekly-img]: https://badgen.net/npm/dw/btc-rpc-explorer?icon=npm&cache=300\\n[npm-dl-monthly-img]: https://badgen.net/npm/dm/btc-rpc-explorer?icon=npm&cache=300\\n[npm-dl-yearly-img]: https://badgen.net/npm/dy/btc-rpc-explorer?icon=npm&cache=300\\n[npm-dl-alltime-img]: https://badgen.net/npm/dt/btc-rpc-explorer?icon=npm&cache=300&label=total%20downloads\\n\\n'},\n",
       " {'repo': 'm0mchil/poclbm',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': \"Usage: poclbm.py [OPTION]... SERVER[#tag]...\\nSERVER is one or more [http[s]|stratum://]user:pass@host:port          (required)\\n[#tag] is a per SERVER user friendly name displayed in stats (optional)\\n\\nOptions:\\n  --version             show program's version number and exit\\n  -h, --help            show this help message and exit\\n  --verbose             verbose output, suitable for redirection to log file\\n  -q, --quiet           suppress all output except hash rate display\\n  --proxy=PROXY         specify as\\n                        [[socks4|socks5|http://]user:pass@]host:port (default\\n                        proto is socks5)\\n\\n  Miner Options:\\n    -r RATE, --rate=RATE\\n                        hash rate display interval in seconds, default=1 (60\\n                        with --verbose)\\n    -e ESTIMATE, --estimate=ESTIMATE\\n                        estimated rate time window in seconds, default 900 (15\\n                        minutes)\\n    -a ASKRATE, --askrate=ASKRATE\\n                        how many seconds between getwork requests, default 5,\\n                        max 10\\n    -t TOLERANCE, --tolerance=TOLERANCE\\n                        use fallback pool only after N consecutive connection\\n                        errors, default 2\\n    -b FAILBACK, --failback=FAILBACK\\n                        attempt to fail back to the primary pool after N\\n                        seconds, default 60\\n    --cutoff_temp=CUTOFF_TEMP\\n                        (requires github.com/mjmvisser/adl3) temperature at\\n                        which to skip kernel execution, in C, default=95\\n    --cutoff_interval=CUTOFF_INTERVAL\\n                        (requires adl3) how long to not execute calculations\\n                        if CUTOFF_TEMP is reached, in seconds, default=0.01\\n    --no-server-failbacks\\n                        disable using failback hosts provided by server\\n\\n  Kernel Options:\\n    -p PLATFORM, --platform=PLATFORM\\n                        use platform by id\\n    -d DEVICE, --device=DEVICE\\n                        use device by id, by default asks for device\\n    -w WORKSIZE, --worksize=WORKSIZE\\n                        work group size, default is maximum returned by opencl\\n    -f FRAMES, --frames=FRAMES\\n                        will try to bring single kernel execution to 1/frames\\n                        seconds, default=30, increase this for less desktop\\n                        lag\\n    -s FRAMESLEEP, --sleep=FRAMESLEEP\\n                        sleep per frame in seconds, default 0\\n    -v, --vectors       use vectors\"},\n",
       " {'repo': 'BlockchainCommons/Learning-Bitcoin-from-the-Command-Line',\n",
       "  'language': 'Jupyter Notebook',\n",
       "  'readme_contents': '# Learning Bitcoin from the Command Line 2.2.0\\n### _by Christopher Allen and Shannon Appelcline_\\n\\n![](https://www.blockchaincommons.com/images/projects/lbtc-screen.png)\\n\\nLearning Bitcoin from the Command Line is a tutorial for working with Bitcoin (and Lightning) that teaches direct interaction with the servers themselves, as the most robust and secure way to begin cryptocurrency work.\\n\\n> NOTE: This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for use.\\n\\n_This tutorial assumes that you have some minimal background of how to use the command line interface. If not, there are many tutorials available, and I have one for Mac users at https://github.com/ChristopherA/intro-mac-command-line._\\n\\n## Translations\\n\\n* [Portuguese](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/portuguese-translation/pt/README.md) — v2.0.1 translation\\n* [Spanish](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/spanish-translation/es/README.md) - v2.0.1 translation\\n\\nIf you\\'d like to make your own translation, please see [Contributing](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/master#contributing), below.\\n\\n## Table of Contents\\n\\n### PART ONE: PREPARING FOR BITCOIN\\n\\n**Status:** Finished. Updated for 0.20.\\n\\n* [1.0: Introduction to Programming with Bitcoin Core and Lightning](01_0_Introduction.md)\\n    * [Interlude: Introducing Bitcoin](01_1_Introducing_Bitcoin.md)\\n* [2.0: Setting Up a Bitcoin-Core VPS](02_0_Setting_Up_a_Bitcoin-Core_VPS.md)\\n  * [2.1: Setting Up a Bitcoin-Core VPS with Bitcoin Standup](02_1_Setting_Up_a_Bitcoin-Core_VPS_with_StackScript.md)\\n  * [2.2: Setting Up a Bitcoin-Core Machine via Other Means](02_2_Setting_Up_Bitcoin_Core_Other.md)\\n\\n### PART TWO: USING BITCOIN-CLI\\n\\n**Status:** Finished. Updated for 0.20.\\n\\n* [3.0: Understanding Your Bitcoin Setup](03_0_Understanding_Your_Bitcoin_Setup.md)\\n  * [3.1: Verifying Your Bitcoin Setup](03_1_Verifying_Your_Bitcoin_Setup.md)\\n  * [3.2: Knowing Your Bitcoin Setup](03_2_Knowing_Your_Bitcoin_Setup.md)\\n  * [3.3: Setting Up Your Wallet](03_3_Setting_Up_Your_Wallet.md)\\n    * [Interlude: Using Command-Line Variables](03_3__Interlude_Using_Command-Line_Variables.md)\\n  * [3.4: Receiving a Transaction](03_4_Receiving_a_Transaction.md)\\n  * [3.5: Understanding the Descriptor](03_5_Understanding_the_Descriptor.md)\\n* [4.0: Sending Bitcoin Transactions](04_0_Sending_Bitcoin_Transactions.md)\\n  * [4.1: Sending Coins the Easy Way](04_1_Sending_Coins_The_Easy_Way.md)\\n  * [4.2: Creating a Raw Transaction](04_2_Creating_a_Raw_Transaction.md)\\n     * [Interlude: Using JQ](04_2__Interlude_Using_JQ.md)\\n  * [4.3: Creating a Raw Transaction with Named Arguments](04_3_Creating_a_Raw_Transaction_with_Named_Arguments.md)\\n  * [4.4: Sending Coins with Raw Transactions](04_4_Sending_Coins_with_a_Raw_Transaction.md)\\n     * [Interlude: Using Curl](04_4__Interlude_Using_Curl.md)\\n  * [4.5: Sending Coins with Automated Raw Transactions](04_5_Sending_Coins_with_Automated_Raw_Transactions.md)\\n  * [4.6: Creating a Segwit Transaction](04_6_Creating_a_Segwit_Transaction.md)\\n* [5.0: Controlling Bitcoin Transactions](05_0_Controlling_Bitcoin_Transactions.md)\\n  * [5.1 Watching for Stuck Transactions](05_1_Watching_for_Stuck_Transactions.md)\\n  * [5.2: Resending a Transaction with RBF](05_2_Resending_a_Transaction_with_RBF.md)\\n  * [5.3: Funding a Transaction with CPFP](05_3_Funding_a_Transaction_with_CPFP.md)\\n* [6.0: Expanding Bitcoin Transactions with Multisigs](06_0_Expanding_Bitcoin_Transactions_Multisigs.md)\\n  * [6.1: Sending a Transaction with a Multisig](06_1_Sending_a_Transaction_to_a_Multisig.md)\\n  * [6.2: Spending a Transaction with a Multisig](06_2_Spending_a_Transaction_to_a_Multisig.md)\\n  * [6.3: Sending & Spending an Automated Multisig](06_3_Sending_an_Automated_Multisig.md)\\n* [7.0: Expanding Bitcoin Transactions with PSBTs](07_0_Expanding_Bitcoin_Transactions_PSBTs.md)\\n  * [7.1: Creating a Partially Signed Bitcoin Transaction](07_1_Creating_a_Partially_Signed_Bitcoin_Transaction.md)\\n  * [7.2: Using a Partially Signed Bitcoin Transaction](07_2_Using_a_Partially_Signed_Bitcoin_Transaction.md)\\n  * [7.3: Integrating with Hardware Wallets](07_3_Integrating_with_Hardware_Wallets.md)\\n* [8.0: Expanding Bitcoin Transactions in Other Ways](08_0_Expanding_Bitcoin_Transactions_Other.md)\\n  * [8.1: Sending a Transaction with a Locktime](08_1_Sending_a_Transaction_with_a_Locktime.md)\\n  * [8.2: Sending a Transaction with Data](08_2_Sending_a_Transaction_with_Data.md)\\n\\n### PART THREE: BITCOIN SCRIPTING\\n\\n**Status:** Finished. Updated for 0.20 and btcdeb.\\n\\n* [9.0: Introducing Bitcoin Scripts](09_0_Introducing_Bitcoin_Scripts.md)\\n  * [9.1: Understanding the Foundation of Transactions](09_1_Understanding_the_Foundation_of_Transactions.md)\\n  * [9.2: Running a Bitcoin Script](09_2_Running_a_Bitcoin_Script.md)\\n  * [9.3: Testing a Bitcoin Script](09_3_Testing_a_Bitcoin_Script.md)\\n  * [9.4: Scripting a P2PKH](09_4_Scripting_a_P2PKH.md)\\n  * [9.5: Scripting a P2WPKH](09_5_Scripting_a_P2WPKH.md)\\n* [10.0: Embedding Bitcoin Scripts in P2SH Transactions](10_0_Embedding_Bitcoin_Scripts_in_P2SH_Transactions.md)\\n  * [10.1: Understanding the Foundation of P2SH](10_1_Understanding_the_Foundation_of_P2SH.md)\\n  * [10.2: Building the Structure of P2SH](10_2_Building_the_Structure_of_P2SH.md)\\n  * [10.3: Running a Bitcoin Script with P2SH](10_3_Running_a_Bitcoin_Script_with_P2SH.md)\\n  * [10.4: Scripting a Multisig](10_4_Scripting_a_Multisig.md)\\n  * [10.5: Scripting a Segwit Script](10_5_Scripting_a_Segwit_Script.md)\\n  * [10.6: Spending a P2SH Transaction](10_6_Spending_a_P2SH_Transaction.md)\\n* [11.0: Empowering Timelock with Bitcoin Scripts](11_0_Empowering_Timelock_with_Bitcoin_Scripts.md)\\n  * [11.1: Understanding Timelock Options](11_1_Understanding_Timelock_Options.md)\\n  * [11.2: Using CLTV in Scripts](11_2_Using_CLTV_in_Scripts.md)\\n  * [11.3: Using CSV in Scripts](11_3_Using_CSV_in_Scripts.md)\\n* [12.0: Expanding Bitcoin Scripts](12_0_Expanding_Bitcoin_Scripts.md)\\n  * [12.1: Using Script Conditionals](12_1_Using_Script_Conditionals.md)\\n  * [12.2: Using Other Script Commands](12_2_Using_Other_Script_Commands.md)\\n* [13.0: Designing Real Bitcoin Scripts](13_0_Designing_Real_Bitcoin_Scripts.md)\\n  * [13.1: Writing Puzzles Scripts](13_1_Writing_Puzzle_Scripts.md)\\n  * [13.2: Writing Complex Multisig Scripts](13_2_Writing_Complex_Multisig_Scripts.md)\\n  * [13.3: Empowering Bitcoin with Scripts](13_3_Empowering_Bitcoin_with_Scripts.md)\\n\\n### PART FOUR: PRIVACY\\n\\n**Status:** Finished.\\n\\n* [14.0: Using Tor](14_0_Using_Tor.md)\\n  * [14.1: Verifying Your Tor Setup](14_1_Verifying_Your_Tor_Setup.md)\\n  * [14.2: Changing Your Bitcoin Hidden Services](14_2_Changing_Your_Bitcoin_Hidden_Services.md)\\n  * [14.3: Adding SSH Hidden Services](14_3_Adding_SSH_Hidden_Services.md)\\n\\n* [15.0: Using i2p](15_0_Using_i2p.md)\\n  * [15.1: Bitcoin Core as an I2P (Invisible Internet Project) service](15_1_i2p_service.md)\\n\\n### PART FIVE: PROGRAMMING WITH RPC\\n\\n**Status:** Finished.\\n\\n* [16.0: Talking to Bitcoind with C](16_0_Talking_to_Bitcoind.md)\\n  * [16.1: Accessing Bitcoind in C with RPC Libraries](16_1_Accessing_Bitcoind_with_C.md)\\n  * [16.2: Programming Bitcoind in C with RPC Libraries](16_2_Programming_Bitcoind_with_C.md)\\n  * [16.3: Receiving Notifications in C with ZMQ Libraries](16_3_Receiving_Bitcoind_Notifications_with_C.md)\\n* [17.0: Programming Bitcoin with Libwally](17_0_Programming_with_Libwally.md)\\n   * [17.1: Setting Up Libwally](17_1_Setting_Up_Libwally.md)\\n   * [17.2: Using BIP39 in Libwally](17_2_Using_BIP39_in_Libwally.md)\\n   * [17.3: Using BIP32 in Libwally](17_3_Using_BIP32_in_Libwally.md)\\n   * [17.4: Using PSBTs in Libwally](17_4_Using_PSBTs_in_Libwally.md)\\n   * [17.5: Using Scripts in Libwally](17_5_Using_Scripts_in_Libwally.md)\\n   * [17.6: Using Other Functions in Libwally](17_6_Using_Other_Functions_in_Libwally.md)\\n   * [17.7: Integrating Libwally and Bitcoin-CLI](17_7_Integrating_Libwally_and_Bitcoin-CLI.md)\\n* [18.0: Talking to Bitcoind with Other Languages](18_0_Talking_to_Bitcoind_Other.md)\\n  * [18.1: Accessing Bitcoind with Go](18_1_Accessing_Bitcoind_with_Go.md)\\n  * [18.2: Accessing Bitcoind with Java](18_2_Accessing_Bitcoind_with_Java.md)\\n  * [18.3: Accessing Bitcoind with Node JS](18_3_Accessing_Bitcoind_with_NodeJS.md)\\n  * [18.4: Accessing Bitcoind with Python](18_4_Accessing_Bitcoind_with_Python.md)\\n  * [18.5: Accessing Bitcoind with Rust](18_5_Accessing_Bitcoind_with_Rust.md)\\n  * [18.6: Accessing Bitcoind with Swift](18_6_Accessing_Bitcoind_with_Swift.md)\\n\\n### PART SIX: USING LIGHTNING-CLI\\n\\n**Status:** Finished.\\n\\n* [19.0: Understanding Your Lightning Setup](19_0_Understanding_Your_Lightning_Setup.md)\\n  * [19.1: Verifying Your c-lightning Setup](19_1_Verifying_Your_Lightning_Setup.md)\\n  * [19.2: Knowing Your c-lightning Setup](19_2_Knowing_Your_lightning_Setup.md)\\n     * [Interlude: Accessing a Second Lightning Node](19_2__Interlude_Accessing_a_Second_Lightning_Node.md)\\n  * [19.3: Creating a Lightning Channel](19_3_Setting_Up_a_Channel.md)\\n* [20.0: Using Lightning](20_0_Using_Lightning.md)\\n  * [20.1: Generating a Payment Request](20_1_Generate_a_Payment_Request.md)\\n  * [20.2: Paying an Invoice](20_2_Paying_a_Invoice.md)\\n  * [20.3: Closing a Lighnting Channel]((20_3_Closing_a_Channel.md))\\n  * [20.4: Expanding the Lightning Network](20_4_Lightning_Network_Review.md)\\n\\n### APPENDICES\\n\\n**Status:** Finished.\\n\\n* [Appendices](A0_Appendices.md)\\n  * [Appendix I: Understanding Bitcoin Standup](A1_0_Understanding_Bitcoin_Standup.md)\\n  * [Appendix II: Compiling Bitcoin from Source](A2_0_Compiling_Bitcoin_from_Source.md)\\n  * [Appendix III: Using Bitcoin Regtest](A3_0_Using_Bitcoin_Regtest.md)\\n\\n## Status - Beta\\n\\nv2.1.0 of **Learning Bitcoin from the Command Line** is feature complete and has undergone full editing and integration. It is ready for learning\\n\\nWe are also tentatively considering what we could include in a [v3.0](TODO-30.md) of the course. If you\\'d like to support work of that sort, become a [GitHub Sponsor](https://github.com/sponsors/BlockchainCommons) or support us at our [BTCPay Server](https://btcpay.blockchaincommons.com/), and let us know that **Learning Bitcoin** was the reason why.\\n### Version History\\n\\n#### 2.2.0 (November 17, 2021)\\n\\n* [Portuguese translation](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/master/pt)\\n* [Spanish translation](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/tree/master/es)\\n\\n#### 2.1.0 (October 12, 2021)\\n\\n* New chapter 15  (i2p).\\n* Added fixes to wallet usage from 0.21\\n* Updated install to new Bitcoin Scripts for 22.0\\n* Incorporated numerous fixes revealed by first translation projects\\n\\n#### 2.0.1 (June 15, 2021)\\n\\n* Numerous small patches following 2.0\\n* Intended as baseline for translations (2.2.0), but 2.1.0 material on i2p slipped in\\n\\n#### 2.0.0 (November 3, 2020)\\n\\n* Second major release of Learning Bitcoin\\n* Added material on Segwit, Tor, hardware wallets, lightning, regtest\\n* Completely previous unfinished work on programming using a variety of languages\\n\\n#### 1.0.0 (pre-2020)\\n\\n* Original, extensive but incomplete version\\n* Contained comprehensive sections on setup, bitcoin-cli, and scripting\\n\\n## Origin, Authors, Copyright & Licenses\\n\\nUnless otherwise noted (either in this [/README.md](./README.md) or in the file\\'s header comments) the contents of this repository are Copyright © 2020 by Blockchain Commons, LLC, and are licensed under  [CC-BY](./LICENSE-CC-BY-4.0.md).\\n\\n## Financial Support\\n\\n*Learning Bitcoin from the Command Line* is a project of [Blockchain Commons](https://www.blockchaincommons.com/). We are proudly a \"not-for-profit\" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.\\n\\nTo financially support further development of *Learning Bitcoin from the Command Line* and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a [GitHub Sponsor](https://github.com/sponsors/BlockchainCommons). You can also support Blockchain Commons with bitcoins at our [BTCPay Server](https://btcpay.blockchaincommons.com/).\\n\\n## Contributing\\n\\nWe encourage public contributions through issues and pull requests! Please review [CONTRIBUTING.md](./CONTRIBUTING.md) for details on our development process. All contributions to this repository require a GPG signed [Contributor License Agreement](./CLA.md).\\n\\nif you would like to provide a translation of Learning Bitcoin into another language, please additionally see [TRANSLATING.md](./TRANSLATING.md).\\n\\n### Discussions\\n\\nThe best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.\\n\\n[**Blockchain Commons Discussions**](https://github.com/BlockchainCommons/Community/discussions). For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the [Community repo](https://github.com/BlockchainCommons/Community) to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the [Gordian Developer Community](https://github.com/BlockchainCommons/Gordian-Developer-Community/discussions) or the \\n[Gordian User Community](https://github.com/BlockchainCommons/Gordian/discussions).\\'\\n\\n### Other Questions & Problems\\n\\nAs an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository\\'s [issues](../../issues) feature. Unfortunately, we can not make any promises on response time.\\n\\nIf your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.\\n\\n### Credits\\n\\nThe following people directly contributed to this repository. You can add your name here by getting involved. The first step is learning how to contribute from our [CONTRIBUTING.md](./CONTRIBUTING.md) documentation.\\n\\n\\n| Name              | Role                | Github                                            | Email                                 | GPG Fingerprint                                    |\\n| ----------------- | ------------------- | ------------------------------------------------- | ------------------------------------- | -------------------------------------------------- |\\n| Christopher Allen | Lead Author | [@ChristopherA](https://github.com/ChristopherA) | \\\\<ChristopherA@LifeWithAlacrity.com\\\\> | FDFE 14A5 4ECB 30FC 5D22  74EF F8D3 6C91 3574 05ED |\\n| Shannon Appelcline |  Lead Author | [@shannona](https://github.com/shannona) | \\\\<shannon.appelcline@gmail.com\\\\> | 7EC6 B928 606F 27AD |\\n\\n\\nAdditional contributions are listed below:\\n\\n| Role                | Names                                    |\\n| ------------------- | ---------------------------------------- |\\n| ***Contributors:*** | [gg2001](https://github.com/gg2001) (Go, Node.js sections), [gorazdko](https://github.com/gorazdko) (Rust section), [Javier Vargas](https://github.com/javiervargas) (C, Java, Lightning, Tor sections), [jodobear](https://github.com/jodobear) (Appendix: Compiling Bitcoin, Python section), [Prayank](    https://github.com/prayank23) (i2p sections)                               |\\n| ***Reviewers:***    | Glen Willem [@gwillem](https://github.com/gwillem) |\\n| ***Sponsors:***     | Blockstream Corporation                  |\\n\\n### Translation Credits\\n\\nThanks to the volunteers who spent extensive time writing and reviewing other-language translations of the original English-language course.\\n\\n#### Portuguese Translation\\n\\n| Name              | Role                | Github                                            | \\n| ----------------- | ------------------- | ------------------------------------------------- | \\n| Namcios | Translator & Reviewer | [@namcios](https://github.com/namcios) | \\n| Korea | Translator & Reviewer | [@KoreaComK](https://github.com/KoreaComK) | \\n| Luke Pavsky | Translator & Reviewer | [@lukedevj](https://github.com/lukedevj) | \\n| hgrams | Translator & Reviewer | [@hgrams](https://github.com/hgrams) | \\n\\n#### Spanish Translation\\n\\n Name | Role | GitHub |\\n| ---------- | -------- | ------------ |\\n| Ian Culp | Translator & Reviewer | [@icculp](https://github.com/icculp) |\\n| Maxi Goyheneche | Translator | [@maxcrowar](https://github.com/maxcrowar) |\\n| Said Rahal | Translator | [@srahalh](https://github.com/srahalh) |\\n| César A. Vallero | Translator & Reviewer | [@csralvall](https://github.com/csralvall) |\\n| Javier Vargas | Translator & Reviewer | [@javiervargas](https://github.com/javiervargas) |\\n\\n## Responsible Disclosure\\n\\nWe want to keep all of our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.\\n\\nWe do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.\\n\\n### Reporting a Vulnerability\\n\\nPlease report suspected security vulnerabilities in private via email to ChristopherA@BlockchainCommons.com (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.\\n\\nThe following keys may be used to communicate sensitive information to developers:\\n\\n| Name              | Fingerprint                                        |\\n| ----------------- | -------------------------------------------------- |\\n| Christopher Allen | FDFE 14A5 4ECB 30FC 5D22  74EF F8D3 6C91 3574 05ED |\\n\\nYou can import a key by running the following command with that individual’s fingerprint: `gpg --recv-keys \"<fingerprint>\"` Ensure that you put quotes around fingerprints that contain spaces.\\n'},\n",
       " {'repo': 'jgarzik/pyminer',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': \"#Pyminer\\n\\nThis is a 'getwork' CPU mining client for bitcoin.\\n\\nIt is pure-python, and therefore very, very slow.  The purpose is to\\nprovide a reference implementation of a miner, for study.\\n\\n##In order for this software to run you must build and run bitcoind from source on your computer.  \\n\"},\n",
       " {'repo': 'paritytech/parity-bitcoin',\n",
       "  'language': 'Rust',\n",
       "  'readme_contents': '# The Parity Bitcoin client.\\n\\n# THIS IS UNMAINTAINED HISTORICAL SOFTWARE\\n\\n[![Build Status][travis-image]][travis-url] [![Snap Status](https://build.snapcraft.io/badge/paritytech/parity-bitcoin.svg)](https://build.snapcraft.io/user/paritytech/parity-bitcoin)\\n\\nGitter [![Gitter https://gitter.im/paritytech/parity-bitcoin](https://badges.gitter.im/paritytech/parity-bitcoin.svg)](https://gitter.im/paritytech/parity-bitcoin)\\n\\n- [Installing from source](#installing-from-source)\\n\\n- [Installing the snap](#installing-the-snap)\\n\\n- [Running tests](#running-tests)\\n\\n- [Going online](#going-online)\\n\\n- [Importing bitcoind database](#importing-bitcoind-database)\\n\\n- [Command line interface](#command-line-interface)\\n\\n- [JSON-RPC](#json-rpc)\\n\\n- [Logging](#logging)\\n\\n- [Internal Documentation](#internal-documentation)\\n\\n- [Project Graph][graph]\\n\\n[graph]: ./tools/graph.svg\\n[travis-image]: https://travis-ci.com/paritytech/parity-bitcoin.svg?token=DMFvZu71iaTbUYx9UypX&branch=master\\n[travis-url]: https://travis-ci.com/paritytech/parity-bitcoin\\n[doc-url]: https://paritytech.github.io/parity-bitcoin/pbtc/index.html\\n\\n## Installing from source\\n\\nInstalling `pbtc` from source requires `rustc` and `cargo`.\\n\\nMinimal supported version is `rustc 1.23.0 (766bd11c8 2018-01-01)`\\n\\n#### Install rustc and cargo\\n\\nBoth `rustc` and `cargo` are a part of rust tool-chain.\\n\\nAn easy way to install the stable binaries for Linux and Mac is to run this in your shell:\\n\\n```\\ncurl -sSf https://static.rust-lang.org/rustup.sh | sh\\n```\\n\\nWindows binaries can be downloaded from [rust-lang website](https://www.rust-lang.org/en-US/downloads.html).\\n\\n#### Install C and C++ compilers\\n\\nYou will need the cc and gcc compilers to build some of the dependencies.\\n\\n```\\nsudo apt-get update\\nsudo apt-get install build-essential\\n```\\n\\n#### Clone and build pbtc\\n\\nNow let\\'s clone `pbtc` and enter it\\'s directory:\\n\\n```\\ngit clone https://github.com/paritytech/parity-bitcoin\\ncd parity-bitcoin\\n```\\n\\n`pbtc` can be build in two modes. `--debug` and `--release`. Debug is the default.\\n\\n```\\n# builds pbtc in debug mode\\ncargo build -p pbtc\\n```\\n\\n```\\n# builds pbtc in release mode\\ncargo build -p pbtc --release\\n```\\n\\n`pbtc` is now available at either `./target/debug/pbtc` or `./target/release/pbtc`.\\n\\n## Installing the snap\\n\\nIn any of the [supported Linux distros](https://snapcraft.io/docs/core/install):\\n\\n```\\nsudo snap install parity-bitcoin --edge\\n```\\n\\n## Running tests\\n\\n`pbtc` has internal unit tests and it conforms to external integration tests.\\n\\n#### Running unit tests\\n\\nAssuming that repository is already cloned, we can run unit tests with this command:\\n\\n```\\ncargo test --all\\n```\\n\\n#### Running external integration tests\\n\\nRunning integration tests is automated, as the regtests repository is one of the submodules. Let\\'s download it first:\\n\\n```\\ngit submodule update --init\\n```\\n\\nNow we can run them using the command:\\n\\n```\\n./tools/regtests.sh\\n```\\n\\nIt is also possible to run regtests manually:\\n\\n```\\n# let\\'s start pbtc in regtest compatible mode\\n./target/release/pbtc --btc --regtest\\n\\n# now in second shell window\\ncd $HOME\\ngit clone https://github.com/TheBlueMatt/test-scripts\\ncd test-scripts\\njava -jar pull-tests-f56eec3.jar\\n\\n```\\n\\n## Going online\\n\\nBy default parity connects to bitcoind-seednodes. Full list is available [here](./pbtc/seednodes.rs).\\n\\nBefore starting synchronization, you must decide - which fork to follow - Bitcoin Core (`--btc` flag) or Bitcoin Cash (`--bch` flag). On next start, passing the same flag is optional, as the database is already bound to selected fork and won\\'t be synchronized using other verification rules.\\n\\nTo start syncing the main network, just start the client, passing selected fork flag. For example:\\n\\n```\\n./target/release/pbtc --btc\\n```\\n\\nTo start syncing the testnet:\\n\\n```\\n./target/release/pbtc --btc --testnet\\n```\\n\\nTo not print any syncing progress add `--quiet` flag:\\n\\n```\\n./target/release/pbtc --btc --quiet\\n```\\n\\n## Importing bitcoind database\\n\\nIt is possible to import existing `bitcoind` database:\\n\\n```\\n# where $BITCOIND_DB is path to your bitcoind database, e.g., \"/Users/user/Library/Application Support\"\\n./target/release/pbtc import \"$BITCOIND_DB/Bitcoin/blocks\"\\n```\\n\\nBy default import verifies imported the blocks. You can disable this, by adding `--verification-level=none` flag.\\n\\n```\\n./target/release/pbtc --btc --verification-level=none import \"$BITCOIND_DB/Bitcoin/blocks\"\\n```\\n\\n## Command line interface\\n\\nFull list of CLI options, which is available under `pbtc --help`:\\n\\n```\\npbtc 0.1.0\\nParity Technologies <info@parity.io>\\nParity Bitcoin client\\n\\nUSAGE:\\n    pbtc [FLAGS] [OPTIONS] [SUBCOMMAND]\\n\\nFLAGS:\\n        --bch             Use Bitcoin Cash verification rules (BCH).\\n        --btc             Use Bitcoin Core verification rules (BTC).\\n    -h, --help            Prints help information\\n        --no-jsonrpc      Disable the JSON-RPC API server.\\n    -q, --quiet           Do not show any synchronization information in the console.\\n        --regtest         Use a private network for regression tests.\\n        --testnet         Use the test network (Testnet3).\\n    -V, --version         Prints version information\\n\\nOPTIONS:\\n        --blocknotify <COMMAND>            Execute COMMAND when the best block changes (%s in COMMAND is replaced by the block hash).\\n    -c, --connect <IP>                     Connect only to the specified node.\\n    -d, --data-dir <PATH>                  Specify the database and configuration directory PATH.\\n        --db-cache <SIZE>                  Sets the database cache size.\\n        --jsonrpc-apis <APIS>              Specify the APIs available through the JSONRPC interface. APIS is a comma-delimited list of API names.\\n        --jsonrpc-cors <URL>               Specify CORS header for JSON-RPC API responses.\\n        --jsonrpc-hosts <HOSTS>            List of allowed Host header values.\\n        --jsonrpc-interface <INTERFACE>    The hostname portion of the JSONRPC API server.\\n        --jsonrpc-port <PORT>              Specify the PORT for the JSONRPC API server.\\n        --only-net <NET>                   Only connect to nodes in network version <NET> (ipv4 or ipv6).\\n        --port <PORT>                      Listen for connections on PORT.\\n    -s, --seednode <IP>                    Connect to a seed-node to retrieve peer addresses, and disconnect.\\n        --verification-edge <BLOCK>        Non-default verification-level is applied until a block with given hash is met.\\n        --verification-level <LEVEL>       Sets the Blocks verification level to full (default), header (scripts are not verified), or none (no verification at all).\\n\\nSUBCOMMANDS:\\n    help        Prints this message or the help of the given subcommand(s)\\n    import      Import blocks from a Bitcoin Core database.\\n    rollback    Rollback the database to given canonical-chain block.\\n```\\n\\n## JSON-RPC\\n\\nThe JSON-RPC interface is served on port :8332 for mainnet and :18332 for testnet unless you specified otherwise. So if you are using testnet, you will need to change the port in the sample curl requests shown below.\\n\\n#### Network\\n\\nThe Parity-bitcoin `network` interface.\\n\\n##### addnode\\n\\nAdd the node.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"addnode\", \"params\": [\"127.0.0.1:8888\", \"add\"], \"id\":1 }\\' localhost:8332\\n\\nRemove the node.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"addnode\", \"params\": [\"127.0.0.1:8888\", \"remove\"], \"id\":1 }\\' localhost:8332\\n\\nConnect to the node.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"addnode\", \"params\": [\"127.0.0.1:8888\", \"onetry\"], \"id\":1 }\\' localhost:8332\\n\\n##### getaddednodeinfo\\n\\nQuery info for all added nodes.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"id\":\"1\", \"method\": \"getaddednodeinfo\", \"params\": [true] }\\' localhost:8332\\n\\nQuery info for the specified node.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"id\":\"1\", \"method\": \"getaddednodeinfo\", \"params\": [true, \"192.168.0.201\"] }\\' localhost:8332\\n\\n##### getconnectioncount\\n\\nGet the peer count.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"id\":\"1\", \"method\": \"getconnectioncount\", \"params\": [] }\\' localhost:8332\\n\\n#### Blockchain\\n\\nThe Parity-bitcoin `blockchain` data interface.\\n\\n##### getbestblockhash\\n\\nGet hash of best block.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getbestblockhash\", \"params\": [], \"id\":1 }\\' localhost:8332\\n\\n##### getblockcount\\n\\nGet height of best block.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getblockcount\", \"params\": [], \"id\":1 }\\' localhost:8332\\n\\n##### getblockhash\\n\\nGet hash of block at given height.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getblockhash\", \"params\": [0], \"id\":1 }\\' localhost:8332\\n\\n##### getdifficulty\\n\\nGet proof-of-work difficulty as a multiple of the minimum difficulty\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getdifficulty\", \"params\": [], \"id\":1 }\\' localhost:8332\\n\\n##### getblock\\n\\nGet information on given block.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getblock\", \"params\": [\"000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f\"], \"id\":1 }\\' localhost:8332\\n\\n##### gettxout\\n\\nGet details about an unspent transaction output.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"gettxout\", \"params\": [\"4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b\", 0], \"id\":1 }\\' localhost:8332\\n\\n##### gettxoutsetinfo\\n\\nGet statistics about the unspent transaction output set.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"gettxoutsetinfo\", \"params\": [], \"id\":1 }\\' localhost:8332\\n\\n#### Miner\\n\\nThe Parity-bitcoin `miner` data interface.\\n\\n##### getblocktemplate\\n\\nGet block template for mining.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getblocktemplate\", \"params\": [{\"capabilities\": [\"coinbasetxn\", \"workid\", \"coinbase/append\"]}], \"id\":1 }\\' localhost:8332\\n\\n#### Raw\\n\\nThe Parity-bitcoin `raw` data interface.\\n\\n\\n##### getrawtransaction\\n\\nReturn the raw transaction data.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"getrawtransaction\", \"params\": [\"4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b\"], \"id\":1 }\\' localhost:8332\\n\\n##### decoderawtransaction\\n\\nReturn an object representing the serialized, hex-encoded transaction.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"decoderawtransaction\", \"params\": [\"01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73ffffffff0100f2052a01000000434104678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5fac00000000\"], \"id\":1 }\\' localhost:8332\\n\\n##### createrawtransaction\\n\\nCreate a transaction spending the given inputs and creating new outputs.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"createrawtransaction\", \"params\": [[{\"txid\":\"4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b\",\"vout\":0}],{\"1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa\":0.01}], \"id\":1 }\\' localhost:8332\\n\\n##### sendrawtransaction\\n\\nAdds transaction to the memory pool && relays it to the peers.\\n\\n    curl -H \\'content-type: application/json\\' --data-binary \\'{\"jsonrpc\": \"2.0\", \"method\": \"sendrawtransaction\", \"params\": [\"01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4d04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73ffffffff0100f2052a01000000434104678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5fac00000000\"], \"id\":1 }\\' localhost:8332\\n\\n## Logging\\n\\nThis is a section only for developers and power users.\\n\\nYou can enable detailed client logging by setting the environment variable `RUST_LOG`, e.g.,\\n\\n```\\nRUST_LOG=verification=info ./target/release/pbtc --btc\\n```\\n\\n`pbtc` started with this environment variable will print all logs coming from `verification` module with verbosity `info` or higher. Available log levels are:\\n\\n- `error`\\n- `warn`\\n- `info`\\n- `debug`\\n- `trace`\\n\\nIt\\'s also possible to start logging from multiple modules in the same time:\\n\\n```\\nRUST_LOG=sync=trace,p2p=trace,verification=trace,db=trace ./target/release/pbtc --btc\\n```\\n\\n## Internal documentation\\n\\nOnce released, `pbtc` documentation will be available [here][doc-url]. Meanwhile it\\'s only possible to build it locally:\\n\\n```\\ncd parity-bitcoin\\n./tools/doc.sh\\nopen target/doc/pbtc/index.html\\n```\\n'},\n",
       " {'repo': 'bitcoinxt/bitcoinxt',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': \"Bitcoin XT\\n==========\\n\\nBitcoin XT is an implementation of a Bitcoin Cash (BCH) full node that embraces Bitcoin's original vision of simple, reliable, low-cost transactions for everyone in the world. Bitcoin XT originated as a series of patches on top of Bitcoin Core and is now a independently maintained software fork. See some selected [features](https://bitcoinxt.software/patches.html).\\n\\nBitcoin XT downloads are code signed and are built reproducibly using gitian. Discussion can be found at the [XT Gitter](https://gitter.im/bitcoinxt/Lobby).\\n\\nData Directory Compatibility\\n============================\\n\\nIf using a data directory from a different BCH or BTC full node, specify `-reindex` on first launch.\\n\\nSet aside `wallet.dat` from Bitcoin Core or Bitcoin ABC (reason: HD wallet not yet supported). Also delete `fee_estimates.dat` from these clients.\\n \\nBitcoin XT can run in BTC chain mode by specifying `-uahftime=0`. Please note that Bitcoin XT does not validate segwit, and the conversion notes above still apply.\\n\\n\\nDevelopment process\\n===================\\n\\nIdeas for useful features are tracked in Issues.  Pull requests from developers, including well-done cherry picks from other clients or cryptos, are very welcome.\\n\\nTo discuss Bitcoin Cash development in general, you are welcome to use the [mailing list](https://lists.linuxfoundation.org/pipermail/bitcoin-ml/).\\n\\nWe have a manifesto that lays out things we believe are important, which you can read about here:\\n\\nhttps://bitcoinxt.software/\\n\\n\"},\n",
       " {'repo': '1200wd/bitcoinlib',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': 'Python Bitcoin Library\\n======================\\n\\nBitcoin, Litecoin and Dash Crypto Currency Library for Python.\\n\\nIncludes a fully functional wallet with multi-signature, multi-currency and multiple accounts.\\nYou this library at a high level and create and manage wallets for the command line or at a low level\\nand create your own custom made transactions, keys or wallets.\\n\\nThe BitcoinLib connects to various service providers automatically to update wallets, transactions and\\nblockchain information. It does currently not parse the blockchain itself.\\n\\n.. image:: https://github.com/1200wd/bitcoinlib/actions/workflows/unittests.yaml/badge.svg\\n    :target: https://github.com/1200wd/bitcoinlib/actions/workflows/unittests.yaml\\n    :alt: Unittests\\n.. image:: https://img.shields.io/pypi/v/bitcoinlib.svg\\n    :target: https://pypi.org/pypi/bitcoinlib/\\n    :alt: PyPi\\n.. image:: https://readthedocs.org/projects/bitcoinlib/badge/?version=latest\\n    :target: http://bitcoinlib.readthedocs.io/en/latest/?badge=latest\\n    :alt: RTD\\n.. image:: https://coveralls.io/repos/github/1200wd/bitcoinlib/badge.svg?branch=installation-documentation-update\\n    :target: https://coveralls.io/github/1200wd/bitcoinlib?branch=master\\n    :alt: Coveralls\\n.. image:: https://snyk.io/test/github/1200wd/bitcoinlib/badge.svg\\n    :target: https://snyk.io/test/github/1200wd/bitcoinlib\\n    :alt: Known Vulnerabilities\\n    \\n\\nDocumentation\\n-------------\\n\\nRead the full documentation at: http://bitcoinlib.readthedocs.io/\\n\\n\\nDisclaimer\\n----------\\n\\nThis library is still in development, please use at your own risk and test sufficiently before using it in a\\nproduction environment.\\n\\n\\nSome Examples\\n=============\\n\\nWallet\\n------\\n\\nThe bitcoin library contains a wallet implementation using SQLAlchemy and SQLite3 to import, create and manage\\nkeys in a Hierarchical Deterministic way.\\n\\nExample: Create wallet and generate new address (key) to receive bitcoins\\n\\n.. code-block:: pycon\\n\\n   >>> from bitcoinlib.wallets import Wallet\\n   >>> w = Wallet.create(\\'Wallet1\\')\\n   >>> key1 = w.get_key()\\n   >>> key1.address\\n   \\'1Fo7STj6LdRhUuD1AiEsHpH65pXzraGJ9j\\'\\n\\nNow send a small transaction to your wallet and use the scan() method to update transactions and UTXO\\'s\\n\\n.. code-block:: pycon\\n\\n    >>> w.scan()\\n    >>> w.info()  # Shows wallet information, keys, transactions and UTXO\\'s\\n\\nWhen your wallet received a payment and has unspent transaction outputs, you can send bitcoins easily.\\nIf successful a transaction ID is returned\\n\\n.. code-block:: pycon\\n\\n    >>> t = w.send_to(\\'1PWXhWvUH3bcDWn6Fdq3xhMRPfxRXTjAi1\\', \\'0.001 BTC\\', offline=False)\\n    \\'b7feea5e7c79d4f6f343b5ca28fa2a1fcacfe9a2b7f44f3d2fd8d6c2d82c4078\\'\\n    >>> t.info  # Shows transaction information and send results\\n\\n\\nWallet from passphrase with accounts and multiple currencies\\n------------------------------------------------------------\\n\\nThe following code creates a wallet with two Bitcoin and one Litecoin account from a Mnemonic passphrase.\\nThe complete wallet can be recovered from the passphrase, which is the masterkey.\\n\\n.. code-block:: python\\n\\n    from bitcoinlib.wallets import Wallet, wallet_delete\\n    from bitcoinlib.mnemonic import Mnemonic\\n\\n    passphrase = Mnemonic().generate()\\n    print(passphrase)\\n    w = Wallet.create(\"Wallet2\", keys=passphrase, network=\\'bitcoin\\')\\n    account_btc2 = w.new_account(\\'Account BTC 2\\')\\n    account_ltc1 = w.new_account(\\'Account LTC\\', network=\\'litecoin\\')\\n    w.get_key()\\n    w.get_key(account_btc2.account_id)\\n    w.get_key(account_ltc1.account_id)\\n    w.info()\\n\\n\\nMulti-Signature Wallets\\n-----------------------\\n\\nCreate a Multisig wallet with 2 cosigners which both need to sign a transaction.\\n\\n.. code-block:: python\\n\\n    from bitcoinlib.wallets import Wallet\\n    from bitcoinlib.keys import HDKey\\n\\n    NETWORK = \\'testnet\\'\\n    k1 = HDKey(\\'tprv8ZgxMBicQKsPd1Q44tfDiZC98iYouKRC2CzjT3HGt1yYw2zuX2awTotzGAZQEAU9bi2M5MCj8iedP9MREPjUgpDEBwBgGi2C8eK\\'\\n                \\'5zNYeiX8\\', network=NETWORK)\\n    k2 = HDKey(\\'tprv8ZgxMBicQKsPeUbMS6kswJc11zgVEXUnUZuGo3bF6bBrAg1ieFfUdPc9UHqbD5HcXizThrcKike1c4z6xHrz6MWGwy8L6YKVbgJ\\'\\n                \\'MeQHdWDp\\', network=NETWORK)\\n    w1 = Wallet.create(\\'multisig_2of2_cosigner1\\', sigs_required=2,\\n                         keys=[k1, k2.public_master(multisig=True)], network=NETWORK)\\n    w2 = Wallet.create(\\'multisig_2of2_cosigner2\\',  sigs_required=2,\\n                         keys=[k1.public_master(multisig=True), k2], network=NETWORK)\\n    print(\"Deposit testnet bitcoin to this address to create transaction: \", w1.get_key().address)\\n\\nCreate a transaction in the first wallet\\n\\n.. code-block:: python\\n\\n    w1.utxos_update()\\n    t = w1.sweep(\\'mwCwTceJvYV27KXBc3NJZys6CjsgsoeHmf\\', min_confirms=0)\\n    t.info()\\n    t.send()\\n\\nAnd then import the transaction in the second wallet, sign it and push it to the network\\n\\n.. code-block:: python\\n\\n    w2.get_key()\\n    t2 = w2.transaction_import(t)\\n    t2.sign()\\n    t2.send()\\n    t2.info()\\n\\n\\nSegregated Witness Wallet\\n-------------------------\\n\\nEasily create and manage segwit wallets. Both native segwit with base32/bech32 addresses and P2SH nested segwit\\nwallets with traditional addresses are available.\\n\\nCreate a native single key P2WPKH wallet:\\n\\n.. code-block:: pycon\\n\\n    >>> from bitcoinlib.wallets import Wallet\\n    >>> w = Wallet.create(\\'wallet_segwit_p2wpkh\\', witness_type=\\'segwit\\')\\n    >>> w.get_key().address\\n    bc1q84y2quplejutvu0h4gw9hy59fppu3thg0u2xz3\\n\\nOr create a P2SH nested single key P2SH_P2WPKH wallet:\\n\\n.. code-block:: pycon\\n\\n    >>> from bitcoinlib.wallets import Wallet\\n    >>> w = Wallet.create(\\'wallet_segwit_p2sh_p2wpkh\\', witness_type=\\'p2sh-segwit\\')\\n    >>> w.get_key().address\\n    36ESSWgR4WxXJSc4ysDSJvecyY6FJkhUbp\\n\\n\\nCommand Line Tool\\n-----------------\\n\\nWith the command line tool you can create and manage a wallet without any Python programming.\\n\\nTo create a new Bitcoin wallet\\n\\n.. code-block:: bash\\n\\n    $ clw newwallet\\n    Command Line Wallet for BitcoinLib\\n\\n    Wallet newwallet does not exist, create new wallet [yN]? y\\n\\n    CREATE wallet \\'newwallet\\' (bitcoin network)\\n\\n    Your mnemonic private key sentence is: force humble chair kiss season ready elbow cool awake divorce famous tunnel\\n\\n    Please write down on paper and backup. With this key you can restore your wallet and all keys\\n\\n\\nYou can use clw to create simple or multisig wallets for various networks, manage public and private keys\\nand managing transactions.\\n\\nFor the full command line wallet documentation please read\\n\\nhttp://bitcoinlib.readthedocs.io/en/latest/_static/manuals.command-line-wallet.html\\n\\n\\nMnemonic key generation\\n-----------------------\\n\\nAllows you to use easy to remember passphrases consisting of a number of words to store private keys (BIP0039).\\nYou can password protect this passphrase (BIP0038), and use the HD Wallet structure to generate an almost infinite \\nnumber of new private keys and bitcoin addresses (BIP0043 and BIP0044).\\n\\nExample: Generate a list of words passphrase and derive a private key seed\\n\\n.. code-block:: pycon\\n\\n   >>> from bitcoinlib.mnemonic import Mnemonic\\n   >>> from bitcoinlib.encoding import to_hexstring\\n   >>> words = Mnemonic().generate()\\n   >>> words\\n   unique aisle iron extend earn cigar trust source next depart yard bind\\n   >>> to_hexstring(Mnemonic().to_seed(words))\\n   \\'9c6f41a347bf4f326f9c989fb522bec1b82c36463580d1769daadba7d59f69a305505fdd5d2131c9c60255c79279d4e8896155e0b126abea036da56a766f81a1\\'\\n\\n\\nService providers\\n-----------------\\nCommunicates with pools of bitcoin service providers to retrieve transaction, address, blockchain information. \\nCan be used to push a transaction to the network, determine optimal service fee for a transaction or to update your\\nwallet\\'s balance.\\n\\nWhen working with wallets, connections to service providers are automatically managed, so you don\\'t have to worry\\nabout them. You can however easily use the Service object directly.\\n\\nExample: Get estimated transaction fee in Sathosis per Kb for confirmation within 5 blocks\\n\\n.. code-block:: pycon\\n\\n   >>> from bitcoinlib.services.services import Service\\n   >>> Service().estimatefee(5)\\n   138964\\n\\n\\nOther Databases\\n---------------\\n\\nBitcoinlib uses the SQLite database by default, but other databases are supported as well.\\nSee http://bitcoinlib.readthedocs.io/en/latest/_static/manuals.databases.html for instructions on how to use\\nMySQL or PostgreSQL.\\n\\n\\nMore examples\\n-------------\\nFor more examples see https://github.com/1200wd/bitcoinlib/tree/master/examples\\n\\n\\nImplements the following Bitcoin Improvement Proposals\\n------------------------------------------------------\\n- Hierarchical Deterministic Wallets (BIP0032)\\n- Passphrase-protected private key (BIP0038)\\n- Mnemonic code for generating deterministic keys (BIP0039)\\n- Purpose Field for Deterministic Wallets (BIP0043)\\n- Multi-Account Hierarchy for Deterministic Wallets (BIP0044)\\n- Structure for Deterministic P2SH Multisignature Wallets (BIP0045)\\n- Bech32/base32 address format for native v0-16 witness outputs (BIP0173)\\n- Native and P2SH nested Segregated Witness transactions (BIP0141 and BIP0143)\\n- Bech32m format for v1+ witness addresses (BIP0350)\\n- and many more...\\n\\n\\nInstalling and updating\\n=======================\\n\\nPre-requirements Linux\\n----------------------\\n\\n``sudo apt install build-essential python3-dev libgmp3-dev libssl-dev``\\n\\nTo install OpenSSL development package on Debian, Ubuntu or their derivatives\\n\\n``sudo apt install libssl-dev``\\n\\nTo install OpenSSL development package on Fedora, CentOS or RHEL\\n\\n``sudo yum install gcc openssl-devel``\\n\\n\\nPre-requirements Windows\\n------------------------\\n\\nThis library requires a Microsoft Visual C++ Compiler. See\\nhttp://bitcoinlib.readthedocs.io/en/latest/_static/manuals.install.html\\n\\nThe fastecdsa library is not enabled at this moment on windows, the slower ecdsa library is installed.\\n\\n\\nInstall with pip\\n----------------\\n\\n``pip install bitcoinlib``\\n\\nThese packages will be installed\\n* fastecdsa (or ecdsa on Windows)\\n* sqlalchemy\\n* requests\\n* numpy\\n* pycryptodome\\n\\nIf you want to use BIP38 encrypted private keys, you should also install the much faster scrypt library.\\n\\n``pip install scrypt``\\n\\nInstall development environment\\n-------------------------------\\n\\nRequired packages:\\n\\n``sudo apt install -y postgresql postgresql-contrib mysql-server libpq-dev libmysqlclient-dev``\\n\\nCreate a virtual environment for instance on linux with virtualenv:\\n\\n.. code-block:: bash\\n\\n    $ virtualenv -p python3 venv/bitcoinlib\\n    $ source venv/bitcoinlib/bin/activate\\n\\nThen clone the repository and install dependencies:\\n\\n.. code-block:: bash\\n\\n    $ git clone https://github.com/1200wd/bitcoinlib.git\\n    $ cd bitcoinlib\\n    $ pip install -r requirements-dev.txt\\n\\n\\nTroubleshooting\\n---------------\\n\\nWhen you experience issues with the scrypt package when installing, you can try to solve this by removing and reinstall\\nscrypt:\\n\\n.. code-block:: bash\\n\\n    $ pip uninstall scrypt\\n    $ pip install scrypt\\n\\nPlease make sure you also have the Python development and SSL development packages installed, see \\'Other requirements\\'\\nabove.\\n\\nYou can also use pyscrypt or pycryptodome instead of scrypt. Pyscrypt is a pure Python scrypt password-based key\\nderivation library. It works but it is slow when using BIP38 password protected keys.\\n\\nIf you run into issues, do not hesitate to contact us or file an issue at https://github.com/1200wd/bitcoinlib/issues\\n\\n\\nUpdate library\\n--------------\\n\\nUpdate to the latest version of the library with\\n\\n.. code-block:: bash\\n\\n    $ pip install bitcoinlib --upgrade\\n\\nTo upgrade make sure everything is backuped and run updatedb.py from the installation directory.\\n\\n.. code-block:: bash\\n\\n    $ python updatedb.py -d [<link-to-database-if-not-standard>]\\n\\n\\nFor more information on installing, updating and maintenance see\\nhttps://bitcoinlib.readthedocs.io/en/latest/_static/manuals.install.html#installation\\n\\n\\nFuture / Roadmap\\n================\\n\\n* Support advanced scripts\\n* Fully support timelocks\\n* Support for lightning network\\n* Support for Trezor wallet\\n'},\n",
       " {'repo': 'JulyIghor/QtBitcoinTrader',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '## Qt Bitcoin Trader\\n\\nThis software helps you open and cancel orders very fast. Real time data monitoring. Automated trading using JavaScript powered scripts.\\n\\nDeveloped on pure Qt, uses OpenSSL, AES 256 key and secret protection.\\n\\n## Official website\\n\\n* https://centrabit.com/downloads/\\n* https://qttrader.com\\n\\n## Download binaries\\n\\n* https://sourceforge.net/projects/bitcointrader/  `Win32`,`Mac`,`Linux`\\n* http://www.softpedia.com/get/Others/Finances-Business/Bitcoin-Trader.shtml `Win32`\\n* http://mac.softpedia.com/get/Finance/Qt-Bitcoin-Trader.shtml `Mac`\\n\\n## Compilation on Linux\\n* `sudo apt-get install g++ libssl-dev libglu1-mesa-dev qt5-qmake qtscript5-dev qtmultimedia5-dev git`\\n* `git clone https://github.com/JulyIGHOR/QtBitcoinTrader.git`\\n* `cd ./QtBitcoinTrader/src`\\n* `QT_SELECT=5 qmake QtBitcoinTrader_Desktop.pro`\\n* `make && make install && make clean`\\n\\n## Demos\\n\\n* http://www.youtube.com/watch?v=C--P258DQkk\\n\\n## Forums\\n\\n* https://bitcointalk.org/index.php?topic=201062 `ENG`\\n* https://bitcointalk.org/index.php?topic=218044 `RUS`\\n\\n## Social\\n\\n* http://www.facebook.com/QtBitcoinTrader\\n* http://twitter.com/QtBitcoinTrader\\n* http://vk.com/QtBitcoinTrader `RUS`\\n\\n## Change Log\\n\\nv1.42.10 Released!\\n\\n- Updated API integration to fix Bitstamp and Poloniex\\n- Synchronized currency pairs\\n\\nv1.42.00 Released!\\n\\n- Fixed crash while running some scripts/rules\\n- Updated API integration to fix Bitstamp, Poloniex and Bittrex\\n- Fixed a bug when trade history stays empty\\n- Fixed UI bugs\\n\\nv1.41.00 Released!\\n\\n- Fixed time syncronization in Binance\\n- Translation fixes, added Korean language\\n- Fixed bug in trade history of Bittrex exchange\\n- Improved request interval limits for Poloniex\\n- Qt 6 support, using QJSEngine instead of QtScript\\n- Optimized CPU usage\\n- Updated currency pairs list\\n\\nv1.40.55 Released!\\n\\n- Fixed trader.groupStop(..) script command\\n- Synchronized currency pairs\\n\\nv1.40.54 Released!\\n\\n- Fixed trader.say(..) script command\\n- Fixed crash on unix systems\\n\\nv1.40.53 Released!\\n\\n- Fixed critical bug causing missing public trade history items\\n- Fixed bug when zero/incorrect balance reached script/rules events\\n- Fixed missing script events/wrong rule state for Bitfinex\\n- Fixed own trade history items missing for Bitfinex\\n- Fixed rounding of buy/sell total calculations\\n- Fixed Hitbtc exchange api keys impossible to add\\n- Fixed translation issues. French language updated\\n- Optimized memory usage\\n- Removed exchanges bitmarket.pl, okcoin.cn, btcchina.com, goc.io\\n\\nv1.40.52 Released!\\n\\n- Enabled experimental vnc server on a Linux\\n- Fixed yobit api, if you ever get nonce error, re-create API keys\\n- Improved minimum request interval for Binance to prevent IP bans\\n\\nv1.40.51 Released!\\n\\n- Fixed hitbtc balance\\n- Fixed binance balance\\n\\nv1.40.50 Released!\\n\\n- Fixed hitbtc authorization bug\\n- Fixed transaction history in bitstamp\\n- Smart paste for spinbox values\\n- Synchronized currency pairs\\n- Improved text to speech engine\\n\\nv1.40.43 Released!\\n\\n- Request interval now can be set less than 0.5 seconds\\n- Fixed bug when timers wasn\\'t stopped on group stop\\n- Fixed crash when open Debug dialog\\n- Fixed incorrect fee value in Bitfinex\\n- Fixed filter open orders in Bitfinex\\n- Fixed tray icon in Linux\\n- Fixed bug caused long delay after network down\\n- Fixed on top mode for dock widgets\\n- Fixed bug when password was incorrectly detected as weak\\n- Currency pairs synchronized in all exchanges\\n\\nv1.40.42 Released!\\n\\n- Fixed start window position\\n- Removed duplicated info in log view\\n- Fixed Own transactions display in Bitstamp\\n- Fixed problem with false time\\n- Added option to change hostname and port for exchange profile\\n- Fixed wrong order amount for Bitfinex, when order partly filled\\n- Minor UI fixes, fixed crash in log view\\n\\nv1.40.41\\n- Bitstamp API integration fixed\\n- Rules generator dialog critical bug fixed when price with fee used\\n- Time sync bug fixed\\n- Binance orderbook table fixed\\n- Removed Wex exchange\\n- Added alternative domain for Yobit\\n- Fixed dock panel issue caused blinks\\n- Many small fixes\\n\\nv1.40.40\\n- New exchange Poloniex\\n- Fixed script language command cancel ask and bid for Binance\\n- Fixed bug caused forever API down in some cases\\n- Minor fixes\\n\\nv1.40.30\\n- Added new exchange HitBTC\\n- Added more decimals for Fee Calculator\\n- Fixed canceling order via rule or script for Binance\\n- Fixed bug in charts\\n- Fixed wex mirror\\n- Minor cleanup and optimizations\\n\\nv1.40.23\\n- Added new exchange Bittrex\\n- Portable mode for Linux and macOS\\n- Secure auto update for Linux x86_64\\n- Uninstall option in help menu\\n- Fixed Binance own trade history order\\n- Time Sync bug fixed\\n- HDPI bug fixed\\n- Minor fixes\\n\\nv1.40.22\\n- Added new exchange Binance\\n- Many small fixes\\n- Subscribe to beta of Qt Trader exchange www.QtTrader.com\\n\\nv1.40.21\\n- Qt Trader 2.0 Announced! Visit www.QtTrader.com\\n- Fixed bug of Rules dialog\\n- Fixed HiDPI mode\\n- Fixed Script and Rules enable-disable command\\n- Fixed Last Buy and Sell price event bug\\n- Memory optimisations, refractoring\\n- Minor fixes\\n\\nv1.40.12\\n- Dropped support of Windows XP and macOS 10.9, but you still can compile it manually\\n- Removed update size limit for future bigger updates\\n- Fixed Bitfinex trade history bug\\n- Fixed Bitstamp certificate issue\\n- Switched to OpenSSL 1.1, no UPX in release binaries\\n- Minor improvements\\n\\nv1.40.09\\n- Fixed FeeCalculator crash\\n- Fixed account open orders filtering and calculations\\n- UI layout bugs fixed\\n\\nv1.40.08\\n- Added WEX exchange, removed BTC-e\\n- Fixed crash on app closing\\n- Added confirmation message on script editor clear\\n- Minor fixes\\n\\nv1.40.07\\n- Release builds for Win64\\n- Fix balance for OKCoin\\n- Fix script for Bitfinex\\n- Fix order type for Bitfinex\\n- JL Script logs now recognize endline and tabulation\\n- Fixed bug when silent auto update wont work\\n\\nv1.40.06\\n- Fixed fee calculator issue\\n- Added new currencies\\n- Minor improvements and fixes\\n\\nv1.40.03\\n- Bitfinex support fixes\\n- Secure auto update now works via Proxy\\n- YoBit support fixes\\n- Added button to force resync currencies\\n\\nv1.4\\n- New Exchange YoBit.net\\n- Currency pair synchronization on startup!\\n- Fixed issue with functions getPriceByVolume and getVolumeByPrice in JL Script\\n- Add HiDPI enable or disable settings\\n- Now you can search for currency pairs by keyword\\n- Improved many elements of interface\\n- Fixed bug with certificate that caused error messages\\n- Many other small fixes\\n\\nv1.30.04\\n- Add new pair for BitStamp\\n- Fixd fee calculations in Bitfinex\\n- Main window title now shows middle price instead of last trade price\\n- Fixed issue when app can\\'t start\\n\\nv1.30.03\\n- High screen resolution support for Windows\\n- Fixed fee for BTCChina and OKCoin\\n- Add new pairs for Bitfinex\\n- Fixed authorization for Bitfinex\\n- Completed the Norwegian translation\\n- Fixed bug on restoring Workspace from previous state\\n- Fixed account data and add new pairs for bitstamp\\n- Fixed minor bugs\\n\\nv1.3\\n- macOS Sierra support\\n- JL Script file read/write support\\n- Syncronised currency pairs of Bitfinex, Bitstamp, BTC-e\\n- Fixed bugs of history and currency pair in Bitstamp\\n- Improved Proxy settings\\n- Fixed network stat information\\n- Fixed display of balance in bitfinex, bitstamp, btcchina\\n- Fix tonce in btcchina\\n- Add reducing interface elements spacing (optional in settings)\\n- Add inactive start script button\\n- Fixed JL Script groups bug\\n- Fixed open order/cancel bug in bitstamp\\n- Fixed time synchronization bug\\n\\n\\nv1.07.01\\n- Hotfix. High CPU load fix. Nonce error fix\\n\\nv1.07\\n- Improved connection stability\\n- API engine rewrited\\n- Added balances triggers to rules\\n- Fixed RUR currency in BTC-e\\n- Fixed auto-scroll mode in last trades\\n- Fixed many minor bugs\\n- Now all binaries is digitally signed\\n\\nv1.06\\n- Bugfix release\\n- Fixed critical bug in Mt.Gox engine\\n- Fixed Mac OS X \"New window\" bug\\n- Fixed minor bugs\\n- Improved buy/sell/cancel stability\\n\\nv1.05\\n- Critical bugs fixed\\n- Calculations fixes\\n- Ui fixes\\n- Added PPC, FTC, RTC support\\n- Added proxy support\\n\\nv1.04\\n- Fixed UI bugs\\n- Added NMC and NVC to BTC-e\\n- Now last price displays in title\\n- Stability improvements in BTC-e exchange\\n- Many small improvements\\n- Translation fixes\\n\\nv1.03\\n- SSL security fix\\n- Fixed translations\\n- Small ui fix\\n\\nv1.02\\n- BTC-E.com support added. Now you can trade with LTC\\n- Added trade history display\\n- Multi-monitor support (Detachable windows)\\n- Improved connection stability\\n- Added German translation\\n- Fixed UI bugs, translation bugs and some minor bugs\\n\\nv1.01\\n- Fixed traffic heavy load.\\n- Added trades fetch to update last values faster.\\n\\nv1.00\\n- Api engine rewrited. Now works faster.\\n- Api lag improvements.\\n- Fixed minor bugs.\\n- Added Norwegian translation.\\n\\nv0.99\\n- Fixed minor bugs\\n- Added Spanish translation\\n- Translation engine updated\\n- Checking update engine rewrited. Secure autoinstall for Mac and Win feature added.\\n- Added portable mode for Windows (Just create folder QtBitcoinTrader near exe file)\\n\\nv0.98\\n- Added translation engine. Now you can translate application to your native language\\n- Fixed ui bugs\\n- Enhanced rules. Now there is two modes, Sequential and Concurrent\\n\\nv0.97\\n- Added profit calculation to main window\\n- Optimized ui\\n\\nv0.96\\n- Fixed minor bugs\\n- Optimized ui\\n- Mac version released\\n\\nv0.95\\n- Fixed fee calculator bug\\n- Now supports resolution down to 1024x700\\n- Enhanced rules feature\\n- Minor bugs fixed\\n\\nv0.94\\n- Rules finally working!\\n- Fixed some minor bugs\\n\\nv0.93\\n- Fixed critical ui bug where was wrong field in orders table\\n\\nv0.92\\n- Fixed minor bugs in ui and currencies\\n\\nv0.91\\n - Added Profiles\\n - Fixed Ui Bugs\\n\\nv0.90\\n- Added all currencies supported by Mt.Gox\\n- Minor fixes\\n\\nv0.89\\n- Fixed critical bug\\n\\nv0.88\\n- Addes Mt.Gox key and secret encryption with AES 256\\n- Fixed some ui bugx\\n- Minor fixes\\n\\nv0.87\\n- Match more faster engine\\n- Fixed some bugs\\n- Improved socket stability\\n- Tested on Linux, thanks to macman31\\n\\nv0.86\\n- Fixed bug in Orders Log\\n- Fixed bug in fee calculation\\n- Fixed ui dialogs\\n\\nv0.85\\n- Added SSL switcher\\n- Fixed some dialogs\\n\\nv0.84\\n- Interlaced software lag performance\\n\\nv0.83\\n- Added Fee Calculator\\n\\nv0.82\\n- Improved socket stability\\n\\nv0.81\\n- Minor bugs fixed\\n- Improved stability\\n- Added packet priority for buying and selling\\n\\nv0.8\\n- First public release\\n'},\n",
       " {'repo': 'stratisproject/StratisBitcoinFullNode',\n",
       "  'language': 'C#',\n",
       "  'readme_contents': '# StratisBitcoinFullNode\\n\\nThis repository is now **archived**.\\n\\nThe [StratisFullNode](https://github.com/stratisproject/StratisFullNode) repository is now maintained with a focus on Stratis Blockchain Technology development.\\n'},\n",
       " {'repo': 'Multibit-Legacy/multibit',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': '# Multibit is Deprecated - Do Not Use\\n\\nWednesday, July 26, 2017\\n\\nDear Bitcoin Community,\\n\\nIt is time for us to let Multibit go. \\n\\nKeepKey acquired Multibit a little over 1 year ago. At the time, the engineers who originally built and supported Multibit had announced that they would no longer be working on it or providing support. Multibit played an important role in the Bitcoin infrastructure. We felt that it was important for Multibit to continue and hoped that with our existing support and development teams, we would be able to keep Multibit alive.\\n\\nThe reality is that Multibit is in need of a lot of work. It has stubborn bugs that have caused us and Multibit users much grief. Additionally, Bitcoin has gone through a fundamental change in regards to the way fees work. The addition of SegWit in the coming weeks will mean the Multibit software has fallen still further behind.\\n\\nUnfortunately, KeepKey simply does not have the resources to support the current issues, nor to rebuild Multibit to ensure ideal user experience. By focusing our attention on the KeepKey device, we will continue building and improving the best hardware wallet available.\\n\\nThus, KeepKey will discontinue support and maintenance of Multibit, effective immediately.\\n\\nWe recommend that all Multibit users discontinue using it and you move your keys to other wallet software of your choosing. \\n\\n## Next Steps for Multibit Users \\nVideos that demonstrate how to move your wallet to Electrum are available on YouTube.\\n\\n- Multibit HD: https://youtu.be/E-KcY6KUVnY\\n- Multibit Classic: https://youtu.be/LaijbTcxsv8\\n\\nPlease note that the version of Electrum available for download today (version 2.8.3) doesn’t fully support the importing Multibit HD wallet words. The version shown in the Multibit HD video is the soon-to-be-released next version.\\n\\nMultibit was a fantastic piece of software in its time, and we want to thank the Multibit developers for such an important contribution to Bitcoin’s history.\\n\\nSincerely,\\n\\nKen Heutmaker\\n\\nCTO, KeepKey \\n\\n------\\n\\n### Introduction\\n\\nMultiBit is a Simplified Payment Verification (SPV) Bitcoin desktop client.\\n\\nMultiBit is now in maintenance mode as it has largely been replaced by [MultiBit HD](https://multibit.org). To avoid confusion\\nwe refer to MultiBit Classic and MultiBit HD to keep them separate.\\n\\nMultiBit Classic relies on the following technologies:\\n\\n* Maven as the build system, so the usual Maven processes apply. If you\\'re not familiar\\nwith Maven then [download it first](http://maven.apache.org) and follow their installation instructions.\\n* [ZXing (\"Zebra Crossing\")](https://code.google.com/p/zxing/) for QR codes\\n* [Bitcoinj](https://code.google.com/p/bitcoinj/) for access to the Bitcoin network\\n* Install4j for creating installers for Windows, Mac, Linux\\n* [Bitcoinj Enforcer Rules](https://github.com/gary-rowe/BitcoinjEnforcerRules) to prevent dependency chain attacks\\n* [XChange](https://github.com/timmolter/XChange) for access to several Bitcoin exchanges\\n\\n### The Bitcoinj \"Alice\" dependency\\n\\nMultiBit Classic depends on a special fork of Bitcoinj for its Bitcoin support. This is due to legacy wallet serialization issues\\nand the MultiBit team are working towards a complete integration through the MultiBit HD project.\\n\\nWhile it is possible to build MultiBit Classic using our staging repository you may want to review the modified Bitcoinj library\\nfor yourself. You can clone from this fork:\\n```\\nhttps://code.google.com/r/jimburton618-bitcoinj-coinbase-tx/source/checkout\\n```\\n\\nThe branch you should use for the MultiBit master code is: `bcj-0.11.2-mb-alice`\\nThe branch you should use for the MultiBit develop code is: `bcj-0.11.2-mb-alice`\\n\\nOnce cloned, you should then install the custom Bitcoinj library using\\n\\n```\\nmvn clean install\\n```\\n\\n### Branching strategy\\n\\nThis loosely follows the [\"master-develop\" or \"Git flow\"](http://nvie.com/posts/a-successful-git-branching-model/) pattern.\\n\\nThere are 2 main branches: `master` and `develop`. The `master` branch is exclusively for releases, while the `develop`\\nis exclusively for release candidates. The `develop` branch always has a Maven version of `develop-SNAPSHOT`.\\n\\nOccasionally a feature branch will be made off `develop` to cover a long-running issue. This will then be merged back into `develop`\\n\\nWhen `develop` is ready for release it is subjected to extensive testing (manual and automated). The final act is to update the `pom.xml`\\nto remove the SNAPSHOT suffix and merge it into `master`.\\n\\nThe `master` branch is then tagged with the release number. Tags are in the format `v1.2.3` to distinguish them from branch names.\\n\\nAn announcement is made on the MultiBit website and social media (Twitter, Reddit, Bitcointalk etc) to alert everyone that a new version is available.\\n\\n### Maven build targets\\n\\nThe important targets are:\\n\\n```\\nmvn clean install\\n```\\n\\nAfter some processing, you will have the following artifacts in the target directory:\\n\\n* an executable jar: `multibit-exe.jar`\\n\\n### Bitcoin Solutions staff\\n\\nUse the Install4j installer in the multibit-installers project to create your Mac/ Win/ Linux installers.\\n\\nTo run MultiBit from these artifacts you can follow the instructions [provided on the main MultiBit website](https://multibit.org/help.html)\\n\\n### Custom configuration\\n\\nMultiBit Classic is quite flexible and has several features only accessible to power users through the configuration file. This\\nis discussed in more detail in [configuration.md](configuration.md)\\n\\n### Contributing\\n\\nAll contributors must be OK with releasing their work under the MIT license.\\n'},\n",
       " {'repo': 'benjiqq/bitcoinArchive',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '# bitcoin original sources\\n\\narchive of original bitcoin material\\n\\nOn Sat, 01 Nov 2008 16:16:33 -0700 Satoshi Nakamoto posted the whitepaper bitcoin.pdf. (md5sum d56d71ecadf2137be09d8b1d35c6c042).\\n\\nOn Thu Jan 8 14:27:40 EST 2009 the first version was released. (md5sum dca1095f053a0c2dc90b19c92bd1ec00 ). http://www.metzdowd.com/pipermail/cryptography/2009-January/014994.html.\\n\\nIn november 2008 some sources were distributed privately\\n\\n\"This is the Bitcoin sources from November 16, 2008 - a few months before the current blockchain began.\". \"I was on the Metzdowd cryptography list at that time.\", https://bitcointalk.org/index.php?topic=382374.0 \\n\\nthe private november 2008 version is in the nov08 folder.\\n\\nthe study folder contains the main files of the 0.1 version, roughly 7000 LOC.\\n\\n*  2660 ./main.cpp\\n*  1127 ./script.cpp\\n*  1020 ./net.cpp\\n*   604 ./db.cpp\\n*   554 ./sha.cpp\\n*   373 ./util.cpp\\n*   265 ./irc.cpp\\n*  6603 total'},\n",
       " {'repo': 'bitpay/insight',\n",
       "  'language': 'TypeScript',\n",
       "  'readme_contents': 'THIS PROYECT HAS BEEN REPLACED BY BITCORE-NODE, AT https://github.com/bitpay/bitcore\\n\\n'},\n",
       " {'repo': 'igorbarinov/awesome-bitcoin',\n",
       "  'language': None,\n",
       "  'readme_contents': 'Awesome Bitcoin\\n===============\\nA curated list of bitcoin services and tools for software developers\\n[![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg)](https://github.com/sindresorhus/awesome)\\n\\n## List of content\\n\\n- [Utilities](#utilities)\\n- [Blockchain API and Web services](#blockchain-api-and-web-services)\\n- [Wallets API](#wallets-api)\\n- [Open Source wallets](#open-source-wallets)\\n- [Blockchain Explorers](#blockchain-explorers)\\n- [C++ Libraries](#c-libraries)\\n- [JavaScript Libraries](#javascript-libraries)\\n- [PHP Libraries](#php-libraries)\\n- [Ruby Libraries](#ruby-libraries)\\n- [Python Libraries](#python-libraries)\\n- [Java Libraries](#java-libraries)\\n- [Scala Libraries](#scala-libraries)\\n- [.Net Libraries](#net-libraries)\\n- [Playgrounds](#playgrounds)\\n- [Blockchain dump](#blockchain-dump)\\n- [Full nodes](#full-nodes)\\n- [Read](#read)\\n- [Course](#course)\\n- [Additional Resources](#additional-resources)\\n\\n\\n## Utilities\\n* [Nigiri](https://github.com/vulpemventures/nigiri/) - CLI to quickly fire up a a Bitcoin regtest box along with Electrs and Esplora. Includes faucet and push commands.\\n* [Nigiri in Travis](https://github.com/vulpemventures/nigiri-travis) - Travis template for adding Nigiri to your Travis (or Github Action) pipeline.\\n* [hal](https://github.com/stevenroose/hal) - Bitcoin CLI swiss-army-knife (based on rust-bitcoin).\\n* [BitKey](https://bitkey.io) - Live USB for airgapped transactions and Bitcoin swiss army knife.\\n* [Pycoin](https://github.com/richardkiss/pycoin) - Python-based Bitcoin and alt-coin utility library.\\n* [bx](https://github.com/libbitcoin/libbitcoin-explorer) - Bitcoin Command Line Tool.\\n* [txwatcher](https://github.com/tsileo/txwatcher) - A little Python utility that lets you monitor Bitcoin addresses through Blockchain Websocket API and perform custom callbacks.\\n* [hellobitcoin](https://github.com/prettymuchbryce/hellobitcoin) - A collection of simple programs which can generate bitcoin wallets, create and sign transactions, and send transactions over the bitcoin network.\\n* [Mining visualization](http://www.yogh.io/#mine:last)\\n* [HD Wallet Scanner](https://github.com/alexk111/HD-Wallet-Scanner) - Find all used addresses in your Bitcoin HD wallets bypassing gap limits.\\n* [LibreSelery](https://github.com/protontypes/libreselery) - Automated Bitcoin distribution to your project contributors and dependencies integrated into GitHub Actions. \\n\\n## Blockchain API and Web services\\n* [block.io](https://block.io)\\n* [BlockCypher](https://www.blockcypher.com)\\n* [Esplora](https://github.com/Blockstream/esplora) - Self-hosted blockchain explorer.\\n* [Gem.co](https://gem.co)\\n* [Insight](https://insight.is)\\n* [Chain.com](https://chain.com)\\n* [Coinbase Wallet](https://wallet.coinbase.com/)\\n* [Smartbit](https://www.smartbit.com.au)\\n* [Cashier-BTC](https://github.com/Overtorment/Cashier-BTC) - Self-hosted payment gateway.\\n* [Chainradar API](https://github.com/yasaricli/chainradar-api) - Blockchain Explorer API for Chainradar.\\n* [One-Time Address](https://github.com/alexk111/One-Time-Address) A better way to share your Bitcoin address.\\n\\n## Market Data API\\n* [CoinMetrics.io](https://docs.coinmetrics.io/api/v2/) JSON REST API (free as well as paid) with access to market data. Also CSV data file download available.\\n* [Messari.io](https://messari.io/api) JSON REST API (free as well as paid) with access to market data, news, metrics, profile, etc. \\n\\n## Wallets API\\n* [BitGo](https://bitgo.github.io/bitgo-docs/)\\n* [Coinbase](https://developers.coinbase.com)\\n* [Blockchain.com](https://www.blockchain.com/api)\\n* [BIP32](http://bip32.org)\\n\\n## Open Source Wallets\\n* [CoPay by BitPay](https://copay.io/)\\n* [Coinb.in](https://coinb.in)\\n* [Electrum](https://electrum.org/)\\n\\n## Blockchain Explorers\\n* [Chain.so](http://chain.so)\\n* [Blockchain.com](https://blockchain.com)\\n* [Blockstream.info](https://blockstream.info) - Blockchain explorer with API (mainnet, testnet and Liquid).\\n* [BlockTrail](https://www.blocktrail.com/BTC) \\n* [Bitcoin Transaction Explorer](https://github.com/JornC/bitcoin-transaction-explorer)\\n* [Blockexplorer.com](https://blockexplorer.com)\\n* [Smartbit](https://www.smartbit.com.au)\\n* [Bitkit](https://bitkit.live) - Real time transaction updates.\\n\\n## C++ Libraries\\n* [Libbitcoin](https://libbitcoin.org/)\\n* [libwally-core](https://github.com/ElementsProject/libwally-core)\\n* [secp256k1](https://github.com/bitcoin-core/secp256k1)\\n\\n## JavaScript Libraries\\n* [Awesome CryptoCoinJS](https://github.com/cryptocoinjs/awesome-cryptocoinjs)\\n* [Bitcore Library](https://github.com/bitpay/bitcore/tree/v8.0.0/packages/bitcore-lib)\\n* [Bitcoinjs-lib](https://github.com/bitcoinjs/bitcoinjs-lib)\\n* [Cryptocoin](http://cryptocoinjs.com/#modules)\\n* [BlockTrail SDK NodeJS](https://github.com/blocktrail/blocktrail-sdk-nodejs)\\n* [bcoin](https://github.com/bcoin-org/bcoin) - Javascript bitcoin library for node.js and browsers.\\n* [Libauth](https://libauth.org/) – A lightweight, zero-dependency, JavaScript/TypeScript bitcoin library.\\n\\n## PHP Libraries\\n* [PHP-OP_RETURN](https://github.com/coinspark/php-OP_RETURN)\\n* [BlockTrail PHP SDK](https://github.com/blocktrail/blocktrail-sdk-php)\\n\\n## Ruby Libraries\\n* [Bitcoin-ruby](https://github.com/lian/bitcoin-ruby)\\n\\n## Python Libraries\\n* [BlockTrail SDK Python](https://github.com/blocktrail/blocktrail-sdk-python)\\n* [btctxstore](https://github.com/F483/btctxstore) - Simple library to store/retrieve information in bitcoin transactions using OP_RETURN.\\n* [pybitcointools](https://github.com/vbuterin/pybitcointools) - Python library for Bitcoin signatures and transactions from Vitalik Buterin. Project discontinued.\\n* [pycoin](https://github.com/richardkiss/pycoin) - Python library for Bitcoin keys, signatures, transactions. Includes full VM implementation and tools for manipulating keys (ku) and transactions (tx).\\n* [bitcoin_tools](https://github.com/sr-gi/bitcoin_tools) - Python library for building and analyzing transactions and scripts (both standard and custom). Comes along with a UTXO set analysis tool. Includes several examples and exhaustive documentation.\\n* [oogway](https://github.com/merwane/oogway) - A secure Bitcoin utility library for Python.\\n\\n## Java Libraries\\n> Note that you can also use [Scala libraries](#scala-libraries) in Java.\\n* [BitcoinJ](https://bitcoinj.github.io)\\n* [XChange](https://github.com/knowm/XChange) - Library that provides a simple and consistent API for interacting with 50+ Bitcoin currency exchanges.\\n* [Bitcoin Spring Boot Starter](https://github.com/theborakompanioni/bitcoin-spring-boot-starter) - Bitcoin integration for Spring Boot applications.\\n\\n## Scala libraries\\n> Note that you can also use [Java libraries](#java-libraries) in Scala.\\n* [Bitcoin-S](https://bitcoin-s.org) - Scala/JVM toolkit for Bitcoin applications, includes Bitcoin data structures, transaction signing, strongly typed `bitcoind`/Eclair RPC clients, and more.\\n\\n## .Net Libraries\\n* [NBitcoin](https://github.com/MetacoSA/NBitcoin) - Comprehensive Bitcoin library for the .NET framework.\\n* [BitcoinLib](https://github.com/cryptean/bitcoinlib) - The most complete, up-to-date, battle-tested .net Library and RPC Wrapper for Bitcoin and Altcoins in C#.\\n* [QBitNinja](https://github.com/MetacoSA/QBitNinja) - An Open Source and powerful blockchain API.\\n\\n## Playgrounds\\n* [Script Playground](https://www.crmarsh.com/script-playground/)\\n* [Bitcoin IDE](https://github.com/siminchen/bitcoinIDE) - Bitcoin Script for dummies.\\n* [Script Debugger](https://github.com/kallewoof/btcdeb)\\n* [Bitcore Playground](https://bitcore.io/playground/)\\n* [Mnemonic Code generator](https://iancoleman.io/bip39/)\\n* [blockchain-demo](https://github.com/anders94/blockchain-demo/) - A web-based demonstration of blockchain concepts.\\n* [Bitcoin Script Debugger](https://github.com/liuhongchao/bitcoin4s) - Visualize Bitcoin script execution for real transactions.\\n* [Bitauth IDE](https://ide.bitauth.com/) – An interactive development environment for Bitcoin contracts.\\n* [ChainQuery Bitcoin RPC](https://chainquery.com) - Run select bitcoin RPC API calls and read full RPC docs in your browser.\\n\\n## Blockchain dump\\n* [WebBTC](http://dumps.webbtc.com/bitcoin/) - These are postgres database dumps of the bitcoin-ruby-blockchain database generated by webbtc.com.\\n* [BitcoinDatabaseGenerator](https://github.com/ladimolnar/BitcoinDatabaseGenerator) - A high performance data transfer tool that can be used to copy data from Bitcoin Core blockchain files to a SQL Server database.\\n* [Blockparser+SQL](https://github.com/mcdee/blockparser) - Fast, quick and dirty bitcoin blockchain parser.\\n* [BitcoinABE](https://github.com/bitcoin-abe/bitcoin-abe) - Abe: block browser for Bitcoin and similar currencies.\\n* [NBitcoin.Indexer](https://github.com/MetacoSA/NBitcoin.Indexer) - Scalable and fault-tolerant block chain indexer for Azure cloud platform.\\n* [Blockchain2Graph](https://github.com/straumat/blockchain2graph) - Graph Database Builder.\\n* [Chaingraph](https://github.com/bitauth/chaingraph/) – A multi-node blockchain indexer and GraphQL API.\\n\\n## Full nodes\\n* [btcd](https://github.com/btcsuite/btcd/) - Go-based full node since 2013.\\n* [Bitcoin-ruby-node](https://github.com/mhanne/bitcoin-ruby-node) - bitcoin node based on bitcoin-ruby-blockchain.\\n* [Fullnode](https://github.com/moneybutton/yours-bitcoin) - Javascript implementation of bitcoin.\\n* [Bitcore Node](https://github.com/bitpay/bitcore-node) - bitcoind linked to node.js by BitPay.\\n* [Bitcore](https://github.com/bitpay/bitcore) - Formerly just a Nodejs library, now a full node.\\n\\n## Read\\n* [A Gentle Introduction to Bitcoin Core Development](https://bitcointechtalk.com/a-gentle-introduction-to-bitcoin-core-development-fdc95eaee6b8)\\n* [Mastering Bitcoin](https://github.com/bitcoinbook/bitcoinbook)\\n* [Grokking Bitcoin](https://www.manning.com/books/grokking-bitcoin) - An in-depth technical book with rich illustrations.\\n* [Bitcoin Stackexchange](https://bitcoin.stackexchange.com)\\n* [Elliptic Curve Cryptography A Gentle Introduction](https://andrea.corbellini.name/2015/05/17/elliptic-curve-cryptography-a-gentle-introduction/).\\n* [Bitcoin Programming with BitcoinJS and Bitcoin Core CLI](https://github.com/bitcoin-studio/Bitcoin-Programming-with-BitcoinJS).\\n* [Bitcoin Protocol Development Curriculum - Chaincode Labs](https://github.com/chaincodelabs/bitcoin-curriculum).\\n* [Lightning Network Protocol Development Curriculum - Chaincode Labs](https://github.com/chaincodelabs/lightning-curriculum).\\n* [btcinformation.org / Developer Documentation](https://btcinformation.org/en/developer-documentation) - Find useful resources, guides and reference material for developers.\\n\\n## Course\\n* [Bitcoin & Cryptocurrency](http://bitcoinbook.cs.princeton.edu/).\\n\\n## Additional Resources\\n* [@lopp / Bitcoin Developers](https://twitter.com/lopp/lists/bitcoin-developers) - Software developers who have experience working on Bitcoin implementations or applications.\\n* [@lopp / Lightning Developers](https://twitter.com/lopp/lists/lightning-developers) - Software developers with experience working on LN implementations / applications.\\n* [Practical Bitcoin Info - Google Sheets](https://docs.google.com/spreadsheets/d/1Z3Ofa4P8097VWV70Z_bMqIMladngvm-Ck24ot9TDNmw/).\\n* [A brief history of Bitcoin development...](https://www.youtube.com/watch?v=ZfFNce6CVsE)\\n* [bitcoin-resources.com](https://bitcoin-resources.com/) Meta-list of Bitcoin resources, from books, articles, to podcasts.\\n* [Jameson Lopp Bitcoin Resource List](https://www.lopp.net/bitcoin-information.html) Very detailed curated Bitcoin resource list and meta-list by J. Lopp\\n* [River Learn](https://river.com/learn) A collection of educational resources to learn about Bitcoin basics, investing, technology, and more.\\n---\\n\\nInspired by the [awesome](https://github.com/sindresorhus/awesome) list thing.\\nCreated by BlockchainU fellows.\\n\\n---\\n\\n### License\\n\\n[![CC0](https://i.creativecommons.org/p/zero/1.0/88x31.png)](https://creativecommons.org/publicdomain/zero/1.0/)\\n\\nTo the extent possible under law, [Igor Barinov](https://github.com/igorbarinov/) has waived all copyright and related or neighboring rights to this work.\\n'},\n",
       " {'repo': 'BitcoinPHP/BitcoinECDSA.php',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': '[![Build](https://travis-ci.org/BitcoinPHP/BitcoinECDSA.php.svg?branch=master)](https://travis-ci.org/BitcoinPHP/BitcoinECDSA.php) &nbsp;\\n[![Quality Score](https://scrutinizer-ci.com/g/BitcoinPHP/BitcoinECDSA.php/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/BitcoinPHP/BitcoinECDSA.php/?branch=master) &nbsp;\\n[![Latest Stable Version](https://poser.pugx.org/bitcoin-php/bitcoin-ecdsa/v/stable.svg)](https://packagist.org/packages/bitcoin-php/bitcoin-ecdsa) &nbsp;\\n[![Downloads](http://img.shields.io/packagist/dt/bitcoin-php/bitcoin-ecdsa.svg?style=flat)](https://packagist.org/packages/bitcoin-php/bitcoin-ecdsa)\\n\\n\\nWARNING\\n===============\\n\\nThis piece of software is provided without warranty of any kind, use it at your own risk.\\n\\nREQUIREMENTS\\n===============\\n\\n*php 5.4.0* or newer.\\n\\n*php5-gmp* needs to be installed.\\n\\nIf you want to launch the test file you need to be under a unix system with libbitcoin intalled on it.\\n\\nUSAGE\\n===============\\n\\n**Installation**\\n\\nBest way is to use composer\\n```\\ncomposer require bitcoin-php/bitcoin-ecdsa\\n```\\nAlternatively add following snippet in you composer.json\\n```\\n\"bitcoin-php/bitcoin-ecdsa\" : \">=1.3\"\\n```\\n\\n**Instanciation**\\n\\n```php\\nuse BitcoinPHP\\\\BitcoinECDSA\\\\BitcoinECDSA;\\nrequire_once(\"src/BitcoinPHP/BitcoinECDSA/BitcoinECDSA.php\");\\n$bitcoinECDSA = new BitcoinECDSA();\\n```\\n\\n**Set a private key**\\n\\n```php\\n$bitcoinECDSA->setPrivateKey($k);\\n```\\nexamples of private keys :\\n\\n4C28FCA386C7A227600B2FE50B7CAE11EC86D3BF1FBE471BE89827E19D72AA1D\\n00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC\\n\\n**Generate a random private key**\\n\\n```php\\n$bitcoinECDSA->generateRandomPrivateKey($nonce);\\n```\\n\\nThe nonce is optional, typically the nonce is a chunck of random data you get from the user. This can be mouse coordinates.\\nUsing a nonce adds randomness, which means the generated private key is stronger.\\n\\n**Get the private key**\\n\\n```php\\n$bitcoinECDSA->getPrivateKey();\\n```\\n\\nReturns the private key.\\n\\n**Get the Wif**\\n\\n```php\\n$bitcoinECDSA->getWif();\\n```\\n\\nreturns the private key under the Wallet Import Format\\n\\n\\n**Get the Public Key**\\n\\n```php\\n$bitcoinECDSA->getPubKey();\\n```\\nReturns the compressed public key.\\nThe compressed PubKey starts with 0x02 if it\\'s y coordinate is even and 0x03 if it\\'s odd, the next 32 bytes corresponds to the x coordinates.\\n\\nExample : 0226c50013603b085fbc26411d5d7e564b252d88964eedc4e01251d2d495e92c29\\n\\n**Get the Uncompressed Public Key**\\n\\n```php\\n$bitcoinECDSA->getUncompressedPubKey();\\n```\\n\\nReturns the uncompressed PubKey.\\nThe uncompressed PubKey starts with 0x04, the next 32 bytes are the x coordinates, the last 32 bytes are the y coordinates.\\n\\nExample : 04c80e8af3f1b7816a18aa24f242fc0740e9c4027d67c76dacf4ce32d2e5aace241c426fd288a9976ca750f1b192d3acd89dfbeca07ef27f3e5eb5d482354c4249\\n\\n**Get the coordinates of the Public Key**\\n\\n```php\\n$bitcoinECDSA->getPubKeyPoints();\\n```\\n\\nReturns an array containing the x and y coordinates of the public key\\n\\nExample :\\nArray ( [x] => a69243f3c4c047aba38d7ac3660317629c957ab1f89ea42343aee186538a34f8 [y] => b6d862f39819060378542a3bb43ff76b5d7bb23fc012f09c3cd2724bebe0b0bd ) \\n\\n**Get the Address**\\n\\n```php\\n$bitcoinECDSA->getAddress();\\n```\\n\\nReturns the compressed Bitcoin Address.\\n\\n**Get the uncompressed Address**\\n\\n```php\\n$bitcoinECDSA->getUncompressedAddress();\\n```\\n\\nReturns the uncompressed Bitcoin Address.\\n\\n\\n**Validate an address**\\n\\n```php\\n$bitcoinECDSA->validateAddress($address);\\n```\\nReturns true if the address is valid and false if it isn\\'t\\n\\n\\n**Validate a Wif key**\\n\\n```php\\n$bitcoinECDSA->validateWifKey($wif);\\n```\\nReturns true if the WIF key is valid and false if it isn\\'t\\n\\n\\nSignatures\\n===============\\n\\n**Sign a message**\\n\\n```php\\n$bitcoinECDSA->signMessage(\\'message\\');\\n```\\n\\nReturns a satoshi client standard signed message.\\n\\n\\n**verify a message**\\n\\n```php\\n$bitcoinECDSA->checkSignatureForRawMessage($signedMessage);\\n```\\n\\nReturns true if the signature is matching the address and false if it isn\\'t.\\n\\n\\n**sign a sha256 hash**\\n\\n```php\\n$bitcoinECDSA->signHash($hash);\\n```\\n\\nReturns a DER encoded hexadecimal signature.\\n\\n\\n**verify a signature**\\n\\n```php\\n$bitcoinECDSA->checkDerSignature($pubKey, $signature, $hash)\\n```\\n\\nReturns true if the signature is matching the public key and false if it isn\\'t.\\n\\nExamples\\n===============\\n - [Generate an address](https://github.com/BitcoinPHP/BitcoinECDSA.php/blob/master/Examples/generateAddress.php)\\n - [Sign a message](https://github.com/BitcoinPHP/BitcoinECDSA.php/blob/master/Examples/signMessage.php)\\n - [Verify a message](https://github.com/BitcoinPHP/BitcoinECDSA.php/blob/master/Examples/verifyMessage.php)\\n - [Import or export a private key using WIF](https://github.com/BitcoinPHP/BitcoinECDSA.php/blob/master/Examples/wif.php)\\n\\nLicense\\n===============\\nThis is free and unencumbered software released into the public domain.\\n\\nAnyone is free to copy, modify, publish, use, compile, sell, or\\ndistribute this software, either in source code form or as a compiled\\nbinary, for any purpose, commercial or non-commercial, and by any\\nmeans.\\n\\nIn jurisdictions that recognize copyright laws, the author or authors\\nof this software dedicate any and all copyright interest in the\\nsoftware to the public domain. We make this dedication for the benefit\\nof the public at large and to the detriment of our heirs and\\nsuccessors. We intend this dedication to be an overt act of\\nrelinquishment in perpetuity of all present and future rights to this\\nsoftware under copyright law.\\n\\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND,\\nEXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF\\nMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.\\nIN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR\\nOTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,\\nARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR\\nOTHER DEALINGS IN THE SOFTWARE.\\n\\nFor more information, please refer to <http://unlicense.org/>\\n'},\n",
       " {'repo': 'MetacoSA/NBitcoin',\n",
       "  'language': 'C#',\n",
       "  'readme_contents': '# NBitcoin\\n\\n[![Join the chat at https://gitter.im/MetacoSA/NBitcoin](https://badges.gitter.im/MetacoSA/NBitcoin.svg)](https://gitter.im/MetacoSA/NBitcoin?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\\n[![Build status](https://github.com/MetacoSA/NBitcoin/workflows/CI/badge.svg)](https://github.com/MetacoSA/NBitcoin/actions?query=workflow%3ACI)\\n\\nNBitcoin is the most complete Bitcoin library for the .NET platform. It implements all most relevant Bitcoin Improvement Proposals (BIPs). It also provides low level access to Bitcoin primitives so you can easily build your application on top of it. Join us in our [gitter chat room](https://gitter.im/MetacoSA/NBitcoin).\\nIt works on Windows, Mac and Linux with Xamarin, Unity, .NET Core or CLR. (Porting to Unity should not be that hard if you need it)\\n\\nThe best documentation available is our [eBook](https://programmingblockchain.gitbooks.io/programmingblockchain/content/), and the excellent unit tests. There are also some more resources below.\\n\\nYou can also browse the API easily through [the API reference](https://metacosa.github.io/NBitcoin/api/index.html).\\n\\n# How to use ?\\n\\nIn .NET Core:\\n```bash\\ndotnet add package NBitcoin\\n```\\nIf using legacy .NET Framework in Visual Studio\\n```bash\\nInstall-Package NBitcoin\\n```\\nYou can also just use the `Manage NuGet Package` window on your project in Visual Studio.\\n\\nGo on the [NuGet website](https://www.nuget.org/packages/NBitcoin/) for more information.\\n\\nThe packages support:\\n\\n* With full features: Windows Desktop applications, Mono Desktop applications and platforms supported by [.NET Standard 1.3](https://docs.microsoft.com/en-us/dotnet/articles/standard/library) (.NET Core, Xamarin IOS, Xamarin Android, UWP and more).\\n* With limited features: platforms supported by [.NET Standard 1.1](https://docs.microsoft.com/en-us/dotnet/articles/standard/library) (Windows Phone, Windows 8.0 apps).\\n\\nTo compile it by yourself, you can git clone, open the project and hit the compile button in Visual Studio.\\n\\n\\n # How to get started? \\n \\n First, you need to understand Bitcoin, for this read:\\n * [Programming The Blockchain in C#](https://programmingblockchain.gitbooks.io/programmingblockchain/content/)\\n\\n Once you get familiar with Bitcoin terminology with this book, follow up by reading:\\n\\n * [NBitcoin documentation](https://github.com/NicolasDorier/NBitcoin.Docs/blob/master/README.md)\\n\\n This will teach you how to use NBitcoin in a practical way.\\n\\n# How to use with Altcoins ?\\n\\n> **Install-Package NBitcoin.Altcoins** \\n\\nFind more information [here](NBitcoin.Altcoins).\\n\\n# How to debug in NBitcoin source code?\\n\\nWhen a new version of `NBitcoin`, `NBitcoin.Altcoins` or `NBitcoin.TestFramework` is released on Nuget, we also upload a separate symbol package (`snupkg`) with SourceLink enabled. This is enabled from version `4.1.1.73`.\\n\\nThis means that it is possible to debug into NBitcoin code, and the source will be fetched transparently from github.\\n\\nThis works on both Visual Studio Code and Visual Studio for Windows.\\n\\n## Debug inside source with Visual Studio\\n\\nYou need to run at least Visual Studio 15.9.\\nThen, you need to:\\n\\n* Go in `Tools / Options / Debugging / General` and turn off `Enable Just My Code`.\\n* Go in `Tools / Options / Debugging / Symbols` and add `https://symbols.nuget.org/download/symbols` to the `Symbol file (.pdb) locations`, make sure it is checked.\\n\\nYou should also check `Microsoft Symbol Server` or your debugging experience in visual studio will be slowed down.\\n\\nNow you can Debug your project and step inside any call to NBitcoin.\\n\\n## Debug inside source with Visual Studio Code\\n\\nInside your `launch.json`, add the following to `.NET Core Launch (console)` configuration:\\n\\n```json\\n\"justMyCode\": false,\\n\"symbolOptions\": {\\n    \"searchPaths\": [ \"https://symbols.nuget.org/download/symbols\" ],\\n    \"searchMicrosoftSymbolServer\": true\\n},\\n```\\n\\nNow you can Debug your project and step inside any call to NBitcoin.\\n\\n# How to use with my own blockchain?\\n\\n Find more information [here](NBitcoin.Altcoins).\\n\\n# How to use in Unity?\\n\\nYou should use at least `Unity 2018.2` using `Script Runtime Version` `.NET 4.x Equivalent` and `Api Compatibility Level` `.NET Standard 2.0`.\\nYou can see more on [this post](https://blogs.unity3d.com/2018/07/11/scripting-runtime-improvements-in-unity-2018-2/).\\n\\nThen you need to compile NBitcoin:\\n\\n```powershell\\ngit clone https://github.com/MetacoSA/NBitcoin/\\ncd NBitcoin/NBitcoin\\ndotnet publish -c Release -f netstandard2.0\\nRemove-Item -Force -Recurse .\\\\bin\\\\Release\\\\netstandard2.0\\\\publish\\\\runtimes\\\\\\n```\\n\\nThen put the libraries of `.\\\\bin\\\\Release\\\\netstandard2.0` into your asset folder.\\n\\nIf you need altcoins support, use the same step but with `cd NBitcoin/NBitcoin.Altcoins` instead.\\n\\n# How to use in .NET Core\\n\\nIf you want to use .NET Core, first install .NET Core [as documented here](https://www.microsoft.com/net/core#windowsvs2017).\\n\\nThen:\\n```\\nmkdir MyProject\\ncd MyProject\\ndotnet new console\\ndotnet add package NBitcoin\\ndotnet restore\\n```\\nThen edit your Program.cs:\\n```\\nusing System;\\nusing NBitcoin;\\n\\nnamespace _125350929\\n{\\n    class Program\\n    {\\n        static void Main(string[] args)\\n        {\\n            Console.WriteLine(\"Hello World! \" + new Key().GetWif(Network.Main));\\n        }\\n    }\\n}\\n```\\nYou can then run with\\n```\\ndotnet run\\n```\\n\\nWe advise you to use [Visual Studio Code](https://code.visualstudio.com/) as the editor for your project.\\n\\n## Description\\nNBitcoin notably includes:\\n\\n* A [TransactionBuilder](http://www.codeproject.com/Articles/835098/NBitcoin-Build-Them-All) supporting Stealth, Open Asset, and all standard transactions\\n* Full script evaluation and parsing\\n* A RPC Client\\n* A Rest Client\\n* The parsing of standard scripts and creation of custom ones\\n* The serialization of blocks, transactions and scripts\\n* The signing and verification with private keys (with support for compact signatures) for proving ownership\\n* Bloom filters and partial merkle trees\\n* Segregated Witness ([BIP 141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki), [BIP 143](https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki), [BIP 144](https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki))\\n* Bech32 segwit address implementation with error detection [BIP 173](https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki)\\n* Mnemonic code for generating deterministic keys ([BIP 39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki)), credits to [Thasshiznets](https://github.com/Thashiznets/BIP39.NET)\\n* Hierarchical Deterministic Wallets ([BIP 32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki))\\n* Payment URLs ([BIP 21](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki))\\n* Full Bitcoin P2P implementation with SOCKS5 support for connecting through Tor\\n* [A C# implementation of secp256k1](NBitcoin.Secp256k1/README.md)\\n\\nPlease read our [ebook](https://programmingblockchain.gitbooks.io/programmingblockchain/content/) to understand the capabilities.\\n\\nNBitcoin is inspired by Bitcoin Core code but provides a simpler object oriented API (e.g., new Key().PubKey.Address.ToString() to generate a key and get the associated address). It relies on the BouncyCastle cryptography library instead of OpenSSL, yet replicates OpenSSL bugs to guarantee compatibility. NBitcoin also ports the integrality of Bitcoin Core unit tests with their original data in order to validate the compatibility of the two implementations.\\n\\nNBitcoin is licensed under the [MIT License](https://opensource.org/licenses/MIT) and we encourage you to use it to explore, learn, debug, play, share and create software for Bitcoin and with other Metaco services.\\n\\n## How to connect use a SOCKS5 proxy to connect to a Bitcoin node?\\n\\nHere an example which assume you run Tor with SOCKS5 proxy on port 9050.\\n```csharp\\nvar connectionParameters = new NodeConnectionParameters();\\nconnectionParameters.TemplateBehaviors.Add(new SocksSettingsBehavior(Utils.ParseEndpoint(\"localhost\", 9050)));\\nNode node = await Node.ConnectAsync(Network.Main, \"7xnmrhmkvptbcvpl.onion:8333\", connectionParameters);\\nnode.VersionHandshake();\\n```\\n\\n## Some OSS projects using NBitcoin\\n\\n* [Wasabi](http://github.com/zkSNACKs/WalletWasabi): Privacy focused, ZeroLink compliant Bitcoin wallet.\\n\\n* [StratisBitcoinFullNode](http://github.com/stratisproject/StratisBitcoinFullNode): Bitcoin full node in C# https://stratisplatform.com\\n\\n* [Breeze](http://github.com/stratisproject/Breeze): Breeze Wallet, the first full-block SPV bitcoin wallet \\n\\n* [BlockExplorer](http://github.com/stratisproject/BlockExplorer): A set of projects that can index and query stratis blockchains on the fullnode. \\n\\n* [BTCPay Server](http://github.com/btcpayserver/btcpayserver): A cross platform, self-hosted server compatible with Bitpay API \\n\\n* [NTumbleBit](http://github.com/NTumbleBit/NTumbleBit): TumbleBit Implementation in .NET Core \\n\\n* [BitPoker](http://github.com/bitcoinbrisbane/BitPoker): Decentralised peer to peer poker, using bitcoin http://www.bitpoker.io\\n\\n* [Zen-Wallet](http://github.com/zenprotocol/zen-wallet): Node and GUI for the Zen Protocol. https://www.zenprotocol.com\\n\\n* [Metaco-Trader](http://github.com/MetacoSA/Metaco-Trader): Bitcoin Wallet for advanced user based on a NBitcoin.Server \\n\\n* [Swarmops](http://github.com/Swarmops/Swarmops): Admin backend for any bitcoin-native or swarm organization http://sandbox.swarmops.com/\\n\\n* [Nako](http://github.com/CoinVault/Nako): A Bitcoin and Altcoin server api that indexes blockchain transactions and addresses \\n\\n* [NBXplorer](http://github.com/dgarage/NBXplorer): A minimalist UTXO tracker for HD Wallets with bitcoin based altcoin support \\n\\n* [UnitCurrency](http://github.com/unitcurrency/unitcurrency): UnitCoin - a hybrid scrypt PoW + PoS based cryptocurrency.\\n\\n* [Openchain](http://github.com/openchain/openchain): Openchain node reference implementation. https://www.openchain.org/\\n\\n* [BreezeProject](http://github.com/BreezeHub/BreezeProject): Breeze Masternode and Wallet with Breeze Privacy Protocol \\n\\n* [geewallet](https://gitlab.com/nblockchain/geewallet/): Non-custodial, minimalistic & pragmatist opensource crossplatform lightweight brainwallet to hold the most important cryptoassets in the same application with ease & peace of mind\\n\\n* [blockcore](https://github.com/block-core/blockcore): Modular Bitcoin fullnode implementation. https://www.blockcore.net/\\n\\n## Useful doc :\\n\\n* **Ebook** [Programming The Blockchain in C#](https://www.gitbook.com/book/programmingblockchain/programmingblockchain/details)\\n\\n* **NBitcoin Github** : [https://github.com/NicolasDorier/NBitcoin](https://github.com/NicolasDorier/NBitcoin \"https://github.com/NicolasDorier/NBitcoin\")\\n\\n* **NBitcoin Nuget** : [https://www.nuget.org/packages/NBitcoin/](https://www.nuget.org/packages/NBitcoin/ \"https://www.nuget.org/packages/NBitcoin/\")\\n\\n* **Intro**: [http://www.codeproject.com/Articles/768412/NBitcoin-The-most-complete-Bitcoin-port-Part-Crypt](http://www.codeproject.com/Articles/768412/NBitcoin-The-most-complete-Bitcoin-port-Part-Crypt)\\n\\n* **Stealth Payment**, and **BIP38** : [http://www.codeproject.com/Articles/775226/NBitcoin-Cryptography-Part](http://www.codeproject.com/Articles/775226/NBitcoin-Cryptography-Part)\\n\\n* **How to build transaction** : [http://www.codeproject.com/Articles/835098/NBitcoin-Build-Them-All](http://www.codeproject.com/Articles/835098/NBitcoin-Build-Them-All \"http://www.codeproject.com/Articles/835098/NBitcoin-Build-Them-All\")\\n\\n* **Using the NBitcoin Indexer** : [http://www.codeproject.com/Articles/819567/NBitcoin-Indexer-A-scalable-and-fault-tolerant-blo](http://www.codeproject.com/Articles/819567/NBitcoin-Indexer-A-scalable-and-fault-tolerant-blo \"http://www.codeproject.com/Articles/819567/NBitcoin-Indexer-A-scalable-and-fault-tolerant-blo\")\\n\\n* **How to Scan the blockchain** : [http://www.codeproject.com/Articles/784519/NBitcoin-How-to-scan-the-Blockchain](http://www.codeproject.com/Articles/784519/NBitcoin-How-to-scan-the-Blockchain \"http://www.codeproject.com/Articles/784519/NBitcoin-How-to-scan-the-Blockchain\") (You can dismiss the ScanState for that, now I concentrate on the indexer)\\n\\nPlease, use github issues for questions or feedback. For confidential requests or specific demands, contact us on [Metaco support](mailto:support@metaco.com \"support@metaco.com\").\\n\\n\\n## Useful link for a free IDE :\\nVisual Studio Community Edition : [https://www.visualstudio.com/products/visual-studio-community-vs](https://www.visualstudio.com/products/visual-studio-community-vs \"https://www.visualstudio.com/products/visual-studio-community-vs\")\\n'},\n",
       " {'repo': 'bitcoincashorg/bitcoincash.org',\n",
       "  'language': 'CSS',\n",
       "  'readme_contents': '<p align=\"center\">\\n  <a href=\"https://bitcoincash.org\">\\n    <img src=\"https://www.bitcoincash.org/media-kit/3-bitcoin-cash-logo-ot-small.png\" height=\"110\" alt=\"Bitcoin Cash\">\\n  </a>\\n</p>\\n\\n<h5 align=\"center\">\\n  Repository for <a href=\"https://bitcoincash.org\">BitcoinCash.org</a>\\n</h5>\\n\\n#\\n\\nBitcoin Cash is a peer-to-peer version of electronic money allowing payments to be sent directly from one party to another instantly and almost for free without going through a financial institution.\\n\\n### How to run the site locally\\n\\n**Note**: *BitcoinCash.org is changing to Gatsby. See the [README in the v2 directory](./v2) to see the new installation instructions. The instructions below are for the older version of the site.*\\n\\nIn order to build and run the site you need Ruby 💎 and Docker 🐳. Then run:\\n\\n```shell\\ngem install bundler\\nbundle install\\n\\n# run the development server with:\\nmake serve\\n\\n# or test the Docker container with:\\nmake run\\n\\n# or test the v2 build with:\\nmake run APP_VERSION=2\\n```\\n\\nOpen a browser to `localhost:4000` or `localhost:8080` respectively.\\n\\nYou can then submit pull requests to this repository.\\n\\n### Listing Policy for Exchanges, Wallets, and Projects\\n\\nBitcoinCash.org is not meant to be an exhaustive directory.  \\nThere is limited space and quite simply, we only want to showcase the best of the best.  \\nIf you think your project should be listed on BitcoinCash.org, simply submit a pull request.\\n\\nWe apologize in advance if we\\'re unable to provide a listing for you on BitcoinCash.org.  \\nLastly, no listing should be interpreted as our explicit endorsement.\\n\\n### License\\n\\nbitcoincash.org is released under the terms of the MIT license. See [COPYING](COPYING) for more\\ninformation or see https://opensource.org/licenses/MIT.\\n'},\n",
       " {'repo': 'p2pool/p2pool',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': 'Requirements:\\n-------------------------\\nGeneric:\\n* Bitcoin >=0.11.1\\n* Python >=2.6\\n* Twisted >=10.0.0\\n* python-argparse (for Python =2.6)\\n\\nLinux:\\n* sudo apt-get install python-zope.interface python-twisted python-twisted-web\\n* sudo apt-get install python-argparse # if on Python 2.6\\n\\nWindows:\\n* Install [Python 2.7](http://www.python.org/getit/)\\n* Install [Twisted](http://twistedmatrix.com/trac/wiki/Downloads)\\n* Install [Zope.Interface](http://pypi.python.org/pypi/zope.interface/3.8.0)\\n* Install [python win32 api](http://sourceforge.net/projects/pywin32/files/pywin32/Build%20218/)\\n* Install [python win32 api wmi wrapper](https://pypi.python.org/pypi/WMI/#downloads)\\n* Unzip the files into C:\\\\Python27\\\\Lib\\\\site-packages\\n\\nRunning P2Pool:\\n-------------------------\\nTo use P2Pool, you must be running your own local bitcoind. For standard\\nconfigurations, using P2Pool should be as simple as:\\n\\n    python run_p2pool.py\\n\\nThen run your miner program, connecting to 127.0.0.1 on port 9332 with any\\nusername and password.\\n\\nIf you are behind a NAT, you should enable TCP port forwarding on your\\nrouter. Forward port 9333 to the host running P2Pool.\\n\\nRun for additional options.\\n\\n    python run_p2pool.py --help\\n\\nDonations towards further development:\\n-------------------------\\n    1HNeqi3pJRNvXybNX4FKzZgYJsdTSqJTbk\\n\\nOfficial wiki:\\n-------------------------\\nhttps://en.bitcoin.it/wiki/P2Pool\\n\\nAlternate web frontend:\\n-------------------------\\n* https://github.com/hardcpp/P2PoolExtendedFrontEnd\\n\\nNotes for Litecoin:\\n=========================\\nRequirements:\\n-------------------------\\nIn order to run P2Pool with the Litecoin network, you would need to build and install the\\nltc_scrypt module that includes the scrypt proof of work code that Litecoin uses for hashes.\\n\\nLinux:\\n\\n    cd litecoin_scrypt\\n    sudo python setup.py install\\n\\nWindows (mingw):\\n* Install MinGW: http://www.mingw.org/wiki/Getting_Started\\n* Install Python 2.7: http://www.python.org/getit/\\n\\nIn bash type this:\\n\\n    cd litecoin_scrypt\\n    C:\\\\Python27\\\\python.exe setup.py build --compile=mingw32 install\\n\\nWindows (Microsoft Visual C++)\\n* Open visual studio console\\n\\nIn bash type this:\\n\\n    SET VS90COMNTOOLS=%VS110COMNTOOLS%\\t           # For visual c++ 2012\\n    SET VS90COMNTOOLS=%VS100COMNTOOLS%             # For visual c++ 2010\\n    cd litecoin_scrypt\\n    C:\\\\Python27\\\\python.exe setup.py build --compile=mingw32 install\\n\\t\\nIf you run into an error with unrecognized command line option \\'-mno-cygwin\\', see this:\\nhttp://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o\\n\\nRunning P2Pool:\\n-------------------------\\nRun P2Pool with the \"--net litecoin\" option.\\nRun your miner program, connecting to 127.0.0.1 on port 9327.\\nForward port 9338 to the host running P2Pool.\\n\\nLitecoin\\'s use of ports 9333 and 9332 conflicts with P2Pool running on\\nthe Bitcoin network. To avoid problems, add these lines to litecoin.conf\\nand restart litecoind:\\n\\n    rpcport=10332\\n    port=10333\\n\\nSponsors:\\n-------------------------\\n\\nThanks to:\\n* The Bitcoin Foundation for its generous support of P2Pool\\n* The Litecoin Project for its generous donations to P2Pool\\n \\nLicense:\\n-------------------------\\n\\n[Available here](COPYING)\\n\\n\\n'},\n",
       " {'repo': 'buttercoin/buttercoin',\n",
       "  'language': 'CoffeeScript',\n",
       "  'readme_contents': \"This project is deprecated— we encourage you to fork it and continue the work\\n=============================================================================\\n\\n\\nButtercoin\\n==========\\n### An Open Source Bitcoin Exchange\\n\\nCopyright &copy; 2013 Buttercoin Developers\\n\\nWhat is Buttercoin?\\n-------------------\\n\\nFollowing the events of April 2013 in which Bitcoin value dropped dramatically as a result of the short comings of existing exchanges it was decided that there should be a community driven and open source exchange. As such Buttercoin was born out of neccesity for this. Buttercoin allows the decentralisation of exchange between Bitcoin and other currencies.\\n\\nLicense\\n-------\\n\\nButtercoin is released under the terms of the MIT license. See `LICENCE` for more\\ninformation or see http://opensource.org/licenses/MIT.\\n\\nDevelopment process\\n-------------------\\n\\nDevelopers work in their own trees, then submit pull requests when they are **sure**\\ntheir feature or bug fix is ready.\\n\\nThe patch will be accepted if there is broad consensus that it is a good thing.\\nDevelopers should expect to rework and resubmit patches if the code doesn't\\nmatch the project's coding conventions or are controversial.\\n\\nThe `master` branch is regularly built and tested, but is not guaranteed to be\\ncompletely stable.\\n\\nThis is an open project and all are encouraged to contribute.\\n\\nTesting\\n-------\\n\\n### Automated Testing\\n\\nDevelopers are strongly encouraged to write unit tests for new code, and to\\nsubmit new unit tests for old code.\\n\\nUnit tests for the core code are in `test/`. \\n\\nDiscussion\\n----------\\n\\n* [Original Post on Reddit](http://www.reddit.com/r/Bitcoin/comments/1c7v6z/buttercoin_open_source_highperformance_bitcoin/)\\n* [/r/buttercoin](http://www.reddit.com/r/buttercoin)\\n* [#buttercoin](irc://irc.freenode.org/buttercoin)\\n* [#buttercoin-dev](irc://irc.freenode.org/buttercoin-dev)\\n* [Hackpad](https://buttercoin.hackpad.com/)\\n* [Trello](https://trello.com/board/buttercoin/516af0ca86d48fe14f0022ab)\\n\\n[![Build Status](https://travis-ci.org/buttercoin/buttercoin.png)](https://travis-ci.org/buttercoin/buttercoin)\\n\"},\n",
       " {'repo': 'bitpay/bitcore',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# Bitcore Monorepo\\n\\n  <p align=\"center\">\\n  <img alt=\"npm\" src=\"https://img.shields.io/npm/v/bitcore-lib\">\\n  <img alt=\"GitHub commit activity\" src=\"https://img.shields.io/github/commit-activity/m/bitpay/bitcore\">\\n  <a href=\"https://opensource.org/licenses/MIT/\" target=\"_blank\"><img alt=\"MIT License\" src=\"https://img.shields.io/badge/License-MIT-blue.svg\" style=\"display: inherit;\"/></a>\\n  <img alt=\"GitHub contributors\" src=\"https://img.shields.io/github/contributors/bitpay/bitcore\">\\n  <br>\\n <img src=\"https://circleci.com/gh/bitpay/bitcore.svg?style=shield\" alt=\"master build\">\\n</p>\\n  \\n**Infrastructure to build Bitcoin and blockchain-based applications for the next generation of financial technology.**\\n\\n## Applications\\n\\n- [Bitcore Node](packages/bitcore-node) - A standardized API to interact with multiple blockchain networks\\n- [Bitcore Wallet](packages/bitcore-wallet) - A command-line based wallet client\\n- [Bitcore Wallet Client](packages/bitcore-wallet-client) - A client for the wallet service\\n- [Bitcore Wallet Service](packages/bitcore-wallet-service) - A multisig HD service for wallets\\n- [Bitpay Wallet](https://github.com/bitpay/wallet) - An easy-to-use, multiplatform, multisignature, secure bitcoin wallet\\n- [Insight](packages/insight) - A blockchain explorer web user interface\\n\\n## Libraries\\n\\n- [Bitcore Lib](packages/bitcore-lib) - A powerful JavaScript library for Bitcoin\\n- [Bitcore Lib Cash](packages/bitcore-lib-cash) - A powerful JavaScript library for Bitcoin Cash\\n- [Bitcore Lib Doge](packages/bitcore-lib-doge) - A powerful JavaScript library for Dogecoin\\n- [Bitcore Lib Litecoin](packages/bitcore-lib-ltc) - A powerful JavaScript library for Litecoin\\n- [Bitcore Mnemonic](packages/bitcore-mnemonic) - Implements mnemonic code for generating deterministic keys\\n- [Bitcore P2P](packages/bitcore-p2p) - The peer-to-peer networking protocol for Bitcoin\\n- [Bitcore P2P Cash](packages/bitcore-p2p-cash) - The peer-to-peer networking protocol for Bitcoin Cash\\n- [Bitcore P2P Doge](packages/bitcore-p2p-doge) **DEPRECATED**[^1] - The peer-to-peer networking protocol for Dogecoin\\n- [Crypto Wallet Core](packages/crypto-wallet-core) - A coin-agnostic wallet library for creating transactions, signing, and address derivation\\n\\n## Extras\\n\\n- [Bitcore Build](packages/bitcore-build) - A helper to add tasks to gulp\\n- [Bitcore Client](packages/bitcore-client) - A helper to create a wallet using the bitcore-v8 infrastructure\\n\\n## Contributing\\n\\nSee [CONTRIBUTING.md](https://github.com/bitpay/bitcore/blob/master/Contributing.md) on the main bitcore repo for information about how to contribute.\\n\\n## License\\n\\nCode released under [the MIT license](https://github.com/bitpay/bitcore/blob/master/LICENSE).\\n\\nCopyright 2013-2023 BitPay, Inc. Bitcore is a trademark maintained by BitPay, Inc.\\n\\n[^1]: The Bitcore P2P Doge library is no longer maintained as all the core functionality is contained in Bitcore P2P\\n'},\n",
       " {'repo': 'bitpay/bitcoind-rpc',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': \"bitcoind-rpc.js\\n===============\\n\\n[![NPM Package](https://img.shields.io/npm/v/bitcoind-rpc.svg?style=flat-square)](https://www.npmjs.org/package/bitcoind-rpc)\\n[![Build Status](https://img.shields.io/travis/bitpay/bitcoind-rpc.svg?branch=master&style=flat-square)](https://travis-ci.org/bitpay/bitcoind-rpc)\\n[![Coverage Status](https://img.shields.io/coveralls/bitpay/bitcoind-rpc.svg?style=flat-square)](https://coveralls.io/r/bitpay/bitcoind-rpc?branch=master)\\n\\nA client library to connect to Bitcoin Core RPC in JavaScript.\\n\\n## Get Started\\n\\nbitcoind-rpc.js runs on [node](http://nodejs.org/), and can be installed via [npm](https://npmjs.org/):\\n\\n```bash\\nnpm install bitcoind-rpc\\n```\\n\\n## Examples\\n\\n```javascript\\nvar run = function() {\\n  var bitcore = require('bitcore');\\n  var RpcClient = require('bitcoind-rpc');\\n\\n  var config = {\\n    protocol: 'http',\\n    user: 'user',\\n    pass: 'pass',\\n    host: '127.0.0.1',\\n    port: '18332',\\n  };\\n\\n  // config can also be an url, e.g.:\\n  // var config = 'http://user:pass@127.0.0.1:18332';\\n\\n  var rpc = new RpcClient(config);\\n\\n  var txids = [];\\n\\n  function showNewTransactions() {\\n    rpc.getRawMemPool(function (err, ret) {\\n      if (err) {\\n        console.error(err);\\n        return setTimeout(showNewTransactions, 10000);\\n      }\\n\\n      function batchCall() {\\n        ret.result.forEach(function (txid) {\\n          if (txids.indexOf(txid) === -1) {\\n            rpc.getRawTransaction(txid);\\n          }\\n        });\\n      }\\n\\n      rpc.batch(batchCall, function(err, rawtxs) {\\n        if (err) {\\n          console.error(err);\\n          return setTimeout(showNewTransactions, 10000);\\n        }\\n\\n        rawtxs.map(function (rawtx) {\\n          var tx = new bitcore.Transaction(rawtx.result);\\n          console.log('\\\\n\\\\n\\\\n' + tx.id + ':', tx.toObject());\\n        });\\n\\n        txids = ret.result;\\n        setTimeout(showNewTransactions, 2500);\\n      });\\n    });\\n  }\\n\\n  showNewTransactions();\\n};\\n```\\n\\n## License\\n\\n**Code released under [the MIT license](https://github.com/bitpay/bitcore/blob/master/LICENSE).**\\n\\nCopyright 2013-2018 BitPay, Inc.\\n\"},\n",
       " {'repo': 'zquestz/bitcoincash',\n",
       "  'language': 'CSS',\n",
       "  'readme_contents': \"[![Build & Push](https://github.com/zquestz/bitcoincash/actions/workflows/build_and_push.yml/badge.svg?branch=master)](https://github.com/zquestz/bitcoincash/actions/workflows/build_and_push.yml?query=branch%3Amaster)\\n\\n# BitcoinCash.org\\n\\nThis is the repository for [bitcoincash.org](https://bitcoincash.org). As the Bitcoin Cash community expands, we hope that many will participate and improve this project over time.\\n\\n## Build & Run the Docker Image\\n\\nIn order to build and run the site you need ruby and docker. Then run:\\n\\n1. `gem install bundler`\\n2. `bundle install`\\n3. `bundle exec rake docker:build`\\n4. `docker run -p 8888:80 bitcoincash:latest`\\n\\nNow the site is running at http://localhost:8888.\\n\\nTo refresh the site after making changes:\\n\\n```\\n# ctrl-c the running docker process.\\nbundle exec rake docker:build && docker run -p 8888:80 bitcoincash:latest\\n```\\n\\nThe site is running at http://localhost:8888 with your changes.\\n\\n## Contributions\\n\\nIf you want to submit updates to the website make sure you are editing the templates in the `views` directory. These are used to generate all translated html files via `rake translations:build`.\\n\\nNote: Image files for projects will not load if against a transparent background or will extend out of card if too oddly sized. Best to use approximately 400x250 plain white card, with logo in the center.\\n\\n## Adding Translations\\n\\nTo add translations to the project, use `translations/en.yml` as a template and create a new file for your locale. Then translate all the content inside of the yaml file and send us a pull request.\\n\\n## Optimizing Images\\n\\nPlease provide all images as WEBP.\\n\\n## About Bitcoin Cash\\n\\nBitcoin Cash brings sound money to the world. Merchants and users are empowered with low fees and reliable confirmations. The future shines brightly with unrestricted growth, global adoption, permissionless innovation, and decentralized development.\\n\\nAll Bitcoin holders as of block 478558 are now owners of Bitcoin Cash. All Bitcoiners are welcome to join the Bitcoin Cash community as we move forward in creating sound money accessible to the whole world.\\n\\n## Listing Policy for Exchanges, Wallets, and Projects\\n\\nAlthough many exchanges, wallets, and other projects would like to be listed on our website, BitcoinCash.org is not meant\\nto be an exhaustive directory. There is limited space and quite simply, we only want to showcase the best of the best.\\n\\nOnly the top several exchanges by trading volume in each country will be considered.\\n\\nFor wallets, we only want to list those that have the highest trust and best reputation within the community. Relevant factors include the brand, the age of the wallet, as well as the track record of the company, developers, and/or other individuals involved.\\n\\nWe apologize in advance if we're unable to provide a listing for you on BitcoinCash.org. We acknowledge the criteria for wallet listings are somewhat subjective. Please understand our decisions are not personal, but rather based on a conservative approach and our responsbility to safeguard the community against questionable projects. Lastly, no listing should be interpreted as our explicit endorsement.\\n\\n## License\\n\\nbitcoincash.org is released under the terms of the MIT license. See [COPYING](COPYING) for more\\ninformation or see https://opensource.org/licenses/MIT.\\n\"},\n",
       " {'repo': 'btcsuite/btcd',\n",
       "  'language': 'Go',\n",
       "  'readme_contents': 'btcd\\n====\\n\\n[![Build Status](https://github.com/btcsuite/btcd/workflows/Build%20and%20Test/badge.svg)](https://github.com/btcsuite/btcd/actions)\\n[![Coverage Status](https://coveralls.io/repos/github/btcsuite/btcd/badge.svg?branch=master)](https://coveralls.io/github/btcsuite/btcd?branch=master)\\n[![ISC License](https://img.shields.io/badge/license-ISC-blue.svg)](http://copyfree.org)\\n[![GoDoc](https://img.shields.io/badge/godoc-reference-blue.svg)](https://pkg.go.dev/github.com/btcsuite/btcd)\\n\\nbtcd is an alternative full node bitcoin implementation written in Go (golang).\\n\\nThis project is currently under active development and is in a Beta state.  It\\nis extremely stable and has been in production use since October 2013.\\n\\nIt properly downloads, validates, and serves the block chain using the exact\\nrules (including consensus bugs) for block acceptance as Bitcoin Core.  We have\\ntaken great care to avoid btcd causing a fork to the block chain.  It includes a\\nfull block validation testing framework which contains all of the \\'official\\'\\nblock acceptance tests (and some additional ones) that is run on every pull\\nrequest to help ensure it properly follows consensus.  Also, it passes all of\\nthe JSON test data in the Bitcoin Core code.\\n\\nIt also properly relays newly mined blocks, maintains a transaction pool, and\\nrelays individual transactions that have not yet made it into a block.  It\\nensures all individual transactions admitted to the pool follow the rules\\nrequired by the block chain and also includes more strict checks which filter\\ntransactions based on miner requirements (\"standard\" transactions).\\n\\nOne key difference between btcd and Bitcoin Core is that btcd does *NOT* include\\nwallet functionality and this was a very intentional design decision.  See the\\nblog entry [here](https://web.archive.org/web/20171125143919/https://blog.conformal.com/btcd-not-your-moms-bitcoin-daemon)\\nfor more details.  This means you can\\'t actually make or receive payments\\ndirectly with btcd.  That functionality is provided by the\\n[btcwallet](https://github.com/btcsuite/btcwallet) and\\n[Paymetheus](https://github.com/btcsuite/Paymetheus) (Windows-only) projects\\nwhich are both under active development.\\n\\n## Requirements\\n\\n[Go](http://golang.org) 1.16 or newer.\\n\\n## Installation\\n\\nhttps://github.com/btcsuite/btcd/releases\\n\\n#### Linux/BSD/MacOSX/POSIX - Build from Source\\n\\n- Install Go according to the installation instructions here:\\n  http://golang.org/doc/install\\n\\n- Ensure Go was installed properly and is a supported version:\\n\\n```bash\\n$ go version\\n$ go env GOROOT GOPATH\\n```\\n\\nNOTE: The `GOROOT` and `GOPATH` above must not be the same path.  It is\\nrecommended that `GOPATH` is set to a directory in your home directory such as\\n`~/goprojects` to avoid write permission issues.  It is also recommended to add\\n`$GOPATH/bin` to your `PATH` at this point.\\n\\n- Run the following commands to obtain btcd, all dependencies, and install it:\\n\\n```bash\\n$ cd $GOPATH/src/github.com/btcsuite/btcd\\n$ GO111MODULE=on go install -v . ./cmd/...\\n```\\n\\n- btcd (and utilities) will now be installed in ```$GOPATH/bin```.  If you did\\n  not already add the bin directory to your system path during Go installation,\\n  we recommend you do so now.\\n\\n## Updating\\n\\n#### Linux/BSD/MacOSX/POSIX - Build from Source\\n\\n- Run the following commands to update btcd, all dependencies, and install it:\\n\\n```bash\\n$ cd $GOPATH/src/github.com/btcsuite/btcd\\n$ git pull\\n$ GO111MODULE=on go install -v . ./cmd/...\\n```\\n\\n## Getting Started\\n\\nbtcd has several configuration options available to tweak how it runs, but all\\nof the basic operations described in the intro section work with zero\\nconfiguration.\\n\\n#### Linux/BSD/POSIX/Source\\n\\n```bash\\n$ ./btcd\\n```\\n\\n## IRC\\n\\n- irc.libera.chat\\n- channel #btcd\\n- [webchat](https://web.libera.chat/gamja/?channels=btcd)\\n\\n## Issue Tracker\\n\\nThe [integrated github issue tracker](https://github.com/btcsuite/btcd/issues)\\nis used for this project.\\n\\n## Documentation\\n\\nThe documentation is a work-in-progress.  It is located in the [docs](https://github.com/btcsuite/btcd/tree/master/docs) folder.\\n\\n## Release Verification\\n\\nPlease see our [documentation on the current build/verification\\nprocess](https://github.com/btcsuite/btcd/tree/master/release) for all our\\nreleases for information on how to verify the integrity of published releases\\nusing our reproducible build system.\\n\\n## License\\n\\nbtcd is licensed under the [copyfree](http://copyfree.org) ISC License.\\n'},\n",
       " {'repo': 'bitpay/insight-api',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '\\nTHIS PROYECT HAS BEEN REPLACED BY BITCORE-NODE, AT https://github.com/bitpay/bitcore\\n'},\n",
       " {'repo': 'lefnire/tforce_btc_trader',\n",
       "  'language': 'Jupyter Notebook',\n",
       "  'readme_contents': '# TensorForce Bitcoin Trading Bot\\n\\n## Update 2018-08-14\\nTag v0.1 has the code which follows this README. Tag v0.2 is a major overhaul after lessons learned in a finance job, and much of this README won\\'t match the new code. I can\\'t get tests to converge in either case, so something is fundamentally missing from this project - ie, don\\'t count on making money (use as a starting-point / education instead). I\\'m stepping away for a while and won\\'t be very active here, but I\\'m not completely abandoning.\\n\\n---\\n\\n\\n[![Join the chat at https://gitter.im/lefnire/tforce_btc_trader](https://badges.gitter.im/lefnire/tforce_btc_trader.svg)](https://gitter.im/lefnire/tforce_btc_trader?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)\\n\\nA [TensorForce](https://github.com/reinforceio/tensorforce)-based Bitcoin trading bot (algo-trader). Uses deep reinforcement learning to automatically buy/sell/hold BTC based on price history.\\n\\nThis project goes with Episode 26+ of [Machine Learning Guide](http://ocdevel.com/podcasts/machine-learning). Those episodes are tutorial for this project; including an intro to Deep RL, hyperparameter decisions, etc.\\n\\n### 1. Setup\\n- Python 3.6+ (I use template strings a lot)\\n- Install & setup Postgres\\n  - Create two databases: `btc_history` and `hyper_runs`. You can call these whatever you want, and just use one db instead of two if you prefer (see Data section).\\n  - `cp config.example.json config.json`, pop ^ into `config.json`\\n- Install [TA-Lib](https://github.com/mrjbq7/ta-lib) manually.\\n- `pip install -r requirements.txt`\\n  - If issues, try installing these deps manually.\\n- Install TensorForce from git repo (constantly changing, we chase HEAD)\\n  - `git clone https://github.com/lefnire/tensorforce.git`\\n  - `cd tensorforce && pip install -e .`\\n\\nNote: you\\'ll wanna run this on a GPU rig with some RAM. I\\'m using a 1080ti and 16GB RAM; 8GB+ is often in used. You _can_ use a standard PC, no GPU (CPU-only); in that case `pip install -I tensorflow==1.5.0rc1` (instead of `tensorflow-gpu`). The only downside is performance; CPU is _way_ slower than GPU for ConvNet computations. Worth evaluating this repo on a CPU before you decide \"yeah, it\\'s worth the upgrade.\"\\n\\n### 2. Populate Data\\n- Download [mczielinski/bitcoin-historical-data](https://www.kaggle.com/mczielinski/bitcoin-historical-data)\\n- Extract to `data/bitcoin-historical-data`\\n- `python -c \\'from data.data import setup_runs_table;setup_runs_table()\\'`\\n  - if you get `ModuleNotFoundError: No module named \\'data.data\\'`, prefix commands with `PYTHONPATH=. python ...`\\n  - If you have trouble with that, just copy/paste the SQL from that file, execute against your `hyper_runs` DB from above.\\n\\n### 3. Hypersearch\\nThe crux of practical reinforcement learning is finding the right hyper-parameter combo (things like neural-network width/depth, L1 / L2 / Dropout numbers, etc). Some papers have listed optimal default hypers. Eg, the Proximate Policy Optimization (PPO) [paper](https://blog.openai.com/openai-baselines-ppo/) has a set of good defaults. But in my experience, they don\\'t work well for our purposes (time-series / trading). I\\'ll keep my own \"best defaults\" updated in this project, but YMMV and you\\'ll very likely need to try different hyper combos yourself. The file `hypersearch.py` will search hypers forever, ever honing in on better and better combos (using Bayesian Optimization (BO), see `gp.py`). See Hypersearch section below for more details.\\n\\n`python hypersearch.py`\\n\\nOptional flags:\\n- `--guess <int>`: sometimes you don\\'t want BO, which is pretty willy-nilly at first, to do the searching. Instead you want to try a hunch or two of your own first. See instructions in `utils.py#guess_overrides`.\\n- `--net-type <lstm|conv2d>`: see discussion below (LSTM v CNN)\\n- `--boost`: you can optionally use gradient boosting when searching for the best hyper combo, instead of BO. BO is more exploratory and thorough, gradient boosting is more \"find the best solution _now_\". I tend to use `--boost` after say 100 runs are in the database, since BO may still be dilly-dallying till 200-300 and daylight\\'s burning. Boost will suck in the early runs.\\n- `--autoencode`: many of you might hit some GPU RAM constraints (hypersearch crashes due to maxed memory). If so, use this flag. It dimensionality-reduces the price-history timesteps so more can fit into RAM. It does so destructively - think of lossy image compression - but might be required for your case. See [#6](https://github.com/lefnire/tforce_btc_trader/issues/6#issuecomment-364179764) for info on what leads to mem-maxing.\\n- `--n-steps <int>`, `--n-tests <int>`: vary how long to train and how often to report. `n-steps` is number of timesteps to train (in 10k; ie `--n-steps 100` means 1M). `n-tests` is how many times to split that and report back to you / save an entry for viz.\\n\\n### 4. Run\\nOnce you\\'ve found a good hyper combo from above (this could take days or weeks!), it\\'s time to run your results.\\n\\n`python run.py --name <str>`\\n\\n- `--name <str>` (required): name of the folder to save your run (during training) or load from (during `--live/--test-live`.\\n- `--id <int>`: the id of some winning hyper-combo you want to run with. Without this, it\\'ll run from the hard-coded hyper defaults.\\n- `--early-stop <int>`: sometimes your models can overfit. In particular, PPO can give you great performance for a long time and then crash-and-burn. That kind of behavior will be obvious in your visualization (below), so you can tell your run to stop after x consecutive positive episodes (depends on the agent - some find an optimum and roll for 3 positive episodes, some 8, just eyeball your graph).\\n- `--live`: whooa boy, time to put your agent on GDAX and make real trades! I\\'m gonna let you figure out how to plug it in on your own, \\'cause that\\'s danger territory. I ain\\'t responsible for shit. In fact, let\\'s make that real - disclaimer at the end of README.\\n- `--test-live`: same as `live`, but without making the real trades. This will start monitoring a live-updated database (from config.json), same as `live`, but instead of making the actual trade, it pretends it did and reports back how much you would have made/lost. Dry-run. You\\'ll definitely want to run this once or twice before running `--live`.\\n\\nFirst, run `python run.py [--id 10] --name test`. This will train your model using run 10 (from `hypersearch.py`) and save to `saves/test`. Without `--id` it will use the hard-coded deafults. You can hit `Ctrl-C` _once_ during training to kill training (in case you see a sweet-spot and don\\'t want to overfit).\\nSecond, run `python run.py [--id 10] --name test --[test-]live` to run in live/test-live mode. If you used `--id` before, use it again here so that loading the model matches it to its net architecture.\\n\\n## 5. Visualize\\nTensorForce comes pre-built with reward visualization on a TensorBoard. Check out their Github, you\\'ll see. I needed much more customization than that for viz, so we\\'re not using TensorBoard. I created a mini Flask server (2 routes) and a D3 React dashboard where you can slice & dice hyper combos, visualize progression, etc. If you click on a single run, it\\'ll display a graph of the buy/sell signals that agent took in a time-slice (test-set) so you can eyeball whether he\\'s being smart.\\n\\n- Server: `cd visualize;FLASK_APP=server.py flask run`\\n- Client:\\n  - `cd visualize/client`\\n  - `npm install;npm install -g webpack-dev-server`\\n  - `npm start` => localhost:8080\\n\\n![](https://s3.amazonaws.com/lefnirePublicFiles/adam_screenshot.png)\\n\\n---\\n\\n## About\\n\\nThis project is a [TensorForce](https://github.com/reinforceio/tensorforce)-based Bitcoin trading bot (algo-trader). It uses deep reinforcement learning to automatically buy/sell/hold BTC based on what it learns about BTC price history. Most blogs / tutorials / boilerplate BTC trading-bots you\\'ll find out there use supervised machine learning, likely an LTSM. That\\'s well and good - supervised learning learns what makes a time-series tick so it can predict the next-step future. But that\\'s where it stops. It says \"the price will go up next\", but it doesn\\'t tell you what to do. Well that\\'s simple, buy, right? Ah, buy low, sell high - it\\'s not that simple. Thousands of lines of code go into trading rules, \"if this then that\" style. Reinforcement learning takes supervised to the next level - it _embeds_ supervised within its architecture, and then decides what to do. It\\'s beautiful stuff! Check out:\\n\\n- [Sutton & Barto](http://amzn.to/2EWvnVf): de-facto textbook on RL basics\\n- [CS 294](http://rll.berkeley.edu/deeprlcourse/): the modern deep-learning spin on ^.\\n- [Machine Learning for Trading](https://www.udacity.com/course/machine-learning-for-trading--ud501): teaches you algo-trading, stock stuff, and applied RL.\\n\\nThis project goes with Episode 26+ of [Machine Learning Guide](http://ocdevel.com/podcasts/machine-learning). Those episodes are tutorial for this project; including an intro to Deep RL, hyperparameter decisions, etc.\\n\\n\\n### Data\\nFor this project I recommend using the Kaggle dataset described in Setup. It\\'s a really solid dataset, best I\\'ve found! I\\'m personally using a friend\\'s live-ticker DB. Unfortunately you can\\'t. It\\'s his personal thing, he may one day open it up as a paid API or something, we\\'ll see. There\\'s also some files in `data/populate` which use the CryptoWat.ch API. Great API _going forward_, but doesn\\'t have the history you\\'ll need to train on. If any y\\'all find anything better than the Kaggle set, LMK.\\n\\nSo here\\'s how this project splits up databases (see `config.json`). We start with a `history` DB, which has all the historical BTC prices for multiple exchanges. Import it, train on it. Then we have an optionally separate `runs` database, which saves the results of each of your `hypersearch.py` runs. This data is used by our BO or Boost algo to search for better hyper combos. You can have `runs` table in your `history` database if you want, one-and-the-same. I have them separate because I want the `history` DB on localhost for performance reason (it\\'s a major perf difference, you\\'ll see), and `runs` as a public hosted DB, which allows me to collect runs from separate AWS p3.8xlarge running instances.\\n\\nThen, when you\\'re ready for live mode, you\\'ll want a `live` database which is real-time, constantly collecting exchange ticker data. `--live` will handle keeping up with that database. Again, these can all 3 be the same database if you want, I\\'m just doing it my way for performance.\\n\\n### LSTM v CNN\\nYou\\'ll notice the `--net-type <lstm|conv2d>` flag in `hypersearch.py` and `run.py`. This will select between an LSTM Recurrent Neural Networks (RNNs) or Convolutional Neural Networks (CNN). I have them broken out of the hypersearch since they\\'re so different, they kinda deserve their own `runs` DB each - but if someone can consolidate them into the hypersearch framework, please do. You may be thinking, \"BTC prices is time-series, time-series is LSTM... why CNN?\" It strangely turns out that LSTM doesn\\'t do so hot here. In my own experience, in colleagues\\' experience, and in 2-3 papers I\\'ve read ([here\\'s one](https://arxiv.org/pdf/1706.10059.pdf)) - we\\'re all coming to the same conclusion. We\\'re not sure why... the running theory is vanishing/exploding gradient. LSTMs work well in NLP which has some maximum 50-word sentences or so. LSTMs mitigated vanilla RNN\\'s vanishing/exploding gradient for such sentences, true - but BTC history is infinite (on-going). Maybe LSTM can only go so far with time-series. Another possibility is that Deep Reinforcement Learning is most commonly researched, published, and open-sourced using CNNs. This because RL is super video-game centric, self-driving cars, all the vision stuff. So maybe the math behind these models lends better to CNNs? Who knows. The point is - experiment with both. Report back on Github your own findings.\\n\\nSo how does CNN even make sense for time-series? Well we construct an \"image\" of a time-slice, where the x-axis is time (obviously), the y-axis (height) is nothing... it\\'s [1]. The z-axis (channels) is features (OHLCV, VWAP, bid/ask, etc). This is kinda like our agent literally looking at an image of price actions, like we do when day-trading, but a bit more robot-friendly / less human-friendly.\\n\\n[Update March 04 2018]: I\\'m having better success recently w/ LSTMs and have made that the default. A change in TensorForce perhaps?\\n\\n### Reinforcement Models\\n\\nTensorForce has all sorts of models you can play with. This project currently only supports Proximate Policy Optimization (PPO), but I encourage y\\'all to add in other models (esp VPG, TRPO, DDPG, ACKTR, etc) and submit PRs. ACKTR is the current state-of-the-art Policy Gradient model, but not yet available in TensorForce. PPO is the second-most-state-of-the-art, so we\\'re using that. TRPO is 3rd, VPG is old. DDPG I haven\\'t put much thought into.\\n\\nThose are the Policy Gradient models. Then there\\'s the Q-Learning approaches (DQNs, etc). We\\'re not using those because they only support discrete actions, not continuous actions. Our agent has one discrete action (buy|sell|hold), and one continuous action (how much?). Without that \"how much\" continuous flexibility, building an algo-trader would be... well, not so cool. You could do something like (discrete action = (buy-$200, sell-$200, hold)), but I dunno man... continuous is slicker.\\n\\n### Hypersearch\\n\\nYou\\'re likely familiar with _grid search_ and _random search_ when searching for optimial hyperparameters for machine learning models. Grid search searches literally every possible combo - exhaustive, but takes infinity years (especially w/ the number of hypers we work with in this project). Random search throws a dart at random hyper combos over and over, and you just kill it eventually and take the best. Super naive - it works ok for other ML setups, but in RL hypers are the make-or-break; more than model selection. Seriously, I\\'ve found L1 / L2 / Dropout selection more consequential than PPO vs DQN, LSTM vs CNN, etc.\\n\\nThat\\'s why we\\'re using Bayesian Optimization (BO). Or sometimes you\\'ll hear Gaussian Processes (GP), the thing you\\'re optimizing with BO. See `gp.py`. BO starts off like random search, since it doesn\\'t have anything to work with; and over time it hones in on the best hyper combo using Bayesian inference. Super meta - use ML to find the best hypers for your ML - but makes sense. Wait, why not use RL to find the best hypers? We could (and I tried), but deep RL takes 10s of thousands of runs before it starts converging; and each run takes some 8hrs. BO converges much quicker. I\\'ve also implemented my own flavor of hypersearch via Gradient Boosting (if you use `--boost` during training); more for my own experimentation.\\n\\nWe\\'re using `gp.py`, which comes from [thuijskens/bayesian-optimization](https://github.com/thuijskens/bayesian-optimization). It uses scikit-learn\\'s in-built GP functions. I also considered dedicated BO modules, like GPyOpt. I found `gp.py` easier to work with, but haven\\'t compared it\\'s relative performance, nor its optimal hypers (yes, BO has its own hypers... it\\'s turtles all the way down. But luckily I hear you can pretty safely use BO\\'s defaults). If anyone wants to explore any of that territory, please indeed!\\n\\n### License: AGPLv3.0\\n\\nGPL bit so we share our findings. Community effort, right? Boats and tides. Affero bit so we can all run our own trading instances w/ personal configs / mods. Heck, any of us could run this as a service / hedge fund. I\\'m pretty keen on this license, having used it in a prior [internet company](https://habitica.com) I\\'d founded; but if someone feels strongly about a different license, please open an issue & LMK - open to suggestions. See LICENSE.\\n\\n### Disclaimer\\n\\nBy using this code you accept all responsibility for money lost because of this code.\\n\\nFYI, I haven\\'t made a dime. Doubtful the project as-is will fly. It could benefit from add-ons, like some NLP fundamentals functionality. But it\\'s a start!\\n'},\n",
       " {'repo': 'bitpay/bitcore-lib',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': \"Bitcore Library\\n=======\\nTHIS REPO HAVE BEEN MOVED TO BITCORE's MONO REPO. Check: \\n\\nhttps://github.com/bitpay/bitcore/tree/v8.0.0/packages/bitcore-lib\\n\"},\n",
       " {'repo': 'ofek/bit',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': \"Bit: Bitcoin made easy.\\n=======================\\n\\n.. image:: https://img.shields.io/pypi/v/bit.svg?style=flat-square\\n    :target: https://pypi.org/project/bit\\n\\n.. image:: https://img.shields.io/travis/ofek/bit.svg?branch=master&style=flat-square\\n    :target: https://travis-ci.org/ofek/bit\\n\\n.. image:: https://img.shields.io/codecov/c/github/ofek/bit.svg?style=flat-square\\n    :target: https://codecov.io/gh/ofek/bit\\n\\n.. image:: https://img.shields.io/pypi/pyversions/bit.svg?style=flat-square\\n    :target: https://pypi.org/project/bit\\n\\n.. image:: https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square\\n    :target: https://en.wikipedia.org/wiki/MIT_License\\n\\n-----\\n\\nBit is Python's `fastest <https://ofek.github.io/bit/guide/intro.html#why-bit>`_\\nBitcoin library and was designed from the beginning to feel intuitive, be\\neffortless to use, and have readable source code. It is heavily inspired by\\n`Requests <https://github.com/requests/requests>`_ and\\n`Keras <https://github.com/keras-team/keras>`_.\\n\\n**Bit is so easy to use, in fact, you can do this:**\\n\\n.. code-block:: python\\n\\n    >>> from bit import Key\\n    >>>\\n    >>> my_key = Key(...)\\n    >>> my_key.get_balance('usd')\\n    '12.51'\\n    >>>\\n    >>> # Let's donate!\\n    >>> outputs = [\\n    >>>     # Wikileaks\\n    >>>     ('1HB5XMLmzFVj8ALj6mfBsbifRoD4miY36v', 0.0035, 'btc'),\\n    >>>     # Internet Archive\\n    >>>     ('1Archive1n2C579dMsAu3iC6tWzuQJz8dN', 190, 'jpy'),\\n    >>>     # The Pirate Bay\\n    >>>     ('129TQVAroeehD9fZpzK51NdZGQT4TqifbG', 3, 'eur'),\\n    >>>     # xkcd\\n    >>>     ('14Tr4HaKkKuC1Lmpr2YMAuYVZRWqAdRTcr', 2.5, 'cad')\\n    >>> ]\\n    >>>\\n    >>> my_key.send(outputs)\\n    '9f59f5c6757ec46fdc7440acbeb3920e614c8d1d247ac174eb6781b832710c1c'\\n\\nHere is the transaction `<https://blockchain.info/tx/9f59f5c6757ec46fdc7440acbeb3920e614c8d1d247ac174eb6781b832710c1c>`_.\\n\\nFeatures\\n--------\\n\\n- Python's fastest available implementation (100x faster than closest library)\\n- Seamless integration with existing server setups\\n- Supports keys in cold storage\\n- Fully supports 25 different currencies\\n- First class support for storing data in the blockchain\\n- Deterministic signatures via RFC 6979\\n- Access to the blockchain (and testnet chain) through multiple APIs for redundancy\\n- Exchange rate API, with optional caching\\n- Optimal transaction fee API, with optional caching\\n- Compressed public keys by default\\n- Multiple representations of private keys; WIF, PEM, DER, etc.\\n- Legacy P2PKH and Segwit nested-P2WPKH transactions\\n- Legacy P2SH and Segwit nested-P2WSH transactions\\n\\nIf you are intrigued, continue reading. If not, continue all the same!\\n\\nInstallation\\n------------\\n\\nBit is distributed on `PyPI`_ as a universal wheel and is available on Linux/macOS\\nand Windows and supports Python 3.5+ and PyPy3.5-v5.7.1+. ``pip`` >= 8.1.2 is required.\\n\\n.. code-block:: bash\\n\\n    $ pip install bit\\n\\nDocumentation\\n-------------\\n\\nDocs are `hosted by Github Pages`_ and are automatically built and published\\nby Travis after every successful commit to Bit's ``master`` branch.\\n\\nCredits\\n-------\\n\\n- Logo courtesy of `<https://textcraft.net>`_\\n- `Gregory Maxwell`_ (Bitcoin core dev) for teaching me a bit of `ECC`_ math\\n- `arubi`_ in #bitcoin for helping me understand transaction gotchas\\n- `fuzeman`_ for bestowing me the name ``bit`` on the `Python Package Index`_\\n\\n.. _PyPI: https://pypi.org/project/bit\\n.. _hosted by Github Pages: https://ofek.github.io/bit\\n.. _Gregory Maxwell: https://github.com/gmaxwell\\n.. _ECC: https://en.wikipedia.org/wiki/Elliptic_curve_cryptography\\n.. _arubi: https://github.com/fivepiece\\n.. _fuzeman: https://github.com/fuzeman\\n.. _Python Package Index: https://pypi.org\\n\"},\n",
       " {'repo': 'ruimarinho/bitcoin-core',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# bitcoin-core\\nA modern Bitcoin Core REST and RPC client to execute administrative tasks, [multiwallet](https://bitcoincore.org/en/2017/09/01/release-0.15.0/#multiwallet) operations and queries about network and the blockchain.\\n\\n## Status\\n[![npm version][npm-image]][npm-url] [![build status][travis-image]][travis-url]\\n\\n## Installation\\n\\nInstall the package via `yarn`:\\n\\n```sh\\nyarn add bitcoin-core\\n```\\n\\nor via `npm`:\\n\\nInstall the package via `npm`:\\n\\n```sh\\nnpm install bitcoin-core --save\\n```\\n\\n## Usage\\n### Client(...args)\\n#### Arguments\\n1. `[agentOptions]` _(Object)_: Optional `agent` [options](https://github.com/request/request#using-optionsagentoptions) to configure SSL/TLS.\\n2. `[headers=false]` _(boolean)_: Whether to return the response headers.\\n3. `[host=localhost]` _(string)_: The host to connect to.\\n4. `[logger=debugnyan(\\'bitcoin-core\\')]` _(Function)_: Custom logger (by default, `debugnyan`).\\n5. `[network=mainnet]` _(string)_: The network\\n6. `[password]` _(string)_: The RPC server user password.\\n7. `[port=[network]]` _(string)_: The RPC server port.\\n8. `[ssl]` _(boolean|Object)_: Whether to use SSL/TLS with strict checking (_boolean_) or an expanded config (_Object_).\\n9. `[ssl.enabled]` _(boolean)_: Whether to use SSL/TLS.\\n10. `[ssl.strict]` _(boolean)_: Whether to do strict SSL/TLS checking (certificate must match host).\\n11. `[timeout=30000]` _(number)_: How long until the request times out (ms).\\n12. `[username]` _(number)_: The RPC server user name.\\n13. `[version]` _(string)_: Which version to check methods for ([read more](#versionchecking)).\\n14. `[wallet]` _(string)_: Which wallet to manage ([read more](#multiwallet)).\\n\\n### Examples\\n#### Using network mode\\nThe `network` will automatically determine the port to connect to, just like the `bitcoind` and `bitcoin-cli` commands.\\n\\n```js\\nconst Client = require(\\'bitcoin-core\\');\\nconst client = new Client({ network: \\'regtest\\' });\\n```\\n\\n##### Setting a custom port\\n\\n```js\\nconst client = new Client({ port: 28332 });\\n```\\n\\n#### Connecting to an SSL/TLS server with strict checking enabled\\nBy default, when `ssl` is enabled, strict checking is implicitly enabled.\\n\\n```js\\nconst fs = require(\\'fs\\');\\nconst client = new Client({\\n  agentOptions: {\\n    ca: fs.readFileSync(\\'/etc/ssl/bitcoind/cert.pem\\')\\n  },\\n  ssl: true\\n});\\n```\\n\\n#### Connecting to an SSL/TLS server without strict checking enabled\\n\\n```js\\nconst client = new Client({\\n  ssl: {\\n    enabled: true,\\n    strict: false\\n  }\\n});\\n```\\n\\n#### Using promises to process the response\\n\\n```js\\nclient.getInfo().then((help) => console.log(help));\\n```\\n\\n#### Using callbacks to process the response\\n\\nCallback support was removed. Since every method returns a `Promise`, [callbackify()](https://nodejs.org/api/util.html#util_util_callbackify_original) (`>node@v8.2.0`) can be used, or for older `node` versions you can use the npm package [callbackify](https://www.npmjs.com/package/callbackify).\\n\\n```js\\nutil.callbackify(() => client.getInfo())((error, help) => console.log(help));\\n```\\n\\n#### Returning headers in the response\\nFor compatibility with other Bitcoin Core clients.\\n\\n```js\\nconst client = new Client({ headers: true });\\n\\n// Promise style with headers enabled:\\nclient.getInfo().then(([body, headers]) => console.log(body, headers));\\n\\n// Await style based on promises with headers enabled:\\nconst [body, headers] = await client.getInfo();\\n```\\n\\n## Named parameters\\n\\nSince version v0.14.0, it is possible to send commands via the JSON-RPC interface using named parameters instead of positional ones. This comes with the advantage of making the order of arguments irrelevant. It also helps improving the readability of certain function calls when leaving out arguments for their default value.\\n\\nYou **must** provide a version in the client arguments to enable named parameters.\\n\\n```js\\nconst client = new Client({ version: \\'0.15.1\\' });\\n```\\nFor instance, take the `getBalance()` call written using positional arguments:\\n```js\\nconst balance = await new Client().getBalance(\\'*\\', 0);\\n```\\n\\nIt is functionally equivalent to using the named arguments `account` and `minconf`, leaving out `include_watchonly` (defaults to `false`):\\n\\n```js\\nconst balance = await new Client({ version: \\'0.15.1\\' }).getBalance({\\n  account: \\'*\\',\\n  minconf: 0\\n});\\n```\\n\\nThis feature is available to all JSON-RPC methods that accept arguments.\\n\\n### Floating point number precision in JavaScript\\n\\nDue to [JavaScript\\'s limited floating point precision](http://floating-point-gui.de/), all big numbers (numbers with more than 15 significant digits) are returned as strings to prevent precision loss. This includes both the RPC and REST APIs.\\n\\n## Multiwallet\\n\\nSince Bitcoin Core v0.15.0, it\\'s possible to manage multiple wallets using a single daemon. This enables use-cases such as managing a personal and a business wallet simultaneously in order to simplify accounting and accidental misuse of funds.\\n\\nHistorically, the _accounts_ feature was supposed to offer similar functionality, but it has now been replaced by this more powerful feature.\\n\\nTo enable Multi Wallet support, start by specifying the number of added wallets you would like to have available and loaded on the server using the `-wallet` argument multiple times. For convenience, the bitcoin-core docker image will be used, but it\\'s not a requirement:\\n\\n```sh\\ndocker run --rm -it -p 18332:18332 ruimarinho/bitcoin-core:0.15-alpine \\\\\\n  -printtoconsole \\\\\\n  -server \\\\\\n  -rpcauth=\\'foo:e1fcea9fb59df8b0388f251984fe85$26431097d48c5b6047df8dee64f387f63835c01a2a463728ad75087d0133b8e6\\' \\\\\\n  -regtest \\\\\\n  -wallet=wallet1.dat \\\\\\n  -wallet=wallet2.dat \\\\\\n  -rpcallowip=172.17.0.0/16\\n```\\n\\nNotice the `rpcauth` hash which has been previously generated for the password `j1DuzF7QRUp-iSXjgewO9T_WT1Qgrtz_XWOHCMn_O-Y=`. Do **not** copy and paste this hash **ever** beyond this exercise.\\n\\nInstantiate a client for each wallet and execute commands targeted at each wallet:\\n\\n```js\\nconst Client = require(\\'bitcoin-core\\');\\n\\nconst wallet1 = new Client({\\n  network: \\'regtest\\',\\n  wallet: \\'wallet1.dat\\',\\n  username: \\'foo\\',\\n  password: \\'j1DuzF7QRUp-iSXjgewO9T_WT1Qgrtz_XWOHCMn_O-Y=\\'\\n});\\n\\nconst wallet2 = new Client({\\n  network: \\'regtest\\',\\n  wallet: \\'wallet2.dat\\',\\n  username: \\'foo\\',\\n  password: \\'j1DuzF7QRUp-iSXjgewO9T_WT1Qgrtz_XWOHCMn_O-Y=\\'\\n});\\n\\n(async function() {\\n  await wallet2.generate(100);\\n\\n  console.log(await wallet1.getBalance());\\n  // => 0\\n  console.log(await wallet2.getBalance());\\n  // => 50\\n}());\\n```\\n\\n\\n### Version Checking\\nBy default, all methods are exposed on the client independently of the version it is connecting to. This is the most flexible option as defining methods for unavailable RPC calls does not cause any harm and the library is capable of handling a `Method not found` response error correctly.\\n\\n```js\\nconst client = new Client();\\n\\nclient.command(\\'foobar\\');\\n// => RpcError: -32601 Method not found\\n```\\n\\nHowever, if you prefer to be on the safe side, you can enable strict version checking. This will validate all method calls before executing the actual RPC request:\\n\\n```js\\nconst client = new Client({ version: \\'0.12.0\\' });\\n\\nclient.getHashesPerSec();\\n// => Method \"gethashespersec\" is not supported by version \"0.12.0\"\\n```\\n\\nIf you want to enable strict version checking for the bleeding edge version, you may set a very high version number to exclude recently deprecated calls:\\n\\n```js\\nconst client = new Client({ version: `${Number.MAX_SAFE_INTEGER}.0.0` });\\n\\nclient.getWork();\\n// => Throws \\'Method \"getwork\" is not supported by version \"9007199254740991.0.0\"\\'.\\n```\\n\\nTo avoid potential issues with prototype references, all methods are still enumerable on the library client prototype.\\n\\n### RPC\\nStart the `bitcoind` with the RPC server enabled and optionally configure a username and password:\\n\\n```sh\\ndocker run --rm -it ruimarinho/bitcoin-core:0.12-alpine -printtoconsole -rpcuser=foo -rpcpassword=bar -server\\n```\\n\\nThese configuration values may also be set on the `bitcoin.conf` file of your platform installation.\\n\\nBy default, port `8332` is used to listen for requests in `mainnet` mode, or `18332` in `testnet` and `regtest` modes (the regtest change will be changed to `18443` in [0.16](https://github.com/bitcoin/bitcoin/pull/10825)). Use the `network` property to initialize the client on the desired mode and automatically set the respective default port. You can optionally set a custom port of your choice too.\\n\\nThe RPC services binds to the localhost loopback network interface, so use `rpcbind` to change where to bind to and `rpcallowip` to whitelist source IP access.\\n\\n#### Methods\\nAll RPC [methods](src/methods.js) are exposed on the client interface as a camelcase\\'d version of those available on `bitcoind` (see examples below).\\n\\nFor a more complete reference about which methods are available, check the [RPC documentation](https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs) on the [Bitcoin Core Developer Reference website](https://bitcoin.org/en/developer-reference).\\n\\n##### Examples\\n\\n```js\\nclient.createRawTransaction([{ txid: \\'1eb590cd06127f78bf38ab4140c4cdce56ad9eb8886999eb898ddf4d3b28a91d\\', vout: 0 }], { \\'mgnucj8nYqdrPFh2JfZSB1NmUThUGnmsqe\\': 0.13 });\\nclient.sendMany(\\'test1\\', { mjSk1Ny9spzU2fouzYgLqGUD8U41iR35QN: 0.1, mgnucj8nYqdrPFh2JfZSB1NmUThUGnmsqe: 0.2 }, 6, \\'Example Transaction\\');\\nclient.sendToAddress(\\'mmXgiR6KAhZCyQ8ndr2BCfEq1wNG2UnyG6\\', 0.1,  \\'sendtoaddress example\\', \\'Nemo From Example.com\\');\\n```\\n\\n#### Batch requests\\nBatch requests are support by passing an array to the `command` method with a `method` and optionally, `parameters`. The return value will be an array with all the responses.\\n\\n```js\\nconst batch = [\\n  { method: \\'getnewaddress\\', parameters: [] },\\n  { method: \\'getnewaddress\\', parameters: [] }\\n]\\n\\nnew Client().command(batch).then((responses) => console.log(responses)));\\n\\n// Or, using ES2015 destructuring.\\nnew Client().command(batch).then(([firstAddress, secondAddress]) => console.log(firstAddress, secondAddress)));\\n```\\n\\nNote that batched requests will only throw an error if the batch request itself cannot be processed. However, each individual response may contain an error akin to an individual request.\\n\\n```js\\nconst batch = [\\n  { method: \\'foobar\\', parameters: [] },\\n  { method: \\'getnewaddress\\', parameters: [] }\\n]\\n\\nnew Client().command(batch).then(([address, error]) => console.log(address, error)));\\n// => `mkteeBFmGkraJaWN5WzqHCjmbQWVrPo5X3, { [RpcError: Method not found] message: \\'Method not found\\', name: \\'RpcError\\', code: -32601 }`.\\n```\\n\\n### REST\\nSupport for the REST interface is still **experimental** and the API is still subject to change. These endpoints are also **unauthenticated** so [there are certain risks which you should be aware](https://github.com/bitcoin/bitcoin/blob/master/doc/REST-interface.md#risks), specifically of leaking sensitive data of the node if not correctly protected.\\n\\nError handling is still fragile so avoid passing user input.\\n\\nStart the `bitcoind` with the REST server enabled:\\n\\n```sh\\ndocker run --rm -it ruimarinho/bitcoin-core:0.12-alpine -printtoconsole -server -rest\\n```\\n\\nThese configuration values may also be set on the `bitcoin.conf` file of your platform installation. Use `txindex=1` if you\\'d like to enable full transaction query support (note: this will take a considerable amount of time on the first run).\\n\\n### Methods\\n\\nUnlike RPC methods which are automatically exposed on the client, REST ones are handled individually as each method has its own specificity. The following methods are supported:\\n\\n- [getBlockByHash](#getblockbyhashhash-options)\\n- [getBlockHeadersByHash](#getblockheadersbyhashhash-count-options)\\n- [getBlockchainInformation](#getblockchaininformation)\\n- [getMemoryPoolContent](#getmemorypoolcontent)\\n- [getMemoryPoolInformation](#getmemorypoolinformation)\\n- [getTransactionByHash](#gettransactionbyhashhash-options)\\n- [getUnspentTransactionOutputs](#getunspenttransactionoutputsoutpoints-options)\\n\\n#### getBlockByHash(hash, [options])\\nGiven a block hash, returns a block, in binary, hex-encoded binary or JSON formats.\\n\\n##### Arguments\\n1. `hash` _(string)_: The block hash.\\n2. `[options]` _(Object)_: The options object.\\n3. `[options.extension=json]` _(string)_: Return in binary (`bin`), hex-encoded binary (`hex`) or JSON (`json`) format.\\n\\n##### Example\\n\\n```js\\nclient.getBlockByHash(\\'0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206\\', { extension: \\'json\\' });\\n```\\n\\n#### getBlockHeadersByHash(hash, count, [options])\\nGiven a block hash, returns amount of block headers in upward direction.\\n\\n##### Arguments\\n1. `hash` _(string)_: The block hash.\\n2. `count` _(number)_: The number of blocks to count in upward direction.\\n3. `[options]` _(Object)_: The options object.\\n4. `[options.extension=json]` _(string)_: Return in binary (`bin`), hex-encoded binary (`hex`) or JSON (`json`) format.\\n\\n##### Example\\n\\n```js\\nclient.getBlockHeadersByHash(\\'0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206\\', 1, { extension: \\'json\\' });\\n```\\n\\n#### getBlockchainInformation()\\nReturns various state info regarding block chain processing.\\n\\n##### Example\\n\\n```js\\nclient.getBlockchainInformation();\\n```\\n\\n#### getMemoryPoolContent()\\nReturns transactions in the transaction memory pool.\\n\\n##### Example\\n\\n```js\\nclient.getMemoryPoolContent();\\n```\\n\\n#### getMemoryPoolInformation()\\nReturns various information about the transaction memory pool. Only supports JSON as output format.\\n- size: the number of transactions in the transaction memory pool.\\n- bytes: size of the transaction memory pool in bytes.\\n- usage: total transaction memory pool memory usage.\\n\\n##### Example\\n\\n```js\\nclient.getMemoryPoolInformation();\\n```\\n\\n#### getTransactionByHash(hash, [options])\\nGiven a transaction hash, returns a transaction in binary, hex-encoded binary, or JSON formats.\\n\\n#### Arguments\\n1. `hash` _(string)_: The transaction hash.\\n2. `[options]` _(Object)_: The options object.\\n3. `[options.summary=false]` _(boolean)_: Whether to return just the transaction hash, thus saving memory.\\n4. `[options.extension=json]` _(string)_: Return in binary (`bin`), hex-encoded binary (`hex`) or JSON (`json`) format.\\n\\n##### Example\\n\\n```js\\nclient.getTransactionByHash(\\'b4dd08f32be15d96b7166fd77afd18aece7480f72af6c9c7f9c5cbeb01e686fe\\', { extension: \\'json\\', summary: false });\\n```\\n\\n#### getUnspentTransactionOutputs(outpoints, [options])\\nQuery unspent transaction outputs (UTXO) for a given set of outpoints. See [BIP64](https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki) for input and output serialisation.\\n\\n#### Arguments\\n1. `outpoints` _(array\\\\<Object\\\\>|Object)_: The outpoint to query in the format `{ id: \\'<txid>\\', index: \\'<index>\\' }`.\\n2. `[options]` _(Object)_: The options object.\\n3. `[options.extension=json]` _(string)_: Return in binary (`bin`), hex-encoded binary (`hex`) or JSON (`json`) format.\\n\\n##### Example\\n\\n```js\\nclient.getUnspentTransactionOutputs([{\\n  id: \\'0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206\\',\\n  index: 0\\n}, {\\n  id: \\'0f9188f13cb7b2c71f2a335e3a4fc328bf5beb436012afca590b1a11466e2206\\',\\n  index: 1\\n}], { extension: \\'json\\' })\\n```\\n\\n### SSL\\nThis client supports SSL out of the box. Simply pass the SSL public certificate to the client and optionally disable strict SSL checking which will bypass SSL validation (the connection is still encrypted but the server it is connecting to may not be trusted). This is, of course, discouraged unless for testing purposes when using something like self-signed certificates.\\n\\n#### Generating a self-signed certificates for testing purposes\\nPlease note that the following procedure should only be used for testing purposes.\\n\\nGenerate an self-signed certificate together with an unprotected private key:\\n\\n```sh\\nopenssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 3650 -nodes\\n```\\n\\n#### Connecting via SSL\\nOn Bitcoin Core <0.12, you can start the `bitcoind` RPC server directly with SSL:\\n\\n```sh\\ndocker run --rm -it -v $(PWD)/ssl:/etc/ssl ruimarinho/bitcoin-core:0.11-alpine -printtoconsole -rpcuser=foo -rpcpassword=bar -rpcssl -rpcsslcertificatechainfile=/etc/ssl/bitcoind/cert.pem -rpcsslprivatekeyfile=/etc/ssl/bitcoind/key.pem -server\\n```\\n\\nOn Bitcoin Core >0.12, use must use `stunnel` (`brew install stunnel` or `sudo apt-get install stunnel4`) or an HTTPS reverse proxy to configure SSL since the built-in support for SSL has been removed. The trade off with `stunnel` is performance and simplicity versus features, as it lacks more powerful capacities such as Basic Authentication and caching which are standard in reverse proxies.\\n\\nYou can use `stunnel` by configuring `stunnel.conf` with the following service requirements:\\n\\n```\\n[bitcoin]\\naccept = 28332\\nconnect = 18332\\ncert = /etc/ssl/bitcoind/cert.pem\\nkey = /etc/ssl/bitcoind/key.pem\\n```\\n\\nThe `key` option may be omitted if you concatenating your private and public certificates into a single `stunnel.pem` file.\\n\\nOn some versions of `stunnel` it is also possible to start a service using command line arguments. The equivalent would be:\\n\\n```sh\\nstunnel -d 28332 -r 127.0.0.1:18332 -p stunnel.pem -P \\'\\'\\n```\\n\\nThen pass the public certificate to the client:\\n\\n```js\\nconst Client = require(\\'bitcoin-core\\');\\nconst fs = require(\\'fs\\');\\nconst client = new Client({\\n  agentOptions: {\\n    ca: fs.readFileSync(\\'/etc/ssl/bitcoind/cert.pem\\')\\n  },\\n  port: 28332,\\n  ssl: true\\n});\\n```\\n\\n## Logging\\n\\nBy default, all requests made with `bitcoin-core` are logged using [uphold/debugnyan](https://github.com/uphold/debugnyan) with `bitcoin-core` as the logging namespace.\\n\\nPlease note that all sensitive data is obfuscated before calling the logger.\\n\\n#### Example\\n\\nExample output defining the environment variable `DEBUG=bitcoin-core`:\\n\\n```javascript\\nconst client = new Client();\\n\\nclient.getTransactionByHash(\\'b4dd08f32be15d96b7166fd77afd18aece7480f72af6c9c7f9c5cbeb01e686fe\\');\\n\\n// {\\n//   \"name\": \"bitcoin-core\",\\n//   \"hostname\": \"localhost\",\\n//   \"pid\": 57908,\\n//   \"level\": 20,\\n//   \"request\": {\\n//     \"headers\": {\\n//       \"host\": \"localhost:8332\",\\n//       \"accept\": \"application/json\"\\n//     },\\n//     \"id\": \"82cea4e5-2c85-4284-b9ec-e5876c84e67c\",\\n//     \"method\": \"GET\",\\n//     \"type\": \"request\",\\n//     \"uri\": \"http://localhost:8332/rest/tx/b4dd08f32be15d96b7166fd77afd18aece7480f72af6c9c7f9c5cbeb01e686fe.json\"\\n//   },\\n//   \"msg\": \"Making request 82cea4e5-2c85-4284-b9ec-e5876c84e67c to GET http://localhost:8332/rest/tx/b4dd08f32be15d96b7166fd77afd18aece7480f72af6c9c7f9c5cbeb01e686fe.json\",\\n//   \"time\": \"2017-02-07T14:40:35.020Z\",\\n//   \"v\": 0\\n// }\\n```\\n\\n### Custom logger\\n\\nA custom logger can be passed via the `logger` option and it should implement [bunyan\\'s log levels](https://github.com/trentm/node-bunyan#levels).\\n\\n## Tests\\nCurrently the test suite is tailored for Docker (including `docker-compose`) due to the multitude of different `bitcoind` configurations that are required in order to get the test suite passing.\\n\\nTo test using a local installation of `node.js` but with dependencies (e.g. `bitcoind`) running inside Docker:\\n\\n```sh\\nnpm run dependencies\\nnpm test\\n```\\n\\nTo test using Docker exclusively (similarly to what is done in Travis CI):\\n\\n```sh\\nnpm run testdocker\\n```\\n\\n## Release\\n\\n```sh\\nnpm version [<newversion> | major | minor | patch] -m \"Release %s\"\\n```\\n\\n## License\\nMIT\\n\\n[npm-image]: https://img.shields.io/npm/v/bitcoin-core.svg?style=flat-square\\n[npm-url]: https://npmjs.org/package/bitcoin-core\\n[travis-image]: https://img.shields.io/travis/ruimarinho/bitcoin-core.svg?style=flat-square\\n[travis-url]: https://travis-ci.org/ruimarinho/bitcoin-core\\n'},\n",
       " {'repo': 'jashmenn/bitcoin-reading-list',\n",
       "  'language': None,\n",
       "  'readme_contents': '## Programming Bitcoin Reading List and Projects\\n\\n* The goal of this document is to provide a reading list for learning to program Bitcoin transactions\\n* The theme of this document is practical and pragmatic instruction with the goal of writing code \\n\\nThe document is split into two major sections: [Content](#content) and [Code](#code)\\n\\n* The Content section contains a reading list which emphasizes programming Bitcoin transactions\\n* The Code section contains a list of open-source bitcoin projects ranging from modern popular tools to early historic implementations\\n* WIP: please send suggestions to [@eigenjoy](https://twitter.com/eigenjoy) or [open a GitHub issue](https://github.com/jashmenn/bitcoin-reading-list/issues)\\n\\n### <a name=\"content\"></a>Content\\n\\n#### Posts\\n* [Programming Bitcoin Transaction Scripts](https://docs.google.com/document/d/1D_gi_7Sf9sOyAHG25cMpOO4xtLq3iJUtjRwcZXFLv1E/edit) (Kofler)\\n* [Developer’s Introduction to Bitcoin](http://bitcoinmagazine.com/9249/developers-introduction-bitcoin/) (Buterin)\\n* [How Bitcoin Works Under the Hood](http://www.imponderablethings.com/2013/07/how-bitcoin-works-under-hood.html) (Driscoll)\\n* [Bitcoin Developer Guide](http://bitcoindev.us.to/en/developer-guide)\\n* [Bitcoin Scripts](http://www.bitcoinsecurity.org/2012/07/22/7/) (Koshy)\\n* [Bitcoins the hard way: Using the raw Bitcoin protocol](http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bitcoin.html) (Shirriff)\\n* [Bitcoin mining the hard way: the algorithms, protocols, and bytes](http://www.righto.com/2014/02/bitcoin-mining-hard-way-algorithms.html) (Shirriff)\\n* [Proving Your Bitcoin Reserves](https://iwilcox.me.uk/2014/proving-bitcoin-reserves) (Maxwell)\\n\\n#### Tutorials\\n* [The libbitcoin Tutorial](http://libbitcoin.dyne.org/doc/) (Taaki)\\n* [How to Parse the Bitcoin Blockchain](http://codesuppository.blogspot.com/2014/01/how-to-parse-bitcoin-blockchain.html) (Ratcliff)\\n* [How to extract every single bitcoin transaction from the blockchain and save it to an ASCII comma separated text file](http://codesuppository.blogspot.com/2014/03/how-to-extract-every-single-bitcoin.html) (Ratcliff)\\n* [How To Clone Scrypt Based Altcoins for Fun and Profit](http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide&rev=1391981820) (shakezula)\\n* [Signing Offline Transactions](https://gist.github.com/jashmenn/9811205) (Maxwell)\\n* [2 of 2 escrow example](https://gist.github.com/jashmenn/9811198) (Maxwell)\\n* [2 of 3 multisig example](https://gist.github.com/jashmenn/9811185) (Andresen)\\n* [How to decrypt messages in the blockchain from btcmsg](https://gist.github.com/ripper234/1625828) (ripper234)\\n\\n#### Papers\\n* [Original bitcoin paper](https://bitcoin.org/bitcoin.pdf) (Satoshi)\\n* [Annotated bitcoin paper](http://news.rapgenius.com/Satoshi-nakamoto-bitcoin-a-peer-to-peer-electronic-cash-system-annotated) (Satoshi / Rap Genius Community)\\n* [Proof of Ownership](http://frozenlock.files.wordpress.com/2011/11/master-bitcoin.pdf) (Fortin)\\n* [Colored Coins](https://bitcoil.co.il/BitcoinX.pdf) (Rosenfeld)\\n\\n#### Specifications\\n* [BIP70: Payments Protocol](https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki) (Andresen)\\n* [Working with the Payments Protocol](https://code.google.com/p/bitcoinj/wiki/PaymentProtocol) (Andresen)\\n* [BIP32: Hierarchical Deterministic (HD) Wallets](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) (Wuille)\\n* [BIP32 Implementation: Money Tree HD Wallet](https://github.com/BitVault/money-tree) (BitVault)\\n* [Deterministic Wallet](https://en.bitcoin.it/wiki/Deterministic_wallet)\\n* [Technical background of version 1 Bitcoin addresses](https://en.bitcoin.it/wiki/Technical_background_of_Bitcoin_addresses)\\n* [Transactions Reference](https://en.bitcoin.it/wiki/Transactions)\\n* [Script Reference](https://en.bitcoin.it/wiki/Script)\\n* [Raw Transactions API](https://en.bitcoin.it/wiki/Raw_Transactions)\\n* [Colored Coins Protocol Specification](https://github.com/Flavien/colored-coins-protocol/blob/master/specification.mediawiki) (Flavien)\\n* [The Mastercoin Protocol Specification](https://github.com/mastercoin-MSC/spec) (Gross)\\n* [Counterparty: Financial Instruments (Announcement)](https://bitcointalk.org/index.php?topic=395761.0)\\n\\n#### Discussion\\n* [There Is No \\'From\\' Address](https://iwilcox.me.uk/2014/no-from-address) (iwilcox)\\n* [Disentangling Crypto-Coin Mining: Timestamping, Proof-of-Publication, and Validation](http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg03307.html) (Todd)\\n* [Double-spending unconfirmed transactions is a lot easier than most people realise](  http://www.reddit.com/r/Bitcoin/comments/239bj1/doublespending_unconfirmed_transactions_is_a_lot/) (Todd)\\n* [Replace-by-fee scorched-earth without child-pays-for-parent](http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg05211.html) (Todd / Anonymous)\\n\\n#### Videos\\n* [Programming Bitcoin Youtube Channel](https://www.youtube.com/programmingbitcoin) (Murray)\\n* [How Bitcoin Works Under the Hood](https://www.youtube.com/watch?v=Lx9zgZCMqXE) (Driscoll)\\n* [Coding Multi-Signature Addresses](https://www.youtube.com/watch?v=zIbUSaZBJgU) (D\\'Angelo)\\n\\n#### API Docs\\n* [Bitcoin Doxygen](https://dev.visucore.com/bitcoin/doxygen/annotated.html)\\n* [Original Bitcoin client/API calls list](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list)\\n\\n#### Sidechains\\n* [Tree-chains preliminary summary](http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg04388.html) (Todd)\\n* [Why do people think that side-chains are going to be secure?](http://www.reddit.com/r/Bitcoin/comments/22vn4m/why_do_people_think_that_sidechains_are_going_to/cgqy5w6) (Maxwell)\\n* [Discussion on 2-way pegging: is there a way to do bitcoin-staging?](http://sourceforge.net/p/bitcoin/mailman/bitcoin-development/thread/20130519132359.GA12366%40netbook.cypherspace.org/#msg30868065)\\n* [Sidechains, Treechains, the TL;DR](http://blog.greenaddress.it/2014/06/13/sidechains-treechains-the-tldr/) (Sanders)\\n* [Sidechains Explained](http://cryptobizmagazine.com/sidechains-explained/) (Payne)\\n* [Side Chains: The How, The Challenges and the Potential](http://bitcoinmagazine.com/12349/side-chains-challenges-potential/) (Buterin)\\n* [Sidechain Technical Feasibility Discussion](https://bitcointalk.org/index.php?topic=566704.0;all) (discussion)\\n* [Alternative Chains / merged mining](https://en.bitcoin.it/wiki/Alternative_Chains) \\n\\n#### Beyond Payments\\n* [Timelock: time-release encryption incentivised by Bitcoins](http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg05547.html) (Todd / Taaki)\\n* [Decentralized digital asset exchange with honest pricing and market depth](http://www.mail-archive.com/bitcoin-development%40lists.sourceforge.net/msg03892.html) (Todd / Mizrahi)\\n\\n\\n### <a name=\"code\"></a>Code\\n\\n#### Core\\n* [bitcoin](https://github.com/bitcoin/bitcoin) `C++` (Satoshi) \\n* [bitcoinj: Java implementation of a Bitcoin client-only node](https://code.google.com/p/bitcoinj/) `Java` (bitcoinj)\\n* [bitcoin-qt: Qt GUI for C++ Bitcoin client](https://github.com/laanwj/bitcoin-qt) `C++` (laanwj)\\n* [bitcoinjs-lib: Bitcoin-related functions implemented in pure JavaScript](https://github.com/bitcoinjs/bitcoinjs-lib) `JavaScript` (bitcoinjs)\\n* [btcd: alternative full node bitcoin implementation written in Go](https://github.com/conformal/btcd) `Go` (conformal)\\n* [bitcore: interface to the bitcoin network](http://bitcore.io/) `Javascript` (BitPay)\\n* [cbitcoin low-level bitcoin library in standard C](https://github.com/MatthewLM/cbitcoin/) `C` (Mitchell)\\n* [btcwire: Implements the bitcoin wire protocol - core wire protocol package from btcd](https://github.com/conformal/btcwire) `Go` (conformal)\\n\\n#### Tools\\n* [pybitcointools: SImple, common-sense Bitcoin-themed Python ECC library](https://github.com/vbuterin/pybitcointools) `Python` (vbuterin)\\n* [bitcointools: Python-based tools for the Bitcoin cryptocurrency system](https://github.com/gavinandresen/bitcointools) `Python` (gavinandresen)\\n* [cryptocoin: Python module for working with cryptocurrencies](https://github.com/lyndsysimon/cryptocoin) `Python` (lyndsysimon)\\n* [bitcoin-ruby: bitcoin utils and protocol in ruby.](https://github.com/lian/bitcoin-ruby) `Ruby` (lian)\\n* [pycoin: Python-based Bitcoin utility library.](https://github.com/richardkiss/pycoin) `Python` (richardkiss)\\n* [bitcoin-testnet-box: Create a private, difficulty 1 bitcoin testnet](https://github.com/freewil/bitcoin-testnet-Box) `Shell` (freewil)\\n* [mastercoin-tools](https://github.com/grazcoin/mastercoin-tools) `Javascript` (grazcoin)\\n\\n#### Non-currency Applications\\n* [dissent: decentralized, transferable, and open software license system using the Bitcoin protocol](https://github.com/aaron-lebo/dissent) `Python` (Lebo)\\n\\n#### Beyond Payments\\n* [paypub: Trustless payments for information publishing on Bitcoin](https://github.com/unsystem/paypub) `C++` (Taaki / Todd)\\n\\n#### Miners\\n* [poclbm: PyOpenCL bitcoin miner](https://github.com/m0mchil/poclbm) `Python` (m0mchil) \\n* [DiabloMiner: OpenCL miner for Bitcoin](https://github.com/Diablo-D3/DiabloMiner) `Java` (Diablo-D3)\\n* [cpuminer: CPU miner for bitcoin](https://github.com/jgarzik/cpuminer) `C` (jgarzik)\\n* [Open-Source-FPGA-Bitcoin-Miner: Bitcoin Miner for Altera FPGAs](https://github.com/progranism/Open-Source-FPGA-Bitcoin-Miner) `Verilog` (progranism)\\n* [jsMiner: A Javascript Bitcoin miner](https://github.com/jwhitehorn/jsMiner) `JavaScript` (jwhitehorn)\\n* [pyminer: Python miner for bitcoin](https://github.com/jgarzik/pyminer) `Python` (jgarzik)\\n* [Bitcoin-JavaScript-Miner: A Bitcoin miner implemented in JavaScript.](https://github.com/progranism/Bitcoin-JavaScript-Miner) `JavaScript` (progranism)\\n* [cellminer: Bitcoin miner for the Cell Broadband Engine Architecture](https://github.com/verement/cellminer) `C` (verement)\\n* [oclminer: OpenCL bitcoin miner](https://github.com/tcatm/oclminer) `C` (tcatm)\\n* [Phoenix-Miner: Modular, fast, efficient Bitcoin miner](https://github.com/jedi95/Phoenix-Miner) `Python` (jedi95)\\n* [tumen_miner: An experimental BitCoin miner, which uses WebCL](https://github.com/temujin9/tumen_miner) `PHP` (temujin9)\\n* [Minimal-Bitcoin-Miner: CPU based Bitcoin Miner in C#](https://github.com/lithander/Minimal-Bitcoin-Miner) `C#` (lithander)\\n\\n#### Wallets\\n* [coinpunk: self-hosted Bitcoin wallet service](https://github.com/kyledrake/coinpunk) `Javascript` (kyledrake)\\n* [termcoin: A bitcoin wallet for your terminal](https://github.com/chjj/termcoin) `Javascript` (chjj)\\n* [pywallet: bitcoin wallet importer/exporter](https://github.com/joric/pywallet) `Python` (joric)\\n* [Hive: Bitcoin wallet for OS X](https://github.com/hivewallet/hive-osx) `Objective-C` (jsuder)\\n* [bitaddress.org: JavaScript Client-Side Bitcoin Wallet Generator](https://github.com/pointbiz/bitaddress.org) `Javascript` (pointbiz)\\n* [Multibit: desktop bitcoin client, powered by bitcoinj](https://github.com/jim618/multibit) `Java` (jim618)\\n* [bitcoin-wallet: A new kind of Bitcoin client](https://github.com/elis/bitcoin-wallet) `Python` (elis)\\n* [picocoin: A small bitcoin client](https://github.com/jgarzik/picocoin) `C` (jgarzik)\\n* [sx: sx - command line Bitcoin to empower the sysadmin](https://github.com/spesmilo/sx) `Python` (spesmilo)\\n* [Safebit: Chrome app wallet](https://github.com/elis/Safebit) (elis)\\n* [Bitcoin-akka: a client to btcwallet, written in Scala and built on akka](https://github.com/goldmar/bitcoin-akka/) (goldmar)\\n\\n#### Clients\\n* [libbitcoin: libbitcoin asynchronous C++ library for Bitcoin](https://github.com/spesmilo/libbitcoin) `C++` (spesmilo)\\n* [electrum: Bitcoin thin client](https://github.com/spesmilo/electrum) `Python` (spesmilo)\\n* [BitcoinArmory: Python-Based Bitcoin Software](https://github.com/etotheipi/BitcoinArmory) `Python` (etotheipi)\\n* [bitcoin-js-remote: Javascript remote for bitcoind](https://github.com/tcatm/bitcoin-js-remote) `JavaScript` (tcatm)\\n* [bitcoinjs-gui: Bitcoin client implementation in HTML5/JavaScript](https://github.com/bitcoinjs/bitcoinjs-gui) `JavaScript` (bitcoinjs)\\n* [bitcoin-php: Bitcoin library for PHP](https://github.com/mikegogulski/bitcoin-php) `PHP` (mikegogulski)\\n* [bitcoin-python: Friendly bitcoin API binding for Python](https://github.com/toomanysecrets0/bitcoin-python) `Python` (toomanysecrets0)\\n* [python-bitcoinrpc: Python interface to bitcoin\\'s JSON-RPC API](https://github.com/jgarzik/python-bitcoinrpc) `Python` (jgarzik)\\n* [bitcoinjs: Bitcoin client library in JavaScript using Node.js / MongoDB](https://github.com/bitcoinjs/bitcoinjs-server/) `javascript` (justmoon)\\n* [caesure: Python Bitcoin Client](https://github.com/samrushing/caesure) `Python` (samrushing)\\n* [chrome-bitcoin: bitcoin client in chrome](https://github.com/kiba/chrome-bitcoin) `JavaScript` (kiba)\\n* [node-bitcoin: Communicate with bitcoind via JSON-RPC](https://github.com/freewil/node-bitcoin) `JavaScript` (freewil)\\n* [gocoin: Bitcoin client library for Go / golang](https://github.com/piotrnar/gocoin) `Go` (piotrnar)\\n* [python-bitcoinlib: Bitcoin library](https://github.com/petertodd/python-bitcoinlib) `Python` (petertodd)\\n* [cbitcoin: A low-level bitcoin library written in standard C.](https://github.com/MatthewLM/cbitcoin) `C` (MatthewLM)\\n* [GoBit: A Golang implementation of Bitcoin](https://github.com/ThePiachu/GoBit) `Go` (ThePiachu)\\n* [Protocoin: A pure Python Bitcoin protocol implementation](https://github.com/perone/protocoin) `Python` (perone)\\n* [BitcoinLib: C# Bitcoin, Litecoin and Bitcoin-Clones Library & RPC Wrapper](https://github.com/GeorgeKimionis/BitcoinLib) `C#` (GeorgeKimionis)\\n\\n#### Mobile\\n* [bitcoin-wallet: Bitcoin Wallet app for your Android device](https://github.com/schildbach/bitcoin-wallet) `Java` (schildbach)\\n* [bitcoinApp: bitcoin for iOS devices](https://github.com/udibr/bitcoinApp) `Objective-C` (udibr) \\n* [bitcoin-android: Send and receive bitcoins from your Android phone](https://github.com/barmstrong/bitcoin-android) `Java` (barmstrong)\\n* [bitcoin-mobile-android](https://github.com/bitcoin-labs/bitcoin-mobile-android) `Java` (Schaaf)\\n* [BitcoinDroid: A thin Android client for Bitcoin](https://github.com/opposablebrain/BitcoinDroid) `Java` (opposablebrain)\\n* [CoreBitcoin: Well-documented Bitcoin implementation in Objective-C](https://github.com/oleganza/CoreBitcoin) `C` (oleganza)\\n* [wallet: Mycelium Bitcoin Wallet for Android](https://github.com/mycelium-com/wallet) `Java` (mycelium-com)\\n* [BitcoinKit: Cocoa framework for creating Bitcoin wallet apps](https://github.com/hivewallet/BitcoinKit) `C` (hivewallet)\\n* [BTCSquared: iOS framework for Bluetooth LE transactions](https://github.com/Gliph/BTCSquared) `Objective C` (Gliph)\\n\\n#### Exchanges\\n* [buttercoin: Opensource Bitcoin Exchange](https://github.com/buttercoin/buttercoin) `Javascript` (buttercoin)\\n* [QtBitcoinTrader: Secure Multi Trading Client](https://github.com/JulyIGHOR/QtBitcoinTrader) `C++` (JulyIGHOR)\\n* [BitWasp: Open Source Bitcoin Marketplace Software](https://github.com/Bit-Wasp/BitWasp) `PHP` (Bit-Wasp)\\n* [bitcoin-central: Bitcoin Central](https://github.com/davout/bitcoin-central) `Ruby` (davout)\\n* [ZeroReserve: Friend 2 Friend Payment and Bitcoin exchange](https://github.com/zeroreserve/ZeroReserve) `C++` (zeroreserve)\\n* [benjamin: bitcoin trading bot & analytics platform](https://github.com/mathisonian/benjamin) `JavaScript` (mathisonian)\\n* [Dark-Exchange: Dark Exchange is a distributed p2p exchange for bitcoin.](https://github.com/macourtney/Dark-Exchange) `Clojure` (macourtney)\\n* [btcnearme: Find Bitcoin traders near you... settle in cash](https://github.com/famulus/btcnearme) `Ruby` (famulus)\\n* [bitrated: Bitrated.com - Bitcoin arbitration marketplace](https://github.com/shesek/bitrated) `CoffeeScript` (shesek)\\n* [intersango: bitcoin exchange](https://github.com/dooglus/intersango) `PHP` (dooglus)\\n* [bitwrk: A Bitcoin-friendly, Anonymous Marketplace for Computing Power](https://github.com/indyjo/bitwrk) `Go` (indyjo)\\n\\n#### Merchant Tools\\n* [BitPay: Bitcoin payment application](https://github.com/warpi/BitPay) `Java` (warpi)\\n* [bitcoin-wp-e-commerce: Bitcoin payment plugin for WP e-Commerce for WordPress](https://github.com/mikegogulski/bitcoin-wp-e-commerce) `PHP` (mikegogulski)\\n* [Magento-Bitcoin-Payment-Module: Magento Payment Gateway Plugin for Bitcoin RPC API](https://github.com/jalder/Magento-Bitcoin-Payment-Module) `PHP` (jalder)\\n* [bitcoin-virtuemart: Bitcoin payment plugin for VirtueMart shopping cart for Joomla!](https://github.com/mikegogulski/bitcoin-virtuemart) `PHP` (mikegogulski)\\n* [magento-bitcoin: Bitcoin payment module for Magento.](https://github.com/ticean/magento-bitcoin) `PHP` (ticean)\\n* [Zen-Cart-Bitcoin-Payment-Module: A payment modules to interact with bitcoind for zen cart.](https://github.com/jalder/Zen-Cart-Bitcoin-Payment-Module) `PHP` (jalder)\\n* [MultiBitMerchant: A free and open source Bitcoin ecommerce platform, with several representative clients](https://github.com/gary-rowe/MultiBitMerchant) `Java` (gary-rowe)\\n\\n#### Bots\\n* [Bitcoin arbitrage: opportunity detector](https://github.com/maxme/bitcoin-arbitrage) `Python` (maxme)\\n* [gekko: A bitcoin trading bot](https://github.com/askmike/gekko) `Node.js` (askmike)\\n* [Redbit: Automated Bitcoin Trading Bot](https://github.com/hyppo/Redbit) `Python` (hyppo)\\n* [ArBit: An automated Bitcoin arbitrage trading program.](https://github.com/goteppo/ArBit) `Go` (goteppo)\\n* [cryptrade: Node.js Bitcoin bot for MtGox/Bitstamp/BTC-E/CEX.IO](https://github.com/pulsecat/cryptrade) `CoffeeScript` (pulsecat)\\n* [btc-trader: Robot for Bitcoin trading on BTC-e](https://github.com/therussianphysicist/btc-trader) `Ruby` (therussianphysicist)\\n* [ga-bitbot: Genetic algorithm trade system for bitcoin](https://code.google.com/p/ga-bitbot/) `Python` \\n\\n#### Block Exploration\\n* [bitcoin-abe: Abe: block browser for Bitcoin and similar currencies](https://github.com/jtobey/bitcoin-abe) `Python` (jtobey)\\n* [insight: A bitcoin blockchain API for web wallets](https://github.com/bitpay/insight) `JavaScript` (bitpay)\\n* [node-bitcoin-explorer: A Block Explorer clone built using node-bitcoin-p2p](https://github.com/bitcoinjs/node-bitcoin-explorer) `JavaScript` (bitcoinjs)\\n* [btcplex: BTCplex is an open source Bitcoin block chain browser written in Go, it allows you to search and navigate the block chain.](https://github.com/tsileo/btcplex) `Go` (tsileo)\\n* [blockparser: Fast, quick and dirty bitcoin blockchain parser](https://github.com/znort987/blockparser) `C++` (znort987)\\n\\n#### Pooling\\n* [p2pool: Peer-to-peer Bitcoin mining pool](https://github.com/forrestv/p2pool) `Python` (forrestv)\\n* [bitcoin-pool: early pooling server](https://github.com/doublec/bitcoin-pool) `C++` (doublec)\\n* [What is Pool Hopping?](http://bitcoin.stackexchange.com/questions/5072/what-is-pool-hopping) (Perry)\\n* [bitHopper: A python based poolhopper for bitcoin](https://github.com/c00w/bitHopper) `Python` (c00w)\\n* [Bitcoin-mining-proxy: Multi-pool, multi-worker proxy for Bitcoin miners ](https://github.com/cdhowie/Bitcoin-mining-proxy) `PHP` (cdhowie)\\n* [stratum-mining: Demo implementation of Bitcoin mining pool on Stratum protocol](https://github.com/slush0/stratum-mining) `Python` (slush0)\\n\\n#### Sites\\n* [petulant-lana: A one-time-payment filehosting site, using Bitcoin](https://github.com/bearbin/petulant-lana) `Go` (bearbin)\\n* [bitstarter-leaderboard: Bitcoin-powered crowdfunder](https://github.com/startup-class/bitstarter-leaderboard) `Javascript` (Srinivasan)\\n* [feedopensource: Iteratively Fund Open Source Projects With Bitcoin](https://github.com/dominictarr/feedopensource) `JavaScript` (dominictarr)\\n* [Bitcoin-Poker-Room: Sources for Bitcoin Poker Room.](https://github.com/hippich/Bitcoin-Poker-Room) `Python` (hippich)\\n* [BitHub: pay Bitcoin for GitHub commits](https://github.com/WhisperSystems/BitHub) `Java` (WhisperSystems) \\n\\n#### Related Protocols\\n* [bitid: Bitcoin Authentication Open Protocol](https://github.com/bitid/bitid) (Larch)\\n'},\n",
       " {'repo': '100trillionUSD/bitcoin',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': ''},\n",
       " {'repo': 'breadwallet/breadwallet-core',\n",
       "  'language': 'C',\n",
       "  'readme_contents': '# breadwallet-core\\nSPV bitcoin C library\\n\\n[getting started](https://github.com/breadwallet/breadwallet-core/wiki)\\n'},\n",
       " {'repo': 'davout/bitcoin-central',\n",
       "  'language': 'Ruby',\n",
       "  'readme_contents': '# Bitcoin Central\\nBitcoin Central powers bitcoin-central.net, a bitcoin trading platform. It is :\\n\\n* Open Source,\\n* Based on Ruby on Rails,\\n* Fully localizable,\\n* Multi-currency.\\n\\n# Installation\\nLinux and Windows setup work well, I found the easiest to be an Ubuntu install\\n\\n## Windows\\n* Install Ruby and MySQL\\n* Install Ruby Development Kit (https://github.com/oneclick/rubyinstaller/wiki/development-kit)\\n* Install rubygems\\n\\n## Linux (Debian flavors)\\n* Install required packages\\n\\n        $ sudo apt-get install ruby ruby-dev libssl-dev irb rubygems mysql-server libmysql++-dev build-essential git-core\\n\\n* Add gem binaries to path and re-login\\n\\n        # I simply add this at the end of /etc/bash.bashrc (feel free to point out a cleaner way)\\n        PATH=\"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/var/lib/gems/1.8/bin\"\\n\\n## Common\\n* Install the `bundler` rubygem, it will easily manage and compile all the other dependencies\\n\\n        $ sudo gem install bundler\\n\\n* Fork project if relevant\\n* Check out sources with git\\n\\n        $ git clone https://github.com/davout/bitcoin-central.git\\n\\n* Get into the sources directory\\n\\n        $ cd bitcoin-central\\n\\n* Compile and install the required dependencies\\n\\n        $ bundle\\n\\n* Log-in to MySQL console and run the following commands. If you are installing a production machine you\\'ll obviously need to pick different credentials. Update the `config/database.yml` file accordingly.\\n\\n        > CREATE DATABASE `bitcoin-bank_development`;\\n        > GRANT ALL PRIVILEGES ON `bitcoin-bank_development`.* TO \\'rails\\'@\\'localhost\\' IDENTIFIED BY \\'rails\\';\\n\\n* Run a couple of rake tasks (omit the `RAILS_ENV` option if you\\'re setting up a development environment, Rails will grab the database configuration in the `config/database.yml` file under the right section (development, test, or production)\\n\\n        $ rake db:migrate RAILS_ENV=production\\n\\n* Edit config/bitcoin.yml to be able to connect your instance to a bitcoin client, the `config/bitcoin.yml` file contents are self-explanatory, just add a production section if you\\'re deploying on a production server.\\n\\n* You\\'re good to go! Run the rails server\\n\\n        $ rails s\\n\\nYour fresh instance should now be running on `http://localhost:3000/` !\\n\\n## Production deployment\\n\\nUsually, Rails applications are deployed in production using nginx or Apache, I\\'ll introduce the Apache option.\\n\\nThe `capistrano` tool is used to automate pretty much every deployment step. Deploying a new version is as easy as typing `cap deploy` in your local command prompt.\\n\\nTo use the `cap` sweetness a couple of extra steps are required : \\n\\n* You\\'ll need to fork the project since all your deployment configuration is stored in `config/deploy.rb`, these configs are pulled directly from GitHub when deploying, so go for it, change them to suit your needs.\\n* Set the remote machine up by typing `cap deploy:setup`\\n* Log in to the remote machine and create the production configuration files in `{APP PATH}/shared/config/*.yml`, they will be used in production (you don\\'t want your production passwords hanging around on GitHub do you ?)\\n* Create the remote DB\\n* Now you can run locally `cap deploy:migrations`, this will update the remote sources and run the migrations on the remote database\\n* Now you just need to install the `passenger` gem on the remote server which will install an apache module\\n* Create an apache virtual host and you\\'re good to go.\\n\\nYou\\'ll just need to issue a `cap deploy` locally for any subsequent deployment.\\n\\n# Contributions\\nAll are welcome, improvements, fixes and translations (the string extraction bounty has been paid).\\n\\n * The use of the `Numeric#to_f` method is big no-no, every single numeric that passes through the code should be typed as `BigDecimal`,\\n * Bugfixes should include a failing test,\\n * Pull requests should apply cleanly on top of `master`, rebase if necessary\\n\\n# Music\\nBitcoin-Central was, and is currently being developed with the following musical background :\\n\\n * [Ali Farka Touré - In The Heart Of The Moon](http://www.amazon.fr/Heart-Farka-Tour%C3%A9-Toumani-Diabat%C3%A9/dp/B0009NDLJA)\\n * [Latchès](http://www.amazon.fr/Latches/dp/B001CISIGC/ref=sr_1_1?s=music&ie=UTF8&qid=1311581988&sr=1-1)\\n * Tons of [Django Reinhardt](http://www.amazon.fr/s/ref=nb_sb_ss_i_0_16?__mk_fr_FR=%C5M%C5Z%D5%D1&url=search-alias%3Dpopular&field-keywords=django+reinhardt&x=0&y=0&sprefix=django+reinhardt)\\n * [Biréli Lagrène - Blue Eyes](http://www.amazon.fr/Blue-Eyes-Bireli-Lagrene/dp/B000007N92/ref=sr_1_1?s=music&ie=UTF8&qid=1311582073&sr=1-1)\\n * Lots of [Gary Potter](http://www.amazon.fr/s/ref=nb_sb_noss?__mk_fr_FR=%C5M%C5Z%D5%D1&url=search-alias%3Dpopular&field-keywords=gary+potter&x=0&y=0)\\n * [Tchavolo Schmitt](http://www.amazon.fr/s/ref=nb_sb_ss_i_0_16?__mk_fr_FR=%C5M%C5Z%D5%D1&url=search-alias%3Dpopular&field-keywords=tchavolo+schmitt&x=0&y=0&sprefix=tchavolo+schmitt), [Romane](http://www.amazon.fr/s/ref=nb_sb_ss_i_0_16?__mk_fr_FR=%C5M%C5Z%D5%D1&url=search-alias%3Dpopular&field-keywords=tchavolo+schmitt&x=0&y=0&sprefix=tchavolo+schmitt#/ref=nb_sb_noss?__mk_fr_FR=%C3%85M%C3%85Z%C3%95%C3%91&url=search-alias%3Dpopular&field-keywords=romane&rh=n%3A301062%2Ck%3Aromane), [Angelo Debarre](http://www.amazon.fr/s/ref=nb_sb_ss_i_0_16?__mk_fr_FR=%C5M%C5Z%D5%D1&url=search-alias%3Dpopular&field-keywords=tchavolo+schmitt&x=0&y=0&sprefix=tchavolo+schmitt#/ref=nb_sb_noss?__mk_fr_FR=%C3%85M%C3%85Z%C3%95%C3%91&url=search-alias%3Dpopular&field-keywords=angelo+debarre&rh=n%3A301062%2Ck%3Aangelo+debarre)\\n * ....\\n\\n# License\\nAGPL License. Copyright 2010-2011 David FRANCOIS'},\n",
       " {'repo': 'bitpay/bitcore-wallet-service',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': \"\\n# bitcore-wallet-service\\n\\n\\nTHIS REPO HAVE BEEN MOVED TO BITCORE's MONO REPO. Check: \\nhttps://github.com/bitpay/bitcore/tree/master/packages/bitcore-wallet-service\\n\"},\n",
       " {'repo': 'Blockstream/esplora',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# Esplora Block Explorer\\n\\n[![build status](https://api.travis-ci.org/Blockstream/esplora.svg)](https://travis-ci.org/Blockstream/esplora)\\n[![docker release](https://img.shields.io/docker/pulls/blockstream/esplora.svg)](https://hub.docker.com/r/blockstream/esplora)\\n[![MIT license](https://img.shields.io/github/license/blockstream/esplora.svg)](https://github.com/blockstream/esplora/blob/master/LICENSE)\\n[![Pull Requests Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](http://makeapullrequest.com)\\n[![IRC](https://img.shields.io/badge/chat-on%20freenode-brightgreen.svg)](https://webchat.freenode.net/?channels=bitcoin-explorers)\\n\\nBlock explorer web interface based on the [esplora-electrs](https://github.com/Blockstream/electrs) HTTP API.\\n\\nWritten as a single-page app in a reactive and functional style using\\n[rxjs](https://github.com/ReactiveX/rxjs) and [cycle.js](https://cycle.js.org/).\\n\\nSee live at [Blockstream.info](https://blockstream.info/).\\n\\nAPI documentation [is available here](API.md).\\n\\nJoin the translation efforts on [Transifex](https://transifex.com/blockstream/esplora/).\\n\\n![Esplora](https://raw.githubusercontent.com/Blockstream/esplora/master/flavors/blockstream/www/img/social-sharing.png)\\n\\n## Features\\n\\n- Explore blocks, transactions and addresses\\n\\n- Support for Segwit and Bech32 addresses\\n\\n- Shows previous output and spending transaction details\\n\\n- Quick-search for txid, address, block hash or height by navigating to `/<query>`\\n\\n- Advanced view with script hex/assembly, witness data, outpoints and more\\n\\n- Mobile-ready responsive design\\n\\n- Translated to 17 languages\\n\\n- Light and dark themes\\n\\n- Noscript support\\n\\n- For Liquid and other Elements-based chains: support for CT, peg-in/out transactions and multi-asset\\n\\n- Mainnet, Testnet and Elements high performance electrum server\\n\\n## Developing\\n\\nTo start a development server with live babel/browserify transpilation, run:\\n\\n```bash\\n$ git clone https://github.com/Blockstream/esplora && cd esplora\\n$ npm install\\n$ export API_URL=http://localhost:3000/ # or https://blockstream.info/api/ if you don\\'t have a local API server\\n# (see more config options below)\\n$ npm run dev-server\\n```\\n\\nThe server will be available at http://localhost:5000/\\n\\nTo display debugging information for the Rx streams in the web developer console, set `localStorage.debug = \\'*\\'` and refresh.\\n\\n## Building\\n\\nTo build the static assets directory for production deployment, set config options (see below)\\nand run `$ npm run dist`. The files will be created under `dist/`.\\n\\nBecause Esplora is a single-page app, the HTTP server needs to be configured to serve the `index.html` file in reply to missing pages.\\nSee [`contrib/nginx.conf.in`](contrib/nginx.conf.in) for example nginx configuration (TL;DR: `try_files $uri /index.html`).\\n\\n## Pre-rendering server (noscript)\\n\\nTo start a pre-rendering server that generates static HTML replies suitable for noscript users, run:\\n\\n```bash\\n# (clone, cd, \"npm install\" and configure as above)\\n\\n$ export STATIC_ROOT=http://localhost:5000/ # for loading CSS, images and fonts\\n$ npm run prerender-server\\n```\\n\\nThe server will be available at http://localhost:5001/\\n\\n## Configuration options\\n\\nAll options are optional.\\n\\n### GUI options\\n\\n- `NODE_ENV` - set to `production` to enable js minification, or to `development` to disable (defaults to `production`)\\n- `BASE_HREF` - base href for user interface (defaults to `/`, change if not served from the root directory)\\n- `STATIC_ROOT` - root for static assets (defaults to `BASE_HREF`, change to load static assets from a different server)\\n- `API_URL` - URL for HTTP REST API (defaults to `/api`, change if the API is available elsewhere)\\n- `CANONICAL_URL` - absolute base url for user interface (optional, only required for opensearch and canonical link tags)\\n- `NATIVE_ASSET_LABEL` - the name of the network native asset (defaults to `BTC`)\\n- `SITE_TITLE` - website title for `<title>` (defaults to `Block Explorer`)\\n- `SITE_DESC` - meta description (defaults to `Esplora Block Explorer`)\\n- `HOME_TITLE` - text for homepage title (defaults to `SITE_TITLE`)\\n- `SITE_FOOTER` - text for page footer (defaults to `Powered by esplora`)\\n- `HEAD_HTML` - custom html to inject at the end of `<head>`\\n- `FOOT_HTML` - custom html to inject at the end of `<body>`\\n- `CUSTOM_ASSETS` - space separated list of static assets to add to the build\\n- `CUSTOM_CSS` - space separated list of css files to append into `style.css`\\n- `NOSCRIPT_REDIR` - redirect noscript users to `{request_path}?nojs` (should be captured server-side and redirected to the prerender server, also see `NOSCRIPT_REDIR_BASE` in dev server options)\\n\\nNote that `API_URL` should be set to the publicly-reachable URL where the user\\'s browser can issue requests at.\\n(that is, *not* via `localhost`, unless you\\'re setting up a dev environment where the browser is running on the same machine as the API server.)\\n\\nElements-only configuration:\\n\\n- `IS_ELEMENTS` - set to `1` to indicate this is an Elements-based chain (enables asset issuance and peg features)\\n- `NATIVE_ASSET_ID` - the ID of the native asset used to pay fees (defaults to `6f0279e9ed041c3d710a9f57d0c02928416460c4b722ae3457a11eec381c526d`, the asset id for BTC)\\n- `BLIND_PREFIX` - the base58 address prefix byte used for confidential addresses (defaults to `12`)\\n- `PARENT_CHAIN_EXPLORER_TXOUT` - URL format for linking to transaction outputs on the parent chain, with `{txid}` and `{vout}` as placeholders. Example: `https://blockstream.info/tx/{txid}#output:{vout}`\\n- `PARENT_CHAIN_EXPLORER_ADDRESS` - URL format for linking to addresses on parent chain, with `{addr}` replaced by the address. Example: `https://blockstream.info/address/{addr}`\\n- `ASSET_MAP_URL` - url to load json asset map (in the \"minimal\" format)\\n\\nMenu configuration (useful for inter-linking multiple instances on different networks):\\n\\n- `MENU_ITEMS` - json map of menu items, where the key is the label and the value is the url\\n- `MENU_ACTIVE` - the active menu item identified by its label\\n\\n### Development server options\\n\\nAll GUI options, plus:\\n\\n- `PORT` - port to bind http development server (defaults to `5000`)\\n- `CORS_ALLOW` - value to set for `Access-Control-Allow-Origin` header (optional)\\n- `NOSCRIPT_REDIR_BASE` - base url for prerender server, for redirecting `?nojs` requests (should be set alongside `NOSCRIPT_REDIR`)\\n\\n### Pre-rendering server options\\n\\nAll GUI options, plus:\\n\\n- `PORT` - port to bind pre-rendering server (defaults to `5001`)\\n\\nNote that unlike the regular JavaScript-based app that sends API requests from the client-side,\\nthe pre-rendering server sends API requests from the server-side. This means that `API_URL` should\\nbe configured to the URL reachable by the server, typically `http://localhost:3000/`.\\n\\n## How to build the Docker image\\n\\n```\\ndocker build -t esplora .\\n```\\n\\n## How to run the explorer for Bitcoin mainnet\\n\\n```\\ndocker run -p 50001:50001 -p 8080:80 \\\\\\n           --volume $PWD/data_bitcoin_mainnet:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh bitcoin-mainnet explorer\"\\n```\\n\\n## How to run the explorer for Liquid mainnet\\n\\n```\\ndocker run -p 50001:50001 -p 8082:80 \\\\\\n           --volume $PWD/data_liquid_mainnet:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh liquid-mainnet explorer\"\\n```\\n\\n## How to run the explorer for Bitcoin testnet3\\n\\n```\\ndocker run -p 50001:50001 -p 8084:80 \\\\\\n           --volume $PWD/data_bitcoin_testnet:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh bitcoin-testnet explorer\"\\n```\\n\\n## How to run the explorer for Bitcoin signet\\n\\n```\\ndocker run -p 50001:50001 -p 8084:80 \\\\\\n           --volume $PWD/data_bitcoin_signet:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh bitcoin-signet explorer\"\\n```\\n\\n## How to run the explorer for Liquid testnet\\n\\n```\\ndocker run -p 50001:50001 -p 8096:80 \\\\\\n           --volume $PWD/data_liquid_testnet:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh liquid-testnet explorer\"\\n```\\n\\n## How to run the explorer for Liquid regtest\\n\\n```\\ndocker run -p 50001:50001 -p 8092:80 \\\\\\n           --volume $PWD/data_liquid_regtest:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh liquid-regtest explorer\"\\n```\\n\\n## How to run the explorer for Bitcoin regtest\\n\\n```\\ndocker run -p 50001:50001 -p 8094:80 \\\\\\n           --volume $PWD/data_bitcoin_regtest:/data \\\\\\n           --rm -i -t esplora \\\\\\n           bash -c \"/srv/explorer/run.sh bitcoin-regtest explorer\"\\n```\\n\\n## Regtest options\\n\\nWhen run for Bitcoin regtest or Liquid regtest, the esplora container will\\ncreate a default wallet and mine 100 blocks internally. You can disable this behavior\\nby setting `NO_REGTEST_MINING=1`.\\n\\n## Docker config options\\n\\nSet `-e DEBUG=verbose` to enable more verbose logging.\\n\\nSet `-e NO_PRECACHE=1` to disable pre-caching of statistics for \"popular addresses\",\\nwhich may take a long time and is not necessary for personal use.\\n\\nSet `-e NO_ADDRESS_SEARCH=1` to disable the [by-prefix address search](https://github.com/Blockstream/esplora/blob/master/API.md#get-address-prefixprefix) index.\\n\\nSet `-e ENABLE_LIGHTMODE=1` to enable [esplora-electrs\\'s light mode](https://github.com/Blockstream/electrs/#light-mode).\\n\\nSet `-e ONION_URL=http://xyz.onion` to enable the `Onion-Location` header.\\n\\n## Build new esplora-base\\n\\n```\\ndocker build -t blockstream/esplora-base:latest -f Dockerfile.deps .\\ndocker push blockstream/esplora-base:latest\\ndocker inspect --format=\\'{{index .RepoDigests 0}}\\' blockstream/esplora-base\\n```\\n\\n## Build new tor (or you can pull directly from Docker Hub - `blockstream/tor:latest`)\\n\\n```\\ndocker build --squash -t blockstream/tor:latest -f Dockerfile.tor .\\ndocker push blockstream/tor:latest\\ndocker inspect --format=\\'{{index .RepoDigests 0}}\\' blockstream/tor\\n```\\nRun: `docker -d --name hidden_service blockstream/tor:latest tor -f /home/tor/torrc` (could add a `-v /extra/torrc:/home/tor/torrc`, if you have a custom torrc)\\n\\nExample torrc:\\n```\\nDataDirectory /home/tor/tor\\nPidFile /var/run/tor/tor.pid\\n\\nControlSocket /var/run/tor/control GroupWritable RelaxDirModeCheck\\nControlSocketsGroupWritable 1\\nSocksPort unix:/var/run/tor/socks WorldWritable\\nSocksPort 9050\\n\\nCookieAuthentication 1\\nCookieAuthFileGroupReadable 1\\nCookieAuthFile /var/run/tor/control.authcookie\\n\\nLog [handshake]debug [*]notice stderr\\n\\nHiddenServiceDir /home/tor/tor/hidden_service_v3/\\nHiddenServiceVersion 3\\nHiddenServicePort 80 127.0.0.1:80\\n```\\n\\n## License\\n\\nMIT\\n'},\n",
       " {'repo': 'Diablo-D3/DiabloMiner',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': \"# This program is unmaintained and does not support the current miner protocol. Use cgminer instead. Do not create issues about this program being broken because it will not be fixed by the original developers. If you want to fix it, you're welcome to fork it.\\n\\n# DiabloMiner - OpenCL miner for BitCoin #\\n    Copyright (C) 2010 - 2013 Patrick McFarland <diablod3@gmail.com>\\n\\n    This program is free software: you can redistribute it and_or modify\\n    it under the terms of the GNU General Public License as published by\\n    the Free Software Foundation, either version 3 of the License, or\\n    (at your option) any later version.\\n\\n    This program is distributed in the hope that it will be useful,\\n    but WITHOUT ANY WARRANTY; without even the implied warranty of\\n    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the\\n    GNU General Public License for more details.\\n\\n    You should have received a copy of the GNU General Public License\\n    along with this program.  If not, see <http://www.gnu.org_licenses/>.\\n\\n# Donations #\\nBitcoins and Devcoins: __1DbeWKCxnVCt3sRaSAmZLoboqr8pVyFzP1__\\n\\n# Warning #\\nDiabloMiner is a command line program. This means you need to open a terminal\\n(cmd.exe, Terminal.app/iTerm2, xterm, etc) and run the program with the proper\\narguments from there.\\n\\nYou __require__ hardware that is capable of running OpenCL.\\n\\n# MacOSX Warning #\\nApple's OpenCL drivers often exhibit strange bugs.\\n\\nIf DiabloMiner is displaying warnings about `CL_INVALID_WORK_GROUP_SIZE`, add\\n`-w 64` to your arguments.\\n\\n# How to download #\\n__[Binary download here](http://adterrasperaspera.com/DiabloMiner.zip)__\\n\\nThis download is always kept up to date with the newest version of the source.\\n\\n# How to build #\\nDiabloMiner requires the SDK for Java 6.0 or higher installed, as well as\\nMaven 3.x. Maven will download the rest of the dependencies.\\n\\nDiabloMiner uses launch4j to build Windows binaries. launch4j requires and\\npartially includes a build chain for Win32. launch4j cannot be ran on any\\n64-bit only version of OSX (10.6 and up) and is difficult to run on Windows.\\n\\nDiabloMiner's git repo does not contian binaries, so if you want to build\\nDiabloMiner from source, heed the above warning and run `mvn package`.\\n\\n# How to use #\\n# Single pool and solo mining #\\n`./DiabloMiner-YourOS.sh -u username -p password -o host -r port`\\n\\nor\\n\\n`./DiabloMiner-YourOS.sh -l http://username:password@host:port`\\n\\nFor solo mining, your host is `localhost` your port is `8332`, and your\\nusername and password is what you set in your bitcoind's `bitcoin.conf`.\\nSee bitcoin documentation for further information on how to enable the RPC\\nAPI.\\n\\n## Multiple pools ##\\n`./DiabloMiner-YourOS.sh -u username1,username2 -p password1,password2\\n -o host1,host2 -r port1,port2`\\n\\nDiabloMiner supports unlimited pools and will switch to the next pool on\\nconnection failure and return to the first pool every 60 minutes.\\n\\n# Optimization #\\n## MacOSX on any hardware ##\\nIt is recommended you use the default settings, see also the MacOSX warning\\nabove.\\n\\n## Nvidia hardware on any OS ##\\nIt is recommended you use the default settings, however if your desktop is\\nlagging badly try adding `-f 120`, `-f 180`, or `-f 240`.\\n\\n## Intel hardware on any OS ##\\nDiabloMiner has not been tested on Intel GPUs. Default is most likely correct.\\n\\n## AMD Radeon VLIW4 ##\\nR7xx\\n\\n* Radeon discrete: 43xx, 45xx, 46xx, 47xx, 48xx\\n* Radeon mobile: 43xxM, 45xxM, 46xxM, 48xxM, 5xxV, 51xxM\\n* FirePro: V3750, V7750, V8700, V8750, 2450, RG220\\n* FirePro mobile: M7740\\n* FireStream: 9250, 9270\\n\\n`-v 2`\\n\\n## AMD Radeon VLIW5 ##\\nCedar, Redwood, Juniper, Cypress, Hemlock\\n\\n* Radeon discrete: 54xx, 55xx, 56xx, 57xx, 58xx, 59xx, 63xx, 6750, 6770, 73xx\\n* Radeon mobile: 54xxM, 56xxM, 57xxM, 58xxM, 63xxM, 65xxM, 68xxM,\\n* FirePro: V3800, V4800, V5800, V7800, V8800, V9800, 2270, 2460\\n* FirePro mobile: M5800, M7820\\n* FireStream: 9350, 9370\\n\\nOn some cards `-v 2,1` is faster, on others `-v 2`. Try both.\\n\\n## AMD Radeon VLIW5 Gen2 ##\\nCaicos, Turks, Barts, Wrestler, Ontario, Zacate, WinterPark, BeaverCreek\\n\\n* Radeon discrete: 64xx, 65xx, 66xx, 6790, 68xx, 74xx, 75xx, 76xx\\n* Radeon mobile: 64xxM, 66xxM, 67xxM, 69xxM, 74xxM, 75xxM, 76xxM\\n* Radeon mobile IGP: 63xxG, 64xxG, 65xxG, 66xxG\\n* Fusion APU: 62xx, 63xx, 64xxD, 65xxD, 74xxD, 75xxD, 76xxD\\n* FirePro: V3900, V4900\\n* FirePro mobile: M5950, M8900, M2000\\n\\nUse `-v 2`\\n\\n## AMD Radeon VLIW4\\nCayman, Antilles, Devastator\\n\\n* Radeon discrete: 69xx\\n* Radeon mobile: 64xxM, 66xxM, 67xxM\\n* Fusion APU: 74xxD\\n* FirePro: V5900, V7900\\n\\nUse `-v 2`\\n\\n## AMD Radeon GCN\\nCape Verde, Pitcairn, Tahiti, New Zealand, Malta, Bonaire\\n* Radeon discrete: 77xx, 78xx, 79xx\\n* Radeon mobile: 77xxM, 78xxM, 79xxM\\n* FirePro: W600, W5000, W7000, W8000, W9000, S7000, S9000, S10000, R5000\\n* FirePro mobile: M4000, M6000\\n* Sky: 500, 700, 900\\n\\nUse defaults.\\n\\n# Command line arugments #\\n* __-u, -p, -o, -r__ Username, password, host, port\\n* __-l__ Fully fledged URL, ex: http://username:password@host:port/\\n* __-x__ Proxy, ex: host:port<:username:password>\\n* __-d__ Debug output\\n* __-D__ Use specific devices. Default is all.\\n* __-f__ FPS, controls how many kernel executions a second happen, default is 30\\n* __-w__ Controls OpenCL workgroup size, default is hardware detected maximum\\n* __-v__: Change manual SIMD parallel alignment.\\n * -v 1: The same as off/single hash, and is the default (`uint`)\\n * -v 2 through 16: Tries more than one hash via SIMD (`uint2` through `uint16`)\\n * -v 1,1, etc: Non-SIMD interleaving on top of SIMD, faster on a very small\\n   minority of hardware (`-v 2,1` is faster than `-v 2` on some Radeon VLIW5)\\n\\n\"},\n",
       " {'repo': 'freewil/bitcoin-testnet-box',\n",
       "  'language': 'Dockerfile',\n",
       "  'readme_contents': '# bitcoin-testnet-box\\n[![docker pulls](https://img.shields.io/docker/pulls/freewil/bitcoin-testnet-box.svg?style=flat)](https://hub.docker.com/r/freewil/bitcoin-testnet-box/)\\n\\nCreate your own private bitcoin testnet\\n\\nYou must have `bitcoind` and `bitcoin-cli` installed on your system and in the\\npath unless running this within a [Docker](https://www.docker.com) container\\n(see [below](#using-with-docker)).\\n\\n## Large Git History\\nIf you\\'d like to clone this git repository locally and disk space or bandwidth\\nusage is of concern, it\\'s suggested to do a shallow clone, excluding some\\nearlier history of the repo, where some testnet data was included.\\n\\n> Regular clone: `du -sh .` 44M\\n\\n> Shallow clone: `du -sh .` 168K\\n\\n### Regular Clone\\n```\\ngit clone git@github.com:freewil/bitcoin-testnet-box.git\\n```\\n\\n### Shallow Clone\\n```\\ngit clone --shallow-since 2014-10-18 git@github.com:freewil/bitcoin-testnet-box.git\\n```\\n\\n## Starting the testnet-box\\n\\nThis will start up two nodes using the two datadirs `1` and `2`. They\\nwill only connect to each other in order to remain an isolated private testnet.\\nTwo nodes are provided, as one is used to generate blocks and it\\'s balance\\nwill be increased as this occurs (imitating a miner). You may want a second node\\nwhere this behavior is not observed.\\n\\nNode `1` will listen on port `19000`, allowing node `2` to connect to it.\\n\\nNode `1` will listen on port `19001` and node `2` will listen on port `19011`\\nfor the JSON-RPC server.\\n\\n\\n```\\n$ make start\\n```\\n\\n## Check the status of the nodes\\n\\n```\\n$ make getinfo\\nbitcoin-cli -datadir=1  getinfo\\n{\\n    \"version\" : 90300,\\n    \"protocolversion\" : 70002,\\n    \"walletversion\" : 60000,\\n    \"balance\" : 0.00000000,\\n    \"blocks\" : 0,\\n    \"timeoffset\" : 0,\\n    \"connections\" : 1,\\n    \"proxy\" : \"\",\\n    \"difficulty\" : 0.00000000,\\n    \"testnet\" : false,\\n    \"keypoololdest\" : 1413617762,\\n    \"keypoolsize\" : 101,\\n    \"paytxfee\" : 0.00000000,\\n    \"relayfee\" : 0.00001000,\\n    \"errors\" : \"\"\\n}\\nbitcoin-cli -datadir=2  getinfo\\n{\\n    \"version\" : 90300,\\n    \"protocolversion\" : 70002,\\n    \"walletversion\" : 60000,\\n    \"balance\" : 0.00000000,\\n    \"blocks\" : 0,\\n    \"timeoffset\" : 0,\\n    \"connections\" : 1,\\n    \"proxy\" : \"\",\\n    \"difficulty\" : 0.00000000,\\n    \"testnet\" : false,\\n    \"keypoololdest\" : 1413617762,\\n    \"keypoolsize\" : 101,\\n    \"paytxfee\" : 0.00000000,\\n    \"relayfee\" : 0.00001000,\\n    \"errors\" : \"\"\\n}\\n```\\n## Creating wallets\\n\\n```\\nbitcoin-cli -datadir=1 createwallet wallet1\\n```\\n\\n```\\nbitcoin-cli -datadir=2 createwallet wallet2\\n```\\n\\n## Generating blocks\\n\\nNormally on the live, real, bitcoin network, blocks are generated, on average,\\nevery 10 minutes. Since this testnet-in-box uses Bitcoin Core\\'s (bitcoind)\\nregtest mode, we are able to generate a block on a private network\\ninstantly using a simple command.\\n\\nTo generate a block:\\n\\n```\\n$ make generate\\n```\\n\\nTo generate more than 1 block:\\n\\n```\\n$ make generate BLOCKS=10\\n```\\n\\n## Need to generate at least 100 blocks before there will be a balance in the first wallet\\n```\\n$ make generate BLOCKS=200\\n```\\n\\n## Verify that there is a balance on the first wallet\\n```\\n$ make getinfo\\n```\\n\\n## Generate a wallet address for the second wallet\\n```\\n$ make address2\\n```\\n\\n## Sending bitcoins\\nTo send bitcoins that you\\'ve generated to the second wallet: (be sure to change the ADDRESS value below to wallet address generated in the prior command)\\n\\n```\\n$ make sendfrom1 ADDRESS=mxwPtt399zVrR62ebkTWL4zbnV1ASdZBQr AMOUNT=10\\n```\\n\\n## Does the balance show up?\\nRun the getinfo command again. Does the balance show up? Why not?\\n```\\n$ make getinfo\\n```\\n\\n## Generate another block\\n```\\n$ make generate\\n```\\n\\n## Stopping the testnet-box\\n\\n```\\n$ make stop\\n```\\n\\nTo clean up any files created while running the testnet and restore to the\\noriginal state:\\n\\n```\\n$ make clean\\n```\\n\\n## Using with docker\\nThis testnet-box can be used with [Docker](https://www.docker.com/) to run it in\\nan isolated container.\\n\\n### Building docker image\\n\\nPull the image\\n  * `docker pull freewil/bitcoin-testnet-box`\\n\\nor build it yourself from this directory\\n  * `docker build -t bitcoin-testnet-box .`\\n\\n### Running docker container\\nThe docker image will run two bitcoin nodes in the background and is meant to be\\nattached to allow you to type in commands. The image also exposes\\nthe two JSON-RPC ports from the nodes if you want to be able to access them\\nfrom outside the container.\\n      \\n   `$ docker run -t -i -p 19001:19001 -p 19011:19011 freewil/bitcoin-testnet-box`\\n\\nor if you built the docker image yourself:\\n\\n   `$ docker run -t -i -p 19001:19001 -p 19011:19011 bitcoin-testnet-box`\\n\\n## Running without docker\\nTo run without docker, one should download the supported Bitcoin core version. \\nTo find the supported version, search for the `BITCOIN_CORE_VERSION` environment variable\\nin the `Dockerfile` file.\\n'},\n",
       " {'repo': 'Bitlits/Bitcoin-Games',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': '<p align=\"center\">\\n<img src=\"https://i.postimg.cc/HLmRx2My/logo.png\" width=\"140\" align=\"center\">\\n  </p>\\n<p align=\"center\">\\n  <a href=\"https://bitlits.com\">\\n  </a>\\n</p>\\n\\n<p align=\"center\">\\n  <a href=\"https://itunes.apple.com/us/app/\">\\n    <img alt=\"Download on the App Store\" title=\"App Store\" src=\"http://i.imgur.com/0n2zqHD.png\" width=\"140\">\\n  </a>\\n\\n  <a href=\"https://play.google.com/store/apps/details?id=io.gonative.android.xrwyjq\">\\n    <img alt=\"Get it on Google Play\" title=\"Google Play\" src=\"http://i.imgur.com/mtGRPuM.png\" width=\"140\">\\n  </a>\\n</p>\\n\\n## Translations\\n🇬🇷 [ελληνικά](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇫🇷 [Français](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇰🇷 [한국어](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/KO_README.md) | 🇨🇳 [普通話](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇹🇼 [台灣話](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇲🇽 [Español](https://github.com/Jfaler/Bitcoin-Casino/blob/master/doc/) | 🇹🇷 [Türkçe](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇩🇪 [Deutsch](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇮🇹 [Italiano](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇮🇳 [हिन्दी](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | [Arabic](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇵🇹 [Português](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇷🇺 [Русский язык](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇯🇵 [日本語](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/) | 🇻🇳 [tiếng việt](https://github.com/bitlits/Bitcoin-Casino/blob/master/doc/)\\n\\n### Features\\n\\n* 🎰 Designed as a high performance cryptocurrency game.\\n* 🧠 Built-in high performance RNG-engine.\\n* 🙊 Anonymous login with no sign up required.\\n* ⚖️ Provably Fair - Each game has a single transaction ID (TXID for short). To get the winning numbers, we convert the TXID from base 16 to base 10 and then pick the first two numbers from the TXID as the winning numbers.\\n* 💡 Usability and scalability.\\n* ⚛️ Supports multiple digital currencies (eg. Bitcoin, Litecoin, Dogecoin etc.).\\n* 📖 Powerful admin dashboard and management tools.\\n* 🔧 Highly configurable and extendable.\\n* 🔐 Industry standard security out of the box.\\n* 💬 Active community behind.\\n\\n## Release History\\n\\n* 1.0\\n    * CHANGE: Update docs (module code remains unchanged)\\n\\n## 🔧 Prerequisites \\n\\n* Ubuntu 18.04\\n* Git 1.7.10+\\n* Sqlite\\n* Mustache\\n* PhpLiteAdmin v1.9.8.2\\n* Apache2\\n* RedBean\\n\\n## 🚀 Installation & Deployment\\n\\n* <p>Sign up with <a target=\"_blank\" href=\"https://m.do.co/c/397fb2277475\">Digital Ocean</a><img width=\"1\" height=\"1\" border=\"0\" alt=\"\" style=\"border:none !important; margin:0px !important;\" /></p>\\n* Install LAMP https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-on-ubuntu-16-04\\n* Edit the configuration file `sudo nano /base/init.php`\\n* Install Litecoin & start the Litecoin Daemon `sudo litecoind` https://github.com/bitlits/Bitcoin-Casino/wiki/Install-Litecoin-for-Bitcoin-Casino-&-Bitcoin-Slot-Machine\\n* Edit the configuration file `sudo nano /vendor/sql/phpliteadmin.conf.php`\\n* Access PhpLiteAdmin Dashboard http://example.com/vendor/sql/phpliteadmin.php\\n'},\n",
       " {'repo': 'mycelium-com/wallet-android',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': 'Beta channel\\n============\\n\\nIn order to receive updates quicker than others, you need to enable beta versions of the software in\\n[Google Play](https://play.google.com/apps/testing/com.mycelium.wallet)\\n\\nAs beta testers, please make sure you have a recent **backup of the masterseed** and all **private keys** inside Mycelium. Beta testers will experience many bugs.\\nSo far, restoring the wallet from masterseed has never been necessary, but we offer no guarantees.\\n\\nBuilding\\n========\\n\\nTo build everything from source, simply checkout the source and build using gradle on the build system you need:\\n\\n * JDK 1.8\\n\\nThe project layout is designed to be used with a recent version of Android Studio (currently 4.1.2)\\n\\n#### Build commands\\n\\nTo get the source code, type:\\n\\n    git clone https://github.com/mycelium-com/wallet-android.git\\n    cd wallet-android\\n    git submodule update --init --recursive\\n\\nLinux/Mac type:\\n\\n    ./gradlew clean test mbw::assembleProdnetRelease mbw::assembleBtctestnetRelease\\n\\nWindows type:\\n\\n    gradlew.bat clean test mbw::assembleProdnetRelease mbw::assembleBtctestnetRelease\\n\\n - Voila, look into `mbw/build/outputs/apk/` to see the generated apk.\\n   There are versions for both prodnet and testnet.\\n\\nAlternatively you can install the latest version from the [Play Store](https://play.google.com/store/apps/details?id=com.mycelium.wallet).\\n\\nIf you cannot access the Play store, you can obtain the apk directly from the Mycelium Bitcoin\\nWallet [download page](https://wallet.mycelium.com/).\\n\\nApp Download Verification\\n-------------------------\\n\\nAll versions released by Mycelium are signed with the same release keys. If you do not trust the apk\\nyou can check that signature with\\n[apksigner](https://developer.android.com/studio/command-line/apksigner.html#options-verify):\\n\\n```\\napksigner verify --print-certs --verbose mycelium.apk\\n```\\n\\nThe output should look like:\\n\\n```\\nVerifies\\nVerified using v1 scheme (JAR signing): true\\nVerified using v2 scheme (APK Signature Scheme v2): true\\nVerified using v3 scheme (APK Signature Scheme v3): false\\nNumber of signers: 1\\nSigner #1 certificate DN: CN=Mycelium Developers, O=Mycelium, L=Vienna, C=AT\\nSigner #1 certificate SHA-256 digest: b8e59d4a60b65290efb2716319e50b94e298d7a72c76c2119eb7d8d3afac302e\\nSigner #1 certificate SHA-1 digest: be575ec3b3b52e0b2392146cbdb245c91ef5a04f\\nSigner #1 certificate MD5 digest: 7aec063675b0206aba3b6175b89abc7d\\nSigner #1 key algorithm: RSA\\nSigner #1 key size (bits): 2048\\nSigner #1 public key SHA-256 digest: 6d9c0cda9dcd3ec5efcdca41243829b1dcf1e9a91c6309bca167807282590a20\\nSigner #1 public key SHA-1 digest: b34336038c7ca678285c14aebe78b7d5add90e4c\\nSigner #1 public key MD5 digest: a78bdb2b6d074db4b1ff12eb9cddcfa3\\nWARNING: ...\\n```\\n\\nDeterministic builds\\n====================\\n\\nTo validate the Mycelium image you obtain from Google Play Store, you can rebuild the Mycelium\\nwallet yourself using [Podman](https://podman.io/getting-started/) and compare both images following these steps:\\n\\n* Get the source as above\\n* Create your own builder image from our simple Dockerfile\\n\\n      $ podman build --no-cache --tag mycelium_builder .\\n\\n* Build using disorderfs to eliminate non-determinism caused by file ordering\\n\\n      $ podman run --rm --interactive --tty \\\\\\n          --device /dev/fuse \\\\\\n          --cap-add SYS_ADMIN \\\\\\n          --volume .:/app \\\\\\n          mycelium_builder \\\\\\n          bash -c \"apt update;\\n          apt install -y disorderfs;\\n          mkdir /project/\\n          disorderfs --sort-dirents=yes --reverse-dirents=no /app/ /project/;\\n          cd /project/\\n          ./gradlew -x lint -x test clean :mbw:assembleProdnetRelease;\"\\n\\n  If you see errors about local paths not being found, remove/move away `local.properties`.\\n\\n  As container might run as a different user, its generated files will also be \"not yours\".\\n  Make them yours using `chown` as super user.\\n  \\n  The app can now be found in `mbw/build/outputs/apk/prodnet/release/mbw-prodnet-release.apk`.\\n  \\n  As maintainer with release keys you want to run a slightly different command:\\n  Add these parameters: `--volume \\'path/to/keys.properties\\':/project/keys.properties --volume \\'path/to/keystore_mbwProd\\':/project/keystore_mbwProd --volume \\'path/to/keystore_mbwTest\\':/project/keystore_mbwTest`\\n  Build all these targets `:mbw:assBtctRel :mbw:assProdRel :mbw:assBtctDeb :mbw:assProdDeb`\\n  and to get an error on missing release keys, add this gradle option `-PenforceReleaseSigning`\\n  \\n  Note: for those who use Docker Toolbox $(pwd) should be under your home user folder since this is the [only folder that is shared with VM](https://github.com/docker/kitematic/issues/2738).\\n\\n* Retrieve Google Play Mycelium APK from your phone\\n  Gets package path:\\n\\n        $ adb shell pm path com.mycelium.wallet\\n        package:/data/app/com.mycelium.wallet-1/base.apk\\n\\n  Retrieve file:\\n\\n        $ adb pull /data/app/com.mycelium.wallet-1/base.apk mycelium-signed.apk\\n        \\n* Extract content from both apks you want to compare, using [ApkTool](https://ibotpeaches.github.io/Apktool/):\\n\\n        java -jar ~/path/to/apktool.jar d mbw-prodnet-release.apk\\n        java -jar ~/path/to/apktool.jar d mycelium-signed.apk\\n\\n* Compare signed apk with unsigned locally built apk using a diff tool\\n\\n        diff --brief --recursive  mbw-prodnet-release/ mycelium-signed/ | grep -v \"META-INF/CERT.RSA\\\\|META-INF/CERT.SF\\\\|META-INF/MANIFEST.MF\"\\n\\n* The expected difference between these files are elements that depend on the signature, that only\\n  the project\\'s maintainer can reproduce:\\n  \\n  * `original/META-INF/CERT.RSA` \\n  * `original/META-INF/CERT.SF` \\n  * `original/META-INF/MANIFEST.MF`\\n\\nFeatures\\n========\\n\\nWith the Mycelium Bitcoin Wallet you can send and receive Bitcoins using your mobile phone.\\n\\n - HD enabled - manage multiple accounts and never reuse addresses ([Bip32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki)/[Bip44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) compatible)\\n - Masterseed based - make one backup and be safe for ever. ([Bip39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki))\\n - 100% control over your private keys, they never leave your device unless you export them\\n - No block chain download - install and run in seconds\\n - Ultra fast connection to the Bitcoin network through our super nodes\\n - For enhanced privacy and availability you can connect to our super nodes via a tor-hidden service ( *.onion* address)\\n - Watch-only addresses (single or xPub) & private key (single or xPriv) import for secure cold-storage integration\\n - Directly spend from paper wallets (single key, xPriv or master seed)\\n - Trezor enabled - directly spend from trezor-secured accounts.\\n - [Mycelium Entropy](https://mycelium.com/entropy) compatible Shamir-Secret-Shared 2-out-of-3 keys spending\\n - Secure your wallet with a PIN\\n - Compatible with other bitcoin services through the `bitcoin:` URI scheme\\n\\n\\nPlease note that bitcoin is still experimental and this app comes with no warranty - while we make sure to adhere to the highest standards of software craftsmanship we can not exclude that the software contains bugs. Please make sure you have backups of your private keys and do not use this for more than you are willing to lose.\\n\\nThis application\\'s source is published at https://github.com/mycelium-com/wallet\\nWe need your feedback. If you have a suggestion or a bug to report [create an issue](https://github.com/mycelium-com/wallet/issues).\\n\\nMore features:\\n - Sources [available for review](https://github.com/mycelium-com/wallet-android)\\n - Multiple HD accounts, private keys, external xPub or xPriv accounts\\n - Multiple Bitcoin denominations: BTC, mBTC, bits and uBTC\\n - View your balance in multiple fiat currencies: USD, AUD, CAD, CHF, CNY, DKK, EUR, GBP, HKD, JPY, NZD, PLN, RUB, SEK, SGD, THB, and many more\\n - Send and receive by specifying an amount in fiat and switch between fiat and BTC while entering the amount\\n - Address book for commonly used addresses\\n - Transaction history with detailed information and local stored comments\\n - Import private keys using SIPA (the ones beginning with a 5) and mini private key format (Casascius private keys) from QR-codes or clipboard\\n - Export private-, xPub- or xPriv-keys as QR-codes, on clipboard or share with other applications\\n - Share your bitcoin address using Twitter, Facebook, email and more.\\n - Integrated QR-code scanner\\n - Client side load balancing between three 100% redundant server nodes located in different data centers.\\n - Sign Messages using your private keys (compatible with bitcoin-qt)\\n\\nAuthors\\n=======\\n - Jan Møller\\n - [Andreas Petersson](https://github.com/apetersson)\\n - [Daniel Weigl](https://github.com/DanielWeigl)\\n - [Jan Dreske](https://github.com/jandreske)\\n - Dmitry Murashchik\\n - Constantin Vennekel\\n - [Leo Wandersleb](https://github.com/Giszmo)\\n - [Daniel Krawisz](https://github.com/DanielKrawisz)\\n - [Jerome Rousselot](https://github.com/jeromerousselot)\\n - [Nelson Melina](https://github.com/DaLN)\\n - [Elvis Kurtnebiev](https://github.com/xElvis89x)\\n - [Sergey Dolgopolov](https://github.com/itserg)\\n - [Sergey Lappo](https://github.com/sergeylappo)\\n - Alexander Makarov\\n - [Nadia Poletova](https://github.com/poletova-n)\\n - [Kristina Tezieva](https://github.com/agneslovelace)\\n - [Nuru Nabiyev](https://github.com/NuruNabiyev)\\n \\n\\nCredits\\n=======\\nThanks to all collaborators who provided us with code or helped us with integrations!\\nJust to name a few:\\n\\n - [Nicolas Bacca from Ledger](https://github.com/btchip)\\n - Sipa, Marek and others from Trezor\\n - Jani and Aleš from Cashila\\n - [Kalle Rosenbaum, Bip120/121](https://github.com/kallerosenbaum)\\n - David and Alex from Glidera\\n - [Wiz](https://twitter.com/wiz) for helping us with KeepKey\\n - Tom Bitton and Asa Zaidman from Simplex\\n - (if you think you should be mentioned here, just notify us)\\n\\nThanks to Jethro for tirelessly testing the app during beta development.\\n\\nThanks to our numerous volunteer translators who provide high-quality translations in many languages. Your name should be listed here, please contact me so I know you want to be included.\\n\\nThanks to Johannes Zweng for his testing and providing pull requests for fixes.\\n\\nThanks to all beta testers to provide early feedback.\\n'},\n",
       " {'repo': 'dooglus/intersango',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': 'This is the exchange software used on intersango.com and britcoin.co.uk\\n\\nCopyright is held by Bitcoin Consultancy (bitcoinconsultancy.com)\\n\\nYou are free to use all artwork and code in this repository in accordance of the\\nterms of the AGPL.\\n\\n'},\n",
       " {'repo': 'butor/blackbird',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': '[![Build Status](https://travis-ci.org/butor/blackbird.svg?branch=master)](https://travis-ci.org/butor/blackbird)  [![Blackbird chat](https://badges.gitter.im/blackbird_bitcoin_arbitrage/Lobby.svg)](https://gitter.im/blackbird_bitcoin_arbitrage/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) ![license](https://img.shields.io/badge/license-MIT-blue.svg)\\n\\n<p align=\"center\">\\n<img src=\"https://cloud.githubusercontent.com/assets/11370278/10808535/02230d46-7dc3-11e5-92d8-da15cae8c6e9.png\" width=\"50%\" alt=\"Blackbird Bitcoin Arbitrage\">\\n</p>\\n\\n### Introduction\\n\\nBlackbird Bitcoin Arbitrage is a C++ trading system that does automatic long/short arbitrage between Bitcoin exchanges.\\n\\n### How It Works\\n\\nBitcoin is still a new and inefficient market. Several Bitcoin exchanges exist around the world and the bid/ask prices they propose can be briefly different from an exchange to another. The purpose of Blackbird is to automatically profit from these temporary price differences while being market-neutral.\\n\\nHere is a real example where an arbitrage opportunity exists between Bitstamp (long) and Bitfinex (short):\\n\\n<p align=\"center\">\\n<img src=\"https://cloud.githubusercontent.com/assets/11370278/11164055/5863e750-8ab3-11e5-86fc-8f7bab6818df.png\"  width=\"60%\" alt=\"Spread Example\">\\n</p>\\n\\nAt the first vertical line, the spread between the exchanges is high so Blackbird buys Bitstamp and short sells Bitfinex. Then, when the spread closes (second vertical line), Blackbird exits the market by selling Bitstamp and buying Bitfinex back.\\n\\n#### Advantages\\n\\nUnlike other Bitcoin arbitrage systems, Blackbird doesn\\'t sell but actually _short sells_ Bitcoin on the short exchange. This feature offers two important advantages:\\n\\n1. The strategy is always market-neutral: the Bitcoin market\\'s moves (up or down) don\\'t impact the strategy returns. This removes a huge risk from the strategy. The Bitcoin market could suddenly lose half its value that this won\\'t make any difference in the strategy returns.\\n\\n2. The strategy doesn\\'t need to transfer funds (USD or BTC) between Bitcoin exchanges. The buy/sell and sell/buy trading activities are done in parallel on two different exchanges, independently. Advantage: no need to deal with transfer latency issues.\\n\\nMore details about _short selling_ and _market neutrality_ can be found on <a href=\"https://github.com/butor/blackbird/issues/100\" target=\"_blank\">issue #100</a>.\\n\\n### Disclaimer\\n\\n__USE THE SOFTWARE AT YOUR OWN RISK. YOU ARE RESPONSIBLE FOR YOUR OWN MONEY. PAST PERFORMANCE IS NOT NECESSARILY INDICATIVE OF FUTURE RESULTS.__\\n\\n__THE AUTHORS AND ALL AFFILIATES ASSUME NO RESPONSIBILITY FOR YOUR TRADING RESULTS.__\\n\\n### Code Information\\n\\nThe trade results are stored in CSV files and the detailed activity is stored in log files. New files are created every time Blackbird is started.\\n\\nIt is possible to automatically stop Blackbird after the next trade has closed by creating, at any time, an empty file named _stop_after_notrade_.\\n\\nBlackbird uses functions written by <a href=\"http://www.adp-gmbh.ch/cpp/common/base64.html\" target=\"_blank\">René Nyffenegger</a> to encode and decode base64.\\n\\n### How To Test Blackbird\\n\\nPlease make sure that you understand the disclaimer above if you want to test Blackbird with real money, and start with a small amount of money.\\n\\n__IMPORTANT: all your BTC accounts must be empty before starting Blackbird. Make sure that you only have USD on your accounts and no BTC.__\\n\\nIt is never entirely safe to just tell Blackbird to use, say, $25 per exchange. You also need to only have $25 available on each of your trading accounts as well as 0 BTC. In this case, you are sure that even with a bug your maximum loss on an exchange won\\'t be greater than $25 no matter what.\\n\\nNote: on Bitfinex, your money has to be available on the _Margin_ account.\\n\\n#### Implemented Exchanges\\n\\n| Exchange | Long | Short | Tested | Note |\\n| -------- |:----:|:-----:|:------:| ---- |\\n| <a href=\"https://www.bitfinex.com\" target=\"_blank\">Bitfinex</a> | ✓ | ✓ | ✓ | |\\n| <a href=\"https://www.okcoin.com\" target=\"_blank\">OKCoin</a> | ✓ |  | ✓ |their API now offers short selling: <a href=\"https://www.okcoin.com/about/rest_api.do\" target=\"_blank\">link here</a> |\\n| <a href=\"https://www.bitstamp.net\" target=\"_blank\">Bitstamp</a> | ✓ |  | ✓ | |\\n| <a href=\"https://gemini.com\" target=\"_blank\">Gemini</a> | ✓ |  | ✓ | |\\n| <a href=\"https://www.kraken.com\" target=\"_blank\">Kraken</a> | ✓ | ✓ | | Validation in progress. Shorting is currently in testing | \\n| <a href=\"https://exmo.com\" target=\"_blank\">EXMO</a> | ✓ |  | | New exchange from PR <a href=\"https://github.com/butor/blackbird/pull/336\" target=\"_blank\">#336</a>. <b>Might be a <a href=\"https://bitcointalk.org/index.php?topic=1919799.0\" target=\"_blank\">scam</a></b> |\\n| <a href=\"https://www.quadrigacx.com\" target=\"_blank\">QuadrigaCX</a> | ✓ |  |  |\\n| <a href=\"https://www.gdax.com\" target=\"_blank\">GDAX</a> | ✓ |  |  | Validation in progress. Shorting is not currently supported. |\\n\\n\\n\\n\\n#### Potential Exchanges\\n\\n| Exchange | Long | Short | Note |\\n| -------- |:----:|:-----:| ---- |\\n| <a href=\"https://poloniex.com\" target=\"_blank\">Poloniex</a> | ✓ | ✓ | BTC/USD trading not supported, BTC/USDT margin trading not supported |\\n| <a href=\"https://cex.io/\" target=\"_blank\">CEX.IO</a> | ✓ | ✓ | Implementation in progress |\\n| <a href=\"https://wex.nz\" target=\"_blank\">WEX</a> | ✓ |  |  |\\n| <a href=\"https://www.itbit.com\" target=\"_blank\">itBit</a> | ✓ |  |  |\\n| <a href=\"https://bittrex.com\" target=\"_blank\">Bittrex</a> | ✓ |  | Implementation in progress, BTC/USD not supported (coming soon.) |\\n| <a href=\"https://binance.com\" target=\"_blank\">Binance</a> | ✓ |  | Implementation in progress, BTC/USD not supported |\\n\\nIf `DemoMode=true`, all the exchanges are shown in the log file.\\n\\nIf `DemoMode=false`, only the exchanges for which the credentials exist in _blackbird.conf_ are used.\\n\\n#### Credentials\\n\\nFor each of your exchange accounts, you need to create the API authentication keys. This is usually done in the _Settings_ section of your accounts.\\n\\nThen, you need to add your API keys into the file _blackbird.conf_. You need at least two exchanges and one of them should allow short selling. __Never__ share this file as it will contain your personal exchange credentials!\\n\\n#### Blackbird Parameters\\n\\nParameter | Default Value | Description\\n| ------------ | ------------------- | ------------- |\\n| DemoMode | true | The demo mode will show the spreads but won\\'t actually trade anything |\\n| Leg1 | BTC | The first leg of the traded pair. This leg is hedged against market risk |\\n| Leg2 | USD | The second leg of the traded pair. This leg is __not__ hedged against market risk |\\n| UseFullExposure | false | When true, all the `Leg2` exposure available on your accounts will be used. Otherwise, the amount defined by `TestedExposure` will be used. Note: the cash used for a trade will be the minimum of the two exchanges, minus 1.00% as a small margin: if there is $1,000 on the first account and $1,100 on the second one, $990 will be used for each exchange, i.e. $1,000 - (1% * $1,000). The exposure is $1,980 |\\n| TestedExposure | 25 | If UseFullExposure is false, that parameter defines the USD amount that will be used. The minimum has to be $10 otherwise some exchanges might reject the orders |\\n| MaxExposure | 25,000 | Maximum exposure per exchange. If the limit is $25,000 then Blackbird won\\'t send any order larger than that on each exchange |\\n| MaxLength | 5,184,000 | The maximum length of a trade in number of iterations. If this value is reached then Blackbird will exit the market regardless of the spread. Warning: with this value, the system can exit with a loss so It\\'s recommended to use a large value. The default is 180 days with GapSec at 3 seconds |\\n| DebugMaxIteration | 3,200,000 | The maximum number of iteration. Once DebugMaxIteration is reached Blackbird is terminated with return=0. Useful for troubleshooting the software |\\n| Verbose | true | Write the bid/ask and then spreads to the log file at every iteration. The log file size will be larger but it will show how Blackbird analyses the spreads |\\n| Interval | 3 sec. | Timelapse in seconds of an iteration. By default, the quotes download and the spreads analysis for all the exchanges are done every 3 seconds |\\n| SpreadEntry | 0.0080 | The spread threshold above which the trailing spreads are generated to capture an arbitrage opportunity |\\n| SpreadTarget | 0.0050 | This is the targeted profit. It represents the net profit and takes the exchange fees into account. If SpreadEntry is at 0.80% and trades are generated at that level on two exchanges with 0.25% fees each, Blackbird will set the exit threshold at -0.70% (0.80% spread entry - 4x0.25% fees - 0.50% target = -0.70%) |\\n| PriceDeltaLimit | 0.10 | The maximum difference between the target limit price and the computed limit price of an order. That is the price generated by looking at the current liquidity in the order books. If the difference is greater than PriceDeltaLimit then no trades will be generated because there is not enough liquidity (risk of slippage) |\\n| TrailingSpreadLim | 0.0008 | The limit under which the trailing spread is generated. If the current spread is above SpreadTarget and at 0.70%, then by default, the trailing spread will be generated at 0.62% |\\n| TrailingSpreadCount | 1 |  The number of times the spread must be between SpreadTarget and the trailing spread before sending the orders to the market |\\n| OrderBookFactor | 3.0 | In order to be executed as fast as possible and avoid slippage, Blackbird checks the liquidity in the order books of the exchanges and makes sure there are at least 3.0 times the needed liquidity before executing the order |\\n| UseVolatility | false |  If true, display the spreads volatility information in the log file. This is not used for the moment and only displayed as information |\\n| VolatilityPeriod | 600 | The period length of the volatility in number of iterations. This is not used for the moment and only displayed as information |\\n| SendEmail | false | When true, an e-mail will be sent every time an arbitrage trade is completed, with information such as the names of the exchanges and the trade return |\\n| DBFile | \\'blackbird.db\\' | SQLite3 database file to use for storing the bid/ask information of the exchanges for reference. Blackbird will create this file if it doesn\\'t already exist |\\n\\n#### Getting and building the software\\n\\nYou need the following libraries: <a href=\"https://www.openssl.org/source\" target=\"_blank\">OpenSSL</a>, <a href=\"http://www.digip.org/jansson\" target=\"_blank\">Jansson</a> (v2.7 minimum), <a href=\"http://curl.haxx.se\" target=\"_blank\">cURL</a>, <a href=\"http://www.sqlite.org\" target=\"_blank\">SQLite3</a> and <a href=\"http://caspian.dotconf.net/menu/Software/SendEmail\" target=\"_blank\">sendEmail</a>. Usually this is what you need to install:\\n\\n```\\nlibssl-dev\\nlibjansson-dev\\nlibcurl4-openssl-dev\\nlibsqlite3-dev (available as a Blackbird submodule)\\nbuild-essential\\ncmake\\nsendemail\\n```\\n\\nDownload the source from GitHub with:\\n\\n    mkdir blackbird\\n    cd blackbird\\n    git clone --recursive  git://github.com/butor/blackbird.git .\\n\\nAlternatively, if you already have the existing source tree use:\\n\\n    git submodule update --init\\n\\nto sync the submodules.\\n\\nOnce you have downloaded the source code, build Blackbird by typing:\\n\\n    cmake -B./build -H. -DCMAKE_BUILD_TYPE=Debug\\n\\nor\\n\\n    cmake -B./build -H. -DCMAKE_BUILD_TYPE=Release\\n    \\nthen\\n    \\n    cmake --build ./build -- install\\n\\nIf all goes well this produces a Blackbird executable in the project directory.\\n\\n#### Ubuntu (Amazon EC2 compatible)\\n\\n1. Run the following commands:\\n\\n  ```\\n  sudo apt-get install libssl-dev libjansson-dev libcurl4-openssl-dev libsqlite3-dev sendemail make gcc g++ build-essential cmake\\n  mkdir blackbird\\n  cd blackbird\\n  git clone --recursive  git://github.com/butor/blackbird.git .\\n  cmake -B./build -H. -DCMAKE_BUILD_TYPE=Release\\n  cmake --build ./build -- install\\n  ```\\n\\n2. Run the software, by typing:\\n\\n  ```\\n  ./blackbird\\n  ```\\n\\n#### Docker\\n\\n1. Download and install Docker (with Docker Compose) [here](https://www.docker.com/).\\n\\n2. Download the source from GitHub with\\n  ```\\n  mkdir blackbird\\n  cd blackbird\\n  git clone --recursive  git://github.com/butor/blackbird.git .\\n  ```\\nAlternatively, if you already have the existing source tree use:\\n  ```\\n  git submodule update --init\\n  ```\\n\\n3. Build the container:\\n\\n  ```\\n  docker build -t blackbird .\\n  ```\\n\\n4. Spin up the entire stack with docker-compose (OSX/Linux):\\n\\n  ```\\n  docker-compose up\\n  ```\\n\\n#### Mac OS X\\n\\n1. Install [Homebrew](https://brew.sh/)\\n\\n2. Run the following commands:\\n\\n  ```\\n  xcode-select --install\\n  brew install cmake openssl jansson curl sqlite3 sendemail\\n  mkdir blackbird\\n  cd blackbird\\n  git clone --recursive  git://github.com/butor/blackbird.git .\\n  cmake -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -B./build -H. -DCMAKE_BUILD_TYPE=Release\\n  cmake --build ./build -- install\\n  ```\\n\\n3. Run the software, by typing:\\n\\n  ```\\n  ./blackbird\\n  ```\\n\\n#### Understanding and debugging the software\\n\\nStep-through debugging is a helpful method to understand how any software application works.  Various scripts and metadata files are included alongside the source code to facilitate building the application so you can use GDB and VisualStudio Code to debug the application while it executes in a Docker container.\\n\\nOnce you have successfully launched Blackbird following the instructions in the \"Docker\" section, you need to do the following:\\n\\n1. <a href=\"https://code.visualstudio.com\" target=\"_blank\">Download and install Visual Studio Code</a>\\n\\n2. <a href=\"https://code.visualstudio.com/docs/languages/cpp\" target=\"_blank\">Setup the C/C++ extension for Visual Studio Code</a>\\n\\n3. You need to have GDB installed on your machine (this is described in the \"Debugging\" section of <a href=\"https://code.visualstudio.com/docs/languages/cpp\" target=\"_blank\">Setup the C/C++ extension for Visual Studio Code</a>).  \\n\\n4. From VS Code, File > Open Workspace... and select the \"blackbird\" workspace (this is in the root directory of your blackbird clone; the one you created this during \"Download source code\" step) \\n\\n5. Press F5 to start the debugger.  This will build and launch the Docker container, Blackbird w/ debug symbols, and a GDB Server running Blackbird on the Docker container.  Since there is a delay between when the Docker container gets launched and the GDB Server is running, you may need to start the debugger a few times before it attaches to the GDB server.  (If you can figure out how to create a \"pause\" between when the container launches and VS Code attempts to attach to GDB Server, that will fix it).\\n\\n### Contact\\n\\n* If you found a bug, please open a new <a href=\"https://github.com/butor/blackbird/issues\" target=\"_blank\">issue</a> with the label _bug_\\n* If you have a general question or have troubles running Blackbird, you can open a new  <a href=\"https://github.com/butor/blackbird/issues\" target=\"_blank\">issue</a> with the label _question_ or _help wanted_\\n* For anything else you can contact the author at julien.hamilton@gmail.com\\n\\n### Log Output Example\\n\\nThis is what the log file looks like when Blackbird is started:\\n\\n\\n```\\nBlackbird Bitcoin Arbitrage\\nDISCLAIMER: USE THE SOFTWARE AT YOUR OWN RISK.\\n\\n[ Targets ]\\n   Spread Entry:  0.80%\\n   Spread Target: 0.30%\\n\\n[ Current balances ]\\n   Bitfinex:    1,857.79 USD    0.000000 BTC\\n   OKCoin:      1,801.38 USD    0.000436 BTC\\n   Bitstamp:    1,694.15 USD    0.000000 BTC\\n   Gemini:      1,720.38 USD    0.000000 BTC\\n\\n[ Cash exposure ]\\n   FULL cash used!\\n\\n[ 10/31/2015 08:32:45 ]\\n   Bitfinex:    325.21 / 325.58\\n   OKCoin:      326.04 / 326.10\\n   Bitstamp:    325.37 / 325.82\\n   Gemini:      325.50 / 328.74\\n   ----------------------------\\n   OKCoin/Bitfinex:     -0.27% [target  0.80%, min -0.27%, max -0.27%]\\n   Bitstamp/Bitfinex:   -0.19% [target  0.80%, min -0.19%, max -0.19%]\\n   Gemini/Bitfinex:     -1.07% [target  0.80%, min -1.07%, max -1.07%]\\n\\n[ 10/31/2015 08:32:48 ]\\n   Bitfinex:    325.21 / 325.58\\n   OKCoin:      326.04 / 326.10\\n   Bitstamp:    325.39 / 325.68\\n   Gemini:      325.50 / 328.67\\n   ----------------------------\\n   OKCoin/Bitfinex:     -0.27% [target  0.80%, min -0.27%, max -0.27%]\\n   Bitstamp/Bitfinex:   -0.14% [target  0.80%, min -0.19%, max -0.14%]\\n   Gemini/Bitfinex:     -1.05% [target  0.80%, min -1.07%, max -1.05%]\\n```\\n'},\n",
       " {'repo': 'inoutcode/bitcoin_book_2nd',\n",
       "  'language': 'Python',\n",
       "  'readme_contents': '### [《精通比特币（第二版）-- 区块链编程》](https://bitcoinbook.info/) 中文版\\n### [Mastering Bitcoin 2nd Edition - Programming the Open Blockchain]( https://bitcoinbook.info/ ) in Chinese (Simplified)\\n\\n![Mastering Bitcoin 2nd Edition](images/cover.png)\\n\\n本书主要面向开发人员，前两章对比特币的介绍也适用于非开发人员。任何对技术有基本了解的人都可以阅读前两章，以深入了解比特币。\\n\\n### 目录\\n\\n[前言](前言.asciidoc)\\n\\n[术语](术语.asciidoc)\\n\\n[第一章 概述](第一章.asciidoc)\\n\\n[第二章 比特币如何运作](第二章.asciidoc)\\n\\n[第三章 Bitcoin Core参考实现](第三章.asciidoc)\\n\\n[第四章 密钥和地址](第四章.asciidoc)\\n\\n[第五章 钱包](第五章.asciidoc)\\n\\n[第六章 交易](第六章.asciidoc)\\n\\n[第七章 高级交易和脚本](第七章.asciidoc)\\n\\n[第八章 比特币网络](第八章.asciidoc)\\n\\n[第九章 区块链](第九章.asciidoc)\\n\\n[第十章 挖矿和共识](第十章.asciidoc)\\n\\n[第十一章 比特币安全](第十一章.asciidoc)\\n\\n[第十二章 区块链应用](第十二章.asciidoc)\\n\\n### 原书购买链接：\\n[Amazon](https://www.amazon.com/Mastering-Bitcoin-Programming-Open-Blockchain/dp/1491954388)\\n\\n### 关于译者\\n互联网从业者，对经济学感兴趣，很早加入数字货币和区块链研究。\\n\\n闲暇时间翻译，欢迎指正，感谢加星~\\n\\n[下一章：前言](前言.asciidoc)\\n### 打赏\\n![](images/thanks.jpeg)\\n'},\n",
       " {'repo': 'siminchen/bitcoinIDE',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': 'Bitcoin Script IDE\\n============================\\n\\nA Bitcoin Script IDE to facilitate the learning, testing, and teaching of Bitcoin Script.\\n\\nFeatures\\n--------\\n\\n* Syntax highlighting\\n* Auto-complete\\n* Translation to and from assembly\\n* Stack visualizer\\n* Step-by-step debugger\\n\\nTry it out!\\n--------------------\\n1. Open up IDE in https://siminchen.github.io/bitcoinIDE/\\n2. In the **Script pane**, type in some script code:\\n  * ex. 1  2  OP_ADD\\n  * ex. 123  OP_HASH256\\n  * ex. 1  OP_IF  2  OP_ELSE  3  OP_ENDIF\\n3. View the equivalent assembly code by clicking the **Assembly tab**\\n4. To execute the script, return to the Script tab and hit the **Run** button on the bottom to run the code\\n5. Note the stack operations in the **Stack pane** on the right.\\n6. To process the script one command at a time, hit the **Step** button on the bottom\\n7. Note the stack operations\\n8. Note the text box on the bottom that shows the next command\\n9. To process the remainder of the commands, hit the **Continue** button on the bottom\\n10. If the script was a valid script, then the text box on the bottom will be green and the stack elements will be orange.\\n11. If the script was invalid, then the text box and the stack elements will be red\\n\\n\\n\\n'},\n",
       " {'repo': 'znort987/blockparser',\n",
       "  'language': 'C',\n",
       "  'readme_contents': 'blockparser\\n===========\\n\\n    Who wrote it ?\\n    --------------\\n\\n        Author:\\n\\n            znort987@yahoo.com\\n\\n        Tip here if you find it useful:\\n\\n            1ZnortsoStC1zSTXbW6CUtkvqew8czMMG\\n\\n        I\\'ve also been cherry-picking changes I found useful from various github forks.\\n        Credits for these:\\n\\n             git log | grep Author | grep -iv Znort\\n\\n    Canonical source code repo:\\n    ---------------------------\\n\\n        git clone github.com:znort987/blockparser.git\\n\\n    License:\\n    --------\\n\\n        Code is in the public domain.\\n\\n    What is it ?\\n    ------------\\n\\n        A barebone C++ block parser that parses the entire block chain from scratch\\n        to extract various types of information from it.\\n\\n        The code chews \"linearly\" through the block chain and calls \"user-defined\"\\n        callbacks when it hits on certain \"events\" in the chain. Here:\\n\\n            \"events\" essentially means that the parser is starting to assemble a new\\n            blockchain data structure (a block, a tx, an input, etc ...), or that the\\n            parser has just completed a data structure, in which case it will usually\\n            run the callback with the completed data structure. The blockchain data\\n            structure level of granularity at which these \"events\" happen is somewhat\\n            arbitrary.  For example you won\\'t get called every time a new byte is seen.\\n\\n            \"user-defined\" means that if you want to extract new types of information\\n            from the chain, you have to add your own C++ piece of code to those already\\n            in directory \"cb\". Your C++ code will get called by the main parser at\\n            \"events\" of your choosing.\\n\\n            \"linearly\" is a bit of an abuse because the parser code often has to jump\\n            back to previously seen parts of the blockchain to provide user callbacks\\n            with fully complete data structures. The parser code also has to walk the\\n            blockchain a few times to compute the longest (valid) chain. But the user\\n            callbacks get a fairly linear view of it all.\\n\\n\\n        Blockparser was designed for bitcoin but works on most altcoins that were\\n        derived from the bitcoin code base.\\n\\n    What it is not:\\n    ---------------\\n\\n        Blockparser is *not* a verifier. It assumes a clean blockchain, as typically\\n        constructed and verified by the bitcoin core client. blockparser does not\\n        perform any kind of verification and will likely crash if applied to an unclean\\n        chain.\\n\\n        Blockparser is not very efficient if you want to perform repetitive tasks on\\n        thr block chain: the basic idea/premise of blockparser is that it\\'s going to\\n        chew through the *entire* block chain, *every* time. Given the size of the\\n        blockchain these days, that\\'s not something you want to do very 5 minutes.\\n\\n        Blockparser is not lean and mean. It used to be, when the blockchain was still\\n        relatively small.  Now that we are inching towards the 100\\'s of gigabytes, the\\n        very proposition that it has to chew through entire chain by design implies that\\n        it\\'s going to take quite a while, whichever way you slice it. Also, the entire\\n        index is built on the fly and kept in RAM. At current sizes, this is not a very\\n        smart choice. This might get addressed in the near future.\\n\\n    Why write this ?\\n    ----------------\\n\\n        It started as an exercise for me to get a \"close to the metal\" understanding of\\n        how bitcoin works. The quality and state of the original bitcoin codebase made\\n        this damn near impossible (it\\'s clear to me satosh, albeit clearly a genius, was\\n        not a professional software engineer. Also, things have vastly improved since then).\\n        It then grew into a fun hobby project.\\n\\n        The parser code is minimal and very easy to follow. If someone wants to quickly\\n        understand \"for real\" how the block chain is structured, it is a good place to\\n        start\\n\\n        It has also slowly grown into an altcoin zoo. It is very far from being a\\n        compendium (there\\'s so many of the darn things these days), but adding your\\n        fave alt is very easy.\\n\\n        Talking about zoo, I\\'ve also started to track and document \"weird\" TXO\\'s\\n        in the chain (comments, p2sh, multi-sigs, bugs, etc ...). Not a complete\\n        compendium yet, but getting there.\\n\\n        A side goal was also to build something that can independently (as in : the\\n        codebase is *very* different from that of bitcoin core) verify some of the\\n        conclusions of other bitcoin implementations, such as how many coins are\\n        attached to an address.\\n\\n        Another thing that blockparser is really nice for is to easily reconstruct\\n        \"snapshots\" of the state of the blockchain from a specific time (e.g. the -a\\n        option of the \"allBalances\" command).\\n\\n    How do I build it ?\\n    -------------------\\n\\n        You\\'ll need a 64-bit Unix box (because of RAM consumption, blockparser won\\'t work\\n        inside a 32bit address space).\\n\\n        If you are unfortunate enough to still have to use windows, there is a port floating\\n        somehwere on github.\\n\\n        I also have heard rumors of it working on OSX.\\n\\n        You\\'ll need a block chain somewhere on your hard drive. This is typically created\\n        by a statoshi bitcoin client such as this one: https://github.com/bitcoin/bitcoin.git\\n\\n        Install dependencies:\\n\\n            sudo apt-get install libssl-dev build-essential g++ libboost-all-dev libsparsehash-dev git-core perl\\n\\n        Get the source:\\n\\n            git clone git://github.com/znort987/blockparser.git\\n\\n        Build it:\\n\\n            cd blockparser\\n            make\\n\\n    It crashes\\n    ----------\\n\\n        At this point, blockparser uses a *lot* of memory (20+ Gig is typical). This\\n        can cause all sorts of woes on an under-dimensioned box, chief amongst which:\\n\\n            - box goes into heavy swapping, and parser takes for ever to complete task\\n\\n            - parser eats up all RAM and all SWAP and crashes. Here\\'s a possible remedy:\\n\\n                 http://askubuntu.com/questions/178712/how-to-increase-swap-space\\n\\n    How does blockparser deal with multi-sig transactions ?\\n    --------------------------------------------------------\\n\\n        AFAIK, there are two types of multi-sig transactions:\\n\\n            1) Pay-to-script (which is in fact more general than multisig). This one is\\n               easy, because it pays to a hash, which can readily be converted to an\\n               address that starts with the character \\'3\\' instead of \\'1\\'\\n\\n            2) Naked multi-sig transactions. These are harder, because the output of\\n               the transactions does not neatly map to a specific bitcoin address. I\\n               think I have found a neat work-around: I compute:\\n\\n                     hash160(M, N, sortedListOfAddresses)\\n\\n               which can now be properly mapped to a bitcoin address. To mark the fact\\n               that this addres is neither a \"pay to script\" (type \\'3\\') nor a\\n               \"pay to pubkey or pubkeyhash\" (type \\'1\\'), I prefix them with \\'4\\'\\n\\n               Note : this may be worthy of an actual BIP. If someone writes one,\\n               I\\'ll happily adjust the code.\\n\\n               Note : this trick is only a blockparser thing. This means that these\\n               new address types starting with a \\'4\\' won\\'t be recognized by other\\n               bitcoin implementations (such as blockchain.info)\\n\\n    Examples\\n    --------\\n\\n        . Show all supported commands\\n\\n            ./parser help\\n\\n        . Show help for a specific command\\n\\n            ./parser allBalances --help\\n\\n        . Compute simple blockchain stats\\n\\n            ./parser simple\\n\\n        . Extract all transactions for a very popular address 1dice6wBxymYi3t94heUAG6MpG5eceLG1\\n\\n            ./parser transactions 06f1b66fa14429389cbffa656966993eab656f37\\n\\n        . Compute the closure of an address, that is the list of addresses that very probably belong to the same person:\\n\\n            ./parser closure 06f1b66fa14429389cbffa656966993eab656f37\\n\\n        . Compute and print the balance for all keys ever used since the beginning of time:\\n\\n            ./parser all >all.txt\\n\\n        . See how much of the BTC 10K pizza tainted all the subsequent TX in the chain\\n          (chances are you have some dust coming from that famous TX lingering on one\\n          of your addresses)\\n\\n            ./parser taint >pizzaTaint.txt\\n\\n        . See all the block rewards and fees:\\n\\n            ./parser rewards >rewards.txt\\n\\n        . See a greatly detailed dump of the famous pizza transaction\\n\\n            ./parser show\\n\\n        . Track all mined blocks with unspent reward:\\n\\n            ./parser pristine\\n\\n        . Show the first valid \"pay to script hash (P2SH)\" transaction in the chain:\\n\\n            ./parser showtx 9c08a4d78931342b37fd5f72900fb9983087e6f46c4a097d8a1f52c74e28eaf6\\n\\n        . Show the first valid naked multi-sig transaction in the chain (it\\'s a 1 Of 2 multi-sig)\\n\\n            ./parser showtx 60a20bd93aa49ab4b28d514ec10b06e1829ce6818ec06cd3aabd013ebcdc4bb1\\n\\n    NOTE: the general syntax is:\\n\\n        ./parser <command> <option> <option> ... <arg> <arg> ...\\n\\n\\n    NOTE: use \"parser help <command>\" or \"parser <command> --help\" to get detailed\\n          help for a specific command.\\n\\n    NOTE: <command> may have multiple aliases and can also be abbreviated. For\\n          example, \"parser tx\", \"parser tr\", and \"parser transactions\" are equivalent.\\n\\n    NOTE: whenever specifying a list of things (e.g. a list of addresses), you can\\n          instead enter \"file:list.txt\" and the list will be read from the file.\\n\\n    NOTE: whenever specifying a list file, you can use \"file:-\" and blockparser\\n          will read the list directly from stdin.\\n\\n\\n    Caveats:\\n    --------\\n\\n        . You will need an x86-84 ubuntu box and a recent version of GCC(>=4.4), a recent version of\\n          boost and openssl-dev. You may be able to compile on other platforms, but the code wasn\\'t\\n          really designed for those.\\n\\n        . As of this writing, it needs a log of RAM to work, typically upwards of 25Gigs. I will switch\\n          to an on-disk hash table at some point, but for now you\\'ll just need that if you ever hope to\\n          see it finish in a reasonable amount of time (or at all if your swap space is too small).\\n\\n        . The code could be cleaner and better architected. It was just a quick and dirty way for me\\n          to learn about bitcoin. There really isn\\'t much in the way of comments either :D\\n\\n        . OTOH, it is fairly simple, short. If you want to understand how the blockchain data structures\\n          work, the code in parser.cpp is a solid way to start.\\n\\n    Hacking the code:\\n    -----------------\\n\\n        . parser.cpp contains the generic parser that reads the blockchain, parses it and calls\\n          \"user-defined\" callbacks as it hits interesting bits of information. It typically calls\\n          out when it begins reading finishes assembling a data structure.\\n\\n        . util.cpp contains a grab-bag of useful bitcoin related routines. Interesting examples include:\\n\\n            showScript\\n            getBaseReward\\n            solveOutputScript\\n            decompressPublicKey\\n\\n        . blockparser comes with a bunch of interesting \"user callbacks\".\\n\\n            . cb/allBalances.cpp    :   code to all balance of all addresses.\\n            . cb/closure.cpp        :   code to compute the transitive closure of an address\\n            . cb/dumpTX.cpp         :   code to display a transaction in very great detail\\n            . cb/help.cpp           :   code to dump detailed help for all other commands\\n            . cb/pristine.cpp       :   code to show all \"pristine\" (i.e. unspent) blocks\\n            . cb/rewards.cpp        :   code to show all block rewards (including fees)\\n            . cb/simpleStats.cpp    :   code to compute simple stats.\\n            . cb/sql.cpp            :   code to product an SQL dump of the blockchain\\n            . cb/taint.cpp          :   code to compute the taint from a given TX to all TXs.\\n            . cb/transactions.cpp   :   code to extract all transactions pertaining to an address.\\n\\n\\n        . You can very easily add your own custom command. You can use the existing callbacks in\\n          directory ./cb/ as a template to build your own:\\n\\n                cp cb/allBalances.cpp cb/myExtractor.cpp\\n                Add to Makefile\\n                Hack away\\n                Recompile\\n                Run\\n\\n        . You can also read the file callback.h (the base class from which you derive to implement your\\n          own new commands). It has been heavily commented and should provide a good basis to pick what\\n          to overload to achieve your goal.\\n\\n        . The code makes heavy use of the google dense hash maps. You can switch it to use sparse hash\\n          maps (see Makefile, search for: DENSE, undef it). Sparse hash maps are slower but save quite a\\n          bit of RAM.\\n\\n'},\n",
       " {'repo': 'kingrock/BitcoinExchange',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': 'BitcoinExchangeScript\\n=====================\\n\\nA opensource exchange script for digital currencies like Bitcoin and other alt-coins. \\n\\nThe trading section is not fully completed at this time. \\n\\nFeel free to contribute\\n'},\n",
       " {'repo': 'ccxt/ccxt',\n",
       "  'language': 'JavaScript',\n",
       "  'readme_contents': '# CCXT – CryptoCurrency eXchange Trading Library\\n\\n[![Build Status](https://travis-ci.com/ccxt/ccxt.svg?branch=master)](https://travis-ci.com/ccxt/ccxt) [![npm](https://img.shields.io/npm/v/ccxt.svg)](https://npmjs.com/package/ccxt) [![PyPI](https://img.shields.io/pypi/v/ccxt.svg)](https://pypi.python.org/pypi/ccxt) [![NPM Downloads](https://img.shields.io/npm/dy/ccxt.svg)](https://www.npmjs.com/package/ccxt) [![Discord](https://img.shields.io/discord/690203284119617602?logo=discord&logoColor=white)](https://discord.gg/ccxt) [![Supported Exchanges](https://img.shields.io/badge/exchanges-111-blue.svg)](https://github.com/ccxt/ccxt/wiki/Exchange-Markets) [![Twitter Follow](https://img.shields.io/twitter/follow/ccxt_official.svg?style=social&label=CCXT)](https://twitter.com/ccxt_official)\\n\\nA JavaScript / Python / PHP library for cryptocurrency trading and e-commerce with support for many bitcoin/ether/altcoin exchange markets and merchant APIs.\\n\\n### [Install](#install) · [Usage](#usage) · [Manual](https://docs.ccxt.com/en/latest/manual.html) · [FAQ](https://github.com/ccxt/ccxt/wiki/FAQ) · [Examples](https://github.com/ccxt/ccxt/tree/master/examples) · [Contributing](https://github.com/ccxt/ccxt/blob/master/CONTRIBUTING.md) · [Social](#social) · [CCXT Pro](https://ccxt.pro)\\n\\nThe **CCXT** library is used to connect and trade with cryptocurrency exchanges and payment processing services worldwide. It provides quick access to market data for storage, analysis, visualization, indicator development, algorithmic trading, strategy backtesting, bot programming, and related software engineering.\\n\\nIt is intended to be used by **coders, developers, technically-skilled traders, data-scientists and financial analysts** for building trading algorithms.\\n\\nCurrent feature list:\\n\\n- support for many cryptocurrency exchanges — more coming soon\\n- fully implemented public and private APIs\\n- optional normalized data for cross-exchange analytics and arbitrage\\n- an out of the box unified API that is extremely easy to integrate\\n- works in Node 10.4+, Python 3, PHP 8.1+, and web browsers\\n\\n\\n## See Also\\n\\n- <sub>[![TabTrader](https://user-images.githubusercontent.com/1294454/66755907-9c3e8880-eea1-11e9-846e-0bff349ceb87.png)](https://tab-trader.com/?utm_source=ccxt)</sub> **[TabTrader](https://tab-trader.com/?utm_source=ccxt)** – trading on all exchanges in one app. Available on **[Android](https://play.google.com/store/apps/details?id=com.tabtrader.android&referrer=utm_source%3Dccxt)** and **[iOS](https://itunes.apple.com/app/apple-store/id1095716562?mt=8)**!\\n- <sub>[![Freqtrade](https://user-images.githubusercontent.com/1294454/114340585-8e35fa80-9b60-11eb-860f-4379125e2db6.png)](https://www.freqtrade.io)</sub> **[Freqtrade](https://www.freqtrade.io)** – leading opensource cryptocurrency algorithmic trading software!\\n- <sub>[![OctoBot](https://user-images.githubusercontent.com/1294454/132113722-007fc092-7530-4b41-b929-b8ed380b7b2e.png)](https://www.octobot.online)</sub> **[OctoBot](https://www.octobot.online)** – cryptocurrency trading bot with an advanced web interface.\\n- <sub>[![TokenBot](https://user-images.githubusercontent.com/1294454/152720975-0522b803-70f0-4f18-a305-3c99b37cd990.png)](https://tokenbot.com/?utm_source=github&utm_medium=ccxt&utm_campaign=algodevs)</sub> **[TokenBot](https://tokenbot.com/?utm_source=github&utm_medium=ccxt&utm_campaign=algodevs)** – discover and copy the best algorithmic traders in the world.\\n\\n\\n## Certified Cryptocurrency Exchanges\\n\\n\\n| logo                                                                                                                                                                                                            | id           | name                                                                                                    | ver                                                                                                               | certified                                                                                                                   | pro                                                                          | discount                                                                                                                                                                                                                                         |\\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------:|-----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|\\n| [![binance](https://user-images.githubusercontent.com/1294454/29604020-d5483cdc-87ee-11e7-94c7-d1a8d9169293.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                        | binance      | [Binance](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                        | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/spot/en)      | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with Binance using CCXT\\'s referral link for a 10% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d10%25&color=orange)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                        |\\n| [![binancecoinm](https://user-images.githubusercontent.com/1294454/117738721-668c8d80-b205-11eb-8c49-3fad84c4a07f.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                  | binancecoinm | [Binance COIN-M](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/delivery/en/) | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with Binance COIN-M using CCXT\\'s referral link for a 10% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d10%25&color=orange)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 |\\n| [![binanceusdm](https://user-images.githubusercontent.com/1294454/117738721-668c8d80-b205-11eb-8c49-3fad84c4a07f.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                   | binanceusdm  | [Binance USDⓈ-M](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/futures/en/)  | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with Binance USDⓈ-M using CCXT\\'s referral link for a 10% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d10%25&color=orange)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 |\\n| [![bitget](https://user-images.githubusercontent.com/1294454/195989417-4253ddb0-afbe-4a1c-9dea-9dbcd121fa5d.jpg)](https://www.bitget.com/expressly?languageType=0&channelCode=ccxt&vipCode=tg9j)                | bitget       | [Bitget](https://www.bitget.com/expressly?languageType=0&channelCode=ccxt&vipCode=tg9j)                 | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://bitgetlimited.github.io/apidoc/en/mix)       | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![bitmart](https://user-images.githubusercontent.com/1294454/129991357-8f47464b-d0f4-41d6-8a82-34122f0d1398.jpg)](http://www.bitmart.com/?r=rQCFLh)                                                            | bitmart      | [BitMart](http://www.bitmart.com/?r=rQCFLh)                                                             | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://developer-pro.bitmart.com/)                  | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with BitMart using CCXT\\'s referral link for a 30% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d30%25&color=orange)](http://www.bitmart.com/?r=rQCFLh)                                                             |\\n| [![bitvavo](https://user-images.githubusercontent.com/1294454/169202626-bd130fc5-fcf9-41bb-8d97-6093225c73cd.jpg)](https://bitvavo.com/?a=24F34952F7)                                                           | bitvavo      | [Bitvavo](https://bitvavo.com/?a=24F34952F7)                                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.bitvavo.com/)                           | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![bybit](https://user-images.githubusercontent.com/51840849/76547799-daff5b80-649e-11ea-87fb-3be9bac08954.jpg)](https://www.bybit.com/register?affiliate_id=35953)                                             | bybit        | [Bybit](https://www.bybit.com/register?affiliate_id=35953)                                              | [![API Version 5](https://img.shields.io/badge/5-lightgray)](https://bybit-exchange.github.io/docs/inverse/)      | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![gate](https://user-images.githubusercontent.com/1294454/31784029-0313c702-b509-11e7-9ccc-bc0da6a0e435.jpg)](https://www.gate.io/ref/2436035)                                                                 | gate         | [Gate.io](https://www.gate.io/ref/2436035)                                                              | [![API Version 4](https://img.shields.io/badge/4-lightgray)](https://www.gate.io/docs/apiv4/en/index.html)        | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with Gate.io using CCXT\\'s referral link for a 20% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d20%25&color=orange)](https://www.gate.io/ref/2436035)                                                              |\\n| [![huobi](https://user-images.githubusercontent.com/1294454/76137448-22748a80-604e-11ea-8069-6e389271911d.jpg)](https://www.huobi.com/en-us/v/register/double-invite/?inviter_id=11343840&invite_code=6rmm2223) | huobi        | [Huobi](https://www.huobi.com/en-us/v/register/double-invite/?inviter_id=11343840&invite_code=6rmm2223) | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://huobiapi.github.io/docs/spot/v1/en/)         | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) | [![Sign up with Huobi using CCXT\\'s referral link for a 15% discount!](https://img.shields.io/static/v1?label=Fee&message=%2d15%25&color=orange)](https://www.huobi.com/en-us/v/register/double-invite/?inviter_id=11343840&invite_code=6rmm2223) |\\n| [![idex](https://user-images.githubusercontent.com/51840849/94481303-2f222100-01e0-11eb-97dd-bc14c5943a86.jpg)](https://idex.io)                                                                                | idex         | [IDEX](https://idex.io)                                                                                 | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://docs.idex.io/)                               | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![kucoin](https://user-images.githubusercontent.com/51840849/87295558-132aaf80-c50e-11ea-9801-a2fb0c57c799.jpg)](https://www.kucoin.com/ucenter/signup?rcode=E5wkqe)                                           | kucoin       | [KuCoin](https://www.kucoin.com/ucenter/signup?rcode=E5wkqe)                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.kucoin.com)                             | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![mexc](https://user-images.githubusercontent.com/1294454/137283979-8b2a818d-8633-461b-bfca-de89e8c446b2.jpg)](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                                | mexc         | [MEXC Global](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                          | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://mxcdevelop.github.io/APIDoc/)                | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n| [![okx](https://user-images.githubusercontent.com/1294454/152485636-38b19e4a-bece-4dec-979a-5982859ffc04.jpg)](https://www.okx.com/join/1888677)                                                                | okx          | [OKX](https://www.okx.com/join/1888677)                                                                 | [![API Version 5](https://img.shields.io/badge/5-lightgray)](https://www.okx.com/docs-v5/en/)                     | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |                                                                                                                                                                                                                                                  |\\n\\n## Supported Cryptocurrency Exchange Markets\\n\\nThe CCXT library currently supports the following 105 cryptocurrency exchange markets and trading APIs:\\n\\n| logo                                                                                                                                                                                                            | id                 | name                                                                                                    | ver                                                                                                                                                | certified                                                                                                                   | pro                                                                          |\\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------:|-----------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|\\n| [![ace](https://user-images.githubusercontent.com/1294454/216908003-fb314cf6-e66e-471c-b91d-1d86e4baaa90.jpg)](https://ace.io/)                                                                                 | ace                | [ACE](https://ace.io/)                                                                                  | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://github.com/ace-exchange/ace-offical-api-docs)                                 |                                                                                                                             |                                                                              |\\n| [![alpaca](https://user-images.githubusercontent.com/1294454/187234005-b864db3d-f1e3-447a-aaf9-a9fc7b955d07.jpg)](https://alpaca.markets)                                                                       | alpaca             | [Alpaca](https://alpaca.markets)                                                                        | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://alpaca.markets/docs/)                                                         |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![ascendex](https://user-images.githubusercontent.com/1294454/112027508-47984600-8b48-11eb-9e17-d26459cc36c6.jpg)](https://ascendex.com/en-us/register?inviteCode=EL6BXBQM)                                    | ascendex           | [AscendEX](https://ascendex.com/en-us/register?inviteCode=EL6BXBQM)                                     | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://ascendex.github.io/ascendex-pro-api/#ascendex-pro-api-documentation)          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bequant](https://user-images.githubusercontent.com/1294454/55248342-a75dfe00-525a-11e9-8aa2-05e9dca943c6.jpg)](https://bequant.io)                                                                           | bequant            | [Bequant](https://bequant.io)                                                                           | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://api.bequant.io/)                                                              |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bigone](https://user-images.githubusercontent.com/1294454/69354403-1d532180-0c91-11ea-88ed-44c06cefdf87.jpg)](https://b1.run/users/new?code=D3LLBVFT)                                                        | bigone             | [BigONE](https://b1.run/users/new?code=D3LLBVFT)                                                        | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://open.big.one/docs/api.html)                                                   |                                                                                                                             |                                                                              |\\n| [![binance](https://user-images.githubusercontent.com/1294454/29604020-d5483cdc-87ee-11e7-94c7-d1a8d9169293.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                        | binance            | [Binance](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                        | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/spot/en)                                       | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![binancecoinm](https://user-images.githubusercontent.com/1294454/117738721-668c8d80-b205-11eb-8c49-3fad84c4a07f.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                  | binancecoinm       | [Binance COIN-M](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/delivery/en/)                                  | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![binanceus](https://user-images.githubusercontent.com/1294454/65177307-217b7c80-da5f-11e9-876e-0b748ba0a358.jpg)](https://www.binance.us/?ref=35005074)                                                       | binanceus          | [Binance US](https://www.binance.us/?ref=35005074)                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://github.com/binance-us/binance-official-api-docs)                              |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![binanceusdm](https://user-images.githubusercontent.com/1294454/117738721-668c8d80-b205-11eb-8c49-3fad84c4a07f.jpg)](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                   | binanceusdm        | [Binance USDⓈ-M](https://accounts.binance.com/en/register?ref=D7YA7CLY)                                 | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://binance-docs.github.io/apidocs/futures/en/)                                   | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bit2c](https://user-images.githubusercontent.com/1294454/27766119-3593220e-5ece-11e7-8b3a-5a041f6bcc3f.jpg)](https://bit2c.co.il/Aff/63bfed10-e359-420c-ab5a-ad368dab0baf)                                   | bit2c              | [Bit2C](https://bit2c.co.il/Aff/63bfed10-e359-420c-ab5a-ad368dab0baf)                                   | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://www.bit2c.co.il/home/api)                                                     |                                                                                                                             |                                                                              |\\n| [![bitbank](https://user-images.githubusercontent.com/1294454/37808081-b87f2d9c-2e59-11e8-894d-c1900b7584fe.jpg)](https://bitbank.cc/)                                                                          | bitbank            | [bitbank](https://bitbank.cc/)                                                                          | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.bitbank.cc/)                                                             |                                                                                                                             |                                                                              |\\n| [![bitbns](https://user-images.githubusercontent.com/1294454/117201933-e7a6e780-adf5-11eb-9d80-98fc2a21c3d6.jpg)](https://ref.bitbns.com/1090961)                                                               | bitbns             | [Bitbns](https://ref.bitbns.com/1090961)                                                                | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://bitbns.com/trade/#/api-trading/)                                              |                                                                                                                             |                                                                              |\\n| [![bitfinex](https://user-images.githubusercontent.com/1294454/27766244-e328a50c-5ed2-11e7-947b-041416579bb3.jpg)](https://www.bitfinex.com/?refcode=P61eYxFL)                                                  | bitfinex           | [Bitfinex](https://www.bitfinex.com/?refcode=P61eYxFL)                                                  | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.bitfinex.com/v1/docs)                                                    |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitfinex2](https://user-images.githubusercontent.com/1294454/27766244-e328a50c-5ed2-11e7-947b-041416579bb3.jpg)](https://www.bitfinex.com)                                                                   | bitfinex2          | [Bitfinex](https://www.bitfinex.com)                                                                    | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.bitfinex.com/v2/docs/)                                                   |                                                                                                                             |                                                                              |\\n| [![bitflyer](https://user-images.githubusercontent.com/1294454/28051642-56154182-660e-11e7-9b0d-6042d1e6edd8.jpg)](https://bitflyer.com)                                                                        | bitflyer           | [bitFlyer](https://bitflyer.com)                                                                        | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://lightning.bitflyer.com/docs?lang=en)                                          |                                                                                                                             |                                                                              |\\n| [![bitforex](https://user-images.githubusercontent.com/51840849/87295553-1160ec00-c50e-11ea-8ea0-df79276a9646.jpg)](https://www.bitforex.com/en/invitationRegister?inviterId=1867438)                           | bitforex           | [Bitforex](https://www.bitforex.com/en/invitationRegister?inviterId=1867438)                            | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/githubdev2020/API_Doc_en/wiki)                                     |                                                                                                                             |                                                                              |\\n| [![bitget](https://user-images.githubusercontent.com/1294454/195989417-4253ddb0-afbe-4a1c-9dea-9dbcd121fa5d.jpg)](https://www.bitget.com/expressly?languageType=0&channelCode=ccxt&vipCode=tg9j)                | bitget             | [Bitget](https://www.bitget.com/expressly?languageType=0&channelCode=ccxt&vipCode=tg9j)                 | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://bitgetlimited.github.io/apidoc/en/mix)                                        | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bithumb](https://user-images.githubusercontent.com/1294454/30597177-ea800172-9d5e-11e7-804c-b9d4fa9b56b0.jpg)](https://www.bithumb.com)                                                                      | bithumb            | [Bithumb](https://www.bithumb.com)                                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://apidocs.bithumb.com)                                                          |                                                                                                                             |                                                                              |\\n| [![bitmart](https://user-images.githubusercontent.com/1294454/129991357-8f47464b-d0f4-41d6-8a82-34122f0d1398.jpg)](http://www.bitmart.com/?r=rQCFLh)                                                            | bitmart            | [BitMart](http://www.bitmart.com/?r=rQCFLh)                                                             | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://developer-pro.bitmart.com/)                                                   | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitmex](https://user-images.githubusercontent.com/1294454/27766319-f653c6e6-5ed4-11e7-933d-f0bc3699ae8f.jpg)](https://www.bitmex.com/register/upZpOX)                                                        | bitmex             | [BitMEX](https://www.bitmex.com/register/upZpOX)                                                        | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://www.bitmex.com/app/apiOverview)                                               |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitopro](https://user-images.githubusercontent.com/1294454/158227251-3a92a220-9222-453c-9277-977c6677fe71.jpg)](https://www.bitopro.com)                                                                     | bitopro            | [BitoPro](https://www.bitopro.com)                                                                      | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://github.com/bitoex/bitopro-offical-api-docs/blob/master/v3-1/rest-1/rest.md)   |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitpanda](https://user-images.githubusercontent.com/51840849/87591171-9a377d80-c6f0-11ea-94ac-97a126eac3bc.jpg)](https://www.bitpanda.com/en/pro)                                                            | bitpanda           | [Bitpanda Pro](https://www.bitpanda.com/en/pro)                                                         | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://developers.bitpanda.com/exchange/)                                            |                                                                                                                             |                                                                              |\\n| [![bitrue](https://user-images.githubusercontent.com/1294454/139516488-243a830d-05dd-446b-91c6-c1f18fe30c63.jpg)](https://www.bitrue.com/activity/task/task-landing?inviteCode=EZWETQE&cn=900000)               | bitrue             | [Bitrue](https://www.bitrue.com/activity/task/task-landing?inviteCode=EZWETQE&cn=900000)                | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/Bitrue-exchange/bitrue-official-api-docs)                          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitso](https://user-images.githubusercontent.com/51840849/87295554-11f98280-c50e-11ea-80d6-15b3bafa8cbf.jpg)](https://bitso.com/?ref=itej)                                                                   | bitso              | [Bitso](https://bitso.com/?ref=itej)                                                                    | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://bitso.com/api_info)                                                           |                                                                                                                             |                                                                              |\\n| [![bitstamp](https://user-images.githubusercontent.com/1294454/27786377-8c8ab57e-5fe9-11e7-8ea4-2b05b6bcceec.jpg)](https://www.bitstamp.net)                                                                    | bitstamp           | [Bitstamp](https://www.bitstamp.net)                                                                    | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://www.bitstamp.net/api)                                                         |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitstamp1](https://user-images.githubusercontent.com/1294454/27786377-8c8ab57e-5fe9-11e7-8ea4-2b05b6bcceec.jpg)](https://www.bitstamp.net)                                                                   | bitstamp1          | [Bitstamp](https://www.bitstamp.net)                                                                    | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://www.bitstamp.net/api)                                                         |                                                                                                                             |                                                                              |\\n| [![bittrex](https://user-images.githubusercontent.com/51840849/87153921-edf53180-c2c0-11ea-96b9-f2a9a95a455b.jpg)](https://bittrex.com/Account/Register?referralCode=1ZE-G0G-M3B)                               | bittrex            | [Bittrex](https://bittrex.com/Account/Register?referralCode=1ZE-G0G-M3B)                                | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://bittrex.github.io/api/v3)                                                     |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bitvavo](https://user-images.githubusercontent.com/1294454/169202626-bd130fc5-fcf9-41bb-8d97-6093225c73cd.jpg)](https://bitvavo.com/?a=24F34952F7)                                                           | bitvavo            | [Bitvavo](https://bitvavo.com/?a=24F34952F7)                                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.bitvavo.com/)                                                            | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![bkex](https://user-images.githubusercontent.com/1294454/158043180-bb079a65-69e8-45a2-b393-f094d334e610.jpg)](https://www.bkex.com/)                                                                          | bkex               | [BKEX](https://www.bkex.com/)                                                                           | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://bkexapi.github.io/docs/api_en.htm)                                            |                                                                                                                             |                                                                              |\\n| [![bl3p](https://user-images.githubusercontent.com/1294454/28501752-60c21b82-6feb-11e7-818b-055ee6d0e754.jpg)](https://bl3p.eu)                                                                                 | bl3p               | [BL3P](https://bl3p.eu)                                                                                 | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/BitonicNL/bl3p-api/tree/master/docs)                               |                                                                                                                             |                                                                              |\\n| [![blockchaincom](https://user-images.githubusercontent.com/1294454/147515585-1296e91b-7398-45e5-9d32-f6121538533f.jpeg)](https://blockchain.com)                                                               | blockchaincom      | [Blockchain.com](https://blockchain.com)                                                                | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://api.blockchain.com/v3)                                                        |                                                                                                                             |                                                                              |\\n| [![btcalpha](https://user-images.githubusercontent.com/1294454/42625213-dabaa5da-85cf-11e8-8f99-aa8f8f7699f0.jpg)](https://btc-alpha.com/?r=123788)                                                             | btcalpha           | [BTC-Alpha](https://btc-alpha.com/?r=123788)                                                            | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://btc-alpha.github.io/api-docs)                                                 |                                                                                                                             |                                                                              |\\n| [![btcbox](https://user-images.githubusercontent.com/51840849/87327317-98c55400-c53c-11ea-9a11-81f7d951cc74.jpg)](https://www.btcbox.co.jp/)                                                                    | btcbox             | [BtcBox](https://www.btcbox.co.jp/)                                                                     | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://blog.btcbox.jp/en/archives/8762)                                              |                                                                                                                             |                                                                              |\\n| [![btcex](https://user-images.githubusercontent.com/1294454/173489620-d49807a4-55cd-4f4e-aca9-534921298bbf.jpg)](https://www.btcex.com/en-us/register?i=48biatg1)                                               | btcex              | [BTCEX](https://www.btcex.com/en-us/register?i=48biatg1)                                                | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.btcex.com/)                                                              |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![btcmarkets](https://user-images.githubusercontent.com/51840849/89731817-b3fb8480-da52-11ea-817f-783b08aaf32b.jpg)](https://btcmarkets.net)                                                                   | btcmarkets         | [BTC Markets](https://btcmarkets.net)                                                                   | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://api.btcmarkets.net/doc/v3)                                                    |                                                                                                                             |                                                                              |\\n| [![btctradeua](https://user-images.githubusercontent.com/1294454/27941483-79fc7350-62d9-11e7-9f61-ac47f28fcd96.jpg)](https://btc-trade.com.ua/registration/22689)                                               | btctradeua         | [BTC Trade UA](https://btc-trade.com.ua/registration/22689)                                             | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.google.com/document/d/1ocYA0yMy_RXd561sfG3qEPZ80kyll36HUxvCRe5GbhE/edit) |                                                                                                                             |                                                                              |\\n| [![btcturk](https://user-images.githubusercontent.com/51840849/87153926-efbef500-c2c0-11ea-9842-05b63612c4b9.jpg)](https://www.btcturk.com)                                                                     | btcturk            | [BTCTurk](https://www.btcturk.com)                                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://github.com/BTCTrader/broker-api-docs)                                         |                                                                                                                             |                                                                              |\\n| [![buda](https://user-images.githubusercontent.com/1294454/47380619-8a029200-d706-11e8-91e0-8a391fe48de3.jpg)](https://www.buda.com)                                                                            | buda               | [Buda](https://www.buda.com)                                                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://api.buda.com)                                                                 |                                                                                                                             |                                                                              |\\n| [![bybit](https://user-images.githubusercontent.com/51840849/76547799-daff5b80-649e-11ea-87fb-3be9bac08954.jpg)](https://www.bybit.com/register?affiliate_id=35953)                                             | bybit              | [Bybit](https://www.bybit.com/register?affiliate_id=35953)                                              | [![API Version 5](https://img.shields.io/badge/5-lightgray)](https://bybit-exchange.github.io/docs/inverse/)                                       | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![cex](https://user-images.githubusercontent.com/1294454/27766442-8ddc33b0-5ed8-11e7-8b98-f786aef0f3c9.jpg)](https://cex.io/r/0/up105393824/0/)                                                                | cex                | [CEX.IO](https://cex.io/r/0/up105393824/0/)                                                             | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://cex.io/cex-api)                                                               |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![coinbase](https://user-images.githubusercontent.com/1294454/40811661-b6eceae2-653a-11e8-829e-10bfadb078cf.jpg)](https://www.coinbase.com/join/58cbe25a355148797479dbd2)                                      | coinbase           | [Coinbase](https://www.coinbase.com/join/58cbe25a355148797479dbd2)                                      | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://developers.coinbase.com/api/v2)                                               |                                                                                                                             |                                                                              |\\n| [![coinbaseprime](https://user-images.githubusercontent.com/1294454/44539184-29f26e00-a70c-11e8-868f-e907fc236a7c.jpg)](https://exchange.coinbase.com)                                                          | coinbaseprime      | [Coinbase Prime](https://exchange.coinbase.com)                                                         | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.exchange.coinbase.com)                                                   |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![coinbasepro](https://user-images.githubusercontent.com/1294454/41764625-63b7ffde-760a-11e8-996d-a6328fa9347a.jpg)](https://pro.coinbase.com/)                                                                | coinbasepro        | [Coinbase Pro](https://pro.coinbase.com/)                                                               | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.pro.coinbase.com)                                                        |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![coincheck](https://user-images.githubusercontent.com/51840849/87182088-1d6d6380-c2ec-11ea-9c64-8ab9f9b289f5.jpg)](https://coincheck.com)                                                                     | coincheck          | [coincheck](https://coincheck.com)                                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://coincheck.com/documents/exchange/api)                                         |                                                                                                                             |                                                                              |\\n| [![coinex](https://user-images.githubusercontent.com/51840849/87182089-1e05fa00-c2ec-11ea-8da9-cc73b45abbbc.jpg)](https://www.coinex.com/register?refer_code=yw5fz)                                             | coinex             | [CoinEx](https://www.coinex.com/register?refer_code=yw5fz)                                              | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/coinexcom/coinex_exchange_api/wiki)                                |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![coinfalcon](https://user-images.githubusercontent.com/1294454/41822275-ed982188-77f5-11e8-92bb-496bcd14ca52.jpg)](https://coinfalcon.com/?ref=CFJSVGTUPASB)                                                  | coinfalcon         | [CoinFalcon](https://coinfalcon.com/?ref=CFJSVGTUPASB)                                                  | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.coinfalcon.com)                                                          |                                                                                                                             |                                                                              |\\n| [![coinmate](https://user-images.githubusercontent.com/51840849/87460806-1c9f3f00-c616-11ea-8c46-a77018a8f3f4.jpg)](https://coinmate.io?referral=YTFkM1RsOWFObVpmY1ZjMGREQmpTRnBsWjJJNVp3PT0)                   | coinmate           | [CoinMate](https://coinmate.io?referral=YTFkM1RsOWFObVpmY1ZjMGREQmpTRnBsWjJJNVp3PT0)                    | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://coinmate.docs.apiary.io)                                                      |                                                                                                                             |                                                                              |\\n| [![coinone](https://user-images.githubusercontent.com/1294454/38003300-adc12fba-323f-11e8-8525-725f53c4a659.jpg)](https://coinone.co.kr)                                                                        | coinone            | [CoinOne](https://coinone.co.kr)                                                                        | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://doc.coinone.co.kr)                                                            |                                                                                                                             |                                                                              |\\n| [![coinspot](https://user-images.githubusercontent.com/1294454/28208429-3cacdf9a-6896-11e7-854e-4c79a772a30f.jpg)](https://www.coinspot.com.au/register?code=PJURCU)                                            | coinspot           | [CoinSpot](https://www.coinspot.com.au/register?code=PJURCU)                                            | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://www.coinspot.com.au/api)                                                      |                                                                                                                             |                                                                              |\\n| [![cryptocom](https://user-images.githubusercontent.com/1294454/147792121-38ed5e36-c229-48d6-b49a-48d05fc19ed4.jpeg)](https://crypto.com/exch/5835vstech)                                                       | cryptocom          | [Crypto.com](https://crypto.com/exch/5835vstech)                                                        | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://exchange-docs.crypto.com/exchange/v1/rest-ws/index.html)                      |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![currencycom](https://user-images.githubusercontent.com/1294454/83718672-36745c00-a63e-11ea-81a9-677b1f789a4d.jpg)](https://currency.com/trading/signup?c=362jaimv&pid=referral)                              | currencycom        | [Currency.com](https://currency.com/trading/signup?c=362jaimv&pid=referral)                             | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://currency.com/api)                                                             |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![delta](https://user-images.githubusercontent.com/1294454/99450025-3be60a00-2931-11eb-9302-f4fd8d8589aa.jpg)](https://www.delta.exchange/app/signup/?code=IULYNB)                                             | delta              | [Delta Exchange](https://www.delta.exchange/app/signup/?code=IULYNB)                                    | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.delta.exchange)                                                          |                                                                                                                             |                                                                              |\\n| [![deribit](https://user-images.githubusercontent.com/1294454/41933112-9e2dd65a-798b-11e8-8440-5bab2959fcb8.jpg)](https://www.deribit.com/reg-1189.4038)                                                        | deribit            | [Deribit](https://www.deribit.com/reg-1189.4038)                                                        | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.deribit.com/v2)                                                          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![digifinex](https://user-images.githubusercontent.com/51840849/87443315-01283a00-c5fe-11ea-8628-c2a0feaf07ac.jpg)](https://www.digifinex.com/en-ww/from/DhOzBg?channelCode=ljaUPp)                            | digifinex          | [DigiFinex](https://www.digifinex.com/en-ww/from/DhOzBg?channelCode=ljaUPp)                             | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://docs.digifinex.com)                                                           |                                                                                                                             |                                                                              |\\n| [![exmo](https://user-images.githubusercontent.com/1294454/27766491-1b0ea956-5eda-11e7-9225-40d67b481b8d.jpg)](https://exmo.me/?ref=131685)                                                                     | exmo               | [EXMO](https://exmo.me/?ref=131685)                                                                     | [![API Version 1.1](https://img.shields.io/badge/1.1-lightgray)](https://exmo.me/en/api_doc?ref=131685)                                            |                                                                                                                             |                                                                              |\\n| [![flowbtc](https://user-images.githubusercontent.com/51840849/87443317-01c0d080-c5fe-11ea-95c2-9ebe1a8fafd9.jpg)](https://one.ndax.io/bfQiSL)                                                                  | flowbtc            | [flowBTC](https://one.ndax.io/bfQiSL)                                                                   | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://www.flowbtc.com.br/api.html)                                                  |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![fmfwio](https://user-images.githubusercontent.com/1294454/159177712-b685b40c-5269-4cea-ac83-f7894c49525d.jpg)](https://fmfw.io/referral/da948b21d6c92d69)                                                    | fmfwio             | [FMFW.io](https://fmfw.io/referral/da948b21d6c92d69)                                                    | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://api.fmfw.io/api/2/explore/)                                                   |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![gate](https://user-images.githubusercontent.com/1294454/31784029-0313c702-b509-11e7-9ccc-bc0da6a0e435.jpg)](https://www.gate.io/ref/2436035)                                                                 | gate               | [Gate.io](https://www.gate.io/ref/2436035)                                                              | [![API Version 4](https://img.shields.io/badge/4-lightgray)](https://www.gate.io/docs/apiv4/en/index.html)                                         | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![gemini](https://user-images.githubusercontent.com/1294454/27816857-ce7be644-6096-11e7-82d6-3c257263229c.jpg)](https://gemini.com/)                                                                           | gemini             | [Gemini](https://gemini.com/)                                                                           | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.gemini.com/rest-api)                                                     |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![hitbtc](https://user-images.githubusercontent.com/1294454/27766555-8eaec20e-5edc-11e7-9c5b-6dc69fc42f5e.jpg)](https://hitbtc.com/?ref_id=5a5d39a65d466)                                                      | hitbtc             | [HitBTC](https://hitbtc.com/?ref_id=5a5d39a65d466)                                                      | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://api.hitbtc.com/v2)                                                            |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![hitbtc3](https://user-images.githubusercontent.com/1294454/27766555-8eaec20e-5edc-11e7-9c5b-6dc69fc42f5e.jpg)](https://hitbtc.com/?ref_id=5a5d39a65d466)                                                     | hitbtc3            | [HitBTC](https://hitbtc.com/?ref_id=5a5d39a65d466)                                                      | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://api.hitbtc.com)                                                               |                                                                                                                             |                                                                              |\\n| [![hollaex](https://user-images.githubusercontent.com/1294454/75841031-ca375180-5ddd-11ea-8417-b975674c23cb.jpg)](https://pro.hollaex.com/signup?affiliation_code=QSWA6G)                                       | hollaex            | [HollaEx](https://pro.hollaex.com/signup?affiliation_code=QSWA6G)                                       | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://apidocs.hollaex.com)                                                          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![huobi](https://user-images.githubusercontent.com/1294454/76137448-22748a80-604e-11ea-8069-6e389271911d.jpg)](https://www.huobi.com/en-us/v/register/double-invite/?inviter_id=11343840&invite_code=6rmm2223) | huobi              | [Huobi](https://www.huobi.com/en-us/v/register/double-invite/?inviter_id=11343840&invite_code=6rmm2223) | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://huobiapi.github.io/docs/spot/v1/en/)                                          | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![huobijp](https://user-images.githubusercontent.com/1294454/85734211-85755480-b705-11ea-8b35-0b7f1db33a2f.jpg)](https://www.huobi.co.jp/register/?invite_code=znnq3)                                          | huobijp            | [Huobi Japan](https://www.huobi.co.jp/register/?invite_code=znnq3)                                      | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://api-doc.huobi.co.jp)                                                          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![idex](https://user-images.githubusercontent.com/51840849/94481303-2f222100-01e0-11eb-97dd-bc14c5943a86.jpg)](https://idex.io)                                                                                | idex               | [IDEX](https://idex.io)                                                                                 | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://docs.idex.io/)                                                                | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![independentreserve](https://user-images.githubusercontent.com/51840849/87182090-1e9e9080-c2ec-11ea-8e49-563db9a38f37.jpg)](https://www.independentreserve.com)                                               | independentreserve | [Independent Reserve](https://www.independentreserve.com)                                               | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://www.independentreserve.com/API)                                               |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![indodax](https://user-images.githubusercontent.com/51840849/87070508-9358c880-c221-11ea-8dc5-5391afbbb422.jpg)](https://indodax.com/ref/testbitcoincoid/1)                                                   | indodax            | [INDODAX](https://indodax.com/ref/testbitcoincoid/1)                                                    | [![API Version 2.0](https://img.shields.io/badge/2.0-lightgray)](https://github.com/btcid/indodax-official-api-docs)                               |                                                                                                                             |                                                                              |\\n| [![itbit](https://user-images.githubusercontent.com/1294454/27822159-66153620-60ad-11e7-89e7-005f6d7f3de0.jpg)](https://www.itbit.com)                                                                          | itbit              | [itBit](https://www.itbit.com)                                                                          | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://api.itbit.com/docs)                                                           |                                                                                                                             |                                                                              |\\n| [![kraken](https://user-images.githubusercontent.com/51840849/76173629-fc67fb00-61b1-11ea-84fe-f2de582f58a3.jpg)](https://www.kraken.com)                                                                       | kraken             | [Kraken](https://www.kraken.com)                                                                        | [![API Version 0](https://img.shields.io/badge/0-lightgray)](https://www.kraken.com/features/api)                                                  |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![krakenfutures](https://user-images.githubusercontent.com/24300605/81436764-b22fd580-9172-11ea-9703-742783e6376d.jpg)](https://futures.kraken.com/)                                                           | krakenfutures      | [Kraken Futures](https://futures.kraken.com/)                                                           | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://support.kraken.com/hc/en-us/categories/360001806372-Futures-API)              |                                                                                                                             |                                                                              |\\n| [![kucoin](https://user-images.githubusercontent.com/51840849/87295558-132aaf80-c50e-11ea-9801-a2fb0c57c799.jpg)](https://www.kucoin.com/ucenter/signup?rcode=E5wkqe)                                           | kucoin             | [KuCoin](https://www.kucoin.com/ucenter/signup?rcode=E5wkqe)                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.kucoin.com)                                                              | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![kucoinfutures](https://user-images.githubusercontent.com/1294454/147508995-9e35030a-d046-43a1-a006-6fabd981b554.jpg)](https://futures.kucoin.com/?rcode=E5wkqe)                                              | kucoinfutures      | [KuCoin Futures](https://futures.kucoin.com/?rcode=E5wkqe)                                              | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.kucoin.com/futures)                                                      |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![kuna](https://user-images.githubusercontent.com/51840849/87153927-f0578b80-c2c0-11ea-84b6-74612568e9e1.jpg)](https://kuna.io?r=kunaid-gvfihe8az7o4)                                                          | kuna               | [Kuna](https://kuna.io?r=kunaid-gvfihe8az7o4)                                                           | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://kuna.io/documents/api)                                                        |                                                                                                                             |                                                                              |\\n| [![latoken](https://user-images.githubusercontent.com/1294454/61511972-24c39f00-aa01-11e9-9f7c-471f1d6e5214.jpg)](https://latoken.com/invite?r=mvgp2djk)                                                        | latoken            | [Latoken](https://latoken.com/invite?r=mvgp2djk)                                                        | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://api.latoken.com)                                                              |                                                                                                                             |                                                                              |\\n| [![lbank](https://user-images.githubusercontent.com/1294454/38063602-9605e28a-3302-11e8-81be-64b1e53c4cfb.jpg)](https://www.lbank.info/invitevip?icode=7QCY)                                                    | lbank              | [LBank](https://www.lbank.info/invitevip?icode=7QCY)                                                    | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/LBank-exchange/lbank-official-api-docs)                            |                                                                                                                             |                                                                              |\\n| [![lbank2](https://user-images.githubusercontent.com/1294454/38063602-9605e28a-3302-11e8-81be-64b1e53c4cfb.jpg)](https://www.lbank.info/invitevip?icode=7QCY)                                                   | lbank2             | [LBank](https://www.lbank.info/invitevip?icode=7QCY)                                                    | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://www.lbank.info/en-US/docs/index.html)                                         |                                                                                                                             |                                                                              |\\n| [![luno](https://user-images.githubusercontent.com/1294454/27766607-8c1a69d8-5ede-11e7-930c-540b5eb9be24.jpg)](https://www.luno.com/invite/44893A)                                                              | luno               | [luno](https://www.luno.com/invite/44893A)                                                              | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://www.luno.com/en/api)                                                          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![lykke](https://user-images.githubusercontent.com/1294454/155840500-1ea4fdf0-47c0-4daa-9597-c6c1cd51b9ec.jpg)](https://www.lykke.com)                                                                         | lykke              | [Lykke](https://www.lykke.com)                                                                          | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://hft-apiv2.lykke.com/swagger/ui/index.html)                                    |                                                                                                                             |                                                                              |\\n| [![mercado](https://user-images.githubusercontent.com/1294454/27837060-e7c58714-60ea-11e7-9192-f05e86adb83f.jpg)](https://www.mercadobitcoin.com.br)                                                            | mercado            | [Mercado Bitcoin](https://www.mercadobitcoin.com.br)                                                    | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://www.mercadobitcoin.com.br/api-doc)                                            |                                                                                                                             |                                                                              |\\n| [![mexc](https://user-images.githubusercontent.com/1294454/137283979-8b2a818d-8633-461b-bfca-de89e8c446b2.jpg)](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                                | mexc               | [MEXC Global](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                          | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://mxcdevelop.github.io/APIDoc/)                                                 | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![mexc3](https://user-images.githubusercontent.com/1294454/137283979-8b2a818d-8633-461b-bfca-de89e8c446b2.jpg)](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                               | mexc3              | [MEXC Global](https://m.mexc.com/auth/signup?inviteCode=1FQ1G)                                          | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://mxcdevelop.github.io/apidocs/spot_v3_en/)                                     |                                                                                                                             |                                                                              |\\n| [![ndax](https://user-images.githubusercontent.com/1294454/108623144-67a3ef00-744e-11eb-8140-75c6b851e945.jpg)](https://one.ndax.io/bfQiSL)                                                                     | ndax               | [NDAX](https://one.ndax.io/bfQiSL)                                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://apidoc.ndax.io/)                                                              |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![novadax](https://user-images.githubusercontent.com/1294454/92337550-2b085500-f0b3-11ea-98e7-5794fb07dd3b.jpg)](https://www.novadax.com.br/?s=ccxt)                                                           | novadax            | [NovaDAX](https://www.novadax.com.br/?s=ccxt)                                                           | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://doc.novadax.com/pt-BR/)                                                       |                                                                                                                             |                                                                              |\\n| [![oceanex](https://user-images.githubusercontent.com/1294454/58385970-794e2d80-8001-11e9-889c-0567cd79b78e.jpg)](https://oceanex.pro/signup?referral=VE24QX)                                                   | oceanex            | [OceanEx](https://oceanex.pro/signup?referral=VE24QX)                                                   | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://api.oceanex.pro/doc/v1)                                                       |                                                                                                                             |                                                                              |\\n| [![okcoin](https://user-images.githubusercontent.com/51840849/87295551-102fbf00-c50e-11ea-90a9-462eebba5829.jpg)](https://www.okcoin.com/account/register?flag=activity&channelId=600001513)                    | okcoin             | [OKCoin](https://www.okcoin.com/account/register?flag=activity&channelId=600001513)                     | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://www.okcoin.com/docs/en/)                                                      |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![okx](https://user-images.githubusercontent.com/1294454/152485636-38b19e4a-bece-4dec-979a-5982859ffc04.jpg)](https://www.okx.com/join/1888677)                                                                | okx                | [OKX](https://www.okx.com/join/1888677)                                                                 | [![API Version 5](https://img.shields.io/badge/5-lightgray)](https://www.okx.com/docs-v5/en/)                                                      | [![CCXT Certified](https://img.shields.io/badge/CCXT-Certified-green.svg)](https://github.com/ccxt/ccxt/wiki/Certification) | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![paymium](https://user-images.githubusercontent.com/51840849/87153930-f0f02200-c2c0-11ea-9c0a-40337375ae89.jpg)](https://www.paymium.com/page/sign-up?referral=eDAzPoRQFMvaAB8sf-qj)                          | paymium            | [Paymium](https://www.paymium.com/page/sign-up?referral=eDAzPoRQFMvaAB8sf-qj)                           | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/Paymium/api-documentation)                                         |                                                                                                                             |                                                                              |\\n| [![phemex](https://user-images.githubusercontent.com/1294454/85225056-221eb600-b3d7-11ea-930d-564d2690e3f6.jpg)](https://phemex.com/register?referralCode=EDNVJ)                                                | phemex             | [Phemex](https://phemex.com/register?referralCode=EDNVJ)                                                | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://github.com/phemex/phemex-api-docs)                                            |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![poloniex](https://user-images.githubusercontent.com/1294454/27766817-e9456312-5ee6-11e7-9b3c-b628ca5626a5.jpg)](https://poloniex.com/signup?c=UBFZJRPJ)                                                      | poloniex           | [Poloniex](https://poloniex.com/signup?c=UBFZJRPJ)                                                      | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.poloniex.com)                                                            |                                                                                                                             |                                                                              |\\n| [![poloniexfutures](https://user-images.githubusercontent.com/1294454/27766817-e9456312-5ee6-11e7-9b3c-b628ca5626a5.jpg)](https://poloniex.com/signup?c=UBFZJRPJ)                                               | poloniexfutures    | [Poloniex Futures](https://poloniex.com/signup?c=UBFZJRPJ)                                              | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://futures-docs.poloniex.com)                                                    |                                                                                                                             |                                                                              |\\n| [![probit](https://user-images.githubusercontent.com/51840849/79268032-c4379480-7ea2-11ea-80b3-dd96bb29fd0d.jpg)](https://www.probit.com/r/34608773)                                                            | probit             | [ProBit](https://www.probit.com/r/34608773)                                                             | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs-en.probit.com)                                                           |                                                                                                                             |                                                                              |\\n| [![ripio](https://user-images.githubusercontent.com/1294454/94507548-a83d6a80-0218-11eb-9998-28b9cec54165.jpg)](https://exchange.ripio.com)                                                                     | ripio              | [Ripio](https://exchange.ripio.com)                                                                     | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://exchange.ripio.com/en/api/)                                                   |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![stex](https://user-images.githubusercontent.com/1294454/69680782-03fd0b80-10bd-11ea-909e-7f603500e9cc.jpg)](https://app.stex.com?ref=36416021)                                                               | stex               | [STEX](https://app.stex.com?ref=36416021)                                                               | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://apidocs.stex.com/)                                                            |                                                                                                                             |                                                                              |\\n| [![tidex](https://user-images.githubusercontent.com/1294454/30781780-03149dc4-a12e-11e7-82bb-313b269d24d4.jpg)](https://tidex.com/exchange)                                                                     | tidex              | [Tidex](https://tidex.com/exchange)                                                                     | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://tidex.com/exchange/public-api)                                                |                                                                                                                             |                                                                              |\\n| [![timex](https://user-images.githubusercontent.com/1294454/70423869-6839ab00-1a7f-11ea-8f94-13ae72c31115.jpg)](https://timex.io/?refcode=1x27vNkTbP1uwkCck)                                                    | timex              | [TimeX](https://timex.io/?refcode=1x27vNkTbP1uwkCck)                                                    | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.timex.io)                                                                |                                                                                                                             |                                                                              |\\n| [![tokocrypto](https://user-images.githubusercontent.com/1294454/183870484-d3398d0c-f6a1-4cce-91b8-d58792308716.jpg)](https://tokocrypto.com)                                                                   | tokocrypto         | [Tokocrypto](https://tokocrypto.com)                                                                    | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://www.tokocrypto.com/apidocs/)                                                  |                                                                                                                             |                                                                              |\\n| [![upbit](https://user-images.githubusercontent.com/1294454/49245610-eeaabe00-f423-11e8-9cba-4b0aed794799.jpg)](https://upbit.com)                                                                              | upbit              | [Upbit](https://upbit.com)                                                                              | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.upbit.com/docs/%EC%9A%94%EC%B2%AD-%EC%88%98-%EC%A0%9C%ED%95%9C)          |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![wavesexchange](https://user-images.githubusercontent.com/1294454/84547058-5fb27d80-ad0b-11ea-8711-78ac8b3c7f31.jpg)](https://waves.exchange)                                                                 | wavesexchange      | [Waves.Exchange](https://waves.exchange)                                                                | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.waves.exchange)                                                          |                                                                                                                             |                                                                              |\\n| [![wazirx](https://user-images.githubusercontent.com/1294454/148647666-c109c20b-f8ac-472f-91c3-5f658cb90f49.jpeg)](https://wazirx.com/invite/k7rrnks5)                                                          | wazirx             | [WazirX](https://wazirx.com/invite/k7rrnks5)                                                            | [![API Version 2](https://img.shields.io/badge/2-lightgray)](https://docs.wazirx.com/#public-rest-api-for-wazirx)                                  |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![whitebit](https://user-images.githubusercontent.com/1294454/66732963-8eb7dd00-ee66-11e9-849b-10d9282bb9e0.jpg)](https://whitebit.com/referral/d9bdf40e-28f2-4b52-b2f9-cd1415d82963)                          | whitebit           | [WhiteBit](https://whitebit.com/referral/d9bdf40e-28f2-4b52-b2f9-cd1415d82963)                          | [![API Version 4](https://img.shields.io/badge/4-lightgray)](https://github.com/whitebit-exchange/api-docs)                                        |                                                                                                                             |                                                                              |\\n| [![woo](https://user-images.githubusercontent.com/1294454/150730761-1a00e5e0-d28c-480f-9e65-089ce3e6ef3b.jpg)](https://referral.woo.org/BAJS6oNmZb3vi3RGA)                                                      | woo                | [WOO X](https://referral.woo.org/BAJS6oNmZb3vi3RGA)                                                     | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://docs.woo.org/)                                                                |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![yobit](https://user-images.githubusercontent.com/1294454/27766910-cdcbfdae-5eea-11e7-9859-03fea873272d.jpg)](https://www.yobit.net)                                                                          | yobit              | [YoBit](https://www.yobit.net)                                                                          | [![API Version 3](https://img.shields.io/badge/3-lightgray)](https://www.yobit.net/en/api/)                                                        |                                                                                                                             |                                                                              |\\n| [![zaif](https://user-images.githubusercontent.com/1294454/27766927-39ca2ada-5eeb-11e7-972f-1b4199518ca6.jpg)](https://zaif.jp)                                                                                 | zaif               | [Zaif](https://zaif.jp)                                                                                 | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://techbureau-api-document.readthedocs.io/ja/latest/index.html)                  |                                                                                                                             |                                                                              |\\n| [![zb](https://user-images.githubusercontent.com/1294454/32859187-cd5214f0-ca5e-11e7-967d-96568e2e2bd1.jpg)](https://www.zb.com/en/register?ref=4301lera)                                                       | zb                 | [ZB](https://www.zb.com/en/register?ref=4301lera)                                                       | [![API Version 1](https://img.shields.io/badge/1-lightgray)](https://www.zb.com/i/developer)                                                       |                                                                                                                             | [![CCXT Pro](https://img.shields.io/badge/CCXT-Pro-black)](https://ccxt.pro) |\\n| [![zonda](https://user-images.githubusercontent.com/1294454/159202310-a0e38007-5e7c-4ba9-a32f-c8263a0291fe.jpg)](https://auth.zondaglobal.com/ref/jHlbB4mIkdS1)                                                 | zonda              | [Zonda](https://auth.zondaglobal.com/ref/jHlbB4mIkdS1)                                                  | [![API Version *](https://img.shields.io/badge/*-lightgray)](https://docs.zonda.exchange/)                                                         |                                                                                                                             |                                                                              |\\n\\nThe list above is updated frequently, new crypto markets, exchanges, bug fixes, and API endpoints are introduced on a regular basis. See the [Manual](https://docs.ccxt.com/en/latest/manual.html) for more details. If you can\\'t find a cryptocurrency exchange in the list above and want it to be added, post a link to it by opening an issue here on GitHub or send us an email.\\n\\nThe library is under [MIT license](https://github.com/ccxt/ccxt/blob/master/LICENSE.txt), that means it\\'s absolutely free for any developer to build commercial and opensource software on top of it, but use it at your own risk with no warranties, as is.\\n\\n---\\n\\n## Install\\n\\nThe easiest way to install the CCXT library is to use a package manager:\\n\\n- [ccxt in **NPM**](https://www.npmjs.com/package/ccxt) (JavaScript / Node v7.6+)\\n- [ccxt in **PyPI**](https://pypi.python.org/pypi/ccxt) (Python 3.5.3+)\\n- [ccxt in **Packagist/Composer**](https://packagist.org/packages/ccxt/ccxt) (PHP 7.0+)\\n\\nThis library is shipped as an all-in-one module implementation with minimalistic dependencies and requirements:\\n\\n- [js/](https://github.com/ccxt/ccxt/blob/master/js/) in JavaScript\\n- [python/](https://github.com/ccxt/ccxt/blob/master/python/) in Python (generated from JS)\\n- [php/](https://github.com/ccxt/ccxt/blob/master/php/) in PHP (generated from JS)\\n\\nYou can also clone it into your project directory from [ccxt GitHub repository](https://github.com/ccxt/ccxt):\\n\\n```shell\\ngit clone https://github.com/ccxt/ccxt.git  # including 1GB of commit history\\n\\n# or\\n\\ngit clone https://github.com/ccxt/ccxt.git --depth 1  # avoid downloading 1GB of commit history\\n```\\n\\n### JavaScript (NPM)\\n\\nJavaScript version of CCXT works in both Node and web browsers. Requires ES6 and `async/await` syntax support (Node 7.6.0+). When compiling with Webpack and Babel, make sure it is [not excluded](https://github.com/ccxt/ccxt/issues/225#issuecomment-331905178) in your `babel-loader` config.\\n\\n[ccxt in **NPM**](https://www.npmjs.com/package/ccxt)\\n\\n```shell\\nnpm install ccxt\\n```\\n\\n```JavaScript\\nvar ccxt = require (\\'ccxt\\')\\n\\nconsole.log (ccxt.exchanges) // print all available exchanges\\n```\\n\\n### JavaScript (for use with the `<script>` tag):\\n\\nAll-in-one browser bundle (dependencies included), served from a CDN of your choice:\\n\\n* jsDelivr: https://cdn.jsdelivr.net/npm/ccxt@2.8.84/dist/ccxt.browser.js\\n* unpkg: https://unpkg.com/ccxt@2.8.84/dist/ccxt.browser.js\\n\\nCDNs are not updated in real-time and may have delays. Defaulting to the most recent version without specifying the version number is not recommended. Please, keep in mind that we are not responsible for the correct operation of those CDN servers.\\n\\n```HTML\\n<script type=\"text/javascript\" src=\"https://cdn.jsdelivr.net/npm/ccxt@2.8.84/dist/ccxt.browser.js\"></script>\\n```\\n\\nCreates a global `ccxt` object:\\n\\n```JavaScript\\nconsole.log (ccxt.exchanges) // print all available exchanges\\n```\\n\\n### Python\\n\\n[ccxt in **PyPI**](https://pypi.python.org/pypi/ccxt)\\n\\n```shell\\npip install ccxt\\n```\\n\\n```Python\\nimport ccxt\\nprint(ccxt.exchanges) # print a list of all available exchange classes\\n```\\n\\nThe library supports concurrent asynchronous mode with asyncio and async/await in Python 3.5.3+\\n\\n```Python\\nimport ccxt.async_support as ccxt # link against the asynchronous version of ccxt\\n```\\n\\n### PHP\\n\\n[ccxt in PHP with **Packagist/Composer**](https://packagist.org/packages/ccxt/ccxt) (PHP 7.0+)\\n\\nIt requires common PHP modules:\\n\\n- cURL\\n- mbstring (using UTF-8 is highly recommended)\\n- PCRE\\n- iconv\\n- gmp (this is a built-in extension as of PHP 7.2+)\\n\\n```PHP\\ninclude \"ccxt.php\";\\nvar_dump (\\\\ccxt\\\\Exchange::$exchanges); // print a list of all available exchange classes\\n```\\n\\nThe library supports concurrent asynchronous mode using tools from [RecoilPHP](https://github.com/recoilphp/recoil) and [ReactPHP](https://reactphp.org/) in PHP 7.1+. Read the [Manual](https://docs.ccxt.com/en/latest/manual.html) for more details.\\n\\n### Docker\\n\\nYou can get CCXT installed in a container along with all the supported languages and dependencies. This may be useful if you want to contribute to CCXT (e.g. run the build scripts and tests — please see the [Contributing](https://github.com/ccxt/ccxt/blob/master/CONTRIBUTING.md) document for the details on that).\\n\\nUsing `docker-compose` (in the cloned CCXT repository):\\n\\n```shell\\ndocker-compose run --rm ccxt\\n```\\n\\nYou don\\'t need the Docker image if you\\'re not going to develop CCXT. If you just want to use CCXT –\\xa0just install it as a regular package into your project.\\n\\n---\\n\\n## Documentation\\n\\nRead the [Manual](https://docs.ccxt.com/en/latest/manual.html) for more details.\\n\\n## Usage\\n\\n### Intro\\n\\nThe CCXT library consists of a public part and a private part. Anyone can use the public part immediately after installation. Public APIs provide unrestricted access to public information for all exchange markets without the need to register a user account or have an API key.\\n\\nPublic APIs include the following:\\n\\n- market data\\n- instruments/trading pairs\\n- price feeds (exchange rates)\\n- order books\\n- trade history\\n- tickers\\n- OHLC(V) for charting\\n- other public endpoints\\n\\nIn order to trade with private APIs you need to obtain API keys from an exchange\\'s website. It usually means signing up to the exchange and creating API keys for your account. Some exchanges require personal info or identification. Sometimes verification may be necessary as well. In this case you will need to register yourself, this library will not create accounts or API keys for you. Some exchanges expose API endpoints for registering an account, but most exchanges don\\'t. You will have to sign up and create API keys on their websites.\\n\\nPrivate APIs allow the following:\\n\\n- manage personal account info\\n- query account balances\\n- trade by making market and limit orders\\n- deposit and withdraw fiat and crypto funds\\n- query personal orders\\n- get ledger history\\n- transfer funds between accounts\\n- use merchant services\\n\\nThis library implements full public and private REST APIs for all exchanges. WebSocket and FIX implementations in JavaScript, PHP, Python are available in [CCXT Pro](https://ccxt.pro), which is a professional addon to CCXT with support for WebSocket streams.\\n\\nThe CCXT library supports both camelcase notation (preferred in JavaScript) and underscore notation (preferred in Python and PHP), therefore all methods can be called in either notation or coding style in any language.\\n\\n```JavaScript\\n// both of these notations work in JavaScript/Python/PHP\\nexchange.methodName ()  // camelcase pseudocode\\nexchange.method_name () // underscore pseudocode\\n```\\n\\nRead the [Manual](https://docs.ccxt.com/en/latest/manual.html) for more details.\\n\\n### JavaScript\\n\\n```JavaScript\\n\\'use strict\\';\\nconst ccxt = require (\\'ccxt\\');\\n\\n(async function () {\\n    let kraken    = new ccxt.kraken ()\\n    let bitfinex  = new ccxt.bitfinex ({ verbose: true })\\n    let huobipro  = new ccxt.huobipro ()\\n    let okcoinusd = new ccxt.okcoin ({\\n        apiKey: \\'YOUR_PUBLIC_API_KEY\\',\\n        secret: \\'YOUR_SECRET_PRIVATE_KEY\\',\\n    })\\n\\n    const exchangeId = \\'binance\\'\\n        , exchangeClass = ccxt[exchangeId]\\n        , exchange = new exchangeClass ({\\n            \\'apiKey\\': \\'YOUR_API_KEY\\',\\n            \\'secret\\': \\'YOUR_SECRET\\',\\n        })\\n\\n    console.log (kraken.id,    await kraken.loadMarkets ())\\n    console.log (bitfinex.id,  await bitfinex.loadMarkets  ())\\n    console.log (huobipro.id,  await huobipro.loadMarkets ())\\n\\n    console.log (kraken.id,    await kraken.fetchOrderBook (kraken.symbols[0]))\\n    console.log (bitfinex.id,  await bitfinex.fetchTicker (\\'BTC/USD\\'))\\n    console.log (huobipro.id,  await huobipro.fetchTrades (\\'ETH/USDT\\'))\\n\\n    console.log (okcoinusd.id, await okcoinusd.fetchBalance ())\\n\\n    // sell 1 BTC/USD for market price, sell a bitcoin for dollars immediately\\n    console.log (okcoinusd.id, await okcoinusd.createMarketSellOrder (\\'BTC/USD\\', 1))\\n\\n    // buy 1 BTC/USD for $2500, you pay $2500 and receive ฿1 when the order is closed\\n    console.log (okcoinusd.id, await okcoinusd.createLimitBuyOrder (\\'BTC/USD\\', 1, 2500.00))\\n\\n    // pass/redefine custom exchange-specific order params: type, amount, price or whatever\\n    // use a custom order type\\n    bitfinex.createLimitSellOrder (\\'BTC/USD\\', 1, 10, { \\'type\\': \\'trailing-stop\\' })\\n\\n}) ();\\n```\\n\\n### Python\\n\\n```Python\\n# coding=utf-8\\n\\nimport ccxt\\n\\nhitbtc   = ccxt.hitbtc({\\'verbose\\': True})\\nbitmex   = ccxt.bitmex()\\nhuobipro = ccxt.huobipro()\\nexmo     = ccxt.exmo({\\n    \\'apiKey\\': \\'YOUR_PUBLIC_API_KEY\\',\\n    \\'secret\\': \\'YOUR_SECRET_PRIVATE_KEY\\',\\n})\\nkraken = ccxt.kraken({\\n    \\'apiKey\\': \\'YOUR_PUBLIC_API_KEY\\',\\n    \\'secret\\': \\'YOUR_SECRET_PRIVATE_KEY\\',\\n})\\n\\nexchange_id = \\'binance\\'\\nexchange_class = getattr(ccxt, exchange_id)\\nexchange = exchange_class({\\n    \\'apiKey\\': \\'YOUR_API_KEY\\',\\n    \\'secret\\': \\'YOUR_SECRET\\',\\n})\\n\\nhitbtc_markets = hitbtc.load_markets()\\n\\nprint(hitbtc.id, hitbtc_markets)\\nprint(bitmex.id, bitmex.load_markets())\\nprint(huobipro.id, huobipro.load_markets())\\n\\nprint(hitbtc.fetch_order_book(hitbtc.symbols[0]))\\nprint(bitmex.fetch_ticker(\\'BTC/USD\\'))\\nprint(huobipro.fetch_trades(\\'LTC/USDT\\'))\\n\\nprint(exmo.fetch_balance())\\n\\n# sell one ฿ for market price and receive $ right now\\nprint(exmo.id, exmo.create_market_sell_order(\\'BTC/USD\\', 1))\\n\\n# limit buy BTC/EUR, you pay €2500 and receive ฿1  when the order is closed\\nprint(exmo.id, exmo.create_limit_buy_order(\\'BTC/EUR\\', 1, 2500.00))\\n\\n# pass/redefine custom exchange-specific order params: type, amount, price, flags, etc...\\nkraken.create_market_buy_order(\\'BTC/USD\\', 1, {\\'trading_agreement\\': \\'agree\\'})\\n```\\n\\n### PHP\\n\\n```PHP\\ninclude \\'ccxt.php\\';\\n\\n$poloniex = new \\\\ccxt\\\\poloniex ();\\n$bittrex  = new \\\\ccxt\\\\bittrex  (array (\\'verbose\\' => true));\\n$quoinex  = new \\\\ccxt\\\\quoinex   ();\\n$zaif     = new \\\\ccxt\\\\zaif     (array (\\n    \\'apiKey\\' => \\'YOUR_PUBLIC_API_KEY\\',\\n    \\'secret\\' => \\'YOUR_SECRET_PRIVATE_KEY\\',\\n));\\n$hitbtc   = new \\\\ccxt\\\\hitbtc   (array (\\n    \\'apiKey\\' => \\'YOUR_PUBLIC_API_KEY\\',\\n    \\'secret\\' => \\'YOUR_SECRET_PRIVATE_KEY\\',\\n));\\n\\n$exchange_id = \\'binance\\';\\n$exchange_class = \"\\\\\\\\ccxt\\\\\\\\$exchange_id\";\\n$exchange = new $exchange_class (array (\\n    \\'apiKey\\' => \\'YOUR_API_KEY\\',\\n    \\'secret\\' => \\'YOUR_SECRET\\',\\n));\\n\\n$poloniex_markets = $poloniex->load_markets ();\\n\\nvar_dump ($poloniex_markets);\\nvar_dump ($bittrex->load_markets ());\\nvar_dump ($quoinex->load_markets ());\\n\\nvar_dump ($poloniex->fetch_order_book ($poloniex->symbols[0]));\\nvar_dump ($bittrex->fetch_trades (\\'BTC/USD\\'));\\nvar_dump ($quoinex->fetch_ticker (\\'ETH/EUR\\'));\\nvar_dump ($zaif->fetch_ticker (\\'BTC/JPY\\'));\\n\\nvar_dump ($zaif->fetch_balance ());\\n\\n// sell 1 BTC/JPY for market price, you pay ¥ and receive ฿ immediately\\nvar_dump ($zaif->id, $zaif->create_market_sell_order (\\'BTC/JPY\\', 1));\\n\\n// buy BTC/JPY, you receive ฿1 for ¥285000 when the order closes\\nvar_dump ($zaif->id, $zaif->create_limit_buy_order (\\'BTC/JPY\\', 1, 285000));\\n\\n// set a custom user-defined id to your order\\n$hitbtc->create_order (\\'BTC/USD\\', \\'limit\\', \\'buy\\', 1, 3000, array (\\'clientOrderId\\' => \\'123\\'));\\n```\\n\\n## Contributing\\n\\nPlease read the [CONTRIBUTING](https://github.com/ccxt/ccxt/blob/master/CONTRIBUTING.md) document before making changes that you would like adopted in the code. Also, read the [Manual](https://docs.ccxt.com/en/latest/manual.html) for more details.\\n\\n## Support Developer Team\\n\\nWe are investing a significant amount of time into the development of this library. If CCXT made your life easier and you want to help us improve it further, or if you want to speed up development of new features and exchanges, please support us with a tip. We appreciate all contributions!\\n\\n### Sponsors\\n\\nSupport this project by becoming a sponsor. Your logo will show up here with a link to your website.\\n\\n[[Become a sponsor](https://opencollective.com/ccxt#sponsor)]\\n\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/0/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/0/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/1/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/1/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/2/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/2/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/3/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/3/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/4/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/4/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/5/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/5/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/6/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/6/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/7/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/7/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/8/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/8/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/sponsor/9/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/sponsor/9/avatar.svg\"></a>\\n\\n### Supporters\\n\\nSupport this project by becoming a supporter. Your avatar will show up here with a link to your website.\\n\\n[[Become a supporter](https://opencollective.com/ccxt#supporter)]\\n\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/0/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/0/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/1/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/1/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/2/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/2/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/3/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/3/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/4/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/4/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/5/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/5/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/6/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/6/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/7/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/7/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/8/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/8/avatar.svg\"></a>\\n<a href=\"https://opencollective.com/ccxt/tiers/supporter/9/website\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/supporter/9/avatar.svg\"></a>\\n\\n### Backers\\n\\nThank you to all our backers! [[Become a backer](https://opencollective.com/ccxt#backer)]\\n\\n<a href=\"https://opencollective.com/ccxt#backers\" target=\"_blank\"><img src=\"https://opencollective.com/ccxt/tiers/backer.svg?width=890\"></a>\\n\\nThank you!\\n\\n## Social\\n\\n- [Follow us on Twitter](https://twitter.com/ccxt_official)\\n- [Read our blog on Medium](https://medium.com/@ccxt)\\n- <sub>[![Discord](https://img.shields.io/discord/690203284119617602?logo=discord&logoColor=white)](https://discord.gg/dhzSKYU)</sub>\\n- [CCXT Channel on Telegram](https://t.me/ccxt_announcements) (important announcements)\\n- [CCXT Chat on Telegram](https://t.me/ccxt_chat) (technical support)\\n\\n## Contact Us\\n\\nFor business inquiries: info@ccxt.trade\\n'},\n",
       " {'repo': 'aceat64/EasyBitcoin-PHP',\n",
       "  'language': 'PHP',\n",
       "  'readme_contents': 'EasyBitcoin-PHP\\n===============\\n\\nA simple class for making calls to Bitcoin\\'s API using PHP.\\n\\nGetting Started\\n---------------\\n1. Include easybitcoin.php into your PHP script:\\n\\n    ```php\\n    require_once(\\'easybitcoin.php\\');\\n    ```\\n2. Initialize Bitcoin connection/object:\\n\\n    ```php\\n    $bitcoin = new Bitcoin(\\'username\\',\\'password\\');\\n    ```\\n\\n    Optionally, you can specify a host, port. Default is HTTP on localhost port 8332.\\n\\n    ```php\\n    $bitcoin = new Bitcoin(\\'username\\',\\'password\\',\\'localhost\\',\\'8332\\');\\n    ```\\n\\n    If you wish to make an SSL connection you can set an optional CA certificate or leave blank\\n    ```php\\n    $bitcoin->setSSL(\\'/full/path/to/mycertificate.cert\\');\\n    ````\\n\\n3. Make calls to bitcoind as methods for your object. Examples:\\n\\n    ```php\\n    $bitcoin->getinfo();\\n    \\n    $bitcoin->getrawtransaction(\\'0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098\\',1);\\n    \\n    $bitcoin->getblock(\\'000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f\\');\\n   \\n    $bitcoin->bumpfee(\\'f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16\\', [\"fee_rate\" => 50]);\\n    ```\\n\\nAdditional Info\\n---------------\\n* When a call fails for any reason, it will return false and put the error message in `$bitcoin->error`\\n\\n* The HTTP status code can be found in $bitcoin->status and will either be a valid HTTP status code or will be 0 if cURL was unable to connect.\\n\\n* The full response (not usually needed) is stored in `$bitcoin->response` while the raw JSON is stored in `$bitcoin->raw_response`\\n'},\n",
       " {'repo': 'libbitcoin/libbitcoin-explorer',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': 'See README.md'},\n",
       " {'repo': 'eveybcd/BitcoinDiamond',\n",
       "  'language': 'C++',\n",
       "  'readme_contents': 'Bitcoin Diamond\\n===============\\n\\nhttps://www.bitcoindiamond.org\\n\\nWhat is BitcoinDiamond?\\n-----------------------\\n\\nBitcoin Diamond (BCD) is a fork of Bitcoin that occurs at the predetermined height of block 495866 \\nand therewith a new chain will be generated as the BCD. Bitcoin Diamond miners will begin creating \\nblocks with a new proof-of-work algorithm, and will consecutively develop and enhance the protection \\nfor account transfer and privacy based on original features of BTC. This will cause a bifurcation of \\nthe Bitcoin blockchain. The original Bitcoin blockchain will continue on unaltered, but a new branch\\nof the blockchain will split off from the original chain. It shares the same transaction history \\nwith Bitcoin until it starts branching and coming into a unique block from which it diverges. \\nAs a result of this process, a new cryptocurrency was created which we call “Bitcoin Diamond”.\\nFor more information, see https://www.bitcoindiamond.org\\n\\nLicense\\n-------\\n\\nBitcoinDiamond is released under the terms of the MIT license. See [COPYING](COPYING) for more\\ninformation or see https://opensource.org/licenses/MIT.\\n\\nAnti replay attacks\\n------------------\\n\\nBitcoin Diamond has an anti-replay-attacks function to prevent bitcoin-diamond transactions replay\\non bitcoin network, or bitcoin transactions replay on bitcoin-diamond network.\\n\\nWhat is the total amount for Bitcoin Diamond (BCD)?\\n---------------------------------------------------\\n\\nThe total amount of BCD is 210 million. No more increase.170 million BCD, 1BTC : 10BCD will be presented \\nto the Bitcoin holders for the long-term Bitcoin ECOSYSTEM support.The rest 40 million will be automatically \\ntransferred into the community rewards pool as tributes and mining.\\n\\nWhat problems do Bitcoin Diamond attempt to solve?\\n--------------------------------------------------\\nAfter nine years of rapid development of Bitcoin, high transactions fees and Bitcoin no longer meets the \\ndemands from rising numbers of clients. And various kinds of problems have arisen, which mainly consist \\nof the following aspects: \\n1. Lack of privacy protection.\\n2. Slow transaction confirmations.\\n3. High threshold for new members.'},\n",
       " {'repo': 'phishman3579/Bitcoin',\n",
       "  'language': 'Java',\n",
       "  'readme_contents': '# Bitcoin\\nAn example Bitcoin implementation which can be used to learn about Bitcoin/Blockchain. This implementations is for educational use only.\\n\\n# Overview.\\n\\n## Wallet\\n\\nThe Wallet is how peers interact with the Bitcoin peer-to-peer network. The Wallet generates a public key and a private key which it uses to sign each Transaction. The pulic key is the send-to address used by the Bitcoin network. Each Wallet has the ability to send coins from your account to another account and it also has the ability to confirm Transactions (except it\\'s own) which it receives from the Bitcoin peer-to-peer network.\\n\\n```\\n    Wallet {\\n      sendCoin(entity, value); // Creates a new Transaction\\n      handleTransaction(Transaction); // Receives a unconfirmed Transaction\\n      handleConfirmation(Transaction); // Receives a confirmed Transaction and adds to blockchain\\n    }\\n```\\n\\n## Transaction\\n\\nTransactions are just a collection of input transactions, output transactions, a value, and a signature. \\n\\n```\\n    Transaction {\\n        byte[] header;\\n        Transaction[] inputs;\\n        Transaction[] outputs;\\n        long value;\\n        byte[] signature;\\n    }\\n```\\n\\nSee the [Transaction Class](https://github.com/phishman3579/Bitcoin/blob/master/src/com/jwetherell/bitcoin/data_model/Transaction.java) for reference.\\n\\n#### The Wallet also has a number of Transaction rules:\\n\\n* Once a Transaction has been used as an input, it cannot be used again. \\n* All inputs on a Transaction have to be completely consumed on a transaction.\\n\\nNote: To send a Bitcoin transaction, you have to already own a Bitcoin. Getting an initial Bitcoin is usually done by trading something for a number of Bitcoins. One caveat of, having to own a Bitcoin to make a transaction, is the first transaction. The first transaction is called the genesis transaction, it is the only transaction which does not need input transactions.\\n\\n### An example Transaction\\n\\nIf Justin wants to send 6 coins to George:\\n\\nLedger:\\n\\n|  Justin\\'s unused Transactions  |  George\\'s unused Transaction  |\\n|  ----------------------------- | ----------------------------- | \\n| Transaction #1 : 5 Coins       |                               |\\n| Transaction #2 : 3 Coins       |                               |\\n| Transaction #3 : 7 Coins       |                               |\\n\\n```\\n    Aggregate Transaction #4 {\\n      byte[]        header      \"6 coins for George and 2 coins to Justin\"\\n      Transaction[] input       { Transaction #1, Transaction #2 }\\n      Transaction[] output      { Transaction #5, Transaction #6 }\\n      int           value       0\\n      byte[]        signature   \"Justin\\'s signature based on the Header\"\\n    }\\n```\\nNote: The \\'value\\' on the Aggregate Transaction (#4) is a reward for anyone who confirms the Transaction. The higher the reward, the better chance the Transaction will be processed quicker.\\n\\n```\\n    Transaction #5 {\\n      byte[]        header      \"2 coins to Justin\"\\n      Transaction[] input       { Transaction #1, Transaction #2 }\\n      Transaction[] output      { }\\n      int           value       2\\n      byte[]        signature   \"Justin\\'s signature based on the Header\"\\n    }\\n\\n    Transaction #6 {\\n      byte[]        header      \"6 coins for George\"\\n      Transaction[] input       { Transaction #1, Transaction #2 }\\n      Transaction[] output      { }\\n      int           value       6\\n      byte[]        signature   \"Justin\\'s signature based on the Header\"\\n    }\\n```\\n\\nThe Aggregate Transaction (#4) will remove Transaction #1 and #2 from Justin\\'s unused Transactions. Since the total of all inputs is 8 coins, which is 2 more than what Justin wants to send to George, the output will contain a Transaction which sends 2 coins back to Justin.\\n\\nThe Wallet will use it\\'s private key to sign the Header of the Aggregate Transactions (#4) and it will also sign each of the output Transactions (#5 & #6). It will then send Transaction #4 to the Bitcoin network for confirmation. \\n\\nEach peer on the Bitcoin network will receive the Transaction and try to confirm it. \\n\\nTo confirm a Transaction, a Peer will:\\n* Check the Signature of Transaction against the public key of the sender. \\n\\nIf it passes:\\n* Send the confirmed Transaction to the Bitcoin network.\\n\\n## Block\\n\\nThe confirmed Transaction (#4) is added to a pool of confirmed Transactions. Peers (also called Miners) will gather confirmed Transactions from the pool and put them into a Block. A Block contains a number of confirmed Transactions, the Miner\\'s signature, and a couple of other fields used for \"Proof of work\" processing.\\n\\n```\\n    Block {\\n      Transaction[]     transactions\\n      int               nonce\\n      int               zeros\\n      byte[]            previousHash\\n      byte[]            nextHash\\n      byte[]            signature\\n    }\\n```\\n\\nSee the [Block Class](https://github.com/phishman3579/Bitcoin/blob/master/src/com/jwetherell/bitcoin/data_model/Block.java) for reference.\\n\\nMiners will create a single \\'block hash\\' from all the confirmed Transactions in the Block. They will then go through the process of \"Proof of work\". The goal of the \"Proof of work\" is to create a hash which begins with a random number of zeros (see the \\'zeros\\' field). \"Proof of work\" is designed to be processor intensive which adds randomness to the time it takes to process a Block. A Miner will take the \\'block hash\\' and append a random integer (called a \\'nonce\\') to it. It will then create a new hash from \\'block hash + nonce\\' and see if it satisfies the \"Proof of work\", this process will repeat until it finds a \\'nonce\\' which satisfies the \"Proof of work\"\\n\\nSee the [Proof of work](https://github.com/phishman3579/Bitcoin/blob/master/src/com/jwetherell/bitcoin/ProofOfWork.java) for reference.\\n\\nOnce a Miner finds a \\'nonce\\' which satisfies the \"Proof of work\", it will:\\n* Create another hash (see \\'nextHash\\') using the Blockchain\\'s current hash (see \\'previousHash\\') and the \\'block hash\\' \\n* Send the Block to the Bitcoin network.\\n\\n```\\n    Block #1 {\\n      Transaction[]     transactions    { Transaction #4 }\\n      int               nonce           453;\\n      int               zeros           3;\\n      byte[]            previousHash    \"Blockchain hash #1\";\\n      byte[]            nextHash        \"Blockchain hash #2\";\\n      byte[]            signature       \"Miner\\'s signature\";\\n    }\\n```\\nPeers on the Bitcoin network will receive the Block and start confirming it. \\n\\nTo confirm the Block, A Peer will:\\n* Make sure the \\'nonce\\' satisfies the \"Proof of work\"\\n* Check the Block\\'s signature \\n* Check the signature of each Trasaction in the Block.\\n\\nIf everything passes:\\n* Add the block to it\\'s Blockchain.\\n* Send the confirmed Block to the Bitcoin network\\n\\n## Blockchain\\n\\nThe Blockchain is a simple structure which contains a list of confirmed Blocks, a list of Transactions in chronological order, a list of unused Transactions, and the current hash.\\n\\nNote: all transactions in the same block are said to have happened at the same time.\\n\\n```\\n    Blockchain {\\n        List<Block>         blockchain\\n        List<Transactions>  transactions\\n        List<Transaction>   unused\\n        byte[]              currentHash\\n    }\\n```\\n\\nSee the [Blockchain](https://github.com/phishman3579/Bitcoin/blob/master/src/com/jwetherell/bitcoin/BlockChain.java) for reference.\\n\\n\\nWhen the Peer adds the Block to the Blockchain, the Blockchain will:\\n* Check to see if the \\'previousHash\\' from the Block matches it\\'s \\'currentHash\\', \\n* Check to see if the input Transactions from all the Transactions in the Block are \\'unused\\'\\n\\nIf everything passes:\\n* The Block is added to the \\'blockChain\\'\\n* The Transaction is added to the \\'transactions\\' list\\n* All \\'input\\' transactions are removed from the \\'unused\\' list\\n* All the \\'output\\' transactions are added to the \\'unused\\' list\\n* The \\'currentHash\\' is updated to \\'nextHash\\' from the current Block.\\n\\n```\\n    Blockchain {\\n        List<Block>         blockchain      { Block #0 }\\n        List<Transactions>  transactions    { Transaction #0 }\\n        List<Transaction>   unused          { Transaction #1, Transaction #2, Transaction #3 }\\n        byte[]              currentHash     \"Blockchain hash #1\"\\n    }\\n```\\n\\nUpdated Blockchain.\\n\\n```\\n    Blockchain {\\n        List<Block>         blockchain      { Block #0, Block #1 };\\n        List<Transactions>  transactions    { Transaction #0, Transaction #4 }\\n        List<Transaction>   unused          { Transaction #3, Transaction #5, Transaction #6 }\\n        byte[]              currentHash     \"Blockchain hash #2\"\\n    }\\n```\\n\\nLedger:\\n\\n|  Justin\\'s unused Transactions  |  George\\'s unused Transaction  |\\n|  ----------------------------- | ----------------------------- | \\n| Transaction #3 : 7 Coins       | Transaction #6 : 6 Coins      |\\n| Transaction #5 : 2 Coins       |                               |\\n|                                |                               |\\n\\nBased off of [1](http://www.michaelnielsen.org/ddi/how-the-bitcoin-protocol-actually-works/) and [2](http://www.imponderablethings.com/2013/07/how-bitcoin-works-under-hood.html)\\n\\nAlso see the [original paper](https://bitcoin.org/bitcoin.pdf)\\n'}]"
      ]
     },
     "execution_count": 33,
     "metadata": {},
     "output_type": "execute_result"
    }
   ],
   "source": [
    "scrape_github_data()"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": null,
   "id": "d9cb90be",
   "metadata": {},
   "outputs": [],
   "source": []
  }
 ],
 "metadata": {
  "kernelspec": {
   "display_name": "Python 3 (ipykernel)",
   "language": "python",
   "name": "python3"
  },
  "language_info": {
   "codemirror_mode": {
    "name": "ipython",
    "version": 3
   },
   "file_extension": ".py",
   "mimetype": "text/x-python",
   "name": "python",
   "nbconvert_exporter": "python",
   "pygments_lexer": "ipython3",
   "version": "3.9.13"
  }
 },
 "nbformat": 4,
 "nbformat_minor": 5
}