Add more warnings about keeping computer on during name registration
See original GitHub issueUsers keep turning their computers off during the name registration phase. I think we can combat this in two ways:
- More warnings about this
- On browser restart we check to see if there is an active preorder and attempt to issue the second transaction if there is time before the
NAME_PREORDER
expires
This is a significant pain point for may users of our product and a significant negative experience right at the beginning of their relationship with it for those that run into the issue.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Windows registry information for advanced users
The Registry contains information that Windows continually references during operation, such as profiles for each user, the applications ...
Read more >How do I add a warning Logon message? - ITPro Today
Start the policy editor (poledit.exe); Open the default Computer Policy; Open the Windows NT System tree and then Logon; Put a tick in...
Read more >Manage warnings about unsafe sites - Google Chrome Help
You'll see a warning if the content you're trying to see is dangerous or deceptive. These sites are often called "phishing" or "malware"...
Read more >Uninstall Pop-up Ads program from your computer
STEP 3: Remove Pop-up Ads adware from your computer with AdwCleaner. The AdwCleaner utility will scan your computer and web browser for malicious...
Read more >Set separation alerts in case you leave a device behind in ...
Tap Devices at the bottom of the screen, then tap the name of your iPhone Wallet with MagSafe. Below Notifications, tap Notify When...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It is no longer required to keep the browser running for name registrations. The transactions are signed and queued up on a server for broadcast.
+1 to this.
We should also consider making the pre-order transaction optional in the next hard fork. If you’re concerned about front-running, check the box and pay 2x the miner fees to broadcast a pre-order. If you’re not, don’t and get zero conf with 1/2 the price.
Related: other parts of the browser fail when the user doesn’t have internet in unexpected ways: https://github.com/blockstack/blockstack-browser/issues/1077