-
Notifications
You must be signed in to change notification settings - Fork 44
Description
Environment
- Smapp version: 1.7.10 | develop
- Epoch: 38
- OS: macOS Sonoma (14.7)
- Chip: Apple M1 Ultra
- Cores: 20 (16 performance and 4 efficiency)
- Memory: 128 GB
Describe the bug
As an experienced CHIA farmer (both command-line and GUI client), I decided three months ago to conduct a proof-of-concept (PoC) using two identical Mac Minis with identical external storage. My aim was to compare SpaceMesh (GUI client) and SIGNUM (BTDEX GUI client) in terms of GUI functionality, plotting efficiency, and profitability. Both clients required approximately a month to plot the necessary space, which is standard, but I’m patient. However, I quickly noticed significant differences during the setup process. For SpaceMesh, you cannot create a local wallet without first earning some rewards, as there’s no way to request “Smidge” (its currency) to initialize the wallet. This contrasts with other clients like BTDEX and CHIA, which provide seed coins specifically for this purpose. To me, this feels like a major oversight. Fast-forward two months: my BTDEX client has been farming smoothly and has generated nearly 500 coins. Meanwhile, my SpaceMesh client tells a different story. Registered in epoch 35 and now nearing the end of epoch 38, my local wallet has yet to receive any Smidge or SpaceMesh rewards. The wallet remains unspawned despite being continuously online with a fast broadband connection. The logs show no errors, yet the client fails to deliver any rewards.
SpaceMesh also lacks effective feedback or visualization tools in its GUI, leaving users to rely entirely on logs for information. By comparison, other coin clients provide much clearer performance insights. To make matters worse, SpaceMesh requires plotting to be completed before mining can begin, unlike other platforms that allow simultaneous plotting and mining. Additionally, if you move the client to another system, you must manually transfer the install directory to avoid re-plotting, as the client doesn’t automatically detect existing plots and may overwrite them. At this point, my SpaceMesh client has consumed three months of energy and internet bandwidth, yet it still shows a zero balance. Unless this changes or someone can offer a solution, I’m ready to abandon SpaceMesh permanently due to the high operational cost and lack of tangible rewards. If the developers are looking for beta testers to improve the setup, I’d be willing to help refine this technology. However, my current experience with the SpaceMesh client has left me deeply disappointed. Has anyone else encountered similar challenges? I’d appreciate hearing about your experiences.
I’ve been working with the Discord Forum online (smapp), but no one seems able to pinpoint the exact issue on why after 3 months I still have no rewards when I am told I should have some? Here’s a summary of my situation and the guidance from others:
- Node Status:
o My node has been running non-stop for 3 months, except for brief downtimes to apply two updates and now a third.
o It is synchronized with the network, publishing proposals for eligible layers. Logs show timely proposals (~300 ms latency),
correct active set hash, and correct beacon values.
- Wallet:
o The wallet is unspawned, which I understand is fine for receiving rewards. However, no rewards have been received despite
published proposals for multiple layers.
o There’s no apparent way to configure the wallet further in the GUI, so I assume this is not the issue.
- System Setup:
o Time Synchronization: Verified with an NTP local service, keeping the system clock accurate to within 1 second. No time offset
warnings in logs.
o Network: The node runs on a dedicated 1Gbps internet connection with low latency and no connectivity issues as I also have a
dedicated ISP IP Address.
o Software: I am using the latest client version (1.7.10).
- Checks Performed:
o Forum users have searched my log (attached) for "LATE_PROPOSAL" but found none.
o No indication of duplicate nodes (equivocation) in the logs.
o Network and peer connectivity appear stable, but logs don’t clarify if peers are “bad” or misbehaving.
- Ongoing Issues:
o Despite publishing valid proposals, no rewards have ever been received.
o Logs show no critical errors or reasons for disqualification.
o Suggestions from other contributors, such as time sync and wallet spawning, don’t apply to my case.
I’d appreciate any deeper analysis, insights or pointers and also compensation for the missed rewards I should have received.
Many thanks
Dave (DrTekno - Smapp / DocTekno - Github)
Steps to reproduce
See the log file, screenshots attached and full description above.
Expected behavior
See the log file, screenshots attached and full description above.
Actual behavior
See the log file, screenshots attached and full description above.
Logs
How to fix
Please also see the detailed conversations on the "Discord Smapp" section where members have tried to help.