Since we added deterministic salts in #247 , it's much better and easier for users to complete a registration (send name_firstupdate after a previously sent name_new, or if the name_new was sent from a different computer, etc.).
For the name_new transactions that were sent pre #247 era, we need a way to remove them from the GUI and mark their corresponding addresses as such. Otherwise, they will remain as pending in a wallet forever and ever. We might automate (for users that restore from seed) if name_new was sent more than n blocks in the past computed from current height, don't even list it in history as Pre-Registration. Otherwise, if name_new was sent recently allow Electrum-NMC to finish the registration (send name_firstupdate) if salt was deterministic, otherwise have a GUI button / option to remove such forever stuck / lost transactions from the wallet.
This is leftover in #237 , but that also includes the deterministic salts idea so closing that in favor of this one.
Since we added deterministic salts in #247 , it's much better and easier for users to complete a registration (send name_firstupdate after a previously sent name_new, or if the name_new was sent from a different computer, etc.).
For the name_new transactions that were sent pre #247 era, we need a way to remove them from the GUI and mark their corresponding addresses as such. Otherwise, they will remain as pending in a wallet forever and ever. We might automate (for users that restore from seed) if name_new was sent more than n blocks in the past computed from current height, don't even list it in history as Pre-Registration. Otherwise, if name_new was sent recently allow Electrum-NMC to finish the registration (send name_firstupdate) if salt was deterministic, otherwise have a GUI button / option to remove such forever stuck / lost transactions from the wallet.
This is leftover in #237 , but that also includes the deterministic salts idea so closing that in favor of this one.
Possibly related: #162