Evgeny Kuzyakov
Evgeny Kuzyakov
In the following line the contract reuses the Set, by using the same prefix for all users https://github.com/near-examples/NFT/blob/bbafd2195d4f6253d84a8cced560fda10fd51d35/contracts/rust/src/lib.rs#L81 The prefix should uniquely identify the collection. Right now it uses the...
Since a lot of contracts depend on each other, we should implement CI to make sure one doesn't break another.
***Describe the bug*** A clear and concise description of what the bug is. Sometimes near-shell shows a nonce conflict error. I think it happens because near-shell tries to resubmit the...
***Describe the bug*** Can't schedule a function call that takes arguments not in JSON format, e.g. raw string. ***To Reproduce*** ```bash near call exchange.m0 exchange_deposit 'USER_123' --accountId= ``` ***Expected behavior***...
***Is your feature request related to a problem? Please describe.*** Current API supports the following: ```bash near delete ``` It's really easy to mess up the arguments and delete the...
***Is your feature request related to a problem? Please describe.*** Currently all transactions by near-shell are done without confirmations. With coming upgrades and renames, it's sometimes easy to mess up...
***Is your feature request related to a problem? Please describe.*** I don't feel secure using near-shell with real tokens because of unencrypted keys stored in files. ***Describe the solution you'd...
Most of the code (all) that uses `try_to_vec` will never have an error from Borsh. Right now it's confusing which error a function can throw and some of them don't...