375d5ec8c3
* Make it possible to explicitly disable discovery Discovery will be disabled in following cases: - if there are not bootnodes - v5 server will be disabled because there is no point in running it - if user defined in config NoDiscovery=true this value will be preserved even if we have bootnodes So, basically discovery will be always enabled by default on mobile, unless it is explicitly specified otherwise. When statusd is used current behavior is that discovery is disabled by default. I kept it in this change, but it would be better to change it. * Fix leftovers * Add wait group to peer pool to protect from races with p2p.Server * Change fields only when all goroutines finished * Turn off discovery after topic searches are stopped * Don't set period to nil to avoid race with SearchTopic * Close period chan only when all writers are finished |
||
|---|---|---|
| .github | ||
| .vscode | ||
| _assets | ||
| cmd | ||
| extkeys | ||
| geth | ||
| lib | ||
| logutils | ||
| metrics | ||
| notifier | ||
| profiling | ||
| services | ||
| sign | ||
| signal | ||
| static | ||
| t | ||
| timesource | ||
| vendor | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .gometalinter.json | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE.md | ||
| Makefile | ||
| README.md | ||
README.md
Status bindings for go-ethereum
Docs
Intro
status-go is an underlying part of Status - a browser, messenger, and gateway to a decentralized world.
It's written in Go and requires Go 1.8 or above.
It uses Makefile to do most common actions. See make help output for available commands.
status-go uses go-ethereum with some patches applied in it, located under vendor/ directory. See geth patches README for more info.
Build
There are two main modes status-go can be built:
- standalone server
- library to link for Android or iOS
Use following Makefile commands:
make statusgo(builds binary intobuild/bin/statusd)make statusgo-android(builds .aar filebuild/android-16/aar)make statusgo-iosandmake statusgo-ios-simulator(builds iOS related artifacts inbuild/os-9.3/framework)
In order to build and use status-go directly from status-react, follow the instructions in https://wiki.status.im/Building_Status, under the 'Building Status with the checked-out version of status-go' section.
Debugging
In order to see the log files while debugging on an Android device, do the following:
- Ensure that the app can write to disk by granting it file permissions. For that, you can for instance set your avatar from a file on disk.
- Connect a USB cable to your phone and make sure you can use
adb.
Run
adb shell tail -f sdcard/Download/geth.log
IDE Debugging
If you're using Visual Studio Code, you can rename the .vscode/launch.example.json file to launch.json so that you can run the app with the debugger attached.
Testing
To setup accounts passphrase you need to setup an environment variable: export ACCOUNT_PASSWORD="secret_pass_phrase".
Make sure the dependencies are installed first by running:
make lint-install
make mock-install
To test fully statusgo, use:
make ci
To test statusgo using a given network by name, use:
make ci networkid=rinkeby
To test statusgo using a given network by number ID, use:
make ci networkid=3
If you have problems running tests on public network we suggest reading e2e guide.
If you want to launch specific test, for instance RPCSendTransactions, use the following command:
go test -v ./geth/api/ -testify.m ^RPCSendTransaction$
Note -testify.m as testify/suite is used to group individual tests.