Good morning, good afternoon, good evening.
I hope wherever you are you're having a good day.
We're going to get started in just one second.
And while you wait, just go ahead and give a quick share of this base
and let your timeline know that you'll be in here and encourage them to come join us.
We're going to talk ICP, ETH integration, we're going to talk hackathons within Coclub.
It's going to be a good time.
So go ahead and just give a quick re-share and we'll join you guys in just one second.
Alright, let's go ahead and get started.
I appreciate everyone joining us today.
I think we're in for a good time.
And just as a quick recap, so this is a multi-chain Monday space.
Multi-chain Mondays is when we talk all things related to multi-chain apps.
So this is specifically apps that integrate across multiple blockchains.
We're not talking about deploying a smart contract on chain A
and then deploying a smart contract on chain B.
We're talking about having a seamless user experience across all within a single app.
And so we love to just kind of go out there and see what's going on
throughout the crypto landscape.
Today we're going to be focused within Coclub, talking about ICP and ETH integration.
We're going to talk through some of the cool apps that they're seeing.
I'm hoping, so we should have, okay, good.
We have Ben Chai from DFINITY on.
Yeah, I'm very excited to have this multi-chain Mondays with you.
Awesome. Yeah, thanks for joining us.
We also have Emajie Park from ENCODE Club.
Emajie, how are you doing?
It's so great to talk with you again.
Yes, happy to see you again, and happy to see all the people who came here
to learn more about ICP, ETH integration, and also all details about the hackathon.
Awesome. Yeah, it's good stuff, good stuff.
And then we also have Clara Selin from ENCODE Club as well.
Clara, how are you doing?
Hi, I'm good. How are you?
So thanks for joining us all.
I know we've been picking up a lot of new community members.
A lot of people have been excited for ICP.
They may not realize exactly what's going on when we say ETH integration.
Ben, do you mind just kind of walking us through what exactly,
when we say ICP, ETH integration, what exactly do we mean?
Yeah, so when we say ICP, ETH integration, I think we mean three things in general.
So first of all, it's tokens integration.
So we have the CKEs and CKBTCs.
So obviously CKBTC is for ICPTC integration, but we have CKEs,
and we have a range of other token integrations that's coming, including.
We have the ICP on ETH, or ETHICP,
which we airdrop to a bunch of participants,
and that is bringing the ICP token to the EVM, to Ethereum mainnet,
and potentially to other EVM chains.
And so in that direction, the future work we're doing is that we are bringing
more ICRC-1 tokens to EVM chains,
and in the opposite direction, we're bringing ERC-20 tokens,
like USDC, USDT, and other ERC-20 tokens onto the IC.
So the first layer is bringing all the tokens together of these two ecosystems.
And then the second part is all IC, we have the ability to use threshold ECDSA signing
to generate valid EVM signatures.
And we can also use HTTPS outgores to directly interact with RPC nodes
so that we can not only query the state of all EVM chains,
but we can also broadcast the state.
So we can send a transaction and broadcast it onto any EVM network.
So that really allows the IC to act as a higher level or lower level,
depending on how you model it.
But ICP would act as a controlling identity of Ethereum identity.
So that's the chain integration part.
And then we are also looking at further running nodes potentially on the IC as well.
So yeah, that's what we talk about, ICPE integration.
That's really what we mean.
In the short span of like two minutes,
you brought up some pretty phenomenal use cases with,
one is taking ICRC, so ICP tokens,
and taking them to the Ethereum ecosystem.
You also mentioned this idea of using RPC service providers and HTTPS outcalls
so that you can, from an ICP app,
you could actually query the Ethereum state
and also sign transactions on Ethereum.
That sounds very familiar with our Bitcoin integration.
Are those two things pretty similar?
Yeah, those things are really similar,
but for the Bitcoin integration we did,
one extra step is actually not dependent on any external RPCs.
Now for Ethereum integration, we are still dependent on RPCs,
which is theoretically a decentralization risk
because we could theoretically receive false information from RPCs,
but then we can also query multiple RPCs to mitigate this risk.
So one of the things I'm fascinated with is the user experience, right?
So currently right now when you're jumping chains within crypto,
usually you have to leave the app you're working in,
go to, let's say, a decentralized exchange,
or go to a centralized exchange, do some sort of swap,
come back into the app you were using,
maybe have a wallet transaction where you're sending tokens out of the app
and then back into your wallet, back into your wallet,
all of that kind of stuff.
Are we moving towards a more seamless user experience with this integration?
I think it's not a feature of the integration itself,
but rather a feature of the IC.
If we look at apps built on the IC using IC technology,
for example, OpenShare, for example, OSE wallet,
they are completely unchanged,
so there's no external dependency.
And through the use of internet identity,
it's really a very smooth user experience
because the user doesn't have to leave the browser
and he doesn't need to install any apps in the browser.
And so users in the ICP ecosystem are really used to this model.
Yeah, because they've been working with this model for a long time,
they interact with dApps both using this model all the time.
But with ICP integration,
there is a very big opportunity, I would say,
for developers to bring this opportunity,
bring this experience also to the Ethereum ecosystem.
So Ethereum dApps could also use,
maybe not always indirectly,
but some wallet apps built on the IC using a similar user flow.
I would say that would be a very big step forward
towards mass adoption because it's really easy for users.
They don't have to deal with setting up MetaMask,
which they don't have to deal with.
Yeah, so they avoid this initial hurdle.
I used to joke with friends that
the time for a general guide,
so not having any crypto knowledge to learn to use MetaMask,
So if you compare that to Web2, that is a very big hurdle.
Although we in the crypto space, we don't really feel it.
But if we want mass adoption, that is critical.
That's such a good point.
And then one final question,
so with the RPC canister architecture,
is that limited just to the main chain of Ethereum
or does this include EVMs?
What's the scope of this integration?
So currently, it only interacts with the Ethereum mainnet,
but it's trivial to extend it to any other chain.
Because we're calling RPCs of different chains,
we basically just need to configure a different endpoint
and a different chain ID, and that will be everything.
That's awesome, and I look forward to a world
in which applications are talking to Bitcoin,
they're talking to any Ethereum chain,
and from the user's perspective,
you don't even really need to take care of that,
all that's going on in the background.
You just get a seamless user experience.
Let's turn the attention now to ENCODE Club,
and Emiji and Clara, I was wondering,
can you guys mind just giving a quick background
on what ENCODE Club is and what you guys do?
First, for those who met me for the first time,
I had a research and operations at ENCODE Club.
ENCODE Club is basically emerging tech education community.
We have been working with DFINITY for a long time,
onboarding a lot of new developers to the DFINITY ecosystem,
and also not only developers, anybody who is interested
in tech content, they can come and watch
while our main content are all around
developer-related content or ecosystem tech updates.
What we are doing mainly is either making
a public education where people can come
and learn about that ecosystem in depth,
which we have just an amazing education series
with the DFINITY team, so you might check it out.
Each expert comes to share about all those updates.
Not only how to say, if the integration is a really new one,
so it's not in our educate, but you can see the workshop
in the hackathon, but right before that,
so it means that really up to all the information
about DFINITY is in that educate series,
and then we are doing like a boot camp or hackathon,
which you can join and build something using this integration,
and then we are also running accelerators
to support early projects going to settle in that ecosystem.
And then in terms of within the zero to hero hackathon,
give us some feedback on what that is.
So first thing is, right before this hackathon,
as I just mentioned, we had an amazing education series
going through like a different bed and box
of the latest update in DFINITY,
one of the topic is, of course,
we cannot miss this, you know, CKBTC,
and then also like what Benzie mentioned about this HTTPS
all around, like you can learn there.
And this hackathon is all those audience who was,
you know, learning during an educate series
and maybe going through, you know, like a together,
some homework building and trying to interact with the canisters,
they can actually shine and show their skills.
But in this hackathon, it's not only like for advanced hackers,
we had like those people who started to building something
in DFINITY as a first time, so you can see multiple tracks
with the different workshops tailored to that.
And also, you know, just right after educate finished,
we had like an amazing announcement of like,
if the integration, so there's a special track for that.
So this hackathon is all about those developers
who are interested in, make hands dirty,
building something new can come,
and then get like the support from different engineers
and experts around to try different bits and bobs
and maybe building non-existing infrastructure.
There's a few apps, you know, you're of course looking for,
but you couldn't find, which means that this is a great time
you're the one who can be offered it.
And so you talked about the educational aspect of it
that kind of is a precursor to the hackathon.
Is there any additional resources or support
that gets provided to the developers as they're participating?
During the space, I will also leave some link in the reply
so that first, those educate series which finished,
we have all the recordings, so like you can watch all of them
and then we have a hackathon workshops.
But on the other hand, there's like all the partners,
you know, the mentors who are ready
and like answering your technical questions.
So one thing is, of course, you can watch workshops
and follow, but on the other hand,
you have like a different mentors get ready
to build something with you.
Most importantly, you can see Clara there.
So Clara is our program manager person, she can say hi.
So she's the one who are going to be holding your hands,
crossing the finish line.
Maybe she can introduce a little bit more about
what our program managers are doing.
I'm the program manager for the ICP series staff hackathon.
And just like Omri mentioned,
I'm kind of your go-to person throughout.
So if there's anything that you need,
whether that would be, you know,
you're confused about which track to go for,
you want to kind of bounce back and forth different ideas.
You don't know where to start.
Whatever it is that you need help with,
I'm kind of the person to get in contact with.
So you can reach out either we can connect here on Twitter,
which is obviously always nice.
But also if you register,
I will be sending you kind of all the onboarding information via email,
the email that you use to register
and invite you to join the Discord channel
where there's a bunch of information
and I'm always happy to jump on a call and chat more
and kind of build that relationship throughout the four weeks of the hackathon
to make sure that regardless of what level you're at
or how ambitious you want to be,
we can kind of help you fulfill that.
So that's my role in the hackathon.
And yeah, like Omri said,
we're more than happy to provide all the support needed.
It's really, really important for us.
It's probably a good opportunity to say,
make sure everyone listen and make sure you give each of the speakers a follow
so you can kind of stay up to date.
There's also the ENCO Club Twitter handle
right down there as a listener.
So go ahead and give that a follow as well.
You want to kind of keep up to date on the progress.
I know DFINITY and ENCO Club have a pretty good history
and so I'm sure this is only part of the journey of a longer relationship.
So make sure keep following ENCO Club as well.
Let's jump to probably my favorite aspect
and this can be for anyone to answer.
What are some of the use cases that you think will emerge from the hackathon
and are there any use cases that you hope to see come out?
So perhaps I can mention something more in general perspective
and maybe Benji if he has some idea
regarding something technically specific stuff.
For us, there are two aspects.
One is how people are going to be utilizing this BTS integration
and if the integration making some smooth experience for users.
One thing is of course we can imagine existing workflow can be connected
and people can use more easily.
But on the other hand, just because this is like a new integration
can it building specific app just like utilizing that fact
and make something interaction around.
It can be like a very wide idea.
If someone is like doing some multi-chain activities
people can create some games around
or people can make different services to helping users understand that
because wide integration make overflow much easier
still in terms of users maybe still quite confusing process
so someone need to make really really good onboarding process
and also it means that a lot of lucky if tools can be used
like a guest list using ICP infrastructure
so we are quite curious that among the all different types of bag
what can be the right products to utilize that fact
and how consumers going to be onboarded for that.
On the other hand, besides this integration still there's a lot of bits and box for tools
even for developers looking.
I was like the last time making homework looking for where I can track all the cycle uses
and then I can see that there was like a two or three different community projects
were working on it so we want to see more of that
developers contributing to the ecosystem building tools what we need
and perhaps this can make hackathon even better and better by time
because we will use those plugins made by hackers.
I love it. Building out that infrastructure is such a key component
and like you said there's ways to even monetize that
to make it more sustainable long run.
Ben, what are your thoughts on use cases?
Yeah, I think I'm in favor of having all those use cases built out
not only by members of our affinity but also by members of the community
I think that is a very important thing to have.
I think we now do have this awesome ICP page
maybe we can extend that to include some of the community projects
built during hackathons. I'm sure some of them are already included
but if we have like somewhere people could more easily find
what community members are building or maybe post on the forum
but post on the forum is not that easy to search for
so if we have somewhere where people can go and look for
cases built by both affinity and the community I think that would be great.
I love it and hopefully any developers out there listening
are getting interested and reaching out to learn more
or if you have an idea to build something innovative
to build something new make sure you're reaching out to get it started.
I'm kind of curious because I love this idea of people building apps
that tap into the Bitcoin communities, they tap into the Ethereum communities
as well as the liquidity between those two chains
that just seems like such a massive potential for our industry
and really again coming back to that user experience
where you can just do it all from a single app
that also hopefully everyone listening has been raised
or trained enough within our industry to think about security.
From an app perspective, what are the best practices for security
if you have a lot of money coming from Bitcoin to Ethereum
or Ethereum to Bitcoin or really even to ICP in that sense
what are some of the best practices developers should be practicing with their apps?
Yeah, I think that's a very good point.
People usually don't think about security when they're building apps
and this is what we see all the time because so many protocols get hacked.
So this question is really about multiple things.
So first of all, on the IC it's relatively easy to have a model
where the identity is well managed compared to Ethereum
because for Ethereum there's obviously the open Zeppelin
that is called open Zeppelin, something I forgot the name.
So they have a set of tools to help users provision contracts
and upgrade contracts and stuff like that and obviously manage identity.
But that is also a centralized solution.
Otherwise, people are just managing credentials themselves.
They tell people in the DAO, we have our DEV wallet
which is secured by the hardware ledger or something like that.
But that is not a very sound security model
because the DEV can still rug the whole DAO.
Compared to all the IC, even if you're building Ethereum applications,
if you have a canister that's on the IC that controls the private key
to an owner of a smart contract on Ethereum,
then this identity is first of all decentralized and then second of all it is secure.
And on the IC side, of course, you can take precautions to secure that canister
because whoever has a controller shipped to that canister
can theoretically use that private key.
But for example, if you have your main DAO that is on the IC, that would be really simple.
You can run an SNS or you can run any form of DAO on the IC.
So that is something to consider.
Second of all, the second layer to this question is when you are managing cross-chain assets.
That is also a very big problem because if you want to bring assets from, for example,
you want to bring your BTC onto Ethereum,
you think there are many solutions but if you're really looking to it,
there's not much available and especially for a DAO
because as a private user, you can always resort to using centralized exchanges.
You have to do KYC, you have to do all of that and trust the centralized exchanges obviously,
but then you can somehow manage that.
But if you want to do that completely on-chain,
in all of the published solutions that we see in crypto,
in the news, if you really try them out, they don't work.
And that is something that is also very interesting
because DAO is about decentralized organizations,
but it's also about decentralizing trust.
So if you have to end up trusting whoever the devs are
or whoever that is managing the few private keys of the organization,
then this model is theoretically broken.
Of course, you can have secondary measures.
For example, maybe they are sort of public or semi-profit on Twitter
and then you can trace them down.
But that is also, it's never 100% safe, so that is always a risk.
And yeah, that I think is the really, the superpower of the ICU
is for a DAO to be able to be 100% autonomous
and control 100% of its own assets.
Yeah, I do know within the Ethereum DAO world,
ICP has a bit of lore to it because of that ability to do 100% on-chain,
100% control of the assets to have zero gas fee voting,
having the ICP governance, having the ability to do following
so you can provide your vote to an expert kind of a thing.
All of that is really appealing.
There's actually, it's kind of funny,
there's a lot of DAO infrastructure built on ICP for Ethereum already.
Just we don't hear about it within the ICP community
because it's intended for Ethereum apps.
I wonder how much that will change with Ethereum integration
if a lot of the DAO tooling will come over.
So if you're a developer and you want to participate in the hackathon
or even just get involved in ICP,
DAO tooling is certainly an area that is worth exploring.
so if there is somebody who's interested in either participating in the hackathon
or even participating in the ENCODE education series,
what are the first steps they should do to reach out?
So first thing is check the comment section of this Twitter space.
I left the Educate series link,
which you can go and listen to previous amazing sessions
to get the latest updated internet computer.
And another thing is afterwards,
of course, you can join us in the hackathon
and then there you can see either workshops
or you can start to build something simple to try things out.
Depending on your level of knowledge of ICP ecosystem
because we know that some of our audience is like,
maybe native Ethereum developer who is trying out ICP stack
or who are the web2 developers.
This is first time going to a blockchain space
or someone who is like an OG ICP developer time to time
trying things out and already have been contributing to the ecosystem.
Also, depending on your level,
you can see there's different tracks to try things out.
And also, as Kyle and Benji mentioned,
there's some kind of complexity in certain things in this integration
But we have prepared a basic template
to say for beginners to try to play with.
So please don't give up even though it looked like something quite new to you.
And there's a lot of hackathon participants doing that
because they think that it's quite important to them
and they think that they must submit something amazing.
But actually, a lot of hackers,
it's much more meaningful that you actually accomplish
just one cycle of your project,
try to finish and submit something even though it's really, really mini projects.
And you can see that we have an even special track
for those who are starting new.
So that's something I'm going to leave the comments there again.
Let me just grab the link.
I will send it in the comments section.
And here is the hackathon.
And then, of course, what I recommend is please schedule a call with a Clara.
If it's your first time to join the hackathon,
you don't know what to do, you're still looking for the team.
Or if you're an advanced hacker but you want to bounce your idea,
we are very, very excited to hear anything about your ideas
or what kind of things you want to build further.
If you really have some project, let's say, in different ecosystems
and then you wanted to connect,
and you were trying something with the best kind,
you were trying something with Ethereum,
and now you want to utilize ICP infrastructure
to make a more efficient, lucky workflow,
then this is a great time to talk to us
so that we can connect to the right people
and we can support you building further.
Yeah, that's such a great point that building an app
is not just all about learning what's the programming language
or what's the platform like to deploy,
but rather actually getting connected within the ecosystem,
maybe learning from other developers,
maybe talking with other teams to figure out
how your apps can have compostability between the two
I was doing Zen Club Club kind of focused on building those relationships
between their partners and participants?
Within our community, especially people going through
all these education initiatives together,
you can see that they're building those funding,
and even like we see several hackathon members,
and maybe they're going even different conferences together.
Perhaps a good example is actually myself,
so my initial background is I'm a mechanical engineer
The way I get into the workplace space is,
I was interested in watching things here and there,
and then I started to take some bounty,
and then I was bold enough to get some stuff, you know?
And I knew that I'm not perfect as someone who,
I don't know, studied in cryptography
or studied about computer science long.
There's definitely something I could contribute,
and I also wanted to try out.
And surprisingly, same in ICP hackathon as well.
You think that there are going to be a thousand hackers,
they will not remember me.
Everyone who joined our sessions and submitting something,
you will be surprised at how many time judges
and each ecosystem developer is going to remember
And sometimes, they will just even know when you come back,
oh, that is the person who last time built,
I don't know, that man switched,
and now they come back with something new.
And all those things rolled out.
So my case is the same thing,
that I was casually hanging around,
trying to contribute to the ecosystem,
and then I got started to get in touch with protocols more,
and even I joined Inkout Club,
as I was one of the consumers of the Inkout Educate series,
as I wanted to learn more about protocols.
So I can see more people coming through
like a different education base for making the team,
and some of them actually become startups as well,
and now they keep working on their startup journey.
So what I would say is, depending on what is your goal,
which even doesn't need to be defined,
it can be changed on the way.
But here's the nice place that you can learn with someone.
So they're like, you know, you can exchange knowledge,
or sometimes when you get just lazy,
you're still going to tune in,
because you have a group chat with your teammates
to build something together,
and then you can build your portfolio,
and be looking for new opportunities in Route 3.
Who knows that you're going to be working at DFINITY
or you're going to have amazing startups,
or just if you become coolest hobby,
so that you can brag to your friends
that I won't hack a ton several times.
So yes, there's a lot of opportunity there,
and community is behind it.
That's such a good way to say everything,
and I love that the idea of,
hey, just put yourself out there.
There's a lot of good that can come from it,
and even if you're on a track to start off with,
you don't have to have a clear, exact vision.
I think one of the great things about what your story was,
Amji, was just that Web 3,
I shouldn't say at this point,
maybe people are starting their careers in Web 3,
but most of us have fallen into Web 3
and that's one of the beauties of the space,
is your career or even your life
can just take unexpected turns,
and you can take different paths
depending on where you're at.
Since we have all three of you on stage here,
I'd love to get your thoughts,
even just thinking outside ICP,
thinking more about broader crypto ecosystem
and this whole cross-chain narrative.
Are there specific storylines or specific visions
that you're hoping will take place,
or that you think will be big storylines
for the coming years related to cross-chain?
2024 is going to be a quite fun year,
definitely with the cross-chain
and also a deniable topic, which is AI.
There are going to be a lot of overlapping spaces
I'm expecting that something is going to happen,
and I'm really looking for is gaming.
There's a lot of things that have been tried
there's no really epic success for one yet.
Either something was really popular
or something really popular
with maybe different dynamics,
which is more near to the D5,
but we didn't really have a game per se,
but which we're going to see perhaps more in 2024,
even utilizing cross-chain infrastructure,
it was quite difficult to pull out.
Either if they're on Ethereum,
it's too expensive to play,
then it becomes pure NFT economics
because all the things were happening off-chain.
But then, when you're building outside of Ethereum,
of course everyone's a little bit suffering
from getting users or getting liquidity into that game.
So now I think we're going to see
the cross-chain infrastructure,
perhaps there are going to be some game people are going to be playing
I think that's the whole game about,
you shouldn't have a proper reason why I'm playing the game.
You're applying because that's fun.
And I think we're going to see that
because infrastructure is ready to do
and making some fun activity,
it can create new types of interactions.
So that's my personal wish
because I really like to play games.
perhaps a cross-chain means that
either it can give us different types of cash in terms of security
or how to utilize things.
So we will see some infrastructure related topics forming up.
While it means, I believe,
we're going to need new types of talent coming in from web 2 to web 3
because there's web-renative developers
or researchers who are focusing on blockchain only.
But I believe we're going to need a lot of infrastructure engineers
and researchers who have their background in web 2
So that one is going to be quite interesting to see in 2024.
So cross-chain infrastructure plus game,
which is pretty much my biased personal wish.
Clara or Ben, anything to add?
I think the future of blockchain is
everything will be cross-chain.
If you look at the path of development of web 2,
people started out hosting things on their own servers
and then data centers and then AWS and Google Cloud.
But if you look at the infrastructure of the dev,
do you as a user know or care what infrastructure that dev is using?
Not that the application, the web 2 application is using.
Because it's the least important for you.
What you are looking for in using an application
is because you like the features provided by that application.
In crypto, we're not at this stage yet, but it will be.
So whether you're playing a game
or you're using some other application
like social application or even DeFi application,
you don't even need to care what assets,
where on which chain your assets are.
You don't even need to care
on which chain the transactions are executed on.
All you need to know is you're using this dev
because you want to use the features of this dev
and all the rest are technical details.
I think we are entering this world
with all the layer 2s, Ethereum and ICP
with the ability to integrate with all the chains.
I think this is becoming a reality.
Of course, there are still hurdles to hop through.
The most apparent one is user-friendliness,
like the level of optimization of devs on web 2
and web 2 are completely in different leagues.
But I think we're slowly getting there.
And with the number of chains that are available today,
this would almost certainly be the case.
Of course, out of these chains,
there will be winners and losers.
Some of them people will forget
or most of them people will forget,
but some of them with their distinct features
would stand out in this game of player ones.
But I think the future is all that would be cross-chain.
I've never used a website and thought,
oh, I don't want to use this because it's hosted on AWS
and I prefer my websites hosted on Google Cloud.
So absolutely, the back-end doesn't matter.
Or the infrastructure doesn't matter.
Users just want a phenomenal user experience.
Clara, I saw you come off mute.
Did you want to add to the hopes for the future?
So it's actually funny that it kind of naturally ended up
gearing towards what I was going to say anyway,
But yeah, my kind of addition would be just that
I'm hoping to see kind of more UX UI improvement
with cross-chain functionality
and seeing kind of the signs of mass adoption there.
And I think it's a super, super important aspect
which you all mentioned before
that that's what users actually care about,
is what they see and not the kind of which chain
is it hosted on or the back-end details.
So yeah, I just simply agree.
Basically, that's all I had to add.
Well, we're coming up to the end of our time here.
Is there any closing thoughts?
Is there any topics we didn't touch on
that you guys wanted to touch on,
or if not, any closing thoughts to wrap up on?
I just want to say, again,
like thank you everyone for joining
and taking the time out of your day.
But also, if anyone is interested in joining the hackathon,
or just in general to kind of connect
and be on the journey with you guys in the ICP ecosystem,
but also just in Web3 in general.
We're always happy to chat
whichever level you're at or what your background is.
You're more than welcome.
So it can be super intimidating,
especially if it's, you know,
if you feel like you're a beginner
and you don't really know what's going on,
please don't be too intimidated
So that's kind of my main closing statement, I'd say.
Yeah, I can absolutely echo that.
Like, please don't feel intimidated.
Like, that's the old, like, go-to side things
of every hackathon when I need to talk to hackers.
First, like, don't hesitate to join.
But second thing is don't hesitate to stop
Of course, like, if you need different types
of, like, a barrier, you need to get over
because, like, most of engineers, I myself, same thing.
I heard this from professors a lot.
Like, engineers are always over-engineering
and, like, not satisfied with your project
because you're always, like, shooting too high to deliver.
So, like, in the hackathon easily,
it happens that you want you to build,
like, really, like, nice, smooth app,
but then, in the limited time, you need to focus
on, like, something very specific.
As, don't forget, all the things you're trying out
So then, like, there's no time to learn everything
and building something too fancy.
Sometimes you might be spending time on, like,
even reporting something slightly wrong
in the documentation or something might be even confusing.
That's the whole process.
And if you see those more and more,
it means that you're actually really early in this stage
and you're an early contributor to the ecosystem.
And don't hesitate to give us all those feedback.
If you don't understand certain workshop or documentation,
perhaps, like, you know, your perspective
is going to help us to improving things.
Or, like, literally, you will be the one
who just contributed to the updating article, you know?
And then another thing is, like,
in terms of, like, building things in the hackathon,
you don't need to be, like, a most lucky Nobel person.
So if you are not sure, like, what to build,
try to just look around, like, what kind of things
people are building in different ecosystems
and try to press tweak a little bit,
like, what kind of things I can tweak
or, like, what kind of innovation I should be,
why people are not using that that much,
what kind of thing I can change, I can absolutely better than them.
Or just even for practice, try to tweak it a little bit
and just build it for fun.
You don't need to make it as a company.
You want you to try things out.
You want you to try new tools.
So maybe this time you want to use, you know, like,
integration, making even to-do is, like,
it can be really, really silly project.
It doesn't need to be something, like, amazing.
You can say that, oh, can I make a to-do is that,
I don't know, my to-do is going to be minted on Ethereum
But it's a really fun project, and you want to build it,
and maybe this functionality can be used
for something much more complex afterwards.
So for, like, a long story short,
please, like, don't be scared to jumping into the space
and be, like, don't need to get pressure to build
something amazing at first place.
It can be extremely silly, and sometimes you will be surprised
at how the silly project can be something amazing,
very, very innovative in the future.
Well said, well said. Thank you so much.
Ben, anything you want to end on?
Oh, I think everything is well said.
I just want to echo that I always reuse code
from my silly projects, so, yeah, absolutely,
don't be afraid and just build something.
That is such a good note to end on.
Ladies and gentlemen, this has been another
I hope you'll see us same time next week.
I think we're talking ordinals,
and pretty much a team from ENCODE Club.
Really appreciate you guys making time.
Ben, I appreciate you making time as well,
and, again, everyone give them a follow
and keep up to date on as things develop across the board.
Get back to building, and see you all next week.