c8f9dad554
## What has changed? I've introduced to the public binding functionality that will compress and decompress public keys of a variety of encoding and key types. This functionality supports all major byte encoding formats and the following EC public key types: - `secp256k1` pks - `bls12-381 g1` pks - `bls12-381 g2` pks ## Why make the change? We want shorter public (chat) keys and we want to be future proof and encoding agnostic. See the issue here https://github.com/status-im/status-go/issues/1937 --- * Added basic signature for compresspk and uncompresspk * Added basic encoding information * make vendor * formatted imports for the linter * Reformatted imports hoping linter likes it * This linter is capricious * Added check that the secp256k1 key is valid * Added test for valid key * Added multiformat/go-varint dep * Added public key type handling * Added key decompression with key type handling * Added handling for '0x' type indentifying * Added more robust testing * Less lint for the linting gods * make vendor for bls12_381 * Added bls12-381 compression tests * Added decompress key expected results * Refactor of typed and untyped keys in tests * Lint god appeasment * Refactor of sample public keys * Implemented bls12-381 decompression * gofmt * Renamed decode/encode funcs to be more descriptive * Added binary bindings for key de/compression * Refactor of func parameters gomobile is a bit tempermental using raw bytes as a parameter, so I've decided to use string only inputs and outputs * gofmt * Added function documentation * Moved multiformat de/compression into api/multiformat ns * Moved multiformat de/compression into api/multiformat ns * Changed compress to serialize on API |
||
|---|---|---|
| .. | ||
| README.md | ||
| multiaccount.go | ||
| response.go | ||
| response_test.go | ||
| status.go | ||
| status_geth.go | ||
| status_nimbus.go | ||
| types.go | ||
README.md
Mobile
Package mobile implements gomobile bindings for status-go. Current implementation servers as a drop-in replacement for lib package.
Individual bindings and their descriptions are available in status.go.
The primary consumer of this package is status-react project.
The framework name is generated from the package name, hence these things are done intentionally:
(1) this package's name isn't equal to the directory name (statusgo vs mobile respectively);
(2) this package name is statusgo and not status which produces the right framework name.
Usage
For properly using this package, please refer to Makefile in the root of status-go directory.
To manually build library, run following commands:
iOS
gomobile bind -v -target=ios -ldflags="-s -w" github.com/status-im/status-go/mobile
This will produce Statusgo.framework file in the current directory, which can be used in iOS project.
Android
gomobile bind -v -target=android -ldflags="-s -w" github.com/status-im/status-go/mobile
This will generate Statusgo.aar file in the current dir.
Notes
See https://github.com/golang/go/wiki/Mobile for more information on gomobile usage.