gemcoin
Official Python implementation of the Gemcoin protocol. (by VladUsatii)
ed25519-unsafe-libs
List of unsafe ed25519 signature libs (by MystenLabs)
| gemcoin | ed25519-unsafe-libs | |
|---|---|---|
| 1 | 5 | |
| 1 | 212 | |
| - | -0.5% | |
| 0.0 | 3.8 | |
| over 1 year ago | 6 months ago | |
| Python | Rust | |
| GNU General Public License v3.0 only | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gemcoin
Posts with mentions or reviews of gemcoin.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-04.
-
Is my transaction signature system secure for my blockchain? (audit)
Before I start, here is all of the Github files for my cryptocurrency (keep in mind that I'll be focusing on the file core/sendShards.py): https://github.com/VladUsatii/gemcoin
ed25519-unsafe-libs
Posts with mentions or reviews of ed25519-unsafe-libs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-07-04.
-
Is my transaction signature system secure for my blockchain? (audit)
I tried to explain to you last time you asked about "your own crypto" that the answer always will be "it's not good, don't do it". First thing that strikes me is that you take public key from the provided data, which suggests a trivial attack like in https://github.com/MystenLabs/ed25519-unsafe-libs
- Vulnerability in the elliptic curve lib used by Trezor (among others)! Has this been disclosed by Trezor team?
- List of unsafe ed25519 signature libs
-
Initial impact report about this week's EdDSA Double-PubKey Oracle attack in 40 affected crypto libs
original findings and audit report by MystenLabs' Cryptography Chief + continuously updated list of affected libs: https://github.com/MystenLabs/ed25519-unsafe-libs
-
40 unsafe ed25519 libs where private key can be leaked via signing api misuse
TL;DR A new audit report revealed that the signing api of many ed25519 libs (some of them very popular) unfortunately expects a public key as input. An attacker may extract the private key by requesting two different signatures for the same message and private key, but on purpose for a different public key. Applications should not expose this api publicly and should refactor it to protect devs against accidental api misuse. Read more: https://github.com/MystenLabs/ed25519-unsafe-libs and https://blog.safeheron.com/blog/safeheron-originals/analysis-on-ed25519-use-risks-your-wallet-private-key-can-be-stolen
What are some alternatives?
When comparing gemcoin and ed25519-unsafe-libs you can also consider the following projects:
ctf - Ctf solutions from p4 team
trezor-firmware - :lock: Trezor Firmware Monorepo
libsodium - A modern, portable, easy to use crypto library.
fastcrypto - Common cryptographic library used in software at Mysten Labs.
ed25519-dalek - Fast and efficient ed25519 signing and verification in Rust.
paseto - Platform-Agnostic Security Tokens