Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bitshares/bitshares-ui
Fully featured Graphical User Interface / Reference Wallet for the BitShares Blockchain
https://github.com/bitshares/bitshares-ui
bitshares bitshares-ui blockchain blockchain-wallet cryptocurrency javascript reactjs wallet web-app
Last synced: 3 months ago
JSON representation
Fully featured Graphical User Interface / Reference Wallet for the BitShares Blockchain
- Host: GitHub
- URL: https://github.com/bitshares/bitshares-ui
- Owner: bitshares
- License: mit
- Created: 2015-10-12T17:36:50.000Z (over 9 years ago)
- Default Branch: develop
- Last Pushed: 2024-04-14T17:41:13.000Z (10 months ago)
- Last Synced: 2024-04-15T01:59:12.344Z (10 months ago)
- Topics: bitshares, bitshares-ui, blockchain, blockchain-wallet, cryptocurrency, javascript, reactjs, wallet, web-app
- Language: JavaScript
- Homepage: https://wallet.bitshares.org
- Size: 47.4 MB
- Stars: 516
- Watchers: 78
- Forks: 569
- Open Issues: 437
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome-bitshares - BitShares-UI (Reference Wallet) - reference web wallet (ReactJS). (Utilities / Opensource Wallets)
- best-of-crypto - GitHub - 18% open · ⏱️ 15.05.2024): (Exchange-based Tokens)
README
BitShares-UI
============
[中文版](README_zh.md)
This is the reference wallet of BitShares Blockchain which connects to BitShares Blockchain nodes (*bitshares-core*).
This reference wallet is a browser based wallet, which means *your keys are stored locally* in your browser and *never leaves it* while using the wallet.
You should *never expose your keys to anyone* as transactions are signed locally before transmitting them to a node.
## Getting started
Building BitShares-UI browser based reference wallet depends on node version 16 using a non-root user.
On Ubuntu or macOS, the easiest way to install node is to use [Node Version Manager](https://github.com/creationix/nvm).
Install nvm according to your platforms recommendation and set the version
```
nvm install v16
nvm use v16
```
Once you have node installed, clone the repository using the following commands:
```
git clone https://github.com/bitshares/bitshares-ui.git
cd bitshares-ui
```
Before launching the UI you will need to install the packages using yarn on a non-root user:
```
yarn install
```
## Running the dev server
Once all the packages have been installed you can start the development
server by running:
```
yarn start
```
Once the compilation is done the UI will be available in your browser at:
`localhost:8080` or `127.0.0.1:8080`. Hot Reloading is enabled so the browser
will live update as you edit the source files.
## Testnet
By default bitshares-ui connects to the BitShares mainnet,
but it's very easy to switch it to the testnet.
To do so, open the UI in a browser, go to Settings, then
under Nodes, select the *Testnet* in the dropdown menu.
The UI will reload and connect to the testnet.
There is also a ready-made deployment directly connected to testnet
including account creation available [here](https://test.xbts.io/).
## Production
If you'd like to host your own UI somewhere, you should create a production
build and host it using NGINX or Apache.
In order to create a prod bundle, simply run the following command:
```
yarn run build
```
This will create a bundle in the ./build/dist folder that can be hosted with the web server of your choice.
### Installable (local wallet)
We use Electron to provide installable wallets, available for Windows, macOS and Linux Debian platforms such as Ubuntu.
There is a [GitHub Action available](https://github.com/bitshares/bitshares-ui/blob/master/.github/workflows/build-release-binaries.yml#L18) that shows all the steps necessary for this build.
This will compile the UI with some special modifications for use with Electron, generate installable binaries with Electron and copy the result to the root `build/binaries` folder.
### Docker
Clone this repository, run `docker-compose up` and visit localhost:8080
## Contributing & Coding style guideline
See [CONTRIBUTING.md](CONTRIBUTING.md)
## Code of Conduct
This repository has a Code of Conduct that should be followed by everyone.
Please read [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
**Please keep comments constructive and clean**
## BrowserStack
The BitShares UI is integrated with BrowserStack (https://www.browserstack.com) to allow manual compatibility testing across devices and browser versions. In the future we will switch to a automated Selenium testing framework.
## Release Branches
There are three branches that forms the current release process.
### Develop
All PRs should be pushed to the `develop` branch.
New commits are automatically deployed to this branch and published for review.
Available for browsing on https://develop.bitshares.org
### Staging (Current Release Candidate)
At the end of each milestone, `develop` branch is pushed to staging and forms the Release Candidate. The date of the RC forms the name, ie. `5.0.220214-rc1`.
Application breaking issues and bugs should be submitted to the issue tracker and PRs should be pushed to `staging`.
Available for browsing on https://staging.bitshares.org
### Master (stable)
When all major issues to the current RC are fixed, `staging` branch is released to the stable `master` branch.
Available for browsing on https://wallet.bitshares.org which is the official reference wallet for Bitshares.