mirror of
https://github.com/Cyrix126/gupaxx.git
synced 2024-12-22 22:59:27 +00:00
p2pool: add warning about remote nodes in [Simple]
This commit is contained in:
parent
786b300623
commit
192b388a17
5 changed files with 33 additions and 2 deletions
|
@ -2,9 +2,10 @@
|
|||
## Updates
|
||||
* Added [`nodes.hashvault.pro`](https://hashvault.pro) to [Community Monero Nodes](https://github.com/hinto-janaiyo/gupax#community-monero-nodes) list
|
||||
* Added [`node.moneroworld.com`](https://moneroworld.com) to [Community Monero Nodes](https://github.com/hinto-janaiyo/gupax#community-monero-nodes) list
|
||||
* Added warning in `[P2Pool Simple]` tab about using remote nodes
|
||||
|
||||
## Fixes
|
||||
*
|
||||
* Top/Bottom bars are smaller, fixes some UI overflowing or being cramped
|
||||
|
||||
## Bundled Versions
|
||||
* [`P2Pool v3.0`](https://github.com/SChernykh/p2pool/releases/tag/v3.0)
|
||||
|
|
16
README.md
16
README.md
|
@ -36,6 +36,7 @@ Gupax is a (Windows|macOS|Linux) GUI for mining [**Monero**](https://github.com/
|
|||
* [License](#License)
|
||||
* [FAQ](#FAQ)
|
||||
- [Where are updates downloaded from?](#where-are-updates-downloaded-from)
|
||||
- [P2Pool connection errors](#p2pool-connection-errors)
|
||||
- [Can I quit mid-update?](#can-i-quit-mid-update)
|
||||
- [Bundled vs Standalone](#bundled-vs-standalone)
|
||||
- [How much memory does Gupax use?](#how-much-memory-does-gupax-use)
|
||||
|
@ -626,6 +627,21 @@ GitHub's API blocks request that do not have an HTTP `User-Agent` header. [Gupax
|
|||
|
||||
---
|
||||
|
||||
### P2Pool connection errors
|
||||
**TL;DR: Run & use your own Monero Node.**
|
||||
|
||||
If you are using the [default P2Pool settings](#P2Pool) then you are using a [Community Monero Node](#community-monero-nodes). Using a community node is convenient but comes at the cost of privacy and reliability. You may encounter connections issues with these nodes that look like this:
|
||||
```
|
||||
2023-01-05 12:27:37.7962 P2PServer peer 23.233.96.72:37888 is ahead on mainchain (height 2792939, your height 2792936). Is your monerod stuck or lagging?
|
||||
```
|
||||
To fix this you can select a different community node, or better yet: [Run your own local Monero Node](#running-a-local-monero-node).
|
||||
|
||||
Running and using your own local Monero node improves privacy and ensures your connection is as stable as your own internet connection. This comes at the cost of downloading and syncing Monero's blockchain yourself (currently 155GB). If you have the disk space, consider using the [P2Pool Advanced](#p2pool-1) tab and connecting to your own Monero node.
|
||||
|
||||
For a simple guide, see the [Running a Local Monero Node](#running-a-local-monero-node) section.
|
||||
|
||||
---
|
||||
|
||||
### Can I quit mid-update?
|
||||
If you started an update, you should let it finish. If the update has been stuck for a *long* time, quitting Gupax is probably okay. The worst that can happen is that your `Gupax/P2Pool/XMRig` binaries may be moved/deleted. Those can be easily redownloaded. Your actual `Gupax` user data (settings, custom nodes, pools, etc) is never touched.
|
||||
|
||||
|
|
|
@ -74,7 +74,7 @@ Every frame, the max available `[width, height]` are calculated, and those are u
|
|||
|
||||
```
|
||||
Main [App] outer frame (default: [1280.0, 960.0], 4:3 aspect ratio)
|
||||
├─ TopPanel = height: 1/14
|
||||
├─ TopPanel = height: 1/15
|
||||
├─ BottomPanel = height: 1/22
|
||||
├─ CentralPanel = height: the rest
|
||||
```
|
||||
|
|
|
@ -257,6 +257,17 @@ pub const P2POOL_SELECT_LAST: &str = "Select the previous community Monero no
|
|||
pub const P2POOL_SELECT_NEXT: &str = "Select the next community Monero node";
|
||||
pub const P2POOL_PING: &str = "Ping the built-in community Monero nodes";
|
||||
pub const P2POOL_ADDRESS: &str = "You must use a primary Monero address to mine on P2Pool (starts with a 4). It is highly recommended to create a new wallet since addresses are public on P2Pool!";
|
||||
pub const P2POOL_COMMUNITY_NODE_WARNING: &str =
|
||||
r#"TL;DR: Run & use your own Monero Node.
|
||||
|
||||
Using a Community Monero Node is convenient but comes at the cost of privacy and reliability.
|
||||
|
||||
You may encounter connection issues with community nodes which may cause mining performance loss! Late info from laggy nodes will cause your mining jobs to start later than they should.
|
||||
|
||||
Running and using your own local Monero node improves privacy and ensures your connection is as stable as your own internet connection. This comes at the cost of downloading and syncing Monero's blockchain yourself (currently 155GB). If you have the disk space, consider using the [Advanced] tab and connecting to your own Monero node.
|
||||
|
||||
For a simple guide, see the [Running a Local Monero Node] section on Gupax's GitHub at: 'https://github.com/hinto-janaiyo/gupax'"#;
|
||||
|
||||
pub const P2POOL_INPUT: &str = "Send a command to P2Pool";
|
||||
pub const P2POOL_ARGUMENTS: &str =
|
||||
r#"WARNING: Use [--no-color] and make sure to set [--data-api <PATH>] & [--local-api] so that the [Status] tab can work!
|
||||
|
|
|
@ -230,6 +230,9 @@ impl crate::disk::P2pool {
|
|||
ui.add_sized([width, height], Checkbox::new(&mut self.auto_ping, "Auto-ping")).on_hover_text(P2POOL_AUTO_NODE);
|
||||
})});
|
||||
|
||||
debug!("P2Pool Tab | Rendering warning text");
|
||||
ui.add_sized([width, height/2.0], Label::new(RichText::new("WARNING: It is recommended to run/use your own Monero Node (hover for details)").color(YELLOW))).on_hover_text(P2POOL_COMMUNITY_NODE_WARNING);
|
||||
|
||||
//---------------------------------------------------------------------------------------------------- Advanced
|
||||
} else {
|
||||
debug!("P2Pool Tab | Rendering [Node List] elements");
|
||||
|
|
Loading…
Reference in a new issue