You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
odb366 ad7a08cfa9 fix(submit-channel-layout): width of amount field matches expected output 6 years ago
.vscode first commit 7 years ago
app fix(submit-channel-layout): width of amount field matches expected output 6 years ago
flow-typed fix(flow): remove custom flow file 7 years ago
internals enhance(logging): Output webpack errors to the main log 6 years ago
resources enhance(comments): Refer to the standard github page for rpc.proto 6 years ago
test enhance(test): Drop pessimistic printing of logs that shouldn't be there 6 years ago
.babelrc build(electron): update to electron v2.0.2 6 years ago
.editorconfig first commit 7 years ago
.eslintignore Merge pull request #160 from Empact/enhance/lints 7 years ago
.eslintrc enhance(linting): Enable the eslint:recommended rules 6 years ago
.flowconfig fix(flow type): attempting to fix flow type errors 7 years ago
.gitattributes Disables text treatment of binary resources 7 years ago
.gitignore fix(gitignore): ignore resources/bin 7 years ago
.stylelintignore fix(style-lint): Bump stylelint and config to latest, fix lints 7 years ago
.stylelintrc first commit 7 years ago
.travis.yml ci(travis): disable security warnings 6 years ago
ADVANCED.md docs(advanced): remove redundant install steps 6 years ago
CONTRIBUTING.md Fix the slack invite link 7 years ago
LICENSE first commit 7 years ago
README.md Fix the slack invite link 7 years ago
appveyor.yml ci(travis): only install grpc once 6 years ago
package.json Merge pull request #428 from mrfelton/feat/electron-2 6 years ago
webpack.config.base.js build(webpack): update webpack to v4.x 6 years ago
webpack.config.eslint.js Removes unused code, adds proper semicolon rule and reduces lint errors 7 years ago
webpack.config.main.prod.js build(webpack): update webpack to v4.x 6 years ago
webpack.config.renderer.dev.dll.js build(webpack): update webpack to v4.x 6 years ago
webpack.config.renderer.dev.js enhance(logging): Output webpack errors to the main log 6 years ago
webpack.config.renderer.prod.js build(webpack): update webpack to v4.x 6 years ago
yarn.lock Merge pull request #428 from mrfelton/feat/electron-2 6 years ago

README.md

screenshot
Zap

Zap is a free Lightning Network wallet focused on user experience and ease of use, with the overall goal of helping the cryptocurrency community scale Bitcoin and other cryptocurrencies.

The UI for Zap is created using Electron + React + Redux.

We have an active slack channel where you can join the discussion on development, design and product.

Installing

Note: If you would like to use a full bitcoin node, please see the advanced usage page.

Download the latest release for your appropriate OS and follow the instructions below.

macOS

Once you have the .zip file downloaded, simply double click on the file to unzip.

Navigate to the newly extracted folder, then drag-and-drop the Zap.app file to the Applications folder.

Unmount the image and navigate to Applications folder.

Finally, double click on the Zap.app file.

Windows

Once you have the .exe file downloaded, simply double click on the file.

Linux

Once you have the .zip file downloaded, simply double click the file to unzip or run the following command:

unzip file.zip

You have the option to either install Zap through the .deb or .AppImage files.

.deb File

Once you have the .deb file extracted, you can install Zap by double clicking on the file or through the dpkg command:

sudo dpkg -i file.deb

If this is your first time installing zap, you may have some unmet dependencies. This can be resolved with the following command:

sudo apt-get -f install

To run Zap you can either navigate through the GUI or run the following command:

zap-desktop

.AppImage File

Once you have the .AppImage file extracted, you can either double click the file or by running in the cli:

./file.AppImage

Advanced Usage

If you would like to install from source or run a full bitcoin node, please see the advanced usage page.

Contributing

If you would like to help contribute to the project, please see the contributing guide.

Q & A (Quality and Assurance)

Note: If you are having problems with Zap, please report the issue in GitHub or on slack with screenshots and/or how to reproduce the bug/error.

A good product not only has good software tests but also checks the quality of the UX/UI. Putting ourselves in the shoes of a user is a very important design principle of Zap.

Example User Stories

User wants to connect to a peer

User wants to open a channel

User wants to create a payment request

User wants to make a payment