Ethereum World Metagov
Metagovernance Seminar Archive | 2025-10-21 | Unknown
Speaker 1: Okay. Today, we're gonna hear from Martin, Philip, and Mihai about, about, Shaka and the or Akasha and the and the Ethereum world project. So please take it away.
Top Keywords
- ethereum 0.011
- social 0.009
- ethereum world 0.008
- legal 0.007
- social network 0.007
- entity 0.006
- akasha 0.006
- moderating 0.005
- association 0.005
- blockchain 0.005
- decentralized 0.005
- governance 0.005
Transcript
Speaker 1
0:00 – 0:00
Okay. Today, we're gonna hear from Martin, Philip, and Mihai about, about, Shaka and the or Akasha and the and the Ethereum world project. So please take it away.
Speaker 2
0:15 – 0:15
Thank you very much, Nathan. I will do the intro. So for those of you that have heard of Akasha, Akasha is the correct name, It's a kind of an old project and we've been, let's say, co evolving along alongside the whole blockchain ecosystem and the general understanding of what blockchain can be in the context of decentralized social networks. And, you know, if we look back, the first experiment that we tried to do was, can we use IPFS as a technology and a smart contract to build a fully decentralized social network? And since then, we grew in our understanding of what would the success look like in this decentralized paradigm, and that's how we reach the vibe viable part. As in, if it's not capable of, independent existence, then when where is the decentralized, part? And, you know, this is one of the set truths of, decentralization, let's say, as a movement today because I think it's only a keyword sometimes. But we'll we'll get to that. That being said, I represent together with Filip and Martin the Akasha team. We are a team of 17 people. Interdisciplinary by default, so to say. We come from a wide range of fields, like Martin, for example, is a former biochemist, you know, the med scientist type of, the cool the cool kind. Filip is also from, like, the more social sciences, and I'm, in this blockchain space since, 2011. When together with Vitryk, we started the Bitcoin Magazine and later on the Ethereum project. And that's end of the the pinnacle. But if you look at the history when talking about Akasha in this particular, talk, the initial version was kind of like, what would be the user experience that we could just replicate and why we use this meaningful technologies in the back end. And it was kind of like a medium type blog posting platform where the mechanism was quite simple, and we even used the private chain just to, you know, as a test net. And, you know, it was during this time when everyone is like even though the pieces of that stack was kind of interesting, the most often asked questions during this time and particularly also during the beta phase when we expanded and started to do also the web access. The most asked question was like, when ICO? So we went through that whole period, you know, and we made the commitment not to do an ICO. And, like, moving on from 2015, in 2000 between 2017 and 2020, we basically rebuilt from scratch to other fully working decentralized apps. Only that in the beta versions, we applied some of the lessons learned, like, we were able to make the content load faster. You know, the user experience was one of the, things that we were really focused on because, you know, Blockchain in general is such a cool idea, and it can make so much impact. But, like, if it's not usable or at least enjoyable, you only do it when you really have to. And the social interaction is about having fun, you know, not being there doing some chores. And, to our surprise, you know, we had, like, one of those moments, Wow, look, This we we are here. There were also a couple of books where Akasha and our initial efforts relating, you know, social networks and blockchains was mentioned. And since then, you know, during this and as the team grew and our understanding grew, we are finding ourselves at this point where, let's say, we combine all the experience we had during these three apps, social networking apps. And we tried to make something, and this is a metaphor. It's not like a super accurate one, but it should serve as a, you know, a close comparison. You can imagine something like the WordPress for decentralized social networks. And, you know, this is quite different from the idea of just building one social app that would be decentralized, the decentralized social network. This moves a bit into the meta, because now it's not about building one social network, but about building an ecosystem of social networks. And this is kind of the meta social network, and that's kind of a decentralized social network when it's comprised of other decentralized social network and, you know, inception. And just to kind of highlight, during this, like, learning curve, I think it's an accurate name, we also realized that, you know, like before Akasha, Akasha, especially during the early days of Ethereum, there was the the component of, like, the the legal entity. And today, we are speaking as the Akasha Foundation, a nonprofit born at the intersection of blockchain and collective intelligence. Yeah, blockchain. And we like, what we talked about until now is the software framework, the Akashabode framework, as we call it, which is this set of libraries, tools, and services that can be used to build the customized social networks. So you can think of, like, Blockchain augmented social networks. In some cases, it can mean just basic transactions. In other cases, it could be more complex on chain interactions. And this is, like, a part, you know, like the whys, the legal framework. And this is like something that we reached a bit later, but it was something that was kind of becoming more and more apparent as our, you know, toolkit matured. It's like, oh my God, we are almost ready to deploy this. And what about the governance of this, and how would the community self cover, you know? And this is how we started to do a bit of legal hacking, bit of legal hacking, by designing this independent legal entity, to serve for ethereum. World, as the the community self governance structure. And the Ethereum world is the first social network that we are building with this framework, and the aim is simple, to unify the Ethereum ecosystem of apps and services. And in the Mission Manifesto is, like, the declared purpose of this particular social network is to accelerate the adoption of Ethereum based apps and services, making transforming how they attract, direct, and engage users. And, you know, for, like, at the surface, it will look it might fool you. It's like, you know, kind of a feed app. You scroll, you see posts, you see hashtags, and this is not by accident. We actually did some user research and tried to understand from the perspective and, like, the almost like the collective consciousness of what the Ethereum community uses today. Twitter seems to be, like, the favorite tool. And, you know, it was an interesting, for example, a dilemma where do we want something like character limit for post? Yes or no? And, you know, for example, the person that joined our UX team was like, I don't think so. It's like testing our assumptions. And people actually wanted the the character count limit, you know? So it's like we it's even the slight decisions in here, at least we we try to inform them with the actual data. And the interesting part part is that behind this user interface, you can also think about the framework that can be used by all these Ethereum developers to integrate their apps and making it available through this social kind of experience. And then you also have the community that can actively engage in self in the self governance process by joining this legally recognized independent entity that, you know, also brings the benefits of limiting liability and so on and so forth. But I will just make a pause here and pass the mic when it comes to the thinking for social networks, social side. Filip?
Speaker 3
0:30 – 0:30
Thanks, Mihai. Yeah. I think if we just think of the phrase social network in the pre digital, the pre web context, then it invokes some aspects of community that we're all familiar with in our everyday lives. And in many ways, the web two manifestations of social networks is kind of, if you like, bastardized the phrase or or at least they've been disingenuous in in in using it. So as we try and understand how social networks might work, if you like, can't launch without ripping off the web two behemoths? What might that look like or how might we compare and contrast the two? So we've just got a very straightforward table here to convey to you how we see the distinctions. I won't speak to each of the rows, but I'll definitely linger on the first one, for example. When you think of Facebook, you think of a tech stack that's proprietary and wholly owned by a Californian for profit entity. But surely, when you think about a a Web three social network, then the social aspect has to come to the fore. This has to be a beautiful interweave of people and technology. So the emphasis, I think, has just changed in terms of its design orientation. You go from being a user to being a participant. You you you start having the platform owner at the center of everything and you you you respect the dignity of the members, the participants. One of the interesting things for us given that Akash's purpose is expressed in terms of unearthing collective intelligences is the dominant dominant mechanism for web two social networks has been control, and we could talk about that in an academic terms and, you know, disciplinary and surveillance and panopticon and all that sort of stuff. It's not so much perhaps the control over being seen, but the fear that you might not be when someone else is pulling the levers and turning the dials. Whereas we like to think in terms of what you could call a plateau of intensity, which was Gregory Bateson's term for a liminal state between just straightforward, unchanging stasis and complete chaos. There's this liminal layer in between where fascinating things can happen. Evolution can be manifest. Collective intelligences can emerge. Another line I'd linger on is topology and tug my forelock to Nathan for having come up with a bit of a phrase that we've internalized at Acacia, which is that decentralization is a means, not an end of itself. We believe that what we're trying to do with web three social networks requires decentralization, but it's important to recognize that it's a means rather than an end. And perhaps we use the word business model in slightly, you know, just a few quotes around it because, yes, Web two has been about a business model and value extracting whereas Web three social networking is very much about value adding. It's about everybody being able to contribute the value that they might in order to derive greater value collectively, Which in turn ties into a little cartoon that Hugh MacLeod did that kind of captures up our essence if if I'm honest. It's just shows the transition from data information to knowledge with with which we're all familiar insight along the way, helping it crystallizes wisdom in order that we can have positive impact in the world. So if we want all of these qualities in the Web three social network, then we have to talk about organizing and governance. So riffing off the the the previous slide and its respect, if you like, for Alice's dignity, And what you could say is that it the non duality of the self and the system. This isn't about Ayn Randian self sovereignty or Confucianism, love of collectivism. This is something in in between, if you are more realistic, more pragmatic. And in simple terms, it's situating Alice's voice. So this little diagram here is from Pangaro and Dudley, and it represents Gordon Pask's conversation theory. It basically is a theory that describes how different participants can create value together, can do work together through conversation, which leads to actions, which leads to transactions and agreements. So we have to if we're gonna be socio technological, we have to accommodate and inspire, empower conversation. But we also then have to recognize how those agreements and those transactions are codified. And the way we've done that for the last few centuries is with legal code. And, of course, in our domain, we also have technological code. So in other words, web through social network kinda has to be trilingual, has to speak all of those three if that's not a meta metaphor. Now contrast that with the code is law approach of the early DAO enthusiasts back in well, I guess, 2016 was a particularly interesting year in terms of the DAO as it was called. They never set out to emphasize conversation or legal code. It was very much about the the smart contracts. Conversation only came in at that point when $50,000,000 USD looked like it was heading out the door and suddenly conversation was very important. And as Joshua Tan wrote last year, early explorations of DAOs focused more on their technical development and less on their social implications. But here we are now, 2021, and we kind of think in terms of machines transact and humans converse, and we have to play to both of those. We're kind of weaving a bit of Claude Shannon and a bit of Gordon Pask. So this legal aspect is really important to us. Mihai, can you pick up again?
Speaker 2
0:45 – 0:45
Of course. Thank you very much, Filip, for grabbing the mic. So, you know, the need for and choice of a legal entity is probably, like, the driest and most boring slide that you can, you know, you go at the Blockchain conferences, like depends on the conference, you know, if it's something in the legal context and maybe it's cool, but in most, it's like boo. But I have to confess that especially in the early days and, you know, this was back in 02/2014, now it's 2021, things are a bit less dark, more gray. But back then, we were faced with this problem. So Ethereum was not yet born let's say, born as in the Blockchain itself, but we had developers working actively on the clients, the Ethereum clients. And, you know, we had a few. We had the c plus plus client. We had the Go client. We had the Python client. And, anyway, the the point was that we had these developers asking us and themselves, will I get in trouble for contributing code to this project? And, you know, in some cases, it's one of those situations when you go for a clear answer to your lawyers and say, hey. Would they get in trouble? And then they reply, well, it depends. And then that's, you know, it's like hours and hours of discussions. But, the certainty is that, you know, I was also one of the earliest enthusiasts and, you know, I was passionate and already thinking, oh my god, DAOs, before the blockchain was even there. And even in the early post, some of the on the ethereum.org when we were discussing about the plans of the foundation and so on, the idea and the vision of something like a transparent, open, community governed, DAO type like structure was in the air, structure was in the air, you know. So this was something that we were going towards. But the pragmatic and, you know, the reality is that you do need this entity if you want to operate in the real world. If you want to enter service agreements with your developers so they have, like, a clear, for example, legal liability and so on and so forth. And the the set truth is that, you know, even if code is law and it can be seen as law in so many dimensions, Just pretending that the laws related to jurisdictions evaporate is like sticking your head in the sand. So I am all for decentralization, but at the same time, it's a matter of looking at the pros and cons. And since then, when we were looking at the initial models and what would be most suited, the end choice that we made for Itanium was a foundation, as a nonprofit, as one move to solidify and, like, protect the vision from any corruption that would be brought by for for profit business models. And, you know, it's like, you might say, wait, what would that mean? The vision there was like CryptoMozilla versus CryptoGoogle, CryptoMozilla one. And if it would have been a CryptoGoogle, you might have been in this situation where you see many protocols, composable protocols, forming the DeFi space, and part of what makes and drives current adoption for Ethereum. And if there would have been some, like, key components that would have been identified as a profit making mechanism, if the Ethereum would have been for profit, you could expect to just replicate that and it's like, oh, wow. This is by Ethereum, the official. I'm gonna use that, not that random developer from the Internet. So anyway, I think long term and looking at the result here, this was the right tracing, kinda create this Linux type safe sandbox for different organizations and interest to play in. And since then, like, fast forwarding, I will pass the mic to Martin to talk about the choice and how this plugs into the picture.
Speaker 4
1:00 – 1:00
Yep. Thanks, Mihai. So when when so as Mihai outlined, it it's a it's it was for us a very important question, what type of legal form we would be using for for Ethereum world that is compatible with the intention and the ideas that we have building here a decentralized social platform. And you know that there are some maximalists that would say, yeah, of course, you you guys are on Ethereum. Or you you have a blockchain project. You need a DAO, but there are definitely limitations of this choice. There is not really a legal entity that is recognized. It's basically merely a collaboration that people would engage in. And so they would be each individually liable for the actions they take on on such a entity. So that's why it's important to, in our minds, to to to take a step back and start bottom up with an already existing legal entity. And the choice that we made, in this case is, the Swiss Association. This is, despite its, its its its provincial name, maybe, it is a legal entity that is used by by quite a few internationally operating organizations. And we like it for several reasons. First, it's very simple in terms of its constitutional requirements. You you could set it up with just two people that need to formulate basically, the articles of the association and define also a board and appoint a president. And if they were doing this all among themselves, that would be fine. You wouldn't even have to register this. This this legal document seals already the the requirements of a Swiss association to be recognized in in the Swiss legislation. What we like, especially, is about the idea of an association that we are talking here about members and not investors. So we we are not interested in selling shares to to investors that want to invest in that project and then at the same time have value extracted from people that are relying on this platform. Instead, any participant of Ethereum World should be able to have a say. You might imagine you just share Ethereum World with others to communicate, and that's that's the way that you derive from it. There might be bloggers that use their profiles to to monetize content that they want to share with others. They should also have a say and and not basically depend on that on that top down governance structure of a of a typical web two company that might just kill the pro kill your profile, change terms and conditions. So it's democratic by default because every participant can become a member of that association and has a single vote. We currently set out in our articles a one member, one vote policy. It's also an organizational form that is very easy need to be joined by by anyone worldwide, both as a as a as a company or as a project if you want to be joining as an, software developer that wants to to to to, implement this, smart contract with Ethereum world, but but also for anyone else. So what we believe, in the way of, how the Linux Foundation has recently formulated similar efforts, we believe that this is the minimum viable form of centralization required to to to bring put to push this forward project forward, basically, and put it on on a sound legal ground. There you might you might argue, of course, is is a problem with this because you still have a president, and you still have a board in an association. So that's quite a political business usually, who who should be elected and so on. And for this reason, we have we have devised a modular approach to this. So, Philip, can you Yes, thanks. So on this slide, you see the concept of panels. So what normally would be the board and the members' assembly now is, in our case, panels and members' assembly. These share the these these two entities, the members assembly and the panels are sharing the sharing the capacity that normally would be residing in the board of physically appointed individuals. In in our case, each of those panels is in itself a type of organization or a group of people up to seven, we have defined, that are in charge of defining what we would call in the vein of the concept of modular politics, which is, by the way, something we discovered after we came up with this and we're really excited about, and that's why we are here today. So these these these panels, basically, are are could be seen in a way as as as modules or as as orgs that are defining the operational procedures of the of the of the association. Ideally, these panels in our idea are very important in the in the initial bootstrapping phase and are setting up the policies. And then later on, these would be increasingly automated, and the panels would be only required when there is need to change something and adjust the agreements that are set out in the code, because that is definitely the case that in the bootstrapping phase or throughout, there will be conditions that it cannot be just run automatically. We also have one specialty, and that is there is while the panels not usually are appointed by volunteers that are elected through the member's assembly. There's one additional legal entity coming into play, and that is a contracted service provider. We call it the administrative panel. And that's supposed to be taking care of the day to day operations, and it's seated in Switzerland and can also perform all the legal duties that the association has in front of the legal court system. Yeah. And I hand over to Philip who is gonna
Speaker 3
1:15 – 1:15
Thank you.
Speaker 4
1:30 – 1:30
Locate the organization.
Speaker 3
1:45 – 1:45
Yeah. Thanks. Thanks, Martin. So this is if you like, it's been the the legal lens onto Ethereum world, specifically the Ethereum World Association, but we're also interested in the way Joshua Tan was writing about the institutional viewpoint in the post that's linked to at the bottom of this stack here slide here. So if we if we take the institutional world view, I guess this is, for those of you who are not familiar with it, comes from Ostrom's analysis of common pool resources, which in turn set the groundwork for institutional design. And I guess that's instructive if our immediate focus might be more public goods than common pool resource. But at the end of the day, whether this is a public good or not, it can be used for organizations who are focused on the management governance of common pool resources. So on this slide, let's go through the pattern or let's see if we can apply the pattern of the institutional view to the story we've just told you. So we have an organization in the loose sense, so it's not an incorporated entity. It's just people coming together for common purpose, and that's Ethereum world. It has participants. Within that, there is a constitution which effectively is the combination of the values that somewhat the norms and the rules. In term, as Joshua points out in his post, you would have some infrastructure that sits alongside that. In this case, it would be the Akashic World framework, open source software. And then within the constitution, he pulls out the idea of computational constitution. So that is, if effect, if you like, the digitally augmented constitution, that's how the rules are enacted in the organization of Ethereum world. But alongside that, there's another constitution that we call the conversational constitution. And in that instance, in terms of talking about the constitution that should inform the rules and values of
Speaker 2
2:00 – 2:00
the
Speaker 3
2:15 – 2:15
organization, we introduce the association. Now it itself has a constitution and members. Every participant can become a member, which is why it's a subset of the latter. And then it has computational constitution, for example, a voting mechanism. But it also has a conversational constitution in terms of how we go about discussing policy changes. So you can see this this nesting, this zooming in. We can zoom in further. Each of those panels that Martin describes is to the association as the association is to the organization if you wanted to zoom in. Equally, you can you can zoom out if Ethereum world is one of many worlds, then above that, there is perhaps a a world of worlds. It's it's a it's a little halonic, if you like. And whilst data has no scale, information does. So we may well require them for the information to carry the informational context of that scale. Looking forward to talking with Joshua a little bit more about the institutional view, see what we can learn from that in our work. Perhaps the hottest topic of the day when it comes to governance, however, is moderating. The not a day goes by without news about online hate speech, potentially harmful QAnon conspiracy theories, the Trump ban. It was only a few seminars ago here. I think that we had Stevie Chancellor talking about her work in all things to do with social media moderation. So we know that this is a really wicked problem. And if we aren't to be in a situation as Facebook is where they employ tens of thousands of moderators, we need to do things differently. So we have a number of design goals in line with the general web three ethos of freedom of speech. We have to moderate that with freedom of attention just because you say something doesn't mean I have to hear it. We have to make sure that moderating actions are available to all if we're going to be agentic here, empowering, respecting Alice's dignity. It needs to be robust which means the moderate moderating actions have to be contextual and distributed. Alice needs to understand them and understand the ramifications of actions that have an a moderating influence. So there needs to be simplicity. But in order for this to be a viable social network, in order for that liminality of that that plateau of intensity, then we need the requisite variety. At the moment, we're conceiving four cybernetic feedback loops if you like. The first is perhaps neglected in normal conversations about moderation. This is just general conversation and behaviors, culture, how we do things around here, how we don't do things around here. It's just intervening as you would do around the dinner table. Then there's the loop that most people consider moderating and often in the negative sense where I flag something as inappropriate and so somebody ought to do something about this, please. But the second loop also has positive feedback as in this is the kind of thing we wanna see more of. The third loop is about recognizing when moderating is working and when it's not working so well, so how do we adjust it? And, of course, then that feeds in because moderating is a subset of governance into the overarching governance of the organization. So this is this is these are all information flows. These are all conversations that we need to facilitate. So where are we on our moderating journey? And it is a journey. We need to start somewhere because no group can go from zero to hero that quickly. So this table just situates where we know we are, if you like version 0.1, and where we'd like to go collectively as an organization, as a collective effort. We wanna move from the idea of a role called moderator to the idea of the verb of moderating. We want to include everybody as I've already said. We're moving from a power play to one for requisite variety. The focus is definitely moving away from moderating as negative feedback in that second loop I described to encompassing at least all of those first three loops. We are expanding it in terms of those loops, that richness of feedback, that contextuality, that locality, so many more dimensions involved. The reach of moderating actions stops being universal and becomes contextual and distributed, which also has inferences for the way in which we might approach reputation. Universal reputation is an evil, so let's not do that for too long. It's okay when we're a few 100 people to start with, but by the time we're into the thousands, we need to start looking at reputation as it helps with moderating as both contextual and local. And we're trying to disentangle the the publishing from the moderating, if you like. The individual can publish and the collective can can moderate. Mihai, do you wanna bring this presentation to a conclusion?
Speaker 2
2:30 – 2:30
Of course. Thank you. Thank you, Philip. So the idea is that during this presentation, you know, we had a choice of, like, what should we actually talk about? So this is like a snapshot from our current thinking on a specific set of problems. And, you know, we chose moderation simply because in terms of, let's say, tangible development, this is one of the areas. It's like, okay, we're gonna build a social network. What is that? It's like a feed. And then, oh my god. What about moderation? Oh, so oh, it's like we can build an app that would would do the moderation and then an app that would take the input and feedback from this to display if chosen by the user, the curated feed by using this moderation. So anyway, that's why we chose the moderation. And as you can expect and already highlighted by Philip, we'll be at a bleeding edge, which means lots of crashes. Many times things not work as they should, but we are getting there and we are very close to actually have something that would be available publicly and, you know, coming soon, the Classic. But that being said, besides the, let's say, subset of governance issues related to moderation, we also have these other active areas of research like self organizing models and systems and modularity and usability by default at all layers of the, let's say, mental LEGO, from the legal part to the softer part to the way the integrations that expand the platform works. And that comes also into, like, for example, questions, how would the community curated and governed app store for Ethereum look like? You know, you how would discovery work in this, you know so there are a bunch of really interesting problems to to solve when you look at this in the context of Ethereum as an ecosystem, and we are kind of zoning in into this, but with the mention that we see this combination of software plus legal frameworks applicable in other context beyond blockchain as well. So, you know, there's nothing really saying that we couldn't see a world for independent journalists, crowd funding, and, you know, time stamping and tracing the are many directions you can go. And while we were kind of doing and, you know, head down and trying to see with our lawyers, hey. Can we customize these organs so we don't have the functions as in in the individuals, but actually distribute the responsibility and power towards the edges, towards the members as much as possible. This is what we reached. And somewhere along the way, we also discovered this modular politics stuff, and so it's like, damn. Look at these guys. They're like, we are we talking about the same thing? It it looks it looks like we're talking about the same thing. So it was like, man, we we gotta talk and see where if there are synergies and if we can do cool things together. And that's where the governance was with now, you know, if we focus the moderation, will be the first really small experiment into, like, really broad, challenge. And, not lastly, generative identity and interpersonal data is something that, you know, is one of those really delicate things when it comes to what is personal data, what is interpersonal data, and anywhere you have this flow of information between participants, especially like in a social network. It goes beyond just me having my data. You are co creating this data with your participants and there are really interesting problems and challenges also there to solve. Filip is doing some great work. You can visit generativeidentity.org and it's a hyphen in the middle for more information on that. And to end with a really classic, you know, problem and active area of research, which should be maybe number one there, the Blockchain UX. And, you know, it's like as we said in the beginning, we developed a few applications, you know, Blockchain apps. And every time it was, like, you know, even for us, it got to the point where, like, man, this is easy. And, you know, then you was like, oh, let's let's have someone to try it. And it's, like, you know, it's not so visible for for everyone. And sometimes it's not even in things that you can control from the interface. Sometimes it's simply how MetaMask works or, like, you know, there are things also out of your control. But moving on, we identified this, leap and which is fought by economic constraints and all that, to a layer two. And this is also maybe quite interesting when you are considering the possibility of kind of like these layers that would encompass and provide the interface but that you can move within communities, you know, lowering the cost of interacting and, like, there are many things that could be done there. But we're still super early and we don't know exactly how that would look. And I would like to, you know, kind of bring the presentation to a conclusion and, you know, we started with this designing of viable decentralized social network. And because we also have some DAO OGs here, I would like to, you know, pinpoint that when it comes to DAOs, at least, you know, for the random Joe that doesn't necessarily understand the magic of Blockchain, that it's, like, transparent. The resource management, you know, it's transparent. You can see, I can trust that, that I'm not, you know that that guy didn't take the money and you know, there are things related to the resource management. And then when it comes to the d in the DAO, it's like the decentralized governance. So it's like, as a community, we can decide on where those resources that are transparent, you know, how they are used. And when it comes to the putting that kind of in this context, we think that through this minimally viable centralized entity that indeed has a footprint in a legal jurisdiction, which makes it, you know, liable also in one, at least you get this shield which protects you from being attacked in all the others. Because if you don't choose a point where you plant your flag, you are kind of liable in all at the same time, which is a nightmare. Imagine having, like, losses for doing activities via a DAO that you're part of in 10 different jurisdictions at the same time. I don't want I hope we won't get to see that happening. But in this case, when we look at the social network as Ethereum, and for Ethereum it's maybe a more special case than in other communities because this is already an established community, We have this idea that if we bring this entity in the middle to empower the community to self govern itself via a legally recognized entity that limits the liability of the members in the governance, We are talking actually about the decentralized autonomous social network, which is like, wow, super excited, and we are looking forward to see how this could be applied in a variety of communities and how this overlaps with also some of the areas of active research in Metagalf and the other projects that you are part of. So thank you very much for your attention, and I'm going to open the floor for questions and for that.
Speaker 5
2:45 – 2:45
Thank you, guys. Thank you, Mihai, Martin, and Philip for that super informational presentation. You guys are working on some really, really exciting things. I I've been aware of Akasha and Ethereum world for a while, but I had no clue how many exciting initiatives you guys are working on. So that was awesome. I'm gonna yeah. Thank you. I'm gonna moderate the q and a. So let's the the first thing I'd actually like to do is to give Seth a chance if he wants to respond to the institutional view question because I know Josh is not on this call. Seth, do you wanna add any comments or questions first?
Speaker 6
3:00 – 3:00
Could you restate the the question? And we're I'm really we're really happy for this for this community to be a forum for intersecting kind of decentralization world and kinda, social science institution science world and several other worlds. So we're really happy. If if you're seeing this as an opportunity to kind of get a deeper sense of of of how those views influence what you're working on, we're really happy to do that. Did you have a did could I'm sorry. Could you restate the question?
Speaker 5
3:15 – 3:15
I didn't have a specific question, Seth. I just wanted to give you a chance to jump in and Oh. Add any comments you had on the institutional view stuff.
Speaker 6
3:30 – 3:30
Great. I mean, you know, I only have, yeah, little little little notes and on on the larger view, I think I have to learn more about the, the the project personally to have a good sense. But you'd y'all can consider me, a a a person to go to if you, have questions. And just want the institutional perspective on the
Speaker 3
3:45 – 3:45
design decisions.
Speaker 5
4:00 – 4:00
Awesome. We had a number of questions on the choice of the Swiss Association. Let me see if I can summarize the questions we had. One was, did you consider any other specific entity types or or jurisdictions, any other sort of foundation or nonprofit structures? Did you decide that other forms just wouldn't work or that this was just the most minimal form necessary? Yeah. I was wondering if you could say any more about the choice if this was association.
Speaker 2
4:15 – 4:15
Can I take this one? Yeah.
Speaker 4
4:30 – 4:30
Go for it.
Speaker 2
4:45 – 4:45
So as I said in the beginning, the search for the most favorable, so to say, jurisdiction when doing blockchain stuff has been something that we've explored since 02/2014, and that's when we've scouted a number of jurisdictions including Netherlands, UK, Germany, Singapore, Canada. We looked at quite a few, USA, and then was like, oh my god. Let's not do that. And the Swiss, let's say, initial kind of setup, that was with after proactively engaging the local authorities and explaining, look, we are doing this. This is like a platform. This can be an opportunity for this country and jurisdiction. You know, it's like, we're not here with the you know, because in the media, it was like, Silk Road and all the bad stuff, and it's like, what about the children? Oh my god. The blockchain people are here. Hide the children. You know? So it but that's like a different topic. But coming back to the choice, there is also an interesting point to be made. There are few established legal frameworks that allow the complete decentralization of power into these functions that dissolve into groups. Most of the legal structures that you have around the world are like the best ideas from one hundred plus years ago. Right? So it was inconceivable almost, like, to envision that what group of random people from around the internet made decisions without some all wise shepherd there for the herd. So at least in my search, I have seen also other initiatives. I will say this, you know, like LAO or LAO is another initiative that's kind of trying to do this from a for profit. I think it's Wyoming or some USA based jurisdiction. And there are other initiatives, but you can try to use the, let's say, units of accounts as some kind of proxy for shares, but they're not shares, you know. So there are many ways in which you could structure this and, you know, including the one that is currently hot. Let's have a governance token, and I will just say that even if I admire the initial intention, which is, like, in theory, sounds like a good idea, when it comes to the actual result, then it's, like, what does success look like in this model? We have this situation where model? We have this situation where governance equals who has the most money, has the most say. And, you know, it's like when you put who who who came up with that idea, you know, looking left at who who thought it's a good idea? But it kind of works, at least in theory. But when you look at then what does this look in, practicing, and then not just in theory, behind these governance tokens, which are more like signaling tools, not governance tools, usually have some kind of entity incorporated some somewhere. So it's like, I don't know, not so, you know, I like the project that I'm mentioning, so it's not like if I mention something, it's like who so for example, even Compound or, like, there are many other, you know, like DeFi or, like, decentralized projects that do have an incorporated company somewhere. And when you look at that, this company would be providing that head where you can point and cut the head, you know. It's like what you're trying to achieve with decentralization and kind of, like, increasing the pass factor. And when you have this type of situation where you do have a centralized entity somewhere regardless of the jurisdiction actually doing and deciding the technological roadmap of the you know, if push push comes to shove and, you know, like, the governor says, 90% of the people, let's do something, but for some reasons, the interests are not aligned with the company actually doing the development and being directly responsible for that development, the entity that is actually liable will have the last say. There is also, of course, like, there will be a fork, and the community can do its own thing afterward, and probably there will be a big fallout. But what we wanted to do here was to actually ignore the tokenomics from the governance problem. And yes, I know, democracy is kind of like outdated also, it's kind of like this old idea, again, like the best idea two hundred years ago, but compared to this model where the people with most money have the most say, I would say, still, maybe it's a better choice than what is. Although I'm open and really excited about all these other ways in which you can customize and come up with your own, like, DNA of governance for your specific needs, which is kind of right to overlap with this. But regarding the jurisdiction, we did not find anywhere else in the world a more favorable jurisdiction, at least from our we would be interested, by the way, if you know, where we could do something like this and get away with it while still being legally compliant. Short
Speaker 5
5:00 – 5:00
version. Awesome. Thank you. That makes sense. Yeah. So another couple of questions here related to the idea of sort of progressive decentralization. I'm wondering if you have any thoughts on this. Like, what strategies might work for starting off centralized, you know, minimum viable centralization and handing things off to the community down the line. There's also this concept of exit to community that we talk about in this group sometimes.
Speaker 3
5:15 – 5:15
So
Speaker 4
5:30 – 5:30
Yep. I can I can maybe do a first part of this, but and then I I I know Meehan has a lot of ideas to say too? So I I just saw another question. I think I want to just put in as well where it was also asked. So in what form would these deliberations happen in the beginning, and how are we scaling this? So the the hands the hands on answer on that, I think it's related to this, will be that we are starting definitely with a nuclear, you know, small small community because you won't be able to to set anything off with with, like, inviting a thousand people and then ask them to agree on something. So so the ideas and also the form in which this is happening will be very organic and nuclear, and there might be initially just cause. We we we won't be ready maybe with everything on our own technology sec yet. So there might be even a discourse forum that that's that's starting that process where we will be discussing how with, by the way, and constitution that's already written. So the rules, the the the permissions, and and duties of these different panels, this is what we have defined. But that's all. We we we needed this for the legal document and the fact that we decided already what legal form we start with. But then in a way and that's the the gradual process of how we are increasingly, yeah, handling this out and distributing the the power in a in a larger community of people that all as members then are able to to join. Yeah? And, yeah, and it's it's it needs to start with just a few people in a in a call and hashing out documents and and and written stuff and and going from there, which is, by the way, again, why I'm really excited to see some of the discussions in the Slack channel because it seems like, man, this is really similar problems. We we are looking here at a specific community, definitely, but but but there are tools being developed, and we are very open to to learn from others. Yeah.
Speaker 2
5:45 – 5:45
I would like to to add something there, like, in regards to, like, how would this be initiated, you know, and we call this, like, the initiation of the association, which is not necessarily the registration. So there will be this, phase in between where, it's it's like maybe a useful metaphor is, like, we are creating this structure. So that's what we created, the structure. Then we open it for the community to kind of self select and see is like this the right structure. If not, let's customize it, adapt it. And at the end of this process, when the community that would actually make use of the structure would take ownership of it and would claim its destiny into whatever governance model he chooses, that's when the community can register that association. And that's gonna be the point where it's not gonna be just two, three, 10. Preferably, it's gonna be over a 100 over I don't know. It's gonna be a a journey to understand also, like, what would be the wisest approach here. But more most likely, it's gonna be a gradual approach. But with the mention that there is this period in the middle where the community can really take control and define or, like, completely override some of the stuff that we came up with before the community really, you know, puts the stand. This is truly a community driven and, you know, decentralized initiative.
Speaker 5
6:00 – 6:00
Thank you guys again, for for the awesome presentation and the the, the answers to the questions. There are many more questions. Unfortunately, we're out of time, and we'd like to wrap up on time. Nathan, I think you can post the questions in Slack afterwards. Right? I think as the meeting host, you'll get a text file or something.
Speaker 1
6:15 – 6:15
Sure. And then and I'll put the video as well.
Speaker 5
6:30 – 6:30
And the video as well. Awesome. So, yeah, please join the Slack if you haven't already. I think Nathan dropped a link in the beginning of the chat here. We'd love to continue with the questions, and if you're not in the Slack already, please join. And, yeah, we'd like to end with a little thank you. So if everyone could unmute.
Speaker 2
6:45 – 6:45
Thank you so much. Thank you so much.
Speaker 3
7:00 – 7:00
Thank you.
Speaker 2
7:15 – 7:15
I'm being here. Thank you for the invitation, you know, and Thank
Speaker 5
7:30 – 7:30
you, guys.
Speaker 2
7:45 – 7:45
Thank you also for this great work that you're doing there. This is pioneering. Looking back, fifty years from now, I will tell my grandson, I knew those guys, you know, when we were just running on that bullshit operating system. So, you know, really encouraging you to continue doing the awesome work you are already doing.