Max Zaver

> I don't think I understand. How is burning all prepaid gas different from a transaction that uses all prepaid gas in the current setting? The fact that we have...

> I think I understand your argument now. Let's say that we burn all prepaid gas. Now if an attacker wants to execute the same attack they have to saturate...

>It seems that you suggest that in the current system attacker can abuse without paying for unused CPU. In a system where blocks are filled in based on prepaid gas...

@vgrichina Our top goal is to make sure our protocol works and is not abusable. We cannot have a node which has convenient DevX but is abusable. For example, we...

> I don't see how we break it when we use attached gas to estimate how many transactions can be processed. Seems like we have the opposite problem – we...

@frol this is a proposal to whitelist certain ZK-competent auditors so that we can proceed with auditing projects like speeding up Aurora bridge with ZK compression. This is a good...

Adding @evgenykuzyakov 's comment: > It would be great to add an option to a function call action to be able to enforce contract_hash . > I think we can...

We can do both. Every contract method can be exposed in both camel and snake case, it is a tiny modification to near-sdk-rs and will have a negligible effect on...

Specifically, currently for each impl method `my_method(&self, args..)` near-sdk-rs generates method `my_method()`. It should generate three methods: `_my_method()`, ` my_method() { _my_method() }`, and `myMethod() { _my_method() }`. It already...

Closing in favor of https://github.com/near/near-sdk-rs/issues/209