mirror of
https://github.com/monero-project/monero-site.git
synced 2024-11-16 15:58:16 +00:00
repo: update web.getmonero.org to baseurl
This commit is contained in:
parent
a66e14d55d
commit
14729082e9
16 changed files with 19 additions and 19 deletions
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -13,4 +13,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -13,4 +13,4 @@ summary: "Функция, которая позволяет операторам
|
|||
|
||||
Обрезанные узлы довольно полезны, и в качестве @удалённых-узлов лучше использовать именно их, но, по возможности, пользователям рекомендуется создавать полные узлы и прибегать к обрезанию только в случае разумной необходимости.
|
||||
|
||||
Возможность 'обрезания базы данных' [добавлена](https://github.com/monero-project/monero/pull/4843) в январе 2019. Дополнительная информация содержится в соответствующем [посте](https://web.getmonero.org/2019/02/01/pruning.html).
|
||||
Возможность 'обрезания базы данных' [добавлена](https://github.com/monero-project/monero/pull/4843) в январе 2019. Дополнительная информация содержится в соответствующем [посте]({{ site.baseurl }}/2019/02/01/pruning.html).
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -14,4 +14,4 @@ There are three ways to prune:
|
|||
|
||||
Pruned nodes are very useful and preferable to @remote-nodes, but if possible, users should run a full node and opt for pruning only in case if necessary.
|
||||
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post](https://web.getmonero.org/2019/02/01/pruning.html) for more information.
|
||||
The 'database pruning' feature [was added](https://github.com/monero-project/monero/pull/4843) on January 2019. See the [blog post]({{ site.baseurl }}/2019/02/01/pruning.html) for more information.
|
||||
|
|
|
@ -11,7 +11,7 @@ author: ErCiccione
|
|||
|
||||
### Overview
|
||||
|
||||
This is the **v0.15.0 release of the Monero software**. This major release, announced in an [earlier post](https://web.getmonero.org/2019/10/01/announcement-release-0-15.html), is due to the November 30th network upgrade. Users, merchants and exchanges should update to the latest Monero software before that date. The binaries for the GUI wallet are forthcoming, we will make another announcement as soon as they are released.
|
||||
This is the **v0.15.0 release of the Monero software**. This major release, announced in an [earlier post]({{ site.baseurl }}/2019/10/01/announcement-release-0-15.html), is due to the November 30th network upgrade. Users, merchants and exchanges should update to the latest Monero software before that date. The binaries for the GUI wallet are forthcoming, we will make another announcement as soon as they are released.
|
||||
|
||||
Some of the major changes introduced with this release are:
|
||||
|
||||
|
@ -23,7 +23,7 @@ Some of the major changes introduced with this release are:
|
|||
- **Optional Tor/I2P** transaction relay for privacy (block relay being done on clearnet)
|
||||
- **New gen_ssl_cert tool** to generate SSL certificates suitable for Monero usage
|
||||
- **IPv6** support
|
||||
- **Removed Long Payment IDs** (see the [deprecation announcement](https://web.getmonero.org/2019/06/04/Long-Payment-ID-Deprecation.html))
|
||||
- **Removed Long Payment IDs** (see the [deprecation announcement]({{ site.baseurl }}/2019/06/04/Long-Payment-ID-Deprecation.html))
|
||||
|
||||
The complete list of features and changes is on GitHub: [github.com/monero-project/monero/releases/tag/v0.15.0.0](https://github.com/monero-project/monero/releases/tag/v0.15.0.0).
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ author: The Core Team
|
|||
|
||||
## Administration of the General Fund
|
||||
|
||||
The Core Team as a group has existed from the very early days of Monero, and its responsibilities have evolved over the years. For a write up of the responsibilities that the team considers itself responsible for nowadays (that is, trusted by the community to take care of), see https://web.getmonero.org/2018/03/01/core-team-announcement.html. These responsibilities tend to diminish as the project moves forward and some structures are changing; for instance, reproducible builds are a big step forward to provide binaries to the community without having to blindly trust any of us.
|
||||
The Core Team as a group has existed from the very early days of Monero, and its responsibilities have evolved over the years. For a write up of the responsibilities that the team considers itself responsible for nowadays (that is, trusted by the community to take care of), see {{ site.baseurl }}/2018/03/01/core-team-announcement.html. These responsibilities tend to diminish as the project moves forward and some structures are changing; for instance, reproducible builds are a big step forward to provide binaries to the community without having to blindly trust any of us.
|
||||
|
||||
A responsibility that remains fully in our hands is to administer and/or escrow financial donations to the project. In practice it means:
|
||||
|
||||
|
|
|
@ -365,14 +365,14 @@ Inputs:
|
|||
|
||||
* *address* - string; The address to validate.
|
||||
* *any_net_type* - boolean (Optional); If true, consider addresses belonging to any of the three Monero networks (mainnet, stagenet, and testnet) valid. Otherwise, only consider an address valid if it belongs to the network on which the rpc-wallet's current daemon is running (Defaults to false).
|
||||
* *allow_openalias* - boolean (Optional); If true, consider [OpenAlias-formatted addresses](https://web.getmonero.org/resources/moneropedia/openalias.html) valid (Defaults to false).
|
||||
* *allow_openalias* - boolean (Optional); If true, consider [OpenAlias-formatted addresses]({{ site.baseurl }}/resources/moneropedia/openalias.html) valid (Defaults to false).
|
||||
|
||||
Outputs:
|
||||
* *valid* - boolean; True if the input address is a valid Monero address.
|
||||
* *integrated* - boolean; True if the given address is an [integrated address](https://web.getmonero.org/resources/moneropedia/address.html).
|
||||
* *integrated* - boolean; True if the given address is an [integrated address]({{ site.baseurl }}/resources/moneropedia/address.html).
|
||||
* *subaddress* - boolean; True if the given address is a [subaddress](https://github.com/monero-project/monero/pull/2056)
|
||||
* *nettype* - string; Specifies which of the three Monero networks (mainnet, stagenet, and testnet) the address belongs to.
|
||||
* *openalias_address* - boolean; True if the address is [OpenAlias-formatted](https://web.getmonero.org/resources/moneropedia/openalias.html).
|
||||
* *openalias_address* - boolean; True if the address is [OpenAlias-formatted]({{ site.baseurl }}/resources/moneropedia/openalias.html).
|
||||
|
||||
Example:
|
||||
|
||||
|
|
Loading…
Reference in a new issue