Hiero TSC Meeting - 2026/09/15

Good morning. >> Hey, Jessica. >> So, Brandon, have you been coerced into chairing this one? Hold on. I couldn't understand. But I I think I think you're uh Yeah, I Yeah, I think you were busy. Um I yeah I believe the last TSC people were saying that few few of the members or most of everybody were going to be occupied during this time but we still decided to oh okay but we still decided to have this meeting because we had few um items pending from what we can see in the agenda. And >> yes, >> besides besides Brandon, the only person we have who is a TSC member is Alex on the call. >> Yeah. >> Um and and I think Keith probably he's probably got the piece that wanted to get some presentation. >> Gotcha. Okay. I'm out of construction now. Okay. Um, I did I didn't see a note about absences um in the TSC chat, so I wasn't aware of that. I guess Ashgraph is having an offsite or something. >> Yes, >> that's right. >> Gotcha. Okay. >> So, I I don't know if any of these things um on the agenda today are um timesensitive. There's a couple of HIP things. um the voting on the HIPP proposal for um 1535 and HIP 1522. Uh Keith, I can see you're on the call. Are either of those things things that you're driving? >> So 1535 got voted on last week. >> Yeah. Okay. So maybe I'm looking at last week's agenda. >> Uh I posted the link to this one. I I basically I just carry all over most of the items. That's what we usually do. we carry over the items from the past one into this one just to review. Um so the there there is one timesensitive one which it is the elections I wanted to I I I continue to create um awareness to all the maintainers that is very important to to vote. We had had very very few boats uh around maybe by now by by now it should be maybe like let me double check one second. Let me just give you an exact number. We have 11 votes out of uh 99. So we need uh we need to create more awareness. And if you if you work directly with the with the maintainers, I I would really appreciate if you can pass on the word that is very important to vote. Uh the end of the the the last date for voting for the two out of three mandainor seats is going to be on the 20th. So uh we still have this week, but it's very very important that people uh cast their votes. Uh, Jessica, may maybe be a dumb question. I correct me if I'm wrong, but um it my TSC seat is coming up for election, correct? >> No, not yours. Um yours, I think, is going to be on 2027. >> Gotcha. Okay. [clears throat] >> We the seats that we have for elections is uh um Hrix, Stoans, and Richards. And the three of them are uh have casted the re-election. We have six candidates in total. Uh so if for those who have not um check out their ballots, uh you're going to see uh the six members there and the idea is to have all maintainers vote on two of them and then from the people that didn't got selected, the TSC is going to select the third the third one. So uh that's basically how the vote is going to look like. But uh we have um submitted the ballots to 99 maintainers which is the maintainers that we have uh registered right now and uh only 11 have casted their votes. So uh we need more people to do so. >> Okay. I'll definitely do a um I'll do a post and also I'll make a note to mention something. I might do a live show or a live stream maybe this week. So, I'll make sure to mention something there as well to to drum up some support. Is there like I've been a little bit out of the loop. I've just been on the job search right now, but um is there a good link to kind of send people to to kind of like um uh I know you've maybe shared something in the Discord chat, but just wanted to make sure I I knew kind of where to send people. >> Yeah. Yeah, for sure. Um I it is easier if and actually I can post in the chat the link to the ballot. Um >> amazing. >> And the um it it it just a little note that people get confused sometimes the way that people log in into the ballot is a little bit tricky. So I just put the I just put a little note there along in the chat. >> Gotcha. Okay. Amazing. Yeah. because that's that's one thing cool about doing the live streams is maybe I could you know like demonstrate doing the vote process or something and there'll be a good clip from that that we can share as well. So yeah, thank you for that. I'll get on that. Yeah, no worries. >> Thank you so much. That's uh mainly the topic that I have for today. >> And and I would ask maybe if Keith are you in um Texas with at at the offsite if you could bring it up to Richard Bear to perhaps remind everybody there. Um because I'm sure there's a lot of maintainers in at the offsite. >> Yep. I I I can do that. And and just back to the earlier comment um regarding hips there, I don't think there's anything urgent on the hip side that we need to talk about today. >> Okay, good. Um do we want to um motor I'm sort of here absconding with a little bit of the agenda here. Um there I can see Daniel's on here. Um, so maybe we could move to there's a couple of Angie's got a presentation on learn coach more um coming up. Um, and Hendrick's got a the AI decentralized trust kick up coming up working group um which is just really a kickoff for the working group [gasps] um under the updates. So I'll skip through the two HIPS if nobody's going to talk through them. I think the HIP 1535 did pass successfully. And then the next thing on the agenda we have is um an update from Daniel who I see on the call on the Hierro website. So perhaps we could let Daniel give that update. >> I I sorry to interrupt. Uh would you mind could I just say a few words because actually I do need to run off to the back to the conference. >> Yeah. >> Yeah. Thank you. Sorry about that, Daniel. Thank you. I I just wanted to quickly um I think I thought I intended to take is I thought I was supposed to present the uh security sensitive proposal. I'll post it in the channel. I don't think it makes sense to present it today because we don't have a lot of people, but I did see that Sophie left some comments and stuff. >> Um I think this is going to be a very controversial proposal and I think there's going to be a lot of strong opinions. Um, so yeah, maybe just this week people can take a start take a look at it and supporting their own opinions just to kind of uh I just want to quickly level set for this proposal. When it comes to identity verification, there is nothing perfect and everyone's going to have a strong opinions and everyone's going able to throw a wrench in anything you propose because you know human identity is a very complex and everchanging thing. I would just say though that the goal of this project if in its most simple terms is like if you do a $10 million hack on Hideera and steal $10 million we want if the police can find you like if there's no police investigation they can figure out who you are and track you down and put you in jail. That is the goal of this proposal. It's not that Hashgraph is going to have perfect knowledge of who you are or something like that, but if a police investigator like goes and talks to your friends or your former colleagues, they can find you and they can throw you in jail. That's the goal of this proposal and I'll just share it. I just wanted to like kind of level set with that and to kind of set expectations. That's that's what I'm trying to aim towards as well as you know a lot but also like that's itself is not enough. There's a lot of other things in the proposal around like additional tools for scanning for security vulnerabilities, more checks on who can sign up on releases, um updating our code owners files. So, it's it's it's a multiffactored approach to target what I think is a a true and genuine security vulnerability uh we have. So, let let me just post that in the chat and maybe just this week people could take a look at it and start forming uh leave comments and questions and um yeah, maybe I I know Sophie you Sophie's on I saw she left a large comment that I I'll think she maybe she's on that I I'll try to address. >> Okay. I would also suggest that you post it in the TSC the Hierro TSC channel so that the TSC members who may won't watch this video um get it as well. >> Okay, I I'll do that. >> Okay. All right. Thanks, Keith. And um have a great conference. >> Daniel, you want to take it and um walk through the website if no one has any questions for Keith? >> Yeah. Okay. Thank you. Um good good evening, good afternoon, good morning everyone. So I just wanted to give you an update on the website I think. Can I share? >> Yes, please. >> Okay. Can you see my screen? >> Yes, we can. >> Okay. So now uh if you if you have noticed or you have checked out from the website in the recent days the it has a new look for now and uh we have been working intensively with the team to make it happen and uh now as we had the TSC vote TSC meeting last time and people voted So this is the final look for now as we have and uh you can drop out comments or you can say that uh you can have you can have your reviews you can see you can reach out to us the maintainers and we can sing on the views that you have but currently this is what we have and uh we have changed its look and uh your comments are highly welcome everything. So you can go check it out and see. That's all I have. >> The is the the issue explorer is a really nice piece now and the the UI for it is pretty great. So thank you for all the work that you've done, Daniel. >> Yeah, thank you very much. But it it was also a collective work with the maintainers, Angie and Sophie. >> Yeah. Awesome. All right. So, if you have any feedback on that, please get it back to Daniel and Angie and um other folks that have been working on it. Um, can we bring back up Jessica the the agenda? >> Make sure I've driven >> I one sec. >> Did you have it? >> Yep. That's okay. This may be the least controversial TSC meeting we've ever had with [laughter] with Keith um poke for next week being more controversial than anything we've had before. So, um so I think we postponed the Yeah, we did the EU cyber resilience. Um, what I've asked is um, Sebastian and Hendrickk um, both um, and Sebastian I think I'm going to kill his last name. Angelina I think it's Titian or something like that. >> Yeah, something like that. >> Something like that. Uh, who works for Open Element also is on uh, uh, one of the the key European cyber resilience um, uh, working groups and so uh, we've kind of nudged him to come and give a presentation on that. um sometime um in the not too distant future. So that's that's coming up. Um is there of the folks who are on here, Milan, Brandon, the TSC members, I think I saw uh Georgie join us. There's any other or Alex any other topics that we want to bring up? Um I do know that the only thing that I wanted to mention on this is that um Clipper did get successfully um put into um or added into the LFDT labs with some help from Jessica and the staff um and Edward is working on that. So um we should have all the code over there and the infrastructure in place soon for them to be working effectively over there. So, it's nice to have that compartmentalized and in the labs. And so, thank you, Jessica, for your work getting that done and the whole team. >> Thank you. >> Um, we cannot announce it or talk about it publicly until the trademark is successfully handed off between um the LLC legal team and uh which is the Hideera Council/Hideera Hashgraph LLC um and LFDT. So, um, please, uh, don't put a post out, Brandon, on your, um, your your your webinar or whatever you're doing, um, this week. We haven't, um, gotten that piece of paperwork finished. As soon as it is, there should be something, um, missive that goes out, um, or blog post that goes out on LFTT that we'll share with everybody. >> Other than that, >> one more thing. Uh there was a request to >> um include or discuss uh bringing over solo um provisioner and operator uh into hyro currently they're they're outside uh the tools and components to >> um stand up and both above and below Kubernetes uh a a hyro node. So that was also something that was uh dis uh brought up and topic. >> Yeah. So was there a hip for that? I thought I saw something written. >> It's separate. It's a separate project. It would be >> a separate project. Okay. >> Outside of the uh consensus node code similar to like the mirror node code, etc. So, it's just a separate um uh set of tooling uh to automate the node uh node setup. >> Okay, cool. Um and I did see that flash by my somewhere. Um I'll see if I can dig that up with some help from Jessica. >> I think it's issue 289 or something like that. Um yeah, in within the TSC. So, if you go to TSC and go to issues, there you go. Yeah. Yeah. Yeah. >> There we go. All right. So, shall we ask everyone to review that? Put that in the TSC channel and put it on the agenda for next week. That will give people a week to review it, though they probably already had a week. >> Um, yeah. So, let's add that to um to next week's for um a conversation and see if we can get next week to um if there's no questions on it to put it to a vote. Yeah, I I think one of the things that is not listed there, I I I might have missed it, is an identifier of who's going to be the maintainer or maintainers of that. >> We'll probably make sure that that's >> um listed. I think I can reach out to Mark. >> Yeah. Um, Jessica, could you throw that link in the um in the chat as well? Um, and I'll take I'll make a comment about the who's going to maintain it on it and thank you. All right. So, um it is 20 minutes after the hour here. Um if there's no other business, I can let Brandon go back um to his walkabout and everybody could get the rest of their day back and I will tap you and Mike for a couple of conversations in Slack and we'll all have a great day, I hope. All right, take care guys. Thank you everybody for joining us. >> Hold on. If I could have the floor for really quick. >> Oh, yeah. Yeah. Y go ahead and >> sorry. Uh I just wanted to briefly share this. I know everybody does have things to do so I will make this quick um just so that at least there's a recording of this somewhere. I just wanted to do it before the meetup event happening next week on the 22nd. So, the time for that was 1:00 p.m. It has been pushed uh to an hour ahead for 12:00 p.m. But I will go ahead and share my screen just so that uh >> we can go ahead. Yeah, just so that there's something that we can watch beforehand. Uh then let me see. Okay. And then can everyone see the whole bunch of icons here? [laughter] >> Not yet. >> Yeah, we can see your desktop. Yes. >> Okay, cool. a very busy desktop. >> Yeah. Yeah. Uh so this is just again super quick, super brief. I'll try to make this quick. I will be doing another demo of this alongside Code Rabbit uh in the meetup for the 22nd of next week. So please uh stay tuned for that and if you have time, I would love to see you there. Um but this is just something I have kind of created just to kind of help new developers especially since with the amount of newcomers, new contributors that we have had coming in there has been uh a great spike in uh questions. People are wanting to leave comments and I know that maintainers uh everyone is in different time zones so questions they take a little bit of time to answer. So, this just kind of is a helpful code coach uh to new developers and seasoned developers. If you're working on something a little difficult, maybe you just need a bit more understanding, uh this is the place to go and kind of way that you can get some more insight without having to bombard so many maintainers with questions and wait uh for hours on end. Uh so I will share the link with this in the chat in just a moment. Uh but again just to kind of keep this brief uh so I went ahead and developed what is called or what I like to call code coach uh learn more is the initial name just so that it's kind of known that you can use the at learn more command and I will show examples of this here uh so I've already kind of gone ahead and just set this up just so that uh for those watching the recording you can kind of see what it does. So this works on issues and pull requests. I will also show uh what it does look like for pull requests as well. Uh so this was an issue. This was just copied and pasted from the Python SDK. So nothing special, nothing crazy that you have to do. Uh you can do this for any kind of issues. It doesn't have to have a specific label. You don't have to make it fancy. Again, just copied and pasted, but you are welcome to do this for your own issues. And uh this will be made available as soon as possible. O will be deployed and useful uh throughout hierroleddger and hopefully hierro hackers. Uh so again this was the RPC method that I had copied from the append or append file JSON RPC method that I had copied from Python. Uh so here we have the problem we have a solution we have output. We do put in the implementation steps uh any chunking notes and then the typical acceptance criteria the stuff that you're used to seeing in a Python issue. So what I have done here is I've kind of gone ahead and I've triggered the GitHub app. So you can do this by commenting at learn more is the exact same way that you would kind of trigger code rabbit. You would do at@code rabbit and then plan and code rabbit would automatically make a plan. This works the exact same way. So here you have the command and then you have your question. What what do you need an answer to? What are you trying to learn? What are you trying to know about the issue? Uh what are your questions more or less? So and then it will take about a second or two just depending on how long uh the downtime is. If you haven't used it for a few minutes, it does take an extra 30 seconds and then it will populate an answer for you. So my question originally is can you explain the purpose of this issue? just kind of giving insight. I'm I'm approaching this as if I'm a new contributor. I'm not really familiar with the append file just an RBZ method and I kind of want to learn more. So in here the learn more code coach will go down. It will explain and kind of break it down. It talks about the TCK server. It what tells you what makes this issue interesting and then it'll even provide you with the concrete work that is kind of required. It doesn't necessarily do a kind of planning similar to what code rabbit does just because we have code rabbit. So I don't want to reinvent the wheel here. This is mostly just to kind of answer uh user questions. So again we can see this in pull requests. It is available. So if I open a pull request here, I have one open just to kind of test this out. And I did leave this open. So if anyone wants to poke around and you want to ask it questions, please feel free to do so. Uh but I did do this kind of a couple of times and I it GitHub does consolidate the responses. So don't worry about overcluttering. Uh this will I will also eventually u most likely add a mechanism just to kind of remove some of these responses uh within x amount of time just so that it's not taking too too long for the UI to load everything in the GitHub issue pull request what have you. Uh so this one here again I'm approaching this as if I am a new person. I'm taking a look at the pull request trying to figure out uh why was this added? What is the purpose of this? What what is this doing? And here the code coach uh learn more helper will kind of provide you exactly that answer. So it explains what it will do, how it integrates. Uh it also does break down these supported modes and provides key behaviors and you can you can keep asking it questions. So if you're completely lost and you have no idea what the issue is or what the pull request is and but you really want to help, you're just not sure and you want some more context, you there is currently there is no limit to the number of questions. So you are more than welcome to ask it as many as you like. Uh please feel free to take a look at this. Again I do have uh this open uh under my name. It is not available in the Hyrule Ledger ecosystem just because uh we are still going over it going through for demo purposes and making sure that uh this would be helpful to the maintainers and current project owners. So again you can kind of see just a few examples of what I've done. This is in the pull request, but you again, you are more than welcome to do this in the issues uh if you'd like. And then again, the repository of it here is shared in the link below. So if you have some time later and you want to kind of poke around with it, please again do feel free to do so. Uh a more broad demo of this uh a similar demo of this again will be shared uh in next week's uh meetup event. and I will kind of quickly just do a demo of what exactly a user or contributor would have to do just to kind of get this triggered. So, I've already done one here. I did this uh earlier just to uh try to speed up the downtime and how long it would take for the bot to respond. Again, if you wait a few minutes or if you're a couple hours, uh then it just takes an extra couple of seconds just to kind of trigger it. So, I went in here uh just to ask it a basic question. Again, I'm approaching this as if I don't know uh what any of this is and I'm coming in as a brand new person. So, this kind of uh brings down breaks it down for you. It answers the question uh completely what receipt validation is in this context and then it also does pull in the codebase. So it does when you do enable this in your repositories, this will have access to your repository code. So it will be able to pull the context from your repository and not give you some sort of obnoxious answer that is completely unrelated to what you're looking at. Um so again, I'm just going to ask it something pretty broad here just because I know uh everyone is uh pretty busy. Um I'm just going to ask it something really simple. just so that we can kind of see uh the benefit and uh also gauge how quickly this takes. So it's been a little bit since I posted a question. So it is going to take a little song uh a little longer than a second or two. Uh but then after that certain amount of time, it should just be able to uh populate kind of an answer for you. And then if it does generate an answer that you just need a little bit more context on, you're more than welcome to kind of pull from that answer as well and ask it more questions to really kind of solidify any understanding or any misunderstanding you're trying to overcome. Or if you have a question that you need to pose to a maintainer, but let's just say maintainer, they're not available. Maybe they're in a different time zone and you're on one end. Uh this just kind of gives you a quicker answer. But again, this does not reduce uh the need for maintainers. It doesn't take away from maintainers. Uh maintainers are still available to ask your and answer your questions. This just is something that helps you speed it up if you either need an immediate answer or again you just want more context. So, as you can see, it does populate an answer. It it more or less will rephrase your question and then it will provide you u an in-depth answer. This does have the ability to kind of be changed and modified in the sense of if you want a more in-depth answer, uh that is something that it can always be programmed to do. If you're worried about the amount of clutter on the UI, again, it can be programmed to remove the responses in x amount of time just to uh speed up that loading of the UI. Uh I know with GitHub it tends to uh lag a little bit depending on how much content uh is uh per issue p pull request per pull request sorry. Um but yeah that was that was it. This is uh I tried to make it as uh quick and brief as I could. Again I know everybody has things to do place to be. Everyone's super busy. Uh so if you have any questions please feel free uh to post them now. If you don't or if you just want to kind of take over or take a look over this and then pose your questions to me, please feel free to reach out to me in Discord. I'm happy to answer uh anything anybody has. Uh for those that end up watching back this recording, please do feel free to reach out to me if this is something you're curious about and you want this enabled in your projects, I would be happy to do so. Uh I hope to have this up in the uh availability of the GitHub marketplace soon and then from there we can kind of release it into the wild and uh let it assist with projects. But thanks everybody. >> Well, thank you for the presentation. Um I'd heard about this in other talks. Um and it's great to see it in action for Hyro. So um perhaps uh we'll just join you for the next call and see what the longer um longer version of this is. Um so again could you repeat when your next um seminar the seminar is next week? The date and time. >> Yes. So the seminar for next week has been changed to 12:00 p.m. EST. I know most folks had probably seen it posted at 1. Unfortunately I had a conflict come up. So, I have been a fortunate to be able to push it up an hour. So, we'll be at 12:00 p.m. EST Tuesday the 22nd. So, that will be a week from today. >> Awesome. All right. So, um we'll send that out to the universe. Um cool. Thank you very much for um giving the quick overview and hopefully everybody will join for the longer deep dive and start using it. Thanks a lot. Is there anything else on the on the call? Um, anyone else got anything to add in here? Um, >> not at the moment. >> All right, I'm going to let you all go and um, take care and we'll see you next week or >> Thank you. Thank you so much. >> Next week. >> Ciao. Bye. >> Bye.