Skip to content

Conversation

MoeMahhouk
Copy link
Member

📝 Summary

As part of the buildernet-playground. Orderflow proxy sender is run outside alongside builder-hub. So to facilitate running all orchestrated in the playground, we need an image of orderflow proxy sender binary to be built and pushed as well

📚 References


✅ I have run these commands

  • make lint
  • make test
  • go mod tidy

@MoeMahhouk MoeMahhouk requested review from bakhtin and metachris March 25, 2025 22:23
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-receiver
images: |
${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-receiver
flashbots/tdx-orderflow-proxy-receiver
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we want to remove the tdx prefix, as this will/can be used for other tees too.

maybe buildernet-orderflow-proxy, or just orderflow-proxy 🤔

Copy link
Member Author

Choose a reason for hiding this comment

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

I removed the prefix. But I left the suffix because there are two images one for receiver and one for sender.

with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-receiver
images: |
${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}-receiver
Copy link
Contributor

Choose a reason for hiding this comment

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

I think GHCR only allows images for the specific repo name, but not if they have such a suffix (which is also why the release CI step failed last time). Maybe we only push to Docker Hub?

Or a single image that can be used for both sender and receiver?

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.

2 participants