Skip to content

Conversation

@OisinKyne
Copy link
Contributor

@OisinKyne OisinKyne commented Jun 19, 2025

Problem to be solved

I wanted to see how much work it was to support an aztec full-node in the stack. Here's what I found:

Screenshot 2025-06-19 at 19 22 24

  • Their charts aren't packaged into a chart museum. So i had to fork them locally. Could be added to the obol helm chart repo, or maybe they could add a chart museum to their CI and publish them to github pages.
  • I had to throw out this volume mount, it wasn't found. https://github.com/AztecProtocol/aztec-packages/blob/next/spartan/aztec-node/templates/statefulset.yaml#L151
  • I had to figure out they ran on sepolia. That took longer than I admit.
  • I had to add sepolia as a supported network on eRPC. For now trusting publicnode.com, without any light-client safety from helios.
    • actually eRPC wasn't working, I had to go direct to public-node.com, something to debug.
  • I had to expose a host port for them. Maybe networkMode: host might have worked instead, but i didn't want to test it when i figured manually setting a port and supplying --host to obolup would work.
  • I had to create a values file for the chart to override the needed pieces. Maybe an aztec hosted example would suffice if there was a solution for the nodePort thing.

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