The "dasherized" syntax provides a URI-safe alternative:
The CryptoURI format leverages the URI generic syntax defined in RFC 3986 to provide simple and succinct encodings of cryptographic keys, including public keys, private/secret keys, encrypted secret keys with password-based key derivation, digital signatures, key fingerprints, and other digests.
Binary data is serialized using the Bech32 encoding format which is designed to prevent human transcription errors by using an alphabet that eliminates similar-looking characters to avoid transcription errors and adds a checksum across the whole URI to detect these errors when they do happen. CryptoURIs which have been mis-transcribed will fail to decode.
Help and Discussion
Have questions? Want to suggest a feature or change?
- Gitter: web-based chat about cryptouri
- Google Group: join via web or email (firstname.lastname@example.org)
Code of Conduct
We abide by the Contributor Covenant and ask that you do as well.
For more information, please see CODE_OF_CONDUCT.md.
Bug reports and pull requests are welcome on GitHub at: https://github.com/cryptouri/cryptouri-rb
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be licensed as noted below, without any additional terms or conditions.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.