Skip to content
This repository has been archived by the owner on Sep 26, 2024. It is now read-only.

Explorer didn't log account transaction if receiver id is a param of function call #1053

Open
cuongdcdev opened this issue Jun 22, 2022 · 1 comment

Comments

@cuongdcdev
Copy link

cuongdcdev commented Jun 22, 2022

This happens because of the account, which is the receiver_id parameter of the function call. For now, the explorer only shows the transactions when the user is the receiver or the signer of the transaction. Please resolve this behavior. Example: The account did not get tx recorded: https://explorer.near.org/accounts/hibaryx.near The TxId above account got: https://explorer.mainnet.near.org/transactions/EWFCLoQXrSDhkxijoDnux8yCicUqZRoKP5vE4eKKp8Ti

@frol
Copy link
Collaborator

frol commented Jun 22, 2022

@cuongdcdev Thanks for bringing this up! It is indeed unfortunate, but in general case there is no way we can index actions based on the arbitrary function call arguments. However, we are working on supporting FT/NFT standards as a special case. Stay tuned, we plan to release it by the end of July

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants