ade
ade
> Hey @oxade what's the status of this PR and how it's aligned w/ @sblackshear's proposal? @kchalkias will close this for now and see how the Pay API evolves.
> Thanks! I have a few questions: > > * Why do we need u128 for the size? Simply because it was the largest deterministic size. I'm flexible on this....
> > Good question: we will have a max TX size, so this size dependent pricing serves as one way to bound TX sizes. It's also the fee for validators...
> > > > I lean towards the argument for flat fee because we already charge for TX size (which includes the package being published), and object storage. Plus the...
@lxfind @tnowacki This PR has diverged a lot. I will make another one with the comments addressed and close this out. However for the unanswered questions: they're tracked [here](https://github.com/MystenLabs/sui/issues/4405)
Calibration PR is [here](https://github.com/MystenLabs/sui/pull/4411)
Two items left: 1. Deterministic sizing: we will use @aschran solution 2. Calibration formulae: I will add this in subsequent PR
Maybe I missed this in the comments but what's wrong with hashing the generated bytecode? It really doesn't change much between versions. And if its changing often, this is a...
I think the easiest place to do these might not be in the explorer but in the full node (or the event subsystem) which has a more complete view of...
Working on this. Will sync with @randall-Mysten on how to best document estimation.