Wallet713 on Windows 10
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
vs-w713
README.md

README.md

Join the chat at https://gitter.im/vault713/wallet713

Discord logo

Wallet713 on Windows 10. Grin logo

vs-w713

Runs on Docker Desktop for Windows or Mac.

Credits: @grigio @hashmap @ignopeverell @kim0 @quentinlesceller @ravidio

Windows 10 Setup

Hyper-V is a requirement for Docker Desktop. Hyper-V requires:

  • Windows 10 Enterprise, Professional, or Education.
  • 64bit CPU with Second Level Address Translation (SLAT)
  • CPU support for VM Monitor Mode Extension (VT-c)
  • 4GB RAM (minimum)
  • Virtualization Technology enabled (BIOS)

Windows 10 Home can be upgraded to Windows 10 Pro. Settings > Update & Security > Activation

Getting Started

Run Windows PowerShell as Administrator.

Press Windows+X > Windows PowerShell (Admin)

In the following sections; text in command boxes should be pasted into PowerShell (Admin). Right click to paste clipboard, hit Enter.

  • Enable Hyper-V, then reboot:

    • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

VirtualBox won't work with Hyper-V enabled. You can toggle Hyper-V, using Hyper-V Switch by Yves Goergen.

Prepare Windows 10

Download vs-w713 GitHub repository:

  • PowerShell defaults to TLS 1.0 (cryptographically weak) - GitHub requires TLS 1.2:

    • [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
  • Pull repository:

    • Invoke-WebRequest -Uri "https://github.com/mi1b/vs-w713/archive/master.zip" -OutFile "\vs-w713.zip"
  • Extract repository:

    • Expand-Archive -LiteralPath \vs-w713.zip -DestinationPath \

Setup Docker Desktop

During installation choose Linux containers. Docker will start automatically and is running when this icon whale appears in the notification area.

  • Right click on the whale icon > Settings > Shared Drives > Tick C (or whichever drive letter you installed Windows on).

  • As Docker needs to mount files, it requires access to the Windows filesystem. Docker will ask for credentials; use your normal Windows password.

  • Run Windows PowerShell (Admin)

  • Check you're connected to Docker:

    • docker version
  • Check Docker can pull and run images:

    • docker run hello-world

Build the Container

  • Navigate to work directory:

    • cd \vs-w713-master\vs-w713
  • Build container images from Dockerfile context:

    • docker build -t my/wallet713 .

Building the container images will take 10-15 minutes on a fast PC. When the container is successfully built, you'll receive a SECURITY WARNING. Windows' filesystem can't mark a file as executable. As you're building a Linux container in a Windows client, all files are marked executable by default (don't worry, just do it).

Run the Container (Opens Wallet713)

  • Run the container and open Wallet713:

    • docker run --rm --name wallet713 -ti -v $PWD/data:/root/.wallet713 my/wallet713 wallet713
  • Make a new wallet:

    • init
  • Write down your recovery phrase and stash it somewhere safe.

  • Lists available Wallet713 commands:

    • -h
  • Close Wallet713 and the container:

    • exit
  • If anything weird happens (not saying it will) you can remove the container:

    • docker rm -f wallet713
  • To start Wallet713 again, navigate to the work directory and run the container:

    • cd \vs-w713-master\vs-w713
    • docker run --rm --name wallet713 -ti -v $PWD/data:/root/.wallet713 my/wallet713 wallet713

Whatever happens to the container doesn't matter. You can delete the container, all the images, and uninstall Docker. Your Wallet713 data remains in the \vs-w713-master\vs-w713\data folder and is safe.

Things You Should Know

Types of data Microsoft gleans via Windows 10:

  • Name and contact
  • Credentials
  • Demographic
  • Interests & favourites
  • Payment
  • Usage
  • Contacts & relationships
  • Location
  • Content

README

Send memes / get help: mi1b@protonmail.com