75e0809f50
When sending messages in quick succession, it might be that multiple messages are batched together in datasync, resulting in a single large payload. This commit changes the behavior so that we can pass a max-message-size and we split the message in batches before sending. A more elegant way would be to split at the transport layer (i.e waku/whisper), but that would be incompatible with older client. We can still do that eventually to support larger messages. |
||
|---|---|---|
| .. | ||
| bridge | ||
| core/types | ||
| crypto | ||
| keystore | ||
| types | ||
| Makefile | ||
| README.md | ||
README.md
Abstraction for Ethereum node implementation
This package is a collection of interfaces, data types, and functions to make status-go independent from the go-ethereum implementation.
status-go is a wrapper around an Ethereum node. This package was created to have a possibility of selecting the underlying Ethereum node implementation, namely go-ethereum or Nimbus. The underlying implementation is selected using Go build tags.
typesandcore/types-- provide interfaces of node services, common data types, and functions,bridge-- provide implementation of interfaces declared intypesusing go-ethereum or Nimbus ingethandnimbusdirectories respectively,crypto-- provide cryptographic utilities not depending on go-ethereum,keystore-- provide a keystore implementation not depending on go-ethereum.
Note: crypto and keystore are not finished by either depending on go-ethereum or not providing Nimbus implementation.
How to use it?
If you have a piece of code that depends on go-ethereum, check out this package to see if there is a similar implementation that does not depend on go-ethereum. For example, you want to decode a hex-string into a slice of bytes. You can do that using go-ethereum's FromHex() function or use equivalent from this package and avoid importing go-ethereum. Thanks to this, your code fragment might be built with Nimbus.