Wallet Daemon is a free, open-source signing service for developers and teams that send transactions on Enjin Platform and want the signing key to stay on their own machine. It is written in Rust, released under the LGPL license, and its latest version is v3.0.11.
Rather than a window for checking balances, Wallet Daemon runs quietly in the background and handles one job: signing the transactions the platform asks for. It opens an authenticated, outbound-only connection, so you do not need to open inbound ports on your machine. The most recent code update is dated October 26, 2026.
What Is an Outbound-Only Signer?
A signer is a component that holds a private key and produces a cryptographic signature for a transaction. The transaction is then broadcast by another system. An outbound-only signer is designed so that all network connections start from inside your network. Your machine calls out to the platform, receives work, and sends back signed results.
This pattern matters for people who run automated systems. A server that accepts inbound connections has to be exposed to the internet, configured with firewall rules and monitored for intrusion attempts. A daemon that only makes outgoing connections can stay behind a firewall that blocks inbound traffic, which removes one large category of risk.
The trade-off is that you are responsible for keeping the daemon running and for watching its behavior yourself. Outbound-only design reduces exposure, but it does not replace basic operational discipline.
Why Keep Signing Keys on Your Own Machine?
Many platforms keep both the key and the signing logic on their servers. That is convenient, but it means you must trust the operator with your funds. Wallet Daemon takes the opposite approach. The signing happens on your computer, with the wallet file stored locally and protected by KEYPASS.
A practical example: a studio that mints digital items on Enjin Platform may want its operations team, not the platform, to control the key that approves transactions. Running a local signer lets that team decide who can access the machine, when backups happen and how the encryption password is stored.
Local custody also means local responsibility. If the machine is lost, compromised or wiped without a backup, the wallet cannot be recovered from the platform side. Plan backups for wallet.seed and the KEYPASS before you go live.
Who Wallet Daemon Is For
Wallet Daemon is aimed at developers, integrators and operations teams who already work with Enjin Platform. It makes most sense when transactions need to be signed automatically, without a person approving each one in a wallet window.
Typical readers include a developer building a game or marketplace that sends transactions on behalf of users, or a team that wants a dedicated signing machine separate from its web servers. Some will prefer the Docker option, which fits teams that already deploy services in containers.
If your goal is to hold, receive and send a range of coins from a personal interface, Wallet Daemon is not built for that. The sections below compare it with general-purpose wallets so you can choose the right tool.
Key features
Outbound-only connection
Event-driven work queue
Encrypted wallet.seed file
KEYPASS protection
PLATFORMKEY authentication
Three-minute safety poll
Supported coins
Wallet Daemon is built around Enjin Platform, so its scope is transactions on that platform rather than a broad list of coins or blockchains. It is a signer for platform-driven work, not a multi-currency wallet, and it should be evaluated on that basis.
How to install Wallet Daemon on Windows
- 1
Choose the official source
Download only from the official website. For Wallet Daemon, that means the project repository at github.com/enjin/wallet-daemon and its Releases page. Avoid mirrors and file-sharing sites, even if they appear to offer the same version.
- 2
Verify the download
Compare the SHA-256 checksum of the file with the value published on the release page, or check the release signature if one is provided. Do not run the file if the values do not match.
- 3
Install the Windows build
Check the latest release for a ready-made Windows package. If one is available, run the installer or extract the archive to a folder you control. Choose a location that your backup routine covers, because wallet.seed will live nearby.
-
Configure the secrets
Set the PLATFORMKEY and KEYPASS values before first start. Store them in a password manager or a secrets store, not in a text file next to the daemon, and do not paste them into chat or support requests.
System requirements
- Windows, using a ready-made build from the latest release if one is published for your version
- Docker is also a supported platform if you prefer containers
- An Enjin Platform account with credentials that allow the daemon to authenticate
How to use Wallet Daemon
Wallet Daemon runs as a background process, so setup is mostly configuration rather than clicking through menus. Plan a short session for the first run, and test the setup before you connect any funds you cannot afford to lose.
- Set PLATFORMKEY so the daemon can authenticate with Enjin Platform.
- Set KEYPASS, which encrypts and decrypts the wallet.seed file.
- Point the daemon at your encrypted wallet.seed so it knows which wallet to sign with.
- Start the daemon and confirm that it opens its outbound connection to Enjin Platform.
- Trigger a test event from the platform side and check that a signed payload comes back.
- Review the logs for errors, failed authentication or unexpected events.
- Leave the three-minute safety poll running, because it acts as a backstop for pending work.
After the first successful test, record the configuration steps in your runbook. Treat any change to PLATFORMKEY or KEYPASS as a planned maintenance task, and keep a tested backup of wallet.seed before making it.
Pros & cons
- Outbound-only design means no inbound ports need to be opened
- Signing keys stay on your own machine in an encrypted wallet.seed file
- Open source under the LGPL license, so the code can be reviewed
- Free to use
- Small, purpose-built tool that does one job
- Available through Docker as well as Windows
- Built for Enjin Platform transactions, not as a general-purpose wallet
- Windows support is described as likely, so you need to confirm a Windows build on the releases page
- Requires an Enjin Platform setup and credentials before it is useful
- You are responsible for managing KEYPASS, PLATFORMKEY, backups and logs
- No everyday interface for holding and sending coins
Is Wallet Daemon safe?
Wallet Daemon handles signing keys, so treat it with the same care as any wallet. Download only from the official website, meaning the GitHub repository at github.com/enjin/wallet-daemon and its Releases page. Verify the SHA-256 checksum or signature of the file against the values the release publishes before running it.
Store KEYPASS and PLATFORMKEY in a secrets manager, and keep them out of screenshots, shared documents and support tickets. Back up wallet.seed to an encrypted location that is separate from the machine running the daemon. Never enter a seed phrase on third-party websites, and be suspicious of anyone who asks for your KEYPASS or the wallet.seed file. The project is not deprecated, but check the latest version on the official website before each update.
- Official source only. Download from github.com/enjin/wallet-daemon. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Most programs in this catalog are consumer wallets. Coinomi and Atomic Wallet focus on holding many assets, Exodus adds built-in exchange, Electron Cash is a lightweight Bitcoin Cash wallet, and Trust Wallet works as a browser extension on PC.
Wallet Daemon sits in a different category. It does not manage a portfolio or offer a broad asset list. Instead, it signs Enjin Platform transactions on your machine as a background service. If you want to check balances and send coins manually, one of the wallets above will suit you better. If you run an Enjin Platform integration and need signing kept on your side, Wallet Daemon is the more relevant tool.
Specifications
- Price
- Free
- Type
- Open source
- License
- LGPL
- Latest version
- v3.0.11
- Last update
- 26 Oct 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/enjin/wallet-daemon
Frequently asked questions
Yes. Wallet Daemon is free and released as open source under the LGPL license. You can read the source code on GitHub, which lets you see how the signing flow works before you deploy it.
The project builds for Windows, but you should confirm that a ready-made Windows package is published for the version you want. The releases page is the place to check. Docker is also listed as a supported platform and may be simpler if you already run containers.
It can be, if you take the right steps. Download it only from the official GitHub repository, verify the checksum or signature, protect KEYPASS and wallet.seed, and never enter a seed phrase on third-party websites. Its outbound-only design also avoids opening inbound ports.
The wallet.seed file is an encrypted file on disk that the daemon uses to sign transactions with the configured wallet. KEYPASS encrypts and decrypts it, so the file cannot be used without the password. Keep backups of it in a secure location.
PLATFORMKEY authenticates the daemon with Enjin Platform. It confirms that your instance is the one receiving events and returning signed payloads. Store it as a secret and rotate it if you suspect it has been exposed.
No, Wallet Daemon is built around Enjin Platform transactions and is not designed for Bitcoin. If you need a lightweight Bitcoin Cash wallet with a desktop interface, Electron Cash is listed in this catalog as an alternative.
Verdict
Wallet Daemon is a narrow, purpose-built tool. If you are a developer or operator building on Enjin Platform and want transaction signing to stay on your own machine, it is a sensible choice. It is free, open source and built around an outbound-only connection. If you simply want a wallet to hold and send crypto from a personal interface, skip it and look at the consumer wallets in this catalog.