Commit Graph

26 Commits

Author SHA1 Message Date
Richard Ramos cadc3998b8 fix_: a message might match more than one filter 2024-08-20 17:12:34 -04:00
richΛrd c68854299a
refactor_: remove unused code from wakuv2 () 2024-08-06 20:18:46 -04:00
richΛrd 20d6d4eb9a
refactor: extract missing messages logic to go-waku () 2024-08-06 14:49:26 -04:00
Prem Chaitanya Prathi 063756b4ed
chore_: move filter mgr to go-waku () 2024-08-06 19:05:56 +05:30
kaichao 47899fd045
feat_: hash based query for outgoing messages. ()
* feat_: hash based query for outgoing messages.

* chore_: more logs

* chore_: fix comments

* chore_: do not lock when send queries

* chore_: use constant for magic number

* chore_: remove message ids from query queue after ack

* chore_: fix ack clean process

* chore_: fix message resend test

* chore_: add test for waku confirm message sent.

* chore_: fix tests.

* chore_: fix more

* chore_: set store peer id when mailserver updates

* fix_: tests

* chore_: increase max hash query length

* chore_: remove debug log of ack message

* chore_: remove automatic peer selection

* chore_: mark raw message to sent after ack

* chore_: fix test

* chore_: fix test
2024-06-11 15:45:01 +08:00
richΛrd 9e0fb30f8d
chore_: bump go-waku () 2024-05-15 19:15:00 -04:00
Igor Sirotin 2a91fba1fa
chore: added and fixed some logs ()
* chore: logs for successful storenode request
2024-01-23 18:20:01 +00:00
Andrea Maria Piana e65760ca85 Add basic peersyncing
This commit adds basic syncing capabilities with peers if they are both
online.

It updates the work done on MVDS, but I decided to create the code in
status-go instead, since it's very tight to the application (similarly
the code that was the inspiration for mvds, bramble, is all tight
together at the database level).

I reused parts of the protobufs.

The flow is:

1) An OFFER message is sent periodically with a bunch of message-ids and
   group-ids.
2) Anyone can REQUEST some of those messages if not present in their
   database.

3) The peer will then send over those messages.

It's disabled by default, but I am planning to add a way to set up the
flags.
2024-01-23 12:46:17 +00:00
kaichao e28eca1c54
Bump waku version ()
* chore: make vendor

* chore: fix data types

* Update wakuv2/common/message.go

Co-authored-by: richΛrd <info@richardramos.me>

* Update wakuv2/common/message.go

Co-authored-by: richΛrd <info@richardramos.me>

* Update wakuv2/persistence/dbstore.go

Co-authored-by: richΛrd <info@richardramos.me>

* chore: use safe method to get timestamp.

* chore: use proto.Uint64 to convert reference

* chore: manual fix lint issue when import dependency

---------

Co-authored-by: richΛrd <info@richardramos.me>
2023-12-05 12:29:27 +08:00
richΛrd 2c954d42cf
feat: replace DefaultPubsubTopic by Shard 32 () 2023-11-09 20:29:15 -04:00
Igor Sirotin 9f69c32593
fix(wakuv2): post envelopes previously cached but not processed () 2023-11-02 14:16:59 +00:00
richΛrd ba5ed725ce
waku2: static shards ()
- use protected topics for communities
- associate chats to pubsub topics and populate these depending if the chat belongs to a community or not
- mailserver functions should be aware of pubsub topics
- generate private key for pubsub topic protection when creating a community
- add shard cluster and index to communities
- setup shards for existing communities
- distribute pubsubtopic password
- fix: do not send the requests to join and cancel in the protected topic
- fix: undefined shard values for backward compatibility
- refactor: use shard message in protobuffers
2023-10-12 15:21:49 -04:00
Vitaliy Vlasov 356b2f5ca3 Refactor filter health checks; add debugging logs 2023-10-04 00:39:33 +03:00
Richard Ramos f9ec588c4e feat: use protected topics for communities
refactor: associate chats to pubsub topics and populate these depending if the chat belongs to a community or not
refactor: add pubsub topic to mailserver batches
chore: ensure default relay messages continue working as they should
refactor: mailserver functions should be aware of pubsub topics
fix: use []byte for communityIDs
2023-08-23 13:56:00 -04:00
Richard Ramos 4fd4bea837 fix: use debug level for content topic extraction error 2023-02-24 14:30:34 -04:00
Richard Ramos 490570c0ec fix: convert TopicType to stack variable and use recvMessage.Topic instead of extracting content topic from WakuMessage 2023-01-11 13:41:29 -04:00
Richard Ramos 0527009f6c chore: update gowaku 2023-01-10 09:02:37 -04:00
Richard Ramos c7ce9adb5e debug: add more logs to determine why community requests are missing 2022-12-13 10:25:24 -04:00
Richard Ramos ea89a41d96 fix: go-waku update discv5 ENR on succesful NAT 2022-11-28 08:41:23 -04:00
Richard Ramos b14de2dd9d fix: content topic in wakuv2 2022-10-10 10:38:42 -05:00
Richard Ramos 0b1c06403b fix: timestamp conversion from uint64 2022-03-02 10:58:56 -04:00
Anthony Laibe 268c8304a1
feat: Mark messages as confirmed in waku2 () 2021-12-01 16:15:18 +01:00
Richard Ramos 38cc695753
waku2: log envelope hash and ids for all messages () 2021-11-11 12:13:55 -04:00
RichΛrd f6dc6f752a
use 23/WAKU2-TOPICS format for content topics () 2021-08-17 11:27:28 -04:00
RichΛrd facad9f07e
feat: upload/download rate for waku v1 messages ()
* feat: upload/download rate for waku v1 messages

* reorganize code

* fix failing test
2021-08-03 15:27:15 -04:00
RichΛrd 40359f9c1b
go-waku integration ()
* Adding wakunode module
* Adding wakuv2 fleet files
* Add waku fleets to update-fleet-config script
* Adding config items for waku v2
* Conditionally start waku v2 node depending on config
* Adapting common code to use go-waku
* Setting log level to info
* update dependencies
* update fleet config to use WakuNodes instead of BootNodes
* send and receive messages
* use hash returned when publishing a message
* add waku store protocol
* trigger signal after receiving store messages
* exclude linting rule SA1019 to check deprecated packages
2021-06-16 16:19:45 -04:00