Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Algorand Tech Roadmap AMA
Recorded: Aug. 4, 2025 Duration: 0:56:09Space Recording
Short Summary
Algorand's recent roadmap launch introduces innovative projects like Intermezzo and ROCA, focusing on mainstream adoption and user empowerment through decentralized identity solutions. The discussions highlight trends in KYC reusability and governance, alongside potential fundraising strategies to enhance the platform's sustainability.
Full Transcription
Thank you. Good morning, good morning. Thank you. and that is all of our speakers in the house today i'm going to hand over to our amazing
host for today algor family mj who's going to run this space. It's a highly anticipated one where we're going to break down the Algorand roadmap and answer any questions you may have.
So over to you, MJ.
Thanks, Mikkel. Good morning, everyone.
It's so great to see all y'all's beautiful profile pictures on this space.
Let's get at it.
So, yeah, as you all know, Al Al Grant's technical roadmap was released last week.
It includes the building blocks for where we're moving, what we're focusing on going
forward from a technical perspective.
And we just wanted to have this space to invite the community to come up, participate, ask
any questions you have on the technical roadmap, get know, get your voices heard and answer any questions.
I'm pleased to be here with Mark, who's our chief marketing officer and also now our chief
strategy officer. He comes with a wealth of knowledge. You know, he came over here
after his time working on Google. You know, he's the one that got Android on the map.
Welcome, Mark. Glad you're here.
Hey, I'm Jane. Nice to be here.
Thanks.
And I'm also joined with Bruno,
who's our principal architect at the Algram Foundation,
who's also acting as our temporary CTO
until we get a replacement for John Woods.
Welcome, Bruno.
Hello, hello.
Sound check.
Can you hear me well?
Yes, you sound great.
Thanks for joining everyone. And for all the community members out there, you know, feel free to raise your hand anytime at this space. We'll get you up here
and get your questions answered. But yeah, so let's talk about the Algorand Roadmap.
Marc, can you give us just a high level overview of what's on the algorithm technical roadmap sure sure mj so um
this is a i'm actually quite excited about this roadmap um it's i think a very different type of
roadmap than you typically see um uh in crypto um and i think one of the key reasons behind it is that when you look at roadmaps
of other blockchains they still deal with like basic things like how do you scale or
how do you get finality then like basic kind of protocol related related items these are
things that we solved a long time ago and so I I think we can, we focus this roadmap really
on mainstream adoption.
How do we get mainstream adoption?
That's the core focus of this roadmap.
And getting to mainstream adoption
needs much more than just protocol related things.
Of course, the protocol related things are important
and they're an important component of our roadmap.
But in order to get mainstream adoption
from our perspective, it's not dependent on on on protocol related items it is much more
dependent on stuff on application level stuff above it and that where you see a lot of the focus is
and so there's two kind of core elements to this one is what are the use cases that we want to
double down on to get that to mainstream adoption
right and those use cases are focused on identity they're focused on tokenization of financial
products and they're and they're focused on agente commerce i can talk a lot more about those
and the second component of getting to mainstream adoption is all about removing friction removing
friction everywhere we find it removing removing friction for developers, removing friction for users, removing friction for businesses and startups who want to develop an algorithm.
And so that's really the core focus of this roadmap is resolutely going on the offensive and reaching for mainstream adoption.
offensive and reaching for mainstream adoption.
And that's the core.
And so in that sense, we're very pragmatic
in how this roadmap is being built.
It's not like pie in the sky top of things.
It's things that we can actually build,
that we can deliver.
And as you've probably seen, 24 hours
after we launched our roadmap,
we had the first product go live, Intermezzo,
which is a product that enables businesses
to build web 2.5 experiences.
And World Chess is our launch partner with with that and they went live with this today.
So, so very excited to see this.
This is, as I said, it's a very pragmatic roadmap.
There's like concrete products in there that we're building and that we're going to launch
over the next months and the next year.
So, and this is a kind of quick intro, but of course we can, we can dive in into any
piece of this roadmap depending
on what people want to talk about.
Incredible, Mark.
Incredible.
Yeah, this roadmap absolutely seems very ambitious.
You know, like you were saying, you know, even just taking one part of this roadmap, like
the Web3 core values, you know, how to have a blockchain that is, you know, scalable to all
people, inclusive, you know, anyone can run a node and participate. There's a lot of blockchains out
there that can't even do like, like the basic stuff, like, like, you can't go and run a node
on some certain blockchains, right. But you know, it feels like this is very ambitious, because
Algorand is tackling all of this at once, you know, yeah, we've always been kind of like the
people's chain, right? If you talk about OG, and we've always been kind of like the people's chain, right?
If you talk about OG values, we've always been kind of the people's chain.
Anybody can run a note, like it costs you, like, you know,
you just get a mini PC like I do on Amazon,
it costs you like $200, $300, you can run a note,
you can stake one algo if you wanted to.
And you look at some of these other chains, you know,
they don't talk about these kind of values of decentralization anymore because it costs tens of millions of dollars to run a node.
And so we're not like that.
And so those OG values mean a lot to us.
These values of decentralization of like on-chain governance mean a lot.
And so we will continue to push in that direction.
And I was very glad to see that p2p actually went live um that was kind of the only remaining kind of centralized
element in our network these relay nodes and so with p2p gossip networks like you will be able to
kind of bypass those relay nodes now called repeaters. And so that will definitely push the decentralization of a network up.
Governance, we made a lot of workers there too.
We're not there yet.
Like there's a lot more stuff to happen, but we brought XCOF grants back.
We have our XCOF council that was elected by all the ALGO holders.
And so a lot of workers there um we want to look at general
governance and and make it also maximally inclusive and and and on chain so more to
come there as well and of course then this project um uh King safety which is probably the most
important one of them all which is to ensure that our protocol is sustainable for the long time so
so so uh lots of progress there as well,
and lots of items to tackle in the roadmap. But the point is, we really believe in this idea of
decentralization and the original crypto values of decentralization and governance. And so you'll
see that reflected in the roadmap as well. Awesome. Great to hear, Mark. Real quick before I let Leo speak, Mark and Bruno, what are y'all's favorite parts of this technical roadmap?
I know what Bruno's going to say. Bruno, go ahead.
What are you going to say?
You're going to say identity. You're going to say identity am i wrong yes no no that's right but uh maybe i'll maybe i'll
start by intermenzo and then i'll go to uh identity so for for me what i predicted to
intermenzo what i think it's important is that integrating these systems especially distributed
systems on a for a traditional uh business uh or or even a startup
it's it's not trivial uh you have all these set of infrastructure in place uh and then you you're
confronted with this how do i integrate this new technology it's a distributed system there is a
custody involved so interment zone gives umum gives the business something they're familiar with in terms of deploying
these components, how to do key management, how to do custody.
Sometimes businesses are not comfortable with a non-custodial model design.
And so they want to do custody themselvesial themselves, or for they're afraid of
regulation, or something like that. And so Intermentum gives them a custodial solution, in which they can, it's a
multi tenant. So if they have multiple employees, it's easy to create this multi tenant access policy, controlled
this multi-tenant access policy controlled role system.
And it uses a traditional key management system to keep the keys secure,
in which they already understand how to separate data amongst their admins,
how to recover, backup, and makes the integration with Algorand just understanding
a REST API. And so it was very easy, for example, in the case of WorldChess, I'm speaking for them
here because I know what they think, but it would be nice to hear it from them at some point.
They integrate all the capabilities of Algorand, most of of them they needed to issue assets transfer opt-in people
create accounts so that they build their loyalty program and they did that on their infrastructure
under their control using a rest api they didn't have to understand cryptography sdks and all the
nuances that Algron brings so they called an api we give them all the endpoints, and they will be able to develop
this tower system, loyalty point system for people to play on World Chess. And if it works for World
Chess, it can work for anybody that wants to create loyalty programs as well. Now, the one that I am most excited about is really identity, because it is with ROCA,
so ROCA, it is envisioned to be our first sort of identity centric wallet system. Many other
networks and ecosystems are already in this space. and there is a reason why everybody's in this space is because it self-sovereign identity it it it is part of web3 like we wanted or not
the control of data is going to go from being controlled by the businesses, this corporate ownership of who you are digitally and your data is going to move to the user control.
And it will be a shame we are not part of this race.
And so Algorand brings very interesting features and an economic model to this space where the users can control can store their digital identity
in Algorand in one of our storage mechanisms it's there it's distributed i'm the one who controls it
is traceable and and we are being in the race of the the broader web 3. and for that we need vehicles to have a window
for the users to get in this space and so roca and roca brings the identity the self-sovereignty
identity aspect it gives us the ability to build systems in algorand that require things like
forward lookups who owns this address how do I prove this address belongs to this one person?
How do I link this one digital ID to a real person?
So compliance is important, and for Algorand,
it's us putting Algorand in the race in this space.
And ROKA has the extra benefit of being another wallet
and has the goal of making on
ramping very, very easy. So it's the opening of a new strategy for growing Algorand, which is
the implicit adoption. It's not targeted for the user that knows what the blockchain is, what Algorand
is. It is targeted for the user that wants an
authenticator for using it on websites to get their credentials, to manage their identity and data.
And Roca makes that very easy. It delegates fees to the businesses, not the user, and gives them
control of their own data. Obviously here, Algorand is the anchor of all these elements.
And there's much more I could say.
I could talk for hours about this subject, but I think that's good nuggets for now.
Thank you, Bruno.
That's a lot to digest right there.
I definitely like owning your own data.
You know, we live in a world where everyone's trying to spy on you with adware and all sorts of stuff. So I'm definitely a fan of owning your
own data. All right. Well, why don't we go ahead and bring up Leo? Welcome, Leo, a community member,
a developer, and you're even in the ice cream commercial. I'm not sure if everyone knows that,
I'm not sure if everyone knows that.
but welcome to the stage, Leo. What questions do you have?
What questions do you have?
Hello.
Good afternoon.
My question was for Bruno.
I had a question about the new KV storage method, the key value storage method that was mentioned in the slideshow.
My understanding, it's not just like further abstraction of like box names and box values
like that workflow which we see with box mapping already but like an entirely new and cost-effective
way to utilize Algorand for data storage so I was wondering if you could expand on that
a little bit thank you it is It is an abstraction for now.
It is meant to make it very easy on a key value system
to bring complex objects, abstract away
the complexity of putting complex objects that
might not fit on a single box, and spread them out
against multiple boxes
and be able to easily then fetch and reconstruct
those complex objects later.
So we do use this in some places.
Like when we did our DID algo, for example,
we had this need of breaking down JSON files that might not fit in a single box and split them.
And then we have the need to track them, their indexes, and then rebuild them back up.
I know some people in the community do similar things with front-end code and whatnot.
And so we try to make this to abstract away the storage mechanisms that we
offer in Algorand. It is a project that was started by one of our members internally,
Fear Zero, Michael Feijer, shout out. And so we want to make that a module of Alkit. There is an
arc about it with discussion. So once that gets finalized,
if people are happy in how it works,
then we'll make it part of Allocuit.
Okay.
Yeah, that was going to be my follow-up question.
So it's kind of like a new arc.
It seems like it's going to be pretty efficient.
Any changes with the fee structure for boxes?
No, so we're going to rely on what's there today.
If there is, so we're trying to obstruct as much as possible.
If there is fee structure changes in the future,
we'll try to incorporate those.
But this does not take into account any future.
Thank you. Thanks, Bruno.
No worries.
Thanks, Leo. And once again, just a reminder, anyone who has a question,
feel free to raise your hand. We can bring you up and hopefully get your questions answered
about the Algorand technical roadmap. But yeah, Bruno, so just to clarify too, like these solutions like Rocco Wallet,
like these aren't solutions like we just randomly pulled out of the blue, right?
Like these are problems we see companies having barriers that they need to be solved
before they like fully hop onto Web3, right?
You know, they need these types of solutions and that's why we're focusing on it correct i just want to clarify like we're not just like we didn't randomly just
make up all these random things on the roadmap like right we these are these are things that
need solving yes yeah to touch that point so the most blockchain uh systems i've been in a few so
i've seen the same problem over and over, is everybody
tries to come up with their own rules on how to do digital identity, they have different
ways to represent who you are in the digital space, they have different ways of authenticating,
proving things to each other, different ways of doing messaging if there's
everybody has their own set of rules and and this becomes a problem to the rest of the of the
digital world that if you want to be easily accepted you can go around and knock on everybody's
door and try to sell a blockchain and And that's very hard, honestly,
as good as technically we might be. It's a hard sell saying, I use my blockchain is better than
yours. And so the smartest strategy for me is the things that we don't have to reinvent the wheel, we don't. And there are already big groups thinking about problems that we have
above the protocol at the ecosystem level.
Things like identity, payments, credentialing, proving things about each other, connectivity, how apps talk to wallets and so there's the multiple
groups thinking about this and groups that the internet knows and historically has been
the workforce behind making sure browsers work exactly the same way. For example, the W3C, the Linux Foundation, and all these concepts around ID credentials,
and rocker is not something we invented. We want to be
interoperable, we make, we want to make our grand very easily to
integrate to the point where, if you develop an application or you
want to verify any sort of claim by another party you don't want to have to understand all the
technical stack in order to do that and this is a problem with integrating blockchain systems is
because a lot of times we have to so most likely everybody has to learn a new language
every time and if you don't have first mover advantage it's very hard for people to even bother
so i do think rocker gives a new element for us to make algorand competitive is which it's with
the verifiers the issuers people build applications people want to be in the self-sovereign identity space,
they're not going to have to worry about the technical details because ROCA adopts what's
being standardized, the rules is being agreed by these bigger bodies, and how we should do these
things. How we should do authentication, for example, pass key based. How we should do these things, how we should do authentication, for example, pass-key based, how we should do claims about each other, verifiable credentials,
how we can apply zero-knowledge proofs to these, how we do payments in a way
that you can protect people's privacy, but also how you can link one ledger address
to a digital anchor that potentially can link to a real person if you need to.
So all these questions have answers. It did not come up from us. What we're going to do is we're
going to play that space, play by the rules, but we're going to make Algorand the engine that makes
it competitive. One good example is managing identity and credentials.
So in the self-solving identity space, you can pick whatever storage mechanism you want.
You can store things in AWS, IPFS, BitTorrent, whatever you can pay.
Algorand can make that data ownership really attached to your key, keys that you control that you carry that you back up
it's not in control the custodian is you is no nobody else and you know the data is there
because you put it there you locked away algo to keep it there and you can delete it at any time
and you can recover the cost if you ever want to. So with this, it can
make Algorand competitive in this space. ROK makes it very easy for people to on the ramp into an
identity wallet. And Algorand is behind the scenes. It is the engine. And you can think of ROK as a
way to do implicit adoption. If the user experience is good, if we introduce these patterns of fee delegation
and abstraction,
where the businesses pay the fees for the users
and the users are in control of their own data,
we have a chance of making ROCA
a good white label solution for people to build wallets
and make Algorand attractive in this in this space yeah and i think this standards
based approach you see this in in other parts of our roadmap as well like for instance on the
agentic commerce stuff like this we we take the same approach we don't necessarily want to build
a new standard or create new standards we want to rely on standards that exist and so MCP of course is
one of them that allows basically agents to interact with the blockchain and and abstracting
all the complexity of a blockchain away that's what MCP does and that's what go plausible has
has already built for algorithms so so shout out to go plausible for this but we're adopting
we're adopting MCP the same thing as the way agents
interact with each other a2a is an existing protocol that uh that was created by google
and was now given to the linux foundation um we're gonna adopt a2a to to enable agentic payments and
allow those agents to interact with a blockchain and then the same thing for payments like you know
coinbase
has developed this x402 protocol like rather than us trying to invent our own we're going to rely on the x402 protocol and of course in the case of agentic payments these are uh or agentic commerce
i should say that these are still all kind of emerging standards and they're not necessarily
i think set in stone uh but but our our strategy is the same is like
as standards emerge and as standards become more prevalent we're going to adopt them and
make sure our ground is fully integrated with them bruno yeah on the x402 since you mentioned mark so
obviously we want Algorand.
I think it's important that Algorand is supported so that we can build with it.
And if somebody builds with X402, we want Algorand to be one of the options.
And the way we're currently going about it, and maybe we can get the community
to chip in and get involved.
We are drafting a specification that internally we're discussing and trying to make it see what fits best to get Coinbase to accept our ideas.
We forked the X402 repo.
There's pull requests that we are keen on on on reviewing if
you guys want to have opinions and and how it should be done there are some ideas being discussed
there so i invite everybody to go into our github uh repo find x402 and and chip in if you want
there there is a there's some specifics around how Coinbase designed
X402 that is based obviously on EVM first and there are some Ethereum standards that are
influenced there and we have to make Algorand attractive there and there's also a good
opportunity to teach a new crowd
how Algorand works.
There are some specifics around that,
but I invite everybody to go there and read the discussion
and contribute.
And I think the most, if you have contributions,
we include everybody's commits and make everybody a contributor
if you're interested in this.
And then, continuing maybe the conversation on standards, the other area where we, in
our roadmap where we adopted existing standards is around the tokenization of financial products,
right? It's like, that's a core part of the roadmap it's like how do how how do you how do
you tokenize um debt instruments equity instruments and so on on on a blockchain and how do you make
sure that these instruments are fully uh understood by a blockchain that the blockchain understands
like the cash flow that's associated with with instruments. So there's an emerging standard
there as well called the ACTA standard. And so again, the same thing, rather than trying to do
our own thing, we are adopting these existing and emerging standards to implement these products on
chain. And in that regard, I think it was interesting to see the recent conversation,
Paul Atkins in his speech mentioned the
importance of tokenization and he referenced the uh uh an ethereum standard called the ERC 3643
um and that deals with like tokenization and so it's interesting to notice that like a lot of
the stuff that that is in ERC 3643 is already implemented and available on algorithm
because tokens are fundamentally integrated into our layer one and so things like white listing
black listing account freezing asset revocation for which you need smart contracts on ethereum
are already available in algorithm and are natively supported by the ASAs
that we currently have. And so it's interesting to see this is a space that's heating up tremendously
and I think we're in a really great position there with our existing ASAs and then if you
add the smart ASAs to it, as we discussed in our roadmap, I think we'll be in a very good position.
I agree, Mark. Yeah, Layer 1
Algorand is just so beautiful and so
powerful, and you can do so many
things on Layer 1 that
other chains you would need smart
contracts for or to build all sorts of specialized
tools. So yeah, for sure.
Shek Juarez,
welcome to the space. I know you
are like OG.
You've been around here for a long time.
So welcome.
Do you have any questions?
Hey, hey.
I just want to keep really excited about this,
the notions of identity.
But to my basic mind on this,
I just wondered if you,
like how to explain this generally
and it's probably as much a Mark question
for, you know, how to get people to
understand, you know, we, from pseudo anonymous addresses to DIDs.
And, you know, when I think about the, you know, we've discussed driver's licenses and
how you can, you know, have proof that you own the car.
It's registered that you are a licensed driver without giving away any information about yourself and zero knowledge.
But just the notion of digital identity and why that's interesting over and above just the notion of a pseudo-anonymous address or
you know how to explain this to quote-unquote normies right I think that's quite interesting
yeah I think I'll maybe answer this first enough we'll have many thoughts on this as well so
I in my perspective like it is very kind of use case driven, right?
Like trying to explain this to a normie in a general kind of sense is impossible to do.
You have to make it very, very specific to the use case and you have to let people see what it works like and so for instance when you think about rocker the first implementation of rocker will be um as we mentioned um uh another element of our partnership with world chess
is to is to basically launch this as a a global chess passport and so and so you can easily
explain to a chess player what this is right hey you go to like an in-person tournament now you
have to jump through a bunch of hoops to basically prove who you are with our global chess passport
you'll be able to just open the wallet show QR code the organizer of a tournament will scan your
QR code and that's it and you're done and so so when when you tell this to a chess player they
will get it because they understand the friction
they understand the problems that they currently have when they try to register for like you know
an in-person tournament and so you take away that friction and you basically show and you don't
necessarily have to talk about that entity and verifiable credentials all that stuff is like
technical mumbo jumbo like to a chess player you just tell them like this is the wallet
it has your identity you show the qr code and you're in and that's it and so i think we have to bring it down to that level and
the more you can make it use case specific um the more easier it is for people to understand and
then use it and that's and that's the whole idea behind this wallet too that's why the the the
wallet is is is um private labeled right so world chess will not launch rocka world
chess will will launch their chess passport they'll call it the chess passport or whatever
they want to call it but it is going to be designed for for their use case and their chess players
and so that's the whole idea behind this work i want anybody can take it and then implement whatever
That's the whole idea behind this work out.
Well, if anybody can take it and then implement whatever
identity use case is relevant to them
and brand it in whatever way that they want to do it
and make it specific for their use case.
And that's how I think you get to mass adoption.
That makes sense.
There's probably a conflict
in how everybody might be spooked
with AI consuming everyone's data,
and then you say put identity on top of that,
and that's part of my concern about people misunderstanding
what we're actually talking about when we talk about identity per se.
Yeah, I can maybe touch a little bit on this
can maybe touch a little bit on this because it's a good insight that you have checked.
because it's a good insight that you have, Shaq.
So I think with this DID system, this DID system, what makes it interesting is that you don't have to have just one DID that
represents, that gets spread around all your digital behavior. Like you can have a multitude of them.
And the idea by itself does not reveal anything about you.
It is just an idea that spans across multiple ecosystems and applications
that it's not created by each different applications.
You control it and you just share it around, but you can have N of them.
And if you do want to have, if you can have N of them. And if you do
want to have, if you want to sort of dox yourself or you want to get onboarded into something that
requires KYC, know who you are, you can have a dedicated DID for that, in which you say, okay,
I'm willing to go, this is my DID.
I'm willing to sort of attach a real identity to this digital anchor.
And from that point on, then, I mean, and then credentials is, is what makes
the whole KYC reusability, is what enables that.
And it removes a massive friction point from our digital life that we always have to be
do QoSE for everything over and over again.
But the idea itself, it doesn't reveal just by itself,
doesn't reveal much about you.
But what I find in your insight about teaching people,
there is a saying in the SSI community,
which is if you show the idea to the user, you already failed.
And Mark touched on this point.
If we design these applications, we should not put the technical standards in front of the user.
We should try as much as possible to make this that the user sees it
oh is one profile i have i have three different profiles behind the scenes it uses the id
rather than a raw algorithm address for example just because it makes the the integration of an
algorithm user through that wallet seamless because the applications and the browsers and the
platforms that are adopting passkeys and the IDs will not care about the technical stack. So out
of the gate we will be connected. That is sort of the goal, if that makes sense. But being private
is important and as part of Rocker you'll be able to create multiple profiles as well.
Cool. Thank you. Thank you. Thank you.
I'm also very excited about all the rest
that's been described by the roadmap.
So I'm looking forward to seeing the progress.
Thank you, Chek Juarez.
It's great to hear your question and hear your voice.
Hey, good to see you too.
All right, all right.
Speaking of, Bruno, speaking of the Roka wallet, will existing Algorand users that say use Parawallet or Dfly or LuteWallet, will they be able to seamlessly add their keys into this new roca wallet
yes that is obviously sort of the plan so we are uh just to clarify the plan so we are forking an
existing uh basically feature complete identity wallet that is open source and properly licensed
and it's one of the best battle-tested,
one of the best bases to build this sort of what's called bifold.
So we're going to, we already forked that.
We are doing the first steps.
And so what we're going to do is add Algorand
as one of the storage engines.
And we're always going to add capability of owning assets
and accounts.
And you'll have the option to import your keys, obviously.
In fact, the only technical information that you will need to use this wallet is your mnemonic.
And eventually with DREC, even that might go away. But for the first versions, you should be able to import your mnemonic.
It will have to be almost like a 24-word mnemonic
just because we need to generate a lot of keys.
Because as I talk about this,
maybe you understand that we need to generate keys
for Algorand accounts, multiple of them,
keys for identity, keys for past keys, for authentication.
We need to generate a lot of different keys, not just to hold,
just to create Algorand accounts.
And so most likely we'll be able to import 24, 36 word mnemonic
and you'll have your Algorand accounts.
Awesome. Great to hear that. Thanks, Bruno.
Ruben, welcome to the stage. Do you have any questions for the Algorand technical roadmap? Adoption at the layer one level. I think that has been a long time coming and I've been preaching since about 2016.
So I'm glad that people are jumping on board because I think that's really like the underlying architecture of, you know, peer to peer as opposed to like peer to peer to platform to peer, which is where a lot of the coordination is taking place in 2025 post you know web
to platform and network effects and so on and so forth right where I feel as
though if we can sort of repatriate the the data objects whether that is the you
know my little Airbnb listing on this app or my Facebook post on that app or my whatever data object on
some other platform, if we can put that on sort of peer-to-peer rails and beef it up with peer-to-peer
tooling in terms of like soft trust and so on and so forth, it seems like there's an opportunity in
the next decade, particularly with like modern tooling, to be able to build sort of composable infrastructure for peer to peer stuff where we might have historically had to rely on platforms for.
And I think some of that will come down to open standards because you need open standards if you can have interoperability.
Right. And so I guess I wonder um what do you sort of see
the first expressions like let's say that we all that we're talking about right now comes to pass in the next six months and it's sort of expanded option what do you see coming down the pipeline
after that that's that that gets you excited about today
about today?
Well, this space...
Oh, thanks, Ruwin, for the question.
So, yeah, I'm happy there is more identity fans out there.
So for me, what gets really excited is to bring these networks
as the technical... networks as part of the engine that feeds into applications that are not just the applications
that I trade my NFTs or I do DeFi, but it becomes part of my digital life. Where if I want to sign
a document, for example, is one thing I'm excited is the ability for me to say, I have these accounts in a ledger that tracks my assets and you can follow history of my behavior.
I have an identity that I can prove I own these things.
And also, when I'm confronted with signing something, let's say a legal binding document,
that I can do so with the key that has history, it can be tracked,
and I can link that, if needed, to a real claim of who I am
and have a higher level of confidence than, for example, what DocuSign does.
And then I stop using Algorand
or another distributed system.
It's just something I use for trading some assets,
NFTs, loyalty points, but it is just part of my digital life.
Any website I go, I authenticate with the keys
that are, have history and I can prove that.
And on a peer-to-peer manner,
something I'll be really excited about is also to get behind open standards, as you mentioned.
And for example, we developed this thing called LiquidDOT,
which is a framework, a reference implementation
using known open standards
that removes Wallet Connect from this Web3 space,
which we can talk about decentralization all we want,
but we still have this one company that develops this protocol
in which blockchain network ecosystems have to ask permission
to add a message to it or your application to be
available. And so the combination of these and Liquidot, it is something I'm really excited
about. I would love to see its proliferation so much so that other ecosystems have proposals
for people to develop exactly that. And we have it. We just don't have it in one of our wallets yet.
It takes a while to integrate.
But with that, we will be able to have identity,
attaching to real identity when needed,
multiple profiles,
and talk from our wallets
that we control our identity and data,
talk in a peer-to-peer manner
with each other and with the applications we
interact with that's what i'm excited about to see that future it's easier said than done because
it's not just up to us the foundation we would need the applications the wall developers
everybody to see the same vision and and chip in and collab and and go in the same vision and chip in and collab and go in the same direction.
But if people are out there and want to pursue this, then...
I mean, there's so many opportunities for that, though, right?
Think about how many platforms are effectively relying
on network effects to keep people
into highly restrictive discovery interfaces.
Say, for example, labor coordination, like on Upwork,
where they're charging up to 30% fees for a matchmaking service, right?
Versus, you know, Tinder, who forces you into swipe left, swipe right,
as the sole discovery mechanism for all that that exists in the human experience right like
not even semantic search right like it's crazy that that's our interfaces is a binary interface
for for eight billion you know objects in a network uh so to speak um metaphorically speaking, I should say. But yeah, but the shittiness, the inshittification, which is a Wikipedia term.
I'll check it out. objects that we have been giving to platforms, repatriate them to the wallet, and then build
better coordination tools across sort of embedded privacy object architecture, then we can have a
lot more secure experiences with a lot more open discovery tooling, which seems really promising.
Yeah. Yeah. And I'll say this. So the RCA, as I mentioned, is based on a known wallet.
It brings a lot of that.
And we also want everything that we do on top of that
is going to be white label.
It's going to be licensed the same way,
so people can do whatever they want.
And one of the things I'm also excited about,
since you touched on this, is the
selective disclosure and the protection of your information, even when you want
to prove certain things.
So today we hear news about, especially in the EU, you have to prove who you are
and age and all these sort of things.
And you have to trust the platforms to manage that data properly.
And it wouldn't be nice if I just use from my wallet that I have my data
to provide the proof that, yes, I'm over 18,
but you don't need to see much more than that.
And I don't have to tell you or share any more than that.
And we're done.
And even if you mishandle that information,
I'm not a victim of a data leak
or a hack.
Wouldn't that be nice?
You could have,
if you wanted to get real fancy,
you could use homomorphic encryption.
Sure, yeah.
Which I don't know if you would need that to figure out if I should buy the bagel or not.
Maybe the port logs for my maritime vessel or something.
But there's a lot of use cases that I think are really boring for institutional and municipal purposes and perhaps more relatable for consumer purposes.
And I wonder, what are the first use cases
that you see coming through the pipeline
once the infrastructure is out there?
Yeah.
Yeah, so for me, the king of all of these use cases
with these systems is KYC reusability.
It is me to go, I want to do KYC once, attach to an ID that I control,
and then every time I want a new debit card issue, I don't want to go through the process again.
I want to provide you a proof that you can verify and you issue the card for me. We call it a day.
The first use case we're likely going to see with Algorand being involved
is really the World Chess on the gaming space,
which, as described, I mean, I described this before,
but I want to prove that I play on this platform,
I have these achievements world chess can
attack can make a claim saying i am a grandmaster level and then i can go anywhere to an in-person
tournament and prove who i am online and on board in that tournament very quickly without all the hassle to prove things manually
it's one of the hurdles we discussed with world chess tournament organizers and grandmasters and
it will make the whole process a lot easier this will be the first use case likely to see with
rocka because it's nice that we have a vehicle we're not just developing something, hoping somebody would adopt.
World Chess is excited about this.
So if it works for chess...
So there's clients, right.
And if it works for chess, then you have anything with an NFC now.
Exactly.
Yes.
Yeah, exactly.
That's great.
Yeah.
We're open to ideas.
So if people have more ideas, it's going to be open source.
Just chip in, contribute.
I have a question.
This is a little inside baseball.
But do you think there would be interest in a full stack, near-field chip slash GPS stack that would allow for a peer-to-peer social graph mediated Airbnb equivalent?
It's like Airbnb without the org. It's just peer-to-peer.
I'm hearing a business idea over here. I don't know. It sounds like I would use it.
It could be.
Back to our regular programming. Thanks know? It could be. Back to our original signaling,
residual programming.
Thanks for your time, Jan-Man.
You know what I'd love to see
is I would love to use
this new decentralized identity
to be able to get rid of
all like corporate logins
to all like corporate SaaS-based systems.
It's just a nightmare.
Like the way you kind of like
every single SaaS system has its own way of logging in.
What if like the company can just give you like a very far-boiled credential and then
you can use that to log in in a consistent way, coherent way to all of these systems
with like one single way.
That's what I would say.
Do you want to know a really aggressive way to handle that?
That's fully legal, but a very technologically aggressive way to handle that that's that's a fully legal but a very technologically
aggressive way to handle that is you build a browser extension which when
you're browsing on the internet it scrapes the internal data that you've
put into your platform pulls it into local objects hosted in a secure server
and now you basically have you can extract your entire profile entire craft a local controlled object, which you can then link up to every other, everybody else who's done the same thing.
What do you think?
I'll let Bruno reply to that.
He's going to give you the technical reasons why.
No, no.
Technical or legal?
I just heard browser extension
and I got excited because I think it's one of
the things we're missing.
But yeah, that can be
actually very useful for you to
for content
ownership.
It's actually one of the things you can do because
you have to own the application
where you actually generate information. Because you can prove, for example, that I wrote this
document, I edited this image. There's ways in which a browser extension would be incredibly useful because it's not enough for you to edit in a different program and then make that claim because there is no transfer. the bytes that you are actually crafting. When you own where you're actually manipulating that
content with an extension in which a browser is actually loading things into the client,
into your browser, you can have a more trusted proof that that content is yours.
And we need browser extensions. We actually one of the few ecosystems that are lacking a bit of an extension.
Yeah, so if you want to brainstorm on this, Ruben,
I'm happy to.
And I'm trying to find excuses to get an extension out there.
Yeah.
And this is actually also a good point.
The way we're thinking about this roadmap as well
is that this is not just we're hoping that this is not just a foundation underground foundation
implementation we really want to actually partner um with our ecosystem and with developers and
ecosystem kind of to deliver on pieces of this roadmap and um and that's one of the things that
we're working on is like what does that formal process look like? How do we basically collect feedback from the community?
How do we engage?
How do we, you know, build collaboration projects?
And also, how do we provide funding for it?
Because we don't want necessarily all developers to contribute just for free.
We want to figure out a mechanism by which you also get paid for your efforts in contributing to this roadmap.
So we're thinking about how to do that,
and we're going to put the process in place to go about that.
Thanks, Ruben, for your questions.
You give us a lot to think about.
And yeah, Mark, I'm so glad you mentioned the community involvement.
Please feel free to add me to any of those types of discussions
because I think the community is just so powerful, right? We have probably the best community
of all of crypto, right? Like, we are passionate, we're enthusiastic, we're on fire, we love the
tech, and we're ready and, you know, willing to be involved in stuff. But let me take a couple
questions from the comments here. And then one, this is about Project King Safety. So Project King Safety is going to revise Algorand's
fees, incentive mechanisms to make the protocol truly self-sustaining long-term, right? So
a couple of questions I'm seeing is, like, what exactly is on the table? Is it raising fees?
Is it increasing the supply of algo?
Is it introducing MEV or is it other things?
Or has this been fleshed out yet?
And if it hasn't been fleshed out yet,
can the community also be part of this project, Mark?
Yeah, absolutely. So the way we approach this,
we're basically looking at all the possible options.
So we're not excluding at all the possible options so we're not
excluding anything ahead of time um and so you mentioned the three ways to go about this like
we're looking at all three um um so that's one thing and specifically we're also looking into
um what is the implication just from a protocol perspective and this is a very close partnership
with with our grand technologies of course we're looking into like what what if we raise fees what if we include mev like what if
we like we we change the fee structure it's not just the same fee for every transaction but what
if we basically change the fee depending on like the amount of compute that is being used like
what is the implication in terms of from a protocol perspective to implement this what's
the difficulty of doing it is it easy is? Is it medium? Is it difficult?
How do we do MEV on our grant?
Like, like, of course, how do we make sure that if we do like, for instance,
if we offer like a prioritization of transaction ordering, for instance,
how do we do it in a way that is, is, is, is, does not create a bad user experience, right?
I think that's really important. We don't want the type of sandwich attacks.
