git.iko.soy/bridge
on edf00a4 help sign in
bridge/README.md
151 lines 5.5 kB history raw
1# Bridge
3[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
5An application for interacting with Azimuth.
7## Usage
9### Requirements
11Python 3.7.2
13### Instructions
15#### Install
171. [Download a release](https://github.com/urbit/bridge/releases)
182. Unzip it (`bridge-$version.zip`)
193. Open up your command line interface (Terminal on MacOS, Command Prompt on Windows)
204. `cd` into the `bridge-$version` directory
22Follow the instructions below to run Bridge.
24#### Run Bridge
26If you plan to authenticate and sign transactions with a Master Ticket, BIP39 mnemonic, Ethereum private key, or keystore file:
281. `cd` into the `bridge-$version` directory
292. Run `python3 -m http.server 5000 --bind 127.0.0.1`
303. Navigate to http://localhost:5000 using a web browser to access Bridge (we recommend using Firefox or Chrome)
32#### Run Bridge with Ledger support
34If you plan to authenticate and sign transactions with a [Ledger](https://www.ledger.com/), Bridge must be serving over HTTPS on localhost. This requires self-signed certificates. To do this:
361. Install [mkcert](https://github.com/FiloSottile/mkcert)
372. If you're using Firefox, additionally install [nss](https://github.com/nss-dev/nss)
383. Install a local certificate authority via `mkcert -install`
394. From the `bridge-$version` directory, run `mkcert localhost` to generate a certificate valid for localhost. This will produce two files: `localhost.pem`, the local certificate, and `localhost-key.pem`, its corresponding private key
405. Run `python bridge-https.py`
416. Navigate to https://localhost:4443 in a web browser to access Bridge
43### Verify checksums
45To validate your downloaded file's integrity, compare the lines in checksum.txt to SHA-256 hashes of the `bridge-$version` directory's contents.
47- On MacOS: `shasum -a 256 -c checksums.txt .`
48- On Linux: `sha256sum -c checksums.txt .`
49- On Windows: Go into the `build` directory and verify files individually with `CertUtil -hashFile [file_name] SHA256`
51## Development notes
53### Install / Build
55Clone the repo, and use a simple `npm install`. You can then use a `npm run
56build` to create an optimised static build (serve it with e.g. [serve][serv]).
58### General notes
60For development, use `npm run pilot` to get going after a `npm install`. This
61will boot up a Ganache node in the background, deploy the Azimuth contracts to
62it, and fire up a local webserver. Bridge will be served on `localhost:3000`.
64Note that one of our dependencies itself depends on a library called
65`handle-thing` which breaks under the Ledger support requirements (see below)
66on node 11.1.0, so make sure you're using some other node version.
68You can use [nvm](https://github.com/creationix/nvm), for example, and do:
70```
71$ nvm install 11.0.0
72$ nvm use v11.0.0
73```
75before running `npm run pilot`.
77### Useful accounts
79The ecliptic owner is the only account that's able to create galaxies, so
80it's a good place to get started. On the testnet, it's the address:
82```
830x6DEfFb0caFDB11D175F123F6891AA64F01c24F7d
84```
86You can authenticate as it using the following mnemonic:
88```
89benefit crew supreme gesture quantum web media hazard theory mercy wing kitten
90```
92Under that mnemonic, Ganache will also auto-populate the following accounts
93with 100 ETH:
95```
960x6deffb0cafdb11d175f123f6891aa64f01c24f7d
970xd53208cf45fc9bd7938b200bff8814a26146688f
980x7b2a2d51e4d8fac602e20a5f6907ff9fbd88e1fd
990xf48062ae8bafd6ef19cd6cb89db93a0d0ca6ce26
1000xf84a77aeb351c49dfa87e805a659d2daddff7606
1010x167e357cf8b845370d0d408f9b389b66185b7b5b
1020xcbecf3abc9878f07afc851aead2d8f1c436cc71d
1030x0afc0c3f4eeea500871f464ca71eef5e54a9af36
1040x6d654ef2489674d21aed428e8a4ad8ca4820f125
1050x218f6f87683db546ad47a5dc8b480e5a9b694866
106```
108To play around with any of these, authenticate using the same mnemonic, but
109use a custom HD path of `m/44'/60'/0'/0/1`, `m/44'/60'/0'/0/2`, and so on.
111### Initial development state
113You can also tweak a couple of things to change your development state
114somewhat (say, for example, you want to start on the points list screen, instead
115of having to re-authenticate whenever you make a change or refresh the page):
117* The `.env.development` file contains environment variables that you can
118 provide to the application when it's running in development. You can access
119 them via `process.env.REACT_APP_<whatever>`.
121* The `componentDidMount` method of the Bridge component in `src/Bridge.js`
122 can be tweaked for setting your initial state. You can provide a specific
123 wallet, network type, and so on.
125### HTTPS
127For development, you can enable HTTPS on localhost without a certificate for
128Chrome by pasting the following into the URL bar:
130```
131chrome://flags/#allow-insecure-localhost
132```
134In Firefox, you may need to allow connecting to the unsecured local node
135websocket. Do this by going to `about:config` and setting the
136`network.websocket.allowInsecureFromHTTPS` flag to `true`.
138Additionally you need to run with the `HTTPS` environment variable set to
139`true`. Note that `npm run pilot` will handle this automatically.
141### Releases
143To generate a release `bridge-$VERSION.zip` file, use a simple `npm run
144release`.
146This will pack the build directory together with the README, `bridge-https.py`
147script, and also generate a set of checksums for the build directory. You can
148verify the checksums on e.g. OS X via `shasum -c checksums.txt`.
150[rele]: https://github.com/urbit/bridge/releases/latest
151[serv]: http://npmjs.com/package/serve