](https://mymonero.com)\n[

](http://kitware.com)\n[

](http://dome9.com)\n[

](http://araxis.com)\n[

](http://www.jetbrains.com/)\n[

](http://www.navicat.com/)\n[

](http://www.symas.com/)\n\nThere are also several mining pools that kindly donate a portion of their fees, [a list of them can be found on our Bitcointalk post](https://bitcointalk.org/index.php?topic=583449.0).\n\n## License\n\nSee [LICENSE](LICENSE).\n\n## Contributing\n\nIf you want to help out, see [CONTRIBUTING](CONTRIBUTING.md) for a set of guidelines.\n\n## Scheduled software upgrades\n\nMonero uses a fixed-schedule software upgrade (hard fork) mechanism to implement new features. This means that users of Monero (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 Monero 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\n| Software upgrade block height | Date | Fork version | Minimum Monero version | Recommended Monero version | Details | \n| ------------------------------ | -----------| ----------------- | ---------------------- | -------------------------- | ---------------------------------------------------------------------------------- |\n| 1009827 | 2016-03-22 | v2 | v0.9.4 | v0.9.4 | Allow only >= ringsize 3, blocktime = 120 seconds, fee-free blocksize 60 kb |\n| 1141317 | 2016-09-21 | v3 | v0.9.4 | v0.10.0 | Splits coinbase into denominations |\n| 1220516 | 2017-01-05 | v4 | v0.10.1 | v0.10.2.1 | Allow normal and RingCT transactions |\n| 1288616 | 2017-04-15 | v5 | v0.10.3.0 | v0.10.3.1 | Adjusted minimum blocksize and fee algorithm |\n| 1400000 | 2017-09-16 | v6 | v0.11.0.0 | v0.11.0.0 | Allow only RingCT transactions, allow only >= ringsize 5 |\n| 1546000 | 2018-04-06 | v7 | v0.12.0.0 | v0.12.0.0 | Cryptonight variant 1, ringsize >= 7, sorted inputs\n| XXXXXXX | 2018-10-XX | XX | XXXXXXXXX | XXXXXXXXX | X\n\nX's indicate that these details have not been determined as of commit date.\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## Installing Monero from a package\n\nPackages are available for\n\n* Ubuntu and [snap supported](https://snapcraft.io/docs/core/install) systems, via a community contributed build.\n\n snap install monero --beta\n\nInstalling a snap is very quick. Snaps are secure. They are isolated with all of their dependencies. Snaps also auto update when a new version is released.\n\n* Arch Linux (via [AUR](https://aur.archlinux.org/)):\n - Stable release: [`monero`](https://aur.archlinux.org/packages/monero)\n - Bleeding edge: [`monero-git`](https://aur.archlinux.org/packages/monero-git)\n\n* Void Linux:\n\n xbps-install -S monero\n\n* GuixSD\n\n guix package -i monero\n\n* OS X via [Homebrew](http://brew.sh)\n\n brew tap sammy007/cryptonight\n brew install monero --build-from-source\n\n* Docker\n\n # Build using all available cores\n docker build -t monero .\n\n # or build using a specific number of cores (reduce RAM requirement)\n docker build --build-arg NPROC=1 -t monero .\n \n # either run in foreground\n docker run -it -v /monero/chain:/root/.bitmonero -v /monero/wallet:/wallet -p 18080:18080 monero\n\n # or in background\n docker run -it -d -v /monero/chain:/root/.bitmonero -v /monero/wallet:/wallet -p 18080:18080 monero\n\nPackaging for your favorite distribution would be a welcome contribution!\n\n## Compiling Monero 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 | Fedora | Optional | Purpose |\n| ------------ | ------------- | -------- | ------------------ | ------------ | ----------------- | -------- | -------------- |\n| GCC | 4.7.3 | NO | `build-essential` | `base-devel` | `gcc` | NO | |\n| CMake | 3.0.0 | NO | `cmake` | `cmake` | `cmake` | NO | |\n| pkg-config | any | NO | `pkg-config` | `base-devel` | `pkgconf` | NO | |\n| Boost | 1.58 | NO | `libboost-all-dev` | `boost` | `boost-devel` | NO | C++ libraries |\n| OpenSSL | basically any | NO | `libssl-dev` | `openssl` | `openssl-devel` | NO | sha256 sum |\n| libzmq | 3.0.0 | NO | `libzmq3-dev` | `zeromq` | `cppzmq-devel` | NO | ZeroMQ library |\n| libunbound | 1.4.16 | YES | `libunbound-dev` | `unbound` | `unbound-devel` | NO | DNS resolver |\n| libsodium | ? | NO | `libsodium-dev` | ? | `libsodium-devel` | NO | libsodium |\n| libminiupnpc | 2.0 | YES | `libminiupnpc-dev` | `miniupnpc` | `miniupnpc-devel` | YES | NAT punching |\n| libunwind | any | NO | `libunwind8-dev` | `libunwind` | `libunwind-devel` | YES | Stack traces |\n| liblzma | any | NO | `liblzma-dev` | `xz` | `xz-devel` | YES | For libunwind |\n| libreadline | 6.3.0 | NO | `libreadline6-dev` | `readline` | `readline-devel` | YES | Input editing |\n| ldns | 1.6.17 | NO | `libldns-dev` | `ldns` | `ldns-devel` | YES | SSL toolkit |\n| expat | 1.1 | NO | `libexpat1-dev` | `expat` | `expat-devel` | YES | XML parsing |\n| GTest | 1.5 | YES | `libgtest-dev`^ | `gtest` | `gtest-devel` | YES | Test suite |\n| Doxygen | any | NO | `doxygen` | `doxygen` | `doxygen` | YES | Documentation |\n| Graphviz | any | NO | `graphviz` | `graphviz` | `graphviz` | YES | Documentation |\n\n\n[^] 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 && cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv libg* /usr/lib/ ```\n\n### Cloning the repository\n\nClone recursively to pull-in needed submodule(s):\n\n`$ git clone --recursive https://github.com/monero-project/monero`\n\nIf you already have a repo cloned, initialize and update:\n\n`$ cd monero && git submodule init && git submodule update`\n\n### Build instructions\n\nMonero uses the CMake build system and a top-level [Makefile](Makefile) that\ninvokes cmake commands as needed.\n\n#### On Linux and OS X\n\n* Install the dependencies\n* Change to the root of the source code directory and build:\n\n cd monero\n make\n\n *Optional*: If your machine has several cores and enough memory, enable\n parallel build by running `make -j` 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*: If cmake can not find zmq.hpp file on OS X, installing `zmq.hpp` from\n https://github.com/zeromq/cppzmq to `/usr/local/include` should fix that error.\n\n* The resulting executables can be found in `build/release/bin`\n\n* Add `PATH=\"$PATH:$HOME/monero/build/release/bin\"` to `.profile`\n\n* Run Monero with `monerod --detach`\n\n* **Optional**: build and run the test suite to verify the binaries:\n\n make release-test\n\n *NOTE*: `core_tests` test may take a few hours to complete.\n\n* **Optional**: to build binaries suitable for debugging:\n\n make debug\n\n* **Optional**: to build statically-linked binaries:\n\n make release-static\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 HAVE_DOT=YES doxygen Doxyfile\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) from https://www.raspberrypi.org/downloads/raspbian/. If you are using Raspian Jessie, [please see note in the following section](#note-for-raspbian-jessie-users). \n\n* `apt-get update && apt-get upgrade` to install all of the latest software\n\n* Install the dependencies for Monero from the 'Debian' column in the table above.\n\n* Increase the system swap size:\n```\t\n\tsudo /etc/init.d/dphys-swapfile stop \n\tsudo nano /etc/dphys-swapfile \n\tCONF_SWAPSIZE=1024 \n\tsudo /etc/init.d/dphys-swapfile start \n```\n* Clone monero and checkout most recent release version:\n```\n git clone https://github.com/monero-project/monero.git\n\tcd monero\n\tgit checkout tags/v0.11.1.0\n```\n* Build:\n```\n make release\n```\n* Wait 4-6 hours\n\n* The resulting executables can be found in `build/release/bin`\n\n* Add `PATH=\"$PATH:$HOME/monero/build/release/bin\"` to `.profile`\n\n* Run Monero with `monerod --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 Monero is a bit more complicated. The version of Boost available in the Debian Jessie repositories is too old to use with Monero, 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 && apt-get upgrade` to install all of the latest software, and increase the system swap size\n\n```\t\n\tsudo /etc/init.d/dphys-swapfile stop \n\tsudo nano /etc/dphys-swapfile \n\tCONF_SWAPSIZE=1024 \n\tsudo /etc/init.d/dphys-swapfile start \n```\n\n* Then, install the dependencies for Monero except `libunwind` and `libboost-all-dev`\n\n* Install the latest version of boost (this may first require invoking `apt-get remove --purge libboost*` to remove a previous version if you're not using a clean install):\n```\n\tcd \n\twget https://sourceforge.net/projects/boost/files/boost/1.64.0/boost_1_64_0.tar.bz2 \n\ttar xvfo boost_1_64_0.tar.bz2 \n\tcd boost_1_64_0 \n\t./bootstrap.sh \n\tsudo ./b2 \n```\n* Wait ~8 hours\n```\n\tsudo ./bjam install\n```\n* Wait ~4 hours\n\n* From here, follow the [general Raspberry Pi instructions](#on-the-raspberry-pi) from the \"Clone monero 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](http://msys2.github.io). 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](http://msys2.github.io), 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 pacman -Syuu \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 pacman -Syuu \n\n\n* Install dependencies:\n\n To build for 64-bit Windows:\n\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\n\n To build for 32-bit Windows:\n \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\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**Building**\n\n* If you are on a 64-bit system, run:\n\n make release-static-win64\n\n* If you are on a 32-bit system, run:\n\n make release-static-win32\n\n* The resulting executables can be found in `build/release/bin`\n\n### On FreeBSD:\n\nThe project can be built from scratch by following instructions for Linux above. If you are running monero in a jail you need to add the flag: `allow.sysvipc=1` to your jail configuration, otherwise lmdb will throw the error message: `Failed to open lmdb environment: Function not implemented`.\n\nWe expect to add Monero into the ports tree in the near future, which will aid in managing installations using ports or packages.\n\n### On OpenBSD:\n\n#### OpenBSD < 6.2\n\nThis has been tested on OpenBSD 5.8.\n\nYou will need to add a few packages to your system. `pkg_add db cmake gcc gcc-libs g++ miniupnpc gtest`.\n\nThe doxygen and graphviz packages are optional and require the xbase set.\n\nThe Boost package has a bug that will prevent librpc.a from building correctly. In order to fix this, you will have to Build boost yourself from scratch. Follow the directions here (under \"Building Boost\"):\nhttps://github.com/bitcoin/bitcoin/blob/master/doc/build-openbsd.md\n\nYou will have to add the serialization, date_time, and regex modules to Boost when building as they are needed by Monero.\n\nTo build: `env CC=egcc CXX=eg++ CPP=ecpp DEVELOPER_LOCAL_TOOLS=1 BOOST_ROOT=/path/to/the/boost/you/built make release-static-64`\n\n#### OpenBSD >= 6.2\n\nYou will need to add a few packages to your system. `pkg_add cmake miniupnpc zeromq libiconv`.\n\nThe doxygen and graphviz packages are optional and require the xbase set.\n\n\nBuild the Boost library using clang. This guide is derived from: https://github.com/bitcoin/bitcoin/blob/master/doc/build-openbsd.md\n\nWe assume you are compiling with a non-root user and you have `doas` enabled.\n\nNote: do not use the boost package provided by OpenBSD, as we are installing boost to `/usr/local`.\n\n```\n# Create boost building directory\nmkdir ~/boost\ncd ~/boost\n\n# Fetch boost source\nftp -o boost_1_64_0.tar.bz2 https://netcologne.dl.sourceforge.net/project/boost/boost/1.64.0/boost_1_64_0.tar.bz2 \n\n# MUST output: (SHA256) boost_1_64_0.tar.bz2: OK\necho \"7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0.tar.bz2\" | sha256 -c\ntar xfj boost_1_64_0.tar.bz2\n\n# Fetch and apply boost patches, required for OpenBSD\nftp -o boost_test_impl_execution_monitor_ipp.patch https://raw.githubusercontent.com/openbsd/ports/bee9e6df517077a7269ff0dfd57995f5c6a10379/devel/boost/patches/patch-boost_test_impl_execution_monitor_ipp\nftp -o boost_config_platform_bsd_hpp.patch https://raw.githubusercontent.com/openbsd/ports/90658284fb786f5a60dd9d6e8d14500c167bdaa0/devel/boost/patches/patch-boost_config_platform_bsd_hpp\n\n# MUST output: (SHA256) boost_config_platform_bsd_hpp.patch: OK\necho \"1f5e59d1154f16ee1e0cc169395f30d5e7d22a5bd9f86358f738b0ccaea5e51d boost_config_platform_bsd_hpp.patch\" | sha256 -c\n# MUST output: (SHA256) boost_test_impl_execution_monitor_ipp.patch: OK\necho \"30cec182a1437d40c3e0bd9a866ab5ddc1400a56185b7e671bb3782634ed0206 boost_test_impl_execution_monitor_ipp.patch\" | sha256 -c\n\ncd boost_1_64_0\npatch -p0 < ../boost_test_impl_execution_monitor_ipp.patch\npatch -p0 < ../boost_config_platform_bsd_hpp.patch\n\n# Start building boost\necho 'using clang : : c++ : \"-fvisibility=hidden -fPIC\" \"\" \"ar\" \"strip\" \"ranlib\" \"\" : ;' > user-config.jam\n./bootstrap.sh --without-icu --with-libraries=chrono,filesystem,program_options,system,thread,test,da","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",1299814788,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},"content_type","creator",2602191,"full_size",85245733,"id",20614310,"images",[101],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},"architecture","amd64","digest","sha256:530d47fb61c5446573ad6748c1737c522153c4890718fc7b93c6f3eb27e283c7","features","","last_pulled","2026-10-01T10:06:56.185416802Z","last_pushed","2018-06-10T20:55:30Z","os","linux","os_features","os_version","size","variant","2018-06-10T20:55:29.59949Z","last_updater","last_updater_username","media_type","latest","repository",3482898,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":142,"_149":150,"_136":159,"_160":11},{"_40":143,"_42":144,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":145,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":146,"_79":21,"_80":148,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":147},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_151":64,"_152":-5,"_153":-5,"_154":155},"count","next","previous","results",[156],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":157,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},[158],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},[],"canDeleteTags","actionData","errors"]

aeonpocket/rpc

Tags for aeonpocket/rpc