A DUSJ manager for Github -Users, gameThe wallet identity managers, voice messages on the chain and a versatile new token protocol were among the winners of BSV hackathon in Austin, Texas, last week. The two-day personal event asked the developers to drive new boundaries with scalable blockchain capacity, show innovative ways to manage identities and create new financial opportunities for web3.
Babbage and BSV Association Where BSV hackathonMain sponsors, along with Silverline. The total price pool amounted to 64,000 US $, including smaller prices for teams placed 4th to the 6th.
The company had said it was looking for projects that used several functions in the BSV -Blockchain network, ideal with the help of tools from Babbage’s software stack. The result was records that used identity verificationoverlay networks, micropayments, tokens and Firmness protocol.
Over 30 people participated in BSV hackathonrepresents 13 project groups. Babbage set a hard deadline on Sunday morning for projects to be completed enough to present to the four-person judge panel. In Hackathon’s spirit, this saw several coders stay awake all night to get everything done.
“There were a few people who stayed up all night, it’s crazy. Subscribe for you, that’s what it takes,” Babbage CEO said for Everett at the assessment session.
The whole of BSV Hackathon Day 2, including the team presentations before the judges, was lived out of the arena (Texas Sake Co.). The sound is a bit rough, but if you are curious to hear the details of all projects competing, the presentations around Market 02:25:15:
About bsv hackathon -winner
The three more prize winners were SMB BSV, Betabolt and P2P-Voicemail. Bolt stands for ”Bitcoin Original Layer-1 token“And demonstrates a token protocol for fungal and non-sponge tokens (NFT). Bolt embeds a validation mechanism within the token itself, using mathematical induction to solve” back to Genesis “problem (ie tracking a token’s history back to its creation to validate it). OP_CAT function.
P2P-VOICEMAIL is a way to send peer-to-peer, encrypted voicemail with BSV blockchain with micropayras attached, and it contains an encrypted contact list.
When he spoke with first prize winner Ishaan Lahoti in a livestream last week, Everett said that the atmosphere created by such face-face events is crucial to producing innovation and creativity.
“The personal vibbs were, frankly, it was really good. It was informal, you can say that it was just thrown together-chopped together, if you want-I think that type of energy is where many cool things come from in our world, and I think about the methane as a compensation for part of the toxicity for web 2.0, everything we have online.
Hackathons usually produce the smallest working code required to demonstrate a project and show its potential vitality on the market. As Everett noted: “All of these apps are very early prototypes, but we are here to build and see what is possible. ”
Not every project (or even winner) in BSV Hackathon is guaranteed to be a well -known brand. Some focus on back-end functionality; Most are not yet refined to launch products. They should be seen as early rough drafts of a story or script, but drafts that show sufficient promise to get attention from experienced industry experts and investors.
Gitpaid, Gitsats, Git-something: BSV Bounties for Github users
Babbage has published a the result page For the Austin event on the BSV Hackathon website, along with links to all projects and their Open Source code at Github.
There were some introductory controversy about the winning project’s selected name, “Gitpaid”, after the incident, and some found that there was a similar project of the same name built on Github for Ethereum Network. Github also has several other projects called Gitpaid (admittedly the name is eye -catching).
Most teams had come up with their names and ideas just before Hackathon, Everett and Lahoti said, and had not googled their names to check if they were already used. Then Lahoti decided to change its name on his project, possibly to “Made“Since he already owns the attached domain name, although it can still change again in the future.
The service is a way to offer and manage monetary bounties in BSV so that Github users can find problems with other people’s Open Source projects. It works as one Smart contract It is integrated with Github’s internal problem tracking system, has funds in an escrow address with multiple signatures and pays them to the person who correctly identifies a problem.
To perform these tasks, both the shower creator and the recipient must be correctly identified, and verify that their Github accounts are genuine and that Bounty is financed sufficiently. It uses BSV/SDK overlay services to look up and track active bounty offers. Babbage’s methane desktop tool, along with certificates, provides identity-grinded measures such as creating and accepting bounties. Overlaying can be synchronized, which enables updates on price outputs to spread to anyone who is looking for their actions.
Everett noted that although similar platforms have existed before, they could only work well on BSV blockchain Thanks to its speed and low network costs.
“Why I like this project so much is that it not only uses the methane tools, but it also helps to grow the methane by financing other projects and helping these devs get what they need to keep things going,” he said.
Lahoti said he was still learning about blockchain and all moving parts within BSV, but was impressed by what he has seen so far.
“I’m still quite new in blockchain development, so much of this was to confuse me, but now most (if not everything) are meaningful … It’s a fantastic ecosystem to work with, definitely. I’m still really excited to work with it.”
Babbage plans another similar BSV hackathon event in July 2025, which will probably take place in Oregon.
Look at | Building the future with blockchain: Insights with TY Everett
https://www.youtube.com/watch?v=YRHVKQ0RJ3W Title = “Youtube video player” Ramborder = “0” Allow = “Accelerometer; Autoplay; Clipboard Writing; Encrypted-Media; Gyroscopes; Image-in-Image; Web-Share” Reference Policy = “Strict-Origin-When-Cross-ORIGIN” permitting lorscene = “” “
