Cryptocurrencies, cannabis stocks, and CEO interviews brought to you by Rich TV Live. Hi guys, how you doing? This is Rich from Rich TV Live. I have identified the hottest stock in the world. It's true. Socoman Iron Corp. Socoman Iron Corp is a Canadian exploration stage company. It is engaged in the process of exploring its mineral properties. The company owns Clark's Brook Gold Property, Central Newfoundland Gold Project, Crippleback Lake Property, Star Trek, and Antimony Ridge Property, Iron Horse Project, and Burin Property. Look at this, up 35% today. Traded 15 million shares. It only has 58.37 million shares, issuing outstanding. Their US symbol is G as in George, D as in David, N as in Nancy, D as in David, F as in Frank, G, D, N, D, F. Its Canadian symbol is S, I, C. Look at this chart. It is a thing of beauty. Are you ready for this? I have not seen a chart like this in a long time. Look at this. On July 23rd, it announced the news that it had hit gold. It went from 3,000 shares in volume and 5 cents, and has exploded in 10 trading days all the way up to today. It is now at 42 cents, representing a gain of 700%. That's right, 700% in exactly 10 trading days.  What's going on? Well, G, D, N, D, F, Sokoman, Iron Corp is on the gray market in America, but even though they're on the gray market, it's still getting 688,000 shares. So that's interesting. Then when I look at Bar Chart, my goodness. Bar Chart has them as, are you ready for this? Look at this. Bar Chart has them listed as a 100% buy and ranks in the top 1% of all short-term signals. Longer term, the trend strength is in the top 1% long-term indicators, fully support continuation of the trend. This could easily go to a dollar. The market is in highly overbought territory. Beware of a trend reversal. Be careful. It is up 700%. It could come back down, but look at this. It's up 740% since July 23rd, 1300% since May, and 1580% since October of 2017. So what is the news that has driven this explosion and made Sokoman the number one stock in the world for you to own right now? Let's read it. Sokoman essays confirm high-grade gold intersections at Moosehead Project Newfoundland. That's right. High-grade gold intersections at Moosehead Project Newfoundland. Here it is. And this was 10 days ago, exactly 10 days ago. So SIC, Sokoman today announced that it has received essay results from drilling recently completed at the Moosehead Gold Project in Central Newfoundland. The company has completed a total of 1,970.5 meters in 15 holes as proposed in its phase one program. Essay results have been received for the first three holes and the results confirm the company has made a high-grade discovery in an area with little previous drilling. This is huge news. Massive news. Timothy Frode. Interim CEO states, we are pleased with our initial results from the Moosehead Project. The significance of MH-1801 lies not only with the exceptional grades of the gold, bearing quartz vein, but that for at least 5 meter up hole and down hole of the vein. Significant essays were also reported. The 17 samples comprising 11.90 meter intercept included 9 samples returning greater than 1.0 gtau. The area surrounding MH-1801 will be prominent in our distribution of drill holes in phase two. So you can go through this release. Do your due diligence. Do your research. Remember, Rich TV Live is strictly for education, entertainment purposes. Always do your due diligence. Always do your research before you invest in anything that we talk about here on Rich TV Live. If you're not winning, you're not watching. We bring you the winners and we bring them to you first. Now this is up a lot. Be careful. It could come back down. But Barchart is saying it has a lot of buying pressure. So I would not be surprised to see this continue to climb. Canada has been dying for a gold company to explode. It's been literally years since we've had this happen and now there's one company that's a white rabbit and it's Sokolman Iron Corp SIC in Canada on the Venture Exchange and you can find them in America under the symbol G D N D F. Thank you for watching. Invest with responsibility. This is your boy Rich bringing you the biggest winner in the world right now. Sokolman Iron Corp. Just another winner. I'll vote.


I just did the full 5k. I thought I was only coming to do one mile because my back surgery is so I'm feeling great. It's for a good cause and just totally awesome. My name is Caitlin Ruele and my husband was Zachary Kish, Army veteran. Zach was in the military for 10 years, 6 months, and he was a 118th MP in the Airborne unit and he was also a K-9 Handler and he did total 4 tours, 2 in Iraq and 2 in Afghanistan. Zach's service meant everything to him. He was very proud to defend his country and he would do anything to help anybody. It changed his life and forever in both good and bad. He was injured overseas. He had a limp and constant back pain but not just his injuries. He also had really bad PTSD to where it just affected a lot in his everyday living. DAV, to me it means a lot because they are out there to support disabled veterans. It really did change Zach's life because it helped him to realize that there are other people out there going through what he's going through and that he wasn't alone. In time, little by little, certain things did help Zach in different ways. It just felt great being around everybody and knowing that we're all here for the same cause and just support our veterans. It's awesome. It's a good feeling. Being with Zach, even though I always support our veterans and service members, he just opened my mind up to a whole new world and a better understanding of what that means. I'm just so happy to be here and I didn't think I was going to do the full 5K so to be able to finish it and do the whole race with everybody, it feels great. I guess I just feel it's important for veterans to know that there are resources out there and that there are people who do care and do want to help and that even though we don't know them all, we owe them all.


it's DDK and I'm back back it's DDK and I'm back again to show you how to win and get these dividends if you are not subscribed go ahead and subscribe and also do not forget to give me a thumbs up and if you're a part of the crew you already know to do baby I ain't even gotta tell you no more you already know what to do if you're a part of the crew we are first starting off with our first load we are going to drive 38 deadhead miles 36 miles loaded so 74 miles all together for 150 it's time for us to get a grip G let's go just like that we are here at the pickup we're trying to get bucks if you're hating so what my guy Russ how you doing boss I got three pallets going to uh sturdermen no pleasant prayer pleasant prayer I said sturdermen I'm sure all right appreciate it these three right here okay all right appreciate you boss let me turn the back my guy Russ about to get us together so we can run off this cheddar if you hate you need to do better baby you need to do if you hate you need to do better hold on one second one second ain't more than that so what you good stop there palette number two get this money is what we're about to do palette number three after this it's time to get busy so we can get this cheese a few moments later this one it ain't gonna fit I only can fit three it's a real small one oh it's a small one so if we we maybe can fit it right here yeah if I screw that up it'll it'll okay so I'm gonna have to unstrap these joints how do you know how much it weigh not it should be on that paperwork they just didn't tell me okay so you should be the three and oh it's a one yes one at it okay let's get I'm gonna bring it over here to see hopefully hopefully the field we'll see okay all right appreciate it they added another skid on those guys so we reached out to the dispatch to see what's going on he didn't even know about it either so I don't know what's going on I have a question for you is this okay to sit on the other on top of the other one or no it ain't gonna be good oh okay so yeah I'm gonna have to yeah we have to reach up I'm gonna have to unstrap these on uh from this lecture we said there was three skids too originally it was and there was oh and so you ain't know I could have just drove off right right it would have been a whole another thing you keep on going right there you good leave it right there appreciate you boss y'all see what's going on baby we strapped up baby I always tell you guys keep them strapped we had these extra straps we got like probably 10 or 12 straps all together tell us what's one of these shadows two right here one right there one right there two up there guess what it's tough for us to get to this money like it ain't funny let's go when y'all to work today Mike they point you all the words Mike getting us right so we get our pockets tight one down three to go let me grab this pallet puller right here I don't know if you're gonna be able to get the second one out without this I don't know yeah we're gonna see it might be getting busy so I got this pallet puller for us okay profession no profession no no profession no no Mike ain't playing no games right there yes sir teamwork makes the dream work Mike teamwork makes let me get that paperwork I wouldn't say that so I have my days Mike some days is good some days is terrible it comes with the territory of life huh great yesterday one thing good it wouldn't be like two something but no I have some good days I have some $500 days so it's just and then some days I have $0 days so you find out so I mean it comes with the territory it comes with being an independent contractor doing your own stuff right like working at a job is consistent the same thing every day same thing every day but it gets boring I'm sure you bored of it aren't you I know you retire soon so Mike you did your fair share the 18th I'm getting surgery on my wrist so I won't be back till the second next year January 2nd yeah so I'm getting this done first then I get my knee replaced I see my knee doctor on the 4th of January I'm gonna get that scheduled as fast as I can so that'll be another two three months out of work really yeah so do you come back like April and then when you retire end of the year oh you a Mike Mike you're almost there you're almost there you're almost you have a good one Mike the next day it is now the next day and yesterday that's all I got baby I only got 150 for that one order we try to go out there and get an order and just so you guys know I'm going to give you an update that this bachelor just said it's okay so we did not get no extra pay for that extra pattern that little small pattern they had to put on because they actually added that in the morning as you heard my guy Russ say now we do have an air hockey table to pick up this is a repeat customer that we had before and I actually invited my guy Mike who is Mike Mike is my guy man that's who he is Mike is my guy my first ever ghost share order was with Mike then not only that I'm gonna tell you guys this when you out there and somebody do your favor make sure you return a favor don't always be wanting to take take take take take but you don't want to give anything Paul you don't want to give anything to anybody so my guy Mike he actually took me on my first ever side job as well we had a side job we're gonna pick up a mattress in a box spring or something like that and well I think it was a queen size bed we're gonna pick up that and then we deliver it he split the profits with me so I got to return the favor and shout out to all the haters now we're picking up an air hockey table we're only going to drive 0.9 miles we're picking up from a basement we're gonna drive 0.9 miles take it to another basement and we will receive a payment of 150 RRP Nipsey let's go just like that we are here at the pick up location baby we came here once before so we get a skull good to hear from you man I was like oh I drew I remember yeah Mike you know you took me on my first side job so I had to return the favor I remember all right how are we doing that um I'm gonna put my end on top right here so we can do the fat work here nice okay thank you so I gotta give you the next address I'll send you a text message with it okay cool I'm gonna strap this down and then we're gonna hit the roll I can see your message now it's like a treadmill oh yeah I have my first year at all would you like me to plug it in now just so it's plugged up you'll have to worry about it guess what we just got an order on D L I V R DB by the puller right now so if we can get this cheese delivered app we just got an order on the delivered app if you want to sign up for deliver make sure you click the link in the description and use Jerome Adams as a referral code so I can go out there and get my pockets on swole and you are you are too baby you're gonna get your pockets on swole as well hey if you hate I don't like the smell I like the smell on haters baby but we have an order we're gonna pick up from tacos El Norte we're gonna drive 6.4 miles we're picking up 68 items the order cost is four hundred and forty six dollars and we will receive a payment of a hot 40 shorty let's go oh really y'all lost the keys um I have an easy catering order I thought y'all was closed I'm like yeah I'm thinking I'll sound like they wasn't going at all easy catering order here's the order number right here this is the hot food you said okay all right bag number one drop it right there bag number two bag number three then we got bag number four up front try me I'm a truck these one of these these uh bungees baby so we get this money baby flap to the bank like it's funny baby just like that we gone it's time for us to get it on let's go just like that we are here at the drop-off tunnel I think socks off I am good to go thank you guys very much you guys have a good one and just like that it is ended a video I hope you guys enjoyed the content yesterday and today was it was a little suspect baby 150 and 140 shorty so it didn't go to greatest baby but it is what it is we ain't complaining we maintain it also before we go I'm glad you stayed to the end of the video because guess what I did make a community post on van talk for van talk episode one van talk episode one is job is tomorrow if you my friend have any questions y'all only got 24 hours make sure you guys put it down below in the community post go to the community post and type your question in so I can tell you what you got to do so you can go up and get some more dividends and win I hope you guys enjoyed the video make sure you log in tomorrow it's going back down we ain't playing around 233 it's still big bags easy we'll keep on giving a reason I see you guys on next one we're going we're going we're fooling you already know this DDK and I'm on my way


Good afternoon, Cloud Community, and welcome back to Fabulous Chicago. We're here at KubeCon, CloudNativeCon. My name is Savannah Peterson, joined by our fabulous new analyst, Dustin. How are you doing today? Having fun, let's do this. Day two, you feeling smart? Absolutely. All right. Smart, I don't know. I'm just checking if we're listening. Now, at this point, very, very, very excited about our guest, a company that you and I are both fans of, GitLab. I'm sure you've all heard of them. We've got David from GitLab. David, hello, welcome. Thank you for having me. How are you doing? Doing good. Good vibe here going on. Yeah, we were just talking before the cameras turned on about the ascent of momentum. It really does feel like a different energy, not just because the show floor is a bit more packed than, say, Detroit last year. But I feel like a lot of projects and collaborations are starting to reach a point of maturity where we're seeing things accelerate. Yeah. What have been some of your observations? Well, everything seems to be about AI in Detroit. Yeah, it's all about security. It felt like everyone was talking about security. And now everyone's talking about AI. I think the other thing too is I've heard a lot about needing more visibility into what's happening. And I feel like that was one of the original themes of KubeCon was operations and observability, right? And so seeing that kind of creep back up to say, yeah, yeah, I'm doing all the cloud native things now, but where's my stuff? And is it up? Is it working? What's going on with it? And so I've seen that be a nice little thread going through a lot of the stuff I've been hearing. And the focus on AI has to play well into your pants, right? It does, yeah. So GitLab in June released what we call GitLab Duo. It is our AI suite of power, DevSecOps AI powered workflows. And it focuses on everything from helping you in planning all the way through coding, securing and deploying. Because GitLab is in a DevSecOps platform and covers the entire DevSecOps life cycle, and I know you both know that, being fans. No, I love it, no, but I mean, it's always great to give the audience context because you are, and it's a broad spectrum and you're touching a lot of different industries within that. We are, and we feel like to make organizations successfully, you got to apply AI for everyone. And so that's where GitLab Duo is really taken hold is people using it for everything. Were you anticipating this moment of AI adoption and this hype curve coming? Because your announcement sounds like it was pretty well timed. Yeah, so yes and no, I would say on the yes, we started adding AI- I think I'm an honest answer. Yeah, I'll kind of give you the framing for it, right? So like, yes and that, we started adding AI to GitLab in 2021. We asked our customers, what's your biggest pain point? It was getting through code review. And so we applied AI to code review. The thing that I was not as surprised for, and I think just the industry as a whole, if you were to ask everyone 18 months ago what GPT-4, Palm 2, Cloud 2 could do, I'm not sure everyone would jump to the amount of things that AI can now already do. So that's where it's a little caught off guard on that part of it. But no, I've always thought that AI would help in depths like ops. It would help in operations. And so I'm not surprised by those things. It's just the, I mean, I'll put it to you this way. My parents thought BARD when I showed them BARD was like a sentient little like, I don't know, person living inside of a computer responding and not software, right? I showed them BARD before chat GPT. I did.  Wow, that's one way to get out of a speech writing situation too. My sister was in tears laughing. She loved it. I think that's great and very clever. I also love that your family humanized a sentient being. Did this person, did BARD have characteristics? Was there like, oh, there's like, where is this person that's doing this? I'm like, it's software. My parents are, are much older, right? So I, but I don't think that their age is actually even super relevant in this case because I feel like a lot of people are wondering what that is. Or is there just- That's true. Yes. We'll be fair to my parents. Yeah. I'll throw your parents a bone. Yeah. They clearly created a lovely son. So we'll give them- Well, thank you. Yeah. So I'm going to bring us back to DevSecOps. Yes. Please do. If anything we're talking about is on stage, I don't know. All right, all right. DevSecOps and AI. Give us like that cross-section, you know, for where you guys are with that journey. Yeah, great. So we did start with code review with AI. Code review, very important part of DevSecOps. But the next year we actually looked at with security. What we did at GitLab, and I joined GitLab in 2019 to add security compliance to DevOps. We realized we shift security left. We made it more developer friendly. But if you ask yourself, and I've asked myself this, like, does a developer wake up in the morning and say, I want to write a vulnerability to the application today? They don't go like, yes, zero day today. I mean, let's hope not. Let's hope not. Well, we'll assume positive intent. So we then said, well, how do you make security even more approachable? And so we started on what we call explain this vulnerability. So what it does is, when a vulnerability is found by our security scanners, they have the option to ask Duo to explain it to them in natural language, give them an example of it being exploited in the programming language they're using, and then how to resolve it in that programming language. And so when you talk about DevSecOps and AI, we see it as empowering everyone who's involved to be more efficient. You hear a lot about AI and DevSecOps and it being around code creation. And that's important. GitLab does that. But if you make your developers a hundred times more effective, that's only one little sliver of the SDLC. Everyone else is going to be impacted. I think developers more effective. Obviously, obviously, obviously core to the GitLab value proposition. I assume you're able to do some measurement. Now that this Duo has explained to developer A, what this vulnerability is, how it was introduced, you're able to educate that developer A. Surely you're able to see that person's contributions going forward and I don't know, measure some new efficiency and new knowledge gained. Yeah, so the one value of GitLab being a platform is that we actually have all the data sitting in GitLab. And so if you're fully adopted to GitLab, we can actually do value stream analytics, so measuring how you're doing it, delivering software. And in that, when you're- Talk about being able to test a hypothesis. Right. You're thinking about this, that's so cool. And so that's how we're able to pull efficiency metrics.  You can see developer merge rate going up. And then you can be able to say like, hey, I've applied AI here successfully. I was talking to a customer last week who said they're seeing between a 50 and 90% boost in efficiency for their engineering or- That's significant. It is. But that's because it's not just improving the developer experience, it's supporting the security teams, the operations teams around them. It's that holistic support. Exactly. Which is going to make a big difference. And according to your own DevSecOps report, 25% of time is spent developing code and that's it. So when we're thinking about that as an only, as a single stream optimization, you're not looking at the activities or the manpower of the entire organization. Yeah, correct. That's why I was kind of saying that if you accelerate just the developer, that's 25%. And honestly, I feel very strongly that if you did just do that, and let's say you made your developers a hundred times more effective, you're going to break everything else around them, right? CIC pipelines are going to work, there's not going to be enough planning stuff ready for them, infrastructure's going to fall over, right? It's just, there's so many things that you have to boost everyone. Marketer's not going to know what's going on. You know, it's like, it's not even just on the tech team in that circumstance. I think that's interesting. GitLab's been on a journey, you're 12 years old. You IPOed two years ago, I remember it was in October, we were actually at KubeCon in LA, totally different vibe than this, but just absolutely explosive growth since that moment, the momentum. Do you think that the AI, I don't like calling it a revolution, I think we're just in the evolution of it. I'm going to call it the AI evolution. I like it, we'll go with that. Thank you. Your approval is all I need when I'm naming terms. You can now ship it. Yeah, we're shipping, it's straight to prod. So let's just make a lot of jokes in the middle of this. Do you think that your growth is going to also explode with this to support that movement? Yeah, so I mean, GitLab continues to grow at an alarming rate or enormous rate, right? A very good rate. It's so alarming, it's wonderful. It's great, yeah, alarming's not the right word. Inspiring rate. And what I've looked at it from is the, thank you, because it's not alarming, it's great, it's explosive. But the thing that I take from that in AI is a parallel to it, is that people are craving efficient delivery of software. And so GitLab's growth is based off of that. And now if you tag AI with that, it's just going to continue to make that success rate go faster. We said a hypothesis for AI when we were embedding it into GitLab. We said three core tenants of how we're going to play AI. One of those was that we wanted to boost everyone in the organization and cause organizations to be 10 times more effective at delivering secure software. And so with that. Casual order of magnitude, yeah. I think I said big goals for the product team. I love that. I'd be disappointed if I wasn't. So, and we've already seen that with GitLab. Our customers, we did a survey through Forster about 18 months ago of GitLab ultimate customers, people using the full platform. And out of that survey came a 7X efficiency from where they were prior to GitLab. And then they got an ROI in less than six months, right? So if you look at that, now you play AI. I want that to go faster. I want you to see that in three months. I want to see that 10X in that window as well. How are you approaching, so this is awesome scale, everyone's using it, love that. I mean 7X alone just from starting to use GitLab. Talk about a tooling boost, that's awesome. Let's talk about the sexiest topic, compliance. How are you factoring that in? So, as I mentioned, I joined GitLab to add securing compliance in the product. Secure is a passion of mine. And started my career as a researcher, went into engineering, then joined the dark side, went into product. But I realized early on that unless you give people the controls to truly understand how they're using GitLab and how security is impacting them, they can't truly ship secure software. And so about two years ago, we launched a new module, GitLab called govern. So, GitLab's based off the DevSecOps stages, create, verify, plan, so forth. We've had our own in secure and govern. And govern's whole principle was, let's give you compliance controls that can be a herit across all of GitLab. Let's give you the visibility to understand where compliance violations are happening and ability to stream audit events to understand what's happening. And so, if you're using GitLab, you see all of that within GitLab and you can stream it out to your compliance software if there's a place you need to store for compliance reasons. A customer, Chorus AI, shared, they got through their SOC2 audit in less than a day because of GitLab. What? Every time the, yeah, every time the analysts- That's unheard of. Every time the compliance person asked- That's awesome. External contractors like, where is, how can you show them? They go, let's try here in GitLab. And so, if you think about that, you have to marry compliance with security and with DevOps, if you don't, you don't really have the full controls and the visibility you need. Yeah, are you seeing that as being a driving factor of some of the buying decisions? GitLab as a commercial product, as a commercial company, we're all here around open source, but I think I've seen, maybe you can validate our counter examples, but, you know, does that drive business? It actually, it absolutely does. So, when people would come to GitLab when I started, it was all about source code management. And then it kind of churned into, we're coming to GitLab for source code management and CI CD. And a lot of customers day one are now starting with security. And it's not that their security tools they have aren't efficient. You know, those people are also our partners, you can integrate them into GitLab, but it's about that visibility and the controls. And so they can make their existing security tools that they maybe don't want to give up yet, even more powerful for them through GitLab's compliance and governance. But then over time, they begin to adopt the GitLab security scanners because they're truly built to shift security left. Our SaaS scanner as an example, so doing SaaS analysis can finish sometimes scanning before the UI tells you it ran. You just see it says it completed. That's because we can scan that Delta code change. And so it's really efficient to be able to use GitLab for that. So you're saying you see some advantages to starting left as opposed to shifting left. Like if you start with a certain security posture, you end up in a better place much faster. Yeah, imagine like if you're making that decision to change how your developers deliver software, how your security teams operations team work, it's easier to do that at once than it is to do it over multiple, like it's like that death by a thousand paper cuts type of thing, right? Yeah. And so if you're going to say, hey, we're moving to GitLab for source code management and CI CD, and we're going to put security governance in from the beginning, you're going to see that boost in your security, your governance and that visibility. And then you feel better as an organization because you have that view into what you didn't have before. And that confidence as you continue to build on top of that. Yeah, absolutely. I love meeting with our customers. You mentioned we started as open source. We did. We're still source available and we have an open source version you can run a community edition. But what I love about our customers is their partners for us. And a lot of companies say that. I can tell you, I feel that they contribute software into GitLab. Some of our ultimate customers build out new ultimate features for their competitors, their partners. The synergy and the win-win there is a little bit. Some of my favorite features have come from open source and some of them have been security improvements. In 2020, I think it was mid-2020, fall of 2020, HEB, large grocery chain in North America here contributed mobile applications to security scanning to ultimate. And so that's the community that GitLab has become. HEB. HEB. My wife shops at HEB twice. Oh yeah, we lived in Austin, we shopped there all the time. That's great. We're talking about groceries, we're talking about sentient beings. Hey, we can talk about everything. We are really covering the spectrum here and I really like it. Just as a side note, because you meant sentient beings. I encourage everyone to be polite to chatbots. Yes. I've seen Terminator and where Skynet goes. Let's be kind to them today. I agree. I mean, spread kindness in general. Yes. And say the nice things out loud. Y'all, it's been a weird year for the chatbots for everyone. It's been a very, very interesting year. Let's just keep the positive vibes rolling. But I'm sorry you're going. Yeah, no. I actually, I really agree with you though there. I love that you brought that up because I think that it is important that we are kind in our approach to this new technology and not just obviously talking to the chatbot, but also when we're thinking about our bias and when we're training these models. Absolutely. And one of the things that I want to call out because I think GitLab does this very well as a company that was all remote day one. You've got 2,200 employees. You mentioned over 65 different countries. Correct. And I think it's a fairly diverse workforce. Is that a part of your strategy slash a benefit for the way that GitLab's approaching AI to fundamentally have that diversity represented already? It is. So one of the things that take a lot of pride in a GitLab is the culture where exactly we look like from the outside and the inside. And that drives our decisions around things like AI where we're hiring what we're doing. One of those values is assumed positive intent. And when you start doing something around AI, there can be a lot of bias. If you're training a large language model on the internet, clearly it's not necessarily a friendly place, right? And so we've been very purposeful. One of the things we decided to do was say that we would pick the right AI model for the right use case. And what that means is that we're using 16 different models depending on the future. Wow. Because that feature is using a model that we select as purposefully for that. That's allowed us to remove bias in a lot of the responses that GitLab Duo can provide. It's allowed us to reduce confabulation, hallucination depending which term you want to use for it in the AI world. And so an example, explain this vulnerability, that second feature relaunched. It's using an AI model that only understands security vulnerabilities. If you ask it about what's the best banana loaf bread recipe, like it does, it's going to tell you it doesn't know what that is, right? And if you're doing that, you can begin to make the models be a little bit more purposeful but a little bit smaller. And then they're trained on only the exact data.  Right. It helps avoid that. And by all means, we hold our partners accountable on making sure they're also helping us with that. I like that. I actually love that you called out those 16 things. It's like you got your box of crayons and depending on the situation, you're picking the right crayon. It makes a really big difference across the board. Wow, this was absolutely fascinating. David, thank you so much for joining us. This was a joy. Yeah, I loved it. And by the way, like I said it right before, earrings are amazing. Thank you. I'm a pretty recorded fall attorney. And I'm joking to meet both of you. Like I said, I was a fan, read some of the stuff, seen interviews, so very much thank you for having me. Hey, our pleasure. We look forward to having you back hopefully in Paris and then again, wherever keep going. There you go. NA is next year. Thanks a lot, Dustin. Thanks so much for your insights, for joining me and for keeping us on topic. This case, let me get a little excited. Indeed, well, you know. Yeah, yeah. I do my part. Except unless we're talking about HEB. We'll see you about it. And thank you all for tuning in live to our coverage here at KipCon, CloudDataCon in Chicago, Illinois. My name is Savannah Peterson and you're watching theCUBE, the leading source for emerging tech news.


We're coming, we do not expect this interest. We are simply facilitators and we will not be speaking very much, but it's all about you guys and collaborating. We are trying to solve a coordination problem by having this workshop. Okay, cool. Should we get started? Yeah. Okay. So as Eva said, we're just going to talk for a brief second to give you an intro to why we put on this workshop, why we're giving you guys this space to talk a little bit on our thoughts, and then how this session is going to go. So if you don't know where you are, this is Workshop on DOWs. It's titled Beyond DOWs, a evolving human organization. So we're going to be talking all things DOWs and everything, wonderful and horrible about this. So as I said, we're just going to run really quickly, maybe 10 to 15 minutes. The format of the session is a workshop, so we're going to have you guys working with each other. It's something that you can come in and out of, but it would be great for you guys to stay the whole session. It's an hour and a half, so it's not too long. We promise that it will probably be okay. Okay, so let's just start off with why we're holding this session. So even I think that DOWs can be more than multisyncs, and that's probably, I mean, I hope not a hot take, but DOWs are representing this really cool thing that we're all talking about. I mean, that's why we're all in the room here today, because this is something that is really interesting, but also really big. So what inspired this workshop? So I guess I wanted to go through why we think DOWs can be more than multisyncs, and from our observation in the space, what we really think is happening, and pitch that to you guys, see what you think, and then we can have a conversation about it. So we believe that the hegemonic approach to human coordination is being challenged as though it's underserved and disempowered by the current system, search for more open, adaptable, and representative solutions. So with the emergence of DOWs, those weird things that we're all building, de-sensualized governance and token engineering, we now have this new design space to re-engineer incentives and mechanisms, and that's really cool.   It kind of means all of these different things that don't really line up, and so it causes a lot of confusion, it causes a lot of inability to work with each other, and it causes this whole space to be completely not accessible to anybody who can actually use this technology to solve their problems, these people who are being disempowered and underserved by our traditional power structures. So this is just a little bit of the DOWs that are in the space. We have everything from grant DOWs to people solving climate change with DOWs to people helping political candidates, meaning themselves to the office, and so there's a lot of different things happening, and it's kind of a lot to do. But one resounding thing that is kind of connecting all of these is that they're kind of envisioning this new way of organization, right? One that wants sustainability, over-profit, regeneration, instead of scarcity, and more cooperative, distributed ways of organizing and working over hierarchical, did I say that right? And centralized ways of working.  This is something that, hey, I'm like serious, I like this stuff. This is what a lot of people have been working towards for a very long time. So this isn't new to just the people in this room. This is very new to us, but it's not new to everybody outside this room. That's what it was meant to say. So this is a really cool vision, right? This is a very counter hegemonic approach to organization that could serve and empower the people who are being disempowered and underserved right now. So Eve and I wanted to get this space to start talking how we can involve beyond DOWs, beyond this weird little thing that we all really like talking about. And how do we start getting towards that vision of sustainable, regenerative, and cooperative organizations, right? And so we believe that there's three things that we need to make that happen. One is collaboration. This is something that cannot be done alone. That's quite obvious. The second is accessibility. So this cannot just be accessible to the people who can come out to Osaka and Japan for a DEF CON. This should be something that anybody can access and build with. And also common ground. We kind of have to get on the same page about what we're building. And what's really cool is that most of the workshops on DOWs at DEF CON have been around the same concept of how are we getting working within the same language, within the same frameworks. And that's super, super important for our evolutionary process. So yeah, that's the basis for this workshop. Eve is going to take it and tell you how we're trying to provide this space to start approaching that counter hegemonic vision. And we can go from there. Thank you, Abby. So one of the biggest criticisms I have with this area is that we talk about these passwords like DOW without thinking about why. It might just boost our cloud or ICO, but we haven't really thought about how to apply it into like Abby said, outside of this room, and to web too. So people who don't know the word DOW and the people who will never care about the word DOW. And so the best way we thought to do this was to collaborate and have people share their learnings. We have several DOWs represented here or people working on them. And aside from Twitter, there's not a lot of collaboration. And so this in itself, we're trying to solve a coordination problem by allowing for that collaboration and talking more about how do we make it more accessible and what should we be thinking about in terms of common ground as a tool set. So, you know, DOW itself is not a thing, but you know, things like co-ops and savings groups have existed for a while. And so how did DOWs play into a larger ecosystem of organization types outside of just this Ethereum buzzword. And so we have a few prompts here. And I'll go through them exactly what we think. You guys should be talking about. Our goal would be if you guys could separate into six groups. And so we have on the walls each of these prompts. And if there are people who don't wanna work on the prompts, that's fine. We also recognize this room is massive right now. And so if it makes more sense to do it all together, we can do that, although that might be harder and we probably won't get through all of them. But I can start going through them. So here's a prompt that's our own for quite board. So firstly, why DOWs? Why are we here in the first place? Why do we think these are different organization types than, like I mentioned, co-ops or savings groups or credit unions? And if they're not different, then how can we start collaborating more with the history that has existed with experimentation globally and different kinds of developing and developations? To DOW or not to DOW? So a lot of people like to now include the word DOW and everything. I would say that's not always the best use case. And so we wanna pin down, when is it not right to use a DOW? And really think about why are we saying the word DOW is a simply for a cloud or does it actually provide a tool set for us that can improve the way that we organize? DOW Toolkit, so aside from the technical infrastructure, what other components are necessary for us to achieve it? So companies like OpenLar doing a lot of innovation around the legal structure. What other business structures should we have? Are we using the same social tools like Discord, et cetera? And if so, that's awesome. But maybe we should be more pinpointed on how we actually need those. You know, there's like a lot of controversy on leadership or project management within a DOW and you still need those web two tools to achieve the organization that we want within a DOW. So governing DOWs, how are they different from the existing structures? Do we need identity solutions? What other components do we need to make them successful? Outside of the civil attack problem, what other problems exist within DOWs and how can we solve them? Experimentation, so as I mentioned, there's a lot of people here who are either making DOWs or a part of DOWs and it would be great for everyone to share their learnings. And so something we learned in mall life is like a lot of people are participating in a lot of different DOWs but without a fundamental, like, there's some shelling point to communicate that. We actually aren't sharing a lot of information. DOW flavors, so I guess piggybacking a little on the taxonomy DOW workshop earlier today. What are the components of different kinds of DOWs? What are the different kinds of DOWs? What are the features that DOWs should have to be successful? And maybe there's people here who are part of that workshop that would be great to have you guys participate in that. But defining more so the lines between different DOW types might make it easier for us to identify what is the DOW outside of this vague term.  And so we've actually built out those prompts with a lot more, like, guiding questions that can be used to lead the groups. And you'll be able to find those on the HackMD page and the Excel sheet. But so we don't just want you guys to just jump in and, like, have discussions. We want this to be something that is actionable and so we can pull out these insights and actually apply them back to the community. So what do we want from you, right? So first, we want you guys to capture and share the key insights from your discussion groups through collaborative note sharing. And then actually share, work together, obviously, and play nicely and engage with each other. And then we want you guys to present those insights to each other. So we want this to be a quick breakout session where people dive into each of these prompts and then come back together and share these insights. So that means that we're gonna have to have one group leader for each group and one person who's taking notes. And those are the two people, so I can't wait to see all those hands volunteer for the groups. That's gonna be really great. And then I guess the guiding framework for what we want out of this session, because it's so hard to dive into all of these big topics and have structured conversation, is more of a proposal for frameworks, deliverables, and continued work that can come out of this workshop that can be worked on with each other, with different groups, and then, again, push back to the community so we can be evolving together. This work only begins here. This is not something that we believe will stop when it exits this room. Our role is just to create space for people to come together and have these discussions. And also, we just want you guys to take inspiration and use this as a launch base for more collaborative discussions around dows. As Eva said, we have tons of people who are representing the different dow groups, dow guilders, dows in general, here in this room. So take this time to kind of break down those project silos and have conversations that in real life, not just over Twitter, which is really important. So, to talk about logistics, and then I'll take a couple questions just to make sure that we're all on the same page. We're actually gonna be doing our note sharing. If anybody didn't know, we have this hack and dee for DevCon. This is a QR code to get it, or you can just find it through the DevCon app. And we've actually set up the document with all of the different group categories. This is the link, when we didn't think that we would have slides. And so, this is where we're gonna be taking our notes and sharing insights, and this will be accessible by everybody. And again, whoever is volunteering to take notes, do this in the hack and dee, that would be great. So, about the group. Okay, so to go back to the original question, we have a really big group of people here. So, I wanna do a quick check on if people would rather be small working groups where you split into corners, or a larger group discussion that Eve and I facilitate and work through each of the problems. So, who wants working groups? Raise your hands. Hi. Hi. Yeah, really hi. Okay. Okay, now who wants a larger group discussion? Guys, it's about half. The other group. One. What? One. One. One. One. One. One. One. One. One. One. One. Okay. Yeah. Guys, I think we're gonna go with groups, okay? Also, also, also I mean, if a group forms and wants to go somewhere else, if you tell them what time we come back, I mean, there's more space than this room for working groups. Thank you. Nice. Can I just mention that, yeah, just as he said, you don't have to work physically here because this is all on hack and dee. We'll see all of it, and our goal is to publish all of this as a collaborative effort on some medium of choice with all of your notes, and also the frameworks or deliverables that you guys create on how to make these easier. Take the question. Can you show your floor again? I don't understand what you guys are talking about. No. No. So basically, Dao itself, a decentralized organization, is not new. We think it's new because we have this new fun thing called a smart contract that allows decentralized coordination. We want to better understand what are the differences and similarities between things like co-ops, savings groups, credit unions, et cetera, that are very parallel to Grant Dao's or Aragon Dao's, et cetera, and what are the tools that we need now to make those easier given that we have this new technology stack that we're using? All of these prompts are on this Excel sheet that you can also access through the HackMD document. So if you want more information on the prompts, you can find them here. So I think that we're going to do. There's stickers on the wall for the groups by your prompt. But if you don't want to be in this room as it is quite packed, as our moderator said, you can leave and then come back. I think coming back at 4.30 would make sense. We want it half an hour at the end for discussion and presentation. So let's everybody take the time now, coordinate the amazing distributed people that you are, and find yourselves into one of these six prompts. If you have another prompt and you have a group around you and you want to talk about something else, go ahead. Now is the time. As I mentioned, all the information is on the HackMD. All right, guys, let's wrap it in 10 Ds. So if you're in a group, can you add your name? Click the lab in Ds so we know who's going to be in the group. Good, good, good. It's like a heat cancellation. Come on, everybody. This is our virtual radio. This is a campus. This is our virtual radio. I don't think we have the most people at the moment. I'm confused. We have more, more, more people. I think we have more. We have more people. And if everybody could just take a second to find out. Okay, group in the back. You still got some stragglers in the back. Is everybody listening to my beautiful voice? I hope so. Hey. Okay, cool. Hi guys. Guys, that was from what I heard from those discussions.  So I'm really excited to hear from all of you guys. The game plan now is I want each group to nominate one person to come up and share the general key highlights, the proposals moving forward, whatever they think is relevant that they want to share with the other groups, nominate one person, and that person is going to have around five minutes for however long that they want. Yeah. That's the rule. Hey guys, come sit down. I'm going to repeat those two options. If you took notes outside of HACMD, make sure to put them into HACMD before you leave, because we know some people were taking this for notes. All right, I think we have everybody in the room now. So I'm going to repeat those instructions one more time. So one lovely person from each group is going to come up and spend however long, maybe max five minutes, sharing the insights, thoughts, general discussion points that they think is really important for every other group to hear. So I want every group to nominate one person. That person is going to come up here with a microphone and have the full attention of the room. So we're going to do that for each group. I think we ended up only having five groups. So again, this will be probably 20, 25 minutes. We'd love for everybody to stay to hear all the insights. And then that's it, okay? Great, any questions? No, okay. So who wants to start first or should we start one through six? Inverse six. Inverse. Six, do you want to go first? No, ma'am. All right, who's coming up? Announce yourself. Hi, I'm Josh. He's coming.  What do you see that way? Which James was? I'll show you. Okay, well, I thought I was going to hear about that. Are you part of James now? So, what's the fact? As was about the flavors of dows, we basically just tried to go through and think of all the characteristics that could be on off switchers or could be scales or sort of about velocities. And so these different points that make up the flavors of the doubt. The first one was the permissionlessness of it, right? Is it purposely really open and permissioned? Or is it, you know, for managing funds for close medical people and the permissionlessness of it? The second one is a for profit slash for sustainability slash not a goal and just doing grants, right? And so where is it given now sets on that parameter? The next one was around the number of members. So how many people, you know, again, purposely as small as a large, is it meant to scale to a million people or is it only meant to be five? The next one that was pretty key was the fund allocation. So is it, you know, is the point of it just to deploy capital in different ways? Or is it how to govern, you know, what color to paint my mom's house? The next one was, is the token or not token, right? So that was something I kind of ended right down. But, you know, does it have a token inside of it? Is that the point to it or is there not at all when it doesn't require it? The other thing, oh, is it focused on sort of like people and open access and creating a middle world almost? Or does it have sort of like hard coded in it? What are the, what are the point of it is, right? So it should never change, you can just say like this or it should develop over time, you know, that sort of immutability of the doubt is another one of the flavors. And then one of the things we talked through was going through Doustet, Colony, Paragon, Panvala, nice. And then sort of the Mollack Forks and what all those flavors. I don't want to do it for analysis, I can sort of do it. Those are clear on the hack of the day. So yeah, the cores for those sort of six different pieces of the puzzle. And then also the different companies and sort of how this all works. Thanks. Anybody want to ask anything for this group? Or add? Nope. Yeah, what did you plan on for the next steps? What's that? Did you plan on anything for the next steps? Oh, geez, now you've got a spot. I think next steps for the different flavors of the doubt. I mean, I think we're going to get them up on hack of day, maybe sort of expanding out these flavors. I think, I mean, no one wants to ask a question now, but I'm pretty sure there's other flavors and other attributes that make up a doubt. So contributing to them, I think would be really useful in sort of building out this lesson and then also putting back the community, right? Because I think there's a lot of community members that aren't in this room that actually care a lot about Doustet and sort of understanding how at least the people that are in the room are thinking about these ideas and thinking about the different flavors and attributes that make up a doubt is really important. So it would encourage you to go to the hack of day as well and contribute to the discussion and build out these flavors. Nice, we had one question. Okay. That's not a question, but a comment.  Like for example, presence or like anything else that is important for the community. So for example, then have as much say about things related to as think as many times you have in this conference is related to that thing. Maybe that's not the best measure but you can come up with better measures. So that doesn't have to be like a value token but it doesn't have to be anything. Which one would you like to proceed? Yeah, yeah. Cool. Thanks. I agree. That's a good ending. Nice, we've got another question. Experimentation, who's coming up? Announce yourself. Experimentation. Thank you. Hi, I'm Dan Finlay. Speaking for the Experimentation team, we spoke on, there were like four themes, major topics. There was what have you learned from past experiments or a variety of past doubt creators in the group. We talked about what we should be cautious of with future endeavors and then also what do we want to do with future endeavors. And then I've got like a little assorted category. So for past experiments that were in our group, we had a great threat of a kid coin with a recent CLR model and, you know, so it's based on the quadratic application that was italics legal. Rattlesnake and it may have some questions, open questions about identity verification and things like that. But the last round was very successful. In particular, 2,200 contributions were made and they noted that it seemed that a UX improvement that helped people visualize how their vote was really affecting it. It gave this like kind of social media a windfall of enthusiasm and participation, which was really cool to hear about. There was some conversation about this thing called lived out that I had heard about.  And so there was this kind of sentiment like sometimes it's how you encode things to don't reflect the community sentiment. There did seem to be a group sentiment that if the group had agreed to slash reputation, this wouldn't seem so bad, but the fact that somebody just didn't vote for a week felt inhumane. There was, then there was a, there's some other doubt alluded to that had some like private HR-ish issue that was now a public vote and everybody sees that somebody's going to get fired. And so there's a question of like, how many of these kinds of more human things should be on the chain in general? There's a little bit of conversation with the DAPPS experiment from an anti-typical Republican status with a curating DAPPS. It was deliberately designed to avoid voting because voter participation is an issue to kind of come back to later, it's like voter participation part, probably. Then we're talking about what you should be cautious of when building dows. Actually, we have one major thread that kind of dominated here. There was like a question of, it was like politics versus autonomy and it kind of ties back into like just the theme of autonomy. We're just finding doubt like autonomous is a letter in the word and how important is that into it? There was like a testimony from a mohawk dows. I know everybody, I'm the founder, I can pretty, I know how to hustle the votes and get an initiative passed and some people might not want to be a part of the doubt that is like that. And there was kind of a conversation about will dows are going to have stronger, weaker cultures and maybe the trust monetization in these systems comes from transparency, not the lack of trust systems. So those are the experiments. We had another thread about what we should be cautious about. Oh, sorry, that was what we should be cautious about. Politics. Yeah, so can we avoid politics or is that intrinsic too? I think that was an interesting conversation. Yeah, yeah, yeah. But it asks us ourselves that. What can we experiment with besides dows? There was a, so for one thing, a dows aesthetic mechanisms, they can be coupled with norms in a community. Those norms can't be self-fulfilling and create feedback loops, right? If you establish some norms, like you've got a community of votes in the way and slash people, like obviously you're gonna create a self-fulfilling kind of community in that way, one concept.  It sounded a lot like Convali, you should talk to him around. Okay, anyways, there's probably a few dows like that. And then also, what was the last thing? Oh, other thoughts, here's the sorted things. Oh, yeah, the whole autonomy thread, can you avoid politics? More dows should think about profiles for users that are participating and hearing the experiences towards them. I actually wish I asked for more detail on that because I wasn't clear whether it was like building the experience towards the profiles that people were, letting people represent profiles. So you'll get an indication of what you meant. I'm loosely summarizing that, I didn't fully grok it, sorry. And then, there can be problems with information asymmetry and dows when there's people who are curating and stuff, like they might know what are actually good proposals and stuff. There are costs that are non-monetary, the usage kind of comes back to voting costs, so how many decisions were there were there were costs of voting with dows. There was a little taxonomy, kind of similar to what Group One suggested, like some are fund allocation vehicles and some are decision-making or parameter-setting dows. Sometimes legal restrictions can play into dows, so you can either bake that into the incentives and mechanisms that you're considering when designing your dows. Or you can just copy and paste bylaws from existing corporate or government structures and we can basically just have those but with guaranteed trustless enforcement. There's a little bit of a thread, I think we got a little bit of agreement by the end where it was like dows are kind of just us building rules that are more trustlessly enforced. It seems like we got kind of a loose agreement but there were a couple caveats about whether that, there was no a dow cannot have a dictator and no a dow has rules enforced trustlessly and transparently, so those are the two big caveats that isn't just the organization that's on it. Voter participation should be required, should be opt-in, there's an idea, what if your lock screen on your phone required you to vote on stuff before you use it? You know, like, and yeah, security tokens, it was a notion of like maybe you get future revenues for voting, well, questions about how to change the rules and questions of how do you do with early members having dominance of reputation in their dows? So can you, should you decay or is it a good thing to have a reputation, I don't know. Yeah, anyways, yeah, it's kind of cool. That was great. Any questions or additions to add to that? That was a really comprehensive list. I'm really excited to read through those. Lot of really good ideas. The profiles thing is kind of interesting, Dan. I guess a comment or what I take away from that is like, we should definitely have like culture is what brings people together and so profiles are, culture is a component of profiles and so if you have too many heterogeneous people then it's really hard to actually create culture or like in a line goal. That's how I'd interpret that. Great, that's awesome. Yeah, tons of thoughts there. Okay, cool, so let's move on to governing dows. Governance, who wants to come? Nice, hey, announce yourself. Hi, my name is Jason, I'm from Malaysia and this is John Light from Oregon. Oregon Network. Oregon Network. So we have a lot of amazing content, okay, personally that's what I think, okay, in the last 15 minutes. So we talk about governance, okay, reason being is because if the governance model breaks down then everything basically pucks over, so. So the first problem, okay, is should governance be on-chain and off-chain? Not all should be on-chain, okay, really depends on what you're looking at where you draw the line. Incentivization models, for example, okay, should be on a DAO, should be on-chain. The line is drawn based on what the purpose of the DAO is. A good example that was brought up was Molok DAO as a good reference to check out. They are very clear line, ETH 2.0 development. Voting should be on-chain and it should be centered around a shared vision. So the second problem that we went into was how do we support decentralized governance and immediately one of the members said that before anything else, the interface is very important because the current voting itself already sucks, so we need to read the voting experience much more easier for people to come in. And they said, look at Arocon, Arocon is a good reference to look at. And one of the other members mentioned it would be cool if we have an app, okay, build a big community and test the concept. And another member mentioned we need, not only do we need a good interface, we also need a better problem, how to guide users to make informed decisions. So how we communicate and coordinate so that people will participate and they'll be meaningful. Then we move on to the third problem, which is, what is the problem? Somebody shout out, what's the test? Are you testing governance? Yeah, how do you test governance, right? So before we even talk about testing, one member pointed out something very important, which is to first establish what success does look like. Successful governance should match with returns, not necessarily financial returns, but also social well-being returns. The fourth problem that we went into is that how much does GAU's look mirror to corporation models and are there any lessons that we can learn from it? So in the very short time that we have, there was a lot of examples that we can refer to. Again, social benefit cooperation, donor advisor funds, participatory budgeting, like for example, what's happening in the US Madrid. Please feel free, all these keywords, keynotes that you can check out later and you can do research on them as well. The fifth problem is when do we need to use identity solutions in GAU? So what was brought up was, whenever there's quadratic funding, or whenever there's one person, one equals one vote, okay, an identity solution is relevant. Who is working on this? We brought up identity, okay. All of the members point out that when it comes to identity, it really is the holy grail of this subject matter, but we still need to continue to work on it with what we have. Another member mentioned that, you know, rather than Facebook giving me an identity, okay, why not we work backwards that a person can basically put in the identity that he wants and then fills it up from there rather than having a centralized authority giving the identity. That was a very interesting idea I thought. Why would I just use IPFS with my identity on the blockchain and then get it from there? One other member also brought up, okay, that. That's it. Right, sorry. That's okay. Identity as one vote, okay, can be capitalistic because when that happens, the more you have, the more power you also have in the voting process. What will be interesting, but more difficult to actually do is to have identity as one unique person. And as for next steps, John. Yeah, great summary. So yeah, some next steps that I pulled out. We didn't discuss as a group because we got absorbed into the discussion itself, but some next steps I pulled out of the discussion would be perhaps to develop a good information, curation and discussion methods. So first, you know, facilitating a great way to have discussions around decisions that Dallas are making, but then also to curate that information for people who maybe aren't as engaged in all of the discussions, but who want to contribute to the decision making. Another is delegated voting. So I think that kind of follows from that whereas somebody isn't able to make an informed decision, they might be able to delegate their vote to somebody who they trust to make a good decision on their behalf. And along these lines, who would be good to have an easy voting interface that perhaps works with maybe all of the different Dow models so people can see what Dow's they're a part of and vote really easily. I think you're gonna need delegated voting for that so that they can keep their keys offline and then just vote from keys that are on their phone or something. It would be great to have a unique personhood mechanism to enable ID dependent mechanisms like quadratic funding or quadratic voting that he mentioned earlier. So he mentioned a couple of projects that are working on this and it would be good to see these like integrated directly with Dow or voting mechanisms so like bright ID or IDN3. And then finally, perhaps we could design some like off the shelf models that people could use for low stakes, short run Dow's so that we can quickly experiment with governance and most importantly in a diverse set of communities so that we can see how these tools interact with a bunch of different types of cultures and people from different backgrounds and age groups and so on and so forth in a way where people don't feel like intimidated by just how much is at stake but something that could just be quick and fun. But yeah, I think those will all be pretty cool next steps to take on as a community. I just wanna address something you said as a next step which is an easy interface and actually Dow's stock has something called Alchemy which is where all the Dow's are housed and you can participate. And also, Venge's is building something called Dow House which is where you can access a bunch of them all at Forks and actually do some of the functions from there instead of like a mollusk site to something like a rage quit. So we definitely have these things growing in our ecosystem. Any other comments? You can access all your Dow's from all the things at the same time. This is my Dow dashboard. My Dow dashboard. My Dow dashboard. There's an eight Berlin project. And the Dow House is for launching your own more. Launching and access. And access. Be cool, maybe another one that's to list these resources so we can all understand and start coordinating to know how to be really nice. And that was mentioned and it was on your slides on bringing Dow's, Dow's, Dow's there, one of this. So those guys listed all this because maybe we could. Yeah. Cool. No, in fact, somebody from our team they talked about having a united Dow's. So imagine that. Oh my God. Nice. Check you need this. Wow. Yes. I like that. Don't say United Nations. Reversing the United Nations. I did. Okay, cool. Thanks guys. That was awesome. Take your notes into the HackMD. Please do so so we can capture them. Thank you. Go ahead. Should we start a new Dow to continue with all of this? Oh my goodness. Oh my goodness. We wish we had more of a new start. Our attention, this is so awesome and I'm really enjoying this. So I don't think that the Dow toolkit met, right? Okay, so that one's canceled. So to Dow or not to Dow, we've talked about ethics. Come on up. Announce yourselves. Is this feedback really, really annoying? Are you guys good? Okay. Thanks guys. We can cut the mic if you need to. We know who you guys are. Hi everybody, I'm Georgia. So we don't have it in a very cohesive manner. I'm going to go through and not take too much time. So if we want to Dow or not to Dow, there was some strong opinions both sides in our group. Some people very much like to Dow is never a solution for anything. All the way up to. We should be using it all the time. So I'm going to go through some of the points that we brought up. It was a lot around ethical concerns as well, the main problems that we were addressing. And how governance by vote kind of assumes that voters are informed. So there's an ethical problem with assuming that voters are informed, definitely. When votes are weighted, this could allow for differences and discrepancies in how well a voter is informed as well. So we were looking at whether there's an ethical responsibility to impress upon voters that they should be informed as much as possible, as constantly as possible. And so that comes to that information and symmetry which other people have been talking about already. We talked about accessibility issues, single issue voters. We're about people who only care about one thing and are not going to participate in everything else. What does that do? And most people default to inaction. So what happens when we change this model? We're insisting that they take action in order to participate. And that goes against a lot of behavioral psychology around how people operate. So what is going to motivate them to take part? And who has the privilege to participate all the time? So if taking part in this now involves you to be constantly voting, who are those people who are going to do that? Maybe not the person with two jobs and many kids. So there's some questions there. And then if you think about, well, if we're going to incentivize people to take part, what damage does incentivization do? So if it's about gamification, what are people going to do to win the game? Do they really care then about the activity that they're involved in? Whether they're voting or not? There's a strong feeling that there's a lack of knowledge generally amongst people building dows about the existing literature out there, specifically around e-voting and why e-voting is problematic. So I can't remember the name of this guy over here. It's got lots to talk about that. So we'll talk to him if you want to learn more about that. Phil. Phil. So I'm a user researcher, so I care about understanding the needs of users. And I think we should be speaking to people who we're building for to understand their problems and their motivations rather than just building it and seeing who will come. And that's a good way of addressing the ethics there too. So yes, some of the things that we could look at is for communities, small communities, specifically marginalized populations as well, we could be understanding the reasons why people now don't vote. If we could solve that problem and understand that and address it, then that could probably then solve for all the people who do also want to vote as well, so you can have higher participation then. And also understand why people are voting for the wrong reasons too. So there was feeling that the scope of current dows seems a bit too large. And we came to the conclusion that in order for a dow to really make sense, you need a group of people who have in common the desire to collaborate, cooperate, and have accessibility to do this thing. And then one of these three things is missing, that is probably not right to have a dow for it. There was definitely feeling that where a dow is addressing something really life-changing, where the proposals could mean life or death, or significant effects for people's lives, we are not ready right now to be addressing any of those kind of problems. And thinking about what is the risk to a person who leaves a dow, you know, is there a risk to them in any way too? And yeah, we talked just a little bit more about, just because this was brought up, the idea of could you get someone to vote in order to unlock their phone? Well, what we might end up doing is in order to incentivize people to take part in dows, we could be building in the same manipulative design practices from one to two applications in order to get people to vote. So there's an ethical question around there as to whether we really want to be doing that. Do we want to make it like a game so that people participate if they don't actually really care the outcome as well? I think that's about it, but we're gonna put our notes in. Thanks. Everyone in our group needs to put your name on this thing down and hand it around. Thank you. Sorry, so do you have any thoughts on the different cautionary principle of in what cases is the dows okay and in what cases is the dows not? We came up with the idea that small communities around single issues are the best place right now. So, particularly groups who can muster around a problem together and solve it that way. So, let's organize access to the order of the religious agency, for example, or protect this place and learn something which is a direct service, and we can all very contentious. Great. Thanks guys. Any others? Any others? Did I see a hand? So. We could have had an answer or a question towards that one. Because I thought maybe you walked in and are interested in the social scalability of some extent and maybe those kind of organizations in small, contained communities would need a blockchain and maybe you can organize with the face-to-face interaction. Yeah, thank you. And maybe that's interesting you guys like to kind of take those structures and scale them up for a larger community. Well, there was a question that we had in our group which is if this is already working effectively within a small community by whatever method they have then why complicate it by adding a gap? Coordination. Trust. Trust. Why do they trust each other? Trust each other. Trust each other. Trust each other. Trust each other. Trust each other. Trust each other. There's a question of whether, you know, we're all building to create the US and blockchain is easier, but are there actual tools that a blockchain can provide to help this community, even if they're doing okay? Like is there something else that this technology brings that would improve the coordination? It requires behavior change and behavior change is the hardest thing to get right, to get people to do. So right now, the far into entry is way too high. That's what we should be addressing. Yeah, and maybe finding the use cases and the places where people are ready to make that behavioral change, but not so much focusing on the ones where they're not ready for it yet and analyzing that, which is a really good point. I think it's this. Yeah, hold on. Sorry, you wanna give a quick question? Yeah, just, I think tools like Lumio, I don't know how many people are familiar with Lumio, where it's just, you know, it's basically interface for voting. I feel like that's very good for a small group of people who trust each other and have some kind of physical capacity, I'd say, or like, kind of experience with interfaces. So that still definitely assumes a lot, but I find that non-blocked tools that are also very similar to what they would scale up to be are really good onboarding tools. So it always starts with a small group of Lumio before I kind of move on to something that has, you know, gas transactions, et cetera, but it's stinking. Yeah, yeah. But it's really good like paper prototyping. Lumio has another very cool advantage that we actually should really monitor. And it's not just made for voting, it's made for sense making around the program itself. So the tool is geared around finding a better collective solution than any individual solution. And that could be something we should be thinking about instead of yes, no, binary things. But at the same time, I can argue that, no, we should keep it warm and simple, yes, no, binary things. Yeah, on the full amount of behavioral change as well, I think a really interesting idea behind that is that when you look at governance right now, like, you know, as a space, we try to be pretty, well, as this community at least, we try to be pretty anti, you know, money, money, money, let's do that. But I think when you look at governance right now, money plays a huge role, right?  And these whole governance structures have been built up and financed around that. I think that's from like the mollock thing, that's what's going on with Peter at the moment, right? Peter's been pushing mollock for a long time and only now has he received the first check to actually, whoa, you go, right? Yeah, that happened. And I think that's really important, right? I think like the people that are coordinating these dows and the bureaucracy we go into these systems, you know, there needs to be financial backing behind them because otherwise things won't happen. You know, and I think right now, dows don't seem to be able enough to get it wrong. Great, that brings up the interesting question of like, are we actually changing the way that our organizations work? Like, people still need to be paid for the work of even creating or coordinating a dow. And we have this like, a contrarian view, there's no leaders in dows when there are fundamental leaders and they should also be compensated. But then also we have the ability to capture value in different ways than traditional profit structures, right? So now we also have the opportunity to redesign the incentives, which is really nice because we get to create a new way for people to be rewarded and to capture more for their labor use. Well, then why do we call it dow? I mean, that's why I think the house doesn't- Peter just went high. I just think that we are using a wrong name and by calling it dow, then we're gonna have a person that is gonna be leading the efforts. It's not really decentralized. I mean, the leader can change every second. Yeah, someone has to do something. And that's all she's saying here. The aim of it is to have a very, a lot more autonomous from now on. I wouldn't say it's wrong. What did you say he did? I think it's wrong. Sorry? The difference between leadership and control. That's how you can have a leadership as informed. That's a great point. I'm telling you, I'm going to show you what we're gonna come to. And I wouldn't say it's wrong, but if I agree, dow is a term that's much broader than what each specific implementation indicates. Each implementation is distinct sort of and the community that forms and the culture that forms around each implementation, you could describe each as either a company or a co-op or some sort of, right? Dow, though, is kind of- It's kind of this blanket. Yeah, but it's called decentralized, right? Yeah, no, I agree. This is decentralized and autonomous. The same thing. Sorry? If you want to bring it between, then talking about your problem is, he's not making sense to you. Yeah, there is. That's exactly what I'm saying, that we're using the wrong naming convention. That's exactly what I'm saying. And the deal, I mean, as you want to share with the media, it's just that it's not discussed. Rachel, man, if you want to speak, okay? Let's make this coordinated. We're not gonna- Okay. I want to say decentralization, and I think sometimes it's a group in one thing. You know, you can have decentralized financing models and also have some type of leadership. You can have decentralization of leadership but actual decentralization of funding. So I think it's a bit of a mystery, like to say, if there is leadership, it's not decentralized because we see the same thing on layer one, right? Like, you're gonna have decentralized notes or you can still have decentralization because it's all on AWS or something like that.  Yeah, wait, wait, wait, I saw one right in the middle. Sorry, I see it too. Oh yeah, I see the letters D and A have more to do with the medium that's floating between them. Yeah, that's how it works. I would also add that, like, leader doesn't imply that the leader has more decision-making power as much as it is who is executing. Like, who is taking out the trash? Does it mean they're the ones deciding where the trash is going? I think also we don't have to, like, compact everything into a DAO, right? We don't need to say that, like, a participatory or a horizontal or collaborative organization has to be a DAO. There's value in these potentially separately. And also, I think we have to, to your point, we also need to acknowledge that, like, back-end labor happens to, like, organize and socialize and create the communications around how you implement a DAO or a horizontal organization. We want to honor that labor fiber we want to do it. Last one. I think we have a broader problem at hand which ties, which you're linking to it is, like, we are open-source based, right? So there are people here that are contributing with work, which we cannot remunerate based on the work produced kind of, right? Because they can't cooperate.   And I think that, you know, if we do it for ourselves, then it might be easier to come to other people and let them know we figured it out for ourselves. Because, you know, we already hear people talking about licensing, coding on these young, you know, so. So going to that house is doing the raid guilt. Tell us. New DAO. We know just to experiment on that exact thing. If you want to try to work together and work on how we can do that right now. What's the name of that? Raid Raid Guilt. Raid Guilt, Raid Guilt. I think, I think I need to- Don't call it that. I need to call it the Guilt Guilt. Yeah, I think we still have one more group. So this discussion is so amazing. Will it be so cool if people have other thoughts that they want to contribute? Please put it in the hack, MD, and we can continue this discussion. But that's really awesome. Thank you, everybody, for participating. But we still have one more group and I want to give them the opportunity to say all their things. So why DAOs?  Thank you. So come on up, announce yourself. And then before we get back to our questions. This guy's David, he could call me dog. I like dog more. Dog. I just want to keep my, I think he's a good dog. So yeah, we've been mandering between three different kind of things about the state of the DAOs right now. So we discussed a lot about all of DAOs, about the right DAOs, Roja DAOs, all those. We also talked a lot about the old failures of the DAOs and also talked about what DAOs could do if we just envision this great future where we don't have all this shit, we only have the DAOs and they do what we want, even though we don't know what we want. What I'm saying is it was a very difficult discussion to put into key points, so I'll just give you what we have. So first key point, we had a consensus that offline and online communities really require deep relationships and most often trust as well. And we weren't really sure if it is possible to just muddle the trust away and just find a mechanism that we can just not have to trust. So it's definitely something that any discussion about DAOs will be getting back into. We also found several use cases. You can find them in a heck of me, I'll just read some of them. So one of the biggest use cases we had was that DAOs allow, and that's a claim, DAOs allow sidesteping the current structures that force organizations, if you just ignore DAOs as a structure into this binary decision. Are we doing this for profit? Are we doing this not for profit? So our claim is we can use DAOs to kind of enable the spectrum in between these two, and like somebody from the middle said a few minutes ago there, we can also really decide whether we want to have the spectrum more on the funding side, more on the governance side. We want to do sample as both. We want to have this fluent. And another claim that we make is that DAOs, because they are kind of shared software stack, enable fluency and all of that. And this is what we believe is one of the key points for anyone who's investigating now is that this fluency in the structures is one of the key sort of big selling points that we're all somehow subconsciously hoping for. What else do we have here? Oh yeah, one of the typical use cases is governance of decentralized projects using DAOs.  I'm with them. I'm with them. What else we have here? Yeah, obviously a new means to capture value and enable value creation with less social and legal friction. I'm not really sure if this is the case in all cases. That's why we're actually having this workshop, I guess, to just enable the design patterns that will make it easier for future generations of conscious people to design DAOs just in a better way. And a big claim we had, accessibility is still not very equally distributed. I mean, there are populations that are not online and there are populations that do not know that you can actually have an organization on the internet. There are people who are unaware that forums exist. That's a problem that is just going to, in my opinion, personal, it can solve itself with time with the development of the digital space in general. And one claim that we had as well is that DAOs provide a digital interface to a social process that often or in the past was hidden. So, for instance, it was this example of the young DAO or if we just imagine we have a more advanced version of that, which is actually a super pack, you could kind of see what's going on in a social system that you normally wouldn't even be able to see, you wouldn't be able to see results, outcomes of that system. But now you can just go online or in the future you could go online and just check what's going on, who's voting, or maybe if you cannot attribute individual identities to individual votes, you can still see what's going on without having to ask your immediate surrounding social network. So maybe we can actually gain some sort of super transparency that is not really something that humans have had in the past. And anything to add, guys and gals? Oh, no, the gals want to vote, I guess that's it mostly. I think, do we have some time for open discussion? Yeah, anybody have any other questions? Hello. Why are we all here? Why DAOs for you guys? DAOs, DAOs, DAOs. Some people are all about new, I think governance is boring. What I care about is new kinds of money, which is what I change a lot of you to do. Tokens are great, but lots more tokens.  Solve more problems, that's for me. So for me, what I announced is that you can continue around a shared mission that if you were a company with shareholders or non-profits, it would be very hard to contribute. And because I come from an insurance background, and insurance as it is sucks, because it's shareholder value maximizing. Whereas traditionally it's always been about helping the community as a whole and avoiding their controls. But that structure is very new thing for it to scale up and repeat with shareholder maximizing the success. So it's whether or not it can work, but it's exploring a new way to push a mission that benefits the society as a whole versus one person or one entity. I think that also to discuss the local community example, I believe that DAOs can be a nice setup, even if you have trust and you have that knowledge between people and common goal, like to create mechanics where you can coordinate decisions and also make it from people from outside the bubble if this is a more general problem. I'd like to second one, which is basically, when you have a DAO, it's really about making trust to the next DAO. It's not only because blockchain giving us cryptocurrencies where we have a trustless monetary system, but now we can delegate the trust. We can see change in places where traditionally we're not some change, like for example, my personal interest is in renewable energy. I'm very frustrated that I don't believe that the large corporations and the governments will work together to transition us for 100%. So what if we have a DAO that basically collects funds to give out loans for people who actually want to install panels and we don't compromise that, it's free from corruption, it's free from manipulation, shared vision. Basically the money goes to where it is. Yeah, I thought that the big questions they'd like for me is seeing that this might be sort of, I don't know what to say, but it's kind of reinventing the wheel in some respects and obviously we're quite just from someone in over who you have worked with already in organisations where they do have these mechanisms already. I think it's cool for us to play with it and that was the point we came to, that it's kind of put to experiment and learn the lingo and for me it's always been great in doing that. And then when I go to an organisation and do the same thing, it's like, oh yeah, they're just doing that in a digital form. I just kind of wonder the advantages. So for some who are coming from the digital space, it gives them more exposure to these processes. And I think for those who aren't already involved in that process and can do that in a community project say they'll have their own personal experience, they'll just feel like they're part of the process. And if these digital tools can work hours, they can give a good visibility of where a vote goes and say, oh, I voted on that and then now I have the fountain built in my community or something, that's the positive side to it. So it's, I'm sort of torn to say, like there will be an element of reinvention in the world to get familiar with it a bit, but hopefully there is something that we'll need to add into it that is saying, here is the potential to be a better participant in this. I think it's there, but I'm just building it. Yeah, I think so. I love that. I think we're going to cut it right there. That was a great inspirational way to end that. So thank you so much. We are already, I'm ready to move on over. Thank you so much for spending this much time with us. Please add any thoughts that happened to you. Even I would be taking this and putting something out into the community. So also stay tuned. This is our cutter. But again, thank you guys so much for your great share. Thank you.