Jeff Burdges
We should overall the blake3 interface to make blake3 `Vec`s act like child trees, so we could've efficient edit proofs into large blake3 `Vec`s. If done right then large blake3...
I opened a discussion on the blake3 repo https://github.com/BLAKE3-team/BLAKE3/issues/279 which may tell us if many people think all that would be useful.
It's also unclear how much we care, like how often someone needs a big bunch of bytes
We could've a thinner substrate change @bkchr but then have an external repo that implements the runtime code for the curve models and curves themselves. I didn't ask for this...
Ahh, you've even got the models there, cool.
Around `Vec`, I'd likely have written something like this, maybe up-streamed it to arkworks, but not sure the best choice. In this, we risk reallocations, but that's likely better than...
We do have equal chunk sizes when sending elliptic curve points or field elements, which makes sense for arkworks, but breaks in general, and thus feels fragile here too. I...
I'm now happy with this I think.. I'd like @swasilyev to take one more look too. We could migrate this to BLST in future, but frankly I think speeding up...
What would a separate repo look like? Can we have test nets running it? At a high level, these are the "opinionated" decisions I made here: - We do no...
It's anyways fine if we avoid this being reachable on kusama or polkadot by whatever means, like doing a separate test net. We should imho avoid doing bespoke calls for...