Try the normal path
Create a wallet, write down the recovery words, mine with your CPU, stop mining, close the app, open it again, then confirm the balance still makes sense.
Beta testing notes
This public beta exists to find broken edges before the live network starts. Test wallets, test balances, blocks, and treasury records will be reset before launch.
Create a wallet, write down the recovery words, mine with your CPU, stop mining, close the app, open it again, then confirm the balance still makes sense.
Switch public nodes, change mining power, check for updates, send test SLTHY to another wallet, and report the exact step that caused trouble.
Never send recovery words, wallet passwords, private keys, or seed files. A real support reply will not ask for them.
Use these SHA256 hashes if you want to verify a download before running it.
Windows installerF23DF269FD7131E4CBB056438736017C07B7D349EF8D4A1DD2AE4935DD22C995
Linux install script1FCEFB7A456B8CB8971F54960502EB9C6E7C7E1569AEA546E190C001680DDF45
Linux x64 package356EC308590BC08DBD0E4259644B399981CB8DEF83DFED21F8387494DB061D53
Public nodes relay and verify. They should not mine. During the latest pre-publish check, Borogove, Mome, and Rath were reachable on the public P2P port, agreed with each other, and reported mining as off.
Borogove is East Coast. Mome is West Coast. Rath is Europe.
Good reports include the Slithy version, Windows or Linux version, selected public node, wallet action, mining setting, and the steps that led to the problem. Screenshots help. Recovery words and passwords do not belong in reports.