You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Really what I'm asking is - is this crate maintained, and if not, could we have the base58 name on crates.io?
Failing that, could we combine the base58 code in rust-bitcoin with this crate, allow rust-bitcoin people to make a new release, and unify the APIs? I know a goal of this crate is to be small, which I think we can retain, and to be fast, which we will definitely maintain (will not replace any algos unless we have a clear speedup) (although we will add base58ck support which requires sha2 which is inherently way slower than anything else related to the format).
The text was updated successfully, but these errors were encountered:
FTR the base58 crate just does encoding/decoding while the base58check crate handles the checksum and depends on base58 and sha2. I don't think we can do a simple name takeover even if @debris agreed to give it away since we want to provide a single "base58 and checksum" crate that depends on bitcoin_hashes.
@apoelstra I can add you as an Owner of this crate on crates.io if you would like to take over the maintenance of it and release future versions. Is that ok for you?
Really what I'm asking is - is this crate maintained, and if not, could we have the
base58
name on crates.io?Failing that, could we combine the
base58
code in rust-bitcoin with this crate, allow rust-bitcoin people to make a new release, and unify the APIs? I know a goal of this crate is to be small, which I think we can retain, and to be fast, which we will definitely maintain (will not replace any algos unless we have a clear speedup) (although we will add base58ck support which requires sha2 which is inherently way slower than anything else related to the format).The text was updated successfully, but these errors were encountered: