b1bart

> Deferred transaction aborts: there's a ton of analysis work into verifying new features are safe when used inside deferred transactions. We're trying to reduce that load. Actually, I think...

> The WASM linear memory of any instantiated accounts persists over the lifetime of an action (and this choice is to enable optimizations in the implementation). This sounds like a...

> This can be done using the existing dependencies mechanism of protocol features. Would we really say that consensus upgrade Y which adds a completely unrelated features "depends" on disabling...

> I see an advantage to keeping an Alternatives section. Going with my theme of features that enable vs restrictions that enforce. I see great benefit in promoting these out...

> A possible approach is for new features to assert they aren't being used from within deferred transactions. I'm more concerned with non-obvious dependencies for instance when some common system...

> I too would love to eventually see this as well so that we can simplify the code base. then we've come full circle 😄 Perhaps the reasons I thought...

yep on second read I caught that the call itself returns the size of the return value. I'm okay with that. I guess I will leave this open to invite...