Baseline Protocol Baseline Demos / Resources, 16 Feb 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Baseline Battleship Demo

Description

Baseline Battleship -

The Baseline Protocol is a set of tools and libraries that enables enterprises to synchronize complex, multiparty business processes with privacy to verify that data is synchronized between counterparties or prove certain attributes of that data.

‘Battleship Baseline’ is an implementation of the classic search & destroy strategy guessing game, using the design pattern specified in the Baseline Protocol standard. This implementation gives you a simple framework of where and how to baseline information between multiple parties, a complete set of code that works, and a lot of clues on how to extend the code to create new features and for other use cases.

View, run, and contribute to the code here -
https://github.com/eea-oasis/baseline/tree/main/examples/battleship

Read more about the work and the Core Devs behind it here -
https://github.com/eea-oasis/baseline/blob/main/examples/battleship/README.md

Join the community to contribute to the development and adoption of Baseline, or learn how to baseline your products and services - https://www.baseline-protocol.org/

A

The baseline, hello, world, battleship game and they'll be walking us through it now over to you, jack.

B

Yeah, I think uh davin's actually going to kick us off here, but we can just do quick, intros of the team um jack, I'm a student at duke university. I did some of the like implementation of the front end back end for this.

C

Yeah and I'll jump in there. I think in the interest of time um we're not going to have everybody come on and do intros so I'll just run through the list. Real, quick as well. I'm damon jones, uh the head up product over here at provide.

C

Additionally on the team, we had uh ryan fish, um stefan caustic and manik john, and it's been a real pleasure working with these guys. It's really important that we give potential baseliners or really anybody for that matter, something something tangible and familiar and really simple that they can grab onto and apply this baseline process to. So that's where that's where this idea of battleship comes from.

C

I think it fits the build pretty well. It uses every aspect of the the baseline process and the in the hello world we've put together uh and I think that's a quick enough intro uh in the interest of time, jack I'll, go ahead and turn it back over to you. Man.

B

Thank you all right, so here we have. uh Are you able to see that at home.

A

B

Okay awesome, um so essentially, our idea was in order to kind of demonstrate this idea of baselining between two parties. We'll use this game battleship simulated between two players to kind of represent this overall process, um and so here we have two different clients pulled up um each kind of connected to their own implementation and then communicating over a kafka messaging provider.

B

And so let's say here: first alice wants to begin baselining with another player. So we're going to go over here and create this organization name alice and she's, going to create a work group um in this case we're just using simple ids. So you can easily copy and paste it over here.

B

But let's say alice shares this code with bob and bob goes over here on his other client somewhere else and signs in creates this organization and then he's going to go ahead and join that work group like so, and then that kind of kicks off the game here um and in the context of baseline, the battleship game is kind of acting as this sort of shared document um and so alice and bob are both going to go ahead and place their ships on the board somewhere and it uses zero knowledge proofs.

B

So that way, alice and bob are sharing information about hey, I'm putting my ship somewhere on the board. They're sharing a essentially a hash of where their ship was placed on the board, and so that way the other player can verify alice and bob place their ship. But they don't actually know the coordinates of the ship that was placed, and so that's kind of how zero knowledge has been integrated in here and then we can go ahead and say: okay, alice is going to start and alice is going to say.

B

I think bob has a ship on c1, and so we can see both alice and bob receive his information again. This is all being communicated over kafka and then on bob's side. He gets this request from alice. Saying hey.

B

I think your ship is in square c1 and if bob goes ahead and says well, my ship is there, but I'm going to claim that that's a miss. It goes ahead and presses that and it says: okay, wait. Proof verification failed. So it generates this zero knowledge. Proof saying using the hash of his board position that we created at the start and communicated between alice and bob and alice's public input.

B

Guess and says you know that that's not true that doesn't match up, so it gives bob another chance to be truthful, stop up and say: yep that's a hit and then on alice's side. Once again she knows the hash of bob's board and she knows her targeting square and bob communicates that proof back to her and she can go ahead and say yep verify and then once that's verified, you get this little check here and we can see down here. This is just currently running in a ganache local cli.

B

um One of the kind of last features we want to add in is a way to actually view these transactions getting added to the shield contract for right now. You can just see like something is happening here and you just kind of have to trust us that it's the shield contract.

B

um But lastly, let's say now: it's bob's turn bob says you know, I think alice has a ship at b4, alice, says nope, that's a miss and then once again, bob can go over here and verify that and then, once that's verified, you can see again that uh record of this kind of interaction is being added into the merkle tree in the shield contract.

B

So that's just kind of a quick demonstration of what we've come up with um just from a tech perspective. uh It's built kind of using a react. Node.Js client server, where alice in this situation is connected to her home node.js instance of the server bob is connected to another instance and they're communicating over that kafka messaging bus.

B

Like I mentioned earlier, um we used kafka just because we were wanting to try something other than nats, just to kind of show that baseline is kind of protocol independent in a lot of cases where you can substitute in different parts of the overall protocol and use things like nats or kafka for kind of your specific use, case implementation and then, like I said, we've been using ganache just to keep it local and simple and fast, but you could easily convert this to run on something like robsten or another test net and then, lastly, all the zero knowledge proofs.

B

uh We did using circle js, mostly just because it was very easy to run the verification of that through the client and the node service, so yeah, that's kind of it from us. If anyone has any questions happy to take some of those.

D

I must be getting weepy in my old age because I'm I'm in tears watching this. It's so freaking awesome. It just makes me so happy and I not only the work and- and this I mean this- it just opens it up. For me, I mean, and I think, a lot of people.

D

This is a this is actually an interesting use case of where you would use zero knowledge just between two counterparties- and I know you guys are already thinking about you know where you make this, uh for uh you know where you're proving the shared state to a third party where that's where baselining gets really interesting right. I've got to prove to the auditor without having them open up all my books right uh some some truth.

D

um You know, I think you guys were talking about um you know proving to a tournament, the game's winning state without having to show the whole game to that tournament, um which is an interesting thought. I just think it's so good. I uh sonal thanks for giving me the not not cutting me off here. I don't want to take up time, but I'm moved by this work and also by both you guys and blipsix how you worked uh live on zoom, together with the videos that we're definitely gonna publish.

D

I think those those alone are are huge, huge assets. I loved the way you guys pair programmed- and I don't know all together. You guys really made an impact and should be proud of the work.