707221954f
This change adds adds an ability to use different source of time for whisper: when envelope is created it is used to set expiry to track when envelope needs to be expired This time is then used to check validity of the envelope when it is received. Currently If we receive an envelope that is sent from future - peer will get disconnected. If envelope that was received has an expiry less then now it will be simply dropped, if expiry is less than now + 10*2 seconds peer will get dropped. So, it is clear that whisper depends on time. And any time we get a skew with peers that is > 20s reliability will be grealy reduced. In this change another source of time for whisper will be used. This time source will use ntp servers from pool.ntp.org to compute offset. When whisper queries time - this offset will be added/substracted from current time. Query is executed every 2 mins, queries 5 different servers, cut offs min and max and the computes mean value. pool.ntp.org is resolved to different servers and according to documentation you will rarely hit the same. Closes: #687 |
||
|---|---|---|
| .github | ||
| .vscode | ||
| _assets | ||
| cmd | ||
| extkeys | ||
| geth | ||
| lib | ||
| logutils | ||
| metrics | ||
| 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.