Start with the correct platform
Download the package for your architecture: Windows x64, Linux amd64 or macOS arm64. The website copies the provided release files unchanged. Compare the full filename, version, file size and SHA-256 before opening an installer. A consistent file is not the same as an independently audited application.
Understand development signing
The source workflow describes temporary self-signed development certificates for Strong Company LTD, Authenticode on Windows, and detached signatures plus ad-hoc signing for Linux/macOS artifacts. Development signing does not establish the trust of a production certificate or Apple notarization. Review your operating system’s publisher information and security prompts; this website does not instruct you to disable system protections.
Current preview and account secrets
The supplied backend demonstrates setup progress and creates a temporary test file. It has no implemented wallet account creation, recovery phrase handling, encrypted vault or on-chain signing. It should not be used as a place to enter a real recovery phrase or manage assets. Wallet concepts on the website illustrate future functionality.
Keep diagnostics local and relevant
Installation logs can help explain a setup error. Record the operating system, architecture, exact version, package hash and error message before requesting support. Remove unrelated personal details from logs. The website’s diagnostic form prepares a local text file; it does not transmit the report or collect secrets.
Release details are derived from the supplied desktop source and distribution files.
21RISE desktop · 4.2.1.1 release notes22RISE desktop · package checksums