Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Evmos Governance Council Meeting (6.1.23)
Recorded: June 1, 2023 Duration: 1:12:45Space Recording
Full Transcription
Hey, Christine.
How's it going?
Hello, hello.
I will definitely share how our week has been.
We are super busy and we are loving taking the time out to be able to spend this with you guys.
It's kind of a nice little, I was hoping to really tune in today and see what everybody else had going on.
But I will definitely take the time to say, but I will take busy, but I will definitely take the time to say that our week is super slammed to the point where it feels like a Monday all over again.
So that's where I'm going to leave you.
Yeah, I mean, busy is good, right?
It's better than having a busy day, but I will take busy busy, but I will take busy busy, and it's really good for my brain because I'm just like generally a scattered person.
Lindsay always makes fun, Lindsay always makes fun, Lindsay always makes fun of me when we're on calls together, I'll just randomly say things, and she's like, okay, what topic are you on now?
So it is good for me to have busy days.
I'll take that one.
Yeah, busy is definitely good.
Maybe not for my girlfriend, but yeah, it's exciting to see if you have most sequences in like kind of, I don't know, compared to the last year or compared to like six months ago, actually.
So I'm seeing a lot of exciting things going on, and it's very encouraging.
So yeah, I guess we'll get started soon.
Because, yeah, I don't know if everyone's busy or everyone's partying or something.
Yeah, so first of all, today is actually a pretty significant day in EVMO's history, I guess, in our young history, young chain.
Today is EVMO's happening day.
So what that means is, for those that aren't really familiar with the term happening, or it's not even a word, it's really happening, but, you know, like the crypto community kind of coined to this, I guess, a mean term, like the happening.
It pretty much means the daily emission rate of EVMO's is going to be halved, so reduced by 50%.
So it has a lot of implications in terms of the whole macro, macro tokenomics.
We don't typically like to talk about token price or things of that nature, but it is still a significant milestone, I guess, or an event in EVMO's, so I thought I would bring that up.
And, you know, hopefully, we'll see better days.
So next up, give you a quick update of Forge.
So currently, we're actually, Forge is like barely a month old or something, if my memory serves me correctly.
And right now, we've managed to lock up a TVL of around $2.35 million.
We've had more than 50,000 transactions, around $4.5 million in volume.
And DeFi Llama is estimating, if the trend was to continue, hopefully, obviously, hopefully, the trend, you know, it accelerates and grows.
But the annualized estimated volume should be over $125 million in volume, which is, you know, great for the community, first of all, because it is a community-owned DEX.
So in the end, you know, even though we don't charge protocol fees, yeah, I think overall volume is a very healthy sign of a network.
So it's definitely good to see.
And on that note, on the note of TVL, obviously, the token price, you know, has taken a hit.
But we are at an all-time high in terms of TVL locked in EVMOS, not in terms of U.S. dollars, but EVMOS locked in DeFi.
And with the happening coming, that's a very, very good sign, in my opinion.
Obviously, none of this is financial advice.
But, yeah, definitely seeing some encouraging trends.
Yeah, so obviously, everyone knows that the incentive program called Inferno and Forge is live.
And we are working to improve the user experience.
And the Forge team and the EVMOS DAO, you know, we're actually working on a Forge version 2 proposal.
So unlike other, or I don't want to say unlike other, you know, DEXs, but unlike what we have seen in the past, mostly on EVMOS,
we want this DEX to continually evolve and improve with new features and integrations,
and hopefully with projects building on top of it.
And since Forge is a uni-v3 swap or fork, yeah, there's so many opportunities for other protocols to easily deploy on top of Forge and EVMOS.
And I'll talk about that a little bit more later.
And, yeah, better documentation is coming.
We've just been so busy.
Yeah, we've been very busy.
But, yeah, we hear the community.
Uni-v3 is very confusing.
Active liquidity management is difficult.
And, you know, yeah, we totally hear the community.
And better documentation is coming.
No set date on that yet, but it's continually, you know, it's a continuous project.
And you will most likely see updates on docs.forge.trade.
So, yeah, that's Forge update next.
I want to mention some...
Hold on one second.
Hey, how's it going?
Hello.
I don't talk on Twitter spaces as often, so I hope you can hear me fine.
Yeah, I just wanted to talk about the Prop 92, address those concerns whenever you want to get into that.
Cool, yeah, we'll get to that in a bit.
Okay, cool.
That's cool.
Yeah.
Yeah, so, other ecosystem news.
There's a new DEX aggregator on Evmost that just launched.
I believe it's pronounced Eisen.
A's Eisen?
Eisen?
Pretty much it utilizes both Uniswap v2 as well as v3.
DEX is on Evmost and tries to find the best route.
So, yeah, check them out on eisenfinance.com.
I also tweeted about it on this account.
So, if you want a quick link, just go to my profile.
And Pangolin.
So, Pangolin, you know, they made a big announcement that they were going to deploy on Evmost.
And they went through the grants route, and I am hearing that they're actually preparing to launch within the next week, which is, you know, very exciting.
Yeah, it's always exciting when new protocols and new DeFi projects are launching.
Yeah, I'm really excited to, you know, see what they have been building, because, supposedly, or, yeah, I haven't really, I don't know the details, but I believe they're, Elixir pools are some, it's like a new novel pool that they're launching on Evmost.
So, it should be interesting to see how they designed it, and hopefully, you know, Pangolin will play a big role in the growth of the Evmost ecosystem.
All right, before we're getting to Tashi, I also want to mention two DeFi projects that are going to be launching on Evmost as well.
So, one of them is Steer Protocol.
Well, I'll go, yeah, we'll probably get into more details next week about Steer, but they're, I believe they are preparing to launch right now.
So, very cool, very cool platform.
It's pretty much active, position management, automated.
Anyone can create their own strategy for UniV3.
Yeah, they gave us a demo.
We had a very productive call, and we're very excited to have them launch.
And another project is Staking, it's kind of like a wordplay, like Stay, S-T-A-Y, King.
They're a leveraged staking platform.
So, what is leveraged staking?
I, yeah, they could probably explain it better, so I won't even try.
But, yeah, they're a very qualified team from Korea.
I'm actually meeting them sometime this week to see where we can help.
Yeah, so, stay tuned for more information on staking.
And then, finally, Tashi, the borrow and lending protocol.
Christine, do you want to introduce Tashi and your team and the progress you guys have made so far?
Yeah, sorry, I had to get back to the right little screen here.
I'm Christine.
Lindsay's in here, too.
We're co-founders of Tashi.
I think we've been around for most of the people listening right now to have kind of an idea of what we're up to.
We're putting a borrow-end on Devmos.
We are super excited to be doing this, and we're getting really close to be able to launch.
We've got a lot going on, like we've said in the past couple weeks here.
We've got probably two to three weeks from now we'll be opening our Genesis pools, so that's exciting, with Edmos and Atom.
And then we'll be holding a token sale, and we should be launched in July at some point, if all goes well.
So we have a ton going on.
But really, like I said, I'm excited to hear about these other things getting off the ground.
We haven't had the chance really to be on these community calls yet.
So if there is people who would like more knowledge about what we're doing, I'm happy to keep talking.
But it's really valuable to me at this moment to hear what else is going on.
I had heard about staking before.
That's really cool.
I'm happy to be on a call that they're talking.
I'm happy to hear that Penguin's on the way because we're working with them.
So I think it's all just really interesting.
Yeah, I love the whole collaborative spirit.
Can you, I guess, clarify how you guys are working with Penguin?
Yeah, we'll be using them for our decks, I believe.
I know that there's the opportunity with Forge having all the native tokens, assets that are already on Edmos, like the Edmos, Atom, whatnot.
But between Wormhole and, well, this is where I'm getting into complications.
I didn't want to talk too much today.
We have a lot going on in our world.
But let's just say that Penguin is good friends with us.
And I think it's going to be really exciting to get to know everybody else in the community, too.
Yeah, absolutely.
And for those that don't know Penguin, they were one of the, you know, they were one of the leading deckses on Avalanche.
I believe it was actually started by the Avalanche Foundation.
I don't know if it's called Avalanche Foundation, but the equivalent of the Avalanche Foundation.
And it was handed off to the community, and now it's 100%, you know, community-governed.
So, yes, always good to see more community-governed protocols.
Yeah, if I can add to that, I think that it's really cool because it's kind of the same idea as Forge.
It's just been around for a little bit longer.
So those are the kind of relationships that we like to have, right?
Right.
So, yeah, I think all these, you know, cool thing about DeFi, and especially EVM, you know, solidity-based DeFi,
is that protocols can, you know, leverage each other and kind of build on top of each other.
I mentioned this before, but, you know, unlike other Cosmos dApp chains, since we are, like, a layer one,
yeah, a lot of interesting collaborations and, you know, cross, yeah, pretty much collaborations that are possible.
So, yeah, if we look at the Ethereum ecosystem, there's tons of protocols to just, like, trying to prop each other up instead of, you know, trying to fight for liquidity.
So, yeah, excited to see how everything will advance in the next few months.
There's a lot going on, like you said.
Super excited.
Super excited.
All right.
Is there, so, for Tashi, is there anything that the community or the governance workstream can do to help, I guess, with a successful launch?
I know we talked about this, like, in a call earlier, but for the community, I guess, to hear.
I think it's just going to be really important for not just the DAB, but the community itself to be involved, you know?
Like, we want to be, this is why we're on these kind of calls now.
We want to be more than just our platform.
We want to know what's important to people.
We want to know how to help create partnerships that extend beyond what's already in Edmos and promote, you know, decentralized collaborations between people.
We'd love to know, like, what kind of introductions people need to be able to move further in the space.
Like, it's not just about us.
For Tashi to be successful, of course, you know, you can, for all the people who are out there holding Edmos, it's a great use case to throw it in our pools and lend it out and, you know, experience what that's like.
And we'll help by teaching a lot.
Like, we plan on making, you know, you were talking earlier with Forge about good documentation.
That's something that we want to get a handle on, too, right from the beginning.
So, Lindsay and I have been working really hard on creating documents and, you know, getting them translated to be able to communicate really well with everybody about education.
And how we just want to really represent teaching in this space and not just about what we do, but hopefully we can collaborate with some of the other people in this call and say, hey, this is how, you know, Tashi can work with Forge.
This is how whoever can work and go beyond just, like, throwing a post out there, you know, because you scroll through all these posts on Twitter every day about how, like, oh, these two people collabed.
And you're like, great. And, you know, as a normal person, you might think, like, so, like, what does that mean for me?
So to be able to collaborate with the people in these calls and, you know, within these communities and actually take the time to not just document, but, you know, make it a little bit more personal and get on a spaces or create like a 20 second video and be like, hey, this is what we mean.
But we think that will really help, you know, and we can do that with the community, too, you know, answer questions that way.
We think things like that are going to be helpful in progressing the whole ecosystem because it allows more people to come in.
I'm going to ramble on for a second here because that's what I do.
But not being a native Cosmos or Edmos person, I find that if this is where you started, of course, it all makes sense.
But the barrier to entry has been kind of high if you're coming from somewhere else, like bridging and this and that.
And, like, what wallet do I need or where do I hold my tokens?
Like, what how do I use this with this?
And what does IBC mean?
Like a lot of that as an outsider kind of makes you think like, OK, maybe maybe I just won't.
So really working on being able to break down those barriers and make it easy for people to want to be in this space because of how welcoming and inviting and teaching we are is going to be a big focus for us.
Because once you're here, you can tell that the community is great, the sentiment is great, you know, but we need people to be able to see that and want to be here.
So that's something that Lindsay and I are really focused on.
Yeah, absolutely agree.
And that's why, yeah, I don't want to go too back into, you know, the past, but that's why I was so, I guess, trying to get the community support team work screen pass because one of their primary, you know, duties would have been to help and assist with all these educational material.
But, yeah, anyways, that's that.
And I totally agree.
And, you know, funny thing, I actually trained a custom chat GPT model on a bunch of like Forge and Uniswap, almost related documents.
Yes, it's been pretty interesting what, like, seeing what people ask.
We call it Forge GPT, but, yeah, you guys, you guys need to stop asking inappropriate stuff.
But, yeah, yeah, so it's like, it's been an experiment, I guess.
And, you know, since our work stream is very shorthanded, you know, might as well leverage AI where we can to help, I guess.
But, yeah, anyways, now we're getting off topic.
All right, moving on.
I want to give a quick update about hackathons and grants.
So, actually, right now, yeah, I'm currently in a hotel room for ETH Seoul.
So, ETHMOS is a silver sponsor, and Swan from the core team will be speaking at the ETH Seoul main stage in about 12 hours.
And if there is a live stream link available, I will provide that.
But, yeah, this is our first, I guess, entry into an ETH Seoul event, so it's exciting.
Unfortunately, our hackathon track was canceled because of some miscommunications.
But, in return, you know, DoraHacks hackathon got extended 14 days, so hopefully that makes up for it.
Yeah, and so far, DoraHacks, you know, I think started about three weeks ago.
We have 61 projects submitted and growing, and it's very encouraging to see projects that are actually leveraging, you know, EVM extensions or pre-compiles.
So, yeah, I'm excited to see what more projects are built out in the next few weeks.
And everyone's totally welcome to look at the projects that have been submitted so far.
It's just DoraHacks.io.
And then if you click on hackathons, you'll see ETHMOS.
And on the grants part, the ENCODE grants round, the deadline is coming soon.
It will be on June 4th.
And this is for the grants round number two.
And as a reminder, this grants program is community-funded.
And it is managed in conjunction with ENCODE Club.
So, definitely check that out.
And definitely get your applications in if you are looking for a grant.
Yeah, you can find more details on their Notion or their blog.
And lastly, we'll go over some Commonwealth discussions that have come up in the past week.
Jeremy, do you want to begin with the Proposal 92?
Yeah, so I posted on behalf of the ETHMOS DAO on Commonwealth.
It's linked in the comments here, addressing concerns with Prop 92, request return of funds.
I'd like people to take a look at that, get the discussion going to see if Prop 92 is meeting the milestones and obligations that Medtank is obligated to with that.
There were a few issues, and some of it might come down to misunderstandings as far as early payout of Milestone 1, where they seem to be under the impression that you get paid out to complete Milestone 1.
But then there were other things, like they persuaded the multi-sig to take a lot of the funds and put them in their personal accounts to stake them in order to try to negate some of the downward price action.
That's a huge security risk.
It was completely outside the scope of anything in the proposal.
And if they wanted to do that, I feel like there should have been another proposal for that.
Now we have staked assets, so in the future, others would be able to hold an STFMOS, for example.
You can see they released on May 29th an example website which shows their conversion platform.
Milestone 1 was the conversion platform and game development.
You can reference the PDF of the Medtank proposal on what they proposed to the community.
It is completely different.
They changed a lot of it without consulting the community.
They've been, it seems to be, from what I've seen, it seems that they're six months behind, four months behind at least.
There hasn't been much communication with them.
I'd spoke previously with one of the multi-sig holders asking if Medtank could put out updates.
And it was very delayed, very delayed for just brief Twitter posts that did not cause much of an update.
So I think briefly, that's a lot of the issues.
It's kind of a lot to go into.
They've posted a response on Commonwealth, and I'd really encourage everybody to just go and read it for yourself and see what you think.
So that's what I've got.
Hey, Luis, did you have anything to add?
Yeah.
Hello, I want to mention that.
I think it's not only, like, mistakes made from the Medtank side.
I think that we can also improve how the multi-sig handled the situation.
Maybe we could do, like, do's and don'ts as a multi-sig signer.
Like, stuff for the personal wallets or asking for updates, verifying addresses.
I don't know, like, suggestions in general whenever someone participates in a multi-sig of what they should and shouldn't do.
Because I think there's, like, some opportunities there to improve.
Yeah, definitely.
So personally, me coming from the Ethereum side, you know, we've, like, NOSSAFE has been used, you know, since for quite some time now.
And there's, like, a kind of, like, unspoken rule on how to effectively and safely manage, like, multi-sigs.
But I understand that, you know, for Cosmos, people that are coming from the Cosmos side, they might not be, you know, kind of familiar with, I guess, multi-sig etiquette.
I don't, is that the right word, etiquette?
Yeah, like, best practices, I guess.
Yeah, best practices, right.
So, on that aspect, I understand how mistakes could have been made.
And, yeah, as I mentioned in the post, I think this is a good learning opportunity.
And definitely think that, you know, a simple, like, guideline on how to, number one, create a strong multi-sig composition.
So, best security practices, you know, like you said, like, pretty much like the guideline would be beneficial, definitely.
And I'll try to work on that.
And to clarify, yeah, we're not, we're not trying to, we're not trying to, you know.
It's tough because we want to set a good example, a good precedent, but at the same time, we don't want to, you know, stunt a growth, the potential growth of a project.
But, so, in a way, there's a lot of room for interpretation here.
So, we would really like community feedback on their thoughts, be super helpful.
Yeah, I think definitely some guidelines for multi-sigs that would help maybe with some clarity.
And, yeah, yeah, there hasn't been a whole lot of discussion on that yet, where I hope we get some eyeballs on it from the greater community.
Yeah, it's, it could all be a bit of a misunderstanding.
But, yeah, we, we voted for this.
We wanted to see it built.
I voted for it.
But, yeah, personally, I've been a little disappointed in it.
But, yeah.
Is MetaTink in the audience by any chance?
I'm going to assume no, since no one raised their hand, right?
Yeah, we'll, we'll definitely try to get them in a call, maybe next week or next, next week.
I don't think this Commonwealth proposal is something that we should rush.
Because, like you said, it could be misunderstandings.
So, yeah, this Commonwealth post, from my understanding is, all the concerns raised, it's not necessarily, you know, us saying that they should be, like, removed, like, ASAP.
Hold on.
Dev, I'll invite you.
Dev, did you have anything to add?
Dev, yeah, the case from MetaTank 13, he wanted to speak, but he don't have mobile, so he can't speak.
Just wanted to speak.
I'm so sorry.
Your, your audio is kind of muffled.
I couldn't, I couldn't hear what you said.
Can you repeat that one more time?
Sorry, I couldn't hear.
Can you hear me now?
It's kind of, kind of, go for it.
Case from MetaTank team, he wanted to come on the state, but he is, he don't have mobile right now, so he can't join.
All right, cool, yeah, I guess I'll try to have them on next time.
Yeah, we're running short on time, so quickly get to the last two things I want to bring up, which is in the Commonwealth Discussions.
There's a pre-proposal thread for the ERC-20 asset registration of the meme token.
Yeah, personally, I don't, I'm not against it or for it, or, I'll be honest, I don't even know what the meme token is, but hopefully the community can chime in and give some insights, I guess.
And there's another proposal, or commonwealth thread, to register Zen token, the IBC token.
Personally, I've been watching Zen, because they were one of the first tokens on Forge, with a pretty impressive volume, considering, you know, none of it was incentivized.
Hold on, we have a request.
Yeah, so, the Zen token, I'm going to be honest, I don't think a lot of people understand what it is.
I still don't understand what it is, but I do know they have a big community in pretty much, you know, all the large EVMs.
So, yeah, I'm not, I don't see anything wrong as, I don't see any negatives to registering it as IBC token.
But, we do need to keep in mind that if it's an IBC token coming from EVMOS, if, yeah.
So, all IBC tokens coming from EVMOS will reflect the EVMOS chain, so hopefully, yeah.
This is something I wanted to ask about the token registrations.
Because, is there any risk for the chain to register, like, basically, tokens?
So, yes.
I see your situation.
So, there is a risk.
And that is why, you know, the core devs made the token registrations, you know, that's why they made it.
So, that it has to go through governance, so that there's due diligence on each asset.
Because I, don't quote me on this, but I believe there could be malicious, you know, malicious code that could be executed during registration or something.
Yeah, I'm not, I'm probably not the right person to ask, but there, yeah, there is a reason why they made it through real governance.
And I assume the risk isn't as high if it's already ERC-20 and then we use it as IBC or create an IBC representation, basically.
Because if it's already ERC-20, then I assume the risk is only on the image of EBMOS as, if there's a scam token that EBMOS actually kind of endures that IBC, right?
Right.
So, yeah.
I think it, the comments are, I don't know if you guys,
check the Commonwealth thread.
There's a bunch of newer, basically, spam on the Commonwealth thread just repeating the same message.
Oh, great project, but no username, no face associated with it.
So, that gives me pause.
It's definitely a very confusing project.
The more I try to learn about it, the more confused I get, but they are bringing, you know, a lot of volume and, you know, network activity and looking at their deployment on other chains.
It seems like, you know, they have a lot of following, so.
Yeah, real, real talk about that.
I've been trying to learn about them myself.
They have a telegram group for Zen.
It has roughly a little under 200 people in it.
And so, they were talking before they posted on Commonwealth.
They were talking about making a Commonwealth one.
And the people that do seem to be active in their telegram, they were encouraged to go and just voice their support that this is something that they want.
So, yeah, from the outside, it looks like, it looks like just a bunch of sock puppet accounts.
But I think they are actually active community members that are just all on the Zen side and nothing fired them up about governance until now, non-endorsement or anything of Zen.
But I think that those are actual, of most users, Zen community members.
Yeah, it's actually pretty vulnerable to know that.
Yeah, yeah.
There's an actual person behind all those folks.
Thank you, guys.
Yeah.
I'm not against Zen token.
In fact, I was the one that merged their pull request to be added on the Forge token list.
But, yeah, I guess ultimately the community needs to, you know, do their own due diligence and decide whether it is something that they want to see as an IBC token.
And I guess I will, so, MetaTank has joined the call.
I guess we'll end with, you know, I guess a statement or defense from MetaTank.
And, yeah, before we begin, I just want to mention that, you know, this was not like a personal attack.
We're just, the DAO was just trying to do the due diligence on, you know, the community pool spends.
So, I hope you didn't take it personally, but I do hope that you see why a lot of the community members were concerned.
But, yeah, you're, yeah, feel free to speak your mind.
All right, thanks.
I believe this is LPX token.
I hope everyone can hear me loud and clear.
Yeah, no, thank you.
This was, I think this was needed as well.
Even though it was a bit of a shock, there 100% are areas that we could have improved.
So, it's good that we're talking about this.
And, like Tilloplot said, I do believe some of those things were misunderstandings.
For example, with the thing with the early payout.
Seeing other proposals, I was also under the assumption that that first funding that you earn from the milestone one is what you use to kickstart development.
If that's not the case, please do correct me and direct me to examples where, you know, it's done properly.
As for the staking, so, once again, this was the first time we ever approached such a situation.
Because of this, I personally attended a community call.
So, I believe even in that call, Benny, Benny Lava from the DAO was there.
LPX, I don't know if you were in there, but Adonis and Kilo were there as well.
So, I was actually speaking to, they were hosting.
So, we actually came to the community first and proposed our plan.
And, I specified in that as well that the funds would be going to our multi-sig trustees, DevD, Kevin, and Delray.
None of those funds ever entered the account of any core member from Metatank.
And, like we said, during that community call as well, how I had looked at the situation initially was that I am the lead, I am in charge of this project.
And, I've requested certain funds and I've told the people that, you know what, it's my responsibility to get the job done and deliver what we need to.
So, seeing the way ETHMOS price token was moving, I thought the best idea is to try to minimize the risk of us running out of funding.
Because then, at the end, it would all be pointless if we don't even deliver a single product.
But now, we've had our conversations.
I do understand the risk and where it was all coming from.
Personally, it was just a decision to make as a leader.
And, I thought it was a risk worth taking because I didn't see DevD, Kevin, and Delray doing anything negative.
But, anyway, we have discussed the stake in and I do apologize.
But, once again, though, we approached the community first to bring this up.
Because this was the first time ever having to come across such a situation.
So, yes, on the delivery, we are late.
And, I do apologize for that, once again.
Although, I do believe this one, it has a bit of context, you know.
So, when we initially approached the community, you know, you can check on my account right now.
There's the video of, you can say our V1 conversion platform.
It was a rudimentary example.
So, that's what we had initially modeled our proposal around.
Creating a conversion platform.
And, in that case, in this old V1 version, it required, you know, connecting your wallet.
It required spending gas.
And, also, on top of that, when you do claim those tokens, those rewards, they are only directed towards the wallet that's connected to the app.
So, over time, we thought, you know what, we need to decrease frictions.
Make this easier for people.
If you think about the EVEMOS token, right now, it's not even traded on Binance or Coinbase, which are the biggest major exchanges that people have access to.
You know, very few people are into crypto.
And, remember, we're targeting people in the web to general public.
So, we wanted to make this as easiest as possible for them to operate and navigate.
So, that's exactly what we did.
And, now, you can use our platform.
It's working right now.
You can check on our Twitter profile.
You sign in, just how you sign in in any other game, you know, with your email or with your Gmail.
And, then, after that, you exchange those points that you've earned playing in your game.
And, instead of having to connect your wallet, you don't even have to connect your wallet for this one.
And, on top of that, you can redirect wherever you want these reward tokens to be sent to any wallet you choose.
And, all of that, without spending any gas.
You don't need to go out there and enter the ifmust discord to get faucet tokens or anything.
So, of course, doing something like that ended up also taking extra time, which is unfortunate.
But, then, I also, I would like to ask the community and to you guys, what would have been the better choice for us?
As in, deliver a product two months earlier, but it's not as user-friendly.
I'm going to speak up even if I'm not part of the doubt, but as a community member, Cass, and I think the only thing that was missing was more robust and continuous updates on the status of, hey, we're going to run late four months.
I think that's fine, but if there's not, like, enough communication, and remember, not everyone's going to be on a Twitter space or not everyone's going to check exactly one post.
So, it's on the, the wait is on the one that's receiving the phones, right, and communicating what's going on with the project continuously to show everyone's, like, on the same page, basically.
So, that's my two cents.
Yes, yes, indeed.
You can see even from my comments earlier, I, I haven't done some reflection.
I definitely do understand that the, the level of communication on our side, there's, there left a lot of room to improve.
100%, 100%.
What I did want to, to add, though, is that this all came as a, as a surprise and a shock, because you can imagine, during this whole time, from January into end of May,
it seems to me that there were, there seems to have been issues within, I don't know whether it's people in the doubt, or community members,
but we, we never received a single message or, or comments, whether it's in the, you know, government's chat, general chat,
personal private DMs, there's, there's, there's not a single person that said, hey, I have a problem with this, can we address it?
And, and instead, after we released our product late, we get this request to return the fundings.
You know, it's almost like, you know, imagine in the workspace, you're doing your job for X amount of months,
and then, all of a sudden, your boss says, all right, it's time to pack up and go.
There's, there's no PIP, you know, the performance improvement plan, where people discuss how to improve or anything.
Yeah.
I get, I get your point, but, but, but, but I mean, using your same analogy, it's like you're doing a job.
You say you're going to deliver X thing in one month, then, uh, you don't give any updates.
I'm not saying you didn't.
Hmm.
Yeah, no, so, I don't.
And then expect the, everyone to be happy that you're late for five months, you know?
It's, I, but I, I get your point, but I think it's, it's in the end, it's a communication issue.
Um, not, uh, and, and that effectively affects trust issues, right?
That's my opinion.
Um, it, it does, uh, Luiska, and, uh, I appreciate your responses, and once again, like, um, like, I know, especially coming from you, that this isn't a malicious attack or anything, and I'm not viewing it as such.
Um, everything has been, uh, reasonable and sensible, and for me now, it's sort of, how do we proceed forwards and, and, and move on?
Because, um, as you know, this project, we've, we've dedicated time, we've time and thought, um, making ideas, plans, scratching them away, going again, and it means a lot to us.
And we, we never went anywhere, we were always here, you could always message us and reach us out at any time, at any point.
There's no person we try to ignore or, or do anything against.
Um, and it's like, we, we wish to move forward, you know?
And how, how do we do that?
What, what is required for us to, to move forward?
And whether that means we're together or, or we're not, you know?
And I'm, I'm, I'm open to anything.
Whatever the, the will of the community, whatever the community feels about us, I will 100% accept it.
It's just, I hope we can, we can look at it and see whether or not this is something people still believe in, people still trust, people still see value in.
If not, that's perfectly fine as well.
But we, let's do our best and see how we can come to a conclusion and, and move on, basically.
Yeah, so, if you've seen the Commonwealth thread, um, you know, I did mention, you know, there's, you know, there's always delays.
There's always, you know, stuff in life that can come up, um, and things never go, like, perfectly according to plan.
Um, so, I've always wanted to give the benefit of the doubt.
Um, and like I said, in the thread, you know, ultimately we are rooting for you and, and that this is just a whole misunderstanding.
Um, so I guess moving forward, well, first of all, um, thanks for, uh, chiming in.
Um, I hope you don't mind, but I will be clipping this audio and posting it to the thread.
Um, so future, um, I guess people looking at the thread later on will have more context.
Um, I think that'll be super helpful.
Um, and ultimately it comes down to communication, right?
Like you said, um, slow progress is okay, but you just gotta be more transparent and, you know, just give constant updates.
And I think the community will be a lot more, you know, at ease rather than having, like, seeing, like, one tweet, like, every couple of months.
Um, like, we're not out to get you, you know.
Chris.
Yeah.
We want, we want to.
Would it be okay to reply?
Sorry, what was it?
Oh, I was, I was saying, I was sorry to interrupt you.
I was wondering whether it would be okay to reply or not.
Um, oh yeah, go for it.
Okay.
Um, yeah, no, I, I, I agree.
This old thing to me, it seemed it could have been easily avoided with, uh, with simple communication.
Um, so just, just, just a small thought that had, um, occurred in my head.
Like, you know, uh, communication to say it's a, it's a two way street, you know, and I, it, we were, we were not aware that some of these problems were, were brewing over these past months.
As, as I said previously, um, no one had approached us, not, not a single person.
Um, I, I do hope, and I, I wished if people had some issues with us, they could have approached us, and then we would have done our best to improve and make things better.
Um, it sort of feels like, with this old scenario, we just went from doing fine to the deep end, all in just one fell swoop.
There was, um, yeah, just like you said, um, little communication.
And if, if, if we had known, and we should, we should have done this as well, the, the level and consistency of updates of which, uh, community members or DAO members would have preferred to feel comfortable, then I promise you, we would have done that.
Um, but, but yes, uh, like you said, uh, communication definitely, and there's, there's still, this is all brand new.
How the proposal works, who's in charge of the treasury, how, um, projects that have been approved, how, how they should behave.
At everything, it's still brand new, and not everything is set in stone from the guidelines, frameworks, so on and so forth.
So, yes, like you said at the start, taking this as a learning point, and figuring out the best practices.
Um, no, thank you for giving me the platform.
Um, definitely, um, you know, there's improvements to be made on our side as well.
Um, so, yeah, um, Jeremy, did you have, uh, anything to add?
Yeah, real quick.
Um, yeah, no, I, I appreciate hearing your side.
Um, I, I haven't spoke with you directly since the proposition's passing, but there had been a few times where, um,
I'd had community members ask me about things, and so I had contacted some of the multi-sig guys, and, and I asked them for updates.
I, I asked them what was going on.
Um, and so, so when you have been, like, asked some updates, like, privately in your, your Discord chat, I think you have, um, that, that, some of that was requests that were coming from me requesting on behalf of other people to the multi-sig.
Um, and, and I know I had, I didn't realize early on about the staking thing.
I had expressed, um, and I think a couple other people expressed privately to the multi-sig that, hey, this isn't, this isn't how it's supposed to go.
Um, so that, that was very surprising for me to find out, um, a couple months after that had happened, and so there's a few things that, um, that appear to be red flags due to, and it could just be due to misunderstandings and, uh, and then just, uh, infrequent updates where, where a few things that, uh, aren't quite how it should be done.
Um, and then lack of communication, um, publicly can all kind of add up.
Um, I would, I would really like to see what you have for game development.
Um, that would be, I think that would be fantastic, or, you know, and I don't know what, what exactly you have for game development, if that's the only character design and stuff.
Um, are you pivoting completely away from the meta tank thing?
So it's, this is a completely different looking than what was publicly proposed.
Um, that, that's some of the things that I'd personally like to see as just a community member that voted yes for you.
And keep in mind that I'm pretty sure that your proposal is the largest approved spend that EVMOS has done on a individual project.
So, so, so, so with that, that, that, that's where I see the importance of it.
Uh, yeah, yes, yes, yes.
Um, I, I, I know, um, there must, there, there was this like, you know, miscommunication thing going on.
Um, when, in our private Discord, whenever DevD would mention to me, I, I had no idea that this request was coming from me on the community.
And, and I think it'll be best if I were to also join, I think maybe this was the Telegram group.
So I'm not in the Telegram group, um, but after this call, I will be in the Telegram group.
Um, yes.
And so let me see, what's the next thing you said afterwards?
So game development.
Yes.
So, um, as we had said, um, previously, I think by the time we had finished trying to sell off our tokens, we had received maybe just about under 34,000 US dollars.
And it, it took a lot from us to, to, what is it, to build this, this, this platform, even in just the time taken and everything.
So in terms of game development, we had just made plans and it was still, it was still, um, mobile games.
So hyper-casual games, more specifically, um, we're not, we're not moving to anything.
Although one change I will say is that, you know, currently our project, we're called Meta Tank.
And we think going forwards, you know, just having the name Meta in, in, in, in your, in your project, your name,
it's not the best way to, to go about things.
So you would see that in our test net, the token is called Raiden.
So that's where we're going to move on to next and then create what's called the Raiden universe.
And we've already started creating, um, lore for this universe to, to fit the, the game characters and everything.
Um, we've got pages upon pages and stories upon stories.
Um, but game development, like, as you see in the proposal, we have part one, part two, part three,
because there's a lot goes into developing.
You don't just, let's say, for example, create a character, you know, you have to first, um, do your research
and then create the idea.
What, what type of, uh, what type of game is it?
Is it like an, an endless hyper-casual game or is it a clicker?
Is it some, some sort of, um, mini micro RPG?
There's different, um, categories you can go for.
And then after that, you slowly progress to creating characters and then putting them to the, uh, the game engine and modeling.
So doing that in parts, you know, um, and yeah, I think, I think just, just to close off, uh,
I know we've been going on for too long and people are probably tired.
Uh, thank you for, for hearing us out.
I, and I am, uh, sorry to the community, especially those who are waiting for more frequent updates.
Um, it is something we have now found how important it is and going forwards, you know, we would be improving that.
Um, and yeah, we'll just, we'll just leave it up to the community to make the decision.
I do, I do hope it's something since, like you said to, uh, to the plot that this was the biggest spend as in on a singular project,
you know, uh, uh, 300,000 talk, um, even as tokens, um, I do hope we can continue to take this seriously and get to, uh, making our decision.
You know, I think on our side of my team members as well, uh, uh, what I don't want for them is to spend one month, two months in limbo,
confused of what's going on. I don't think it would be fair, especially after what, what we've all, um, put work and effort in, you know?
So when, when people are ready to say their thoughts, make their decisions, we'll, we'll sit here patiently and be happy to receive whatever final verdict is,
whether the trust is there or if it's gone, it's up to the community as it always has been.
But thank you.
Yeah, definitely. Uh, thank you for, you know, telling your side of the story. Um,
I, yeah, I mentioned this before, but I, I'm not too big of a fan of this going on chain. So, um, hopefully, um, everything will work out.
But like you said, it's up to the community. Um, but that being said, uh, we're running really late on time.
Um, so I think, uh, for this week, uh, we should wrap things up. If anyone has any last minute questions, concerns,
I'll give you five seconds.
All right. Well, thank you for, uh, attending, uh, June 1st, another month.
So thank you for attending the governance council council meeting.
And, uh, if anyone's in Seoul for, uh, all the events going on, feel free to let me know and we could meet up.
Uh, thank you. And, uh, I guess goodbye. See you next week.
Uh, thank you.
