Stepan Chekhovskoi

As i understood from the community discord, it is not a feature, it is a bug and developers are working on to make returning values from blockchain transactions possible. https://discord.com/channels/945856774056083548/946123778793029683/1029108132397453352

During my Aptos Education, I've created a module which wraps any tokens and in such way keeps them safe. I think it also could be a solution, however, it looks...

One more point may be: - Develop best practices of safe resource management -- provide a tutorial of how resources could be managed. Remind how access permissions are transmitted through...

I've created the article on medium to make users more conscious. It describes the steps which user should follow to keep funds safe. I think, Aptos Team should also provide...

As I know, the modifier does not exist for now. However, the function may not be marked `public` to prevent calls from other modules.

> I would suggest a custom field in `--run-types` that support a string to be executed: I like the proposal, would it be implemented in the near future? An ability...

> I remember some Curve code that ensures that a partial derivative must be negative and thereafter multiplies it by the sign (`-1`) to make it again a positive number...

I support the idea. Leafs double hashing is considered to be a best practice when generating any Merkle Trees and is implemented by default in [@openzeppelin/merkle-tree](https://github.com/OpenZeppelin/merkle-tree) generator. @Amxx I don't...

The only argument against I see is that for consistency reasons it is reasonable to apply the pattern for `multiProofVerify` function as well and it may be a bit more...

It looks like two sides of the same coin: - Usage of [@openzeppelin/merkle-tree](https://github.com/OpenZeppelin/merkle-tree) will cause double hashing on the smart contract side: `bytes32 leaf = keccak256(bytes.concat(keccak256(abi.encode(addr, amount))));` - Additional hashing...