Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • monero-project/monero-site
  • moneromooo-monero/monero-site
  • el00ruobuob/monero-site
  • erciccione/monero-site
  • woodser/monero-site
  • m2049r/monero-site
  • JohnnyMnemonic/monero-site
  • rehrar/monero-site
  • selsta/monero-site
  • mycryptocheckout/monero-site
  • antanst/monero-site
  • leon/monero-site
  • BlackLotus64/monero-site
  • lh1008/monero-site
  • MSavoritias/monero-site
  • Ehhoe/monero-site
  • turossztrapacska/monero-site
  • anonimal/monero-site
  • dsc/monero-site
  • IsthmusCrypto/monero-site
  • rbrunner7/monero-site
  • Degreel/monero-site
  • Kyritheous/monero-site
  • ProkhorZ/monero-site
  • Monero_Helper/monero-site
  • ulineto/monero-site
  • xjmzx/monero-site
  • vp11/monero-site
  • sawinyh/monero-site
  • chadyo/monero-site
  • XMRNoblesse/monero-site
  • bartvk/monero-site
  • dginovker/monero-site
  • rodolfo912/monero-site
  • Mitchellpkt/monero-site
  • Needmoney90/monero-site
  • ndorf/monero-site
  • Cactii1/monero-site
  • xeagu/monero-site
  • ngecoin01/monero-site
  • ninezero-tr.com/monero-site
  • janowitz/monero-site
  • Aurora/monero-site
  • Lafudoci/monero-site
  • hrumag/monero-site
  • xmr-romine/monero-site
  • hooftly/monero-site
  • binaryFate/monero-site
  • LocalCoinIS/monero-site
  • timetherewere/monero-site
  • serhack/monero-site
  • hyc/monero-site
  • jonathancross/monero-site
  • monerobby/monero-site
  • Wegerich/monero-site
  • matilde/monero-site
  • koe/monero-site
  • TheFuzzStone/monero-site
  • lalanza808/monero-site
  • sgp/monero-site
  • Rexi/monero-site
  • Monero-Weblate/monero-site
  • Avis/monero-site
  • emes/monero-site
  • xiphon/monero-site
  • omurad/monero-site
  • MoneroArbo/monero-site
  • dianacraig/monero-site
  • beeroliver/monero-site
  • ngulgowski/monero-site
  • getsmile/monero-site
71 results
Show changes
Commits on Source (1627)
Showing with 1000 additions and 431 deletions
ietemplates/
_site/*
.idea/
*.swp
image: ruby:2.5
stages:
- build
variables:
LANG: "C.UTF-8"
before_script:
- gem install bundler
build_site:
stage: build
only:
- master
script:
- bundle install
- bundle exec jekyll build
#### What's the name of your business?
<!-- Write here -->
#### What's the URL of the website?
<!-- Write here. Referral links and/or trackers are not accepted -->
#### Write a brief description of your business/service (max 50 characters)
<!-- Write here. This text will be displayed on the Merchant page. Keep it short -->
#### Enter the URL where a Monero mention can be found
<!-- Be aware of the fact that to be listed, you must specify somewhere on your website that you accept Monero. -->
https://
#### How do you accept Monero? *(choose only one option)*
- [ ] Monero integrations *(github.com/monero-integrations)*
- [ ] Globee
- [ ] Native wallet
- [ ] Other payment gateaway (Coinpayments, Morphtoken, etc. *Please specify*)
#### How would you categorize your business? *(choose only one option)*
- [ ] Exchange
- [ ] Block Explorer
- [ ] Payment Gateway
- [ ] Library and Helper
- [ ] Tool
- [ ] Service
- [ ] Goods
- [ ] Entertainment
#### Comment
<!-- Write here any additional comment -->
2.4.1
......@@ -15,7 +15,7 @@ title: "Error 404, Page Not Found"
<div class="top-left">
<div class="not-found-text">
<h1 class="not-found-text">Oh no, we couldn't find anything for that link!</h1>
<h1 class="not-found-text">Oh no! We couldn't find anything for that link!</h1>
</div>
</div>
......
# General Guidelines
- Commits should be [atomic](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_commit_convention) and diffs should be easy to read. Please try to not mix formatting fixes with non-formatting commits
- The body of the pull request should:
* contain an accurate description of what the patch does
* provide justification/reasoning for the patch (when appropriate)
* include references to any discussions such as other tickets or chats on IRC
- If a particular commit references another issue, please add a reference. For example "See #123", or "Fixes #123". This will help us resolve tickets when we merge into `master`
# [Code of Conduct (22/C4.1)](http://rfc.zeromq.org/spec:22)
## License
Copyright (c) 2009-2015 Pieter Hintjens.
This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This Specification is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see <http://www.gnu.org/licenses>.
## Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
## Goals
C4 is meant to provide a reusable optimal collaboration model for open source software projects. It has these specific goals:
- To maximize the scale and diversity of the community around a project, by reducing the friction for new Contributors and creating a scaled participation model with strong positive feedbacks;
- To relieve dependencies on key individuals by separating different skill sets so that there is a larger pool of competence in any required domain;
- To allow the project to develop faster and more accurately, by increasing the diversity of the decision making process;
- To support the natural life cycle of project versions from experimental through to stable, by allowing safe experimentation, rapid failure, and isolation of stable code;
- To reduce the internal complexity of project repositories, thus making it easier for Contributors to participate and reducing the scope for error;
- To enforce collective ownership of the project, which increases economic incentive to Contributors and reduces the risk of hijack by hostile entities.
## Design
### Preliminaries
- The project SHALL use the git distributed revision control system.
- The project SHALL be hosted on github.com or equivalent, herein called the "Platform".
- The project SHALL use the Platform issue tracker.
- The project SHOULD have clearly documented guidelines for code style.
- A "Contributor" is a person who wishes to provide a patch, being a set of commits that solve some clearly identified problem.
- A "Maintainer" is a person who merges patches to the project. Maintainers are not developers; their job is to enforce process.
- Contributors SHALL NOT have commit access to the repository unless they are also Maintainers.
- Maintainers SHALL have commit access to the repository.
- Everyone, without distinction or discrimination, SHALL have an equal right to become a Contributor under the terms of this contract.
### Licensing and Ownership
- The project SHALL use a share-alike license, such as the GPLv3 or a variant thereof (LGPL, AGPL), or the MPLv2.
- All contributions to the project source code ("patches") SHALL use the same license as the project.
- All patches are owned by their authors. There SHALL NOT be any copyright assignment process.
- The copyrights in the project SHALL be owned collectively by all its Contributors.
- Each Contributor SHALL be responsible for identifying themselves in the project Contributor list.
### Patch Requirements
- Maintainers and Contributors MUST have a Platform account and SHOULD use their real names or a well-known alias.
- A patch SHOULD be a minimal and accurate answer to exactly one identified and agreed problem.
- A patch MUST adhere to the code style guidelines of the project if these are defined.
- A patch MUST adhere to the "Evolution of Public Contracts" guidelines defined below.
- A patch SHALL NOT include non-trivial code from other projects unless the Contributor is the original author of that code.
- A patch MUST compile cleanly and pass project self-tests on at least the principle target platform.
- A patch commit message SHOULD consist of a single short (less than 50 character) line summarizing the change, optionally followed by a blank line and then a more thorough description.
- A "Correct Patch" is one that satisfies the above requirements.
### Development Process
- Change on the project SHALL be governed by the pattern of accurately identifying problems and applying minimal, accurate solutions to these problems.
- To request changes, a user SHOULD log an issue on the project Platform issue tracker.
- The user or Contributor SHOULD write the issue by describing the problem they face or observe.
- The user or Contributor SHOULD seek consensus on the accuracy of their observation, and the value of solving the problem.
- Users SHALL NOT log feature requests, ideas, suggestions, or any solutions to problems that are not explicitly documented and provable.
- Thus, the release history of the project SHALL be a list of meaningful issues logged and solved.
- To work on an issue, a Contributor SHALL fork the project repository and then work on their forked repository.
- To submit a patch, a Contributor SHALL create a Platform pull request back to the project.
- A Contributor SHALL NOT commit changes directly to the project.
- If the Platform implements pull requests as issues, a Contributor MAY directly send a pull request without logging a separate issue.
- To discuss a patch, people MAY comment on the Platform pull request, on the commit, or elsewhere.
- To accept or reject a patch, a Maintainer SHALL use the Platform interface.
- Maintainers SHOULD NOT merge their own patches except in exceptional cases, such as non-responsiveness from other Maintainers for an extended period (more than 1-2 days).
- Maintainers SHALL NOT make value judgments on correct patches.
- Maintainers SHALL merge correct patches from other Contributors rapidly.
- The Contributor MAY tag an issue as "Ready" after making a pull request for the issue.
- The user who created an issue SHOULD close the issue after checking the patch is successful.
- Maintainers SHOULD ask for improvements to incorrect patches and SHOULD reject incorrect patches if the Contributor does not respond constructively.
- Any Contributor who has value judgments on a correct patch SHOULD express these via their own patches.
- Maintainers MAY commit changes to non-source documentation directly to the project.
### Creating Stable Releases
- The project SHALL have one branch ("master") that always holds the latest in-progress version and SHOULD always build.
- The project SHALL NOT use topic branches for any reason. Personal forks MAY use topic branches.
- To make a stable release someone SHALL fork the repository by copying it and thus become maintainer of this repository.
- Forking a project for stabilization MAY be done unilaterally and without agreement of project maintainers.
- A stabilization project SHOULD be maintained by the same process as the main project.
- A patch to a stabilization project declared "stable" SHALL be accompanied by a reproducible test case.
### Evolution of Public Contracts
- All Public Contracts (APIs or protocols) SHALL be documented.
- All Public Contracts SHOULD have space for extensibility and experimentation.
- A patch that modifies a stable Public Contract SHOULD not break existing applications unless there is overriding consensus on the value of doing this.
- A patch that introduces new features to a Public Contract SHOULD do so using new names.
- Old names SHOULD be deprecated in a systematic fashion by marking new names as "experimental" until they are stable, then marking the old names as "deprecated".
- When sufficient time has passed, old deprecated names SHOULD be marked "legacy" and eventually removed.
- Old names SHALL NOT be reused by new features.
- When old names are removed, their implementations MUST provoke an exception (assertion) if used by applications.
### Project Administration
- The project founders SHALL act as Administrators to manage the set of project Maintainers.
- The Administrators SHALL ensure their own succession over time by promoting the most effective Maintainers.
- A new Contributor who makes a correct patch SHALL be invited to become a Maintainer.
- Administrators MAY remove Maintainers who are inactive for an extended period of time, or who repeatedly fail to apply this process accurately.
- Administrators SHOULD block or ban "bad actors" who cause stress and pain to others in the project. This should be done after public discussion, with a chance for all parties to speak. A bad actor is someone who repeatedly ignores the rules and culture of the project, who is needlessly argumentative or hostile, or who is offensive, and who is unable to self-correct their behavior when asked to do so by others.
# Addendum to [Code of Conduct (22/C4.1)](http://rfc.zeromq.org/spec:22)
## License
Copyright (c) 2017 The Monero Project
## Language
The "Monero Site Maintainer Team" is defined in this document as the following users:
- fluffypony
- anonimal
### Development Process
- Maintainers MUST NOT merge pull requests in less than 168 hours (1 week) unless deemed urgent by the Monero Site Maintainer Team
source 'https://rubygems.org'
gem 'jekyll'
gem 'jekyll-paginate'
gem 'builder'
gem 'rubysl-rexml'
gem 'wdm', '>= 0.1.0' if Gem.win_platform?
gem 'jekyll-multiple-languages-plugin'
GEM
remote: https://rubygems.org/
specs:
addressable (2.7.0)
public_suffix (>= 2.0.2, < 5.0)
builder (3.2.3)
colorator (1.1.0)
concurrent-ruby (1.1.5)
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
eventmachine (1.2.7)
ffi (1.11.3)
forwardable-extended (2.6.0)
http_parser.rb (0.6.0)
i18n (0.9.5)
concurrent-ruby (~> 1.0)
jekyll (3.8.6)
addressable (~> 2.4)
colorator (~> 1.0)
em-websocket (~> 0.5)
i18n (~> 0.7)
jekyll-sass-converter (~> 1.0)
jekyll-watch (~> 2.0)
kramdown (~> 1.14)
liquid (~> 4.0)
mercenary (~> 0.3.3)
pathutil (~> 0.9)
rouge (>= 1.7, < 4)
safe_yaml (~> 1.0)
jekyll-multiple-languages-plugin (1.5.1)
jekyll (>= 2.0, < 4.0)
jekyll-paginate (1.1.0)
jekyll-sass-converter (1.5.2)
sass (~> 3.4)
jekyll-watch (2.2.1)
listen (~> 3.0)
kramdown (1.17.0)
liquid (4.0.3)
listen (3.2.1)
rb-fsevent (~> 0.10, >= 0.10.3)
rb-inotify (~> 0.9, >= 0.9.10)
mercenary (0.3.6)
pathutil (0.16.2)
forwardable-extended (~> 2.6)
public_suffix (4.0.1)
rb-fsevent (0.10.3)
rb-inotify (0.10.0)
ffi (~> 1.0)
rouge (3.14.0)
rubysl-rexml (2.0.4)
safe_yaml (1.0.5)
sass (3.7.4)
sass-listen (~> 4.0.0)
sass-listen (4.0.0)
rb-fsevent (~> 0.9, >= 0.9.4)
rb-inotify (~> 0.9, >= 0.9.7)
PLATFORMS
ruby
DEPENDENCIES
builder
jekyll
jekyll-multiple-languages-plugin
jekyll-paginate
rubysl-rexml
BUNDLED WITH
1.17.3
Copyright (c) 2014-2020, The Monero Project
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This diff is collapsed.
......@@ -2,7 +2,7 @@ email: dev@getmonero.org
name: Monero
description: Monero is a digital currency that is secure, private, and untraceable.
keywords: "monero, xmr, bitmonero, cryptocurrency"
baseurl: ""
baseurl: "https://getmonero.org"
url: "https://getmonero.org"
markdown: kramdown
......@@ -13,11 +13,24 @@ kramdown:
smart_quotes: ["apos", "apos", "quot", "quot"]
input: GFM
exclude: ["README.md"]
gems: [jekyll-paginate]
exclude: ["README.md", "CONTRIBUTING.md", "LICENSE"]
# paginate
paginate: 10
paginate_path: blog/page:num/
plugins:
- jekyll-paginate
- jekyll-multiple-languages-plugin
# jekyll-multiple-languages-plugin settings:
languages: ["en", "es", "it", "pl", "fr", "ar", "ru", "de", "nl", "pt-br", "tr", "zh-cn", "zh-tw"]
exclude_from_localizations: ["img", "css", "fonts", "media", "404", "feed.xml", "404", "meta", "forum-funding-system", "_posts", "legal", "blog"]
# Windows live tiles config
ie_tile_color: eeeeee
ie_tile_small: https://static.getmonero.org/images/live-tiles/small.png
......@@ -35,4 +48,4 @@ sitemap:
- "/ietemplates/poll4.xml"
- "/ietemplates/poll5.xml"
- "/feed.xml"
- "/404/index.md"
\ No newline at end of file
- "/404/index.md"
# This is included as an example of a config file that works for the site. This is important so that anyone can re-host it in the event of something going wrong with the main site.
# The main takeaways from this config file are the redirects, everything is relatively bog standard.
server {
listen 80;
# Specify this vhost's domain name
server_name dlsrc.getmonero.org downloads.getmonero.orgdlsrc.monero.mu downloads.monero.mu downloads.monero.cc;
return 301 https://$server_name$request_uri;
}
server {
listen 80;
listen 443 ssl http2;
......@@ -13,7 +20,7 @@ server {
ssl_prefer_server_ciphers on;
# Specify this vhost's domain name
server_name updates.getmonero.org downloads.getmonero.org downloads.monero.cc;
server_name updates.getmonero.org dlsrc.getmonero.org downloads.getmonero.org updates.monero.mu dlsrc.monero.mu downloads.monero.mu downloads.monero.cc;
root /var/www/downloads.getmonero.org/webroot;
index index.php index.html index.htm;
......@@ -57,56 +64,56 @@ server {
# Downloads!
location /win64 {
rewrite ^ /cli/monero-win-x64-v0.10.3.1.zip redirect;
rewrite ^ /cli/monero-win-x64-v0.13.0.2.zip redirect;
}
location /win32 {
rewrite ^ /cli/monero-win-x86-v0.10.3.1.zip redirect;
rewrite ^ /cli/monero-win-x86-v0.13.0.2.zip redirect;
}
location /mac64 {
rewrite ^ /cli/monero-mac-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-mac-x64-v0.13.0.2.tar.bz2 redirect;
}
location /linux64 {
rewrite ^ /cli/monero-linux-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-linux-x64-v0.13.0.2.tar.bz2 redirect;
}
location /linux32 {
rewrite ^ /cli/monero-linux-x86-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-linux-x86-v0.13.0.2.tar.bz2 redirect;
}
location /linuxarm7 {
rewrite ^ /cli/monero-linux-armv7-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-linux-armv7-v0.13.0.2.tar.bz2 redirect;
}
location /linuxarm8 {
rewrite ^ /cli/monero-linux-armv8-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-linux-armv8-v0.13.0.2.tar.bz2 redirect;
}
location /freebsd64 {
rewrite ^ /cli/monero-freebsd-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-freebsd-x64-v0.13.0.2.tar.bz2 redirect;
}
location /dragonflybsd64 {
rewrite ^ /cli/monero-dragonflybsd-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /cli/monero-dragonflybsd-x64-v0.13.0.2.tar.bz2 redirect;
}
# GUI downloads
location /gui/win64 {
rewrite ^ /gui/monero-win-x64-v0.10.3.1.zip redirect;
rewrite ^ /gui/monero-gui-win-x64-v0.13.0.2.zip redirect;
}
location /gui/mac64 {
rewrite ^ /gui/monero-mac-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /gui/monero-gui-mac-x64-v0.13.0.2.tar.bz2 redirect;
}
location /gui/linux64 {
rewrite ^ /gui/monero-linux-x64-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /gui/monero-gui-linux-x64-v0.13.0.2.tar.bz2 redirect;
}
location /gui/linux32 {
rewrite ^ /gui/monero-linux-x86-v0.10.3.1.tar.bz2 redirect;
rewrite ^ /gui/monero-gui-linux-x86-v0.13.0.2.tar.bz2 redirect;
}
# Other download redirects
......@@ -221,8 +228,15 @@ server {
location / {
try_files $uri $uri/ $uri.php $uri.htm $uri.html =404;
index index.html index.htm index.php;
# post_action @download_complete;
}
# location @download_complete {
# resolver 8.8.8.8;
# proxy_pass http://statcounter.monero.cc/stat_counter.php?zz=yy&status=$request_completion&uri=$uri&remote_addr=$remote_addr&http_x_forwarded_for=$http_x_forwarded_for&body_bytes_sent=$body_bytes_sent&request_time=$request_time&scheme=$scheme&server_name=$server_name&http_user_agent=$http_user_agent;
# internal;
# }
# Block for processing PHP files
# Specifically matches URIs ending in .php
location ~ \.php$ {
......@@ -240,4 +254,4 @@ server {
fastcgi_pass phpfpm;
}
}
}
\ No newline at end of file
- platform: Windows, 64-bit
id: windows
icon: icon-windows
cli_url: win64
cli_hash: 2fbda6f6b1051053703e40cf77b6c6e11334509ad03a3c22d89b6bcb05615910
gui_url: win64
gui_hash: 0eddd423f5f0df236303d8b9225842142b331093eb69e6183f3f694238c371a7
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: win
gui:
- version: "0.15.0.4 - Carbon Chamaeleon"
downloads:
- platform: Windows 64-bit (Installer)
hash: 874ebbfcf79d09c60e2d85d09e5b8b971066c6355dfc2a5eca6d109d32e45ddb
link: https://downloads.getmonero.org/gui/win64install
icon: icon-windows
vers:
- platform: Windows 64-bit (Zip)
hash: 9b61fa807c66ebe3010869d1fa926fe033a2c82e6e660ca8acb75a8fba0248a0
link: https://downloads.getmonero.org/gui/win64
icon: icon-windows
vers:
- platform: Mac OS X 64-bit
hash: 9b0164cd90345c5fd4014a6bc8258465c2e5aae7c527c7f64a2d795830db7ae4
link: https://downloads.getmonero.org/gui/mac64
icon: icon-apple
vers:
- platform: Linux 64-bit
hash: 2d105c792b46ec03739d39aaa6db3801f268e074814ab26e3824435f954c6a1c
link: https://downloads.getmonero.org/gui/linux64
icon: icon-linux
vers:
- platform: Source Code
link: https://github.com/monero-project/monero-gui
icon: icon-github
- platform: Windows, 32-bit
icon: icon-windows
cli_url: win32
cli_hash: da628a45adfcb8be44df06ac904711d644d608c4eb6479a5d256062a5f6d74de
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: win
- platform: Mac OS X, 64-bit
id: mac
icon: icon-apple
cli_url: mac64
cli_hash: fd17d55a8c9e901ff4064c39d9e14786cdd077aff9b3bb556e60d3a5e322050c
gui_url: mac64
gui_hash: c80ca68037158216a080e59e90b0a70761cff2f317d3c9cd0eeb661e8e2a1f99
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: mac
- platform: Linux, 64-bit
id: linux
icon: icon-linux
cli_url: linux64
cli_hash: 8db80f8cc4f80d4106db807432828df730a59eac78972ea81652aa6b9bac04ad
gui_url: linux64
gui_hash: 4915473265d58720fd8f019e536c2b7fb02648ab51a8087e84aa1e2434788452
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: linux
- platform: Linux, 32-bit
icon: icon-linux
cli_url: linux32
cli_hash: abc99f3928f4083bd1a380a869253e07bee9950e0aeb6388e9493bc0f0ec3f53
gui_url: linux32
gui_hash: 092b49080c3380666845f7f39823b09f4960ea1e250b84b150856ef33ca30690
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: linux
- platform: ARMv7
id: arm
icon: icon-arm
cli_url: linuxarm7
cli_hash: 8473fa20e0db4a3d3e46120cdf92c55be6a159478c511e21f7b77aa05d6c1910
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: arm
- platform: ARMv8
icon: icon-arm
cli_url: linuxarm8
cli_hash: 451f65e4846b92d54859e22a5d92124557b397b4208d8752d5289d0262573c3c
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: arm
- platform: FreeBSD, 64-bit
id: bsd
icon: icon-freebsd
cli_url: freebsd64
cli_hash: 4c66a76752e18ae70b5fb1c728f0d2780eb129a6c8c7d0dee7ba02e05d91efae
version: 0.10.3.1
tag: Wolfram Warptangent
blockchain: freebsd
- platform: Source Code & Blockchain
id: source
icon: icon-github
cli_url: https://github.com/monero-project/bitmonero
cli_hash: source
version: Bleeding edge (possibly unstable)
- platform: Mobile & Light Wallets
id: mobilelight
- platform: Hardware Wallets
id: hardware
\ No newline at end of file
cli:
- version: "0.15.0.5 - Carbon Chamaeleon"
downloads:
- platform: Windows 64-bit
hash: 0286e21552d3fedfedbc7c7aba2f34c370ad4c21007a75fb67ac87994c5cec5a
link: https://downloads.getmonero.org/cli/win64
icon: icon-windows
vers:
- platform: Windows 32-bit
hash: bdcc5af964b6271bbf05609edfc49093b690f15031b748dfb43ffe991ae9cc6e
link: https://downloads.getmonero.org/cli/win32
icon: icon-windows
vers:
- platform: Mac OS X 64-bit
hash: 8ef04398350b8de68e21da236801f276cf662641e03dc067f6e865180f9853f6
link: https://downloads.getmonero.org/cli/mac64
icon: icon-apple
vers:
- platform: Linux 64-bit
hash: 6cae57cdfc89d85c612980c6a71a0483bbfc1b0f56bbb30e87e933e7ba6fc7e7
link: https://downloads.getmonero.org/cli/linux64
icon: icon-linux
vers:
- platform: Linux 32-bit
hash: fd2c32fc3efa47b2feda6526b0a2df4e1acc7325ec205a25d7947fbc843b24df
link: https://downloads.getmonero.org/cli/linux6432
icon: icon-linux
vers:
- platform: Linux ARMv8
hash: 04e73cf72f37f0bbdfa757c9bb5df2117aee473632a917041077da3c05169743
link: https://downloads.getmonero.org/cli/linuxarm8
icon: icon-linux
vers:
- platform: Linux ARMv7
hash: a23402ccf5ac432306fe263fae660646206ecb9d2aec3cfacb25afce34794067
link: https://downloads.getmonero.org/cli/linuxarm7
icon: icon-linux
vers:
- platform: Android ARMv8
hash: ceccc11723c4dff3cef420b37bc795850b74a8e71d23d44aa26faf5cd8fcc0e6
link: https://downloads.getmonero.org/cli/monero-android-armv8-v0.15.0.0.tar.bz2
icon: icon-android
vers:
- platform: Android ARMv7
hash: 52e46ead674275ed446e261795b2cde19e65f7098ce62902bfa275e67f9f10f7
link: https://downloads.getmonero.org/cli/monero-android-armv7-v0.15.0.0.tar.bz2
icon: icon-android
vers:
- platform: FreeBSD 64-bit
hash: b0ea91c4d0f68d8d85ba15ed537bdd81589fa796f88d96aec451543f87b9fdb7
link: https://downloads.getmonero.org/cli/freebsd64
icon: icon-freebsd
vers:
- event: Monero Meetup (Dublin, Ireland) - June 26th, 2017
where: J.W. Sweetman Craft Brewery, 1-2 Burgh Quay, Dublin 2, Dublin, Ireland
when: 7:00 PM - Monday, June 26, 2017
description: The meeting will cover the history of privacy and fungibility in Bitcoin, discuss several approaches to these problems, and explain how Monero achieves its privacy in detail. Justin will discuss the next steps in development going forward and the limitations compared to other coins. Finally, there will be a Q&A session after the meeting, where he can clear up some final thoughts.
link: https://www.meetup.com/Bitcoin-Dublin/events/240152422/
\ No newline at end of file
- stage: Ideas
proposals:
- name: Fake. Nothing here yet. Check WiP and Completed Proposals.
url: #
summary: This is for the best ideas ever!
author: rehrar
- stage: Open Tasks
proposals:
- name: Fake. Nothing here yet. Check WiP and Completed Proposals.
url: #
summary: This is for the best ideas ever!
author: rehrar
- stage: Funding Required
proposals:
- name: Monero Bounty For HackerOne
url: /forum-funding-system/proposals/monero-bounty-hackerone.html
summary: we need dedicated funds to satisfy bounty for Monero and all Monero sub-projects on hackerone.com/monero
author: anonimal
- stage: Work in Progress
proposals:
- name: Getmonero.org Redesign
url: /forum-funding-system/proposals/getmonero-redesign.html
summary: Redesign the official getmonero.org website to make it more accessible and aesthetically pleasing.
author: rehrar
- stage: Completed Proposals
proposals:
- name: What is Monero? is produced and open-sourced
url: /forum-funding-system/proposals/whatismonero-produced.html
summary: Make an introduction video to Monero.
author: savandra
\ No newline at end of file
- title: مصادر
subfolderitems:
- name: عن مونيرو
url: resources/about/
- name: مونيروبيديا
url: resources/moneropedia/
- name: دليل المُطور
url: resources/developer-guides/
- name: دليل المستخدم
url: resources/user-guides/
- name: RSS Feed
url: https://getmonero.org/feed.xml
- title: IRC قنوات الدردشة
subfolderitems:
- name: مونيرو
url: irc://chat.freenode.net/#monero
- name: مطور مونيرو
url: irc://chat.freenode.net/#monero-dev
- name: أسواق مونيرو
url: irc://chat.freenode.net/#monero-markets
- name: تعدين مونيرو
url: irc://chat.freenode.net/#monero-pools
- name: مجتمع مونيرو
url: irc://chat.freenode.net/#monero-community
- name: ترجمات مونيرو
url: irc://chat.freenode.net/#monero-translations
- name: مُعدات مونيرو
url: irc://chat.freenode.net/#monero-hardware
- title: المجتمع
subfolderitems:
- name: Reddit
url: https://reddit.com/r/monero
- name: Stack Exchange
url: https://monero.stackexchange.com/
- name: BitcoinTalk Thread
url: https://bitcointalk.org/index.php?topic=583449.0
- name: Mattermost Chat
url: https://mattermost.getmonero.org/
- name: Telegram Chat
url: https://telegram.me/bitmonero
- title: مشروع مونيرو
subfolderitems:
- name: Open Alias
url: https://openalias.org/
- name: مشروع كوفري
url: https://kovri.io/
- name: مختبر بحث مونيرو
url: resources/research-lab/
- name: عدّه الصّحافه لمونيرو
url: press-kit
- name: قانوني
url: legal
- name: شفره المصدر
url: https://repo.getmonero.org
- title: إبدأ
subfolderitems:
- page: ما هو مونيرو ؟
url: get-started/what-is-monero
- page: الإستخدام
url: get-started/using
- page: القبول
url: get-started/accepting
- page: المشاركه
url: get-started/contributing
- page: التعدين
url: get-started/mining
- page: الأسئله المتكرره
url: get-started/faq
- title: التنزيلات
url: downloads/
- title: آخر الأخبار
subfolderitems:
- page: Urgent
url: blog/tags/urgent.html
- page: الإصدارات
url: blog/tags/releases.html
- page: Community
url: blog/tags/community.html
- page: سجل الإجتماعات
url: blog/tags/dev%20diaries.html
- page: جميع المشاركات
url: blog
- title: المجتمع
subfolderitems:
- page: الفريق
url: community/team
- page: الملتقي
url: community/hangouts
- page: الرعاه
url: community/sponsorships
- page: التجار
url: community/merchants
- title: موارد
subfolderitems:
- page: عن مونيرو
url: resources/about
- page: خريطه الطريق
url: resources/roadmap
- page: مختبر البحث
url: resources/research-lab
- page: مونيروبيديا
url: resources/moneropedia
- page: دليل المستخدم
url: resources/user-guides
- page: دليل المُطور
url: resources/developer-guides
- page: المواصفات التقنيه
url: technical-specs
year_2014:
- month: April
completed:
- name: تم إنشاء المشروع علي Bitcointalk
- name: Renamed from Bitmonero to Monero
- month: September
completed:
- name: Recovered from a spam attack
- name: Monero Research Lab Papers 1 and 2 published
- name: Monero Research Lab Paper 3 published
- month: December
completed:
- name: 0.8.8.6 released
year_2015:
- month: January
completed:
- name: Monero Research Lab Paper 4 published
year_2016:
- month: January
completed:
- name: 0.9.0 Hydrogen Helix released
- month: February
completed:
- name: Monero Research Lab Paper 5 published
- month: March
completed:
- name: Network Upgrade to require minimum ringsize of 3 on all transactions
- month: September
completed:
- name: 0.10.0 Wolfram Warptangent released
- name: Network Upgrade to split coinbase into denominations
- month: December
completed:
- name: 0.10.1 Wolfram Warptangent released
- name: Official GUI Beta 1 released
year_2017:
- month: January
completed:
- name: Network Upgrade to enable RingCT transactions
- month: February
completed:
- name: 0.10.2 released; critical vulnerability patched
- month: March
completed:
- name: 0.10.3.1 Wolfram Warptangent released
- month: April
completed:
- name: Network Upgrade to adjust minimum blocksize and dynamic fee algorithm
- month: July
completed:
- name: Website redesigned
- month: September
completed:
- name: 0.11.0.0 Helium Hydra released
- name: Fluffy blocks
- name: GUI out of beta
- name: Network Upgrade to increase minimum ringsize to 5 and require RingCT transactions
- name: GUI 0.11.0.0 Helium Hydra released
- name: 0MQ/ZeroMQ
- month: October
completed:
- name: Subaddresses
- name: Monero Research Lab Paper 6 published
- name: 0.11.1.0 Helium Hydra released
- name: GUI 0.11.1.0 Helium Hydra released
- month: December
completed:
- name: Multi-signatures (multisig)
year_2018:
- month: March
completed:
- name: 0.12.0.0 Lithium Luna released
- month: April
completed:
- name: GUI 0.12.0.0 Lithium Luna released
- name: New Proof of Work CryptoNightV2
- name: Network upgrade to increase minimal ringsize to 7, integrate multisig, subaddresses, and change PoW algo
- name: Getmonero.org Localization in French and Polish
- month: May
completed:
- name: 0.12.1.0 Lithium Luna released
- month: June
completed:
- name: Ledger Hardware Wallets Support
- name: 0.12.2.0 Lithium Luna released
- month: July
completed:
- name: 0.12.3.0 Lithium Luna released
- name: GUI 0.12.3.0 Lithium Luna released
- month: August
completed:
- name: Kovri alpha release
- name: Getmonero.org Moneropedia open for Localization
- name: Getmonero.org Localization in Arabic
- month: October
completed:
- name: 0.13.0.2 Beryllium Bullet released
- name: GUI 0.13.0.3 Beryllium Bullet released
- name: New Proof of Work CryptoNightV3
- name: Implementation of Bulletproofs to reduce transaction sizes
- name: Network upgrade to increase minimal ringsize to 11, integrate Bulletproofs, update fees calculation algorithm, and change PoW algo
- name: 0.13.0.4 Beryllium Bullet released
- month: Nobember
completed:
- name: Monero Research Lab Papers 8 and 9 published
- name: GUI 0.13.0.4 Beryllium Bullet released
- name: Monero Research Lab Paper 7 published
- month: December
completed:
- name: Monero Research Lab Paper 10 published
- name: Implementation of Monero Messaging System (MMS) to automate multisig wallets information exchange
year_2019:
- month: February
completed:
- name: Getmonero.org Localization in German
- name: 0.14.0.0 Boron Butterfly released
- month: March
completed:
- name: GUI 0.14.0.0 Boron Butterfly released
- name: New Community Crowdfunding System (CCS) to replace the Forum Funding System (FFS)
- name: 0.14.0.2 Boron Butterfly released
- name: New Proof of Work CryptoNightR
- name: Getmonero.org Localization in Brazilian-Portuguese and Dutch
- month: May
completed:
- name: "DLSAG: Non-Interactive Refund Transactions For Interoperable Payment Channels in Monero"
- month: July
completed:
- name: Blockchain pruning
- name: Trezor model T support
- name: Ledger Nano X support
- name: Tor & I2P CLI wallet integration
- name: Multisig Messaging System
- month: October
completed:
- name: "Localization platform change: from Pootle to Weblate"
- month: November
completed:
- name: "Localization platform change: from Pootle to Weblate"
- name: Pay for service system using mining (RPC-Pay)
- name: IPv6 support
- name: Standalone (long) payment ID support removed
- name: GUI automatic remote nodes discovering and switching option
- name: New Proof of Work RandomX
year_2020:
- month: February
completed:
- name: Getmonero translatable on Weblate
- month: March
completed:
- name: GUI 0.15.0.4 released
- month: Coming Soon
ongoing:
- name: Onion address for Getmonero.org
- name: Implementation of the Dandelion++ protocol
- name: Wallet scanning speedups (support for supercop ASM)
- name: Concise linkable spontaneous anonymous group (CLSAG) signatures
- name: "Triptych: logarithmic-sized linkable ring signatures with applications"
- name: "Kastelo: open source hardware wallet"
upcoming:
- name: Second-layer solutions for speed and scalability
future:
- month: Coming Soon
upcoming:
- name: Return addresses
\ No newline at end of file
- title: Ressourcen
subfolderitems:
- name: Über Monero
url: resources/about/
- name: Moneropedia
url: resources/moneropedia/
- name: Anleitungen für Entwickler
url: resources/developer-guides/
- name: Anleitungen für Nutzer
url: resources/user-guides/
- name: Bibliothek
url: library
- name: RSS-Feed
url: https://getmonero.org/feed.xml
- title: IRC-Channels
subfolderitems:
- name: monero
url: irc://chat.freenode.net/#monero
- name: monero-dev
url: irc://chat.freenode.net/#monero-dev
- name: monero-markets
url: irc://chat.freenode.net/#monero-markets
- name: monero-pools
url: irc://chat.freenode.net/#monero-pools
- name: monero-community
url: irc://chat.freenode.net/#monero-community
- name: monero-translations
url: irc://chat.freenode.net/#monero-translations
- name: monero-hardware
url: irc://chat.freenode.net/#monero-hardware
- title: Community
subfolderitems:
- name: Reddit
url: https://reddit.com/r/monero
- name: Stack Exchange
url: https://monero.stackexchange.com/
- name: Thread auf BitcoinTalk
url: https://bitcointalk.org/index.php?topic=583449.0
- name: Mattermost-Chat
url: https://mattermost.getmonero.org/
- name: Telegram-Chat
url: https://telegram.me/bitmonero
- title: Das Monero-Projekt
subfolderitems:
- name: OpenAlias
url: https://openalias.org/
- name: Kovri
url: https://kovri.io/
- name: Monero Research Lab
url: resources/research-lab/
- name: Monero-Presseunterlagen
url: press-kit