feat: update message protobuf to support new message types

Author: dirkmc

src/types/message/message.proto.js

@@ -5,11 +5,18 @@
 module.exports = `
   message Message {
     message Wantlist {
+      enum WantType {
+        Block = 0;
+        Have = 1;
+      }
+
       message Entry {
         // changed from string to bytes, it makes a difference in JavaScript
         optional bytes block = 1;      // the block cid (cidV0 in bitswap 1.0.0, cidV1 in bitswap 1.1.0)
         optional int32 priority = 2;    // the priority (normalized). default to 1
         optional bool cancel = 3;       // whether this revokes an entry
+        WantType want_type = 4;         // Note: defaults to enum 0, ie Block
+        bool send_dont_have = 5;        // Note: defaults to false
       }
 
       repeated Entry entries = 1;       // a list of wantlist entries
@@ -21,8 +28,19 @@ module.exports = `
       optional bytes data = 2;
     }
 
+    enum BlockPresenceType {
+      Have = 0;
+      DontHave = 1;
+    }
+    message BlockPresence {
+      bytes cid = 1;
+      BlockPresenceType type = 2;
+    }
+
     optional Wantlist wantlist = 1;
     repeated bytes blocks = 2;          // used to send Blocks in bitswap 1.0.0
     repeated Block payload = 3;         // used to send Blocks in bitswap 1.1.0
+    repeated BlockPresence blockPresences = 4;
+    int32 PendingBytes = 5;
   }
 `

test/types/message.spec.js

@@ -35,7 +35,9 @@ describe('BitswapMessage', () => {
     expect(pbm.Message.decode(serialized).wantlist.entries[0]).to.be.eql({
       block: cid.buffer,
       priority: 1,
-      cancel: false
+      cancel: false,
+      send_dont_have: false,
+      want_type: pbm.Message.Wantlist.WantType.Block
     })
   })