Top 10 Hackathon | Common S3nse - 2026

[music] All right. Maybe some of you know we were also hosting a hackathon the last two days um for common sense. Well, they've hacked, they've worked, they've cracked their brains, they've not slept, and you're here to present the top 10 hackathons from this year edition of Common Sense, which is actually the first edition of Common Sense. And with no further ado, and with no further one, two, three, this is just the list. So, with that being said, they get five minutes to present their case real quick.

First, I would like to have FK reality on stage. Like I said, you have five minutes, so make it quick. Do we have folk reality in the Yes. So, the rest of you, you can see the list. Please make sure to get ready because like I said, five minutes is five minutes.

I will have to kick you off the stage after five minutes. Those are orders from the from my from my boss. Second order inscribe stellar cast get ready rip cord get ready at interesting names get ready ghost name get ready I hope you don't get a ghost Yes.

One, two, one, two.

Uh, hello guys. Thank you for uh having me to the top 10 finalists. [clears throat] Uh, I'm Kevo. I'm working as a software engineer at Cisco and web 3 is my kind of a hobby. And for this hackathon I built a project called forked reality.

So uh basically in the age of AI and autonomous uh agents and the D5 the trading are going to be autonomous they it is already but uh agents are going to propose anything. So imagine if you are a defi trader or you are having into any dexes and so on. uh while you are your agents are executing any transactions uh basically the platforms the D5 platforms the dexes the the trading uh platforms they will have their own rest uh endpoints the MCP servers and so on so your agents can go directly query them and the the get the data and based on the data they are going to execute the uh the transaction or no so uh what happens when those parties are compromised for example instead of giving you the accurate uh token price, they might give you like a slightly higher price and your agent is going to execute the transaction.

Or for example, it can happen uh in some of the dexes or the uh the defy pools, there might be like a malicious vaults uh where they can uh trick you to give the allowance the spending limit of your tokens and they can just drain your wallet. So the fork reality it is basically acting as an adapter for you. So here on the left we have unprotected agent and on the right we have like a protected agent. So what it is basically can I have a picture with you and basically the first example is a token trap. So I have the deploy the poison token basically it is uh basic when you are uh I'm saying here buy 20 poison with the USD.

So basically the agent is going to buy it because it's unprotected. uh but the idea of this token is you are able to buy you are but you are not able to sell it uh but you have to verify through the contract uh the the protected agent will run so with the mobile it is going to check the security of the token first then I'm not relying into any uh like evidence from it I am first simulating that transaction into my own EVM simulator and then with that I am also have testing it with zk proof so that I'm not licking in my data and if I have a pass basically the uh the secure agent is going to allow the transactions or no. So in this example the protected agent didn't uh buy the uh the poison as you can see but the uh unprotected agent bought the poison so it will not be able to sell it afterwards. So if I'm saying sell poison it will not be able to sell it. Yeah.

And uh I have the safe token as well which basically safe to buy and the agent is going to basically buy it. So the next example is uh the drainer [clears throat] in the defy pools. There's some vaults. Obviously the defi faults are uh hunting for the highest yield. So they can deposit some amounts into the vault and with the highest yield and they can uh get the they can earn the yield.

And uh once uh you are giving allowing the uh spending amount for your USDC for example let's say you are given the certain amount and that vault can uh get like unlimited allowance the spending allowance for your assets and in the end it can drain your wallet. So yeah the the protected agent is going to flag that and will not execute it. So basically this was it my as end result I built like an uh npm SDK which you can directly take and use it in your agents and also the uh I am working on having the open AI plugin so if you have already your agents farm set up you can just directly add it as a plugin and uh use it as your trading. Thank you. [applause]

Thank you very much. Thank you very much. That was for reality. The next speaker um is going to be from Second Order. I hope he's ready.

Also, uh guys, don't um try and respect his privacy. He's not doesn't want to have pictures of him taken. So, let's respect that. And yeah, the floor is your second order. All right.

So, I'm one half of the second order. Uh the other guy is uh remote surfing somewhere right now. Uh so, I'm gonna I'm going to give you a a short pitch here. So, basically, we built uh on mobile. Uh we're looking at uh the problem of copy trading and trying to create an uh analysis tool that would allow users to essentially predict how their copy trading is going to be um reflected on the liquidity pool.

So the problem is usually you know when looking at the um your favorite trader uh you can see you know their leaderboard somewhere says great smashing it 186% APY over 90 days sounds great so you want to go in you deposit $1,000 let's say with the manual execution you'll be around 5 seconds delayed And maybe you are expecting you look at the follower count maybe of the trader you see there is 10,000 followers you know you expect maybe 64 same direction trades to happen at around $20,000. So, so basically you need you need to find out how this is going to affect the pool. And we can see on this screenshot here that uh you'll actually receive not the promised 186 uh% but actually minus 12% potentially you know this trader is exposing to uh leveraged trading. So you will actually end up losing money if you go in. So this is what we try to uh address.

We're kind of thinking about it as a as a as a car crash test where the car is uh you know the the trader the the the passengers are the wallet maybe the the passengers are not okay in this case. So the alpha crash test uh replace the source trait enters 100 shadow followers across a grid of delays and sizes and these are priced against observed quotes and competing flow. Uh remaining alpha here uh it's a capacity meter that I'll show you in a minute uh that drains in real time as same direction flow consumes the surface. um what you're looking for is the answer to am I early enough to this uh trading strategy and we have created a crowd guard which uh is checking your intended size against the surface and it then returns either allow for the trade to happen resize or block with a maximum scenario compatible size enough of talking I hope it's somewhat clear uh so let me show you the the demo here. Hopefully, it's readable.

Um, so over here we have a demo scenario. This is the previously mentioned 186% APY wallet that we have found on the base chain. Um, intended size. Let's say again, so it doesn't look like it's all preset up. This is the amount we are going in the delay could be whatever uh additional let's say there is additional $500 coming into it that we expect.

So now we're going to run the crash test and hopefully in a minute in a minute we'll see. So now you can see that uh the shadow followers that we created in different input values with different uh intended size and the delay are flooding the pool. And now we see the outcome. So here it says uh block do not copy this trade remaining alpha is zero dollars at your delay. So no order size would keep this scenario sort of um the the outcome of the scenario positive.

So in this case uh maybe you want to adjust the size that you are going in with. Let's say I'm going with 100. I have a shorter delay. I still expect 500 to come in. Let's try to run it again.

[snorts] All right. It should be done. All right. So here it tells us that it allows us at $100 and we'll have a return of 1.6%.

The remaining alpha is 187. So actually if we would want to deplete it completely, we can go in uh with a higher value than $100. So here you can explore the evidence also what the report is based on. One thing that I would like to point out here is also the security snapshot which is part of this uh uh of this uh guard that we created. So it looks at uh whether that's a potentially honeypot mintable.

We can see these are false. Are there any buy selfies? These are at zero. So that kind of lets us to then generate a report and potentially show share it with our buddies.

Yes. Thank you very much. I can order a big round of applause for him please. Okay, we have inscribed next. Um, Stella cast, get ready.

Ripcord, get ready. Presentation ready. All right. Hello. Uh hello.

Um so I created the Nscribe. Um it's a private uh payments platform for freelancers. So basically the main issue when you're a freelancer and you want to receive payments for a client is that if you give your wallet, they can see everything you own. And I saw this uh tweet about a freelancer complaining that a customer paid him and then messaged him about like why is he holding these coins and not staking it or whatever. So he felt his privacy was breached right.

So what I built is like the solution for this. Uh this can done be this can be done in many ways but basically you register in the platform create an an invoice uh put your uh wallet it can be solana it can be EVM there's a lot of options uh I'm using um near intent under the hood uh for private crosschain uh payments. So the user I create um an ENS subdomain. So you give an ENS of domain that can be resolved to a wallet and the user sends the payment to the wallet and then near gives it to their uh private shard and then send this to the destination chain. In this case uh it's Solana.

So this is an example of a transaction that I did uh on arbitum mainet. Uh I sent uh one uh dollar and this is uh address poisoning or shitcoin. This is not the transaction. Now you see how bad this is, right? This is a newly created wallet.

Okay, so ne nevertheless. So one USDC came in, one USDC came out. This is the payment from my client. They cannot see the destination wallet. It went to my Solana wallet.

This is the transaction. I received 0.98. 2% is not so bad for a for receiving a private payment. So after you create the invoice, you get a PDF that you can send to your client.

You can send them their uh wallet address. You can send them the ENS. I think ENS is easier because you're not worried of uh making an error, copy pasting, having uh having the address poisoned or something like that. Your clipboard may be poisoned with an ENS name. It's easier, right?

Um and then also this is all uh stored on its swarm also privately. I just tried it a little bit and this platform also allows you to um with the accounting because also accounting is difficult for freelancers. So you can have all your invoices and it also tracks which one have been paid and which is not paid. And this is all like it's not production ready. It's a hackathon project but this is live information.

It works on arbitron mainet right. So, if you go to the pay page, the client can pay here and this will go to the to the ENS address and then to the my destination wallet. And also one last thing that I did for the accounting purposes is like you can see all your invoices by month and then export this as a CSV file. So, you can import it into your into your accounting program and then make your life easy, right? Freelancing is already hard enough.

So this is the project. I I like privacy. So and I like testing new technologies. So that's why I do a lot of hackathons. Thank you very much.

Thank you very much. Enscribe. I think um yeah, a lot of people can relate to that problem of when you need to send someone your wallet and the whole thing gets docked. Yes. Um we have Stellcast.

Oh, it's a group of three people. Oh well, incredible. Welcome. All three of you need to speak. So, we're presenting Stellarcast.

This is a streaming platform that's privacy oriented. Uh the problem we're trying to solve or we're trying to make is a stream platform that also allows monetization. Uh the problem with monetization of blockchain is that a lot of it is uh publicly viewable and in some cases in some industries you also want to retain uh uh privacy and not uh let anyone else know what you're paying for what you're seeing. Uh so what we did is uh we uh made a way that you can there were two points of monetization we wanted to focus on. So either donations or tips which currently moves most of the streaming industry but also pay-per-view.

So like in sporting events or other cases like that that you need to pay to gain access to a stream. Um, and the way we did this, if you move on, um, yeah, one more. Um, basically the host or the streamer can, uh, create the NFT on the NFT registry to publish the stream to let viewers know that they are providing a stream in specific categories, give it a title, give it a thumbnail, stuff like that. Um then uh the user pays but he doesn't directly pay the uh wallet of the ENS that is uh the personality that's streaming he's paying a stealth wallet that is generated from the meta stealth wallet in the ENX text records of the streamer. So uh then basically anyone else who's trying to snoop or see what he's doing, they see that he's paying a random wallet, but in reality then the streamer can go and uh basically go over the list of announcements of the stealth wallet transactions, finds which stealth wallets belongs to him and uh use that money uh for himself with his key that he can claim it and that also uh the payment is what provides access uh for the viewer to watch stream.

So I think now Jonathan can also demonstrate how it works.

So we created here so it will look like unknown uh Twitch or streaming services. Then uh a known ENS that is a creator in the platform that wants to initiate a stream. He comes with his ENS. He connects to it and now he wants to open a new stream. He goes to the go live button and then he types let's say uh demo one and then he's choosing the category and he already created beforehand or creating new when he's going live a set of stealth meta addresses on ENS it will look something like this it's the new ERC 55664 that ENS are supporting uh where you have a set of private keys and public keys that are being computed in order to derive here a stealth meta address that later users can choose a random R that will be later computed for this stealth address in order to transfer secretly money to.

So here I already have I set it up before and I can bring it from my computer. I saved it and it tells me to sign with an ENS so we can verify that is indeed owning it. Uh demo one and then it's creating the room. This is going to the NFT streaming uh directory creating the stream. Uh the website has no back end besides the blockchain.

It's now uh viewing us. We can go to another uh viewer. There's a new stream coming here. He's connected with another wallet as a viewer and then he wants to join the stream. We set it up the price and now he needs to pay for it.

[snorts] is paying for the stream, getting an access for it, getting uh password encrypted for accessing the stream from the distance. After this is confirmed and everything is all right, he's getting an access to it connecting to the host. The host can see that someone paid. So we see the small amount and then in the middle of the in the stream if he really likes what the streaming is doing then he can contribute make a tip make a donation to the streamer and then also this is being transferred to the stealth address. So the creator, the streamer can still retain his um ENS, the all of his credentials and all of his um reputation for the ENS, but still manage to get money to a stealth address that can be later secretly brought to whatever he wants.

Yes, thank you very much. I think that's a very incredible idea you keep with um you know live streaming going very yeah it's very popular these days and like uh in live streaming meta glasses or whatever so yeah I think this actually a great idea so good luck okay Ripcord do we have Ripcord in the house okay Ripcord Hi. Uh my name is Thomas and I've built Ripcord for this hackathon. Uh most DeFi security focus on the question can attackers break the code but what Ripcord's trying to answer is the question what can the people who are authorized to control the protocol actually do and most importantly can users exit before authorized controllers can act. So three questions need to be answered before you deploy uh capital into a DeFi which are who controls the who controls the protocol, how quickly can they act and how quickly can you exit.

Ripcourt turns control into a decision window. So uh it it creates a power map uh which shows who controls upgrades, roles and exit restrictions and uh creates a notice. So it shows the shortest enforce the day across the relevant authority routes and uh at last it does an exit proof by executing a fork in um that tests whether an open exit can be closed. So to use the program you let's see uh this is the website you simply click on scan an address here you paste the contract address of a protocol and choose what kind of scan you want to run uh here I have a report that has already been uh generated from from uh analyzing a contract and here we can see the withdraw experiment where at first the withdrawal was establish established and uh it all went through. But after the privilege mutation was enabled by enabling this authority that has no time lock uh the withdraw was blocked and that means that the protocol can uh pause a withdrawals anytime they want without any notice.

All right. So this is the power map. The power map shows the contract then shows the implementation, the proxy admin and the authority. This authority basically tells that the proxy admin can only be upgraded uh after the time lock of 2 days. But there's a different branch here which is the authority of say five of nine which has no time lock.

And we tested this by uh by using a fork and enabling this uh authority. And it shows that this authority can actually pass withdrawals of the target. So how ripart recognizes and ferite function is by extracting the four bite ids matching a known signature uh that is handwritten now uh identifying the guard and verifying the observed effect. Ripcord tests whether the two actually bind. So uh it tries to change the time lock and if it says as it says call must come from time lock.

So the two days actually does bind but because there's a different branch with no time lock uh the withdrawal reverts when that authority is enabled. So instead of the two days time lock that they show the actual time lock is 0 seconds. Uh mobile proposes the next assets to test. So mobile gives back all the assets that are connected to the protocol contract. Then propose to uh Ripcord to analyze those on a fork as well.

And Ripcourt only uses the assets that are verified by the protocol because of course uh protocol addresses can contain uh fake tokens or uh fishing alerts. Uh in the future I want to create a AI layer to uh to be able to recognize more bytes. I want to test complete failure paths like more exit adapters, governance executions, oracle changes, liquidity shocks and mis mass withdrawal. And I want to enable continuous alerts. So if anything in the background of the protocol changes without them alerting the user, the user will be alerted by Ripcord.

Uh thank you for listening.

Thank you very much Ripcord. [applause] Um, next we would like to welcome Tete to stage. Are you ready Tete? Yeah. Oh.

Okay. Hello, my name is Alex and I'm presenting project called Tetat. It is a French word for meaning um like head-to-head which uh means that the conversation that happens in that way remains private and yeah and I use also French names uh throughout the demo because I used to learn French for 11 years but I barely could speak but I like uh French words so it's about ENS Uh let's imagine we want to use those uh like ENS names uh like our um chat handles. So pretty easy idea, right? But if we don't uh apply additional measures, we could have pretty unencrypted chat if you want to do it like Telegram does for example.

And we will have like the uh the the messages themselves and also the metadata exposed to an external observer. We could do better. We could for example uh exchange private public key pairs between uh participants and then we could uh make uh the messages private. Uh but also uh but we still leaking the metadata. So someone uh they don't know that Pierre and Marie um what what they are talking about but they will know that they are connected and they could uh like create a graph of connections which also kind of leaking of privacy and uh if we u encrypt the metadata then everything will be private and for external app server it will be kind of uh unclear what is happening there.

So what is happening tetat stays tetat and also what I wanted to try is to make it as simple as possible so uh non uh technical people could probably use it for their uh use cases and here I have an uh screenshot but better I would do a live demo. Hey, so live demo uh imagine we are one participant and we will connect our wallet and we are thinking that uh like participants will bring their own uh ENS names and what they have to do is enable tatet meaning that they need to publish their public key and it will be shown here on on the records of the ENS record. So this is the public key and uh I will really quickly do this in another wallet as well. And uh after that they could just start exchanging uh encrypted messages with their counterparty in un identifiable chat. So for example, we could send hello and the other guy and this is deliberately without address book.

You should know the uh ENS name of your uh correspondent and yeah it will see and uh they could respond back and uh this is because it's encrypted end to end it is stored in database in any data. It could be stored in any database and this is just encrypted cipher text. So you could not if you found this database you could not derive who is talking with whom and what they are saying and this is based on ENS. So you besides having an ENS and ability to send a single transaction you could um kind of access a very simple privacy messaging solution. Thank you so much.

That's the tech. Thank you very much for presentation on tetat. Okay, ghost name. Do we have you in the house? Oh, okay.

ZK Reddit can get ready at the same time. Yeah, let's try that.

Perfect. Um hello everybody. Yeah, so an ENS name is um is a very good way to to have identity in crypto, but it's also uh one of the worst privacy leaks um there. I was um doxed by a conference that won't be named a couple of years ago. Um I was moderating a privacy panel and they published my real name and face on axe for the first time.

So I lost my cool crypto identity at that point. And until this day in this hackathon really I've been uh you know kind of not really able to use my ENS name in the way that I would like to. So I built ghost name to be able to claw back my privacy and to be able to use this address by using the uh ER ERC 5564 stealth addresses in combination with EIP 7700 uh 7702 which allows you to uh sponsor the gas funds for new transactions. So we can't go back in time unfortunately. I can't uh obusate my history but we can look forward to the future.

Um yeah, so essentially if you're familiar with Revolute and the way you can generate a new card for each purchase, um here we can generate these uh sort of one-time stealth addresses for each each transaction. Um yeah, so essentially without the viewing key, you wouldn't be able to see uh the link between those addresses and the the actual ENS name. Um yeah, you can resolve as many of these addresses as you want. Um you can create hundreds of them if you want. I'm just going to do three for the purposes of this demo.

Um but the the other challenge that I faced is when you when you fund a wallet um for the first time with with the gas fees, it actually links it back to the original original spend. So here I integrated the 7702s and um the sponsor submits this type four transaction under the EIP um and pays the gas for the receiving wallet to to then uh do the transactions with the funds it's received. Um yeah, you can check everything on chain but um I want to be clear that what's protected here is future receiving addresses being linked to the ENS name by a passive observer. is this isn't going to help you if you know the cops are after you or chain analysis is is is [laughter] tracing your funds. Um but it is useful if you want to just not have your financial life visible to everybody on chain.

Um yeah deriviation is local. So no gateway learns of the destination. I think that's differentiator from other projects that are based on 5564 and uh yeah avoiding the recipient address reuses is quite crucial here as well. Um obviously we can't cover uh we can't protect um visibility on ENS ownership or timing and RPC metadata or compromised devices. So let's try it out.

Um yeah so this is a well-known ENS name here. We can audit it first of all and uh here obviously there's no staff meta address. So we're going to assign a ghost name and then from the ghost name we can derive some keys and again you can derive as many of these as you want for receiving addresses. Here the viewing key is recognize the the uh the keys and then we can verify some payments. Oops.

Those are live on Sepulia. Here's the payment. Here is the announcement. And we can also sponsor the exit from those addresses as well. So, we're sponsoring here the because these stealth addresses don't have any gas at the moment.

Uh funding it from the original wallet again will relink it. So, instead the sponsor is paying instead. And here we can see that that is simply a contract address delegated. Okay. Yeah, I think that's everything.

Thank you everybody. Very thank you. Ghost name. [applause] This way we can have with the same ENS we can have multiple stealth addresses, right? So that works.

Yeah. Thank you. Um next I want to um invite Z credit to the stage. I thought it's ZK Reddit but um no it's Z credit. Um, yeah.

Yeah.

Yeah, we uh we heard that before.

It's a bunch. It's a whole group. So, it's a big project.

Uh, hello everyone. Today getting a DeFi loan either means one of two things usually uh either overcolaterizing the loan or revealing a lot of financial history to collaterize the loan and prove you're trust trustworthy. So we built a solution for this uh it's called Zredit. It's a privacy preserving lending platform on Solana. Uh what we aim to do is um yeah borrowers and credit uh approvers can uh trade in an open marketplace and can verify themselves through an ENS domain uh and try to collateralize loans without revealing financial history through zero knowledge proofs that are generated.

Uh so my colleague is going to uh demo how it works and uh hopefully it uh it makes sense. So

yeah. So hello everyone. Uh my name is Maurice. I'm going to give you a small demonstration about what we actually made during the past couple of days. Um so yeah, as my colleague said, it's like a marketplace for borrowers and lenders of uh cryptocurrency.

Um right now we need to connect my MetaMask uh wallet first for the ENS domain. This is on the Sapoleon network uh like the def network right now. Uh just for testing purposes I can confirm this. Then it's uh automatically pulling my ENS uh name. Uh in this case it's Mariss E.

Then I can connect my Phantom wallet and then it reads the uh Solana live from the mainet. Uh and I had to put some money on it. So right now there's about $15 on the account and it reads it here $15. Um so this is my private passport and it generates it from what it can read from the mainet. Uh right now it says my wallet is zero months old.

That's true because I created it yesterday. Um and those four boxes here are actually the uh like the weights uh the policy needs and they can be adjusted later if that's needed like according to the situation. You can change it afterwards. Um

so the way these weights are currently configured it basically pulls them uh creates a zero knowledge proof and then on the side of the the credit provider uh they get the proof that the um conditions that they set are being met and the lender can actually see several different offers and can choose the one that's most best fitting for them. So you have interest rates, you have other stuff. So it's kind of an open marketplace. Yeah. So, uh, good to notice on top there's like two buttons, one for request the credit and one for providing the credit.

Uh, throughout the demo here, I'm going to show both screens mixed up. Uh, that's just for the demo purposes. We tested it on the live website. So, we can actually u but this this is just for the two PUVs at the same time because I have no two screens here. Um, so we can continue to configuring the terms.

So, let's say I want to borrow 10,000 USDC uh with a first loss deposit of maybe $5,000 for a course of 30 days. And of course, that's not a real number because I only have $15 in my account. So, that's not going to work. Um, but for the demo, this will work. Um, so right now I have a listing.

I've created a listing of 10,000 uh on the market. And now we can actually switch the view. So, pay attention. Uh, I'm opening the other POV. So this one is to provide the credit.

Uh keep that in mind. So now there's one listed uh uh one list that's seeking capital. Um and we can actually underwrite this. So it it never sees how many uh Solana I have on my account. It just knows uh through ZK what uh actually is confirmed.

So right now this is the term these are the terms for the for the lender for the pro one the providing credit uh the minimum allowed allowed as collateral is $1 and that's I can put it higher but it doesn't work because I don't have 10k on my Solana account so I just put it on $1 now um no history requirement for my account because it once again I just created yesterday but in a real life scenario uh you would you would want this a bit higher like 12 months or 18 months uh to be more trustworthy, you know.

And so basically, we're going to go through the weights u that these are the four weights. The longer of course your account exists, it's more trustworthy. Uh the collateral you can set a minimum uh the more uh you can have a quality for the collateral. So stable coins of course are preferred. uh and liquidation history we looked into uh is a possible weight to be looked at but that's currently kind of a revealer of financial history.

So we thought it wouldn't be very privacy focused. Uh so these are the ways you can configure them as the uh provider. So you go to the next side and then the the borrower actually sees the the requirements and he can choose to generate the proof and then the provider will see whether he checks all the the conditions. In this case conditions are satisfied. So you can continue with the loan.

Yeah. So right now um this policy is satisfied according to the terms we set. So both match. Now we're going to switch again to the other POV. The

I'm so sorry. That's time.

That's time.

Okay.

Okay.

Yeah. Thank you very much.

Okay. Next we have uh MSG Punk. Okay. Uh so this is message punk. Um message punk is uh uh basically a little tool that um I built because I kind of needed something like that.

Um, I was building a static website and I wanted a contact form and uh, generally when you build a static website and you need a contact form, you usually have to go through some random uh, third-party uh, uh, form provider that um, basically takes all of your leads uh, and takes their email addresses and um, sells them to the highest bidder or just spams the hell out of them. And so I thought, well, um, we can do better. And so uh I built an end to-end encrypted um uh message form uh system. Um basically the way it works is um within the app uh it creates uses a uh um a a seed phrase to generate a bunch of keys and um for basically you can create new forms. Um so we'll create one now.

forum. Okay. And we publish. And you'll notice that um each form's got its own little avatar. The avatar is based on the um age key that um the form's encrypted to.

And then I've got a little link here to go and open it. Um in the future there'll be a form builder, so you can actually pick and choose which things you want to put in there. Um there we go. So, uh, this form's just got like a couple of things. It's got, uh, that's really bad.

Uh, the the, uh, the avatar is very small. I'm sorry about that. But, um, this is a just a proof of concept. So, we can put in some some information. All right.

All right. And um okay, we can submit the form. And then if we go back to the app and go into our into our form, we can see a reply. Okay, so then we got our data up there. And I'll just see if I can just quickly move this window that work.

Okay, so this is what's happening here is that's actually just a dump of how form gets saved. Currently, it's just being saved as a file. And there you've got like the form JSON coming in. So, it's completely end to end encrypted uh encrypted with age. Um the little uh the little Let's see if we can do this.

Go back. Yeah, the little uh little avatars here. You could um like I don't know if you saw that was on the form as well. you can kind of publish those in your website so that at least you know when you're filling out one of these forms that it's actually going to the person whose website it is that you're doing. So I think I think the use case here could be like you're going for a job and you're maybe you're using a recruiter but you want to just know that there's a form and when you're giving them your information uh you know that it's being encrypted and sent to the correct person.

So that's message one. Thank you very much. Last but not least, we have a guess. Is that is that about right?

About right.

Ages. Okay. I'm not Greek enough, so [laughter] it's fine. Hello everyone. I'm Ron.

Today I will be presenting uh Aegis. But before I explain exactly what the solution is, I'll start with a problem by telling you a little story about the Breakfast Club. I don't know if you guys saw, but there is a breakfast club branch really nearby to here and they have a website and I can contact them using that website. But similarly to what MSG Punk was saying, um to fill out this contact form, I need to put in all kinds of details. And why does the Breakfast Club need to know my number and my email and my full name and my blood test results?

You know, this is way too much. And it's a GDPR problem basically. H because if they leak it then my privacy is done for. And not only that, the company Uber also had to pay for this GDPR mistake. A fine sum of €290 million euros and they were leaking uh they were sending their data to the US of their drivers without the consent of the drivers.

So our take on the solution is ages and basically we flip the problem on its head. Um we do communication without share without collecting personal data. So basically instead of bringing your own identity and your own details to contact the business the business will give you an identity that they create and because there is less data then there is less GDPR risk. You cannot leak data that you don't have. Right?

Let me just explain and show quickly what it looks like. Basically, a business would buy a domain, configure some things on ENS for that domain, uh maybe deploy a few contracts, and then they will set an inbox [snorts] for the end user. They would go to the bank or the bakery or the breakfast club's website and if they want to contact them, then they would just scan a QR code that allows them to claim an identity to get into contact with that business. Looks a little bit something like this. Basically, they go to the website and they get a QR code.

As you can see, it's a lead hasht your bank, for example, global. They scan it. And now, oh, okay. And then they're able to claim that identity and start sending messages to the bank. Now why did we choose ENS for this solution?

Basically by not having a backend to store all of this information about the inboxes and about which inbox we should message, which inbox is for sales, which one is for that. We are able to store all of that information on the ENS and uh have no back end. And in addition to that, since a lead identity is a unique idiness.global global and the inbox is a inbox the business.global.

We are able to have verifiable um chats and calls if you send a signature with each message and uh call. [snorts] Additionally, the only thing in this situation that is linked to the end user is the wallet that the ENS points to. But we can even use ERC 5564 in order to link this identity to a stealth address and allow them to use that for messaging. In addition to that, we use swarm for um the lead state status. So unlike the unlike the business uh inbox information that can be public, you wouldn't want any sort of information about you as a lead to be public even if it's not technically linked to you.

That's why we decided to put this on swarm where only the inbox has data and sorry access to the data it needs about the lead and only the lead has access to its own data as well. So that is basically how we are able to do communication without collecting any personal data. Thank you very much.

Thank you very much for your presentation about AGUS. Agus still don't know how to pronounce it.

Okay. Yeah. Okay. Now, we've seen the 10 presentations. Let's see who won something, right?

That's what we all been waiting for. Which were the best. What did the judges think? Okay, first best privacy, forked reality. [applause] Congratulations.

Best security. Well, basically, yeah. Oh, yeah. So, my bad. My bad.

You get a a picture. So, I don't know if you have They gave you something already, but I'm not so sure. [applause] Let's keep Hey, [applause] congrats. Yeah.

[applause]

last second order. [applause] I know he doesn't want pictures that okay. Oh yeah, that's interesting.

Second order.

Yeah. [applause] [cheering]

Okay. And this is best auto tank and hackathon winner.

No. Best Auto Tank and Hackathon winner. Okay. So the yeah basically auto thank were the people who you know presented yesterday and yeah there's also a winner from that and that is Tai. Hey well done.

I remembered your presentation from yesterday very vivid. So yeah and you had a very high score so it's only it's only it's only normal that you get recognition for that. Yeah. [applause] Yeah. Okay.

Yeah.

Yeah. Sorry. Before we we go into the bounties and and the rest, I would like to to to first of all, sorry, I'm gonna take a moment here, but to to to thank all of you hackers and for anybody who wants to be on stage and for to have like a big picture with all the the hackers, feel free to join me on stage right now. No pressure. But if you want to be part of it, you can join.

Oh, yeah. We'll have uh what do we put? Who are you shilling here? Top 10. Come on.

Let's go. Congratulations everyone. Really congratulations to the top 10. Join.

I know. I know. I'm moving to the side.

[applause]

Thank you so much. Thank you so so much. And now we can go on with the Okay, now I know this is all what you want. Want the money? Where's the money?

Where's the money slide? Come on. Come on. Come on. Okay.

So, now we know. Okay. The ENS bounty winners are And by the way, is Yash here? I don't see him. Yes.

ENS. You go. You ready? Ghost names and Tet get 300 each [applause] noise. [cheering] and stittercast gets 600.

[applause] Huh? Make it rain for and scribe. [applause] Congratulations. Congratulations. Does someone want the picture with the money?

Yeah. Everyone's like, "Yeah, of course I want that. Congratulations [laughter] Sierra Hacker by the way who thank you also for helping all the time in the crypto canal telegram group like really I really appreciate that and for being a recurrent hacker and coming to congratulations what more than a hundred hackathon this guy

sorry

one of those serious ones Oh, I'm going to invite the super team very soon. But the super partner bounties from the super team Netherlands go to ZK Reddit for $350. Congratulations. Congratulations, sir. You want to do the other ones?

Drum roll for Mill from Super Team.

Thank you. Thank you. Uh, also congratulations guys, by the way. I know. I don't think we even exchanged context.

So, let's do this after this as well. Um, yeah, take a take the money shot, you know, for sure. Congrats.

Awesome. All right, let's get one more round of applause for Zeke Reddit. Number two is Hunch Trade. Give it up for Hunch Trade. Where is Hunch Trade?

No money shot. No. Very sad. they do get money. [snorts] Um, all right.

Awesome. So, I think we had some really cool projects. Also, thanks again, uh, Common Sense for hosting this amazing hackathon. Very happy to be part of this. And now, let's give it up for number one of our bounty.

Let's do some some drums. Number one goes to TI Protocol again. Awesome, sir. Great job. You did a wonderful job.

Congratulations. You want to take a picture together? Maybe.

Let's do it.

Perfect. And then I think we do a little shout out after this, right?

Okay. Ah, amazing. Beautiful. Uh, so if I did talk to you during this conference, uh, I might have tried to spread the gospel of the coliseum hackathon. Uh I think for a lot of people especially this time around it's really really interesting to uh participate in this.

It is the largest online hackathon blockchain hackathon that's going to be running uh from the 14th this month until October 12th and this time is the first time that they're running it chain agnostic. So as you can see uh they have other chains uh participating as well. [laughter] Uh so they have ETH, they have Hyperlid, they even have Robin Hood, Zcash. Uh so there's some really really cool opportunities for this. Uh I put the QR code here as well if you are interested.

Uh and you know part of being a super team is that we help anyone that would like to participate uh in this endeavor. So do sign up um and hope to see you there. Thank you. [applause and cheering]

Amazing. Okay. Oh, okay. It's raffle o'clock. Everybody grab your pink little tickets.

This is your last chance. No, I'm scaring everyone here coming in the back like what is she doing? I have the raffle bag. Okay. Oh, and I have the raffle items.

Okay, so we decided to split. And I know Trezor went through something really really awful yesterday for those who everybody checks crypto Twitter, but like there's a reason why Trez didn't uh sadly wasn't able to join Common Sense. Yeah, you know, check crypto Twitter. [laughter] It's pretty bad. Yeah, but the good news is that I received these goodies to our office address.

So, for any OPSSEAC moment here, this is a good time maybe to share like if you are going to order a hardware wallet, which I do we we had panels here about self- custody um and self- custody is really important. I do believe in in being your own bank, but also I believe in operational security and I believe in all of us being safe and I don't want to promote wrench attacks. Um, Kazar is working on an anonymizing uh the packaging because uh when I received this giant giant box of treasure uh it had treasure marketing all over it. So I was walking around Amsterdam was like this big pile of of wallets. Um they're working on it.

All right, the first We're going to win here is the keep medal where you can engrave your private keys. 24 words. Uh, as for that one and I have everybody's little tickets. This is the most manual thing to take. [laughter] Feel like I should have done this like Okay, ready?

Yeah. Okay. Number 267.

You where? 267. 26. Whoa. [screaming] [applause]

Let's go. Mo,

congratulations.

Thank you very much.

Congratulations. Congratulations, sir. It's like three numbers. Okay. Round.

Okay. Make some noise for the winner. Oh, by the way, I picked the the green one. I thought it was really pretty. This is for a Trezor [clears throat] 7.

Yeah. Yeah. Latest. Latest sexy one. It's really pretty.

Okay. Ready? Number 215. 215. No way.

[applause] Congratulations. Congratulations. Thank you. Congratulations. All the best.

Done. Congratulations to the winners. Thank you for spoiling our attendees and our guests with Model T's and with uh with the Model 7. I'm glad I asked for a bit more because at first they were only bringing us the Model T's. I'm like, no, let's give us the new stuff.

So, I'm really glad you guys could go back with that tonight. Before we go into all the the finals, I wanted to just remind that we have a walking tour at 6:30 till 8 uh with the Zcash peeps and then afterwards we're going to party at so that's for later for tonight. And I would like to thank our hackathon partners for making this possible. Like organizing hackathons and hurting cats is really really really difficult. But I would like to really from the bottom of my heart say thank you to Swarm ENS Super Team Netherlands and Mobila for spoiling us.

Thank you so much. Thank you to our partners [applause] and these are all the partners that made it possible. You don't realize [applause] in a bare market. Thank you, Colin. In a bare market to have this to have Zcash, Zano, Privacy Pools, Dash, Cyber Capital, Swarm, Rail Gun, Zurex, Bow, Super Team, Netherlands, Mobula Dash again.

Never mind. Edge, [laughter] ENS, NanoGPT, Mocha, Metroen, Near Intense. I know I'm forgetting some, but thank you. really uh they believe in what we're pulling off. They like the community we have.

They like the intentional um the intentional and sort of the driven aspect of this conference. And I'm sure you could have seen it through the speakers we invited and the panel discussions we had. So, thank you so much. Thank you so much to our partners.