chore: explicit re-exports from amaru-kernel
Signed-off-by: Roland Kuhn <[email protected]>
Signed-off-by: Roland Kuhn <[email protected]>
Signed-off-by: Roland Kuhn <[email protected]>
Signed-off-by: wcatz <[email protected]>
Signed-off-by: KtorZ <[email protected]>
Signed-off-by: KtorZ <[email protected]>
Signed-off-by: KtorZ <[email protected]>
Duplicates are allowed in there, and silently swallowed. Signed-off-by: KtorZ <[email protected]>
This is a big and unpleasant commit; but vastly necessary. Multiple things are going on, but before I explain further: why are we doing this? We have decided to move away from Pallas. There are various reasons motivating this and a proper EDR will come ASAP. The gist being that we ended up working more _around_ Pallas than _with_ Pallas. The amount of duplication and workaround have reached a point that makes this switch a lot more painful than I'd have liked. In short, here's what's happening: - The kernel top-level `lib` has been broken down into many smaller modules; the general strategy being "one type per module", with associated methods and traits. - This shall allow us to now migrate in a more incremental fashion from Pallas to Amaru's own kernel / prelude. And, importantly, to give more thoughts about the public API we want to expose; for us, but also for downstream consumers. - Few methods have been moved around, from the kernel to other places or vice-versa when it was relevant. - Many duplications were already addressed; sometimes requiring a bit of finesse, renaming and moving types around. Some heavy work remain in a couple of places such as the amaru-plutus & the script context, as well as the "memoized" sections, which needs to be promoted as the new defaults. Signed-off-by: KtorZ <[email protected]>
The block body hash wasn't really the bug I was originally after; and it seems like we've been doing it wrong since ... always. It's a bit comical that the one thing we forgot to verify was that blocks actually form a valid chain! This is totally missing from our ledger rules, and therefore, ended up going under the radar and the block body hash not being needed at all. The reason I added it here was simply because I created a regression test from one of the failing block on preprod, and thought it would be interesting to control the block hash. I am glad I did, but even more worried now. Signed-off-by: KtorZ <[email protected]>
Anything beyond trace is printed on stderr by default, as pretty log. So we ought to keep those logs under control. Signed-off-by: KtorZ <[email protected]>
demonstration for everything apart from the cardano module (which is huge) Signed-off-by: Roland Kuhn <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
* init react native * nextjs works * react native working * fix redirect URL * critical fixes * fix build error
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>
Signed-off-by: Chris Gianelloni <[email protected]>