Skip to content

Releases: Synorixz/synorix

Synorix Mainnet v0.1.0

Choose a tag to compare

@Synorixz Synorixz released this 22 Jun 17:32

Prebuilt Linux x64 node + CLI for the Synorix mainnet.

Connect via the DNS seed (seed.synorixcoin.com) or addnode=161.97.180.76:9333.
Mining + node guide: https://synorixcoinn.vercel.app/mining

Synorix Testnet v0.1.7

Choose a tag to compare

@Synorixz Synorixz released this 11 Apr 22:30

Synorix Testnet v0.1.7 (Pre-release) is a Windows desktop client that connects to the Synorix testnet via a remote VPS node. Each user gets a unique wallet — balances, addresses, and mined coins are private and persistent per installation.

SETUP (required before first launch):

  1. Open PowerShell as Administrator.
  2. Run: wsl --install -d Ubuntu
  3. Restart your PC if prompted.
  4. Open Ubuntu from Start Menu once and complete username/password setup.
  5. Verify with: wsl -l -v (Ubuntu should be listed as WSL2).

HOW TO RUN:

  1. Download synorix-testnet-mvp-win-unpacked.zip from this release.
  2. Extract the zip file using Extract All.
  3. Run synorix-testnet-mvp.exe inside the extracted folder.
  4. If SmartScreen appears, click More info then Run anyway.

FEATURES:

  • Remote VPS node connection (no local node required).
  • Per-user unique wallet (auto-generated on first launch).
  • Wallet ID displayed in the app for reference.
  • Send coins to other testnet addresses.
  • Manual mining (Mine Once button).
  • Auto mining every 2.5 minutes (Start Auto Mining / Stop Auto Mining toggle).
  • Modern dark UI with real-time dashboard.

NOTES:

  • This is a testnet pre-release build.
  • Your wallet ID and balance persist between sessions.
  • For VPS security, restrict RPC access with IP allowlists or SSH tunnel.

Synorix Testnet v0.1.6

Choose a tag to compare

@Synorixz Synorixz released this 11 Apr 21:50

Synorix Testnet v0.1.6 (Pre-release)
Please follow the setup steps below carefully before launching the app.

  1. System Requirements
    Windows 10/11 (64-bit)
    Administrator privileges (required for WSL installation)
    Stable internet connection
    At least 4 GB RAM recommended
    At least 2 GB free disk space recommended
  2. Install WSL + Ubuntu (Required)
    Step 2.1 — Open PowerShell as Administrator
    Press Start
    Type PowerShell
    Right-click Windows PowerShell
    Click Run as administrator
    Step 2.2 — Install WSL and Ubuntu
    Run this command:

wsl --install -d Ubuntu
Step 2.3 — Restart Windows
If prompted, restart your computer.
If not prompted, restarting is still recommended.
Step 2.4 — Complete Ubuntu first-time setup
Open Ubuntu from the Start Menu.
Wait for initialization to complete.
Create your Linux username and password when prompted.
Step 2.5 — Verify WSL installation
Run:

wsl -l -v
Expected result:

Ubuntu appears in the list
Version is 2 (WSL2)
3) Download and Extract the Application
Download synorix-testnet-mvp-win-unpacked.zip from this release.
Right-click the file and choose Extract All...
Open the extracted folder.
4) Launch the App
Run synorix-testnet-mvp.exe.
If Windows SmartScreen appears:
Click More info
Click Run anyway
5) First Launch Guidance
The first launch may take a short time to initialize.
Keep WSL/Ubuntu installed; the app depends on it.
If firewall/security prompts appear, allow the app when appropriate.
6) VPS / RPC Connection Notes
Ensure your VPS node is online and healthy.
Verify RPC credentials are correct.
Confirm firewall rules and RPC port settings are correct.
If connection fails, check VPS logs and RPC bind/allow settings.
7) Troubleshooting
“WSL not found” or “Ubuntu not found”
Open Admin PowerShell and run:
wsl --install -d Ubuntu
Restart Windows and try again.
Ubuntu exists but app still fails
Open Ubuntu manually once and complete setup.
Re-run wsl -l -v to confirm WSL2 status.
App does not start
Close and reopen the app.
Try launching once as Administrator for testing.
Verify extracted files were not blocked by antivirus.
Node / RPC connection issues
Confirm VPS is running.
Confirm RPC username/password.
Confirm correct RPC host/port.
Confirm firewall permits intended access.
8) Security Recommendation (Important)
This is a testnet build.
For safer operation, do not expose unrestricted RPC access publicly.
Use:

IP allowlists (rpcallowip) and/or
SSH tunnel / secure proxy access.