Is your feature request related to a problem? Please describe.
re: name -> hash as an identifier scheme. OpenSSL only began support for SHA3 in 2018-09. There are no security reasons for the hashing pattern, we just need unique IDs. Also SHA3-512 is kind of slow.
I think we should try to make the process of getting an id and the id itself as simple as possible.
Note also that since we'd be using a tiny substring of the hash, there's really no point in the extra bits (512 is overkill).
Describe the solution you'd like
Use MD5. It gives a very reasonable enough chance of non-collisions. SHA1 would work fine too.
Describe alternatives you've considered
id = "Just pick any noun that isn't taken or make up a word".
Is your feature request related to a problem? Please describe.
re: name -> hash as an identifier scheme. OpenSSL only began support for SHA3 in 2018-09. There are no security reasons for the hashing pattern, we just need unique IDs. Also SHA3-512 is kind of slow.
I think we should try to make the process of getting an id and the id itself as simple as possible.
Note also that since we'd be using a tiny substring of the hash, there's really no point in the extra bits (512 is overkill).
Describe the solution you'd like
Describe alternatives you've considered
id = "Just pick any noun that isn't taken or make up a word".
Additional context
Rel #5
:warning: https://github.com/BelfordZ/starIPs/blame/master/README.md#L17 !=
Resulting \*IP Name:ECIP-cebf0a05``