All the actions in the app with the same level importance are represented as buttons (Login, Create wallet).

I think we should replace the Log Out link with a button.

The light wallet and Sheikah use a different way to import and export a wallet from an xprv.

According to @parodyBit, we check against the hash and not the password itself, so:

• if a wallet already exists, the password needs to be the same and with the same hash
• if it is a new install and no wallet exists, the XPRV needs to have been exported from the light wallet
• if it was exported from Sheikah, it will not work

Example of what's happening, also provided by @parodyBit:

import 'dart:typed_data';

import 'package:pointycastle/digests/sha256.dart';
import 'package:pointycastle/digests/sha512.dart';
import 'package:witnet/crypto.dart';
import 'package:witnet/src/crypto/hd_wallet/extended_private_key.dart';
import 'package:witnet/utils.dart';

void main() async {
  testEncryptedXprv();
}

void testEncryptedXprv() {
  String mnemonic =
      'abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon about';
  String password = 'password';

  Xprv xprv = Xprv.fromMnemonic(mnemonic: mnemonic);

  /// Sheikah Compatible XPRV
  print(xprv.toEncryptedXprv(password: password));

  /// Light Wallet Compatible XPRV
  print(xprv.toEncryptedXprv(password: hash(password)));
}

/// we store the hash of the password in the local database.
String hash(String password,) {
  final pbkdf2 = new PBKDF2(
    blockLength: 128,
    iterationCount: 2048,
    desiredKeyLength: 64,
    digestAlgorithm: new SHA512Digest(),
  );
  String digest = bytesToHex(SHA256Digest()
      .process(pbkdf2.process(data: Uint8List(0), passphrase: password)));
  return digest;
}

To fix this incompatibility, we just need to:

• To export, the user needs to enter the password because we are only storing the hash of the password
• To import, we need to decrypt with the password provided in Sheikah when the user exported the wallet.

Review current copies and update placeholders.

The copies that need to be updated can be found here: #45

• Fix generateAccount error in api_crypto
• Implement button in receive-transaction view to generate new account

• Create reusable layout for every step
• Disclaimer view
• Seed phrase view
• Confirm seed view
• Password view
• Identify wallet view

Currently, there is a mismatch between the font specified in the design and the one we use in the code. Our reference should be what is in the Figma design.

IMO, adding a name to your wallet shouldn't be mandatory. We should create a default name for the wallet, such as wallet-$index, so the user can create or import the wallet without typing anything here.

Add pagination for transactions

• Decide a better name than Witnet Light Wallet
• Rename repository with the new name

• Show sending transaction in transaction list. Currently the information is not shown until it is accepted.
• Update mined transaction status to confirmed. Currently the status does not change.

Export xprv:

• Fix import wallet from xprv
• Add export xprv feature

General settings:

• Add select unit

The native top bar in the app is not using the theme.

Allow selected estimated fee in create vtt form

Right now, the only way to close the wallet selector is by clicking again in the Identicon. The expected behavior to close it's swiping down the selector and clicking outside it.

Tasks

• Close the wallet selector clicking outside
• Close the wallet selector swiping down

• Fix mobile margins
• Fix main layout to fit mobile height (avoid scroll in welcome view)
• Fix transaction info in transaction list to fit mobile width

Add library to generate identicons based on the wallet id

• [ ] Discuss current logo
• Discuss naming
• [ ] Implement New logo
• Replace logo in the UI

To be able to facilitate the testing of the the latest changes we have to add a GitHub action that triggers a daily build and generates:

• APK for android
• ? for iOS
• Desktop

User validation from formz.dart model in create wallet forms.

Add a select to set the preferred wit unit

Avoid using wallet name as ID

When we build the Light Wallet for Android and execute the .apk, the import wallet is stuck while connecting the Block Explorer. The error that appears in the logs is: "Failed host lookup: 'witnet.network'".

The solution for this is to add the following line to the AndroidManifest.xml:

  <uses-permission android:name="android.permission.INTERNET" />

Regarding the iOS build, I don't know if we have the same problem. In case we experience the same problem the solution could be the one provided Flutter docs:

  <key>com.apple.security.network.client</key>
  <true/>

• Linux
• MacOS
• Windows

• Transaction List
• Value Transfer Transaction
• Data Request Transaction

• Address list
• Generate address flow

Unexpected behavior

1. Unlock your wallet using a wrong password
2. The confirmation button will be disabled
3. Enter a different password
4. The confirmation button is still disabled, with no chance for retry

Expected behavior

The confirmation button should be re-enabled as soon as the password is edited.

Or maybe it should never be disabled at all. I think that's common practice. Let's double check what other apps do and follow that.

In the send VTT form, the amount and fee fields should have the following validation rules:

Amount

• Required
• Format. It should be a valid number. Right now, accepts .1 and 1. as valid
• Length. Max number of decimals is 9
• Length. Max whole-number is 10

Fee

• Required
• Format. It should be a valid number. Right now, accepts .1 and 1. as valid
• Length. Max number of decimals is 9
• Length. Max whole-number is 10

When I try to import a wallet using an xprv, the app stops working in this view:

And I get the following error:

E/flutter (19095): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: FormatException: Invalid number (at character 1)
E/flutter (19095): 
E/flutter (19095): ^
E/flutter (19095): 
E/flutter (19095): #0      int._handleFormatError (dart:core-patch/integers_patch.dart:124:7)
E/flutter (19095): #1      int.parse (dart:core-patch/integers_patch.dart:50:14)
E/flutter (19095): #2      ApiPreferences.setCurrentWallet (package:witnet_wallet/util/preferences.dart:26:21)
E/flutter (19095): <asynchronous suspension>
E/flutter (19095): #3      CryptoBloc._cryptoInitializeWalletEvent (package:witnet_wallet/bloc/crypto/crypto_bloc.dart:161:5)
E/flutter (19095): <asynchronous suspension>
E/flutter (19095): #4      Bloc.on.<anonymous closure>.handleEvent (package:bloc/src/bloc.dart:226:13)
E/flutter (19095): <asynchronous suspension>
E/flutter (19095): 

Add loading state to PaddedButton
Add loading state in export xprv and login forms

• Create VTT Form step
• Review VTT step

[TBD]

We have to release 0.0.1 to distribute mainly between the team members and get feedback. After fixing these errors, we can release a new version for the community.

• web
• android
• iOS

Create a website to download witnet_wallet binary

When we select an input to add some text, the keyboard slides up and coverts the input text:

The expected behavior is to scroll down to show the input while writing.

This problem occurs in:

• Welcome view
• Send view

Update "to several addresses" copy in transaction card info:

"The “To” thing is not very helpful right now, because it will show “several addresses” for every transaction that used a change address. Given the BIP-32 nature of all Witnet wallets, we can safely assume that the first output is the actual send, so we should use that address here.

(As a matter of fact, we are doing exactly the same to derive the true value of the transaction — we’re substracting the value of the outputs that point to our own internal addresses)"