Matthias Benkort

> why was it closed - what went wrong? Can I reuse the code? I think this is already pretty explicit from the PR comments? The suggested approach in the...

I've updated the original issue, providing more details on the items and clarifying a few interrogations.

Latest Ogmios is (in all likelihood) compatible already. I don't have any dates for the bundled image.

As far as I remember now, I did this on purpose. Specifically because, the redeemers & datums are actually re-encoded... I suppose this was to make the test case more...

Hey, thanks for the PR, that's an interesting idea to be discussed. The current implementation path however duplicates a lot of logic at every level of the compiler and doesn't...

Please refer to the following compatibility table between the compiler and the standard library: https://github.com/aiken-lang/stdlib?tab=readme-ov-file#compatibility

I believe there are use-cases for something like pallas-traverse and multi-era representations; especially if you're building indexers and apps that use historical data.

Thanks for the reply @scarmuega; > My concern is that I don't see the value of having both pallas-latest and pallas-traverse. To me, requirements 2 & 3 can be fulfilled...

> What's wrong with this api? where is the multiera bothering you? What would the difference be compared to a pallas-latest? The difference lies here: ```rs let block = MultiEraBlock::from(conway_block);...

> @scarmuega There's no dynamic dispatch in pallas-traverse, I think you're confusing terms. I am not; I didn't say that pallas-traverse had dynamic dispatch; I said that it's how one...