Feature request: ability to clear Send Idempotency IDs and force send #1162
(1) Ability to clear all of these Idempotency IDs with one command
If it was deemed more secure to make (1) a CLI
@argakiig in production, no. In fact, these features I'm suggesting shouldn't be used in production at all.
In development, I have a local database table storing transaction IDs. These are auto-increment, starting at 1 and counting up. When I flush the database and start over with ID 1, this means if I want to use the send idempotency feature, I need to start with a fresh
One way I've circumvented this issue is by using GUIDs instead of standard integer IDs on transaction records in DB, and that works fine, but this got me thinking about development niceties especially if these idempotency IDs will be required in the future.
My naive opinion is that local node state like wallets, accounts, and idempotency IDs should be decoupled from public block storage. In such a scenario we'd have