You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary or problem description
Plugins/extensions can be used to index NEP17 and NEP11 transactions. However, this only works for NEP-specific transfers. Other transactions, such as vote, deploy, etc., aren't returned. The only alternative is to use Dora or create a custom indexer.
Do you have any solution you want to propose?
An RPC endpoint should be used to retrieve all transactions where the user is the sender.
Questions:
Should the endpoint return transactions where the address is not the sender but appears in a notification? (when it's a transfer recipient, for example).
Should this be added to the existing plugins or do we need a new one?
Where in the software does this update apply to?
Plugins
RPC (HTTP)
The text was updated successfully, but these errors were encountered:
Summary or problem description
Plugins/extensions can be used to index NEP17 and NEP11 transactions. However, this only works for NEP-specific transfers. Other transactions, such as vote, deploy, etc., aren't returned. The only alternative is to use Dora or create a custom indexer.
Do you have any solution you want to propose?
An RPC endpoint should be used to retrieve all transactions where the user is the sender.
Questions:
Where in the software does this update apply to?
The text was updated successfully, but these errors were encountered: