2019-11-21 16:19:22 +00:00
|
|
|
module github.com/status-im/status-go/protocol
|
2019-07-17 22:25:42 +00:00
|
|
|
|
2019-10-14 07:53:38 +00:00
|
|
|
go 1.13
|
2019-07-17 22:25:42 +00:00
|
|
|
|
2019-11-23 17:57:05 +00:00
|
|
|
replace github.com/ethereum/go-ethereum v1.9.5 => github.com/status-im/go-ethereum v1.9.5-status.6
|
|
|
|
|
|
|
|
|
|
replace github.com/gomarkdown/markdown => github.com/status-im/markdown v0.0.0-20191113114344-af599402d015
|
|
|
|
|
|
|
|
|
|
replace github.com/status-im/status-go/eth-node => ../eth-node
|
|
|
|
|
|
2019-12-09 10:36:14 +00:00
|
|
|
replace github.com/status-im/status-go/whisper/v6 => ../whisper
|
2019-12-09 10:06:04 +00:00
|
|
|
|
2019-07-17 22:25:42 +00:00
|
|
|
require (
|
2019-09-02 09:29:06 +00:00
|
|
|
github.com/cenkalti/backoff/v3 v3.0.0
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
github.com/ethereum/go-ethereum v1.9.5
|
2019-07-26 07:17:29 +00:00
|
|
|
github.com/golang/protobuf v1.3.2
|
2019-11-15 08:52:28 +00:00
|
|
|
github.com/gomarkdown/markdown v0.0.0-20191113114344-af599402d015
|
2019-10-09 14:22:53 +00:00
|
|
|
github.com/google/uuid v1.1.1
|
2019-07-26 07:17:29 +00:00
|
|
|
github.com/jinzhu/copier v0.0.0-20190625015134-976e0346caa8
|
2019-09-26 07:01:17 +00:00
|
|
|
github.com/lucasb-eyer/go-colorful v1.0.2
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
github.com/mattn/go-pointer v0.0.0-20190911064623-a0a44394634f
|
2019-08-27 12:04:15 +00:00
|
|
|
github.com/mutecomm/go-sqlcipher v0.0.0-20190227152316-55dbde17881f
|
2019-07-17 22:25:42 +00:00
|
|
|
github.com/pkg/errors v0.8.1
|
|
|
|
|
github.com/russolsen/transit v0.0.0-20180705123435-0794b4c4505a
|
2019-11-04 10:08:22 +00:00
|
|
|
github.com/status-im/doubleratchet v3.0.0+incompatible
|
2019-10-14 14:10:48 +00:00
|
|
|
github.com/status-im/migrate/v4 v4.6.2-status.2
|
2019-11-23 17:57:05 +00:00
|
|
|
github.com/status-im/status-go/eth-node v0.0.0-20191120100713-5053b0b6835b
|
2019-12-09 10:36:14 +00:00
|
|
|
github.com/status-im/status-go/whisper/v6 v6.0.0
|
2019-11-04 10:08:22 +00:00
|
|
|
github.com/stretchr/testify v1.4.0
|
|
|
|
|
github.com/vacp2p/mvds v0.0.23
|
2019-11-25 20:16:00 +00:00
|
|
|
go.uber.org/zap v1.13.0
|
Move to protobuf for Message type (#1706)
* Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage`
* Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text.
* Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not.
* Change the various retrieveX method to a single one:
`RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is:
`Chats`: -> The chats updated by receiving the message
`Messages`: -> The messages retrieved (already matched to a chat)
`Contacts`: -> The contacts updated by the messages
`RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away.
2019-12-05 16:25:34 +00:00
|
|
|
golang.org/x/crypto v0.0.0-20191119213627-4f8c1d86b1ba
|
2019-07-17 22:25:42 +00:00
|
|
|
)
|
