Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Zcash x NEAR Intents Hackathon
Recorded: March 28, 2025 Duration: 0:47:00Space Recording
Short Summary
In a dynamic session of DevHub Live, the Zcash and Near Intense Hackathon is spotlighted, featuring exciting project tracks focused on AI agents, private DeFi, and cross-chain interoperability. Participants are encouraged to innovate and collaborate, with an extended deadline to enhance their projects.
Full Transcription
Outro Music What you want, what you want, what you want, what you want, what you want. The next step is to make sure that the video. Welcome, welcome everyone for this new special edition of DevHub Live. This time we'll talk with the developer of Zcash
and DevHub about the Zcash and Near Intense Hackathon.
And we got this special edition for you, the hackers,
the people are building for that hackathon.
Just bring your questions,
showcase your ideas in the comment section.
And we get with us today please welcome
Paku from zcash hello everyone nice to be here and with us is uh Gije from near dev hub hi hi
everyone hi everyone thank you so much for having me. Thank you.
Thank you for coming.
We get an exciting update that the new deadline for the hackathon will be this Sunday at midnight.
So you got one more weekend to hack.
So it's 48 hours full of coding.
hours full of coding and that's the goal of this session when you can you know like if you're having
And that's the goal of this session.
if you're finding a blocker uh something is not working with the project or you just want to you
know like share your ideas and and check in like if it's in tune with the with the tracks just
came and talked with us in the comments.
So a quick review here.
I would like Paco if you want with us
review the tracks and add some comments.
Sorry, can you hear me?
Okay.
Yeah.
Just again, everything is okay.
Okay.
So can we check the tracks for a moment?
So the first theme that we're covering is AI agents for Zcash.
It's building an AI-powered trading bot that store manage and transact ZEC across the blockchain.
The last session we were talking about Zcash and ZEC. If you don't mind, Paco, to make a quick
review again about ZEC for the people who are are joining last minute to this hackathon.
Yeah, sure.
So like 60 seconds of Ccash crash course is a big fork from Bitcoin core in 2015, which was added a zero knowledge proofs to bring privacy to the Bitcoin protocol.
And long story short, the technology was awesome, but very, very new at the time. So Ccash became its own project.
And there have been many updates to the Ccash protocol
until today, but because of being originated
as a Bitcoin fork, Ccash has two kinds of transactions.
Basically one kind of transactions is the ccash transparent
um a part of a protocol which is basically um bitcoin transactions and you take so model
um that that you already know of and then you have the possibility to actually go to the shielded side of the protocol, which are the sapling and the orchard pools, which actually leverage the zero knowledge technology
that provides complete anonymity and privacy by using zero knowledge proofs to prove that you own a certain amount of ZEC
and that you are legitimately spending it and that you're not double spending it.
And that allows you to transact in a decentralized way
and being unlinkable, private, and hiding the recipient, the receiver and the
amount of the transaction that will be in the blockchain but nobody else other than the person
receiving the funds and the person sending the funds will know some of the details of the
transaction and you won't see
anything on the blockchain that's basically what ccash is this fabulous internet money internet cash
awesome and regarding the the the track of ai agents for ccash and and just before jumping into the shield swaps
and what would be the ideal agent
that you would like to see running on Zcash
near intents?
Yeah, I think that what near brings to Zcash
is the ability of combined Zec with DeFi.
And it would be awesome to see bots that can do different trades
and identify opportunities to swap ZEC and for example give you I don't know it could be give you what the
best trade is for in different chains like using different assets and also it could be a good use
of also a good addition would be that these agents could also tell you via the resulting transaction, like how private it will be.
And also plus bonus points if you can leverage anything of the Shield of protocol.
We know that it's not that simple. It's not straightforward.
it's not straightforward uh but even if you can like do a transparent exec uh poc and then
show a roadmap on how you think you could actually include uh shoot the shield protocol um it's uh
it's a really good start that's actually the the second track uh that we offer in this
acaton is the private defy, shield of swap, portfolio management
and intent driven assets trading.
The third track is the cross chain interoperability.
So it's Zcash enabled intent based transactions
across Bitcoin, ETH, SOL and other tokens.
And I would love Gija if you can bring some light
about what Near Intense is for the people
who are joining last minute in this hackathon.
And by the way, you can see the link scrolling in your screen
if you want to join the hackathon.
Nice, yes. in your screen if you want to join the hackathon nice yes so near intense is basically just
um a high level declaration of what our user wants to achieve right like think of uh of it as a way
of telling the blockchain what you want to do and not how you want to do it okay so instead of saying
to do it okay so instead of saying i want to swap this for this in this exact way like by calling
this a smart contract and executing this function here and this function there you just simply sign
a message saying like i would like to swap token a for token b at the best price And what happens is that you sign this intent with your NEAR account, right? And then
you send it to a network of solvers or you publish it. And there's a network of solvers that are out
there listening for intents. And they can say, for example, you want to swap token A for token B?
token A for token B, it's fine.
If you provide token A, I can provide this amount of token B, right?
And what happens is that you broadcast your intent to the solver network,
the solver network gives you an answer,
and that all of the settlements happens on the blockchain
where you can prove that something happened.
For example, swapping tokens is one of the simplest things right because i as a user can prove to you that i have a transaction
hash that shows that i deposit some token right like that i put it there and it's waiting for
your swap and you can prove as a solver or as a provider right of liquidity that you put token B in the chain, right? And that the swap happened. And well,
this is basically the most basic idea, right? Like, and ideally you could take this even further,
right? Because you could have solvers for absolutely everything, including, hey, I want to
give a hundred dollars in exchange of, or I want to buy headphones.
And then a solver would say, if you provide 100 USDT, I can provide you with headphones in real life.
Then I can show you that I provided 100 USDT because there's a transaction hash.
But now, how are you going to show me, or how is the solver going to show me that they actually sent something?
me or you know like how is the solver going to show me that they actually send something right
so the the solver could you know like put on chain hey okay perfect like here's the trend the number
of the the tracking number of you know like i don't know like the amazon package that i'm sending you
right and therefore like i would you know like will i receive the product or not and therefore
like another important part of intense is like problem solving or like dispute solving disputes right like and how to solve them but
this is beyond this hackathon like we can you know we just like the previous part of uh maybe
handling uh tokens it's enough for now thank you and and there's a question for for both of you i would like to to
to hear what are your thoughts about real use cases to use uh intense for for shielded swaps
why using zcash in in in these cases what are the the real use cases that you may find that is important
to keep privacy on this transaction and to to to keep the transaction safe and and
and shield some of the of the information that is happening uh so what are your thoughts about it
what will be the the use cases that you may find for for this integration well i think
that um it's um it's interesting for example um going to this kind of like solver that can provide
you with some um some goods um for example how would you send your address, your shipping address for those headphones?
And then you could use Ccash Shielded Memo to actually send that information.
The Ccash shielded transactions have an encrypted memo
of 512 characters or bytes that can contain
either arbitrary bytes or Unicode bytes
that can be read in form of text.
So you could actually encrypt your information so that your shipping details are safe.
And also you could provide a reply to address so that the solver can know where to send you the tracking number.
to send you the tracking number.
For example, it may be able to,
it might be required to sign some message for out of code,
but some dispute resolution that it can prove
that it actually send you the tracking number,
but then what it can do as well
is to actually provide the real information only to you by using your
the shielded address you provided in your memo so that could be one thing
and for example and then well you could for example if you had a, instead of a, like a physical product, you could say,
oh, I need, I want a eSIM or some eSIM or phone
or prepaid line with, I don't know, two ZEC of credit.
And then the solver could actually say,
yeah, okay, I can do that.
And it can acquire the e-stream for you
and send you the details over the shielded memo
over there and things like that,
where this messaging,
although it's not capable of holding a lot of information,
it should be capable of holding enough information
for you to exchange like the crucial parts of the of your um intent uh with the solver
very interesting let me ask you a question taku can you when you do what can you by using you
know this shielded technology hide what is my original account?
Can I prove to you that I made a payment to you without you knowing my original account?
Yes, because when you make a payment to me, I will receive your payment, but I wouldn't know that you are the one sending it.
So what you can do is to send me your reply account.
It should be possible and it is possible by the protocol, but I think that we haven't implemented that.
It's to actually sign your,
you can provide a signature
that actually authenticates your memo.
But I think that that will require
that we implement a few things that we haven't yet,
but that we will implement in the next,
probably in the next few months
because i was thinking that something that would be interesting for example is that
you know with with the current idea that i just plain of like you know buying something online
one of the issues that you know like one one interesting issue is that imagine that i go
and buy something with amazon with you know my account my account, Gile.Nia, right? And I just want to pay Amazon.
I don't necessarily want Amazon to know how much money I have in my account, right?
Like, neither, you know, like, the history of transactions of Gile.Nia.
So, you know, like, even before, you know, like, of course, like, hashing my address,
which I would also want, you know, like, maybe if you're talking with a specific, you know,
want you know like maybe if you are maybe if you're talking with a specific you know uh if i
already pay you maybe you can send me to your website to just put like my address but when i
pay you it will be very nice that you don't know how much money i have in my wallet do you think
that that's the idea of ccash that it's there's nothing to do or to develop there because that's
That's how shielded Ccash works.
What usually happens
when some entity wants to accrue that you pay,
that they have received payment from a sender,
what they do is they generate a new shielded address
that is unique for that use case, right?
They know that there's no
problem if you reuse a shielded address because given that the everything is encrypted and it's
using zero knowledge proofs nothing of the shielded address is revealed publicly on the blockchain. Only the fee of the transaction, which CCASH uses a pseudo-uniform fee,
which all transactions that look alike
will have the same fee.
So it's not statistically possible
to identify a Shiloh transaction from the fee
because they all use similar fees
for the same amount of inputs and outputs.
So you can buy whatever and you don't need to worry about,
if this is your main account, if it's your savings account,
then since the receiver can't learn anything about your holdings,
you don't have to be jumping through hoops on,
hey, I need to, I guess, jump through this exchange or try to hit this mixnet to just send this $50.
I need to buy this headphone.
So the headphone store doesn't know that I've been huddling for some time and I've been doing well.
Right? I've been huddling for some time and I've been doing well.
Right?
So that's not a problem. Yeah, and these shielded transactions,
do they follow the same idea of like a Bitcoin transaction
that I just signed with my account?
account or like do they, are they created in a different way?
Or are they created in a different way?
They're similarly created as a Bitcoin.
They do follow a different kind of,
they are not UTXOs, but shielded nodes,
which a shielded node is very similar
to what a paper note is for cash.
With the differences that you will have different, you don't have fixed amounts for those notes, right?
And what you can do,
what you do when you send a transaction
is that you send the,
you spend your note by creating a serial knowledge proof
that says, hey, I have this note
that has not been spent ever in the blockchain, and I'll commit this zero knowledge proof to this commitment tree of the Ccash blockchain.
That doesn't happen in Bitcoin, for example.
Because in Bitcoin, everything is transparent, so you don't need to prove anything.
Like the blockchain can be verified by the naked eye.
And in this case, since everything is shielded,
what you do is you rely on zero-notch cryptography
to prove that you haven't spent this node,
and you will give the zero-notch proof to the receiver
and to the full node that will be broadcasting your transaction that will actually verify that it can actually verify the proof. you will reveal a nullifier, which is a specific value that you derive from with your private keys
to prove that once you reveal a new nullifier,
you said, oh, this nullifier is actually the thing
that marks my Ccash as spent.
And now the Ccash, I don't own that Ccash anymore.
I spend it.
And now, you know, the new owner of Zec will have this new node that will have its own notifier, etc.
And the chain goes forward.
So that's basically in a nutshell what happens.
And the difference is that you can't go looking for
shielded nodes in the blockchain because you won't be able to see
them until the owners reveal their nullifiers and spend them.
But even though then you won't be able to see any details of
the of that spending, you only see the transaction. And that's
it like the block header, the transaction ID and the fee.
Okay. And then non-shilled transactions,
they just act as Bitcoin transactions, right?
Like I would have my own sign-ed, right?
The tricky part is that you can yes you can go from one protocol to the other like
if you have shielded notes and you provide me your transparent address for example like when you
deposit into near intense what actually happens is that i'm deshielding my notes and those notes will
is that I'm deshielding my nodes,
and those nodes will now be revealed their value, right?
And they will belong to the new Ccash transparent address
that the near intents UI has given me to deposit.
But the near intents or near anyone out there will be able to know who i am or what is
the address i'm sending the those shielded notes from um which gives you this possibility of being
shielded and then selectively choose um when to interact with the transparent blockchain. And that's the same when you withdraw.
Usually, for example, when I want to buy some ZEC
and somebody, let's say somebody pays me USDT
and I want to buy ZEC with it.
So I go to the new intent and say,
hey, okay, I'll deposit this USDT.
And then I want to exchange it with
with Zek. So then I'll have to provide my withdraw address and near currently supports
transparent addresses only so I can just grab my wallet, I can grab either my Zyngo wallet or my Sashi wallet or Y wallet
and just copy my transparent address
and put in the UI of near intense.
I will tap withdraw and it will send me the transparent Zek.
So while it's like Zyngo or Sashi,
they are shielded first.
So they'll make you always shield your coins before you send them everywhere, anywhere else.
So they will just pick up that transparent address and say, okay, let's shield this font.
So they will send the transparent stack into one of your shielded addresses,
and those 50 formerly USDT, now converted into ZEC,
will be shielded and jump off the transparent pool into the shielded pool,
and then you won't see where they are in the blog explorer.
You will see a transaction where there were some set
as input and there were some shielded outputs and some fee and that's it um
and so i was wondering uh because for example we have this concept in near called chain
abstraction right and and we have uh basically a an npc that allows us to sign transactions for
other protocols right so you have a near account i don't know if if you're familiar with this but
maybe there's people you know watching that it's not familiar with this basically you have your
near account and you have the npc network that you can just you know think of it as a wallet and basically by
making your account call a smart contract on chain you will get a signature for random bytes
those random bytes can particularly be a transaction in bitcoin a transaction in ethereum
right or in this case a transaction in ccash for what you were saying like a transparent address right so i was wondering
do you think that you will give up too much privacy if for example i have my near account
i use my near account through near intense to get some ccash and we draw that ccash into here's my
near account here's my ccash to deposit it in a Ccash account that my near account can control, right? Like by signing transactions. So now my near account can sign transactions for this Ccash account, right?
shield the C cache that I have in my transparent account.
For that, I guess that I would have to use my near account
to sign a couple of messages.
But I would sign those couple of messages
through the MPC.
So everyone will be seeing what kind of message
I'm trying to sign.
So do you think that that would make it not transparent
at all because you know, like there I'm gonna be giving away
like, hey, I'm actually depositing in this shielded account.
And therefore, you know, that's already, you know,
my shielded account makes no sense anymore.
To shield from the MPC,
I will have to like look it up really into detail,
but there are a couple of things that you will have to do,
but maybe like you could have a,
if you,
if you have the same account address derivation in,
in the shielded wallet that you control, then you could create, for example, the Ccash dev tool on the CLI, you could create a partially created Ccash transaction,
which is a format that is inspired on the partially created Bitcoin transaction,
which actually is all the metadata necessary to create
a non-signed or non-authorized transaction.
So then that transaction,
the only thing that it's lacking is the signature.
So then if you can sign that PCZT, depending on what you reveal of it in the blockchain, then that's how much privacy you'll be giving up in the process.
But you can definitely sign the transaction separately
from the transaction creation process.
And why do I bring this up?
It's because to create a serial knowledge proof,
you need certain things that it will be
pretty complicated to like you have to basically create a way to for a near intent to know how to
grab a viewing key and sync the part of a blockchain to create the commitments and all the moon math to actually create
the zero knowledge proof.
So that heavy loading process,
maybe you can do it with a CLI wallet
or some wallet of some kind that is Ccash dedicated.
And then the signature process,
you could delegate it to the near MPC,
but it will have to support like Red DSA signatures,
for example, for Orchard.
So it's obviously some heavy lifting,
probably not something that you can do before Sunday.
Well, maybe if you can, I guess,
will you win the hackathon, maybe if you can, I guess, will you win the hackathon?
Yeah, we all offer you a job, right?
Yes.
I don't know.
People will offer you some jobs, probably.
Actually, sorry for the interruption.
These are great ideas, but I would love to read what the people are building for this hackathon.
So for the listeners who are hacking this opportunity, please share your thoughts and your project on the comments and if you have any questions.
Regarding these operations, Guillermo, how do you foresee that you can leverage an agent for this transaction?
Going beyond this interface improvement or avoiding the user experience using an agent,
how to improve these decisions and these callings using an agent, how to improve these decisions
and these callings using an agent.
Well, actually I really liked the ideas
that Pacquiao already shared, like saying,
hey, how, like I'm gonna be doing something
that I suppose that is private in Ccash,
how safe, you know, my agent think that this is.
And what we were talking so far,
like what we have been talking so far
is actually very relevant, right?
Because it might be hard to maybe create all of these shielded transactions or, you know, like this concept of shielded accounts in pure near blockchain with, you know, pure smart contracts calls to the MPC.
But agents are actually arbitrary Python code.
So you could offload a lot of this logic into libraries that maybe already exist
or libraries that at least, you know, like can exist or libraries that, you know,
in the worst cases now you just use external services, right?
Like you just call some service
that already does the heavy lifting for you.
And therefore, like your agent could be the one that,
just says like, okay, I use near intense
in order to be onboarding to see cash.
Now I use all the see cash technology
to do like a private payment.
Now I can prove that I made that payment or through the, you know, like the shield of the payment,
I just give the instructions on how something should behave or where should I get the answer.
And again, arbitrary code, I can do whatever I want.
I can just wait until I see that common answer and then come back to my user and say like, hey,
it's what I just bought something for you and you didn't have to reveal that you actually pay with gilead.near where you
keep you know like a certain amount of money because this is something that we keep forgetting
in in blockchain about like how being people think that sometimes you just want to hide things because
you're doing something bad but uh sometimes you also don't want to be super transparent right like i i have my account with a
certain amount of money and i don't want people to know what money i have because that you know like
might be i might become like a target of advertisement i might become you know i don't
want you to know what i was doing like what are my interests on chain or like i i i want some you know like
when i buy with my debit card i don't expose my whole life to the shop that i have in the corner
of my house right and that that just doesn't happen when i use it near or any other normal
cryptocurrency because like there's a link there's an account linked to that payment so yeah you know the agent could
use all of this technology to say hey i off boarded to a private place so you don't have to be exposed
and expose your whole financial life yeah something that would be um like tapping into
something you said first i love something that um chris ncombe from a core developer of Ccash from ECC said that there's no free economic system without privacy.
Because basically, if you have a shop or you have a store and you have different kinds of customers, it's probably that you have some price policies that are private to you and are the base of your business model.
And it's probable that you don't charge the same amount to those same people.
Like, for example, you have customers that are regular customers, and then you have a
courtesy discount for them, but not necessarily you don't want that to know
for new customers or for your competitors to know.
And if you like use a Transfarm blockchain
and your competitors can figure out
or can send a fake customer to get acquainted
of your Bitcoin usage.
And if you're not like a super hacker
that you know how to derive your accounts well,
or for some reason your Bitcoin wallet
just mismanages your addresses,
it can reveal a lot of things.
And even though like you've managed super well,
like with the correct hardware,
you will be able to, or with the correct agent,
in this case, you will be able to tell or with the correct agent, in this case, you will be able to tell, like, what are the payments related to the store or to this address?
So, CCash allows you to run your business in a private way so that you can have your, you don't have to worry about managing addresses
in a very complex way for every customer.
And you can just hand your Shield address for payments
and nobody will be able to figure out
what the amount is that you received, etc.
But something that will be real cool to see is for
example something that ccash unfortunately lacks is merchant like merchant tools so if you can
use near intents to help merchants merchants provide Ccash payments,
and even if it is transparent Ccash,
it will be really useful for the Ccash community
and the ecosystem.
That's a very, sorry.
No, no, no, please, please, no, no, go ahead.
That's a very interesting point, right?
Because then you can actually use the advantages of Nier, like, for example,
link drops and, you know, just like handle the complex logic of, you know,
adding financial logic into an application on Nier, right?
And all of the onboarding in Nier and all of the, you know, maybe offboarding if you
want to send something to someone but then through intents you do it privately in seed cash right
so then i'm just saying like ah yeah i'm i'm okay i'm paying you and just follow this link to pay
and all of that you know like on the surface you have nears and on on the background you have like ccash to make it private
yeah for example if you can make an intent that can take an arbitrary amount of usdt on
any chain and like automatically route it to zek or the other way around um it would be really awesome because then if I'm a merchant and I want to, I don't know, give you a payment method,
merchants don't care about the cryptonomics, what they need to do.
Like merchants are not hodlers. They don't care about the cryptonomics what they need to do like merchants are not hodlers they they
don't care about the different projects what they need to to do is to sell whatever they're selling
and cover the costs and have the revenue so they don't need volatility to eat up their costs
covering their costs or neither eating up their revenue.
So crypto payments are convenient for HODLers,
but we want merchants to have the convenience
of being able to offer the payment method.
And then if they want to profit and play with their crypto,
it's up to them, but we don't want the payment rails
to actually have anything to do with that. So
it's not betraying Satoshi's vision to actually just let merchants convert to some fiat stable
coin, because what we want is the opposite. We want to be able to spend our crypto and we want
the merchants to be in touch with crypto and get acquainted with and be able to continue to run their businesses and not let volatility make any damage to them and make them withdraw from crypto payment rails.
So this will be a really good next thing to have, like some payment rail for ZEC will be a total win.
Actually, this is one of the craziest sessions of giving away ideas for Hackathon. un total de ganas. En realidad, esta es una de las sesiones
de dar ideas para Hackathon.
Muchas gracias.
Pero estás llamando a soluciones muy sofisticadas
que necesitan estos casos de uso.
Y hasta ahora, no hay nadie
preguntar nada en los comentarios. There isn't like nobody's asking anything in the comments.
So first of all, thank you very much for the ideas
because are really, really great.
And these are real use cases for this technology.
And I would like to review with you guys
where the proper and the best channels for the hackers
who wants to, you know, like,
not ping you or ask for you know like some help on this weekend
we get some channels we get a Telerand group the channel of the Zcash Telerand group for
DevHub collective sorry for Hackbox collective but also you get the ccash discord you're
looking at the link on the screen uh guille something that you may add where to to find some
help uh fixing problems with with uh intents yeah so actually there is we have documentation in the near site and very important we not only
have documentation on like what near intents are we also have a whole tutorial about how to
deposit into near intents how to use it to swap from one coin to another from one asset to another
and also how to withdraw into any type of account.
So dogs.near.org slash chain abstraction slash intents.
That's, you know, like the source of truth
for everything about near intents.
And we are around the Telegram channel.
So if you have any questions, please do ask them.
questions, please do ask them.
And also, you have a link for docs on Zcash, Paco, right?
Yes.
I think that the best thing is to check out, yeah, the Ccache read the docs, also Zekhub, which is like zekhub.wiki,
which has a really good tutorials on everything Ccache,
like from zero to hero.
And also the Discord channel,
the research and development channel
is very good to reach developers.
And there are a lot of like
people not only like the core developers but those ccashers that will be able to help you out um
probably there awesome well i guess that this will be a short session. I guess that people are shy or they are just, you know, you just blow their minds with their idea
and they are going to panic regarding their own project.
So just last minute advice for the hackers regarding
that they're facing like 48 hours plus until the deadline.
Paco shared great ideas last time we talked for the hackers.
Guille, what would be your advice for the people who have been hacking
to actually deliver and please submit your project.
On the TideK, it's quite easy to do the submission.
So just don't fail on the submission.
Even if you achieve just a part of your main idea,
go for it and submit.
Guilherme, what would be your advice for hackers?
My main advice would be the same
that I give for every hackathon,
which is do remember that this is a hackathon and the people evaluating it remembers I give for every hackathon, which is, do remember that this
is a hackathon and the people evaluating it remembers that it's a hackathon.
So I often see people think that if they don't have like a production grade, you know, project
that is like literally as good as near intense, which took like 10 senior developers, six months, you know, like,
if I cannot do that in 48 hours, then I'm useless. And that's not the case. We are always like
looking at the code, knowing that you had to write it in 48 hours or in like two weeks or in a month,
or it doesn't matter. We know that it's a hackathon. And therefore, if you build something,
we can forgive small quirks, we can forgive, you know, like the button that sometimes works and sometimes doesn't work, or like the service that is on and off because you use some free provider and it takes 50 seconds to take it up.
and say like, would this work? Because I didn't manage to make it work, but like,
because of some dependency, but would this work? Yes. Is the idea good? Yes. Can I see that,
you know, if I, a senior developer that is knowledgeable, take you and help you for like
two weeks, three weeks, a month, we can make this into like a prototype or like an MVP.
So then for me, it's a good project. So remember, it doesn't have to be production ready,
it doesn't have to compete with the best wallet of Zcash or the best project in the year. It just
has to be a good idea and showcase that with time and appropriate help, that could become a real
project. Because that's most of the time what we are searching for, right?
And not necessarily like a project
that we would just say like, hey, great, now go on your own.
We're searching for someone, for a team
that we can say, perfect, now you have my attention
and moreover, you have resources in my head.
So that's the point, don't overthink it.
It's much better, like, you know,
everyone would overthink it and not send it like you know everyone would overthink it and don't send and
not send it therefore if you just send it you already have a huge advantage of all the rest
so please submit your project awesome any something that you will add on top pacu
no no i think that that's a perfect uh closing argument for this live stream.
Okay, again, thank you so much guys.
And if the people who are watching this live,
go and watch it again.
You got great ideas for your project on this hackathon.
And again, that's it.
Happy hacking and remember the submission
deadline uh this sunday at midnight utc happy again everyone thank you thank you bye bye
