janedegtiareva

What amount of time should the signature be valid for? Making it last indefinitely/for extended periods of time is a security risk.

This is a duplicate of https://github.com/near/near-shell/issues/340

> So the output should be... > Error: GuestPanic [Error]: Smart contract panicked: panicked at 'Failed to deserialize input from JSON.: Error("missing field `owner`", line: 1, column: 88)', src/lib.rs:68:1 >...

Confirmed that adding engineStrict = true doesn't solve the problem.

Do we want to always ask for input if there are multiple account ids?

which node /usr/local/bin/node jane_nearprotocol_com@jane:~/near-shell$ which yarn /usr/bin/yarn jane_nearprotocol_com@jane:~/near-shell$ which np /usr/bin/np

quick design discussion: do we want to have the node version as a value that's available in Near object that's returned from nearlib connect? Pros: clients can implement whatever version...

I would definitely rewrite this as well. Can we try to explain it maybe as "fixed component" and "variable component" or something like this?

This is most likely a race condition on project load.

To fix, we need to either update to gulp 4 or not use gulp