IPFS 0.5 Meetup, 23 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: IPFS as part of an Agile Data Toolbox - Peter Godbolt

Description

Where does IPFS fit into an Agile Data Stack? Peter Godbolt, tech lead of Hut34, shows us exactly how in this demo, featured during the 0.5 Release Meetup.

Hut34 is The Agile Data Company, solving data problems because data solves problems. https://hut34.io/

For more information
+ read the go-ipfs 0.5 release announcement: https://blog.ipfs.io/2020-04-28-go-ipfs-0-5-0/
+ visit the project website: https://ipfs.io
+ or follow IPFS on Twitter: https://twitter.com/IPFS

Sign up to get IPFS news, including releases, ecosystem updates, and community announcements in your inbox, each Tuesday: https://ipfs.us4.list-manage.com/subscribe?u=25473244c7d18b897f5a1ff6b&id=cad54b2230

A

Thank you very much for having me at the ipfs 0.5 launch Meetup before I begin. I would like to say.

A

Now, I better confess that this is about 12, take of this particular presentation, so the wine is going down rather well. Thank you for having me, though, it's great to be here. My name is Peter. I am Peter on the Block on Twitter and I'm. The tech lead for the Hut 34 project, the HUD 34 project, we're an agile data company, startup, building data tools, solving daily problems, because data solves problems. A very brief word on the origins of our name.

A

This is Bletchley Park, which, during the Second World War, was home to code breakers, including the great Alan Turing, trying to crack the Enigma code. This is Bletchley Park today, and this is our office where we earnestly endeavor Bletchley Park literally had huts. These are four of the huts: hut-one hut-two hut-three and out four and we're an amalgam of huts three and four putts 34.

A

This is not in fact, our office because we're lucky enough to be based down here in Sydney Australia. Our offices are just human manly, so something like seven half thousand miles away from the San Francisco Bay Area, so it couldn't be there tonight, but I'm glad to be here in part now I'm just going to a brief presentation on where ipfs fits into our stack.

A

How excited we are- and you know the future really so what you're looking at here is a react front-end of our sort of core product, which is a data Hut we set up huts Hut's, contain rooms and they're places where users can come to exchange data. They can secure it, they can exchange it, they can track it, they can monetize it if they want to and you're looking at a front-end and with an app engine back-end on Google Cloud, so having logged in via OAuth.

A

What we'll see in a moment when I get in there is that the the stack here you've got a traditional service stack, but really the heart of it begins. When we look at this fearian blockchain based wallet, this is a website called ether scam. Many of you may be familiar with it.

A

This is just a block Explorer showing me what's going on, so a user has arrived, he's got access to this wallet, so here's an address that we control I'm, just gonna copy that address, because now by the smart contract, when that user was first registered with us, we've logged on chain this, so our smart contract has some data which says this identity. Is this address this location hash? So here's an IP, FS hash. This is where begins an IP. Fs is really the glue that binds those three things together. We've got the Google OAuth identity.

A

We've got the etherium wallet with this private key and we've got the IP FS hash containing various bits of data. This particular bit of data can only be updated registered by this identity by this address holder, and if we look at it, it's a base64 string containing this information. It's an RSA key pair there's a public key and there's an encrypted private key that private key is encrypted using the private key of the etherium dress that registered it.

A

So we've got ipfs sitting there via this smart contract as the glue that binds the identity to an encryption key pair and there it is so now. Let's do some data exchange. What we do with this so now that I'm logged in I can I may be an enterprise user. I may be a hobbyist. I may be a data scientist, but I can use this UX to just browse around some data and I'm interested in alcohol consumption.

A

So I'm going to acquire this data set, and you can see now that it's retrieving the blockchain details and it's signing the value object. We use a protocol called 0 X 0 X is a trustless value exchange, so the hot X object, which is the heart of our technical delivery, contains meta data value and it's just successfully exchanged. So now that I've got that data I can come here and complete the full circle and I can access my wallet once more.

A

It's gonna download the keys it's going to download the encrypted data and it's going to present their data to me in the client. So here we are, let's dive under the hood. Just a little bit and have a look at that, our tax exchange object, which again is part of the key. So here we've got the contract and you can see that there's a there's.

A

The transaction there's literally just gone through being mined right now, look at the previous one and we can see that the identity who completed that transaction has called a function called hot X, complete, Alex transaction complete, and this transaction is aimed at the ipfs location. This location doesn't represent your identity, it represents the specific exchange of data and if we look at that object against base64-encoded object which comes out to this, this is a HUD X object containing meta and data and value and within the meta information this is promoting interoperability.

A

The model can contain schema information. This is all public information. This, of course, oku, contains the public information about the data exchanged, but the actual data itself is presented via a further ipfs hash. They tells me where can I get this data and if I have access to it? Here's the encrypted key that encrypted key can only be decrypted by the identity of the person who completes the transaction. So that's a real Whistlestop tour.

A

We have users from academia, doing research projects, we have a couple of teams investigating dementia risk and assessing autism, as well as an autism assessments going on collecting data and exchanging in via this protocol, and we have some corporate users. You can work with the protocol in directly within the Excel workbook or within our studio or wherever you want to that's our mission and at the heart of it is ipfs.

A

So if you want to reach out to us, it's Peter on the block or HUD 34 project, otherwise just a big congratulation really really excited to see the path to 1.0 and what happens next. I'd like to thank the inferior guys who are out there. We currently having experience of running our own nodes, we're currently using in fewers infrastructure, so very keen to be part of the ecosystem. Very excited for the nonpoint 5 launch best wishes from seven half thousand miles away. Take care, guys, Congrats.