Excessive step during transaction status view
alexauroradev opened this issue · 1 comments
At the moment, when operating the interactive mode with the following flow: near -> transaction -> view-status -> <tx_hash> an additional parameter is asked -- signer account ID.
This parameter is probably omitted during the execution of the call, since even with incorrect signer account ID, the CLI returns the correct tx data. Most probably, this step can be omitted.
This step reflected the nature of NEAR Protocol, which requires the requester to specify the signer account id, so the RPC server can route the request to the shard where the transaction is stored. Today, with all the shards tracked by all nodes, it does not make a difference, in the future, I believe CLI will be able to offset this problem by querying all the shards for the user behind the scenes, so we decided to remove this explicit requirement for CLI users.