Edky is a free, public domain command-line tool for converting Ed25519 public keys between the encoding formats used by different networks and software. It is aimed at developers and system administrators who work with IPFS, libp2p, NEAR, iroh, OpenSSH and similar systems, and who need the same key shown in another format.
The project sits in the decentralized storage category, but its job is narrower than a storage node or a sync client. It translates keys so that tools built on different conventions can recognize each other's identities. If you plan to download Edky for Windows, expect a small utility that does one job well rather than a full application with a graphical interface.
What Is an Ed25519 Public Key?
Ed25519 is a signature scheme built on an elliptic curve. It is popular because it is fast, produces compact signatures and is hard to implement incorrectly. A public key in this scheme is a 32-byte value, and it is the part of an identity that you can share openly while the matching private key stays secret.
The key itself is just bytes. How those bytes are written down is a separate question. Developers often see the same 32 bytes represented as a long hexadecimal string, a base58 identifier, a base64 blob or a prefixed multibase string. Each representation carries the same identity, but software expects one particular form, so a key copied from one system may simply be rejected by another.
Understanding this distinction helps you use Edky correctly. The tool does not create new keys or change the underlying identity. It changes how an existing public key is written, so the same identity can be recognized by a different ecosystem.
Why the Same Key Looks Different Across Systems
Different networks made different choices about encoding. Some identifiers use base58 because it avoids easily confused characters. Others use base32 or multibase, which add a prefix that tells the reader which encoding is in use. OpenSSH uses its own line format, where a key type label is followed by a base64 block.
These choices are sensible within each system, but they make cross-system work tedious. A developer who wants to link an IPFS identity with a libp2p peer or check a NEAR-style key against an OpenSSH setup may have to convert the value several times. Mistakes at this step are easy to make and hard to spot, because the output still looks like a valid key.
A converter removes the manual step. By producing each format from one source key, it lowers the chance that a copied string is off by a character or carries the wrong prefix.
Practical Scenarios for Key Format Conversion
Consider a developer who runs an IPFS node and wants to confirm that a peer's identity matches a key listed in a configuration file written for another tool. Edky lets them convert the key into the expected format and compare the two strings directly, without reformatting anything by hand.
Another common case is debugging. If two services disagree about an identity, converting the same public key into each service's format can show whether the problem is the key or the encoding. This narrows the search quickly and keeps the investigation focused on the right layer.
Teams that maintain test suites can also use the library form. A script can generate conversions for a set of known keys and store the results as fixtures, so that future changes to the pipeline are caught early. The tool is most useful where identity strings cross boundaries between systems.
Key features
Command-Line Tool and Library
Multiple Encoding Formats
Cross-Ecosystem Interoperability
Public Domain License
Supported coins
Edky is built around interoperability with several networks and tools, including ASIMOV, IPFS, Iroh, libp2p, NEAR and OpenSSH. Its encoding support covers Base16, Base32z, Base58, Base64 and Multibase. It works with Ed25519 public keys, so it is a fit for identity strings in these ecosystems rather than a general-purpose wallet or coin utility.
How to install Edky on Windows
- 1
Get the Official Files
Open the project's official GitHub repository at github.com/artob/edky and go to the Releases page. Look for version 0.1.1 and check whether a Windows build is listed. Download only from the official website or GitHub Releases, and avoid mirror sites that repackage the file.
- 2
Verify the Download
If the release provides a SHA-256 checksum or a signature, compare it with your file before running anything. In PowerShell, the Get-FileHash command prints the SHA-256 value of a file, which you can match against the published one. A mismatch means the file should not be used.
-
Place and Test the Program
Extract the archive if one was provided, then keep the edky executable in a folder you control. You can add that folder to your PATH environment variable or run the program from its own directory. Open Command Prompt or PowerShell and confirm that edky starts before you move on to real keys.
How to use Edky
Edky is a terminal tool, so the workflow happens in a command window. The steps below keep the process predictable and help you avoid mixing up input and output formats.
- Open Command Prompt or PowerShell and change to the folder that holds the edky executable.
- Confirm that the program starts from the terminal before you handle any real data.
- Read the README in the GitHub repository to find the exact command syntax and the format names it accepts.
- Copy only the public key you want to convert. Never include a private key in the input.
- Run the conversion, choosing the source encoding and the target format exactly as the README describes.
- Compare the output with the format your target system expects, paying attention to prefixes and length.
- If you need the same conversion inside a program, use the library form once it is available for your language.
Keep a record of which format each output came from. This makes later debugging much easier when two systems disagree.
Pros & cons
- Free to use, and released into the public domain under the Unlicense
- Focused on one task: converting Ed25519 public keys between formats
- Covers several common encodings, including Base58, Base64 and Multibase
- Offers both a command-line tool and a library for scripted use
- Narrow scope: it converts keys and does not store, sync or host files
- Libraries for Dart, Python, Ruby, Rust and TypeScript are listed as upcoming, not yet available
- Windows support is conditional on the release files, so confirm a Windows build on the Releases page
- Version 0.1.1 points to an early-stage project with a small surface area
Is Edky safe?
Edky works with public keys rather than wallets, but identity strings still belong to real systems, so handle them carefully. Get the file only from the official GitHub repository or its Releases page, and check the SHA-256 hash or signature when one is published. Before installing, check the latest version on the official website, since the release listed here may be superseded. Never paste private keys or seed phrases into online converters or third-party websites. Run conversions locally on your own machine, and keep your operating system and antivirus protection active. Because the code is public domain, forks with altered behavior may circulate, so verify that the copy you run matches the official source.
- Official source only. Download from github.com/artob/edky. 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
Edky is not a substitute for IPFS Desktop, Kubo or Peergos. Those programs run nodes, manage content or handle files for end users. Edky sits beside them as a helper that makes identity strings line up across tools. Pinner CLI is also terminal-based, but it focuses on pinning content to IPFS rather than converting keys. ZeroNet takes a different approach altogether, serving decentralized sites built on Bitcoin-style cryptography. If you need storage or a network node, choose one of those programs. If your problem is converting Ed25519 public keys between formats, Edky is the focused option.
Specifications
- Price
- Free
- Type
- Open source
- License
- unlicense
- Latest version
- 0.1.1
- Last update
- 14 Oct 2026
- Windows support
- Likely (builds for Windows; check releases)
- Source code
- github.com/artob/edky
Frequently asked questions
Edky converts Ed25519 public keys between encoding formats such as Base58, Base64 and Multibase. It is useful when a key from one system, such as IPFS or libp2p, must be written in the form another system, such as NEAR or OpenSSH, expects. It does not store files or run a network node.
It can be, provided you download it from the official GitHub repository or Releases page and verify the SHA-256 hash or signature when one is published. Avoid mirror sites, and never enter private keys or seed phrases into third-party tools. Keep antivirus protection running while you test the program.
Yes. Edky is listed as free software and is released under the Unlicense, which places it in the public domain. You can use, modify and redistribute the code without paying a license fee. Check the repository for any notes about the current release before you rely on it in production.
No. Edky has a narrow purpose: it changes how an Ed25519 public key is written so that different systems can read it. If you need to store, pin or share files on a decentralized network, look at tools such as Pinner CLI, Kubo or Peergos, which handle content directly.
Edky supports Base16, Base32z, Base58, Base64 and Multibase encodings. These formats cover most of the identity strings you will meet when moving keys between IPFS, libp2p, NEAR and OpenSSH. Check the README for the exact format names the command accepts.
Yes, the project offers a library alongside the command-line tool. Polyglot libraries for Dart, Python, Ruby, Rust and TypeScript are described as upcoming, so availability depends on the language you use. For now, the command-line tool is the most direct way to run conversions on Windows.
Verdict
Edky is a good fit for developers and system administrators who regularly move Ed25519 public keys between IPFS, libp2p, NEAR, OpenSSH and similar systems. It is free, public domain and focused on a single task. It is not a storage program, despite its category, and it will not help if you need to host or share files. If you need a dependable converter for identity strings and you are comfortable with a terminal, it is worth testing with your own non-sensitive keys first.