Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive step during transaction status view #279

Closed
alexauroradev opened this issue Dec 20, 2023 · 1 comment · Fixed by #280
Closed

Excessive step during transaction status view #279

alexauroradev opened this issue Dec 20, 2023 · 1 comment · Fixed by #280
Labels
enhancement New feature or request

Comments

@alexauroradev
Copy link

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.

@frol
Copy link
Collaborator

frol commented Dec 21, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants