alnoki
alnoki
@lightmark Thanks for the clarification. Per our recent whiteboard discussion, all vectors are stored as a single blob in the global storage Merkle tree, and so the 4k figure is...
@runtian-zhou
@gregnazario Right now the Move CLI does offer this functionality: after running `move package test coverage`, then running `move package coverage summary` will print out a percentage for each file,...
> Summary of our follow-up discussion from yesterday: Refunding storage costs to the extent of negative gas fees introduces: 1. Inflationary events: if enough storage were to be freed up,...
Addressed by #5187
@movekevin @georgemitenkov the primary use case is for an order book application where each order has an ID number that encodes a serial GUID: if two users place limit orders...
@georgemitenkov you explanation seems right to me, for further context ill note that the order ID is simply price concatenated with the GUID. This way, an ask with price 1234...
> Thanks for further explanation. But it seems to me that you do read GUID in every transaction. When you assign it to an order ID, combining with price, you...
> Precisely. With this use case I do not think there is a way to get rid of such a sequential dependency, at least at the moment. Each new GUID...
@movekevin is there anyway that this could support Move script invocation? For example a single signatory posts a script on GitHub and submits the Move script bytecode into a waiting...