Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Nero WaveHack program progress report
Recorded: June 19, 2025 Duration: 0:59:07Space Recording
Short Summary
In a recent AMA, Taka from Akindo and Marcus from Nero discussed the exciting developments in the crypto space, highlighting new project launches like SeedSafe, D-Pools, and Vidverse, while emphasizing the importance of long-term commitment among developers. The WaveHack event showcased a vibrant ecosystem with a bonus prize pool to encourage further innovation.
Full Transcription
Thank you. Thank you. Thank you. Hello, hello.
Hello, good morning, good evening, where everyone is.
I think we just started this space so we can wait a little bit to everyone join in. Thank you. Thank you. Okay, we're still waiting for people to join.
Maybe we can chat casually until everyone's ready and and uh starting the rma maybe yeah i think it's great
can you hear me well yes i can hear you marcus
great great great great oh by the way uh for, for those who are already on this MA, I'm Taka. I'll obviously explain my name, my background again later, but I'm head of BD at Akendo.
Yeah, and I'm Marcos. I'm head of the VRL Miro chain.
So I'm glad to join this space as well.
So really excited to talk a little bit about the projects we had there.
100%.
Where are you, Marcos?
I'm from Brazil. I'm based in Brazil right now.
Cool. Brazil. What time is it it there it's 10 a.m it's the
the reverse of japan so right right right yeah i'm now in tokyo 10 pm 10.05 actually yeah yeah
Yeah.
How is it talking right now?
It's actually super, super hot.
Melt and hot.
Super hot.
Yeah, super hot for a gin.
Yeah, and don't talk about hot with me.
Right, right, right.
Right, right, right.
100%.
100%.
Brazil is always hot.
Even when it's winter, it's always hot even when it's winter it's always hot so
there is no difference at all right yeah it's supposed to be like a raining a little more
i mean that's why in all the uh the the conferences conference in japanese conferences are
avoiding june because it's's famous as a rainy season.
It's probably going to run in
July, August,
and September.
That's interesting.
But it's the hottest there, though, right?
It's like peak heat in August.
Yeah.
Yeah.
That's right.
It's like whether it're taking the rain or
heat in this.
People normally take
the summer time because
then everyone can, of course,
come to Japan more
easily as the
halification is on.
Awesome.
While we're waiting, I think, why don't you tell us a little bit about your ECC plans, if yeah. Awesome. I think while we're, while we're waiting, I think, why don't you,
uh, tell us a little bit about your ECC plans if you can, uh, share. Oh yeah, right. Yeah. So
as an, I came to, uh, you know, the largest builders and platform we're, we're, uh, showcasing,
uh, we're, we're having the showcase event at ECC, their main venue that is a site event on July 2nd, and then
where the ecosystems showcase their projects, and then having VTOP VCs as judge, like in
the Spartan, DFG, Animoca, like those VCs are coming as a judge, and then the projects will
pitch their project for 10k price pool. And then the unique also unique point is is that the
wheel have a 3k prize pool for audience and then there are gonna 200 300 seats uh at our stage
so like even like 300 people all like you know vote into like in a one you know for the winner
then they can all get the ten dollars a list right so but
this is you know to have more quality audience and obviously we need uh the audience need to
register beforehand and then get approval from our side so yeah interesting yeah very very it's yeah but in a week and a half versa and we're in a two
weeks yeah yeah and then I heard like in a kind is also you know like warm we're
not warm well so we'll see I mean I'm sure it's like better than in Tokyo you
in Tokyo you know not humid as a year right are you guys going to ECC and not
know not humid as a here
this year at least for me I don't know I don't think so preparing for preparing
for Japan in you know July August so mm-hmm. Right.
You guys are joining all the conferences in the summertime? Yeah, yes.
In Japan?
So, WebEx and the FinTech Summit in Osaka as well.
So, we'll be gearing up for that.
Yeah, I'll be there as well, hopefully.
Oh, you'll be here?
Yeah.
That's going to be a long flight
44 hours no but that's wait but you have that's because you have to like get get from small town
to another bigger town yeah yeah yeah bigger town yeah the scales and the the the scales are also the longer ones, you know.
But I don't dislike it. I often enjoy these long flights.
It's not a big deal for me. But I can think better on bad flights on long flights so sleep and hopefully like room for the
laptop sometimes that's uh when the like seat in front of you like comes crashing back and you're
like oh my god this is my laptop almost cracked in half uh happened many times to me oh my god but that happens right like
you were using the the thing there and like yeah that happens that happened to me once but it's okay
It's okay.
Of course.
Yeah, should we get started?
Yeah, yeah.
Awesome.
That's great.
Yeah.
When do we can start?
Yeah.
So, okay.
So, hey, I mean, yeah.
And everyone, and welcome to this special AMA featuring Nero and Akindo.
Again, I'm Taka from Akindo, head of BD.
And for those of you here, Akindo is the builder activation platform behind WaveHack.
And today, we're super excited to talk about what's been happening in a narrow WaveHack,
some sound-out projects, and tips for builders who want to create with privacy or to pay muscles in mind.
builders who want to create with privacy or to pay master they might.
So let's dive in, but maybe first for those who may not be familiar yet with the narrow
chain, narrow team, could you give us a quick overview of what narrow is all about with
your guys introduction?
Sure, sure.
Yeah, I can give it a start. So thanks for hosting today. Yeah,
we're just kind of high level for what our ethos is at Nero is really giving the power back to
applications when it comes to especially how transactions are priced and how transactions are processed. So we built Nero because we saw this significant gap in flexibility for the amount of control
that applications have at the application layer with how transactions are priced.
So we essentially used a model that sort of activates proposer builder separation to like its fullest extent,
allowing for full policy control, pricing policy control governed by the applications and the
developers themselves. So what that means in practice is it allows for the applications
and the builders to set all of the gas policies that their own users will see.
So, you know, just from a high level philosophy point of view,
we think that, you know, when the applications bring the users,
they should be the ones controlling what the users see in terms of gas logic and gas policies.
This has been a huge sticking point, a pain point in
the industry. This is why killer dApps leave the protocols that they became killer on,
just because the incentives break down and it doesn't become obvious until there's real money
on the line later. So how we solved that is we decided,
okay, let's never let that happen on a protocol.
So we built this Paymaster API,
which is really what we wanted to focus on
during this hackathon.
So we really want the builders to kind of experiment
with the Paymaster, see kind of how their community would respond to this type of implementation, whether that's, you know, gas sponsorship
for a short period of time leading up to a progressive gas activation in their own token
to, you know, full, you know, full customization of gas logic from the beginning.
So, yeah, so for us, you know, again, just kind of circling back to the kind of core principles, we want
to make sure that when killer apps build on Nero's infrastructure, they are never motivated
to leave because the incentives were aligned out of the gate.
So, yeah, we've got some interesting stuff in the pipeline. We're going to extend
the Paymaster architecture to other chains in the future as well. But really for the purposes of
this hackathon, we wanted to really get a sense of how the builders are using this tech stack.
So I'm Jake, co-founder, CEO, and happy to. It really excites me to see all of the different
applications building and you'll see some of the numbers that we're hitting
when it comes to API integration so I'll pass it over to Marcos who's been much
closer to the much closer to the fire when it comes to the to the all the
questions and all of the interactions so uh thanks so much for joining us marcus
uh thanks for for the overall overview on the onero i'm glad to to hear that as well and like talk about fire uh the the the wave hack and the builders uh are being bringing a lot of cool ideas for for this one and the demos are there the the
the applications are really burning on the on the ecosystem and i'm really really glad to be closer
to the fire because i'm seeing those ones firsthand like shining and bringing a lot of cool stuff for Nero.
Yeah, I'm Marcus.
I'm the lead dev rel for Nero.
And yeah, I'm really excited to talk here today because my goal is to not only giving
some tips for the builders, but also highlight some projects and why they were successful on those waves.
And, of course, prepare you guys for the last wave.
Right, right, right. Thank you. Thank you, Jake and Marcus.
Yeah, let's dive into the current wave hack.
And then from a Kindle side, I need to ask,
But from a Kindle side, I need to ask,
how do you think the WaveHack,
I mean, there is a WaveHack doing, going?
It's been amazing.
It's been great.
We'll have to know your ideas.
Yeah, as I mentioned, I think the WaveHack, the whole event,
it's been very great.
It's been great in terms of the ideas that are being proposed,
the interactions that I'm having with the developers,
they are not only, some of them are not only interested in participating on a hackathon,
they are really interested in building for the long term.
That's what I feel the most pleasing to see in the whole event.
Like they are really getting to the heart, the build-a-thon term in a way. They are not only
interested in the short term delivering something, but they are also seeing the long term commitment.
That's so cool.
In terms of the ideas and the amount of the proposals,
it's been amazing.
That's great to hear that.
That's great.
Did you hear that, Jake?
Yes.
Yeah, of course.
No, I think it's been awesome.
You know, I think like when I see the reports of things, you know, coming out in different projects, it's like nothing excites, you know, excites me more than seeing, you know, what people are building.
It's just, yeah, it's super awesome.
And, you know, it's kind of letting your imagination run on, you know, the commercialization of some of these things and, you know, how the world would receive them when they're in their kind of mature form.
So yeah, it's my favorite thing is seeing these submissions come through
and getting to evaluate them with Marcus.
That's great.
And I mean, it's like I'm forcing you guys to compliment the the kinder but um
do you have anything do you have anything nice to say tell me more about my eyes
no but yeah i mean i just needed to say that uh we didn't like to talk about this but and i just
uh sort of this question randomly and then you two did a great job. Great, great.
And then, yeah, talking about the submissions and all those projects.
And then, yeah, I would love to know more about your perspective.
Maybe Marcus, who's near the fire.
Right.
And then what kind of projects or themes have stood out to you so far?
Yeah. Before highlighting some projects, I want to give a little step back and bring the short reasoning on why they were successful. And the main reason for that, it's just mentality in a way.
So if they, some of the projects I saw there, they were not experienced in Web3 or even beginning on AA stack and of course Nero, but they still, they
made success on the, on the, on the event.
And the success is mostly because they were, they have the will to commit to an idea for
months. And because they really understood what the build-atons are, and it should have
a different approach than standard hackathons. So on hackathons, you spend a week or a weekend building something, and
most of the cases, the idea dies out. But for the build-atons, it's an opportunity to
think and commit, make a proper plan, design the whole blueprint of your idea, and of course,
hear the feedbacks for the ones who are proposing and promoting the
the hackathon to improve and while i bring only three uh ideas to just highlight here uh there
were a lot of projects that got this idea in a way or another in the the way of the Waves.
But the reason they were successful
is this mentality shift from Hackathon to Butadron.
But for today, I want to highlight three
of my favorite applications that we had
in the Wave hack itself.
So bear with me with this.
Let's go.
I want to start, I really want to start with SeedSafe
because they really committed to the Buildathon idea
from the very beginning.
Like in the Ideatron phase, they don't just describe
the application technically, but they went further and further.
They made a strong pitch.
They researched market problems in the crop financing and carbon credit.
So, uh, doing that, they created a whole documentation page in a product level
that I could like pitch to any investor if I will.
Uh, in this documentation was present present at technical information, how they
planned to create the smart contracts, how they would be integrating each of these contracts
in the application, and more importantly, how they would use NeuroStack and why. Each persona
of their application, each actor of the applications was very well
designed. Why someone must pay gas and why someone not. That said, that creates in any software
development thing and software development case creates a strong base for any execution and the execution will be way easier and that's what happened they
did have delivered a cable demo in terms of integration use it almost all narrow features
and the demo is there is like it's live on on the testnet and in my opinion it's already
it's almost ready to go to the main net as well and use it by
their target target so i'm really excited to see what they will be bringing uh even further for the
from the event because they do they do uh uh they have the will to bring this to to going further
they have the will to bring this to going further from the event.
So that's why I wanted to start from the SeedSafe,
because they really start thinking this in a product level
instead of just a hackathon project in a way.
So that makes them mostly from the very beginning wave one, they are thinking about this, it's the
right approach for build atons. Secondly, I want to talk
about the pools, the pools, the application that brings
centralized and frictionless pools on neural chain, users can
vote and create pools there. So pools aims to reward the users for their time and feedbacks and also for make the users have fun there.
It's a very objective application, but it has insane potential in a lot of fields. can apply this for community management, or you can also apply this to, I don't know, even prefectures or even real world applications that needs a pool, a verifiable pool or rewards for,
answer just both so even though the the the application is seems like a simple one
the the the potential is like limitless in a way so and of course behind this was the
mentality of the developer i talked with him a lot of times and his mentality was like, I know I'm just starting my journey.
I might don't know a lot of things, so I will follow the feedbacks from heart and receive
with how I got.
And this mentality itself resulted into a very polished application, very well thought
to like, I made some pairs on the on the community to test it.
And they said he's great. He's doing he's going in the right direction.
It just needs to change this, this and that. And that's what he did.
He got the feedbacks to to the very heart, answered me a lot of questions to say, OK, this is right.
This is what you want to expect to Marcus.
And I say, yeah, let me test this.
And he was very close to be very talkative in the journey.
So the application itself in technical terms,
it uses the Nero wallet template.
So it comes with all the Nero features pre-configured.
So he built on top of this template.
It was like one of the suggestions we do on the documentation.
So he read the documentation.
So please read the documentation before going to the.
Very important.
Yeah, it will help you a lot to read the documentation.
So D-Pools is like itself, it's a strong user case in terms of applicability on Nero,
especially on the Paymaster features.
This also shines the amount of time we spend on the BuilderTone itself,
because the developer itself,
it had the necessary amount of time to figure out how it works.
And with a few more details,
then the application is a strong contender to go into mainnet soon.
So we also expect the application to go to the mainnet,
is the developer is already working on that.
I'm really excited to see this going live,
and especially for the users to be leveraging
its cool features to create
pools and be rewarded for that and have some fun.
I'm really excited for seeing that.
Lastly, it's my last application for today,
but not necessarily least.
I want to talk a little bit about Vidverse.
Vidverse is a decentralized frictionless video sharing
platform with the true creator ownership.
So users can watch videos, upload videos, share tips
for the video creators.
They can comment, make some...
It's a very cool translation of video platforms to the Web3,
and especially using the Nero features.
This application
came itself came a little bit after the waves, but started
when the waves started, but the developer itself, it's a very good one
and have a natural curiosity on everything going through that,
on what is going on under the hood.
So he quickly understood what Neiro offers.
And when he after successfully created an application, he started to cook more
through applications in the same time, like, uh, applying the same concepts,
technologies, like since he understood, okay, the a very natural and a very uh a very straightforward
developer thing okay since i know this now i can create more and more things and he also went
deeper in the in the technology and started exploring the subgraphs, which thinking on the build-out-down is a very unique thing.
So he actually explored our other possibilities that Nero has to offer,
not only the ones that we proposed for the builders to be exposed.
So he kind of figured out how best use Nero features to make it even seamless than just using the wallet itself.
Like he his application doesn't use the wallet at all.
They like he directly integrates with the API without even like having to apply their wallet.
So it's even seamless doing this way. And it's only possible,
like there's a lot of examples around this on the documentation. So again, it's a good practice to
read the documentation that is there. And the result for this was not only Vidverse being a very
polished application and a
strong demo, but the other two applications as well.
And he brought a third application for the Wave 6 that is around carbon credits.
So I'm really excited to see not only his applications grow in Nero, but the
developer itself, it's already seeing Nero has a long-term commitment.
So I'm really excited for that. And that's it. I think those three applications really
understood what build-atons and what the opportunity they have to explore this.
they have to explore this. But of course, there were a lot of other applications who follow the
same purpose, the same mentality out there. We have EasyStake there. We have Linkfolio as well
as one of these developer applications. So really, the Hackathon itself brought those ideas to life.
Those demos are there on the testnet as well.
Really cool to see those applications.
Great. Can you just in case,
share those three,
first you just share uh with
us again oh the links for the applications i don't know i mean just names here fine you know
for for other people who just need to join that guy you know while you're yeah the the three
applications were seed safe deeples and vidverse see safe de safety pool, vidverse.
Vidverse, right.
Like video, yeah.
Great, great, great.
And then surely those three projects and then another
project you mentioned are at a top candidate for the
nearest Wave Hack bonus pool as well, right?
Yeah, exactly.
Again, for the bonus pool uh of course those applications were the
the the one of the one of the top top projects for candidates for this bonus pool but there was
there are also another ones that took part on each wave uh for about on the event itself. So they are also great candidates to have a share of the bonus pool as well.
So, yeah.
And then also hearing from like what do you share with those projects details,
two things came up in my mind.
So the long term visioned building is important
in terms of as this is a more long-term building,
obviously, as a narrow existing project.
And then also the other one is the communication is a key.
Obviously, it's an obvious thing.
But again, Marcus pointed out this point,
maybe like especially in the
with the sea safe that the uh you know that guy was you know communicated super well and so that demarcus so you got you can also share your mind as a narrow project and then that is
leading the csa food building in a good way, I assume.
Yeah, I think you pointed a very important aspect of this,
like the clear and direct communication.
We want developers to win,
but developers should want to win too.
And the communication is key on this environment.
So when you produce something, when you create something,
you want people to see, you want people to use,
and there is no better way to communicate very, very good
communication around what you're building.
So don't underestimate how good a documentation,
a very well detailed documentation can be,
a very well demo can be polished at the interface in very details.
It's like the core principle on any field.
It's like you don't.
You has a developer i'm a developer myself as well, so some of that sometimes we can like be very.
introspective in a way that it's our style to do things like we want to program run to code, but the environment that ecosystem itself is more than this at the moment so documentation
and well explanation what you're doing is key for any kind of technical projects today so yeah
jake were you trying to say something i think uh just to echo something yeah marcus was saying is
I think just to echo something that Marcus was saying is, yeah, I think these days when attention is becoming more and more rare, through the feature set of what's been built can be more impactful than almost anything else.
And I think that just explaining it through the lens of the person who designed it
with a kind of front row view, like almost in the driver's seat with the people who are viewing,
I think it's a really, really powerful tool.
Whenever I'm trying to explain something to the dev team,
I'm like using a Loom link,
Loom video to just say,
can we move this over here or that over there?
I think it's kind of like,
somebody said this once and it stuck with me,
which is like, everyone's heard the expression expression like a picture is worth a thousand words well I think a demo is worth a thousand
pictures also so so just a quick like even if it's very not you know not polished not not
particularly you know produced I think just get expressing the idea in in full genuine form is is extremely powerful
these days more and more so so um yeah i would definitely encourage encourage that as well
that's great i mean the ceo is saying this way so it's off show right it's no
right and then yeah go ahead no no i'm just agreeing with you yeah yeah and then yeah as
i can both uh jay and margaret saying then yeah and then also for affordability and communication
is the key and then uh even for an after the mainnet release and then when it comes to the
you know the best adoption of becoming a more real business and then of course communication
with the market is the key as well so maybe uh building with the that communication heavy style
on a way to mainnet is also maybe helping you know uh the building the culture of the project itself
to be uh you know successful post uh mainnet as well. I think it's great.
And then also, yeah, now, so maybe we can also,
Marcus, you can also share the tips for further and a future builders as well.
Maybe for builders thinking about joining the last waves,
some of the foods you're working on or some of the tools you're already working on,
or some of the tools you're jumping on as a new builder?
Yeah, for sure.
I think for the builders who are participating
on the hackathon itself, who are already in,
it's time for the last push
and bringing all the last cool features and thinking about
going to the mainnet. It's my call for them, the ones who are already there, but for the
ones who are joining right now, it's still time. It's like, think of it as a very reduced version of the whole event.
You have enough time to think and propose new ideas.
It's totally welcome for us.
And building is the key, but as we were mentioning here in this call, a good proposal, a good communication is equally good as well. So my tips for all of those newly joining the last wave,
it's like, firstly, have fun,
because if you don't have fun on what you're doing,
it will be kind of boring and you're delivering something
that you don't even you will like it.
So first have fun.
But of course, technically technically speaking communicate your idea
uh in a clear way build around your idea and of course uh see how the the judgment
criterias we have in the in the in the wave like a demo is essential. No demos, unfortunately, it makes a disqualification,
but it's only a demo,
so I don't see this as a bigger hurdle.
And especially and most importantly,
the goal of this hackathon is integration with the paymaster so uh this is the the core principles for
for participating in any wave as well so yeah that would be like my core tips for the builders
but a special one as well is after you're building after you developing something
Well, it's after you building, after you developing something, test it like a user would do in your application.
So many builders, even experienced ones fail in this aspect, and that's okay.
Because in software development, it's kind of usual to have different teams to build and test it.
to have different teams to build and test it.
But in this kind of environment we are right now,
it's kind of key for you to at least test the basic stuff
that you are proposing in a view that is not
from the developer's view.
So if you have someone to test your application,
that's even better.
But if you don't just test the development, the deployed version of your application.
It like, for me has a, I'm in the software development for 10 years right now.
When I deploy something, I always go there and test my deployed version.
And I can say like 40% of the times
I found something that shouldn't be there.
So that's the importance of self-testing.
That I couldn't even give a better advice than this
because if someone happens to find the edge case, that's great.
But if someone happens to find an obvious case failing, that's what gets bad in the viewing of an evaluation.
So edge cases are great, but obvious cases are not.
So testing is my best my best of device,
not only for the event, but for life.
For life, 100%.
Yeah.
Yeah.
And then try an error.
Yeah.
Yeah.
Sometimes it's not even like a hard thing to do.
When we are building, especially for web development, different
browsers already is enough for breaking your application and maybe your evaluator are testing
in a different browser.
And then you get your hour, your work that could be avoided like two, three lines of code differently.
So testing is a good thing to do in any...
Trust me.
Yeah.
So the builders make your onboarding simple.
Think about how Paymuscle lets you remove friction and then test it.
If you have any questions, with marcus marcus yeah
in a good way yeah and like uh the builders who came to me and asked the most like any question
i i i would welcome to do it so and i will answer them the this is true because i can because
marcus is great at that this is true uh i would i would just yeah emphasize too like the you know
what marcus was saying about testing is you know this is um you know what we've built hasn't been
built before like this kind of you know applications if we just kind of zoom out, applications have always been told what the user has to pay for transactions and in what token. The protocols
have sort of throughout all of blockchain history has forced, you know, forced the applications
into their rule set. And so, you know, we're kind of exploring new territory here. And so that's where the, you know, the testing is extremely important and experimentation is important just because, you know, we'll be figuring this out sort of together and optimizing these things together.
One of the things that I always talk for the closest one to, that is interacting with me, not only on this event in Europe, but any other field that I'm helping is like, there is no obvious question.
Even for me, as I am experienced one, there are questions that I, that is like obvious for me, but, and especially when we are exploring new things, the whole Web3 environment is about exploring new things.
So there is no obvious question.
But I understand that there is a feeling on the developer side,
who feels that this question might be obvious.
I won't be questioning him.
I won't be expending his time with this.
But I go with the other hand and say,
hey, even if it's obvious, question me.
Because for me, it can be a matter of minutes to answer you.
But for you, it can be a matter of days locked
in a problem.
And even worse, it can be like direct to you to the wrong way.
So there you go.
Trading minutes for days.
That's the offer. That's the offer. And really, it's another tip that is not only for this event,
but for interacting with any protocol in any place.
It's like, ask questions, even if they sound obvious,
they might not be.
And I was in. are sound obvious they might not be. 100%. Right. And then
about regarding the tips and then so on, I thought like maybe Jayco, so you have something
maybe you want to share?
Yeah.
On the development side, it sounds like Marcus has covered most of it. But yeah, I do just want to share, I think something about our vision and intentions is really to have not a single type of incentive campaign on Nero,
but rather this kind of like progressive and gradual incentive campaign where
our goal is really to reward the most active applications on the chain.
So really align in the same way that the Paymaster design is aligned to have
way that the paymaster design is aligned to have mutual benefit to the applications and bring
revenues where appropriate to them. The same ethos was brought into our decision on how to
kind of distribute token incentive rewards as we progress. So, you know, just high level, we can just share that we will be, you know, the majority
of all incentive rewards will be going towards, you know, applications that are performing
certain tasks with their users, you know, namely, you know, getting them to interact
with your paymaster, getting them to spend your token as gas, you know, namely, you know, getting them to interact with your paymaster, getting
them to spend your token as gas, you know, bridging over your token to the network, these
types of things, like these kind of ongoing types of metrics are really what we will be,
you know, continuing to motivate.
We don't want to, we don't want, you know, sort of the kind of typical problem with the most,
that we're seeing with kind of most token incentive campaigns is the shortness of the effects
when you do kind of one singular event.
So our goal is really to have this kind of long-term, you know, save a lot of the bullets
for kind of longer- term alignment with applications that are
succeeding and really kind of support that flywheel of growth with the applications
and their user bases. So, Marcus, can maybe expand a little bit more if necessary,
or we can just leave it at that. I think that's a great overview on what we are planning.
Of course, there are different perspectives on this
that we are currently planning, and we want to push it.
The message is solo events like this short-term perspective is not what we
not what we are uh putting our efforts we are planning for the wrong run so all the builders
uh who are participating uh on the event itself or the builders who want to join and create new ideas will be always welcome
to join and we are preparing different possibilities for those builders to keep going,
keep evolving on our ecosystem. So yeah, I think that's pretty much what we are doing right now.
Great, great, great. And then yeah, that's great and then maybe also uh the the people here
want to ask some question about that or uh narrow uh web hack in general or narrow in general
would be great and then while like we wait for those questions coming up then and uh
i'm also uh interested you know uh what's like a what's
narrow's like a next move or is there anything we can you know have a we can get to know more
about like narrow's you know next action or maybe next collaboration partners because i've been seeing
a narrow partner up with a lot of a lot of a lot of uh companies services projects right
partner up with a lot of companies, services, projects, right?
Yeah. Yeah. I think I can take this one. Yeah. I mean, our goal is to continue to,
you know, partner with larger enterprises and, you know, bring real business on chain.
I think that's the benefit, you know, that's how, that's how everyone wins in this space is,
is, is really bringing, you know, bringing those who, you know, have those who have not made it yet on chain, giving
them a strong reason to be there, showing them how to interact with the killer application.
So the focus there starts with these enterprises that have massive audiences who, you know, are looking for an
angle into exploring Web3, but just haven't found it yet. So, you know, we'll continue to kind of
work with those enterprises, see what their pain points are, see if what we've built can, you know,
solve those problems. And just, yeah, just kind of continue to get feedback and build for this next generation
of applications and users.
So something that can be either fully abstracted from the gas perspective or customized that
fits in a way that fits the needs of their own particular profile of users.
So, yeah, that's really what we're looking at, you know, on the horizon, I guess, you
know, what we're kind of the businesses that we're targeting, you know, are kind of less
DeFi focused, I think, generally speaking, if I had to choose a lane and more, you know,
sort of retail focused, because I think that that's where the lowest
hanging fruit are in terms of a profile or a demographic of customer is people who haven't
had fun yet on chain or maybe intimidated by the complexities and the intricacies.
I think that right now, anyone who is dead set on learning
and understanding what DeFi is and how it works, all of that addressable market has already
kicked the tires on chain. Meanwhile, there's this whole other world of people who haven't really
made a first transaction on chain. Maybe they own crypto assets through a centralized exchange.
Maybe they're exposed to it.
They're kind of following along.
They're on Twitter reading things, but they don't have a web wallet.
They don't have a profile on chain.
They haven't really made that first leap in, and maybe they don't
fully understand. So that's where we think the market needs some help, need some help bridging
over to this side. So that's going to continue to be where we kind of focus our efforts on, on, on some of these partnerships and integrations.
Great, great, great. I mean, any, I don't know,
any additional from Marcus, if not,
I'll just go ahead, but just in case.
No, no, no. I think Jake covered that.
Yeah. Yeah. Yeah. He covered everything pretty much super well.
And I'm sure the builders, or even maybe I'm assuming not just builders,
but business-related people are on this space.
So it's a great impression to them as well.
So, yeah.
And then as this AMA, and like next action will be for to the builders submissions will reopen and start opening again from the 23rd of June.
And then most importantly, next wave is going to be the last wave with this theme.
And then also up to 5,000 in prizes plus 2,500, 2, that's a bonus prize poll as we as we share it so uh
maybe builders you know who haven't really uh started yet is like a great chance and if who's
already working on this narrow wave hack uh um you know you guys still have a chance to get that bonus prize pool so i mean yeah good luck
and then if there's any question uh marcus was always there you know to communicate so and then
maybe you guys better utilize that chance uh from like in a hearing what he just he shared with us
here so definitely recommend it and then you can find all the details on the WebHack portal.
Okay, those WebHack portal.
And then now the name is also changed from WebHack to Build us on on the tab.
So in the Build us on tab, you can find the Nero WebHack portal.
And also don't forget to join the narrow Discord,
if you haven't already.
That's also important.
And also follow a narrow account and also a kind account as well.
So yeah, I mean, we're super excited to see the final process, right?
Marcus, Jake, of course.
Yeah, I'm really excited for this final stretch, let's say.
And I'm really eager to see what they will be proposing at the end.
So I know some good projects are coming really strong for the last wave.
So yeah, it's always really exciting to see. As Jake mentioned, I'm closer to the
fire, so I saw everything on the first hand. So really excited to see it all.
Cool. And then Jake, do you have a last comment?
Yeah, just final thoughts. if you have any questions or
you know curious how to get involved or or anything yeah like as marcus said
save yourself any time uh that it might that you might uh have otherwise spent uh just yeah send
us a message and and we're pretty pretty quick to respond. So feel free to reach out.
Great, great.
Super communicative support people from Nero, Jake and Marcus.
And then also as an Akinda, we're always here.
If there's any system troubles, if there's any operational troubles,
feel free to reach out and then happy
to uh support and then uh also uh we uh as i mentioned in the beginning of this ama as an
i can they were having the ecc demo day so if if someone will be there uh please feel free to stop
by and it's gonna be a great event there so Yeah. Thanks again to the Nero team for partnering with us.
Then big thanks to all the builders who've already
submitted or are working hard behind the scenes.
We hope this webhackers is just beginning of
a long-term journey between builders and Nero.
Yeah. Let's keep pushing the boundaries of what's possible in the narrow depths. So
thank you everyone and then see you on Wavehack.
Thanks so much. Thank you so much. All right. Bye guys. Bye.
