feat: integrate eigenda using hokulea library #12
Conversation
|
It seems like the requirements to switch over the pipeline in Kailua are quite small, which is great! I get the goal of separating out the added functionality here, but I'm curious if you've considered multiple risc0 guest programs and no feature gating? Having the Kailua client just work out of the box w/ alt da without special build instructions sounds appealing imo. |
|
@hashcashier so you mean having a separate eigenda-specific client. I had not considered that approach no. You would still need a whole separate build/run/test pipeline for that other client though. And I feel like there would be more code duplication overall than the feature-based approach? But happy to try it out if you think that could be nicer. |
|
How about let's move fast and get this to a working state first however you see fit then we can discuss refinement later? |
This is still a WIP, but opening this PR to give a sense of the approach we're thinking, to get feedback, and to see whether you guys would be willing to upstream this. I've made all eigenda code behind a feature flag, so should have 0 impact on your binary and toolings.
Our https://github.com/Layr-Labs/hokulea library is an extension to kona to support eigenda blobs.