Illia Polosukhin
Illia Polosukhin
Currently by default it creates a full stack application. Which means that if building for existing app - need to deal with all the contract stuff. Ideally something like --frontend...
Currently because we don't know the size of the buffer inside the `deserialize` method we can't predict if the length is way too large and should error out (right now...
This is factory that allows to deploy any contracts that are stored inside it. Anyone can store a contract and anyone else can use hash to deploy it with various...
# Description NEAR Protocol uses human-readable account names. This allows for much better user experience for regular blockchain use cases. We also expect that these accounts will be used across...
Currently our tooling only knows to look for lockup contracts under *.lockup.near But this means that only NF can deploy those. This can be easily made permissionless by creating a...
Because NEAR runtime doesn't have a way to query access keys that current account has, contract must have an internal set of keys. This would also allow to configure different...
There are usually few pieces of data about the pool that people are interested in: - Logo (IPFS hash or url) - Description - Website URL (or IPFS hash) This...
Currently if view call fails, the error object just contains a string that contains something like this: ``` { "error": "wasm execution failed with error: FunctionCallError(HostError(GuestPanic { panic_msg: \"08c379a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000114552525f5355425f554e444552464c4f57000000000000000000000000000000\" }...
Calling any transaction with too much attached gas leads to unclear error: > near call testnet create_account '' --gas 1000000000000000000 --accountId illia Leads to error `Error submitting heartbeat: InvalidTxError: {}`...
`WalletConnection.requestSignTransactions` function has unclear signature, as it's requires transaction with signer_id and signer_pk. Developers are not sure what to fill in when signing a transaction. We should document usage of...