I am trying to send coins from Bob to Namebase, but I get an error message:

"Something went wrong, please try again."

Any ideas?

version 0.2.3 of Bob wallet (using Windows OS)

Use the version that includes the patch for invalid post-import balances.

Currently, errors surfaced from the main process don't display actual error message. We should change this: errors from the main process should render the error message.

This can be implemented by sending an error object rather than a concatenated string on errors in the RPC layer.

I believe the last column on the right should say "Bid + Mask" not just Mask - I've placed a few bids now and just from looking at the transactions, it looks like either this column should say "Bid + Mask", or we should load subtract the bid amount before displaying.

WDYT, @mslipper @chikeichan ?

Please check on your end with bids you've placed: if this turns out to be a one-time bug, I'll try a few more cases to repro.

Describe the bug
After sending some HNS from Bob Wallet to Namebase.io, a tx was generated as usual, but has been stuck in pending for over 10 hours now. When I look it up on HNScan, the following message appears: "Looks your connection to a node is offline. Want to try a different network?".

https://hnscan.com/tx/70a1466c5970339f468852a6c798091ee66ebc482e2ce5ab9477ede92da5fcc8

To Reproduce

Generate an address on Namebase.io, send to that address from Bob Wallet.

Desktop (please complete the following information):

Windows 10
Chrome Version 81.0.4044.138 (Official Build) (64-bit)

Expected Behavior

I have had success using this screen before, so I won't get into more detail here. The bid should successfully be placed. See below.

Current Behavior

Steps to Reproduce

Note: it has worked in the past, and consistently works when closing the app completely, re-loading it, re-entering password, and going directly to the name via the watchlist.
i.e. here is a recording of it working.

It failed when I was mucking around with the watchlist, adding and removing stuff, and then attempting to bid.

Beyond that, not sure how to repro. Will add more details here as it happens more. Beyond that, not sure - let me know if you have ideas.

Context (Environment)

macOS, v0.2.6

Logs

skipping, let me know if you want them.

Screencap

see above

Auctions with active bids on them are not displaying any bid history on my local client. I confirmed bids by simply comparing against Namebase.

Expected Behavior

1. Search for domain dpos
2. The list of bids should be displayed.

Current Behavior

1. Search for domain dpos
2. No bids are displayed, but bids verified to exist at https://www.namebase.io/domains/dpos

Context (Environment)

• OSX Mojave 10.14.5
• Latest v0.2.8 .dmg
• Network: Mainnet

Logs

• Exported bob-debug.log but it's empty

Screencap

image

Currently, Bob runs HSD in in single-worker mode without bcrypto, which makes synchronizing the full blockchain take ages already. Ideally we should use HSD with multiple workers and the native backend.

Expected Behavior: date display should be a rough estimate, more clear (tooltip that described expected date based on block time?), or removed (if hard to estimate, unnecessary)
Current Behavior: date display is static, to Feb 3rd 2020

I am using the latest version of Bob as posted on Telegram, on this date.

hi team
what are the tcp/udp ports to open on a firewall to make bob wallet work?
regards

Currently it only affects transactions sent from the send interface, but could be set in settings panel and applied to all covenant transactions as well.

Running 6b15a2c built for OSX.

If hsd is already running on mainnet when you launch Bob, you get the familiar, easy-to-understand error:

However, I've been working on hnsd and had it running as my computer's resolver on mainnet (running as root with --rs-host=127.0.0.1:53). When I launched Bob this morning I got a much more terrifying prompt:

Shutting down Bob, shutting down hnsd, then re-launching Bob worked around the issue. My wallet, watchlist, all data, etc - everything is fine.

Some errors tell users they must register their name, but Bob doesn't literally have any Register buttons -- maybe "manage my domain" should say "Register my domain" if it hasn't been registered yet?

Currently, zapping a transaction requires users to use the CLI. Since it's likely that transaction fees will vary significantly in the early days of the network, it'd be helpful if users could zap transactions directly from the UI.

I'm thinking some kind of drop-down menu on the accounts screen with a 'Zap' menu item should be sufficient. When 'Zap' is pressed, a confirmation modal should appear explaining how zapping works and how it isn't guaranteed that the transactions won't be mined.

Will close #99.

Current Behavior

Once you send a transaction, there is a confirmation page. But, there is no link to for the user to click and see their pending transaction on HNScan. This would make it so the user doesn't have to hop back to their transactions page to open it up quickly in a browser window (as most do).

Suggested Behavior

Add a link under the confirmation text "To see your transaction on HNScan, click here[]."

Note: This is a fantastic wallet, and I look forward to using it more as it continues to improve. Incredible work.

Multiple times using Bob-0.2.6.dmg I copied the seed phrase correct only for the program to shake and tell me it's wrong.

I figured out you can't have a space after the last word. This needs to be fixed to provide a better user experience. Thank you!

Since it can take a good long while for synchronization to complete during initial setup, it would be really helpful UX wise to be able to get some idea of how things are progressing, and to help distinguish broken/stuck from just taking a while to finish. I presume it's feasible to fetch the network's current block height from hsd before it's fully caught up, and you could track sync progress relative to that, if I understand correctly.

Furthermore, it'd be nice to see synchronization status while the wallet is locked, since that seems to happen pretty quickly and isn't end-user configurable. I don't need to go to the trouble of fetching the passphrase from my vault each time if I'm just trying to check on whether sync is done yet.

Expected Behaviour: when adding things to my waitlist using the filled heart icon, I expect to be able to come back to that page and see a consistent state.

Current Behaviour: it doesn't always reflect the true state, I can add something, search for something else, come back, and it looks as if the name is not on my waitlist. I've also seen the inverse, where I've added a name, moved to search for another name, and then lost the active state.

Right now when you look up "Bob Wallet" on Google, there is no description displayed for Bob Wallet indicating anywhere that it's a wallet GUI wrapper for HSD, nor that it can be used for auctions. Could you all add this information? I think it would aid more in the project's discovery...

Screenshot

Not sure if this is intended - suggest we remove or complete this feature.

I had my TLD sent to my HNS wallet managed via Bob Wallet. Will it be possible to send out my TLD from Bob Wallet in the near future?

Suggestion

A Telegram user (Cassandra Shi) suggested support for multiple wallets at once, so users don’t have to logout and import other phrases, which eventually can cause issues like WatchOnly addresses filling up and forcing a rm rf of the application data (this happened to me personally).

Also, native support for utilizing a ledger with the app similar to MyCrypto would be excellent as well.

When Bob receives a single TX with more than one output to a Bob address, the UI only displays the value of one of the output coins.

Expected Behavior

The UI should indicate the total amount received by all outputs to the wallet of a TX.

Steps to Reproduce

1. Obtain multiple receive address from Bob using CLI or reusing old receive addresses
2. Construct and send a TX with multiple outputs that pay to more than one address (ie with rpc sendmany)
3. Observe the value of the incoming TX displayed in the "Portfolio" pane of the UI

There is another related issue, in the "Received funds [from address]" message in the UI. A transaction could be sent from more than one address. I'm not sure if users care so much about the sender's address[es], I would personally almost prefer to see a TX hash there instead.

Expected behavior: open link to hs-airdrop in a new window, like all other links in the app.

Current behavior:

When creating a new wallet in Bob 0.2.6, it's stuck on the "Back up your recovery seed phrase" screen.

Expected Behavior

I should see the recovery seed phrase

Current Behavior

When I hit "I agree", it changes to "Loading..." but it stays greyed out and nothing happens.

Environment

Macos 10.15.3
Bob wallet 0.2.6

Encountered a timeout error on opening Bob UI on Windows 10.

The debug file was still getting populated.
(I had it running like that without realizing that it was still there.)

So, some the error messages I have from the log could be from later.
(The timestamps are the first time that type of error is encountered in that log)

In the log file, there were 10 types of error messages. Posting one of each type below.

Line 1215: [D:2020-06-12T02:46:34Z] (net) Error: Socket Error: ECONNRESET (173.255.209.126:12038)
Line 1260: [D:2020-06-12T02:46:39Z] (net) Error: Socket Error: ECONNREFUSED (45.79.108.139:12038)
Line 1266: [D:2020-06-12T02:46:42Z] (net) Error: Connection timed out. (138.68.224.26:12038)
Line 1292: [D:2020-06-12T02:46:43Z] (net) Error: Socket hangup. (96.126.101.79:12038)
Line 138699: Error: No DNS results.
Line 167308: [I:2020-06-14T21:18:42Z] (net) Error: Verification failure: invalid-covenant (code=invalid score=0 hash=...)
Line 167491: [D:2020-06-14T21:19:05Z] (net) Error: Peer is stalling (block). (172.104.214.189:12038)
Line 298217: [D:2020-06-16T03:48:44Z] (net) Error: Peer is stalling (verack). (45.79.134.225:12038)
Line 385502: [D:2020-06-16T12:35:14Z] (net) Error: Socket Error: EHOSTUNREACH (54.184.104.94:12038)
Line 433524: [I:2020-06-16T17:27:15Z] (net) Error: Verification failure: dust (code=nonstandard score=0 hash=...)

I thought I changed all these to say "open auction" instead of "open bid"

like...

...and...

...so it is easier to tell what version of Bob you're using.

I believe that the current UI implies to users that what we display in Bob is all of the bids, which is concerning because many of them might assume a name has not been bid on, and be surprised when they don't win a name that actually has other bidders.

Suggestions:

1. Lowest effort: specify with a header of "Your Bids" instead of "Bid History", and make some copy/tooltip changes to be consistent with that.
2. Link out to hnscan for the name, so people can see other bids.
3. Implement the ability to see other bids directly in Bob, and leave the headers/copy as-is.

My transaction has been pending for ages, and prevents me from spending those coins.

Expected Behavior

Transaction should complete or fail.

Current Behavior

Stuck in pending stage.

Steps to Reproduce

Context (Environment)

Logs

Screencap

See bcoin-org/bcoin#905

and:

$ npm audit
...
found 434 vulnerabilities (427 low, 4 moderate, 3 high) in 14496 scanned packages
  run `npm audit fix` to fix 411 of them.
  1 vulnerability requires semver-major dependency updates.
  22 vulnerabilities require manual review. See the full report for details.

We need to be extremely careful with dependencies since this application involves security, money, privacy, and cryptography. We shouldn't allow for dependency attacks which are rampant in the crypto ecosystem and especially with JS modules. The fact that we use react and redux with all their sub-dependencies exposes us to some risk.

I'm not sure the best course of action but we may want to consider git-committing node_modules.

Similar to #82 - likely fixable at the same time.

Note:

• Feb 3rd (this is #82)
• Even though we are not at the release block, it says it is available.
• Even though it says it is available, "Start Auction" is not greyed out.

My thinking is that we should make all of these things consistent.

Will need to dig this one out too, not sure what happened there.

Eeek.

Based on the latest information from hs-airdrop, the correct cut-off date for accessing HNS based on 15 or more followers is actually 2019-02-04 (not sure if this is February 4th 2019 or April 2nd 2019) but it is definitely no longer 2018-08-27 (clearly August 27th 2018) as is currently shown on the Windows version of the wallet. See the red highlighted area in the image below:

I'm a novice at Windows dev so I'm gonna just write a log of what I tried and see if I'm missing something obvious.

Windows 10
node 12.6.3
npm 6.14.4
git 2.26.2.windows.1

First this oddity on master branch, just one commit ahead of 0.2.9-rc2

362e3f5

$ git checkout master 
$ rm -rf node_modules/
$ npm i
npm ERR! code ENOLOCAL
npm ERR! Could not install from "node_modules\hsd\bcrypto@git+https:\github.com\bcoin-org\bcrypto.git#5c3e2b8b3f79d13e1b5c26be197708d0b9e5bcf9" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\turnt\AppData\Roaming\npm-cache\_logs\2020-06-05T17_35_28_000Z-debug.log

Next I checked out the release candidate directly:

120bd8f

$ git checkout tags/v0.2.9-rc.2
$ rm -rf node_modules/
$ npm i

This install runs fine, but threw this error when I tried run dev mode:

$ npm run dev

Windows pop up dialog:

An error occurred that prevented Bob from starting. Please quit and try again.

Error: A dynamic link library (DLL) initialization routine failed.
\\?\C:\Users\turnt\Desktop\work\bob-wallet\node_modules\bcrypto\build\Release\bcrypto.node
Stack: Error: A dynamic link library (DLL) initialization routine failed.
\\?\C:\Users\turnt\Desktop\work\bob-wallet\node_modules\bcrypto\build\Release\bcrypto.node
    at process.func (electron/js2c/asar.js:155:31)
    at process.func [as dlopen] (electron/js2c/asar.js:155:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:155:31)
    at Object.func [as .node] (electron/js2c/asar.js:155:31)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (internal/modules/cjs/loader.js:685:19)
    at require (internal/modules/cjs/helpers.js:16:16)
    at bindings (C:\Users\turnt\Desktop\work\bob-wallet\node_modules\loady\lib\loady.js:98:17)

Finally tried an even older commit when hsd was still pinned to a pinheadmz branch:

8d7698e

$ git checkout 8d7698e481b4beb92ff3e283ae0696daa9361dcf
$ rm -rf node_modules
$ npm i
$ npm run dev

Results in the same windows DLL error.

Also just to note that downloading the rc2 binary from github runs FINE as far as I can tell, albiet a bit slow wihtout the native crytpo...

Currently, Bob will display an opaque error if users attempt to reveal bids with missing nonces. Rather than displaying an error, we should instead display a warning on the auction screen that gives users the option to import the nonce graphically.

This user owns a high number of tlds and is noting that it can take >5mins to go from this state:

to this state:

throughout all this, one can't look at their existing domains.

Can we speed this up by caching some data locally, or do some sort of progressive loading where individual UI elements are still accessible? If the latter, a user can make changes even if bid status is not fully loaded for all names.

Bob requires a wallet passphrase on boot but (I think) doesn't ask for it again during wallet operations. I'm not sure how long the wallet passphrase stays in memory, but it seems like if the GUI is active long enough the passphrase is cleared and required to (e.g.) sendupdate.

Is there a way to pop your passphrase back in? Or we could pop open a dialog.

The value displayed as "Unlocked Balance" is the wallet's "confirmed" balance:

This is misleading because Handshake has an additional wallet property called lockedConfirmed which is the total number of coins locked in auctions. The real confirmed spendable balance of the wallet is balance.confirmed - balance.lockedConfirmed

Also can't seem to find the version we added in #124 but I think part of that PR was understanding that it would only apply to OSX?

• It can be quite hard to tell if Bob is stuck/experiencing a bug, or simply working as intended and taking awhile. This is especially true on slower computers.
• Suggestion: some kind of indicator on the top nav, cursor, or 'button state' progression that shows work is being done, so the user can contrast that with a bug / the need to re-start.
• Note: this was noticed when resetting my wallet - it hung for awhile and I wasn't sure if we should re-set it.

• While I work at Kyokan, please triage these issues (and all new ones from me from now on) as if they were coming from a regular user.

I replaced previous ver of Bob (0.2.8) and I do not have other instances of hsd running.

I get the following error on first run (see screencap below).

Steps to Reproduce

Context (Environment)

Mojave 10.14.6

Logs

Screencap

Bob may be randomly losing logged in state when updating names.

Expected behavior: it should be possible to continue updating without needing to log back in.
Current behavior: the reporting user get the following error after updating a handful of text records.

This issue really slows down the name update / domain management process, combined with #100 (related), it makes Bob basically unusable for this use case (managing names) beyond 1-2 names as one has to continue to close the app, re-load all bids, and publish more updates

If a user loses an auction, the REDEEM button is easy to find on both the auction page and on the "my bids" page. However, auction winners may not realize that they need to REGISTER to get the change back from the second-highest bid.

For auction winners, we can keep the REDEEM button on the page, and under the hood just send a REGISTER with null data '{"records": []}'. If a user has placed more than one bid (one of which is the winner) the usual REDEEM button could actually include this REGISTER output in the same transaction.

Currently, the auction screen displays only bids placed by the wallet user. We should change this so that all bids are displayed in a similar manner to Namebase.

This is an auction I won (with no extra lockup) where the 2nd highest bid was 50 HNS. Bob is showing the "update" as a 0-delta balance because it ignores change from all transactions. In the case of a register, the difference between the winning bid and the second highest is the change output!

oops sorry, will fix.

When importing an address with a non-zero balance, the wallet state says "Synchronized", but the balance remains at zero for up to 20 minutes.

This is shown within 1 minute of starting the app:

This is shown later: for me it took ~10mins, but I've heard it can take up to 30 mins from others.

@mslipper - we discussed this offline a few minutes ago; let me know if you need other info.

I've checked 3 auctions that are still in reveal: inan, ihn, and 0i.

Dates always look like this: 01/19/70