Yeah I hear you. I am trying to encode what cdk gives me. Not even sure if I can or should customize the keyset right now. That could be a different rabbit hole.
Not even sure if keyset is needed. Maybe we can use one pubkey per epoch and let the share difficulty speak for itself? This will have implications when splitting or combining ehash tokens. We are straying from the cashu spec now, which may be inevitable but do we want to rush into it?
It's a tradeoff of customizing cdk to suit hashpool needs or customizing Sv2 to suit cdk. At this point, I don't know the answer. Need to try a bunch of shit and feel my way around the problem to get a good grasp on it.
Recreate the data strives in Sv2 then create Into and From traits between the two structs
Please Login to reply.
Structs**
Yep that's the plan. Cdk wants the whole keyset to construct a proof so I need to send it from the mint to the proxy on startup. This is where I'm struggling with the encoding. I'll get it eventually. It's all bytes at the end of the day.
