Daniyar Itegulov

@akhi3030 yes, so this is what I meant by `action_receipt_id`. `sign_request_id` is indeed a domain-specific thing here. The idea is that `sign_request(...)` results into `Promise` which is what Rust SDK...

@akhi3030: having a timeout mechanism seems very reasonable to me. We can have a retry mechanism on the application level and even potentially subsidize it (e.g., set up a relayer...

Yes, what @volovyks suggests would be ideal. We have a comprehensive set of Rust ABI generation tests under https://github.com/near/cargo-near/tree/main/integration-tests/tests/abi; it might make sense to port them here as well. NAJ...

"Specify" as in use a specific version in the code instead of depending on latest or as in writing the version in README?

So that method is only called once by the entity that deploys the smart contract. That entity does not necessarily know all nodes information (their URL, id etc). With the...

FYI I briefly discussed tokenomics with Michel (the WIP design with slashable pots) and he said there might be some we could do with forward-secure signatures to have better security...

Here is a document written by Michel on forward security: https://docs.google.com/document/d/1a1ilRVGkDYoKn3WxAhTDUAy15XfbE9XWvr_zMJ_ai84/edit#heading=h.bqupaxg6kupz Unfortunately, there is no clear way of enforcing this behavior since there is no way of distinguishing a server...

Moving out of the sprint for now as it is unclear what is the best place for this to happen (see #206)

Not really, I am doing mainnet/testnet deployments manually for now

Great summary @ChaoticTempest! This ticket seems like it will be a bigger effort than expected, so let's create some subtasks here. I think we can start working roughly from the...