{"id":50557928,"url":"https://github.com/judecoin/judecoin","last_synced_at":"2026-06-04T09:00:34.453Z","repository":{"id":41417636,"uuid":"344045915","full_name":"Judecoin/judecoin","owner":"Judecoin","description":"Website of the judecoin Ecosystem project","archived":false,"fork":false,"pushed_at":"2026-05-26T15:17:54.000Z","size":185436,"stargazers_count":94,"open_issues_count":2,"forks_count":20,"subscribers_count":11,"default_branch":"master","last_synced_at":"2026-05-26T17:16:03.294Z","etag":null,"topics":["blockchain","cryptonote","judecoin","privacy","security"],"latest_commit_sha":null,"homepage":"https://www.judecoin.io","language":"C++","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Judecoin.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"docs/CONTRIBUTING.md","funding":".github/FUNDING.yml","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null},"funding":{"custom":"https://www.judecoin.io/contribution"}},"created_at":"2021-03-03T07:54:20.000Z","updated_at":"2026-05-26T15:23:51.000Z","dependencies_parsed_at":"2024-07-28T02:43:51.112Z","dependency_job_id":"c56df364-69db-422f-95ca-d3e287db5512","html_url":"https://github.com/Judecoin/judecoin","commit_stats":null,"previous_names":[],"tags_count":60,"template":false,"template_full_name":null,"purl":"pkg:github/Judecoin/judecoin","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Judecoin%2Fjudecoin","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Judecoin%2Fjudecoin/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Judecoin%2Fjudecoin/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Judecoin%2Fjudecoin/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Judecoin","download_url":"https://codeload.github.com/Judecoin/judecoin/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Judecoin%2Fjudecoin/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33897568,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-04T02:00:06.755Z","response_time":64,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["blockchain","cryptonote","judecoin","privacy","security"],"created_at":"2026-06-04T09:00:26.054Z","updated_at":"2026-06-04T09:00:34.413Z","avatar_url":"https://github.com/Judecoin.png","language":"C++","funding_links":["https://www.judecoin.io/contribution"],"categories":[],"sub_categories":[],"readme":"# Judecoin\n\nCopyright (c) 2014-2026 The Judecoin Project.   \nPortions Copyright (c) The Cryptonote developers.\n\n## Table of Contents\n\n- [Development Resources](#development-resources)\n- [Documentation](#documentation)\n- [Vulnerability Response](#vulnerability-response)\n- [Research](#research)\n- [Announcements](#announcements)\n- [Translations](#translations)\n- [Coverage](#coverage)\n- [Introduction](#introduction)\n- [About This Project](#about-this-project)\n- [Supporting the Project](#supporting-the-project)\n- [License](#license)\n- [Contributing](#contributing)\n- [Scheduled Software Upgrades](#scheduled-software-upgrades)\n- [Release Staging Schedule and Protocol](#release-staging-schedule-and-protocol)\n- [Compiling Judecoin from Source](#compiling-judecoin-from-source)\n- [Running Judecoind](#running-judecoind)\n- [Internationalization](#internationalization)\n- [Using Tor](#using-tor)\n- [Pruning](#pruning)\n- [Debugging](#debugging)\n- [Known Issues](#known-issues)\n\n## Development Resources\n\n- Web: [judecoin.info](https://www.judecoin.info/)\n- Community-News: [github.com/Judecoin/information](https://github.com/Judecoin/information/tree/main/community-news)\n- GitHub: [github.com/Judecoin/judecoin](https://github.com/Judecoin/judecoin)\n- Block Explorer: [judeblock.org](https://www.judeblock.org/)\n\n## Documentation\n\n- [Judecoin Wallet Documentation](https://github.com/Judecoin/wallet)\n- [PoS Evolution and Service Node Documentation](https://github.com/Judecoin/pos-evolution)\n\n## Vulnerability Response\n\nResponsible disclosure is encouraged.\n\nIf you discover a security issue, please report it through the official Judecoin communication channels or the official repository issue process when appropriate.\n\nPlease do not publicly disclose sensitive vulnerabilities before they have been reviewed.\n\n## Research\n\nJudecoin research and development may include work related to privacy, cryptography, protocols, fungibility, network behavior, wallet tools, and Service Node operation.\n\nFor roadmap-related research and development directions, please refer to the [Judecoin Roadmap](https://www.judecoin.info/roadmap).\n\nResearchers, developers, and contributors are welcome to review the codebase, discuss technical improvements, and submit relevant contributions.\n\n## Announcements\n\nImportant announcements, software updates, release notes, and upgrade information should be checked through official Judecoin resources.\n\nFor updates, please refer to the [Judecoin Community News](https://www.judecoin.info/community-news).\n\nUsers, wallet operators, node operators, and service providers should keep their software updated according to official release guidance.\n\n## Translations\n\nJudecoin wallet tools may support multiple languages depending on the release version.\n\nTranslation support and localization behavior may vary by wallet type and software release.\n\n## Coverage\n\nCoverage and testing status may vary by repository configuration, release branch, and development stage.\n\nPlease refer to the current repository status, release notes, and available CI/test results where applicable.\n\n| Type | Status |\n|------|--------|\n| License | [![License](https://img.shields.io/badge/license-BSD3-blue.svg)](https://opensource.org/licenses/BSD-3-Clause) |\n\n## Introduction\n\nJUDE is many things. A private cryptocurrency. A secure messaging platform. A network anonymity layer. A vision for a future where privacy is effortless.\n\nWe provide a range of tools and services powered by the JUDE network, enabling people all over the world to leverage the power of decentralised blockchain networks to achieve unparalleled privacy and security as they work, play, and live their day-to-day lives on the internet. But this isn’t a plan we have for the future — our suite of privacy tools already exists, and it is already used by over one million people.\n\nJudecoin is a privacy-focused cryptocurrency and blockchain network built for private digital payments, censorship-resistant value transfer, decentralized participation, and long-term ecosystem infrastructure.\n\nAt its core, Judecoin is designed to protect user privacy while enabling secure value transfer on a verifiable blockchain network. It gives users a way to send, receive, store, and participate in the network’s digital value without relying on fully transparent transaction systems that expose financial activity to public tracing.\n\nJUDE is the native currency of the Judecoin network. It is used for transactions, value transfer, staking, Service Node participation, reward distribution, atomic swaps, and future ecosystem activity.\n\nJudecoin is built as a privacy-focused network that brings together private digital currency, Proof of Stake, Service Nodes, wallet infrastructure, atomic swap development, cross-chain value movement, privacy tools, network anonymity, and future ecosystem applications.\n\n**Privacy:** Judecoin uses privacy-oriented cryptographic technology to help users send and receive funds without exposing unnecessary transaction information on the public blockchain. This helps protect purchases, receipts, transfers, and financial activity by default.\n\n**Security:** Using the power of a distributed peer-to-peer consensus network, every transaction on the network is cryptographically secured. Individual wallets have recovery information that should be backed up carefully and protected with strong security practices.\n\n**Censorship resistance:** Judecoin is designed to let users hold, send, receive, and participate in digital value without relying on banks, payment platforms, or centralized intermediaries.\n\n**Decentralization:** The utility of Judecoin depends on its decentralized peer-to-peer network, wallet infrastructure, Service Node operation, Proof of Stake participation, research-driven development, atomic swap capability, cross-chain value movement, and community participation. Anyone should be able to run Judecoin software, validate the integrity of the blockchain, and contribute to the long-term resilience of the Judecoin network.\n\n## About This Project\n\nThis repository contains the core implementation of Judecoin. It is open source and free to use under the terms specified in the license agreement below.\n\nThe project includes the core daemon, wallet tools, build files, network components, and related technical documentation needed to build, run, and contribute to the Judecoin network.\n\nAs with many open source projects, this repository may include ongoing development work. Users running production systems should follow official release guidance and use tagged stable releases whenever possible.\n\n**Anyone is welcome to contribute to Judecoin's codebase and documentation.** Clear, accurate, and relevant pull requests are welcome. Larger or more complex changes should be discussed in advance or reviewed carefully through the pull request process.\n\n## Supporting the Project\n\nJudecoin is a community-supported open source project.\n\nIf you would like to support the project, you may do so through the official donation address below, or by using the `donate` command in the command-line wallet.\n\nThe Judecoin donation address is:\n\n`J6GX4gh7ix1ft9xVvUci45cTPFPjaRihnNQ7Y8kRvAxCNGVh6Fw8Hw83aJ8hFZyYtvB2CBaBfNKK3gSr4zJkqox1Jm2TiLF`\n\n## License\n\nSee [LICENSE](LICENSE).\n\n## Contributing\n\nIf you want to help, see [CONTRIBUTING](docs/CONTRIBUTING.md) for contribution guidelines.\n\nYou may contribute by improving documentation, reporting issues, testing releases, submitting code, or helping improve user guides.\n\nBefore submitting changes, please make sure your contribution is clear, accurate, and relevant to the Judecoin project.\n\n## Scheduled Software Upgrades\n\nJudecoin uses a fixed-schedule software upgrade (hard fork) mechanism to implement new features. This means that users of Judecoin (end users and service providers) should run current versions and upgrade their software on a regular schedule. Software upgrades occur during the months of April and October. The required software for these upgrades will be available prior to the scheduled date. Please check the repository prior to this date for the proper Judecoin software version. Below is the historical schedule and the projected schedule for the next upgrade.\nDates are provided in the format YYYY-MM-DD.\n\n| Software upgrade block height | Date | Fork version | Minimum Judecoin version | Recommended Judecoin version | Details |\n|-------------------------------|------|--------------|--------------------------|------------------------------|---------|\n\n## Release Staging Schedule and Protocol\n\nApproximately three months prior to a scheduled software upgrade, a branch from master will be created with the new release version tag. Pull requests that address bugs should then be made to both master and the new release branch. Pull requests that require extensive review and testing (generally, optimizations and new features) should *not* be made to the release branch.\n\n## Compiling Judecoin from Source\n\n### Dependencies\n\nThe following table summarizes the tools and libraries required to build. A\nfew of the libraries are also included in this repository (marked as\n\"Vendored\"). By default, the build uses the library installed on the system\nand ignores the vendored sources. However, if no library is found installed on\nthe system, then the vendored source will be built and used. The vendored\nsources are also used for statically-linked builds because distribution\npackages often include only shared library binaries (`.so`) but not static\nlibrary archives (`.a`).\n\n| Dep          | Min. version  | Vendored | Debian/Ubuntu pkg    | Arch pkg     | Void pkg           | Fedora pkg          | Optional | Purpose         |\n| ------------ | ------------- | -------- | -------------------- | ------------ | ------------------ | ------------------- | -------- | --------------- |\n| GCC          | 4.7.3         | NO       | `build-essential`    | `base-devel` | `base-devel`       | `gcc`               | NO       |                 |\n| CMake        | 3.5           | NO       | `cmake`              | `cmake`      | `cmake`            | `cmake`             | NO       |                 |\n| pkg-config   | any           | NO       | `pkg-config`         | `base-devel` | `base-devel`       | `pkgconf`           | NO       |                 |\n| Boost        | 1.58          | NO       | `libboost-all-dev`   | `boost`      | `boost-devel`      | `boost-devel`       | NO       | C++ libraries   |\n| OpenSSL      | basically any | NO       | `libssl-dev`         | `openssl`    | `libressl-devel`   | `openssl-devel`     | NO       | sha256 sum      |\n| libzmq       | 3.0.0         | NO       | `libzmq3-dev`        | `zeromq`     | `zeromq-devel`     | `zeromq-devel`      | NO       | ZeroMQ library  |\n| OpenPGM      | ?             | NO       | `libpgm-dev`         | `libpgm`     |                    | `openpgm-devel`     | NO       | For ZeroMQ      |\n| libnorm[2]   | ?             | NO       | `libnorm-dev`        |              |                    |                     | YES      | For ZeroMQ      |\n| libunbound   | 1.4.16        | YES      | `libunbound-dev`     | `unbound`    | `unbound-devel`    | `unbound-devel`     | NO       | DNS resolver    |\n| libsodium    | ?             | NO       | `libsodium-dev`      | `libsodium`  | `libsodium-devel`  | `libsodium-devel`   | NO       | cryptography    |\n| libunwind    | any           | NO       | `libunwind8-dev`     | `libunwind`  | `libunwind-devel`  | `libunwind-devel`   | YES      | Stack traces    |\n| liblzma      | any           | NO       | `liblzma-dev`        | `xz`         | `liblzma-devel`    | `xz-devel`          | YES      | For libunwind   |\n| libreadline  | 6.3.0         | NO       | `libreadline6-dev`   | `readline`   | `readline-devel`   | `readline-devel`    | YES      | Input editing   |\n| ldns         | 1.6.17        | NO       | `libldns-dev`        | `ldns`       | `libldns-devel`    | `ldns-devel`        | YES      | SSL toolkit     |\n| expat        | 1.1           | NO       | `libexpat1-dev`      | `expat`      | `expat-devel`      | `expat-devel`       | YES      | XML parsing     |\n| GTest        | 1.5           | YES      | `libgtest-dev`[1]    | `gtest`      | `gtest-devel`      | `gtest-devel`       | YES      | Test suite      |\n| Doxygen      | any           | NO       | `doxygen`            | `doxygen`    | `doxygen`          | `doxygen`           | YES      | Documentation   |\n| Graphviz     | any           | NO       | `graphviz`           | `graphviz`   | `graphviz`         | `graphviz`          | YES      | Documentation   |\n| lrelease     | ?             | NO       | `qttools5-dev-tools` | `qt5-tools`  | `qt5-tools`        | `qt5-linguist`      | YES      | Translations    |\n| libhidapi    | ?             | NO       | `libhidapi-dev`      | `hidapi`     | `hidapi-devel`     | `hidapi-devel`      | YES      | Hardware wallet |\n| libusb       | ?             | NO       | `libusb-1.0-0-dev`   | `libusb`     | `libusb-devel`     | `libusbx-devel`     | YES      | Hardware wallet |\n| libprotobuf  | ?             | NO       | `libprotobuf-dev`    | `protobuf`   | `protobuf-devel`   | `protobuf-devel`    | YES      | Hardware wallet |\n| protoc       | ?             | NO       | `protobuf-compiler`  | `protobuf`   | `protobuf`         | `protobuf-compiler` | YES      | Hardware wallet |\n| libudev      | ?             | No       | `libudev-dev`        | `systemd`    | `eudev-libudev-devel` | `systemd-devel`     | YES      | Hardware wallet |\n\n[1] On Debian/Ubuntu `libgtest-dev` only includes sources and headers. You must\nbuild the library binary manually. This can be done with the following command ```sudo apt-get install libgtest-dev \u0026\u0026 cd /usr/src/gtest \u0026\u0026 sudo cmake . \u0026\u0026 sudo make \u0026\u0026 sudo mv libg* /usr/lib/ ```\n[2] libnorm-dev is needed if your zmq library was built with libnorm, and not needed otherwise\n\nInstall all dependencies at once on Debian/Ubuntu:\n\n``` sudo apt update \u0026\u0026 sudo apt install build-essential cmake pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind8-dev liblzma-dev libreadline6-dev libldns-dev libexpat1-dev doxygen graphviz libpgm-dev qttools5-dev-tools libhidapi-dev libusb-1.0-0-dev libprotobuf-dev protobuf-compiler libudev-dev```\n\nInstall all dependencies at once on macOS with the provided Brewfile:\n``` brew update \u0026\u0026 brew bundle --file=contrib/brew/Brewfile ```\n\nFreeBSD 12.1 one-liner required to build dependencies:\n```pkg install git gmake cmake pkgconf boost-libs libzmq4 libsodium```\n\n### Cloning the repository\n\nClone recursively to pull-in needed submodule(s):\n\n`$ git clone --recursive https://github.com/Judecoin/judecoin`\n\nIf you already have a repo cloned, initialize and update:\n\n`$ cd judecoin \u0026\u0026 git submodule init \u0026\u0026 git submodule update`\n\n### Build instructions\n\nJudecoin uses the CMake build system and a top-level [Makefile](Makefile) that\ninvokes cmake commands as needed.\n\n#### On Linux and macOS\n\n* Install the dependencies\n* Change to the root of the source code directory, change to the most recent release tag, and build:\n\n    ```bash\n    cd judecoin\n    git checkout \u003clatest-release-tag\u003e\n    make\n    ```\n\n    *Optional*: If your machine has several cores and enough memory, enable\n    parallel build by running `make -j\u003cnumber of threads\u003e` instead of `make`. For\n    this to be worthwhile, the machine should have one core and about 2GB of RAM\n    available per thread.\n\n    *Note*: The instructions above will compile the most stable release of the\n    Judecoin software. If you would like to use and test the most recent software,\n    use ```git checkout master```. The master branch may contain updates that are\n    both unstable and incompatible with release software, though testing is always\n    encouraged.\n\n* The resulting executables can be found in `build/release/bin`\n\n* Add `PATH=\"$PATH:$HOME/judecoin/build/release/bin\"` to `.profile`\n\n* Run Judecoin with `judecoind --detach`\n\n* **Optional**: build and run the test suite to verify the binaries:\n\n    ```bash\n    make release-test\n    ```\n\n    *NOTE*: `core_tests` test may take a few hours to complete.\n\n* **Optional**: to build binaries suitable for debugging:\n\n    ```bash\n    make debug\n    ```\n\n* **Optional**: to build statically-linked binaries:\n\n    ```bash\n    make release-static\n    ```\n\nDependencies need to be built with -fPIC. Static libraries usually aren't, so you may have to build them yourself with -fPIC. Refer to their documentation for how to build them.\n\n* **Optional**: build documentation in `doc/html` (omit `HAVE_DOT=YES` if `graphviz` is not installed):\n\n    ```bash\n    HAVE_DOT=YES doxygen Doxyfile\n    ```\n\n#### On the Raspberry Pi\n\nTested on a Raspberry Pi Zero with a clean install of minimal Raspbian Stretch (2017-09-07 or later). If you are using Raspbian Jessie, [please see note in the following section](#note-for-raspbian-jessie-users).\n\n* `apt-get update \u0026\u0026 apt-get upgrade` to install all of the latest software\n\n* Install the dependencies for Judecoin from the 'Debian' column in the table above.\n\n* Increase the system swap size:\n\n    ```bash\n    sudo /etc/init.d/dphys-swapfile stop  \n    sudo nano /etc/dphys-swapfile  \n    CONF_SWAPSIZE=2048\n    sudo /etc/init.d/dphys-swapfile start\n    ```\n\n* If using an external hard disk without an external power supply, ensure it gets enough power to avoid hardware issues when syncing, by adding the line \"max_usb_current=1\" to /boot/config.txt\n\n* Clone Judecoin and checkout the most recent release version:\n\n    ```bash\n    git clone https://github.com/Judecoin/judecoin.git\n    cd judecoin\n    git checkout \u003clatest-release-tag\u003e\n    ```\n\n* Build:\n\n    ```bash\n    make release\n    ```\n\n* Wait 4-6 hours\n\n* The resulting executables can be found in `build/release/bin`\n\n* Add `PATH=\"$PATH:$HOME/judecoin/build/release/bin\"` to `.profile`\n\n* Run Judecoin with `judecoind --detach`\n\n* You may wish to reduce the size of the swap file after the build has finished, and delete the boost directory from your home directory\n\n#### Note for Raspbian Jessie users\n\nIf you are using the older Raspbian Jessie image, compiling Judecoin is a bit more complicated. The version of Boost available in the Debian Jessie repositories is too old to use with Judecoin, and thus you must compile a newer version yourself. The following explains the extra steps and has been tested on a Raspberry Pi 2 with a clean install of minimal Raspbian Jessie.\n\n* As before, `apt-get update \u0026\u0026 apt-get upgrade` to install all of the latest software, and increase the system swap size\n\n    ```bash\n    sudo /etc/init.d/dphys-swapfile stop\n    sudo nano /etc/dphys-swapfile\n    CONF_SWAPSIZE=2048\n    sudo /etc/init.d/dphys-swapfile start\n    ```\n    \n* Then, install the dependencies for Judecoin except for `libunwind` and `libboost-all-dev`\n\n* Install the latest version of boost (this may first require invoking `apt-get remove --purge libboost*-dev` to remove a previous version if you're not using a clean install):\n\n    ```bash\n    cd\n    wget https://sourceforge.net/projects/boost/files/boost/1.72.0/boost_1_72_0.tar.bz2\n    tar xvfo boost_1_72_0.tar.bz2\n    cd boost_1_72_0\n    ./bootstrap.sh\n    sudo ./b2\n    ```\n\n* Wait ~8 hours\n\n    ```bash    \n    sudo ./bjam cxxflags=-fPIC cflags=-fPIC -a install\n    ```\n\n* Wait ~4 hours\n\n* From here, follow the [general Raspberry Pi instructions](#on-the-raspberry-pi) from the \"Clone Judecoin and checkout most recent release version\" step.\n\n### On Windows\n\nBinaries for Windows are built on Windows using the MinGW toolchain within\n[MSYS2 environment](https://www.msys2.org). The MSYS2 environment emulates a\nPOSIX system. The toolchain runs within the environment and *cross-compiles*\nbinaries that can run outside of the environment as a regular Windows\napplication.\n\n**Preparing the build environment**\n\n* Download and install the [MSYS2 installer](https://www.msys2.org), either the 64-bit or the 32-bit package, depending on your system.\n* Open the MSYS shell via the `MSYS2 Shell` shortcut\n* Update packages using pacman:  \n\n    ```bash\n    pacman -Syu\n    ```\n\n* Exit the MSYS shell using Alt+F4  \n* Edit the properties for the `MSYS2 Shell` shortcut changing \"msys2_shell.bat\" to \"msys2_shell.cmd -mingw64\" for 64-bit builds or \"msys2_shell.cmd -mingw32\" for 32-bit builds\n* Restart MSYS shell via modified shortcut and update packages again using pacman:  \n\n    ```bash\n    pacman -Syu\n    ```\n\n\n* Install dependencies:\n\n    To build for 64-bit Windows:\n\n    ```bash\n    pacman -S mingw-w64-x86_64-toolchain make mingw-w64-x86_64-cmake mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-zeromq mingw-w64-x86_64-libsodium mingw-w64-x86_64-hidapi\n    ```\n\n    To build for 32-bit Windows:\n\n    ```bash\n    pacman -S mingw-w64-i686-toolchain make mingw-w64-i686-cmake mingw-w64-i686-boost mingw-w64-i686-openssl mingw-w64-i686-zeromq mingw-w64-i686-libsodium mingw-w64-i686-hidapi\n    ```\n\n* Open the MingW shell via `MinGW-w64-Win64 Shell` shortcut on 64-bit Windows\n  or `MinGW-w64-Win64 Shell` shortcut on 32-bit Windows. Note that if you are\n  running 64-bit Windows, you will have both 64-bit and 32-bit MinGW shells.\n\n**Cloning**\n\n* To git clone, run:\n\n    ```bash\n    git clone --recursive https://github.com/Judecoin/judecoin.git\n    ```\n\n**Building**\n\n* Change to the cloned directory, run:\n\n    ```bash\n    cd judecoin\n    ```\n\n* If you would like a specific [version/tag](https://github.com/Judecoin/judecoin/tags), do a git checkout for that version. eg. 'v0.17.1.0'. If you don't care about the version and just want binaries from master, skip this step:\n\n    ```bash\n    git checkout \u003clatest-release-tag\u003e\n    ```\n\n* If you are on a 64-bit system, run:\n\n    ```bash\n    make release-static-win64\n    ```\n\n* If you are on a 32-bit system, run:\n\n    ```bash\n    make release-static-win32\n    ```\n\n* The resulting executables can be found in `build/release/bin`\n\n* **Optional**: to build Windows binaries suitable for debugging on a 64-bit system, run:\n\n    ```bash\n    make debug-static-win64\n    ```\n\n* **Optional**: to build Windows binaries suitable for debugging on a 32-bit system, run:\n\n    ```bash\n    make debug-static-win32\n    ```\n\n* The resulting executables can be found in `build/debug/bin`\n\n### On FreeBSD\n\nThe project can be built from scratch by following instructions for Linux above(but use `gmake` instead of `make`). \nIf you are running Judecoin in a jail, you need to add `sysvsem=\"new\"` to your jail configuration, otherwise lmdb will throw the error message: `Failed to open lmdb environment: Function not implemented`.\n\nJudecoin is also available as a port or package as `judecoin-cli`.\n\n### On OpenBSD\n\nYou will need to add a few packages to your system. `pkg_add cmake gmake zeromq libiconv boost`.\n\nThe `doxygen` and `graphviz` packages are optional and require the xbase set.\nRunning the test suite also requires `py-requests` package.\n\nBuild Judecoin: `env DEVELOPER_LOCAL_TOOLS=1 BOOST_ROOT=/usr/local gmake release-static`\n\nNote: you may encounter the following error when compiling the latest version of Judecoin as a normal user:\n\n```\nLLVM ERROR: out of memory\nc++: error: unable to execute command: Abort trap (core dumped)\n```\n\nThen you need to increase the data ulimit size to 2GB and try again: `ulimit -d 2000000`\n\n### On NetBSD\n\nCheck that the dependencies are present: `pkg_info -c libexecinfo boost-headers boost-libs protobuf readline libusb1 zeromq git-base pkgconf gmake cmake | more`, and install any that are reported missing, using `pkg_add` or from your pkgsrc tree.  Readline is optional but worth having.\n\nThird-party dependencies are usually under `/usr/pkg/`, but if you have a custom setup, adjust the \"/usr/pkg\" (below) accordingly.\n\nClone the Judecoin repository recursively and checkout the most recent release as described above. Then build Judecoin: `gmake BOOST_ROOT=/usr/pkg LDFLAGS=\"-Wl,-R/usr/pkg/lib\" release`.  The resulting executables can be found in `build/NetBSD/[Release version]/Release/bin/`.\n\n### On Solaris\n\nThe default Solaris linker can't be used, you have to install GNU ld, then run cmake manually with the path to your copy of GNU ld:\n\n```bash\nmkdir -p build/release\ncd build/release\ncmake -DCMAKE_LINKER=/path/to/ld -D CMAKE_BUILD_TYPE=Release ../..\ncd ../..\n```\n\nThen you can run make as usual.\n\n### On Linux for Android (using docker)\n\n```bash\n# Build image (for ARM 32-bit)\ndocker build -f utils/build_scripts/android32.Dockerfile -t judecoin-android .\n# Build image (for ARM 64-bit)\ndocker build -f utils/build_scripts/android64.Dockerfile -t judecoin-android .\n# Create container\ndocker create -it --name judecoin-android judecoin-android bash\n# Get binaries\ndocker cp judecoin-android:/src/build/release/bin .\n```\n\n### Building portable statically linked binaries\n\nBy default, in either dynamically or statically linked builds, binaries target the specific host processor on which the build happens and are not portable to other processors. Portable binaries can be built using the following targets:\n\n* ```make release-static-linux-x86_64``` builds binaries on Linux on x86_64 portable across POSIX systems on x86_64 processors\n* ```make release-static-linux-i686``` builds binaries on Linux on x86_64 or i686 portable across POSIX systems on i686 processors\n* ```make release-static-linux-armv8``` builds binaries on Linux portable across POSIX systems on armv8 processors\n* ```make release-static-linux-armv7``` builds binaries on Linux portable across POSIX systems on armv7 processors\n* ```make release-static-linux-armv6``` builds binaries on Linux portable across POSIX systems on armv6 processors\n* ```make release-static-win64``` builds binaries on 64-bit Windows portable across 64-bit Windows systems\n* ```make release-static-win32``` builds binaries on 64-bit or 32-bit Windows portable across 32-bit Windows systems\n\n### Cross Compiling\n\nYou can also cross-compile static binaries on Linux for Windows and macOS with the `depends` system.\n\n* ```make depends target=x86_64-linux-gnu``` for 64-bit linux binaries.\n* ```make depends target=x86_64-w64-mingw32``` for 64-bit windows binaries.\n  * Requires: `python3 g++-mingw-w64-x86-64 wine1.6 bc`\n* ```make depends target=x86_64-apple-darwin``` for Intel macOS binaries.\n  * Requires: `clang`\n* ```make depends target=arm64-apple-darwin``` for Apple Silicon macOS binaries.\n  * Requires: `clang`\n* ```make depends target=i686-linux-gnu``` for 32-bit linux binaries.\n  * Requires: `g++-multilib bc`\n* ```make depends target=i686-w64-mingw32``` for 32-bit windows binaries.\n  * Requires: `python3 g++-mingw-w64-i686`\n* ```make depends target=arm-linux-gnueabihf``` for armv7 binaries.\n  * Requires: `g++-arm-linux-gnueabihf`\n* ```make depends target=aarch64-linux-gnu``` for armv8 binaries.\n  * Requires: `g++-aarch64-linux-gnu`\n* ```make depends target=riscv64-linux-gnu``` for RISC V 64 bit binaries.\n  * Requires: `g++-riscv64-linux-gnu`\n* ```make depends target=x86_64-unknown-freebsd``` for freebsd binaries.\n  * Requires: `clang-8`\n* ```make depends target=arm-linux-android``` for 32bit android binaries\n* ```make depends target=aarch64-linux-android``` for 64bit android binaries\n\n\nThe required packages are the names for each toolchain on apt. Depending on your distro, they may have different names.\n\nUsing `depends` might also be easier to compile Judecoin on Windows than using MSYS. Activate Windows Subsystem for Linux (WSL) with a distro (for example Ubuntu), install the apt build-essentials and follow the `depends` steps as depicted above.\n\nThe produced binaries still link libc dynamically. If the binary is compiled on a current distribution, it might not run on an older distribution with an older installation of libc. Passing `-DBACKCOMPAT=ON` to cmake will make sure that the binary will run on systems having at least libc version 2.17.\n\n## Installing Judecoin from a package\n\n**DISCLAIMER: These packages are not part of this repository or maintained by this project's contributors, and as such, do not go through the same review process to ensure their trustworthiness and security.**\n\nPackages are available for\n\n\n* Debian 12 (Bookworm) or later\n\n    ```bash\n    sudo apt install judecoin\n    ```\n\n* Arch Linux:\n\n* Void Linux:\n\n    ```bash\n    xbps-install -S judecoin\n    ```\n* Guix\n\n    ```bash\n    guix package -i judecoin\n    ```\n\n* macOS (homebrew)\n    ```bash\n    brew install judecoin\n    ```\n* Docker\n\n    ```bash\n    # Build using all available cores\n    docker build -t judecoin .\n\n    # or build using a specific number of cores (reduce RAM requirement)\n    docker build --build-arg NPROC=1 -t judecoin .\n\n    # either run in foreground\n    docker run -it -v /judecoin/chain:/root/.bitjudecoin -v /judecoin/wallet:/wallet -p 18080:18080 judecoin\n\n    # or in background\n    docker run -it -d -v /judecoin/chain:/root/.bitjudecoin -v /judecoin/wallet:/wallet -p 18080:18080 judecoin\n    ```\n\n* The build needs 3 GB space.\n* Wait one hour or more\n\nPackaging for your favorite distribution would be a welcome contribution!\n\n## Running judecoind\n\nThe build places the binary in `bin/` sub-directory within the build directory\nfrom which cmake was invoked (repository root by default). To run in the\nforeground:\n\n```bash\n./bin/judecoind\n```\n\nTo list all available options, run `./bin/judecoind --help`.  Options can be\nspecified either on the command line or in a configuration file passed by the\n`--config-file` argument.  To specify an option in the configuration file, add\na line with the syntax `argumentname=value`, where `argumentname` is the name\nof the argument without the leading dashes, for example, `log-level=1`.\n\nTo run in background:\n\n```bash\n./bin/judecoind --log-file judecoind.log --detach\n```\n\nTo run as a systemd service, copy\n[judecoind.service](utils/systemd/judecoind.service) to `/etc/systemd/system/` and\n[judecoind.conf](utils/conf/judecoind.conf) to `/etc/`. The [example\nservice](utils/systemd/judecoind.service) assumes that the user `judecoin` exists\nand its home is the data directory specified in the [example\nconfig](utils/conf/judecoind.conf).\n\nIf you're on Mac, you may need to add the `--max-concurrency 1` option to\njudecoin-wallet-cli, and possibly judecoind, if you get crashes refreshing.\n\n## Internationalization\n\nSee [README.i18n.md](docs/README.i18n.md).\n\n## Using Tor\n\n\u003e There is a new, still experimental, [integration with Tor](docs/ANONYMITY_NETWORKS.md). The\n\u003e feature allows connecting over IPv4 and Tor simultaneously - IPv4 is used for\n\u003e relaying blocks and relaying transactions received by peers whereas Tor is\n\u003e used solely for relaying transactions received over local RPC. This provides\n\u003e privacy and better protection against surrounding node (sybil) attacks.\n\nJudecoin can also be used with torsocks by setting the following configuration parameters and environment variables:\n\n* `--p2p-bind-ip 127.0.0.1` on the command line or `p2p-bind-ip=127.0.0.1` in\n  judecoind.conf to disable listening for connections on external interfaces.\n* `--no-igd` on the command line or `no-igd=1` in judecoind.conf to disable IGD\n  (UPnP port forwarding negotiation), which is pointless with Tor.\n* `DNS_PUBLIC=tcp` or `DNS_PUBLIC=tcp://x.x.x.x` where x.x.x.x is the IP of the\n  desired DNS server, for DNS requests to go over TCP, so that they are routed\n  through Tor. When IP is not specified, judecoind uses the default list of\n  servers defined in [src/common/dns_utils.cpp](src/common/dns_utils.cpp).\n* `TORSOCKS_ALLOW_INBOUND=1` to tell torsocks to allow judecoind to bind to interfaces\n   to accept connections from the wallet. On some Linux systems, torsocks\n   allows binding to localhost by default, so setting this variable is only\n   necessary to allow binding to local LAN/VPN interfaces to allow wallets to\n   connect from remote hosts. On other systems, it may be needed for local wallets\n   as well.\n* Do NOT pass `--detach` when running through torsocks with systemd, (see\n  [utils/systemd/judecoind.service](utils/systemd/judecoind.service) for details).\n* If you use the wallet with a Tor daemon via the loopback IP (eg, 127.0.0.1:9050),\n  then use `--untrusted-daemon` unless it is your own hidden service.\n\nExample command line to start Judecoind through Tor:\n\n```bash\nDNS_PUBLIC=tcp torsocks judecoind --p2p-bind-ip 127.0.0.1 --no-igd\n```\n\nA helper script is in contrib/tor/judecoin-over-tor.sh. It assumes Tor is installed\nalready, and runs Tor and Judecoin with the right configuration.\n\n### Using Tor on Tails\n\nTAILS ships with a very restrictive set of firewall rules. Therefore, you need\nto add a rule to allow this connection too, in addition to telling torsocks to\nallow inbound connections. Full example:\n\n```bash\nsudo iptables -I OUTPUT 2 -p tcp -d 127.0.0.1 -m tcp --dport 18081 -j ACCEPT\nDNS_PUBLIC=tcp torsocks ./judecoind --p2p-bind-ip 127.0.0.1 --no-igd --rpc-bind-ip 127.0.0.1 \\\n    --data-dir /home/amnesia/Persistent/your/directory/to/the/blockchain\n```\n\n## Pruning\n\nAs of May 2020, the full Judecoin blockchain file is about 80 GB. One can store a pruned blockchain, which is about 28 GB.\nA pruned blockchain can only serve part of the historical chain data to other peers, but is otherwise identical in\nfunctionality to the full blockchain.\nTo use a pruned blockchain, it is best to start the initial sync with --prune-blockchain. However, it is also possible\nto prune an existing blockchain using the judecoin-blockchain-prune tool or using the --prune-blockchain judecoind option\nwith an existing chain. If an existing chain exists, pruning will temporarily require disk space to store both the full\nand pruned blockchains.\n\n## Debugging\n\nThis section contains general instructions for debugging failed installs or problems encountered with Judecoin. First, ensure you are running the latest version built from the GitHub repository.\n\n### Obtaining stack traces and core dumps on Unix systems\n\nWe generally use the tool `gdb` (GNU debugger) to provide stack trace functionality, and `ulimit` to provide core dumps in builds which crash or segfault.\n\n* To use `gdb` in order to obtain a stack trace for a build that has stalled:\n\nRun the build.\n\nOnce it stalls, enter the following command:\n\n```bash\ngdb /path/to/judecoind `pidof judecoind`\n```\n\nType `thread apply all bt` within gdb in order to obtain the stack trace\n\n* If however the core dumps or segfaults:\n\nEnter `ulimit -c unlimited` on the command line to enable unlimited filesizes for core dumps\n\nEnter `echo core | sudo tee /proc/sys/kernel/core_pattern` to stop cores from being hijacked by other tools\n\nRun the build.\n\nWhen it terminates with an output along the lines of \"Segmentation fault (core dumped)\", there should be a core dump file in the same directory as judecoind. It may be named just `core`, or `core.xxxx` with numbers appended.\n\nYou can now analyse this core dump with `gdb` as follows:\n\n```bash\ngdb /path/to/judecoind /path/to/dumpfile\n```\n\nPrint the stack trace with `bt`\n\n * If a program crashed and cores are managed by systemd, the following can also get a stack trace for that crash:\n\n```bash\ncoredumpctl -1 gdb\n```\n\n#### To run Judecoin within gdb:\n\nType `gdb /path/to/judecoind`\n\nPass command-line options with `--args` followed by the relevant arguments\n\nType `run` to run judecoind\n\n### Analysing memory corruption\n\nThere are two tools available:\n\n#### ASAN\n\nConfigure Judecoin with the -D SANITIZE=ON cmake flag, eg:\n\n```bash\ncd build/debug \u0026\u0026 cmake -D SANITIZE=ON -D CMAKE_BUILD_TYPE=Debug ../..\n```\n\nYou can then run the Judecoin tools normally. Performance will typically halve.\n\n#### valgrind\n\nInstall valgrind and run as `valgrind /path/to/judecoind`. It will be very slow.\n\n### LMDB\n\nInstructions for debugging suspected blockchain corruption as per @HYC\n\nThere is an `mdb_stat` command in the LMDB source that can print statistics about the database but it's not routinely built. This can be built with the following command:\n\n```bash\ncd ~/judecoin/external/db_drivers/liblmdb \u0026\u0026 make\n```\n\nThe output of `mdb_stat -ea \u003cpath to blockchain dir\u003e` will indicate inconsistencies in the blocks, block_heights and block_info table.\n\nThe output of `mdb_dump -s blocks \u003cpath to blockchain dir\u003e` and `mdb_dump -s block_info \u003cpath to blockchain dir\u003e` is useful for indicating whether blocks and block_info contain the same keys.\n\nThese records are dumped as hex data, where the first line is the key and the second line is the data.\n\n## Known Issues\n\n### Protocols\n\n#### Socket-based\n\nBecause of the nature of the socket-based protocols that drive Judecoin, certain protocol weaknesses are somewhat unavoidable at this time. While these weaknesses can theoretically be fully mitigated, the effort required (the means) may not justify the ends. As such, please consider taking the following precautions if you are a Judecoin node operator:\n\n- Run `judecoind` on a \"secured\" machine. If operational security is not your forte, at a very minimum, have a dedicated computer running `judecoind` and **do not** browse the web, use email clients, or use any other potentially harmful apps on your `judecoind` machine. **Do not click links or load URL/MUA content on the same machine**. Doing so may potentially exploit weaknesses in commands which accept \"localhost\" and \"127.0.0.1\".\n- If you plan on hosting a public \"remote\" node, start `judecoind` with `--restricted-rpc`. This is a must.\n\n#### Blockchain-based\n\nCertain blockchain \"features\" can be considered \"bugs\" if misused correctly. Consequently, please consider the following:\n\n- When receiving Judecoin, be aware that it may be locked for an arbitrary time if the sender elected to, preventing you from spending that Judecoin until the lock time expires. You may want to hold off acting upon such a transaction until the unlock time lapses. To get a sense of that time, you can consider the remaining blocktime until unlock as seen in the `show_transfers` command.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjudecoin%2Fjudecoin","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjudecoin%2Fjudecoin","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjudecoin%2Fjudecoin/lists"}