amend: self-signed tls certificates changelog

This commit is contained in:
Binarybaron 2025-08-03 20:59:24 +02:00
parent 249fd25a3b
commit 1bfb4b7e8d

View file

@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
- GUI: The following rendezvous points have been added to the default list of rendezvous points. If you're running a maker, please add them to your config file (under `network.rendezvous_point`). They are operated by members of the community that have shown to be reliable. These rendezvous points act as bootstrapping nodes for peer discovery: `/dns4/eigen.center/tcp/8888/p2p/12D3KooWS5RaYJt4ANKMH4zczGVhNcw5W214e2DDYXnjs5Mx5zAT`, `/dns4/swapanarchy.cfd/tcp/8888/p2p/12D3KooWRtyVpmyvwzPYXuWyakFbRKhyXGrjhq6tP7RrBofpgQGp`, `/dns4/darkness.su/tcp/8888/p2p/12D3KooWFQAgVVS9t9UgL6v1sLprJVM7am5hFK7vy9iBCCoCBYmU`
- GUI + ASB + CLI: When using the "Monero RPC Pool" feature, we now accept self-signed TLS certificates. A lot of prominent community ran nodes use self-signed certificates. This'll be revisited once RPC-over-Tor is turned on by default. When specifying a custom node (without the RPC pool feature) we still require a valid certificate.
## [3.0.0-beta.3] - 2025-08-01