The translation is temporarily closed for contributions due to maintenance, please come back later.
Key English Serbian State
team->mpwg Monero Policy Working Group
team->mpwg_descr Monero Policy Working Group is a loosely formed quorum of individuals with an interest in interacting with regulators, policy makers, and the wider financial services sector to ensure broad understanding of Monero’s component technologies, especially with regards to its compatibility with evolving regulatory and compliance requirements.
team->mpwg_start If you would like to take part or follow policy discussions, join matrix/freenode chatroom.
downloads->releasenotes release notes
downloads->wallet Wallet
downloads->mobile Mobile
downloads->desktop Desktop
downloads->antivirus Antivirus
contributing->developp Monero is open source and permissionless; contributors are welcome and encouraged. A developer may contribute in numerous way to different projects:
contributing->cli CLI wallet and Daemon:
contributing->cli_p The core wallet, mostly written in C++.
contributing->gui GUI Wallet:
contributing->gui_p Mostly QML and C++.
contributing->website This website:
contributing->website_p Built with Jekyll. No Javascript.
contributing->bug Bug and vulnerability hunting: Monero is listed on Hackerone and developers are asked to responsibly disclose bugs and vulnerabilities. See
contributing->discl The Monero Project Vulnerability Response Process.
contributing->develop_descr This list only includes the tools stewarded by the core team, but the Monero ecosystem is much more vast. People can contribute to the development of libraries, services, documentation, graphics, etc. The list is virtually infinite. Contact or join the workgroup more affine to your way of contributing.
contributing->develop_wg See the Monero Workgroups.
contributing->full-node_p An easy and effective way to help the Monero network is to run a @node. Nodes ensure the network keeps running safe and decentralized. A simple fully synchronized node is enough to help the network, but if you want to go out of your way, you could run an open @remote-node, to allow other people to connect to it.