 Okay, so thanks Dave, thanks everyone. My name's Jason, I work with Dave for Artifacts. We are not a blockchain company. We are a for-profit software company and data company, however, and we came here to visit with you all the way from California. And so we've heard a lot of interesting stuff about crypto kitties and some skepticism from researchers, which is all interesting to hear. So what I want to try to do today is actually, instead of talk and show slides, I'm going to try to show you some working software. I'm going to walk through some, just some simple examples, just to illustrate some of the tools that we've built here. And hopefully this will be interesting and compelling. And of course, our platform is live. Anyone can try it out for free or we can talk later if you want to hear more details. Just real quickly to reiterate. So we have a website that looks pretty nice. We have a platform. Researchers are using this now. Any of you can come and try it out if you'd like. But we really know that this theme of integration is really going to be key to our success with Artifacts. Changing behaviors is hard, takes a long time. That would be nice if some serendipity fell into place. But realistically, in order for us to be successful to add value to users, to make money as a company, we need to be integrated in tools that users are already using. So that's more or less what I'm going to try to show here. I'm going to go through. And there's a timer somewhere. I have 28 minutes. I will be efficient. OK, so a couple of things that Dave mentioned here. I'm already logged in, so I'm going to do a shortcut. But if you wanted to log in with Orchid or any of these other things, again, people are already in those places, so we make it easy with a single click to do that. I, of course, already have an account. It knows my name. I'm going to go in. And so essentially what we have is with a web-based platform, we have APIs and integrations with all kinds of different things. It's a growing list. And the software allows a user, a group of users, to create a project. A project can be anything you like. It might result in a data set. It might result in a poster. It might result in a journal article down the line. That's fine. But you can create a project. You can add stuff to it. You can share it with colleagues. You can make it public to make it more findable. And of course, the blockchain integration, which, as James mentioned, building a blockchain infrastructure is fun for some people. It wasn't fun for us. So when Blocksburg came along, we were very excited and said, we're going to use that. The perception of authority coming from Max Planck Society was great for us. And the idea of an immutable timestamp or the perception of the value that that adds is something that we've heard from a lot of users, from pharma companies, from research labs, from publishers, all the different people that are out there in the ecosystem all like that idea. And so we've built that in along with the whole full stack web application. And with that blockchain element, we do two things, proof of existence, which is a little bit of a mouthful. But essentially, that's this initial timestamp transaction. And as Dave spent time talking about attributions, so citations. And again, we want to be able to make it easy for people to give and get citations for anything that they want to share. There was a question about how do those citation counts then sort of get out? Now, of course, we need to feed those citation counts out to people who are interested in seeing them. You can see them on this dashboard. Of course, right here, I have a couple of proofs and attributions. We'll show those working live in just a second. But the publishers in particular that we're talking to, they all love this idea. Small publishers with one journal, bigger publishers, they say, yeah, feed us those attribution feeds because we think those are going to be valuable. And we're going to mix those in with all these other metrics. Whether there are too many metrics or not, that's not for me to decide. But the publishers are interested in more metrics. And they think this idea of a citation to something other than a preprint, which usually happens like after someone's paper has already been accepted. So to any of these other things Dave mentioned, a data set, a research instrument, of course that's going to vary across the different academic disciplines. But again, users are saying they want a little bit of protection for that. They want to make it easier to get that stuff out there. The other end publishers and funders and everyone, they want to see those little numbers associated with those things. Maybe not little numbers. Maybe they become bigger numbers. They can slice and dice that with the other metrics as they choose. And that's what we're going to try to do here. I'm going to show you a project. I have a list of projects. Again, these can be sort of anything that we want. I have a bunch here. I actually created a little project that I'm going to share with everyone. I called it the Blockchain for Science Conference. I can, again, add anyone I want. I can make this public. I can drag and drop things in here. Maybe eventually this will turn into a public resource that we want to share and make findable. Maybe we want to write a paper and we're going to publish and we'll start with this. So I actually, also, as I was paying attention yesterday, I created a data set. So what I'm going to do is I'm going to take this data set and I'm going to drag this data set file. This happens to be an Excel file, but it could really be anything. So I'm uploading this file to our storage. So Dave mentioned that the system, we ask people to upload a file. It stays on the system for a millisecond. We create a hash. We write that to the blocks we're going to show that working. In this case, we also do allow folks, if they want to store stuff on our system, this is a courtesy, you can store files. It's AWS S3 bucket. It can be a lot of other things. I'll show you some examples. That's just sort of, if you want to store stuff there, you can, you certainly don't have to. We're not doing anything with those files other than keeping those there for you. So I'm an author of this file, right? Maybe I'm, I conceptualized it. I did a high amount of work on this. I'm going to now look at this file as it's hosted. You can see it's a preview. Just a little bit of data. Admittedly, probably not that valuable of a data set, but I counted the number of male and female attendees at the meeting yesterday. Perhaps gender is not a key determinant of whether or not the conference is successful. Hopefully all of us think it's pretty successful, but that was something I could use my own observational powers to do live here. And I thought this might be at least a little bit interesting and curious to folks. So I'm going to now add a tag. So we're going to say, buh, exchange for, for science con, right? We're going to say data set. We're going to say, what else are we going to say? I'm sorry, my typing here is less than perfect. We're going to say Germany. We're going to say Berlin. We're going to say, there we go. Okay, so I added some tags. Now I'm going to go ahead and I'm going to transact this to the blockchain. You can see it's processing right there. So in the meantime, I'm going to go back over to another project that I have. I'm going to jump around here just a little bit, folks. So here's a sample project. Just the other day I did a similar kind of a thing. This is a psychology sample project where I uploaded this JPEG, right? And then you can see here, if one was so inclined, which as we've heard sort of mixed messages about, but there certainly are plenty of researchers that are not really interested in tokens. They're not interested in consensus algorithms, but they generally like the idea, again, at least of the perception of a blockchain adding some additional security to help protect the work, right? But if someone was interested and curious, what is this blockchain thing about? They can go all the way through to James' block explorer and they can see the transaction. And what we've done with our smart contract is added some custom bibliographic metadata, including these keywords. So ideally, to Dave's point about helping to make researchers work protected, again with a timestamp on the blockchain, but also to make it more accessible and findable by putting in things as simple as keywords, we can then do some unsexy but necessary search engine optimization to make sure that it's easier for folks, other researchers to find things based on searching for keywords, which many of us do, and then ultimately build on that work and cite it. So that's the direct connection with the Bloxburg blockchain. That's one element of blockchain here. We can close that out. We can go back to our other project. We can see whether this transaction has gone through. And of course, the transaction has gone through here as well. So we could look at that again. It all just takes sort of a few seconds. So we have created our own custom bibliographic metadata smart contract and we're putting that out as open source so anyone else can use that if they like. And the goal there is to, and this thing, this definitely needs to evolve. We're gonna add more and more metadata there, again, to help make it easier to find these research artifacts and they are protected because they're time-stamped and transacted to the blockchain. Okay, so those are projects and those are blockchains. If anyone is interested in building on my data set here, I put a lot of time into this. I would love for you guys to work with it and maybe write papers and you could cite my data set that I created right here. Okay, I realize it's a little bit of a silly example but hopefully it helps make the point. What's that? Well, yeah, okay, so I didn't put anyone's name. That's true, yeah. So data privacy is always a concern and in this case you saw, I did upload that file to show that you can store things but the vast majority of the use cases are really, you don't need to upload the file. It's really just making that hash and then writing that hash and the metadata to the blockchain and some of that, you can do that actually right from our homepage. You can drag and drop a file right there. You don't even have to be registered. You have to have an email address because we have to have sort of something to key off of initially. So any of you can try this. It takes literally five seconds. You can drag and drop the file, add an email address. It'll email you the hash and then if you want to do more with it, you can set up an account but you get essentially that timestamp right there. Okay, so we talked a little bit more about how we do it on time. Okay, good. So I have 17 minutes and 54 seconds remaining. That's good. So we're gonna go back into the platform a little bit and show you a few more examples of some of the things that Dave talked about. So I showed you projects. We have sort of a little bit of a dashboard. We're not trying to replicate other profiling systems like ResearchGate or anything like that. Basically we just need sort of a home location where you can sort of look at your stuff in one glance. We also have custom dashboards that we're building for institutions and for organizations. So we're working for example with the Journal of the British Blockchain Association. We're building a custom dashboard for them which we think is pretty cool. It makes sense. We're both sort of, you know, they're interested in blockchain stuff. So these will evolve. But the point here is I wanna show you how my proofs of existence and my citation counts can go up and I'm gonna show you that live in just a moment. But we also have, we have quite a few items on our platform already. These are metadata records. Some of these are metadata records you could find in Dimensions or Scopus or Google Scholar. But these are things that we sort of put there as convenience. We have literally tens of millions of metadata records. This system is pretty smart. It will recommend some things that it thinks I've, you know, I've already done. These are published items. But we mix right in there sort of anything else that I want to, any other metadata records that I want to upload to the system. And you can see as developing and testing the system, I've added a lot of different things. A lot of these are just sort of test items. But some of these are real data sets, right? There's some real data sets. These are some real graphics and so forth that I've used for real projects. But now the real, so the real value here is enabling folks to find those things and then, you know, site them when we're writing. So I'm going to use one of these tools that I think a lot of other people use. This is Google Docs, right? And here's an example of one of our integrations. Okay, so Google Docs, I created a blank document just this morning. You can see we have a, using our own API, we've built a little add-on here. And this allows me to search for something, let me see if it's saved or I want, no, it did not. Okay, so I'm going to go and make sure I find something that I know I've published. I'm going to self-site here, which I know is sort of, some people don't like that. I'm not trying to game the system. I just know that this is something that I have published and it does have some other citations. Okay, so here, again, this is just a sample document, a little bit of a simplistic example, just to try to make the point, right? But we're in Google Docs, where many of us write anyway. Don't need a blockchain for that, but we are going to start writing a basic paper, right? And then we're going to say our references are here and you can go ahead and you can insert that and that's going to insert and create a basic, basic bibliography, as we all know, there are dozens of tools out there that already do that. So that's not particularly novel, but what is pretty cool is now I can go back over to my, I can go back over to my artifacts platform and I can see that two things have just happened. First of all, it's now created an artifact for my document for me automatically, right? This Berlin document, if I wanted to, I could then add this to that project that I showed a little while ago, I could upload that and all of us could collaborate on it, but it also has now incremented my citations, right? So these are the citations here that, as Dave had talked about, given and received, so this just went up, this was 27, you know, a couple minutes ago, this is 28 now. And so the main question of how do these citations get out to people, it's sort of been asked in a couple of different ways. Well, one way is by going in here and looking, right? That's if you wanna come to our front door. But again, we have data feeds that we're offering out to partners all across the ecosystem so that they can get that. And that can be, that'll be updated in real time as much as people are citing the items from the artifact system. Couple of other things that Dave has mentioned that I can demonstrate quickly here. I'm going to just do a quick search again. I said, we have lots of items already in this system, but here is one in particular, this is an author from Max Planck, and he has all kinds of different, he has all kinds of different things. And essentially what we're looking at here is a direct integration with the Max Planck admin repository, right? So the repositories are already out there. Has anyone ever tried to really find anything in a library repository? It's very hard, it's very painful. These are resources that universities around the world have invested hundreds of millions of dollars in over the last 15 or 20 years. They're supposed to be open, they're supposed to be permanent, but if you ever actually try to go in and use one, it's really, really painful. So we've been talking to librarians all around the world that said, hey, we could integrate, help make that stuff easier to find and get used and build upon and then cite it and so forth. And so to prove that we actually did that, working with James and the rest of his team, we've integrated it as the first step with the admin repository, which is one of the Max Planck repositories. And you can see that here's an example of one of these files, and this happens to be just a little text, readme file associated with one of the data sets and you can click right through to the, you know, to the native interface if one wanted to. Now, one could go to admin directly, of course, so we're not trying to necessarily duplicate exactly what they're doing, we're just trying to pull things together so they're easier to find and to use and again to cite and to build those citations on. Okay, so I think we're doing pretty well. What else should we try to show? And so yeah, question. And I want to cite in art something like this. Yes. How do I do it? Well, that's what I thought I just showed that with here. So essentially, in this case, we happen to have built this add-on for Google Docs and you saw that I just cited that paper. This is a real paper that I wrote with some colleagues about a year ago, and that's indexed in our database. By pressing insert, I actually cite. Yeah, that's cited and this just makes a basic bibliography entry here. And again, back onto my, my, you know, back on my dashboard, you can, that number was lower a few minutes ago, but that's right there. And again, so the next step for this really to be successful to add value to all these disparate people and organizations across the ecosystem. Again, whether those are working well or not isn't really for me to decide, but what we are trying to do, as Dave showed, is just to try to help make it easier for people to get credit for more things that they are doing work on, right? And it's up to any of you as the creators of those research artifacts to decide whether they're in the right state that you want to share them or not. But once we do that, we help to protect your IP and then we help you to get citations. Now again, then we feed those citations out to anyone else who might be interested in them in custom dashboard, data feeds to publishers and so forth. We haven't done all that yet. We're a quote unquote startup. We're a new software company that's just getting started on a lot of these things. But that is the vision. And we feel pretty confident about the vision in the sense that we talk to and listen to a lot of these different players, right? And they are all saying, yeah, that makes a lot of sense to us. They're not saying that's gonna be super easy, you're just gonna push a button and it's gonna happen. It's going to be a lot of work and it's gonna take, again, a little bit of serendipity as almost anything does. But the goal is to continue to build more and more of these integrations into the tools and the platforms and the systems that are already established in the scholarly research and publishing ecosystem. Again, whether those are good or bad, we're not really trying to revolutionize that. We're trying to work from within the system to help add value for users and all the other stakeholders. So if we go back over to our projects, I can show you a couple of other examples of other integration tools that we already have. I mean, certainly for those of you who are coders or tinkers or hackers, things like Bitbucket and GitHub and GitLab, these are not blockchain dependent by any means. These are straightforward proven web REST APIs that almost any other web service. If you see something on this list, like, oh yeah, that looks pretty cool. We could try that out. Very straightforward, you do a shared login, share an OAuth token or something. And we're constantly asking and listening to folks on, what else should we add to this list? So we're talking both to the developers and the companies and publishers of these kinds of tools and saying, hey, you guys have an API, let's see if we can do an integration. But it's really much more meaningful to hear from individual people that say, instead of this one, we use another tool. Could you guys do an integration for that and just make it that much easier for us to combine those? So please let us know, especially if you try out the system and you think, hey, this is another tool I use. It would be great if you could plug this to things together. I mean, we're definitely all yours on that. Okay, so I think we're doing pretty well and I still have six minutes and 55 seconds. So hopefully we have some comments and questions or if there's something else that I went through quickly that you want me to go through again, just to demonstrate. Otherwise, I should listen and try to answer some questions. Okay, yeah. I think it takes a second to work. Yeah, so we form, I don't know. Well, so before you, you showed this quick upload or quick way to put it into the blockchain without, yeah, this one. So this is without having an account. So this is without having an account. Yes. But then how does the signature work? You need to have at least an email address. Yeah, and so then we will, again, you would upload your file, whatever file it is. It's just on the system for a millisecond where we write the hash and then that hash and I can show you what it looks like if you want to select a file. I can just even pick this PowerPoint file which isn't very real. You would add some tags or some keywords. All this is basic, just web upload stuff and then it would email a link to the hash as soon as it's created and then in order to do anything more with it, we want you, of course, to create an account. But it's going, I mean, that hash and that proof of existence transaction is going to persist no matter what, right? I mean, it's probably not really valuable for artifacts or for you as a user unless you create an account and you want to do more with it. But this is, we're just trying to make it as simple as possible for someone to say, hey, what is this about? We're gonna, we want to try this out. But again, this is, we're realistic. We know that we can't expect millions and millions of researchers to just stumble upon our front door even if they think it sounds cool and start creating files. So that's why the integrations, API, all that stuff we think is really much more valuable and it just takes a little bit longer to develop all of this thing. Yeah, there's a question in the back as well. Thanks again for the demonstration. Just as a researcher myself, right? I mean, on the one hand, you would create an inflation of citations, right? So everybody, like if we do partial publications, all the researchers would kind of climb up in their citation count, right? So it's kind of, if it works, it would be on equal level. The second thing is, like most researchers would tell their students that a set of data needs to be put in a context to have a certain value and that's why we write papers, right? So to just, I mean, there might be different fields, whatever, if you have clinical studies and so on, that data set, whatever, you try a certain medication or so on certain types of diseases and that might have a value by itself and might even have a high commercial value, right? And I think we had some talks yesterday and so on, on that one. But I would say the typical information that my colleagues create only makes sense if you write a story, create a writing context around it, which is essentially a paper, whether it's a high level paper or low level paper. And then presently you have the option to only put the key data into your main paper and just have supplementary information where the ones who are deeper interested or need more detail can resolve it while the others can just read the main paper to get like the gist of what this is about. So I don't really, can you give me some examples where, except for maybe high value medical data, where these bits of information would be kind of as a standalone so valuable that they are of use for others in contrast to just writing a paper. I mean, it's like we all can type and so on. So why would we not do that? What's the value of this kind of fractional information where every good researcher would know how to convert that into a full paper and then you are in the routine of scientific publishing again? Yeah, there's a lot there. I'll try to unpack it. I think the main answer is it's going to be very discipline specific, so it's gonna vary quite a bit. And again, we're not trying, I think Dave made this point pretty nicely, we're not trying to contrast with anything that's working well right now. Again, all the problems with peer review, whatever. I mean, journals still seem to publish a lot of articles that people have get something out of, I suppose. So there's nothing we're doing with artifacts that's trying to undermine any of that. I mean, if people want to publish articles that's still, that's fine. But even if they are planning to publish an article, in many disciplines, being able to share the constituent components that ultimately comprise that article, at different points, makes sense for different researches. And we've heard from literally hundreds and hundreds of people in different disciplines that say that makes a lot of sense. Just personally, from my own PhD dissertation 15 years ago, I have a few citations. My own career doesn't really depend on citations, but I like doing research. I don't have to pretend to know what the, what my end users are doing because I can go through those processes myself. But honestly, even now, 15 years later, every six months or so, I get a request from someone around the world that they want to ask, they want to use a very specific survey instrument that I developed from my dissertation. They're of course free to do that, but that's a constituent component of the final work that does make sense on its own. And people do want to use that and make, if I was able to put that on artifacts 15 years ago, it would have been way easier for people to find. And it would have been, you know, people might have wanted to cite that and give me credit for building on that one specific component. If my dissertation was in the form of a journal article, can I also have listed that as a piece of supplemental information? Yeah, sure, you could have done that as well. Yeah, so, but I think the main answer is, and I have 20 seconds, eight seconds, yeah. So I think it's really going to depend on the individual discipline and the behaviors, again, we're not presuming to change those, but we're seeing signs that they're evolving and as this information is easier for people to get to and cite and secure, we think that the behaviors will, you know, will adopt to that. All right, so that's my time, thanks everyone. Thank you.