Ben

I'll revert file separation, then merge on monday. I'll also raise a discussion in github about that (I personally prefer not to have `mod.rs` files, but I'll raise it in...

With the caveat that I don't have much history with scripting, here are my two cents : Whichever way we go, I advocate for having some sort of strongly enforced...

@damip I was given a short brief on this by @AurelienFT. In your own time, could you please fill out the issue in more detail. I am prioritising #3275 for...

For the time being, i'm going to make things naive to versioning, but here's the idea right now. ```rust enum CtxAddress { User(UsrAddress), // wraps `Hash` SC(SCAddress), // wraps slot,...

That's my understanding, with the caveat that, for the time being, I'm not taking into consideration the versioning, so: ```rust struct SCAddress { slot: Slot, idx: u64, read_only: bool }...

...and I'll be coordinating with @AurelienFT and @Leo-Besancon with respect to versioning. My understanding around versioning, is that we are shooting for an approach where we use a macro of...

First look at something that sorta works: #3452 something that just occured to me. the smallest varint is `I32`, and we can probably pack the variant prefix and version into...

Does "read-only" need to be encapsulated in the `SC` address itself? I would think not, as an SC "location" is independant of if it's read/write or not. ...or could there...

I've made some more progress on the address-enum PR: - Things are currently split between `UserAddress` and `SCAddress` - There is the `AddressTrait` trait, which uses generic monomorphisation to handle...

#3475 cleans simplifies things. Made the mistake of trying to go complicated too early. I think I at least learned a few things along the way. Under the hood, there...