Publish workspace to crates.io

[conorsch]

Overview

We want to publish the crates in the protocol repo workspace to https://crates.io, so that external developers can depend on Penumbra code when writing downstream tooling. To date, we've recommended that external developers use git dependendencies in Rust projects, e.g.

penumbra-transaction = { git = "https://github.com/penumbra-zone/penumbra", rev = "ac7abacc9bb09503d6fd6a396bc0b6850079084e", features = [
   download-proving-keys",
] }

but doing so is not possible for projects already publishing their crates to crates.io. Two notable projects we intend to support are Astria (#3125) and Hermes. We're already maintaining a fork of Hermes, and publishing the crates would unblock us from submitting the Penumbra integration for Hermes to upstream.

Work to date

There's currently some WIP around the workspace consolidation happening in the following branches:

• https://github.com/penumbra-zone/penumbra/tree/release/v0.82.x
• https://github.com/penumbra-zone/penumbra/tree/erwan/prepare_crates_io

That work should be appended to, and organized in a feature branch that can be PR'd into main. In the process, we'll likely attempt to resolve both #4400 & #4682.

[erwanor]

Thanks for writing this up and tracking it, fwiw:

In the process, we'll likely attempt to resolve both #4400 & #4682.

I think this is already done in v0.82.x branch. v1 reflection was only released as part of [email protected] iirc.

The release branch should have all of the ecosystem bumps (tonic, ibc-types, tendermint, tower, etc.)

[conorsch]

The release branch should have all of the ecosystem bumps (tonic, ibc-types, tendermint, tower, etc.)

That's true, the release branch does contain a commit that bumps the deps (#4973), but unfortunately it contains regressions like breaking HTTPS support for tonic clients. Fixing that regression is a bit of a side quest from the described goal of publishing the workspace, but worthwhile to get things straightened out. I'll follow up with PRs into main that describe the problem in detail.

[erwanor]

Thanks for the write-up, my understanding is that this is caused by the rustls backend change to aws-lc-rs (and away from ring). I think this might potentially cause platform issues down the road, but we'll figure it out when we get there (and hopefully, the ecosystem will beat us to it).

1. cargo add aws-lc-rs
2. let _ = aws_lc_rs::default_provider().install_default(); per process (so, e.g, one in `main.rs in the pcli bin)
3. Tracking the tls_config calls to make sure that they configured with the bundled certificates: tls_config(ClientTlsConfig::new().with_webpki_roots())?

I am not entirely sure that this is sufficient to unblock, but that's what I got from hacking on this a bit.