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
STX transactions are supported only when using Infura. When users switch to an alternative RPC URL, STX functionality reverts to a standard send transaction without any explicit notification, which might not be immediately clear to the user. This can lead to confusion as the user interface changes unexpectedly.
Additionally, users have reported an inability to edit the nonce value when connected to Infura, a feature that was accessible on other RPCs. This behavior aligns with the expected functionality when STX transactions are enabled, yet the rationale behind this limitation was not apparent to users.
To enhance clarity and user experience, it would be beneficial to introduce a notification or alert informing users that STX functionality is exclusive to certain RPCs.
Scenario
Design
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
Engineering (needed in most cases)
Design
Product
QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
Security
Legal
Marketing
Management (please specify)
Other (please specify)
References
No response
The text was updated successfully, but these errors were encountered:
sleepytanya
changed the title
Smart Transactions UI and nonce editing confusion on Ifure vs alternative RPC URLs
Smart Transactions UI and nonce editing confusion on Ifura vs alternative RPC URLs
Dec 30, 2024
sleepytanya
changed the title
Smart Transactions UI and nonce editing confusion on Ifura vs alternative RPC URLs
Smart Transactions UI and nonce editing confusion on Infura vs alternative RPC URLs
Dec 30, 2024
What is this about?
STX transactions are supported only when using Infura. When users switch to an alternative RPC URL, STX functionality reverts to a standard send transaction without any explicit notification, which might not be immediately clear to the user. This can lead to confusion as the user interface changes unexpectedly.
Additionally, users have reported an inability to edit the nonce value when connected to Infura, a feature that was accessible on other RPCs. This behavior aligns with the expected functionality when STX transactions are enabled, yet the rationale behind this limitation was not apparent to users.
To enhance clarity and user experience, it would be beneficial to introduce a notification or alert informing users that STX functionality is exclusive to certain RPCs.
Scenario
Design
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References
No response
The text was updated successfully, but these errors were encountered: