Release stable verison

[frisitano]

Overview

Currently, downstream consumers of this library are referencing it via a git reference to the main branch. This is a fragile pattern and sensitive to logic drift and API changes of the library which could have a downstream impact. I propose we cut a stable release of this library by either creating a git tag or publishing the crate to crates.io. Publishing to crates.io would be the preferred option but may incur additional overhead. An alternative is that we could refer to a specific commit hash in downstream consumers but I believe this is bad practice.

[lispc]

sounds good.what about you first use cargo reference to a git rev inside reth, after hundreds of blocks verified (make sure no big issue, both in correctness and interface design), then we publish to crates.io?

[frisitano]

That sounds reasonable to me 👍