---
# System prepended metadata

title: Web wallet beta testers

---

Welcome everyone to the beta testers group! We are excited to have you here and look forward to your feedback.
Please feel free to share your thoughts, ideas, and suggestions with us.


### Current state

NOVA will include:
- Bitcoin on-chain & off-chain actions on Bitcoin Testnet
- EVM on-chain actions on Ethereum Holesky testnet
- Wallet page
- Channel page
- Transactions page
- Settings 
- Dark/light mode 

NOVA doesn't include:
- Lithium 
- External signer
- Welcome screen
- Lightning channel backup options
- Channel Rental manager
- any DEX functions 


#### Wallet interactions
- Send
    - Bitcoin
        - on-chain :heavy_check_mark: 
        - off-chain via invoice / node address  :heavy_check_mark: 
    - EVM
        - on-chain :heavy_check_mark: 
        - off-chain :x: 
- Transfer
    - Bitcoin
        - to on-chain :heavy_check_mark: 
        - to off-chain :heavy_check_mark: 
    - EVM
        - to on-chain :x: 
        - to off-chain :x:
- Receive
    - Bitcoin
        - on-chain :heavy_check_mark: 
        - off-chain :heavy_check_mark: 
    - EVM
        - on-chain :heavy_check_mark:
        - off-chain :x:

- Channels
    - Bitcoin
        - Open :heavy_check_mark:
        - Close :heavy_check_mark:
    - EVM
        - Open :x:

Please check out this testing template for a complete overview: https://docs.google.com/spreadsheets/d/1wAHF67t_KKchOzfFB53koYkoTOpzqFjG1I8Qng-7DW8/edit?usp=sharing

### Lithium
Lithium will be Hydranet's off-chain state technology for all chains except Bitcoin. 

Different EVM State channel solutions, like Connext’s Vector, the Raiden Network, and Plasma, all have different benefits, but also various shortcomings. 

For instance, the Connext Vector protocol doesn’t allow multiple routing nodes, which is a necessity for a future multi-hub architecture in the Hydranet DEX Network. Hydranet’s Lithium protocol aims to overcome these issues and enable faster, multi-hop off-chain payments.

We have achieved the first round of fee optimization and are currently implementing the updated version into the wallet backend, aiming for early April 2024.


### Reporting issues

While the devs will participate actively in the discussions, if we do not respond for quite some time, feel free to ping **Thierry** as he will be responsible for the reportings

To report an issue we kindly ask you to follow a specific format to help us gather the necessary informations in the least amount of times. We have two different type of issues that can be reported

Every release we will publish a changelog informing you what bugs / features have been resolved in it.

#### Bugs

For bugs we will ask you to fill the dedicated template below. When reporting a bug please verify if it has already been reported/acknowledged. 

We will provide you a list of the current known/reported issues so if you happens to have the same problem, only inform us referecing the issue number, ie: *#132* and any other differents details that you may find useful.

When reporting a bug, alongside of filling the template acordingly, we would kindly ask you to provide us the logs present in the console at the moment of the error(s) alongside of the time + timezone it happened.

**Where are the logs located**
Logs aren't stored within your machine this time since it's an online application. To find the logs you must open *the developer console (see #reset my cache section to know ho to open it)*

Two type of logs can be found:
- debug (the blue rectangle)
    - information that we may provide to help us debug/gather more informations 
- errors
    - raw errors outputed usually by the backend

We kindly ask you to provide each time the logs of the both types.

As in the core dex, sometimes logging can be overwhelmed with a lot of noise, so please if you are able to identify what cause this error we kindly ask you to open the console first and click on the :no_entry_sign: sign to clear the console and then execute the action.


![Screenshot 2024-03-08 at 22.19.48](https://hackmd.io/_uploads/SyMB-bY6T.png)


#### Features requests / enhancements

Feel free to request them, but we can't guarantee to give a suite of all features requested, they will be discussed internally.

### How to access

LINK: https://hydranet-wallet.netlify.app/
PW: hydranet04032024

Don't share the URL or password, if we detect sharing, we will have to close this testing round.

### Help

If you run into any weird behaviors, such as really long syncs, Repetitive global node error, please reset your cache.

#### Reset my cache

1. Open the developer console within your browser *([how to find the console in my browser](https://balsamiq.com/support/faqs/browserconsole))*
2. On the top of the opened console look for the ***Application*** tab, if you don't find it directly, you must click on the two chevrons `>>` to find this section.
3. Find and click on the ***Storage*** list item, then click on ***Clear site data***
4. Give it a good window refresh.
![Screenshot 2024-03-08 at 22.04.00](https://hackmd.io/_uploads/HJHlRxKT6.png)

---- 

### Templates

#### Bug


**1. Steps to reproduce**
Explain the steps required to reproduce the issue, including any setup required to reproduce it. No need to include too much information on this section, just the steps.

*Example*
*1. Login with a new wallet*
*2. Open the Channel tab*
*3. Click on the dropdown in the table*
*4. Clicking on Force close*

**2. What is expected?**
*I expect that my channel change state to Force Close*

**3. What is actually happening?**
*Nothing, the channel stays as active*

**4.System Info**
- On mobile with Chrome: v122.0.6261.112

**5. Any additional comments?**
e.g. some background/context of how you ran into this bug.

Find here the debug log:

Find here the error log:

Here is a screenshot of the error or a loom video showing it's not working

---

#### Feature request

**1. Description**
A clear and concise description of what you think would be an helpful addition to the application, including the possible use cases and alternatives you have considered. If you have a working prototype or module that implements it, please include a link.

**2. Additional context**
If applicable, add any other context or screenshots here.

-----