Faye Amacker

@ssanderson Thank you for opening this issue! I also prefer not to encode high-precision time into floating point. > All of these options are either lossy w/r/t the time's wall...

@ssanderson Yes, I am looking into issue #623 and waiting for the Go team to finalize the proposed API. Currently, if users want to encode time in ways that are...

> One other option that occurs to me looking at this again: what would you think about adding a TimeRFC3339NanoUTC option, with the same beahvior as the current TimeRFC3339Nano but...

I created a [notion doc](https://www.notion.so/flowfoundation/New-Service-Events-to-Upgrade-Execution-Stack-2a31aee123248028ba72e4819606a202) "New Service Events to Upgrade Execution Stack". It proposes new services events for upgrading components and execution parameters. It also outlines validation rules and examples...

Thanks for opening this issue. I will look into it.

For testing and benchmarks, we have been using this branch: - https://github.com/onflow/flow-go/tree/v0.33-atree-inlining

Closing as completed by this feature branch - https://github.com/onflow/flow-go/tree/feature/atree-inlining-cadence-v0.42

Good point Janez and bluesign. The bottleneck for migration duration has been the top few largest accounts. If the largest account is modified, we might not see much difference compared...

Maybe add memory usage to the benchmarks posted here: `B/op` and `allocs/op` columns.

> I assume it might be related to encoding/json/v2, though it's not clear how that ties into this CBOR library. Yes, "waiting-for-go-api" label is related to `encoding/json/v2` still being in...