This doesn’t work at least on Brave Browser.
When starting to type in the input it goes back to 0.
Also the actual swap in the hub doesn’t go through for me. It doesn’t go beyond “Signing transactions…”, no error in the console though.
EDIT: Nevermind, both work now.
I’m getting the errors shown below and can’t import my login access file onto the testnet wallet
Edit:
I’m running Safari 13.0.4 and Chrome 86.0.4240.183 on macOS 10.15.2 (Catalina)
This image shows the same error on Chrome:
Thanks for your feedback. We’ll look into this and come back to you as soon as we know more about the origin of the issue 
After some testing i’m unable to reproduce your issue even on the same browser & os version. So either you have something preventing you from connecting to the websocket (like an adblocker, some VPNs, etc…) or maybe blockstream.info is denying the connection or the proxy is unable to connect to it for some reasons.
Is the issue still persisting on your end @rraallvv ? If so, when did it start to occur approximately? (to try to match it with something we could’ve pushed to the testnet).
I see. I tried to make a BTC/NIM swap like about a week ago but it didn’t go through, I checked the browser log and there it was the error about the websocket connection failing to connect to blockstream.info. Then during the past weekend I tried to log out from the Testnet wallet but couldn’t get logged in again, and the same error was showing up in the logs. I’m going to try disabling anything that could be potentially blocking the connection and report back. Thanks for taking a look at the issue.
@Matheo I disabled Avast’s Web Shield and all browser extensions but the problem persisted, only after I used a proxy I was able to log onto the walled.
I was able to make some NIM/BTC swaps, only found a couple of minor issues as shown in the image.
The text showing the current amount of BTC overlaps the button to open the swap window.
Dragging the slider outside the swap window and releasing the button causes the swap window to be closed.
Thanks for your feedbacks @rraallvv We’ll work to fix those as soon as possible
Regarding your issue, we don’t have any kind of IP blocking in the wallet or in the electrum websocket. So i guess either it comes from blockstream.info denying connections from your location or IP, or you have some network problems on your end (DNS? / Firewall?).
Did you tried to use the testnet wallet in other conditions / on another device (smartphone, tablet, another pc, another internet connection, etc…) to see if it works?
I’m using a DLS modem, I’m not sure but it could have some custom firmware or presets that could be blocking the connection, also the ISP I’m using seems to be blocking some websites, but some websites are blocking connections from my location too, so I’m not sure. If I get a chance to test the wallet with a different IPS I’ll report back. Thanks so much.
In case anyone is having issues logging onto the Testnet wallet like those I described a few messages above and the error shown below is appearing in the logs, try using some of the DNSs listed here. In my case Google’s and Cloudflare’s didn’t work and I ended up adding all of them, just in case, but it did the trick.
[Error] WebSocket connection to 'wss://electrum.nimiq.network:50002/?token=testnet:electrum.blockstream.info' failed: WebSocket is closed before the connection is established.stuff is broken on chromium/linux i get wss errors in console
When you have many funded NIM addresses and no funded BTC address the NIM/BTC component in the swap modal gets a bit mangled.
Edit: In this case I have 13 nim addresses 11 of them are funded with roughly equal amounts. and 1 BTC address with a zero balance
Note: I tested this on mainnet using Chrome 87 on MacOS
If I pull the lever all the way to the left it increases the size of the input fields so that the NIM/BTC value components are outside of the modal
Other case (from testnet Chrome 87) 13 addresses, 5 funded, 1 btc addresses funded
Thanks for your feedback @negativebenefit . We’ll look into those issues and come back to you once it’s fixed
Thanks for your feedback @negativebenefit . We’ll look into those issues and come back to you once it’s fixed
Seems to be fixed already, not sure if you did anything or if it’s some kind of random glitch with the CSS (maybe was a cache issue?)
There is some users that actually have css cache issue like what you reported earlier. It can be that, but i’ll still take a quick look at it just to be sure.
Hi
I have now tried to connect Bitcoin in the new wallet and it works well, and as always Nimiq web team shows their excellence by design and visual beauty. Great job. A couple of ideas to perhaps improve it more.
First off, being a late night dev and often working in partial darkness, switching from one or other of my applications or websites into Nimiq is a painful experience for the eyes. Make a Dark Mode setting, please
Second. The whole experience with connecting a Ledger X device (using cable to connect to USB, not Bluetooth which doesn’t work) was very complex and somewhat counterintuitive. This was so much non-Nimiq and therefore surprising. Usually everything you guys come up with is simplistic and intuitive to use. Perhaps have another iteration on the hardware wallet integration, it can be improved.
And merry Xmas in advance
