All righty, welcome, welcome everyone to our November PL Andres All Hands. It's actually the 1st of December, but we're squeaking it in sometimes on somewhere. Maybe it's still November. Agenda for this meeting, we have a meeting working group update for you, which includes a look back at kind of 2022 strategy and also a preview of focus for 2023 across this working group and roadmap steps. So it's going to be fun. We'll spend a little bit more time there than usual. No deep dives today, but we have a lot of awesome spotlights across many groups as we go into the end of the year. So let's get right to it. Hopefully we actually have time for Q&A, which we usually don't. As a reminder, what is the PL Andres working group? We are one of many teams in the Protocol Ops network where we drive breakthroughs in computing technology to push humanity forward. We're all unified and work across many of these groups, working on the core of making the internet more accessible because we think it empowers amazing superpowers for humanity and wanted to have a solid, robust foundation, including things like content addressing peer-to-peer collaboration and high user agency. And we want to make it a secure foundation for humanity's most important information and collaboration and tools. We do that through supporting and growing a number of breakthrough computing projects, three of the ones we contribute to heavily in this working group are IPFS, Liberty, and Filecoin, but also many others, including DRAND, IPLD, multi-format, test ground, and more. Our mission is to scale them and offer new opportunities for these protocols. We do that in a myriad of ways. These are our different teams. I think we actually have some updates to do. There's lots more subteams within these teams as well these days. And this is our strategy for 2022. This is kind of what's guided the core of our work. There is actually now a great video, I think it's in the spotlight section, that describes what are the things that Andres team has done around this 2022 strategy over the past year, first around growing the teams contributing to these open source protocols and enabling network native development, then around making sure robust storage and retrieval is available across IPFS and Filecoin and that we are gaining kind of adoption through real user data. We're driving breakthroughs in programmability, scalability and compute and doing all of that while most importantly, keeping all of our critical network operations running really smoothly, releasing, upgrading, bringing down tech debt, things like that. So these are our OKRs for Q4 that align with that. We've already done some of them, which is good, given that it's the last month of the quarter and it's a short month at that, but a couple of them are still open or still landing. These are around the same objectives from the beginning of the year, around growing our knowledgeable and aligned developers within the PL stack. We succeeded with an amazing set of presentations at IPFS camp, Lab Week, Phil Lisbon, Phil Bangalore, which just happened the past couple of days. Thank you for everyone who was making it up to India and presenting there, that's fantastic. The photos look phenomenal, I'm very jealous and it gotten a ton, both of in-person engagement but also kind of accessibility to remote communities and remember most of the viewers and engagement for these things are actually in the future and so always prepare those presentations with an eye towards future people that'll be working on it. We've shifted our focus from kind of more general hiring growth across teams, just especially given macro and crypto conditions to focus more on leadership hiring and so making sure that we can bring in the leads that help scale our organizations and kind of reduce kind of burden on coordinating some of the working groups and teams that sit within our space around accessible and robust storage and retrieval. Congrats to Saturn and Station on their MVP launches. Very exciting to have the early versions of those out and starting to gain users at adoption and continued workloads towards making sure new data added to Filecoin is retrievable, reliably and also retrievable from Kubo and IPFS gateway users who want to access data stored in Filecoin. And so there's a chunk of work going towards that. I don't think we're currently on track to hit this OKR as it was stated a couple months back but we're going to measure and keep working towards that. Breakthroughs around scalability and compute, launch of FBM BuilderNet. I think they've named this to Hyper Space, HyperNet, Hyper Something or other with many highly useful smart contracts of which we have at least 20 amazing exemplar case studies. I think we're on track for this. I think it's gonna be great. And then landing concrete go-to-market roadmaps for interplanetary consensus, retrieval markets, time lock encryption and a number of other breakthroughs. They have great roadmaps. I think we need a little bit of refinement to get them to concrete go-to-market roadmap status but we're making progress towards that, which is great. In terms of keeping things running smoothly, we have actually already achieved our Q4 goal which was to cut our spend on kind of centralized legacy web-to-infra services like AWS without hurting our overall performance and quality which is great. I think we're actually gonna over-achieve on this OKR significantly. I think we can get to 50% cut by end of year which is phenomenal without negative impacts which like huge kudos to everyone who has refocused time to help us get to that. It is important and valuable. It means we can put more resources back into the web-to-reco systems that we participate in which is exactly what we wanna do. And so congrats to everyone. And then final goal is around maintaining uptime. We still have an AI to make this really more clear and precise but obviously we can't grade that until the timeframe is up because that's a any moment we can be spending time on that. Cool, and this is our core improvements roadmap that we've been looking at for the past year-ish, six months. And we have a ton of check marks. So many things accomplished since our last all hands together like pause, unmute, round of applause for all the amazing launches. We haven't gotten together in this format in a while but like, thank you, thank you everyone. Super exciting. And there's a, yeah, a time to celebrate here. And it's amazing to see us hitting into the end of the year and just shipping awesome stuff all the time. Big congratulations to all the teams that are having big moments like that. I mentioned we were gonna talk about 2023 strategy as well. There is again, a really good recording of this that's up on the PL YouTube channel which we will link to you that talks and breaks down these areas of 2023 strategy. But this, you know, it really builds on top of what we've been focused on for the past year and maps pretty nicely to also file coin, focusing first at the base layer on critical systems stewardship then growing team and overall network contribution towards PL stack protocols faster plan. Thank you, thank you. Then robust storage and retrieval and then compute over file coin, state and data. And so that is our driving strategy for next year which led us into this roadmap for next year which is a first draft of this that we shared at Lab Week and a number of other summits during that kind of Lisbon blockchain week. And we've been working for the past couple of weeks on making this not be a slide that is very hard to maintain and update but actually putting this into tooling that then is accessible and beautiful across people. Still a little bit work in progress on that but we're happy to share a very first draft of what that looks like. We still have some iteration to do and it's a great opportunity for everyone to take a look at it. But we went from kind of, you know looking across these major initiatives and breakthroughs landing next year to using this new tool called Star Maps which you're gonna hear more about in half a second to visualize the file coin core improvements roadmap. Now, I don't think I have everything because I had to squeeze through everyone's different roadmaps to find the right milestones and people didn't always define them the exact same way that I had to find them above. So I think we're missing say compute over data maybe a couple of other things but we have other things that weren't there before and that's exactly what we wanna get is more visibility across all these different teams. Huge thank you to the Ignite team which like jumped in and made this happen and to read who kicked off this project with Juan to actually go in and build and design and implement this tool. We can cue that up for later. You can go there and see these various different roadmaps. You can click into the GitHub issues that back them. All of these issues are across many other people's roadmaps. So when those individuals update those milestones they will move around in time in this roadmap saving me the effort of updating it always which is wonderful. And so this is ideally what we're gonna use going forward. You notice that there's probably some feedback loops for you as you look at your milestones within this roadmap or like, hmm, I should probably make sure to put the title of my thing in my milestone so that, you know, L1 knows, oh yeah, those are Saturn L1 nodes but you don't have that context visualized here in StarMap. So there's some learnings there for us to continue iterating on but really amazing progress and super excited to see. So what are roadmaps? We have a talk on this more from conversations at Lab Week and our Endress Summit. Actually if Juan here, Juan, if you wanna talk through this you did a really great presentation on it. This is me grabbing your slides but I can voice over. Yeah, happy to. The thing you hear is that when you think about roadmaps there are several different levels which you might think about describing a roadmap for a team or a project. There's, of course, the lowest zoom level might be a very detailed set of tasks and to-dos that you and your team are directly executing on. And then when you can sort of zoom out from that and you start thinking about the milestones that you're working with other teams in adjacent areas with, you look at a higher granularity then you can zoom out at an even higher level and then start looking at a set of specific milestones that then maybe consumers of your project or other groups that are further away from your work but are dependent upon your work, the information about and so on. So there's, as you're thinking about updating and describing progress along a vision or progress along a trajectory for a project it's extremely useful to have these different roadmaps different levels of granularity or the different groups that need access to this information. So we've done pretty well in terms of figuring out kind of the lower granularity roadmaps and various different teams use different tools everything from GitHub to Gantt charts to their own tasks and to-do list and whatnot. And what we were missing was this kind of like higher level zoom view what here in the slide is described as kind of like zoom level three in a sense that corresponds well to the kind of roadmaps that a number of teams have been working on in the last couple of quarters in terms of having kind of a roadmap on the earth with milestones in the order of like three to six milestones spanning somewhere between kind of two to six quarters ahead in time. These are not kind of like very prescriptive boundaries but they kind of give you a sense of roughly the set of milestones that you wanna be able to communicate to a larger set of users that kind of wouldn't know the progress on the project. So that's the set of roadmaps that we're using to coordinate across all of our teams and with a lot of the dependent users that's kind of like that zoom level three set of roadmaps and that's what's kind of going to start maps and which Molly has been using in the core improvement roadmap slides like those are kind of like that zoom level three. Exactly and I think that was my next slide as well like probably the biggest thing having read through everyone's roadmaps over the past couple of days since we've landed first drafts of those earlier this week is we've tended to do too many is your biggest takeaway is focus, focus, focus. You can have more milestones that you keep track of as your team, as what you're working on but when you visualize a user focused roadmap this is like five milestones a year. If you have five themes per year each of which has five milestones, you're doing it wrong. That's too many milestones. Those are not user focused milestones. Those are maybe team development milestones and so focus your roadmaps come up and the wonderful thing is this is now computable. It's in tools, it's in GitHub issues. You can have many issues and you can have different views that you include some children in one view but not another view. And so big thanks to this new computable tool which is more machine readable interlinkable and automates that visualization process you actually get much more optionality on how you want to visualize things which I think is really exciting. Yeah, roughly the milestone count here will depend by project. It's not exactly five person point that's kind of like a think of it as a range but definitely like if you're giving people more than six things to care about like you're already kind of past the point of then being able to remember and so on. So really think of the Zoom level three as communicating to thousands to tens of thousands of people, not a very granular thing. What most team members individually will care about in your team is the lower level, lower granularity maps. So kind of like Zoom level one and two. Julie, I don't know if you want to talk us really quickly through star maps that you have that ignite and help us help. So I think a lot was already said so I'll skip over some things. But yeah, most if not all of Endra's teams have now added their roadmaps to GitHub. So a huge thank you there and huge thank you to everyone who's offered feedback along the way. For the time being, you can find those links in Notion we'll probably figure out a better home for those. But yeah, all the links that you see in the link there are compatible with star maps. So feel free to play around and explore some other team roadmaps. So just quickly, this is what you would see if you pasted a roadmap link in star maps. This one is actually a rendering of roadmaps across all of Endra's in the detailed view which is what you're looking at. You can see that top level issue and then a milestone one level down. If that milestone has child milestones you can keep clicking into that so you get more and more granular as you go. Each one as Molly mentioned has a link to GitHub so you can follow along the issue there. And then also as those child milestone issues close in GitHub, you'll start to see a progress indicator which we're not seeing on this one yet but we will soon. It is working though. So if you do have any close issues you'll see it for your roadmap. But yeah, I'm intentionally not going into too much detail that's the gist of it. I would love though folks to play around and offer any feedback that they have so that we can help make this tool super user friendly and great for the work. Thank you so much for building this. Yeah, I put, I grabbed this together from all of the different roadmaps. I think there is some, you know already immediate learnings from going through that exercise. I created like six new route issues last night with different visualizations of sub milestones. Like definitely learnings around if you break things up into a lot of different themes hard to see what are the major milestones that are happening within there? All you get is the theme, not the milestone. And also if you don't put any ETAs in your root issue then that gives us warnings and concerns. And so always put an ETA and you know just do your best estimate for what's contained within the roadmap that's being described there. But I definitely think this gives us a highly flexible tool. We're gonna keep iterating on it but the really cool thing that this is not unlocks. Again, all of these issues are happening in each team's specific repo in GitHub where they are tracking kind of their roadmap areas. Many different people own these different issues and can make their own views. If you have other ecosystems in, you know data libp2p space or IPFS where many different teams across implementations like IRO and other groups are building capabilities that create cross dependencies or should live in an overall IPFS project roadmap or Falcon project roadmap that extends across multiple groups. We can create visualizations across the roadmaps of all of those different teams and communities. It's truly open source and cross ecosystem and network native in how it can visualize the contributions that are happening across many different teams. So we do not see this as the thing just for Andres. We are biting the bullet of helping build the tool and be early guinea pig testers of putting our roadmaps in it. But we would love to see this become more used and a tool that is super valuable across the whole PL network but we still have some work to do to get it to that point. And one thing you'll notice as we start using these is that we'll start seeing that some of the milestones won't line up meaning some dependencies will like strike out as hey wait, suddenly like these milestones won't actually be possible. And yeah, that's exactly what we hope will pop out of a lot of this stuff. So a lot of the, these are the first kind of integration of everybody's individual roadmaps. It'll take a while while we kind of sort through that and detangle some of the dependencies. And I think right now we don't have, we have children, but we don't have dependencies yet between different areas. And so that's a future thing for us to be able to define those dependencies and make things turn red if the timeline of a dependency is after the timeline of a thing that is dependent on it. Great, that gives us good signals. And we can use these visualization tools to alert us and then drill down within these areas. And so that is, this is the wonderful tool, StarMaps. You can open items in GitHub. You can swap into a more detailed view that sees kind of the sub items within different themes. All sorts of really, really cool stuff. It's a big, big thanks to the Ignite team for building this. Please keep giving them lots of feedback as GitHub issues on the StarMaps repo. And yeah, we're gonna keep moving forward on it. That's it I had for road mapping today and let's hop into team updates starting with IPFS. Hey, yeah, IPFS makes the web work peer to peer. First thing you'll notice is the network nodes went down a lot on that upper left graph. Turns out this measurement is not quite what we thought it was. So we're trying to refine this metric here. The network size from what we understand didn't actually go down. It's just that this metric is not measuring what we thought it was. So we're going to refine this metric and put a better one here. We have the other two metrics, find latency, which is the content routing latency. We've held steady all year long at around 400 milliseconds for that. And we've been staying on top of pull requests. Also, in case anyone didn't know, we had IPFS camp last month in Lisbon. It was amazing. There was a ton of people there and everyone was really excited. 17 tracks with 100 plus speakers. So all of the content that is on YouTube, so for anyone who couldn't make it, you can go on YouTube and find all the videos on there. You'll be spending a long time catching up on them. As far as work goes, today we turned off the DHT caching of the Hydras, which is going to save at least $30,000 a month, possibly more. I did have a nice graph on there, but I think you'll need to refresh but that's okay. The plan is to turn off the Hydras entirely next year, but we're gonna have to wait on content router discovery. Just so everyone's aware, Dennis did a lot of good work analyzing how much the Hydras were contributing and what the impact would be when we turn them off. So we know that this isn't really negatively affecting the network very much. We released Kubo 0.17, which turned on the libpdp resource manager by default, which gives us DOS protection from a lot of different DOS vectors on Kubo nodes. It also included the tar response format support for gateways and we marked the reframe as deprecated, but it is not yet removed because we have a new HTTP API for reframe based on a bunch of the feedback and issues that came up with reframe. So that'll be in the next release in 0.18. There's a couple of new working groups for IPFS. There's a data transfer working group called Move the Bytes, which is being headed up by B5 from the IRO project. And there's a content routing working group. You can, there's Slack channels for both of them if you're interested. Yeah, so upcoming delegated content routing by the end of two weeks from now, we expect SID.contact to be available on all IPFS.io gateway requests. Currently, it's enabled on some small subset of them, so it's not reliable, but we're rolling that out to all the gateway nodes so that they can discover who the content providers are from the SID.contact indexers. And we're going to finalize the design for ambient discovery of content routers so that we don't have to hard code any indexers like SID.contact into Kubo. They will just be discovered by asking around on the network. And we'll release Kubo 0.18, which will include some new response formats. It'll add the HTTP API and remove reframe. Web transport will be enabled by default, which was a popular topic in Lisbon. And we're also starting to consolidate all of the Kubo libraries into a single repo called Live IPFS. And then in January, we've got verifiable IPNS, optimistic provide, which reduces the amount of time it takes to add content by a whole lot. And we're going to start working on some double hashing improvements to improve your privacy on the IPFS network. Thanks, guys. All right, try and make this quick. So we've already got the name drop a few times. Already in the slide, so new name Ignite. I want to welcome our new team members, Nashant and Dan. They've already been doing some great work. Thanks, you guys. There was a new release of IPFS companion for the first time in a year and a half. That took a huge effort. Big shout out to Lytle, David Justice and Nashant there. Star Maps, you've heard about already, but I do want to thank everybody who contributed with GitHub issues, PRs, Slack comments, anything and everything. And then we're working on metrics. That'll be kind of our first priority for our roadmap to get numbers for all of our products. We've got some here and yeah, we'll work on fine-tuning those. I've tried to link the issues for tracking that. Yeah, so that we can give you more information, more metrics on slides in the future. And then the list of upcoming, I won't go through that. You could read that, but that's about it. Hi, everyone. This is the IPJS highlights since the last little hands. So we've shipped a couple of things, like we've basically been concentrating on hardening efforts for JSL and P2P. This is basically to support chain safe and load star with the Ethereum 2 merge. So there's a lot of much greater DOS protection and Eclipse attack protection now. We've got documentation on how to protect yourself against common attacks and how to tweak limits on memory usage and connection limits and how to ensure that you are connected to the peers, that you value the most. We've dropped support for V1 signatures in IPNS. That's been the IPFS release, which also includes the LIP to P release. Yeah, lots of stuff, lots of small bug fixes and performance improvements. We've done a bunch of talks at IPFS camp, where our links are available. You can watch them if you miss them. Yeah, we're trying to grow the team. We're going to ship a new LIP to P next week that has revamped metrics. Loads of stuff, it's just lost going on. I am going to hand over to somebody. All right, greetings from Snowy Mammoth Lakes, California. I'm Marco, I'm here to give you some LIP to P news. You can use. So we got a lot of stuff here. Huge highlight, WebRTC browser to server is out, it's merged. It was a huge effort. We had like 400 plus commits on the spec alone. We started this like in May, but the ideas have been floating around since 2019. It's now enabled by default on the small dot network.  Some other news is we got a spec for how to do LIP to P on top of HTTP. This is going to enable a lot of use cases. And so if you're interested in this, please reach out to me or any other LIP to P person. We're kind of looking for someone to like tear with and like develop this in tandem. I think like a lot of the new data transfer protocols might want to do this. We got a performance spec out, which will help establish a standard for how we talk about performance. We got some test ground interop work we're doing. In Lisbon, we had our first ever LIP to P day, which, well, I got personally sick and couldn't attend from everyone I talked to. It sounds like a great event. So you should check out the recap post. There's a lot of really good talks that happened there. One of my favorites was Tangi's talk on NIM LIP to P. So I recommend that one. I thought that was a really fun one. Patar also did a really fun power of two choices on how like the Kedemla DHT is balanced. We have a new dock site, which looks really snazzy. Thanks, Danny, for that work. And we're updating the roadmap from user feedback. So we're now prioritizing LIP to P and HTTP work. For implementations, we got a new version of Rust LIP to P, which has quick. This is huge, quick is awesome. It will make your connections have fewer, a fewer latency for your connection. And this is a project that started like four years ago. So it's great to see it out. We have browser to server in Rust LIP to P. We have a new version of build to P to P coming out soon. This is going to allow you to listen, web transport and quick on the same port, which means you're not going to have to open up and deal with new firewall rules if you already have quick set up. And we also have deterministic cert hashes. So if you restart the node, you don't have to now propagate a whole new multi adder for a web transport. Jase LIP to P. Alex talked a little bit about this, but we got metrics and observability. Okay. Feed mode coming up December and January, we got generating LIP to P KPIs working with test ground, better interrupt testing, more browser connectivity, and we're going to launch a LIP to P blog. All right. Paul Quinn. Again, we're decentralized crypto powered as storage network is what we're trying to build here. KPIs again, today's like now we'll talk a storage capacity. It's a little bit degraded because we just shipped a network upgrade yesterday. So while we do that work upgrades, normally we will have to slower recover the power due to a sort of further upgrading their nodes and possibly like missing window post. But as of today, the network power is like 15.31. Exhibits is still a lot. And as you can see, there are more data getting onboarded onto the file coin via deals. And gradually we're almost 400 PIP for the data. We also hit a new daily max of committed deals, which is like four PIP a day, which is like amazing. So we are pretty, we are only one PIP away from our fifth PIP per day goal. So, you know, that's quite cool. Some high level file coin highlights, they have heard about the shark a lot over the past couple of months. And it's finally released yesterday. We have landed a lot of like Alex work that set a really good foundation for user program. They like smart contract upon FEVM launch. Also like set a good foundation especially for the storage market set of the things. There's a shark block with all the details. So if you're interested in that, I just want to say huge congrats and thanks to the whole team send like mostly the lowest team and also a lot of support from the field info, the Sentinel team to help us like making sure the network upgrade goes smoothly. And we have the matrix to monitor the healthy of the network. The next thing is we have Travis has shipped a new lightweight file coin to Snapshot Service for the file coin community. I see a lot of you probably know that to join the file coin network it's basically impossible to think from like Genesis. So a lot of the operators and sort of others are dependent on Snapshot to quickly sync up the chain and interact with the chain. So Snapshot Service is like quite important. Since yesterday's upgrade we are already seeing over a thousand requests and downloaded just yesterday and over the past week there are 3700 of requests for the new Snapshot Service which is quite amazing. I believe we will have a spotlight from someone from the FEM team on this but there's a hack FEVM that was a hack zone at the East Global which a lot of like EVM related developer resources was shipped to the community and they are worth over like 400 registrations and there's over 100 registrations of the final applications which is quite important, quite amazing. And also most importantly, there are six bugs that was discovered through the hack zone which helped us like hardening the FEM implementations. Again, there's a spotlight later so I won't go into the details. Last but not least, I do want to mention that SP Girls Team has posted a discussion on Network Girls and the current challenges and proposed solutions as you may hear the talks from the places. There are micro economy challenges in general for the crypto industry. So like how does that impact that fall coin? What kind of the fall coin challenges are we facing? And how can we propose some protocol changes potentially help our community and ecosystem? It's quite a topic that we're trying to discover right now. So please take a look at that post and if you have any ideas, please share in the discussion. Upcoming FEM team is launching a hyperspace test network that's developer focused, I believe potentially it's going to ship on December the 8th, FEM team should confirm that. But if you know anyone that is interested in develop like FEM, EVM, Compatible Smart Contract or like applications on the network, ask them to join and test their smart contracts in hyperspace. And also the coordinates are working really hard to align on what to include in the NV-18, the next network upgrade, the scope and the timeline. If you're interested in the TPM forum, there's a discussion you can follow on. I think that's everything for fall coin. So IPDX developer experience, IP stewards team.  So you can visit them, comments, let us know what you think. Next item, our collaboration with Voxicon, Testground on EKS came to fruition finally. And the alpha version is out. And Celestia is already using it in their testing scheme and running it on scale. So that's exciting. On the Testground site, we do fully support large test matrices that sleep P2P is going to use and is working very hard on making it easy to maintain and present on their site. So that's really great too. We were working with little Bearlabs on browser support in Testgrounds. And we do have a working example of that as well. GitHub management landed in three new orgs. And one of them wasn't even set up by me. So that's really cool. We've been to IPFS camp and our very own Laurent presented a talk on interrupt testing in the P2P with Testgrounds. I highly recommend watching that. And Testgrounds is finally being used by devs all around by the P2P, Magma, Celestia, Iron, Sigma Prime. So it's really great to see our efforts actually paying off. There are plenty of things we want to focus on next on the Kubo site. We're working on CI migration to GitHub Actions and release process automation and on Testgrounds. We are moving integration testing to go from bash. We are going to improve network simulation to be able to provide even more reliable network simulations. We are migrating docs off of GitHubook, which is almost done. And we are going to start collecting data on GitHub Actions. And Testgrounds 2022 report is coming out soon. Keep an eye out for that. More interesting stuff of what we've been up to is going to be included there. Thank you. Cool. Team updates. This cycle, we're moving on to a cadence where I think every three months, every quarter, we rotate through a various subset of teams to do slightly deeper dives into what they're working on because we have a lot of teams now. A lot of awesome projects happening. This month, we have Consensus Lab, Producers on Lab, DAG House, Sentinel, and D-Rand. So starting with Consensus Lab. Great. Thanks, Molly. So Consensus Lab, I will just give an update since the lab week. So the big day was actually this Monday when we shipped the SpaceNet. So SpaceNet launched, as we promised, on November 28th, as per our roadmap. And so far, it ordered already 1 million blocks. And if the math doesn't work, this is because we did some pre-mines. So basically, we launched the network actually last week. And then when we were not resetting it on November 28. But OK, I mean, there is no, if you want to get some tokens, just go to our faucet and start playing with it. So far, you can send very fast fields around. So you can send Filecoin the latency of one second. And this mimics the Consensus protocol that we are using mimics what we are going to use on L2s and beyond. But what we did is essentially we integrated this Consensus protocol with Lotus, although it was Lotus. And this took us most of the engineering work, basically, in the last few weeks. We launched the fill space latency, or no latency. I'm reading what one post. Fill space, basically landing page for all things IPC. Go there to check, basically, updates on IPC. And then basically for SpaceNet, there is a set of on GitHub, there is a landing page, which takes you wherever you need to go. Enric Moniz joined us on November 21 as a research engineer, very experienced. So this is our most experienced hire. And we expect a lot from Enric and welcome. I did have a one bullet where I mentioned the Consensus Day. We deliver Consensus Day after lab week. So this was on November 7 with ACMCTS. And so we had a plenty on our table, basically, since lab week. We are looking forward to winter colo with a few other people. We are going to be strongly represented there. Strong hiring pipeline waiting for head counts and hiring strategy yearly. And basically, we're working with those crypto net team. This is a great opportunity for us to bring them to the SpaceNet. And yeah, so Pikachu is also getting some attention as we are invited to write a cover blog on one of the smart contract research sites just today. Thanks a lot. Awesome. And if you are curious what Pikachu is, go into the Consensus Select channel and ask. And also post your best meme of Pikachu. Moving on to CryptoEcon Lab. Dave. Cool. Thanks, Molly. Hey, friends. Dave here from CryptoEcon Lab. Let's start with updates at the top left. The FVM rollout is anticipated to affect the gas economy. So if you follow that little arrow over to the right, the diagram kind of goes over that. Basically, the problem that we're looking at there is that more messages from FVM equates to some transition phase before base fees then equilibrate. That will probably be higher with more messages occurring. So then you have that little delta T there. There's a transition phase there. We need to do modeling to project what the trajectories of that transition phase are going to look like, how much time is it going to take, and ultimately, what's the magnitude of that change? What does that do to the economics, the ROI, that sort of stuff? So that's kind of the game plan there. We have a work plan and a discussion on GitHub that's linked in the bullet point. We're asking for feedback, questions, and ideas. So please check that out. Another update, number two, we're working with the Saturn team. We're exploring upgrades to the current incentive design with respect to collateral mechanisms, putting down, staking some collateral, and then maybe breaking out rewards into regional segments so that different cost regimes have different reward structures that may be better tuned to them running well. Third update, we are drafting a project proposal to do a incentive design for compute over data. So all of those links are there. Opportunities, the one that we highlighted, Jennifer brought up this new discussion that the ecosystem team put out. There's continued macroeconomic and cryptoeconomic challenges. They articulated them very well. So our team right now is listening to community feedback or analyzing potential enhancements. We have a few tools in our tool bag that we are thinking about applying. So we're tuned into that discussion very much and we just wanted to highlight that for other people. Where to find us, we have our links there. The one new thing I'll point out here is that we have office hours that we're just starting. So love to have you come join us. We have one per month in the America's time zone and one per month in the kind of Europe, APAC friendly time zones. So thanks a lot. It's awesome, great technique and something other groups could emulate. DAG house. Hello, this is David with an update for DAG house. So NFT storage crossed 100 million uploads. That is a ton. In terms of just general growth between NFT storage and web-free storage, things are holding fairly linearly, not a big drop-off since the winter started. So crypto is cyclical, but it turns out data storage is not. So that's great. The team is all hands on deck heads down on finishing W3UP, which is our new, you can authorize upload API and client and integrating it with web-free storage and NFT storage. And we're really excited about the potential view cans here. We talked to a ton of folks in Lisbon who gave us very useful feedback, but also gave us kind of the thumbs up that this is a great direction. But as soon as you expose delegatable verifiable off, it just exposes a ton of searches area out there. So you got to worry about it at like the protocol level is the protocol you're designing, something that is going to be future-proof, but then also think about all the service area in terms of user stories and user experience, making sure that's exactly what users want and you're not leaving a ton exposed to things like attacks. And then writing a new backend authorization system, something that can take in metrics scalably, that sort of thing. So yeah, it's a ton of work not to mention migrating all the users from the old stuff to the new stuff. So I'm really glad that we have such a great team working on that. Thanks to everyone there. And then just an update on the NFT storage front as we proceed to nucleation, we hired a NFT storage lead PM, which is great. She'll start in January and start to carve out a small portion of the team to work on really the dedicated NFT storage mission as it continues to be built on the web pre-storage platform. Still looking for a lead tech lead there. So if you know anyone who might be interested, please do let me know. As far as opportunities go, just in general talking to a ton of potential users in different spaces that really kind of share what content addressing and decentralized storage can really be game changers for in their spaces, places like gaming with Unreal Engine, video, the web-free dev tools with the Koi team and third web folks like that. So really kind of just flushing up where we might rediscover product market as we view it as a paid product. And then we're also chatting with RedRock in terms of how as their efforts proceed, we can take advantage of increasing the amount of infrastructure or the file points side of infrastructure we're relying on in production for users and kind of serving their needs as reliably and quickly as possible. And that's it, thanks. Awesome, congrats on passing 100 million. Very impressive. Sentinel. Thanks, Molly. This is Birdie from Sentinel. So yesterday we shipped the new release to support a new network upgrade. There was some hiccups but things are back to normal and we are trying to fill all the gaps hopefully by the end of today. With this release, we are providing new schemas that minor beneficiary and data cut balance, the data will be available. And we are also migrating to a new infrastructure along with some performance improvement that will help us save the cost in the long run. And we are ready to deprecate the old cluster in the staging and production cluster accounts. And that will easily save us 10s of 1,000 per month. This update we have archived a great daily file coin snapshot since Genesis. So this will help us facilitate a full-chain reprocessing more easily going forward and it will make it possible to put those snapshots on IPFS or Filecoin in the future. And opportunities, we are in talk with Ken Labs for some potential collaboration on Open Data Lake idea. They are already running Lili themselves and they are interested to use Lili for their project and will be willing to contribute to Lili in the future. More things to follow. And second, we are still aiming to provide the full-chain data in BigQuery by the end of the year. And hopefully we can apply for the BigQuery public data set. And we're also looking to see if there are potential collaboration with Google. I heard they have some public chain state indexing spec and we'll see if there's anything we can put together on that. And that's it, thanks. Awesome, thank you. Jolin, D-Rand. Hello. So this is a bit more than just what happened since Lisbon but basically all partners have upgraded successfully to be 1.4, which is the biggest release we've had of D-Rand since last year. So it's a pretty big milestone for us because it means all the work and all the commits we've done, that break D-Rand. We did not get any downtime, thanks for Lisbon. So everything's fine on that front. We already mentioned it in Lisbon but Star Swift has started running a relay. So here is the URL. If you want to add it to, I don't know, Lotus or whatsoever, you can start using it. It should be working just like the Cloudflare and the Protocol Labs Relays. We had a bit less participation than we expected in the LOE and Front Summit in Lisbon but we had very interesting conversations that already led to a couple new people applying to join the LOE, well, companies applying to join the League of Entropy and that's pretty cool. We are also working on challenges we've discussed in Lisbon. So yeah, that was super effective. We were still working on maintenance upgrades. The Patrick is currently doing a huge refactoring of the DKG which should really eliminate a whole class of bugs we've had in the past during DKG where suddenly one partner would get excluded in the ceremony or it wasn't meant to happen. So that's pretty cool. We are working on launching a new network, hopefully next week on testnet and then a new network the week after on mainnet. This new network will have a swap of the pairing friendly curve we're using. The groups G1 and G2 will change which means we will have smaller signatures which is super interesting because we have a lot of signatures. So the smaller the better, it will lead to a fee. Beside that, if you want to join the Slack we have the link at the bottom and we have more and more people joining the Slack. So currently we're at like 145 people which is pretty cool. We submitted the time lock paper to RealWatchCrypto 2023 which will happen in Tokyo. So that's pretty cool. We are hopeful it will get accepted because it's a way to turn the existing DRUN network into a network that's provide time lock capabilities. So it's a pretty fun paper and it's already live anyway. And oh yeah, we've launched them when we've started the audits of the time lock code with Kudalski security. They already found a few bugs we are looking to fix soon. And yeah, nothing critical but it's ongoing. We will look into setting up fuzzing of DRUN for Q1 2023. And yeah, that's it, my sign. Awesome, congrats on an amazing gathering and very excited for a lily expansion and time lock. We are now in our spotlight section and the first one highlighting the Entrez Summit which was a gathering as part of Lisbon Blockchain Week where we got folks together from these various different teams within the Entrez working group and shared our progress and accomplishments over the past year, what different teams had worked on. You can see this video that is up on the PL YouTube channel with a lot of chapters where you can jump around to specific teams. You can link to specific teams, highly recommend people like, what did you do this year? Share this video. Very useful to get a quick index. And we also each presented roadmaps for next year. These are work in progress and will change. We will present them again in January once they're finalized, but a great first look into what each group is going to be focusing on for the next year and seated a lot of really good conversations during Lisbon Blockchain Week. Yeah, hey, you know those folks and it's actually really, really fun to rewatch this. So I recommend it even for people who are there in person to page back in. You've probably forgotten some things. Ryers, Nicholas, tell us about deals. Hi, Rebonne. It was brought to our attention that storage providers were struggling with snap deal. We located the pain points, worked our way down the initial list and the team managed to fix almost every snap issue reported. And to make it even easier for the storage provider, the TSEs made the different ceiling layouts and made diagrams on what works and what doesn't. There are no new optimizations, but during testing and running the latest hardware, we managed to turn an empty CC sector into a deal sector in less than 15 minutes, which is really fast compared to ceiling a new sector. There are three issues left on the board, but they should not be a blocker for any SP that wants to use the feature and onboard data fast. All the fixers will land in Lotus version 119, which will land in one week. And a full report with all the highlights from the spin will be available on motion. That's it, thank you. Awesome, much requested, much needed. Thank you so much for doing that. I'm sure the SP community thinks you as well. Space.net Alfonso. Hello, everyone. So Marco already hyped this, but we have Space.net since Monday and you can start running your own full node. You can start getting some test file coin and soon you will be able to become a validator in the network if you want. So right now, that's why we call it soft launch. Right now we are running our own validators and we only allowed full nodes, but what you should expect from this is first to provide samples for fast syncing. Like we actually started on Monday, the network. Now we're in 1,000, like when I was doing these slides on Wednesday, we were in the 700s. Today we are 1,000, so this is growing fast. That's what one second block times means. So it means that now full nodes, like they have to spend a lot of time until they sync. So we need to start figuring out how we're gonna manage snapshots or periodic snapshots for full nodes to be able to connect to the network and support light nodes, in case someone wants to drag with the network without having to run their full node. And then once F EVM lands Lotus Master, we also will support solidity contracts in Space.net. So that eventually will lead to not empty blocks and actual traffic coming into the network. And that's it. Like there's a Space.net consensus ninja for the faucet and a Space.net repo if you wanna read more and we have a demo afterwards, in case you wanna dive into the network. Thank you. Awesome. Lots of questions. Straighten the Slack channel. On to Dennis for Nat Hole Punching. All right. Hey, everyone. Quick update from me that we are a quick reminder that we will be running in Nat Hole Punching month during December, which starts today. So I highly encourage everyone to download a tiny tool to help us in this measurement campaign. So we want to measure the success rate of the decentralized Hole Punching that was implemented in Rust and Goad and the PTP. And yeah, well, the only thing that you need to do would be to download one of these clients and which will, yeah, one of these links on the left. And if you're on a Mac, you would see the thing that's on the right there. So a little menu bar icon and, well, you just started up and it's in the best case it says running and that's it. And you leave it running throughout December and it will send, well, just results of Hole Punches to our server and we will analyze this during January. You don't need a running IPFS node and actually no technical skills are required. For the more tech savvy people, there are also command line versions or Docker files also answer the Galaxy configurations. And also you can also register on a Google form with the link is on the bottom left there and provide some more information on your home network and so on, which will help us in our analysis at the end in January. And well, we have already 80 active API keys as you can see in the top lower right. And yeah, please download the client and participate. So thank you. Awesome, it's super, super, super easy. Get started and last but absolutely not least, Hack FBM. This is Raul, I'm heading in for Sarah who's in a 17 hour journey right now and she can't present. She basically put this together with Nikki from Outikor and other Outikor team members. Hack Febben was a hackathon in collaboration with ETH Global earlier in November and some top line stats there, 400 plus registration showing very strong interest in the FEM. We had 117 projects submissions, which is a one to 3.5 ratio, which is one of the strongest ratios that ETH Global has seen so far. This was amazing because Febben is really being incrementally delivered. We shipped features, key features the day before to the wannabe testnet as long as together with a Filecoin mock solidity library that Zondax put together for this. And literally this was like bleeding edge going out of the development pipeline into the builder community with like minutes in between. And it was also a great forcing function to actually get all these deliverables from the team, getting a ton of testing done and also DX Clarity around a bunch of things. Some insights about the submissions, data DAOs were by far the most popular use case accounting for 30% of the submissions where Febben was basically powering storage proposals, DAO operations and token minting. DeFi was the second most popular use case accounting for 9% of the submissions covering things like liquid staking, lending, automated AMMs and sold bound tokens which were a concept introduced to the Web3 space earlier in 2022 were also very popular and people were marrying sold bound tokens with data primitives which was pretty cool and pretty unprecedented here. And I think there's a lot to that and that yielded force admissions. Now this was a great exercise for the team as well. We came back with a ton of learnings and some of those were, we need a lot more comprehensive developer resources. We kind of like, you know, this was put together very rapidly and we stitched together resources from the forum, from DAOs and Sondax DAOs and a bunch of other things so we need to really put a lot of work there. We also need a clearer value proposition of why existing EVM developers should care about Febben. So there's a lot of more messaging clarity that we need to land there and also to be able to scale to other blockchain communities and new communities so we need a much better filecoin primer for developers. So these are things that we're working on in the FEM team and yeah, you can see all the submissions in the first link at the bottom of this slide and you can see a recap that ETH Global also posted in the second link. Super cool. If you are excited about building on FEM, check out the new RFS requests for startup that Royal Woolen team actually just put together as well. It's awesome sauce. Quick note on Phil Bangalore. So we had a, in a very fast-paced huddle 01 which is a project that started on top of Filecoin. They are a group that started with HackFS which was one of the first hackathons that we did with ETH Global. Maybe the first one, actually, right around Filecoin at launch and has since become like a pretty strong startup in the Filecoin ecosystem. Organized Phil Bangalore and it was a huge success there were about, you know, over 1,100 attendees, primarily developers, there were over 30 speakers and over 20 workshops or something like that. There were several workshops for key interest projects like FEM, back allow, and so on. A ton of demand and attention for FEM and computer data and so on. You can see the workshops here, like they were super packed. So a ton of like learnings from all of that. And I guess a great learning here is that the Dev community, India and Web3 has exploded over the last couple of years. Like it's just super massive and there's a lot of interest in demand in our tech. So for all of our projects, I heard about, I heard from developers on all of the stuff that we're working on, from Lippitopee to DRAN to all kinds of things. So there's a huge, huge developer community that's paying a lot of attention to what we're doing and also super interested in contributing directly to a lot of the core protocols. So I got a ton of questions. I'm like, how do I contribute to Lippitopee or how do I contribute to IPFS and so on? So I directed a lot of folks to repo. So it should be hearing from folks there. And I think we should probably have a much stronger presence from our teams out there in 2023 and could be a great place to both recruit and to help form teams to participate and work on a lot of these projects. And from Phil Bangalore, we're gonna have ETH India starting tomorrow which will be another hackathon and also strong presence in Polygon Connect. Awesome. We mentioned the FEM RFS, the request for startup. Pretty awesome. There's a ton of great examples there if you are looking for something to build over your holidays or someone in your connected set is looking to start something really cool in the Web3 space, send them this. There's some really, really great ideas that can be super high value and could lead into that. But cool, that is it for our Andreas Allhands. Thank you all so, so, so much. Really, really amazing to see this progress and I don't believe we have another one of these before we hit our holiday break. So have a wonderful holidays, everyone who celebrates and come back well rested and pumped for the amazing set of things shipping out the door in 2023. It's going to be a legendary year and I'm super excited. So hope you all are too. Get a rest, cause it's gonna be awesome. And yeah, thank you all so much.


Once a distant pipe dream, the Alberta tar sands have become a startling reality. This mega project covers large areas of boreal forest in Northern Alberta, requiring giant machines to separate the sands from their most valuable component, oil. As the industry has boomed with the rising price of oil, so too have local communities, which are filling with migrants from all over Canada and the world. The tar sands raise many questions for those concerned about justice, peace and sustainability. While this industry has created jobs, energy and growth, it has also fueled inequality, pollution and ecological destruction. Instead of seeing the tar sands through the narrow lens of energy, economics and employment, Kairos is connecting the drops to include the people involved and impacted by this development. Understanding the tar sands demands a big picture perspective, one that sees the links between our lives, our economy and our environment. To learn more about the tar sands and their impacts on people and the earth, Kairos sent an ecumenical delegation to Alberta from May 21st, 27th, 2009. That we as citizens and we as members of Christian churches have the opportunity to make right decisions that will bless the earth. It was even more complicated than I had imagined beforehand. Every group that we spoke with, environmental groups, local community people, for example in Fort McMurray, Aboriginal groups, government, industry, they all had slightly different perspectives even when they quoted exactly the same facts. It's certainly not a simple problem and it's certainly not going to have simple solutions. They appreciated the fact that we didn't just come here or go there wagging our finger at them. We came to listen and to learn and to see how we were involved. Our group is here to listen, to listen to your concerns, to listen to how life may have changed or have changed drastically after the industry of tar sands came in. Our goal is to work hard as a team, this delegation, throughout the journey to listen, to share our concerns and in the end to see if we can build common ground for an ecumenical witness to what we learned about the tar sands development. 173 billion barrels of oil in tar sands are recoverable with today's technology. Only Saudi Arabia has more oil reserves. Oil sands operations cover 140,000 square kilometers or an area the size of Florida. There are currently 91 active oil sands projects in Alberta. Per barrel of oil, 4 tons of material is mined and 4.5 barrels of water are required to extract the bitumen. The tar sands generated 4% of Canada's greenhouse gas emissions in 2006. This percentage is predicted to rise to 12% by 2020. Extracting oil from the tar sands consumes 10 to 30% more energy than conventional oil sources. The extraction process produces 200 million liters of tailings or wastewater after recycling. This is enough to fill 82 Olympic swimming pools. 1.2 million tons of sulfur is produced as a byproduct. In 2015, this is predicted to rise to 4.1 million tons. In 2030, 10 to 12 million tons. 51 cancers occurred in the indigenous community of Fort Chippewan between 1995 and 2006. Statistically, only 39 cases were expected. First Nations communities have launched a total of three lawsuits against the government for inadequate consultation and treaty rights violations. One in 13 Alberta jobs is related to energy. 15,836 temporary foreign workers were in Alberta in 2005. This rose to 37,257 in two years by December 2007. 18,000 tar sands workers currently live in work camps. The average family in Fort McMurray earns $135,000 per year. The average single family home costs $621,003. In 2001, the population of Fort McMurray was 42,085. By 2007, it had risen to 65,400. 71% of Albertans agree that no new approvals should be granted in the tar sands until environmental concerns are addressed. Zero environmental impact assessments have been done of potential oil sands projects. 0.2% of land disturbed by mining has been reclaimed. Zero tailings ponds have been reclaimed, though the process has begun on one. Our cities and societies are often isolated from the natural world, and so we forget our spiritual connection to nature as a part of God's creation. As life becomes faster and easier, we see nature as an unnecessary luxury, useless and less exploited. God has blessed us with natural resources that all humanity might use them sustainably. Instead, we have parceled these out for ownership and development by select groups. What are human beings for? How are we to relate to the earth and our place within the body of creation? We've got to get rid of the mentality that human beings are the pinnacle of creation. We are the same. We are part of all living things in the earth, and therefore the spiritual question is what right do we have to exploit the earth so dramatically without questioning why we are doing it, and we should not be doing it just to feed a pathological addictive consumerism. The impact of flying over the oil sands and watching and seeing these giant, giant machines in operation and knowing that they run 365 days a year, 24 hours a day, they never stop, those belts never stop moving, and in such giant proportions, that's very dazzling. And at the same time, it's a bit frightening to see how we are so aggressively minding the earth. The impact of the tar sands extends beyond expectations, reaching across borders and between families. The tar sands have a destabilizing social impact for countless workers, their families, and surrounding communities. Worker migration from Canada's east coast divides families for months at a time. Workers from other countries are also arriving through temporary foreign worker programs, which do little to protect these migrants from exploitation. Employees work long, hard hours in often isolated conditions. Municipalities such as Fort McMurray have also felt the strain. Health services, schools, and other infrastructure lack funding and are unable to keep pace with the increasing population. The tar sands' most visible and lasting impact is environmental. Hundreds of square kilometers of boreal forest have been destroyed, and attempts at reclaiming used land have, to date, created non-indigenous, biologically uniform spaces. Huge amounts of water are required to refine the sands, threatening to reduce the volume of the Athabasca River. The refining process creates waste, much of which is stored in man-made tailings ponds. The water quality impact is not well understood, and the risk of contaminants leaking from these ponds into groundwater is significant. Extracting oil from tar sands produces more greenhouse gases than any other form of fossil fuel production, increasing Canadian emissions, at a time when every effort must be made to reduce our carbon consumption. While the tar sands are extremely profitable, this profit does not equally benefit everyone. The rate of growth has placed an economic strain on surrounding communities. As more people migrate to Alberta to find employment, the costs of housing and basic goods have inflated to unaffordable heights. Instead of benefiting low-income residents, much of the profit remains with shareholders and company executives. We also need, in our discussions in our dialogue, to highlight the social and environmental costs of oil production, not just in Alberta, but all over the world, because this cost has not been included in the cost of oil. It makes oil very cheap, but we know oil costs life, it costs the environment, it costs families, stability, and all that. And we must associate this cost, we must calculate this cost, and let people decide for themselves which is cheaper. I was talking with the chief of the Miksukri, and she was saying that on the one hand, the elders are telling her that the development needs to stop, and the emphasis needs to be on the environment and on the spiritual wellness of the people. And on the other hand, there are other members of the community who are saying, and those who are heavily involved in some of the business aspects relating to tar sands development, who are saying no, we need to go ahead because of the economic benefit that this has for our community. So even within a small, somewhat homogenous community, there's diverse and conflicting opinions about which direction to go. With every layer, it gets more and more complicated in terms of figuring out what indeed the truth is, and what's the best way to proceed, not just for the benefit of each individual, but for the benefit of society as a whole. Because if we don't, we have now, there's going to be a tremendous catastrophe that's going to be happening today, it's going to be natural, it's going to be man-made, you know, and we are all going to be affected from it, so we just don't want to see it because when you see the young generation come and dance in here today, you know, what's going to be left for them in the future if we don't fight for them out there? They are people who live with the effects of the tar sands, the job creation that is there, some of the folks who have well-paying jobs in the tar sands operations, to all of the cancer questions that are being raised to the use of their land that is being so deeply affected in terms of wildlife and their spiritual relationship to the land. And these leaders, one of the things that impressed me is that they asked penetrating questions and they talked very gently and passionately about how the tar sands is affecting their communities. They also, of course, raised the question of the common good, and who are the tar sands for? The tar sands involve many people and organizations with the power both to encourage and discourage development. Both the provincial and federal governments have the ability to regulate how, when and where development takes place. The government could respect indigenous territories and set aside land for environmental protection. It could enforce best practices to minimize emissions, waste and water use. It could sponsor research into the environmental and health impacts of the industry, which would provide a better understanding of how to manage development. It could invest in communities to ease the effects of inflation and population growth. And most importantly, the government could influence the direction of future energy projects, investing in renewable energy instead of throwing full governmental support behind a tar sands economy. Global demand for oil also drives the exploitation of the oil sands. Canada exports over two-thirds of tar sands oil, most of which goes to the United States. Canada is the leading provider of oil to the United States, and this export relationship will only grow with current campaigns for secure sources of oil. As the architects of the tar sands, industry bears obvious responsibility. Despite being tied to profits, companies have the ability to improve their practices and working conditions. Industry research into and refinement of technologies to rehabilitate the land, reduce carbon emissions, use less water and better refine and store tailings could result in significant progress in managing the impacts of development. We cannot exclude ourselves from responsibility. Our northern lifestyles depend on an oil-based economy. Some of our daily routines incorporate activities that we don't connect with this dependence, buying fruits and vegetables, taking a shower and traveling to work to name a few. Living a more ecologically conscious life will lower the demand for oil and help us shift to a more sustainable society. People who enjoy the benefits that flow from the lifestyle that the oil sands and other energy policies and realities give to us. All of us are part of the tar sands mentality. We all rely on oil and gas and that means that ethically then we all are involved in seeking solutions without demonizing particular people or particular organizations. We're dealing with a society that is addicted to oil period and that's one larger question that most people don't want to begin addressing. I mean, I find it hard to seriously address on my own because it's so challenging. It's a way we live and the consequences and changes we have to make on a personal level as well as at very different levels of corporate responsibility. One of the things that really impressed me was the extent to which if we can develop the technology and develop big machinery to chew up the earth to get at resources, we will do it. We don't have any sense of perspective or restraint. Just the extent of our appetite to exploit the earth and not asking the question of, what do we need to do it so fast? The development of the tar sands is both a crisis and an opportunity. The pace and scope of development have clearly created social and environmental havoc, while unequally distributing economic benefit. At the same time, the tar sands allow us to examine our dependence on oil through multiple lenses and emerge more conscious of our unsustainable lifestyles. There is no escaping the tar sands. They are in our own backyard. The sooner we transform our concern into action, the sooner we will implement real, hopeful solutions. Change has to come about. The church, from what I've heard, has to be more creative. Practice our spirituality. Practice our spirituality through our children. We have to take our children down to the river. When is the last time we've done that? We all know, either as individuals or as a group or as a society, especially as a society, change is so hard and difficult to do or even contemplate because we embrace too tightly the creature comforts. It doesn't matter how complicated the situation is or the fact that it might be controversial. There is a role for us as individuals and there is certainly a role for us as churches to be involved. We are learning questions, learning as much information as we can from as many different sides and opinions as we can. And I think recognizing that we as individuals are going to have to do something to change our individual way of our addiction to oil, our lifestyle. But it also means that we have to pressure government to take responsibility and leadership in this area. And I think it's doable. In the end, I came away thinking this is not going to be easy unless we start, it's just going to get harder. So it's time to get on and begin the things.


Let's look at some diagnostics as well in Poisson regression models. So I will introduce some residual analysis briefly, just to sort of introduce some of these ideas as well. Although we've already discovered that based on the log likelihood test statistic and the Pearson-Quai-Square test statistic, the model may not hold, but let's look at what it does to the residuals and introduce what type of residuals there might be for Poisson regression models. And then we can later on extend our model to a more sophisticated model in particular using a categorical variable in the model or using another explanatory variable in the model. So let's look at diagnostics in Poisson regression models, residual analysis. And let's continue with our example from our previous session about the recall of stressful events. Residuals represent variation in the data that cannot be otherwise explained by the model. So that's quite a nice feature generally about residuals and they can help us. Residual plots can help us to understand our model better and to diagnose any particular problems. So the residual plots can be used to discover certain patterns, certain outliers, mis-specifications of the models. So basically ideally we would like to see a sort of random pattern in our residual plots and if there are some sort of more systematic patterns then we can identify certain particular problems and it can help us to reformulate the actual model. So if the residuals exhibit no pattern then in a way that's a good indication because that would imply that the model is probably appropriate for the particular data at hand. I would like to introduce three different types of residuals for Poisson regression models. So the raw residuals would just be the difference between the observed and the expected values. The Poisson residuals or the standardized residuals are basically the raw residuals divided by the square root of the expected values and then also the adjusted residuals and they can be rather helpful for actually the diagnostics and the actual plots that we are going to look at. So that is defined as the observed minus the expected values divided by the standard deviation of these observed minus expected values. So basically we've got adjusted residuals that we would like to look at and to use for our residual plots. So if H0 is true the adjusted residuals have a standard normal distribution with a zero mean and a standard variance of one. So basically at least for large samples that should be the case and looking at that for the recall of stressful events example that basically means that we look at the adjusted residuals and we would like to see how they compare. So we compare the observed and the expected values divided by the standard deviation of that. So we obtain the adjusted residuals and for each category basically for each month we look at the adjusted residuals that are greater or smaller than 1.96 comparing it with the normal distribution that would hold if H0 actually holds. And if you see this bigger discrepancy so adjusted residuals larger than 1.96 or smaller than minus 1.96 that would give us an indication that there is divergence from the H0 hypothesis. So if the adjusted residuals follow indeed the normal distribution which is true under H0 we would expect roughly one adjusted residual being larger than 1.96 or smaller than minus 1.96. So we would only be finding one large or a small adjusted residual we would expect. Now looking at the actual data we saw that in months 1, 3 and 4 we had actually positive adjusted residuals and in months 16 and 17 we had negative adjusted residuals that are larger or smaller than 1.96. And basically we see that it's actually more likely to report more recent events. So the positive residuals means that observed data is larger than the expected data and it's more likely to report a stressful event in the months immediately prior to interview. So we do see some sort of time trend probably in our data set that obviously isn't captured with the equity probable model. So we want to define our model in a better way or improve our model and we see in the next session how we are going to do that. Looking at the plot of adjusted residuals per month we also see a downward trend so the adjusted residuals are on the y-axis and the months are given on the x-axis and we can see just by plotting those types of adjusted residuals that there is a downward trend so again it's not a random pattern there's a downward trend and we might see basically the sort of time trend. Another way of looking at residuals are the normal QQ plots. So basically these are probability plots that plot the quantity of one distribution with the quantiles of another distribution and here we would like to compare the distribution of the observed adjusted residuals with the expected residuals i.e. the normal residuals from a normal distribution. So basically here and Q stands for quantiles i.e. for a quantile against quantile plots effectively. So basically we are plotting observed quantiles against these expected quantiles and hence we plot quantiles of adjusted residuals against the quantiles of the standard normal. That means that the points should actually lie just on the straight line of the y-equal x-line at least if the adjusted residuals indeed follow the normal distribution which is true under the h-node hypothesis. So again we can compare divergence from the h-node hypothesis. And here looking at the QQ plots from this particular data set we can see that in the tails so in the upper end and in the lower end there is divergence from the straight line relationship so again we would conclude that there is some kind of time trend in our data set. So conclusions are clearly that there is divergence in the tails from these straight lines. There is overall strong evidence that this model doesn't really hold, doesn't fit the data that well which maybe isn't too surprising and we would like to we'll see sort of more likely or we see that the data is more likely to report recent events. So basically such a tendency would result if respondents were more likely to remember recent events than distant events. So basically again there is strong evidence that we should be using some kind of other model and we are going to now explore the Poisson time trend model a Poisson model with a covariate.


All right, so we're here at the ID Tech Act show, here with Dex Matt. Hi, so who are you? Hello, I'm Colin with Dex Matt. So what do you do? We produce conductive materials out of carbon nanotubes. We basically adapted polymer processing using carbon nanotubes as the polymers so that we can make continuous threads or continuous thin films that are electrically conductive and also lightweight, flexible, high tensile strength and durable. So right here you're showing... Yeah, we just have a looping video and this is showing a couple of different things. This beginning of the video is showing part of the process of producing the filaments. So this is off-camera, this is a solution which we're extruding through a nozzle of many small holes to create solid filaments of carbon nanotubes. Just carbon nanotubes, there's no filler or epoxy. It's just a solid thread of aligned nanotubes. And then we can take those individual filaments and twist them together or braid them together into thicker cable. So that we can make yarn that's anywhere from a single filament of around 20 micrometers in diameter up to a thick braid of a millimeter in diameter or more. So is this special? Nobody else is doing this? There are a couple of other companies making carbon nanotube thread. We're the only one doing it, I believe, with this liquid-based, fluid-based process. Right here in the video you were showing that this is kind of like your machine? Yeah, exactly. So a moment ago you saw the threads being extruded from the liquid phase. This is now after they've solidified and this is just winding from the collection drum onto a smaller spool. This is a picture of the machine that we used to process it into a thicker room. We're twisting together many filaments into, as you see, a thicker yarn that we're winding up on. So you have some different nibbles right here? So you have that one? What's the other one? Yeah, so this is about 50 filaments twisted into a yarn. This is the braid you just saw in the video being assembled into this thick braid. So is it strong? Yeah, it's quite strong. It's a little bit stronger than steel, much stronger than copper. And so the applications, we think it's going to be very useful for multifunctional applications if you need conductivity but also mechanical strength or durability or lightweight. Then it'll be a useful replacement for metals in applications where you really need more than one of those properties. So is this how we're going to be making the space elevator? Hopefully. This is not quite strong enough yet. But if we continue to improve the properties that we're getting, that would be a fantastic use for it. It was one of the stories, right? They wanted to use carbon? Yeah, this is the material that people always talk about to make a space elevator. You need a certain amount of strength to make that. So carbon nanotubes on an individual molecule level are extremely strong, strong enough to do that. There's a great challenge in making a material that's this large, a macroscopic material that has properties that are similar to those of the single molecules. And so the challenge is to arrange them, put them together into the material in such a way that they reinforce each other that you can get, even if you can get a significant fraction of the single molecule properties, you already have a pretty useful material. That's how you make ropes, right, when you do a rope? Sure, yeah. There's a whole bunch of filaments that are put together in some kind of structure. Exactly, yeah, into a larger and larger structure. So you just do a rope of this? Exactly. You're done. Yeah, more or less. We can go to Space for Chief. That's one of the applications. So this is a similar material, but here we've just made it into the form of a strip so that it's a standalone film. And you can see, I don't mean to block the lens like that, but this is standalone film. It's also very flexible. It's quite thin. It's around 20 micrometers in thickness. But it's also literally conductive and extremely flexible. Durable? Yeah, quite durable as well. Is it not going to rip? Nope. It has alignment to it, so if I tore it down along the direction of alignment like this, it would tear like string cheese. But if I try to tear it across the direction of alignment, it's quite tough. They're basically good luck. It's not going to happen. Yeah. Right? Right. Something like that. So it's very flexible. It's got very good fatigue life and also very good tensile strength. So what would be the application for those? One of the main applications that we're excited about for this is actually in shielding for electromagnetic shielding for data cables, for coaxial cables, particularly in aerospace applications, or really any application where weight is important. It is much lighter than copper conductors. And so in applications where weight savings are extremely critical, in aerospace, if you make an airplane or a satellite lighter, you save on fuel. And that's quite a significant cost savings. And so that's one of the primary applications we're interested in, especially for this film. So you're talking about space? Yeah. And we can do that with the thread as well. This, for example, is a coaxial cable in which we've replaced the copper braid that formed the shielding layer with a carbon nanotube braid. You can also replace that with our carbon nanotube film that you just saw. Another application that we're interested in for this thread, because it's thin, it's durable, you can use it in sewing. You could stitch this into a fabric. And it's flexible enough and durable enough to be part of an article of clothing or other wearable electronic device. And then it's conductive? It is electrically conductive, exactly. So that means you can use it to send data around? Yeah, send data or send power. It's not quite as conductive as copper, but it's much more durable. And so if you need that durability or if you need flexibility, it's a very useful alternative to metal. Machine washable? Yes. And unbreakable? Not unbreakable, but pretty tough, stronger than steel in terms of tensile strength. Are you doing like, because when the US has a bulletproof vest or nothing to do with it? So I think for bulletproof vests, you'd bear off sticking with Kevlar. This is not quite as strong as Kevlar, and you don't need a bulletproof vest to be electrically conductive. But if you do, if in fact you want to incorporate electronics or some other devices into bulletproof vests, then you could incorporate this into a Kevlar vest as a conductive element. You wouldn't make the entire vest out of it. It'd be more expensive and you don't need it to be electrically conductive. And this is what you were talking about? Yeah. So this is a spool of the thread or a close-up of the braided thread that's been combined into a thicker cable or a close-up of tape. We have a website at our online store, dexmatt.com, if you'd like to... So people can go and buy stuff? People can go and buy stuff and then look at one of the properties. They can buy any of these properties, any of these products here. Yeah, the tape in several different widths. You have customers already? They can buy the yarn. Yeah, we don't have any, it's not really being used in any final products, but we have a few, we're basically selling to people who are making prototypes and are interested in trying it out for their applications and we're hoping that some of those will... Somebody's playing badminton with it. Does that mean the badminton racket can send signal about where you hit the ball? We didn't construct it in such a way as to do that, but yes, this is a badminton racket that is strong with our carbon energy. Does that make you have the best badminton racket in the market? What do you think of it? I think probably yes. We do. It's definitely the most expensive badminton racket on the market. The most expensive. So it's not cheap technology what you have? No, it's not. But it enables potentially embedding sensors and electronics directly into your strings. So you may be able to get information that you would not normally be able to get from a typical non-conductive type of string. And a typical material that's conductive would not survive the stresses about hitting this birdie multiple times, whereas the nanotube material can... It's abrasion resistant and it's much stronger than a typical metal wire. So on your store and... So hi, so who are you? My name is Dimitri. I'm the COO of Dexmat. And I'm here with Colin to show off our materials and try to get some... So on your store, how much is one of these? So this material right now is $100 per meter. Per meter, yeah. So as we said, expensive. Because the machine seemed to be going really fast. That's like $100 every second. But so a lot of that cost is basically the labor of us doing the synthesis and then also running the machines. So we aren't really producing at large scale yet. We're producing, let's say, hundreds of meters of this per month, but not anymore than that. So at a larger scale, that price will go down. What do you need to do to go large? What's next? We need to find customers that are ready to develop this into a product that is actually going to be sold to either consumer market or used in a final system. For example, in aerospace or in an e-tech style application that's going to be produced in large quantities. And then at that point, we'd be ready to scale up our process. And we think that this material, the $100 a meter material, we are able to produce it at under a dollar a meter if we scale up. If we were producing a lot of it.  If there's a big order and we scale up our process so that we're producing it in larger quantities. Because it's going so fast. Not yet? Well, this is making the rope. So it's spinning fast, but if you can see, the collection process is not the fastest. With more sophisticated equipment, it can go a lot faster. This is pretty small scale equipment, so it just goes a meter per minute or so. What's the materials when they come from? How do you, what happens? You just make them out of? No, so we buy carbon nanotubes from suppliers. We have a couple of suppliers we've worked with where we can make this out of any, not any carbon nanotube material. It has to be sufficiently high quality. In particular, the molecular lattices have to be low in defect. So unfortunately, we aren't able to use the cheapest sources of carbon nanotubes, but manufacturers of high quality carbon nanotubes were able to use in our process. Carbon nanotubes is a cool kind of thing, right? I think so, yeah. Is it the ultimate material or what is the story about it? No, it's not the ultimate material because it's not the best in terms of strength. It's not the best in terms of conductivity, but what it is is it's a material that has a combination of properties that is unlike any other material. So if you have an application that requires you to have something conductive and flexible at the same time, this is the best material you can use for that. If you need something that is conductive and lightweight, this is going to work better than any metal wire. So it's really a combination of properties that it has that is unique, but it's not the best in any one single property. So it's going to be everywhere? How soon? Well, anywhere that you need multi-functional material. Hopefully, if we find a good way to make these cables, then it'll be in everywhere in aerospace at any rate and maybe in more places as well. Realistically, we're probably talking five to ten years before you see any sort of widespread adoption, but it could be in consumer products within a year. So, for example, in the wearable space, because that is just ready to go with cables. What do you have? What's going on here? This is a wristband where we sewed in a couple of LEDs and they're just connected with the carbon nanotube yarn. And it demonstrates that you can use this carbon nanotube yarn to connect to electronics. You can show inside kind of whore. Yeah, so this is just a coin cell battery. And you can see that there's some CNT yarn on the back of it. And so that is what's using the connecting the LEDs to the coin cell. You could obviously have a more sophisticated setup where you have more sophisticated electronics. It doesn't have to be LEDs. It can be anything that you need to provide power to. And this can be put into a sewing machine. This was done by hand and needle, but it can be run through a machine. There's another wearable application that, I don't know if your video of our video will work out very well and let me get to the correct portion of it, but this is a video of a test that was done by someone who used our fiber to stitch our fiber into a bit of a space super fabric. And this is then covering it with dust and then running the current through the carbon nanotubes to repel the dust. Is it the current? It's just an AC current through the fiber. This is just demonstrating how you can really stitch that filament into fabric. It's very high voltage, so that's what causes it to actually repel the material. And what you do is nobody else is doing... Who's the biggest carbon nanotube companies out there? What are you doing? The biggest ones are producing the nanotubes. So there's a couple of companies that produce a ton of quantities of carbon nanotubes. And there's also a couple of companies that produce fibers and films. And so those companies include companies like Nanocomp, General Nano. Those are the U.S. companies. There's a couple of companies in China, Japan. But really, we're the ones that make the highest connectivity material. So compared to all the other companies, we have connectivity that's at least a factor of two or three higher than the competition. Cool. All right. Thanks a lot. Yeah, thanks for talking to us.