Scaffold HBAR Bounty 🏆 $10K in Prizes | AMA & Office Hours

being open-sourced, but we will actually a bit of a sneak peek for later on. We will be having some bounties focused on Clipper in the coming months, but you know, you can be using things like chain-link CCIP, which is integrated onto Hedera, or you can use Layer Zero or Axelar. All of these bridge solutions we have, none of which of course are quite as powerful and secure as Clipper. But that's just to summarize a couple of ideas on the ecosystem integration part. The second part is the documentation quality. So that's also heavily weighted, where ecosystem integration and value is weighted at 35 points, 35% out of 100. The docs quality is rated as 30%. And the reason why this is rated so highly is because we want to see scaffold H by templates, which other people can come along and use them self. That's a really big part of this scaffold template bounties. Not just building stuff for yourself, it's building stuff which existing developers and new developers in the ecosystem can use. And all of these bounties, all of these templates, which pass the sort of benchmark criteria, don't necessarily need to be a winner, will also be featured on our documentation. So that's the docs part. And again, I think like a good stress test of our documentation, good, is first of all, can you clone the repo and get it running end to end just by looking at the documentation from a completely clean slate? That's really, really important. And that's generally the minimum evaluation that you can do. Even better would be if you can have someone in your friend or a colleague to try it themselves. Because as we all know, as developers, something might work locally. But whatever reason, I think it's the growths again, probably people aren't throwing enough acorns to distract them. You know, you go over to another environment and suddenly it stops working. So getting other people to test is going above and beyond and that's going to be the best way to be really safe. And I think another one in this day of AI also makes sure that your docs aren't sloppy. AI is really great at adding stupid, unnecessary redundant information. It drives me crazy. I mean, you can probably hear the pain in my voice. But I'm sort of shipping code with AI and I see the docs and the comments that it writes. And I'm like, why have you mentioned that? So really, if you do have AI write your docs, please read through it. And I doubt you need to be adding more information. It's probably a case of delete, delete, delete, delete, delete. Less is more. Less is certainly more, especially in this age of AI slop. So that's just another point. Yeah, I think AI is writing for elementary school English as long as possible trying to get trying to pack as many sentences as that paragraph as you can. Yeah, exactly. Yeah, and it's like just simple English. It doesn't need, you know, we're not looking for similes in a bloody Hedera documentation. We're looking for how can I get stuff done without, you know, expending too much brain powers to try and figure out this three-class sentence with seven commas. Nice and simple. Keep it simple, stupid. Keep it simple, stupid. So the other criteria, and just to sort of cover what we've covered so far, we've covered the ecosystem integration, that's a 35% weight. We've got the quality of the docs, 30% weight. We've got code quality. This is weighted at 20%. Again, I think another sort of, you know, it's easy to say, don't do AI slop. But I think what does that actually mean? And I think we went into some detail in terms of from the documentation side, you know, I think there's some tangible actions there. On the code perspective, the typical signals to me that there's been some, you know, sloppy AI writing code without really taking a look at the code base as it is. And you know, it's just a pending new code. What I generally look for is, well, comments, which are really long comments, which talk about previous decisions that have been changed. But, you know, don't really carry any relevance. This is a really big giveaway to me. If you've got like a seven line comment talking about what the code used to look like, and then why that code has changed, and the reason for it changing. And then, you know, at that point, it's like, well, we just need to know what the function does now. You know, there are of course times where you do want to say why there's been a change, but it's not particularly relevant within the context of this. Also, when you have, you know, duplicate functions that I find often AI likes to, it sometimes misses. Let's say you've got something which broadly does, it broadly achieves this particular job, right? You've got a function which does X. Sometimes the AI doesn't know you have that function, so it will sort of do it twice. So you have this duplication of code. There is a, an old adage in software development, which is dry. Do not repeat yourself, you know, keeping things modular and limited, minimizing duplicate code, which AI, you know, for AI, AI can write code for days. It can, it loves to write duplicate code. And then I think the other one is, you know, abstractions which are not necessary. And I mean, I, there's definitely been a few times where I've sort of seen a file that that AI is written. And it's basically a function which is, you know, just calling another function and exporting it in a new file and they're like, what, why are we just exporting a function and wrapping it in another function that there's kind of a bit pointless. So those are just sort of a few things that I tend to look for. And then, you know, also just code which is really hard to understand. I'm, I'm still a big fan and I'm not, I'm not perfect at it myself. But, you know, when code is really, really complicated, there's a lot of nesting, there's, you know, you know, a human has not written that because no human can follow that really extensive complex logic. And so often, and so often code can be written in a way which is less complex. Maybe it doesn't capture so many edge cases as the AI complex one captures. But again, you need to be pragmatic, right? You don't need to cover every single edge case. And, you know, sometimes having just a really nice easy to read function is, you know, that's indicates to me that humans written it. Or a human has reviewed it and ensured that there's not AI slop in the source code. So that's a bit on code quality. And then finally, Hadeera service depth. So that's the final marking criteria that we're looking at for this scaffold H by bounty. That's worth 15%. The reason why that sort of wait a bit lower, you might be thinking, oh, hang on, this is a Hadeera bounty. Why is that sort of wait a bit lower? A lot of that is going to get, you know, that there will be some overlap with that when it comes to the first big criteria, which is the ecosystem integration. And, you know, if you're if you're hitting a dexes and you're hitting bridges and whatnot, you're going to be using the Hadeera services implicitly. But in and of itself, what we're looking here is uses of the Hadeera service, which are not trivial. So for example, it's not just creating a token for the sake of creating a token and then not really doing anything else or it's not just, you know, submitting something on the Hadeera consensus service for the sake of doing it. Something which actually can be justified as almost as like a business case, right? What would the if a business was to do this or if a product was to adopt this technology, is it actually adding value to the specific use case? So those are the four, those are the four criteria. And now I'm going to open the floor. If anybody has there any questions where we can discuss, you know, what you're building, any specific questions based on the criteria I've discussed, any clarifications that you need, please do put your hand up and come up and and come up and and share your share your thoughts. We've got quite a few people in here, which I'm very happy about. So hopefully many people here are building. And if you're not building and you just joined head over to Hadeera, Hadeera scaffold H for a bounty, I believe, yeah, if we could have somebody just comment that below, it's that, yeah, if you head over to Hadeera community account has shared that the scaffold H by a template bounty from there, you can register. We are finishing on Sunday. So there's still a lot of time. And yeah, we'd love to see your submissions. But anyway, that's enough of me talking. I'm going to pause, stop for a bit and hopefully see some hands come up. I see we've got one already from FI, from FI, from FI. Please come on up. Cheers, Jay. Thanks for that insightful breakdown of the Hadeera blockchain and especially AI integration. So I'm an entrepreneur based currently in Bangladesh, but we're focused on vertical farms and we're leveraging the use of NFTs and AI to do something new with food. And I'm very excited about the developments you guys have done on Hadeera because Cardano recently rolled out a solution, for example, with wines, where the validity of the wines being... So just to be clear for everyone coming up, this is specifically to ask questions about the HBAR scaffold bounty program, registering, getting through your builds, any kind of advice, it's not for coming up and shilling a project or talking about off topic stuff. There's other spaces for that plenty of them. So let's try to keep it focused on what we're here for. Thanks for clarifying that. I think, yeah, if you do have questions about the bounty, maybe I guess specifically how your projects, how it currently stands against the bounty criteria, then feel free to ask that, but I think it's a good point. Because I think we also need to be conscious of other people's time here. Hopefully, many people here want to ask their questions. So yeah, a bit of brevity when we're not asking it, but feel free to put your hand back up if you do have a genuine question. Tolga, let's go over to you now. I see you've got your hand up. And I think in just in terms of structure, then, let's go for 10 seconds on what you're building and what your question is, again, related to the agenda of today. Tolga, do you want to go off pause and ask, yeah, there we go. I didn't assume that you were calling me. Actually, I have a question. Actually, I'm marketing communication professional, but I want to develop and build something. And I love HederecoStem at all. So actually, that bounty is something for newcomers, or let's say, somehow a person in the tech ecosystem, we can find some people along with him to build something. It is at that level, bounty, or it's something advanced. That's a really good question. So, what I would say is, well, firstly, if you want to win the prize, there is going to be some tough competition. So, if you're looking to get one of those $2,000 prizes, then at that point, you might want to partner with someone, especially if you're coming from a less technical background. But it's always really great to have people who have business experience when designing products. One of the most common ways of failing, not just in bounty submissions, but in businesses, you've got a bunch of techies building something which is not helpful at all. So, definitely, if you're looking to be one of the winners, I think head over to the discord. You can find that at hederea.com slash discord. And we've got a very active discord. We've got some really great mods who are actually on here, absolutely shout out to Abdel, he's one of the top moderators. Maui as well, just a few. And it's a very active community. You'll be able to find people to participate in the bounty there. But if you're just looking to get started, I think this is also a really great opportunity too, particularly because we've just released this tool called the hederea harness, which is essentially a special AI layer that sits on top of things like Claude code and other coding agents, which makes Claude code supercharged when it comes to AI when it comes to hederea. So, I'm going to drop a link to that in the chat below. That's the hederea harness. It might be something worth looking into yourself, particularly if you know you haven't got a lot of hands on hederea developer experience. The idea is that the harness takes a lot of that away from you. And you can just sort of put in the thing that you want to build as a specification. And then the harness can come back and implement that. So I've just put that in the chat below. What I