Skip to content

Update documentation to use attested-tls-proxy rather than cvm-reverse-proxy for getting TLS certificates#78

Open
ameba23 wants to merge 2 commits intoBuilderNet:mainfrom
ameba23:peg/docs-use-attested-tls-proxy-not-cvm-reverse-proxy
Open

Update documentation to use attested-tls-proxy rather than cvm-reverse-proxy for getting TLS certificates#78
ameba23 wants to merge 2 commits intoBuilderNet:mainfrom
ameba23:peg/docs-use-attested-tls-proxy-not-cvm-reverse-proxy

Conversation

@ameba23
Copy link

@ameba23 ameba23 commented Feb 26, 2026

This updates documentation to use attested-tls-proxy's get-tls-cert command rather than cvm-reverse-proxy when directing users how to retrieve a TLS cert over an attested channel before using it to send orderflow.

This pairs with a PR to attested-tls-proxy with some minor changes to make the options more consistent with `attested-get. flashbots/attested-tls-proxy#142

Issue with Azure

Currently the documentation tells users to install the vanilla build with no azure support (since we made it opt-in).
For azure attestations, there are issues with installing on Macos, as well as a need for the --override_azure_outdated_tcb flag.

TODO:

  • Update expected output
  • Document azure issues

@vercel
Copy link

vercel bot commented Feb 26, 2026

@ameba23 is attempting to deploy a commit to the Flashbots Team on Vercel.

A member of the Team first needs to authorize it.

@ameba23 ameba23 marked this pull request as draft February 26, 2026 11:18
--expected-measurements=https://measurements.buildernet.org \
--out-response=builder-cert.pem
cargo install --git https://github.com/flashbots/attested-tls-proxy attested-tls-proxy
# optionally add --tag <version number of latest release>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately there isn't a way to tell cargo to use the latest published release when installing from git rather than crates.io. This would be an argument to publish this to crates.io - but then we have the issue that crate versions do not [currently] necessarily match release tag versions.

@ameba23 ameba23 marked this pull request as ready for review February 26, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant