Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Win 100k: Istanbul Hackathon AMA 🇹🇷
Recorded: Nov. 3, 2023 Duration: 0:54:28Space Recording
Full Transcription
So, yeah.
Yeah.
I mean, we love your project, obviously, and just the mission of bringing education, doing
it in a decentralized way.
I think there's a lot to love about that, and great.
So, you guys are also going to be a judge of the hackathon.
Guys, before we move on to our last introduction, I just want to direct your attention to the
pinned tweet in the space right now.
This is a link to a Luma page.
You can click on the link and you won't be kicked out of the space, don't worry.
This is basically the registration page.
So, all the details we're going to be talking about today, including the dates, when is the hackathon,
how much are the bounties, and what are the tracks, right?
The tracks are really important too.
All that information is going to be there for you on Luma, including links to GitHub and
stuff like that as well.
So, we're still accepting registrations, guys.
So, feel free to register literally as we're talking right now because there's not many days
left, right?
It's literally like one week away.
So, if you want to fight for this 100k prize pool, now is your time to activate.
So, until then, let's go ahead now to DoraHacks.
Thanks for waiting until the end here for your introduction.
And hello.
Hello.
Thank you for having me today.
Hi, guys.
This is Chris from DoraHacks.
I'm with DoraHacks BDM Venture Team.
And for DoraHacks, we are leading global developer incentive platform.
And what does that mean is that we basically provide the infrastructure for hosting virtual
hackathons, grants programs, bounties, public goods taking, and developer funding in general.
We were founded in 2014, and we started to work with BNB Chain since 2019 in Beijing.
And after that, BNB Chain has always been one of our top partners in the ecosystems.
I believe we have done nearly 10 hackathons already before.
We are also a Binance Labs portfolio.
And we have contributed some, like, very important infra for BNB Chain, including but not limited
to BNB Chain native quadratic funding, smart contract, BNB Chain native Macy, which is a
minimum anti-conclusion infrastructure, and basically support the best BNB Chain ecosystem builders
and early-stage teams in general.
So I think it's definitely a very exciting time for us to work with BNB Chain for another hackathon in Istanbul.
And we are such an honor to support this hackathon as a submission platform portal and also be a sponsor for the hackathon.
So yeah, appreciate everyone having us to join us for the hackathon.
And we are super excited to meet and find out all of the best BNB Chain merging teams and builders through this hackathon.
Awesome.
Yeah, obviously, you guys are complete veterans of hackathons.
Tons of experience that you're going to bring that's going to help and support all the people entering into this really exciting hackathon next week.
So, so happy to have you, Dora Hacks.
Looking forward to hearing a bit more of your perspective later on.
Okay, guys, so we've met all of the sponsors and the judges of the hackathon.
Now it's time to find out a little bit more about the event itself, what they're looking for, and how it's all going to go down.
Let me just say really quickly first, guys, if you're in the audience and you're listening, if you could do me a big favor,
go ahead and follow all of the projects who have the speaker tag at the top of the space here.
We want to make sure that not only are we bringing attention to you guys, the entries, but also the amazing work that they do in our ecosystem as well.
They're taking time out of their busy Fridays to chat with us.
So go ahead, hit the follow button, make sure to check out some of their content, interact with their projects if it's something that you're interested in.
And I think that's a great way to bring value to everyone involved in this situation right now.
Okay, so I want to get into this specific question.
I'm going to go to Space ID first on this one.
We really want to know, like, why do you think devs or projects should attend the hack?
And what's the benefit for them?
And if you could sort of like maybe let me know just a little twist on this question that we wrote down beforehand.
Like, what is it like at a hackathon like this?
Because like for me, I'm a social media manager, right?
So I'm not a hacker.
I've never been in a hackathon.
So, like, how would you describe hackathons?
And then why do you think that people should take part of it?
Yeah, of course.
Of course. Good question.
Well, I mean, first, first reason, obviously, there's a pretty significant price pool offered there, right?
But also like the quality of sponsor, I think for this hackathon is just like really good.
And you get to meet people working for these projects.
So it's good to make connections, but not only necessarily with the sponsors, but also with the team that you're going to be building on and with the interaction that you're going to have with the other teams as well.
And like before the hackathon actually starts, there's always plenty of opportunities to go and network with other people, especially if you don't have your team yet.
But even if you found your team, it's just great to talk to other builders like in the space.
I also think it's just like a great way to add a twist on your resume, right?
People love seeing that you have that kind of experience to go in.
And especially for people that might not already have like Web3 experience in terms of like working for a Web3 company.
It's very hard when you hire to find people with that kind of experience.
But anytime that you just add a little thing where you participate in the hackathon, sometimes it's just what it takes to finally go over the next steps like in into getting like an interview.
Also, I think it could lead you to building a new startup, right?
Who knows, again, as we've mentioned space that he was a hackathon project before and look where it is now.
I think it can be like a really good opportunity for this.
And it's just like taking taking a risk, right?
Taking some of your time to go and build is just good for your own like personal growth.
And for having been on the judging side of the hackathon, you were asking like, what's what's it like over there?
There's a lot of energy going like before you can feel the the sort of like tension, but you can mostly feel just the the energy like people are eager to start.
And then once it starts, just people are just full on concentrated light.
There's a lot of Red Bulls and energy drinks going around to just like go through all this.
And sometimes you'll see teams just working nonstop for like 48 hours and being on a judging panel.
Sometimes there's like events during the nights and you go there and you'll see some of the hackathon teams go also to the events just to take like a little break.
And it's also fun to see that and get to talk to them about like what they've been currently building.
Great. I think you painted a really cool picture there, like not only of all the benefits to builders, but what it's actually like at a hackathon as well.
Yeah, I agree. There's probably a lot of a lot of Red Bull in that situation.
Sounds pretty intense, but also pretty fun as well.
So let's see what Polly Hedger thinks about that same question.
Like, it's okay if, you know, you repeat some of the things that are going to be said, because I'm sure a lot of you guys have similar ideas.
But in your view, what are the good reasons why devs or projects, you know, should attend the hack or sign up?
And then maybe on the personal side, like, how would you describe a hackathon to someone that's never been before?
Yeah, sure. I'll try to pivot from a different point of view, a little more technical on my side.
So what we are expecting is that, of course, the 100,000 USDT rewards, that's going to be something for new projects.
And besides, we are offering some fantastic tasks.
I have seen the tasks that I cannot really disclose right now.
But what we would like to do is that we would like to invite real hackers joining our team based on the performance.
There is a chance that after completing the task, you do have the chance to join Polyhedra or ZK Bridge team,
because we are offering some tasks that are closely related to our production-level products,
and they can become part of our production-level products once they are finished.
Also, because we are offering several chats on different tasks,
you have different ways to implement what ZK Bridge provides, what Polyhedra provides.
And upon implementing that, we are very interested in inviting our hackers,
actually try to get a taste of how it feels working with Polyhedra team,
how it feels to become part of the Polyhedra team.
So I think that's something we are looking for,
and there are some traits we are looking for from hackers who can really build on ZK Bridge
and expand the influence of ZK Bridge.
And plus, we're picturing what it's going to be like in the hackathon,
because it reminds me of the old good school days when I also attended several hacks,
quite a lot of hackathons when I was still in college.
So we would love to talk to our hackers to provide the best support on site.
We are going to open some exclusive endpoints and APIs that's only for the hackathon,
that you can get a real taste of the power of ZK Bridge and the power of the zero-knowledge-proof
based interoperability provided by Polyhedra team.
I think that's going to be some most advanced experience,
but probably won't get able to try in other hackathons that's exclusive to this
Binance Blockchain Week hackathon only.
So I'm really looking forward to it.
I'm really looking forward to see if there will be any applications building on the interfaces we provide.
Okay, wow, that sounds really exciting.
I mean, I'm not even a hacker and that got me hyped up a little bit.
Sounds like some really cool stuff with Polyhedra and ZK Bridge
that's going to be available just for people at the hackathon, right?
So just another reminder, guys, if you're listening in the audience,
if you'd like to attend, please do go to the pinned tweet in the top of the space here.
You can go ahead and register 100K in bounty prizes up for grabs for exceptional projects.
Let's go over now to Open Campus.
Your opinion on this? How do you see this?
What's the main reason why someone should attend a hack like this?
And do you have any sort of thoughts on what the hackathon environment is like
or maybe some fun stories from past hackathons you've worked on?
Yeah, I think everyone did such a good job already.
I think for hackathon, I think it's just an opportunity to build something new and fun.
Maybe an idea that you always had in the back of your mind
or just something new that you dreamed up of over the weekend.
I think that is always a really fun experience to just, you know, to be able to just, you know, go crazy about an idea.
And with some of the friends or, you know, if you're ready to have a team, you know, build something with friends or, you know,
just to build something with someone random from a completely different perspective.
And I think, you know, one of the biggest thing you can get out of the hackathon other than, you know, obviously the job that we just mentioned and also the big cash prize is also kind of just a learning experience really.
You know, you have a wealth of experience and knowledge, not just from this particular panel from the sponsors and from, from finance itself, but also, you know, your fellow, your fellow hackers and the participants, you know, everyone's coming from a different kind of space or have their own experience and knowledge.
And it's just a really fun time to, a fun way to learn from other people in this space, you know, a bunch of like-minded enthusiasts.
And so, yeah, you know, it's going to be really intense.
You know, everyone, I think it's going to be working flat out and partying very hard at the end of it, but, you know, I guarantee it's going to be a great experience and you're going to have a, you're going to learn a lot, a lot out of it.
So, so yeah, so I think, I think that's, that's why you should, you should join the hackathon.
Okay. Yeah. I didn't, I didn't know that there was like partying hard at the end of the hackathon, but it's probably worth it. Right. After all that hard work. So that's cool to hear. I think that sounds pretty fun.
Okay. So for Dora Hacks, let me switch up the question a little bit, because I think we kind of covered the main reasons why someone should enter a hackathon. Let's talk a little bit more about what you guys as judges will be looking for as you review people's projects that they're building on OPBB and Greenfield.
So we're going to go with Dora Hacks and then we'll sort of snake, snake backwards, just so that, you know, that last people get to go first on a couple of questions so they can break some new ground and then we'll get back to space ID again.
But let me ask you, what, what kind of characteristics are you looking for in a main project? Like when you're judging and looking at a project, like what is it that's, what is it that's going to jump out to you?
Sure. Thanks for asking. Just, I think it's a little bit relevant to previous questions. So I will also cover a little bit part of that.
So I think what's amazing about hackathon is, especially for web3 is that hackathon is actually a very like open and transparent, fair place for web3 hackers to ignite their ideas into and turn it into an actual project.
projects. I'm not sure if everyone is a well or not, but like some, some core like protocols right now in the industry is like Uniswap, like one inch, RV, they are actually came from like very first batch of East global hackathons.
And just like space ID and Zikri, which is like ZKBNB, they are, they all actually came from previous hackathons before.
So actual hackathon is definitely like very important way for not only ecosystem, but also for builders to build their reputations.
They basically bootstrap their ideas and meet great peoples, get more well connected and into the space and turn their projects from zero to one.
And what we are looking for, just like, just like I mentioned, I like Uniswap, one inch, all of these projects back to old days are actually very innovative.
So I would say, like, at the current stage of industries, we definitely don't want to see more replicated wheels.
For example, if the hackathon, like for DeFi, let's assume there's a DeFi track, and we definitely don't want to see there will be another 20 pancake swap forks, or like Venus protocol forks to the track.
I don't think this type of project will be any more attractive, and I can bring like more values to the industries in general.
So I think the truly innovative ideas, even a little bit hypothesis is okay.
Like, as long as it's truly innovative, and it can tackle the real, real, real pain points in industries, and solve the real problems,
those type of projects and teams are what we are looking for and want to see in general.
Sure, I love what you said there about, like, originality.
I think especially when you have such new projects and exciting technology like OPBB and Greenfield,
it really opens up this whole new world of possibility where it's just, it's really waiting, both of these pieces of tech, in my opinion, really waiting for like these breakthrough amazing projects.
That's the whole reason why we're holding the hackathon, why there's such a huge prize pool.
So, yeah, I love that comment there.
Let's snake backwards again and just say hello once again to Open Campus.
What about you?
What are you looking for when you're judging a hackathon like this?
Yeah, I think impact is, you know, the potential impact is a really big kind of criteria for us.
You know, solutions that have kind of the potential to make a significant difference in, you know, whatever target domain that you are aiming for.
You know, whether it's a sufficiency, you know, scalability or even just user experience.
The problem itself, you know, it can be big, it can be small.
But whatever the problem that you're trying to tackle must, you know, the solution must be, you know, must be leaps and bounds better than whatever is out there.
You know, I think there was already mentioned, we're not, I think anything, especially in this market, anything iterative is probably not going to be, you know, that particular interesting.
You know, we're not looking for, you know, a couple, you know, a minor improvement in speed or costs or anything like that.
But, you know, it can be a really small problem, but, you know, that your solution must be, you know, significantly better than anything that's out there.
I think, I think that's kind of one of the criteria and also kind of sustainability.
I think right now in this market, again, that's quite important where, you know, you have to demonstrate there is indeed some sort of long-term viability, both from a product and business sense or from a technology and also the business kind of perspective.
It must be, you must be able to build this in the long term and not just for kind of quick kind of profit, that kind of project.
I think those are not as attractive, I would say, but yeah, definitely bring something, have the potential to bring positive impact to the space in whatever area or whatever kind of target that you're aiming for.
So I think that those are kind of the two criteria that I think would help a lot in the project.
Yeah, we want to see that impact, right?
And I love the way you put that.
That was a great answer.
Let's find out some more.
Let's go to Polyhedra now.
How would you, so someone submit to projects.
I mean, what, what are you looking for?
Like what's important for you as you try to pick who's going to win these amazing rewards?
Yeah, sure.
So little, little bit of heads up, because technically we are not supposed to, to release what we wrote for the past.
But as we suggested, we are focusing on OKBNB recently.
And of course, Polyhedra is building ZK Bridge.
So based on those two points, I can suggest that we are looking for three qualities for the products building on ZK Bridge and using our APIs.
The first thing would be security.
Because as a Bridge product or as applications building on Bridge product, it's either cross-chain DEX or cross-chain GameFi, cross-chain DeFi, whatever.
Security is always the top concern because we want our users, funds, assets, information to be secure.
So, of course, a secure product is the most important quality we are looking for.
The second would be efficiency, because ZK Bridge itself guarantees very nice efficiency in order to optimize the user experience.
For ZK Bridge itself, we are able to finalize the cross-chain transfer within like seconds, minutes in some of the cases.
So, if you'd like to build some cross-chain DApps building on ZK Bridge, one thing we are looking for is efficiency.
Because we want users to be able to use the DApp swiftly.
We don't want to see in a scenario where users have to wait for like 30 minutes before they can finish a transaction on the cross-chain DApp.
The third quality we are looking for is cost efficiency.
So, since we are doing our OPBNB, as we all know, OPBNB is like super, super cost-efficiently.
So, we made some experiments on OPBNB.
We actually have a production level, product running on OPBNB, where all the transaction gas can be calculated within cents.
Actually, less than cents, like 0.3 cents, 0.5 cents, 0.7 cents, etc.
So, we want DApps or components of the DApps to be cost-effective.
We are looking for DApps that can achieve the goal of interoperability or user experience.
with the minimum gas cost, so that users will have almost a gas-less experience when building on the ZK Bridge product.
And this might be hard on other layer 1s or layer 2s, but it's achievable.
It's definitely achievable on OPBNB, as we have already made some demos and some explorations,
and even some production level products on OPBNB already.
So, while summarizing that, it's security, efficiency, and cost-less.
Those are the qualities we are looking for for the projects participating in the BNB chain hackathon.
Okay, awesome perspective.
Always love having Polyhedra on this basis, guys.
They always come with the good knowledge and the detail, the value add to the conversation.
I think the same can be said for everybody on the panel.
Been having a great chat with everybody so far.
Let me just do another quick reminder for anybody that's listening that came a little bit late.
We are talking about the BNB chain Istanbul hackathon.
It's going to be next week on Friday, right? The 10th.
And I'm really looking forward to it.
It's going to be an awesome hackathon.
Huge prizes up for grabs.
And, of course, we're going to be making sure to build great projects on OPBNB and Greenfield.
That's the whole point of it.
These crazy, amazing, futuristic technologies we have, whether it's like super low fees, super fast transactions, or decentralized storage with Greenfield.
We want to see the amazing stuff that you guys build using these technologies.
And you can do it by just clicking on the pinned tweet here in the space.
Go to the Luma link.
Find out how to register.
Hopefully, you can get to Istanbul if you're not local.
A little bit of logistics required, but I think it will be worth your time.
And as I said, huge prizes available for those who do want to take part.
So let's just finish up on this line of questioning.
As far as space ID, let's kind of merge this last question into the next question.
What are the characteristics that you're looking for in a winning project?
But also, what kind of hints could you give people about preparing to build a strong team, understand the tracks, or just come ready to build something amazing?
What kind of tips could you give people?
Yeah, of course.
So I would say first tip is you'll see the different bounces for the project.
And they're looking for people building on what's already existing and giving it more utility.
I mean, I'm talking about like space ID specifically where like we got our domain names.
Like it's one thing.
It can be resolved or reverse resolved into different apps so that these names that people pick are then displayed in the apps.
But we're not just looking for projects to do this integration and then move forward.
We want something more innovative, more creative.
We want to give more utility to the names themselves.
For example, I don't know.
Just from other projects that have built on top of it where they've released a website that you can log in and access using your domain name.
Or they're this project called OnThis, which uses ENS to simplify different transactions.
For example, I could send funds to an address that would be stake.ledo.eth, and I would automatically get my ETH stake on Lido just by sending funds in a wallet.
Something like that gives added utility to domain names is useful because if you just tap into a small integration, this is where your project's not necessarily going to stand out.
I've been a judge on behalf of ApeCoin before, and we had a requirement which was to add utility to the token.
And we had a lot of presentations from projects that were showing us their projects and they were showing, oh, look, you can swap the Ape token on what we've built.
But this is not enough, right? And the judges can tell if some of the projects out there, they just try to link all the different bounties together.
But these projects, they won't stand out compared to the other project that really focuses on one bounty in particular.
So if you want to stand out, focus on one bounty in particular.
And obviously you can integrate name services in there if it's going to like elevate what you've built.
But if you present your project as just having integrated the SDK of a name services, which we know takes about 30 minutes to an hour, it's not going to be enough to win a particular bounty.
And speaking of like other other hints, I would say definitely use available resources out there, right?
If there's pre-made SDKs that you can use so you don't have to build stuff from scratch, use them.
Come prepared. And when I say come prepared, like it's one thing to arrive with your environment all set up like in a technical perspective.
But don't forget that at the end of all this, you need to pitch your project as well.
So you can come arrived already with some pitch decks template with a particular branding, right?
So even if you don't know what's going to be the bounty like in advance and the criteria, you can still have templates and be prepared in terms of pitching and not just in terms of building.
Wow. What a terrific answer. Thank you for that.
I think it's really fascinating for me, too, because as I said earlier, like I'm not a hacker.
I've not participated in something like this.
So to hear about, you know, the way it works and your expectations, but also giving genuine tips.
I feel like people in the audience that they're attending, people who are listening back later on, take notes, guys, because I think even something simple like that, right?
Like you can have a little slideshow ready, get your branding, you know, done in that moment, slap it on there.
And then you can have a much more professional looking pitch deck than when you come in doing it sort of in a rush towards the end of everything.
So I think lots of really cool like nuggets of information that we're getting here.
And I do want to go back to Dora Hacks now to let them sort of give their tips.
You'll notice Dora Hacks has changed a little bit.
I think their main account had to leave, but we do have our same speaker here.
He's just going to be talking from his personal account.
So what do you think?
What kind of tips would you give to people who are trying to to win this hackathon to win a huge reward?
Sure. Thanks for having me again.
I think it should be quite simple and straightforward from my side.
I mainly have three points.
The first is that please pick the right track for your project.
It might sound a little bit stupid, but actually for every hackathon that we host before,
there are always some projects.
Maybe there are DeFi or the NFT project on the base, but they apply for other tracks.
It might because they just didn't pay much attention or it just because like the tracks that they apply has less competition.
But that won't help you to increase the chance to win the tracks.
So always pick the right tracks. Pay attention on that part.
This is the first.
And second is that always try your best to provide your GitHub link or your book link.
I know that there are some like sort of the worry from especially from early stage builders that they're worried about their coding base to be copy paste by others.
But like this is the industry that with the philosophy of transparent and open source.
So keep that in mind.
And if you really do have the concern, definitely share your code base privately with the judges to make sure that you will be qualified for the final for the final prizes competition.
And the third prize will be always try to submit your project as early as possible to our platform.
Don't wait till the last minute because you might encounter some unexpected problems, for example, like the technical issues or maybe the website just crashed.
It happened like a couple of times before as well.
And we all observed that many of teams just waiting for maybe like to the until the last 30 minutes to submit and like a certain amount of them just missed the deadline.
Sometimes we can open the deadline, open the portal again for them to submit.
But sometimes they just won't be qualified to participate in the teams of participate, participate for the hackathons.
So definitely keep that in mind.
And you can always submit projects early and come back to edit your project profile later.
It's it is enabled by door hacks platform.
So don't wait till the last minute to submit a project and submit as soon as possible.
Yeah, so that would be my three tips.
Thanks.
Thanks.
OK, those were, again, really specific, I think, strong pieces of advice.
Hey, how about real quick if we go to I can't remember what way we're going now.
We'll go back to open campus now.
Could you explain to anybody in the audience, like maybe there's some people who are like really new to hackathons.
Could you explain like what tracks are and kind of how they work and like how should people pick a track?
Like what what what should that decision be like for them?
Yeah, I think in terms of tracks, I think pick something that I think earlier that was mentioned, you know, you've got to think about really hard about you've got to pick the right one.
You know, pick one that you're familiar with or at least you have some experience in or you understand kind of the environment of that solution or the of the ask of that track.
Definitely don't pick something, you know, that that sounds really fun or it's more kind of trendy, quote unquote.
But, you know, just going to be mindful of your own abilities and your own skill set, your own experience and, you know, just pick the right one.
I think I think that's that's kind of one of the most important decision that you can make.
I think, you know, before you come to to the hackathon, I think, you know, do your own research, do a bit of background research.
You know, you know, who are the sponsors, who are the judges, what you know, we already talked about what we're looking for.
You know, have a thing before you come to the hackathon, you know, do a bit of research on each of the projects.
You can kind of maybe hazard a guess on what we're asking for, what we're looking for, what kind of solution or what kind of problem that we're facing that we are going to put forward.
So do a bit of homework.
Don't just come to hackathon and just like, you know, I'm going to wink it because I know everything.
So, yeah, chances are you don't.
And, you know, make sure you have the right team.
I think that that's also very important because, you know, it's very it's human nature to pick someone that you something that you're really familiar with.
Maybe you're just going to pick all the friends that are, you know, similar background as you or, you know, work on the same project you previously.
Maybe pick someone new or pick someone different on from different backgrounds or or kind of even not just, you know, from a technical ability point of view, but also kind of marketing a product or, you know, design anything that will bring fresh perspective.
I think I think that'll be that'll be really important.
So, yeah, so that's kind of my advice and my tips.
Cool. Yeah, that was a great, great answer there for that.
I want to sort of get into our last question.
Now, guys, just before we go, we're going to have just probably like five, 10 more minutes.
So thanks so much for your time.
You sort of mentioned things that people should avoid.
I think one of the things you said was maybe don't pick a track that you're not super familiar with.
Anything else, guys, that kind of mistakes that you've seen or like, you know, good, good entries gone wrong that kind of people could learn from that you could let people know, hey, like, think to do this or don't do this.
Anybody can just unmute and just sort of shout out if they have an opinion or maybe just like a memory of something they saw happen that they could sort of give advice to the audience about.
Yeah, if I can if I can pitch in, I would say research maybe a little bit in advance, like how to pitch your final project.
Like I talked about having like a pitching deck template ready like in advance, but it's also like how you're going to deliver that project to the team that is judging because not everyone on that team is going to be super technical.
And I've seen some pitches that were very, very technical, very around like a product demonstration, which is good.
But a product demo and a sales pitch are two really different things.
You're trying to convince an audience of the benefits around the challenges that you're trying to solve.
So it's always good to do a little bit of research around this.
And I know that in a hackathon, you know, the team's not necessarily all going to have a business development like background, but it's also good to come a little bit prepared around that because that's going to help you differentiate yourself from from others.
Yeah, I think that's such a good point. Right. Like when you're giving a demonstration, you kind of have to sell it. Right.
You have to think a little bit like a business person or a marketer.
If you're just sitting there demonstrating a project, you want it. You have to try and find some way to make it accessible and really get those ideas across to the audience.
That's what I understood from your answer.
And it makes sense to me in that way.
Anybody else want to unmute and share some feedback on like mistakes they've seen or just things to avoid doing as you enter?
Yeah, I guess I just follow up on that.
So as we're talking about documentation is very important.
It's on two sides.
First is read the documentation, especially in hackathons.
A lot of information are actually already provided to you in the documentation.
A lot of components are built already.
What you're doing is like utilize those components and try to come up with your own solution.
So one thing is read the documentation and do not think too big because it's a hackathon.
It's time limited.
So try to first locate your scope, what you are going to do, what the toolkit you have and what the components you have and what are the missing components.
So try to figure out from the documentation, try to find the resources you have.
And secondly, as judges from hackathon, when we are making the decision, we need to figure out what the project is building and how the code qualities are.
So one thing very important that we are looking for is the documentation from your code.
Because sometimes the code works, but it's going to be hard for us to understand how the code works.
So I've seen different projects.
They have very well functioning codes.
But when we are reviewing the codes, we are having a problem understanding them.
So documentation in your own code is also very important.
Some products we have seen have very nice performance, but they are missing the documentation.
And that could be a minus when it comes to the judges.
So well, read the documentation and write your own documentation.
That's the advice I would provide for our participants.
Okay, yeah, that makes sense.
You know what I really like about this space?
We have a lot of B&B chain spaces and hear a lot of stuff about projects, what people are working on, roadmaps.
I feel like in this space, we've really got some concrete, specific ideas about what you guys can do to build.
Hopefully, everybody has learned from this space.
Does anybody else have any final thoughts or things that they want to add before we go?
I think we covered a lot today.
Yeah, I think one last thing to add is, you know, I think during the hackathon is going to be very intense, you know, a couple of days.
So I think, you know, I think all the other judges have already provided great advice.
I think one last thing I would say is, you know, don't panic.
Just take a breather.
Have some time to plan ahead what you're going to do.
Have some clear deliverables, you know, who's going to be doing what and what is expected to be coming out of who's work.
I think that's going to be very important.
Just have a clear plan of attack.
You know, I think everyone, when we start a hackathon, you know, all the energy, all the excitement, you want to dive straight into it.
But, you know, just take a breather, plan ahead, have a think about how you're going to do it.
And, you know, don't just, don't just blindly, you know, wing it.
I think that's not going to, that's not going to, you know, do too well.
I'm going to switch tight deadline and just don't forget to, you know, relax.
This is going to be a fun experience, but, you know, just, just relax and have a game plan of attack and then you'll do just fine.
Awesome advice.
Yeah, I think that's really the key is like, we want this to be something really creative that you guys enjoy.
But at the same time, I could see how it would be stressful.
There's a lot of money on the line.
You know, we've heard there could potentially be jobs on the line, like if you make something that's really impressive.
So there's really a lot, I think, to get out of this experience.
One more time, if you're listening, if you've heard stuff today that has inspired you, if you're in Istanbul, if you can travel, if you're inspired to join,
we're still accepting applications, but you're running out of time.
Head to the pinned tweet in this space.
You'll find a link to a Luma.
We also have a blog on the B&B chain blog, which has information about all the tracks if you want to know what they are beforehand.
So you have an idea of what you're getting yourself into.
So all the information is out there for you guys.
If you have questions, please feel to feel free to DM me on Twitter to this account.
I'm sure our judges would be happy to take your questions as well.
But for now, I think that is going to be the end of today's space.
I want to give a sincere shout out and big thank you to Polyhedra, Space ID, Open Campus, and DoorHacks for their time today.
I think you guys are going to learn a lot.
If you're in the hackathon from this experience, obviously these judges have a lot of experience and wisdom that they've gained for themselves, but can share with you guys as well.
So with that said, it's been a great afternoon of discussion.
I'm really looking forward to next week.
I'd like to thank everybody in the audience for attending too.
And Projects, would you guys like to say goodbye really quickly?
Sure.
Thank you for having us today's space.
Definitely looking forward to all of the amazing projects and viewers to attend the hackathon and can potentially emerge to be the next best teams in the industries.
Yeah, thank you everyone for coming here.
Looking forward to seeing you in person or either online around Binance Blockchain Week in Istanbul.
Yeah, thank you everyone for listening.
Thank you for the invite to BNB Chain.
Everybody get excited.
It's going to be fun, super good learning experience, and you'll feel like in a movie in no time.
Yeah, and thanks everyone for listening.
Thanks Chris for hosting.
Thanks my fellow judges and sponsors for the awesome advice.
And yeah, definitely very excited to see all of you in Istanbul, hopefully.
Okay guys, there you have it.
We've done it.
Everybody has an awesome weekend and of course an awesome time in Istanbul.
Binance Blockchain Week, BNB Chain Hackathon, BNB Chain giving a keynote presentation that we teased earlier this week.
Lots of exciting stuff coming through.
Keep it locked on Twitter.
I'm going to be keeping you up to the latest about everything that's going on.
Until then, as I said, have a great weekend.
Thanks for joining us and we'll see you next time.
Bye bye.
Bye bye.
Host
Speaker
Open Campus
from
EDU Coin
