Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Anoma Community AMA
Recorded: July 18, 2025 Duration: 1:02:57Space Recording
Short Summary
The recent AMA highlighted the strategic rollout of the testnet, emphasizing community engagement and the introduction of a referral system to boost user participation. Key discussions included the importance of partnerships, growth strategies, and the project's commitment to innovation in the blockchain space.
Full Transcription
Music Thank you. Thank you. Music Thank you. Hello, hello.
It's the Brit say.
Do Brit say that? Do Brit say hello, hello. Yeah, hello. What's the Brit say? Do Brit say that?
Do Brit say hello, hello.
Yeah, yeah.
Yeah, yeah.
That's very accurate.
Good job.
Hello, love.
Perfect.
Don't ever do that again, though.
Don't ever.
How's everyone doing today?
Doing good.
Doing good.
How are you? Good good. Doing good. How are you?
Good, good, good.
Excellent.
Hey, hey.
Thanks, everyone, for joining.
Yeah, we'll get started in a couple of minutes here
and let you guys know what the plan for the AMA is.
But in the meantime, how is the testnet looking?
It's looking good.
So obviously we have started this rollout
as a sort of gradual exclusive process.
It's important that we did it this way
just so that we could actually iron out
exactly the sort of systems the optimal systems that we're doing to get the best experience
possible and we have we couldn't have done it without the massive support and feedback from
our telegram group that we set up with the top 100 yappers so thank you so much for everyone involved
it is not going unnoticed and we are very happy that you've sat through
all of our, you know, fixing of the systems
just so that it becomes the best experience possible.
We are aiming to do a couple more fixes
on some of the games that are in the testnet,
hopefully today, which will follow another rank
a slightly slightly less wide rank reset for everyone involved that's currently in the testnet
and from that point if things are looking good we will be distributing quite a few more codes
we will be distributing quite a few more codes manually
to the top 100 Yappers that aren't in the Yapper chat,
but also we'll give some to some of our Yappers
that are in the chats
so that they can give them to their communities.
So we really want to reward the people
that have been there for us the whole time.
And we have, like we say, it's not going unnoticed.
You need to keep going strong with all of your yapping. It's not going unnoticed you need to keep keep going strong with all your yapping it's not going unnoticed um so yeah hopefully you should be able to expand it
out a bit more and then once we're happy with the systems and we see it's working for you know a
couple days or so a few days um we can move on to opening up further um we'll be dropping codes here
and there in the meantime uh but we should be looking good for opening a referral
based system hopefully on Monday if things go well and this will basically be
current plan is to allow existing testnet users to invite up to three people daily into the testnet so
this will dramatically increase and democratize the access these refresh
daily so you can refer more more people and if you think of it like you know
they'll refer someone else who refers someone else blah blah blah so this
should open it up it's never going to be completely public I don't think that's
in our current plans but this should dramatically open up the testnet and
obviously watch out for us dropping codes here and there. There's some nice things that
come with the referrals, which we're going to keep under wraps for now. But yeah, look forward
to that. Thank you, everyone, for being so patient. And I do appreciate the frustration of being,
you know, what was almost locked out. There's an Eric Andre gif where he's like,
let me in, let me in.
And I understand a lot of you guys are like that,
but we really want to get it right
by the time we start opening up massively.
So I hope you guys can appreciate that.
And thank you all for being so supportive.
It's been really great so far.
Nice. Yeah, thanks for the update.
I guess the biggest question we got this week
was when and how can I get a code?
But sounds like next week that will be opening up quite a bit. update. I guess the biggest question we got this week was when and how can I get a code?
But sounds like next week that will be opening up quite a bit. So hopefully, if everyone's
paying attention on all the right channels, should be a better chance to get one next
week. But yeah, top 100 Yapper group has been absolutely crucial. I don't know if they realized
that part of the privilege of being in that group was helping to test out the test net, but, you know, they've done a great job with that. And I think
we're getting to the point where things are running smoothly. So yeah, thanks to everyone involved.
So for this AMA, for those folks who've been joining these in the past, we're going to do
something a little bit different. This week, we're going to start with some trivia. So hopefully you guys studied
up on your random Anoma facts and lore, because we've got about 10 trivia questions. And the way
it's going to work is once I ask the question, folks, you can type the answer into the chat, into the comments.
And ASJ is going to be watching the chat to see who answers first.
So basically chronologically, if you get the right answer first, then you will get a testnet code.
first, then you will get a testnet code.
So yeah, please, folks, for this portion, for the trivia,
try not to spam the chat, because we're
going to be using it to get answers to the questions.
So let's try to keep that for people actually trying to answer
and win a code here.
So without further ado, let's see if this works here. We've got some
James Bell music.
Welcome, welcome, welcome to the Enoma Privia Hour. Let's start with the first question here,
Let's start with the first question here, which is,
what is the Anoma equivalent to the virtual machine?
What is it called?
What is the equivalent to the virtual machine on Anoma?
What is that?
Let's see. Do we have any answers i guess we can run through them too um also if you're on yep you can let us you can let us know when you spot the first correct answer
yeah i'll let you know as soon as i see it but we'll just go through here
um passing through all of the messages.
What's that?
Yeah.
There's a lot of messages.
This is why I asked people not to spam the chat,
but we'll see if this can work.
Otherwise, maybe we can call on folks to answer.
Oh, I see it.
Looks like we have Radix with the correct answer.
Nice.
Which is?
The Anoma resource machine.
Nice.
Yeah, that's perfect.
You could have answered intent machine or resource machine on that one.
Both would be equally correct, I think.
All right, second question is, which programming language
is Enoma built in?
Which programming language is Enoma built in? do do do do we need like some some waiting music for this part we have ultra ego with
the correct answer which is juvx oh that is incorrect
oh wow
trick question
trick question even for me huh
it's not the language that you build apps
I think I see one
I think I see one
yeah I've got
Aurelia X with Elixir
perfect got it
yeah that is correct
if someone can tell us the bonus point what other language is involved X with Elixir. Perfect. Got it. That is correct.
If someone can tell us the bonus point,
what other language is involved in that entire stack, given that we're using
Elixir?
I don't know if I even know this one.
I think we already got it from Mush.
If I'm not mistaken again,
it's Taiga, right?
No. Oh, man.
Two in a row. You've got to brush you gotta brush up you gotta brush up in
your trivia come on
I'm willing I think Cameron you know right is it is it is it is it Rust? I would call that also.
That would have been my guess, too.
I mean, we've had a ton of people saying Rust.
Okay, so Silverfang, I think, was the one that got Rust.
Yeah, I mean, there's a million people saying Rust.
Unfortunately, this is going to be a bit random as well, guys.
We can't.
The comments are flowing.
So, yeah.
A lot of comments.
What was the correct answer on this one, Adrian?
Or did we get it?
Erlang.
Erlang, right.
Yes.
That's what the next compiles down to.
Right, right.
So there's the bunch of Erlang under the hood as well.
Okay.
And actually, the other answer I would have accepted would would have been oh it's not rust the smallest slightly nicer version of rust which i'm currently blanking on
the name uh zik right zik yeah that one's new to me too.
It's what we use for all our C dependencies.
Dude, Zik is so great.
Zik is so great.
I'm a huge fan of Zik.
Great language.
I just hate Rust.
All right, next question here is this one should be a little bit easier if folks have been paying attention. But what is the name of the programming model that Enoma introduces for building intent-centric
applications? So the hint here is it's not imperative, but it's...
I'm watching, don't worry. I'm watching, I'm refreshing the replies.
Really need that answer music at this point it's all good i'm going through it
if it's not imperative it's oh i've got one i've got one that's with the right answer
bm crypto 4 with declarative nice congratulations bm crypto 4 awesome
um all right next one is one of the prototype applications for Enoma
is like a version of Kickstarter
where users can express their intent
for projects they want to see built.
What is the name of this prototype application?
This is a bit of a deep cut.
This is a deep cut.
There's some deep cuts in here,
but I feel like people have been digging.
Okay. Does anyone know
the name of the app for
Anoma? That's like Kickstarter.
Come on, guys. I've posted a lot about
this one in Discord.
Also, our AI overlords know the answer no the answer is not elther fathark guys
oh i think i've got i think i've got someone um with pub with public signal is that correct yeah
yes yeah that is correct got him that's a grot That's Grottschew Ivor, I believe.
I've got them.
Nice.
That was a good deep cut.
Okay.
Next one is, what is the name of a NOMA's Builders Program?
What is the name of a NOMA's Builders Program?
Okay.
Let's see who's got it.
Come on, guys. This one should be easy
uh i think i've got someone with the right answer i think it's all right
oh i've got i've got smexa one i mean we could give out both
yeah we keep them both that's a tie that's a tie i gotmexel one and you've got the guy. Ty around. So correct answer is...
Intense Initiates.
Yes, that is right.
Bonus points.
Bonus code here for someone who can name one of the teams building on Intense Initiates.
Refreshing.
I know you guys got this one fast all right maybe one more second let's see
all right we have gutso with hey elsa ai nice that does count good job
um all right next up is which generation of blockchain architecture does enoma introduce
which generation of blockchain architecture does Enoma introduce?
And we're refreshing. Yeah, I'm on it as well.
Oh, I've got some.
It's quite a few.
Yeah, I'm just trying to scroll down to the first one that's on my screen.
I've got NoobQ2 with three.
That is correct.
NoobQ2.
Let's go.
For bonus points on this one, can you can anyone name um the type of settlement used
in generation one in generation two blockchain architectures what i think as a bonus answer by
the way you could also accept the last one yeah exactly yeah true true does anyone know
the types of settlement used in Gen 1 and Gen 2?
All right.
Refreshing.
Let's see.
I think we got it.
All right.
Hit me.
We have Alex Jones with Intent Citric Fractal Blockchain Architecture with Tenderman EFT.
The real Alex Jones with the incorrect answer, unfortunately.
Oh no.
I went three for three.
I have a guy that's got the right answer.
I think it's
Derek.
I don't know.
Are we taking Scriptical
and Programmable? are we taking scriptical and programmable?
Are we taking that?
Yes, that is correct.
I think scriptical, scriptable settlement and programmable settlement.
We should just call this scriptical.
Not scriptical, it's just scriptical from now on.
I like that.
Bitcoin introduced scriptable settlement in Gen 1,
Ethereum introduced programmable settlement in Gen 2, and introduced it introduced programmable sediment in gen two and enoma introduces intent centric in gen three
all right we're going to speed it along here um with two last ones they're going to be
deep cuts so hopefully you guys can get them here um but this one this one's super deep
let's see if anyone can get it though in en, what is the atomic unit of state used to code with intents? These are the basic building blocks of intent centric
applications on Anoma. What is the atomic unit of state used to code with intents on
Anoma? The building blocks of intent centric applications. This one should really get two codes
being very generous
I think I have an answer
I think I've got a guy
they have the answer of I think I've got a guy. They have the answer
of, this is 0x
lethal with
resource. That is correct.
0x lethal. Nice job.
I love Genoma.
And the last one,
this one's a deep lore cut,
but does anyone know
what a Noma co-founder christopher goes
is known for or credited as being the lead designer of what interoperability protocol
enoma co-founder bonus points if you also know the other non-interoperability protocol
i should probably double bonus points if you know that one know the other non-interoperability protocol.
I should probably double bonus points if you know that one.
I don't think I know that one.
Is that four codes?
Okay, I can see an answer
for...
Sorry, I've just lost the name.
I've got an answer for Cosmonauts,
which seems pretty applicable.
Created IBC.
Yes, correct. Cosmonauts. Good job. Very nice. All right. That concludes our trivia show here.
Thank you to all the participants. We will reach out in DMs with your reward.
But yeah, good answers. That was pretty fun.
Going to move on to the AMA section now,
starting with some Testnet and Kato campaign questions.
So I guess these will be mostly for MRG,
if he's still around.
He's not around.
No, I'll take him.
Don't worry, I got him.
Jim can take him. He's not around. No, I'll take him. No, I got him. Jim can take him.
All right.
Yes.
So how do you plan to increase the number of participants in the Telegram chat?
Will users from the seven-day leaderboard be invited and will users who have left the
leaderboards be removed?
So that's a great question um so we are planning to take another snapshot um to
introduce some new members into the exclusive telegram chat um we're not going to give away
what the exact snapshot date uh time frame will be because it you know keeps you guys on your toes
you know a little bit of little bit of surprise it's quite nice i think um and will users who have left the leaderboards be removed no um we are not
about uh removing these people that have been in the chat they have been nothing but uh incredible
to the feedback uh we've had so even if there is a drop because you know the kaito algorithm is great
but it can be a bit of a black box sometimes so it can feel frustrating if you're dropping off so do not panic anyone in the top 100 will not be getting removed
from the chat um we we want this to grow and it's been so great so far
um that um yeah i mean we just wouldn't remove any of them they've all been great
nice i think people are probably happy to hear that one. So yeah, obviously that gives folks a reason to keep grinding on the Yapper campaign because we'll be adding you there and we'll have some more perks to look forward to.
another lottery pick of the top 1000. So if you're not in the top 100, don't be disheartened.
We will pick another 10 at random to be added into the chat as well.
Nice. Got to keep it democratic.
Exactly.
Probably should ask this one first because it's the high level question. And I'm sure maybe Adrian
can chime in on this one as well. But sort of, there are a lot of questions on the overall idea behind the test
net. You know, what was the sort of idea behind the approach we took with it, sort of compared
to maybe the usual test net experience and why? I can start with this if you want, and then Adrian can type in.
So I think, you know, in the past, we've had test nets where, you know, they're live, and then you go on and you do a bunch of swaps every day.
People automate them, they farm them, blah, blah, blah, blah, blah.
And it's like, okay, so I've done a load of swaps on this interface that looks exactly the same as every other interface I've done.
And what have I learned? I've learned nothing.
So essentially what we wanted to do was to kind of make it interesting, so there's some educational elements there, but also fun, right? We don't want people just
mindlessly clicking and automating their processes and it's just like it becomes more of a farmer's
thing as opposed to a thing that you actually want to interact with every day. So by sort of
gamifying the experience,
you get to learn about how an OMAD works at a high level
with a nice visualization, but also you're entertained.
And there's stuff to go back to every day
to keep you guys hooked so that you're not just mindlessly
clicking away on buttons.
You know, like, swap here, swap that.
And it's like, oh, have I achieved this?
Because who actually enjoys doing that, right?
So we wanted to make it fun and, you know, educational.
Nice.
Yeah, I think like the whole three level thing
is really helpful, even for me,
if I've been working with Enoma for a while,
but like to see that there's this like
one application layer on top,
and then there's all the intent magic
that happens in the middle with solvers and and
gossip nodes and stuff like that and then you have the motherboard layer where all the different
blockchains and and l1 networks are sort of settling the transaction so i think that's
it's a nice way to visualize it for folks i don't know if adrian if you had any other thoughts on
this the whole testnet approach uh no no nice okay so so we had quite a few questions actually on like why is it gated
sort of a thing. So what's the reasoning there? Is it about hand curating users or is it a matter
of stress testing it, etc.? So again, I'll take this one. I believe, you know, the referral scheme
is kind of, at least at first, we just wanted to open up to the people that we've had in our first snapshot with the top 100s.
Then it means that the people that have been there from the start and, you know, got the, you know, got their yaps up, I guess.
I don't know what the kids are saying these days, but it sounds right.
Got access to it first. And as they've experienced, it hasn't, you know, there's been a couple of issues to sort out. So basically, what that means is it allows us to sort out the, you know, the
couple of things to iron out with a smaller group of people that are being really supportive, like
I say, and giving great feedback before we sort of open the floodgates, so to speak. So not only
does this sort of iron it out so that when we
get more people on, it's a way nicer experience. But it also means that there's kind of,
you know, it's just, in general, it's kind of just letting people in slowly so we can stress test it,
iron out everything so that, you know, like I say, as soon as everyone's on, it's great.
Like that's, that's really the main incentive there and i do appreciate how frustrating
it must be not being in i can't really you know emphasize that enough we do appreciate that um but
we really want to get this opened up very soon so um yeah keep your eyes peeled almost there um nice
um how long will the testnet last? And will there be a leaderboard?
I don't know if MLG is on to take the testnet length,
but I can go with the leaderboard.
So we're potentially looking at adding a leaderboard
because we know people like to discuss,
you know, see where they are on there. but I think what we probably will introduce pretty soon hopefully kind of next week
as well when we start getting these referrals going is definitely a rank so you can actually
visually see your rank and then you guys can discuss you know you guys can do your competitions
who's first who's second and discuss all. So yeah, you'll be able to
visually see your rank, we think, at some point soon. Nice. Yeah, it looks like we got MRG on.
So there was some questions around, like, how long we're planning to run it, and, like, is there
going to be a cap to the codes? How many are going to be able to join? Yeah, in terms of like running length,
like let's get the software in working order first.
And once we get everybody on, we're done testing
and we start rolling out the ref codes more broadly,
then we can kind of communicate the length of the test net to everybody.
In terms of ref codes, we will cap them at some number.
Again, more information to come once we work
through the initial bugs, which as Jim mentioned,
is super close.
But our overall goal is to keep it open,
but also have just a small degree of exclusivity where we kind of reward our community
members and, you know, don't make it a total free for all. So that's, that's where our heads are at.
Nice. Makes sense. All right. So that pretty much wraps up the test net related questions.
Of course, we'll keep an eye on the chat if there's any more that we can answer.
And at the end, maybe we'll invite some folks on to ask questions live as well.
But we're going to move into some of the other AMA questions that were more on Anoma and Anoma's tech.
We did do a call for questions on the X announcement and the top 10 questions we're giving away codes to.
So we'll go through a couple of those questions first.
The first being here from CryptoPunk.
How does a Noma choose which decks or route to use for a swap or bridge?
I can quickly take this.
Anoma itself doesn't choose this.
So Anoma is the underlying infrastructure
to allow people to express this sort of intent
in a clear format,
and then which specific route gets chosen,
honestly, it's up to a solver.
The nice thing is the users don't have to care.
This is at the core of it, which is you sign with a specific intent and then the solver cannot
like background you front run you or change your intended in any way and so you don't have to care
whether there's like one counterparty or a thousand counterparties to that specific route
you just care that you get what you want on the other side.
Yeah, I think that makes sense.
There's one also from Crip Influence who's asking,
I think this is kind of related to what you said here,
but do I need other users in the intent gossip layer to fulfill my intent
or is my interaction with the solver only?
Okay, that's like, there's sort of a
more complex answer to this and then there's a simple answer. You don't need to
directly connect to another user, if that's the question, right? Like you don't need to figure
out which specific counterparty you want to interact with however if you're the only if no
one in the world is selling bitcoin and you want to build buy some bitcoin but there's like zero
sell pressure like zero people are selling any bitcoin uh then of course your intent will never
get fulfilled like no one does not have cannot
magically make sure that someone is always willing to sell some asset neither can any other system
but like so like you need to have a someone that's willing to take the other side of the trade
right so in this example like if no one is willing to sell any bitcoin you can't buy bitcoin so what
will happen like in the app in an app for, if no solver picks up an intent?
This is not due to the solver not picking it up, right?
The solver may pick it up, but maybe don't think about it.
You want to buy someone's house.
If that person isn't willing to sell their house, you not you like you can't do anything to like get
them to sell to you uh even if you offer them a billion dollars and they're still going like no
i don't i don't want to sell it right yeah this is something structural to just economics so in that
case uh you wouldn't be able to buy the house uh what happens in this case you intend to just
expire or you can maybe try to increase the price maybe at a trillion dollars, the guy's willing to sell his house.
Right. Yeah.
So there was another related question here from if he love,
which was, are there any fallback mechanisms in these cases? Like does the architecture support expiration,
like future expiration dates or retries or partial fulfillment logic?
Yes. It supports partial fulfillments. You don't need... I mean, you can essentially encode in your intent
whether you'd like...
You fill everything or not have it be valid,
but you could also do partial fills, of course.
You can do expiration times, sure.
Retrys you don't really...
Retrys you don't need as long as you have expiration time.
Right.
Yeah. Okay. Yeah.
Okay.
And maybe also the other important thing to consider here is that like,
you can even fall back to existing forms of liquidity.
So for example,
even if there's no direct person issuing an intent that's willing to trade,
I don't know,
some Ether BTC,
you could fall back to some like AMM running on Ethereum or running on Solana.
Right, right.
So basically to any of the networks that Enoma is connected to, you could fall back to the existing systems.
Okay, nice.
Okay, from Neo Walker, how does Enoma make intent-based transactions feel native to the users?
Like, will wallets abstract all the solver matching stuff
behind the scenes?
No user ever has to see a solver.
Yeah.
So you just sign over what you want
and then it either gets filled or it doesn't.
Yeah.
And this is kind of the whole point of the intent-centric application,
is that you're not surfacing all the complexity to the user.
Currently you have to do all these transactions, step-by-step stuff. This is sort of
just like everything happens automagically in the background. So, yeah. All right.
This is an interesting one. Now, if a bunch of people submit intents that kind of conflict,
like they all want different things and that can all happen at once,
but it's theoretically possible,
how does a NOMA decide which ones go through?
Is it first come, first serve, or will it be chosen randomly?
Again, a NOMA does not encode specific matching strategies so in case you have mutually
exclusive intents for example and only one of them can get filled um i would suspect that most
solvers like in the end the specific matching criteria are going to be up to the solvers
um and so i would suspect that most solvers will essentially order this by fees slash by time of arrival.
Right.
But they could also choose to prioritize a point of some other criteria.
Okay.
Yeah.
That makes sense.
Atulchandle03 asks,
what role do solvers play in preventing MEV and Enoma's architecture?
How are they incentivized to ask act honestly uh this is always nice um in anoma like anoma intends to sign over
a specific state transition i.e like this is uh i i currently have some Ether and I'm willing to hold some Bitcoin if and only if I get this many Bitcoin.
It's a limit price.
You know, if you sign up a shitty limit price, you will get filled.
And someone is going to make some money off you in the default setting.
So, I know that's basic infrastructure.
It doesn't really come with guardrails at the fundamental level.
So, don't sign over shitty
limit prices essentially so till you are however as soon as you sign over a specific state over a
specific intent you are guaranteed by the system that that intent will not be violated so if you
had said you are only willing to take this specific state transition then you will only get this
specific state transition right now on top only get this specific state transition.
Now, on top of it, you can build,
on top of sort of the base layer infrastructure here with Anoma,
you can start building more complex applications
that provide guardrails,
such as batch auction mechanisms
or some form of encrypted batch auction mechanisms
where users can then get more guarantees
where they can even have market price,
like can essentially send out a market order.
And then the guarantee is that like everyone in this batch receives the same
clearing price, for example.
Right. Okay. That makes sense.
We've got a couple builder related questions here from filthy war who asks,
is there an SDKdk or framework available
for developers who want to build cross ecosystem depths on anoma the second part of that is what
steps or requirements are there to integrate new ecosystems into the anoma network
I can also take this on the last, the second question.
This is purely about, you just have to implement Anoma, the circuit that implements Anoma and the Anoma resource machine.
machine, you have to implement this to be verified on a new system.
You have to implement this to be verified on a new system.
For example, you have to implement the verifier contract on Solana or you'd have to verify
the verify contract in Rust, you name it.
This is pretty much you have to implement a version of your, like you have to implement
the operating system on your chosen CPU.
Think of it like you have to implement Windows to work with Intel CPUs as well as ARM CPUs.
And if there's a third type of CPU coming out, you'd also have to implement Windows to work with that specific CPU.
The first bit, yeah, just go to docs.anormal.net and start playing with things.
And then if you really enjoy it, then ping Maurice on Discord.
Or Cameron.
Yeah, Maurice or Cameron. That is Ching Pham. enjoy it uh then ping maurice on discord or cameras yeah maurice or cameron um that is uh ching phone um cool well uh crypto ape is asking um this is also kind of an interesting question
um when intents become composable across multiple domains, the system becomes more powerful, but also harder to predict.
The question is where the cracks might show up first
and whether Anoma has the tools to observe, limit, or learn
from the chaos that results from this cross-chain composable situation.
Where do the cracks show up first?
I mean, the cracks will always show up
in the distributed systems side of things
because distributed systems are messy.
This is not unique to Anoma.
This is just like where do the cracks appear
generally in these systems?
It's in how they are connected to each other,
how different security domains are connected to each other.
Anoma has pretty good tools to handle this
because you can have even synchronous composability
between software and domains
if the valid assets opt into this.
This is a lot around the heterogeneous Paxos research
and Typhon, the consensus mechanism via Anoma.
So if you're really interested in that problem
of multi-domain controllers, do check out the paper there,
which I guess we can drop in the chat in a sec.
Yes, the interesting thing here is these problems
appear already in the existing world,
because fundamentally all the systems we currently have are these cross-domain systems.
And I think I know it's the first time that someone has spent time figuring out how to properly reason about them
and how to build a system that allows developers and users to properly reason around this cross-domain problem.
to properly reason around this cross-domain problem.
Whereas like a lot of the existing,
all the existing bridging solutions, for example,
they sort of like try to pretend
that this complexity doesn't exist.
Anomad just allows you to develop it to tackle this head on.
And this isn't just something
that sometimes shows up catastrophically.
Right, that makes sense.
Yeah, it seems like a lot of the cross-chain solutions are sort of, they make a lot of trade-offs, right? And Enoma takes this first principles sort of like higher top-down sort of approach to the system as a whole, right?
to some of these we've already talked about,
but it's kind of interesting.
So Liu Yifei asks,
given the emphasis on a unified application layer,
how will Enoma handle future upgrades
and protocol changes across this diverse ecosystem
of integrated chains and fractal instances
to ensure long-term stability and interoperability?
I mean, that's the nice thing.
Most of these systems really don't change.
Like Ethereum hasn't really changed in five years.
So, like, they're very stale at this point.
And even if they were to make massive changes,
the nice thing is, since you have this layer of abstraction in between,
you can start hiding this or at least smoothly upgrading
the operating system versions that you can move
from
first generation CPUs
to second generation CPUs
without all your applications
breaking all the time. Windows is
famous for this. Windows
even nowadays
I don't know if they dropped this guarantee
lately with new versions of Windows
but historically they even supported applications that were 20 years old that were
written against Windows 95 and they still would run nowadays and Anomai can sort of do the same
thing because it's again at the same level of something like Windows but it's like it's this
operating system abstraction it's interesting I didn't know that they did that, actually.
Windows has been tremendous, actually, in terms of
backwards compatibility,
mostly because it was used in so many banks and healthcare
setups
that they really
made sure that they were backwards
compatible. As a result, they
made some weird-ass choices over the years.
But, you know,
Windows remained really backwards compatible
all the way at least until windows 7. and we all know how we all know how fast uh how fast the us
financial system updates their infrastructure their core technology right i mean i think we're
still on it's on swipe credit cards in a lot of cases over there. So the answer is how fast does the financial system update the technology?
It's just never.
You just build a new financial system at some point.
And that's like your technology update.
Like that's essentially what crypto is doing.
We built the financial system in the 80s and now we're just building the new one.
It's like it's not going to be this like graduate upgrade.
Just like, yes, now we have a new system and it's much better.
Exactly.
Okay.
So this is the last question from the top 10 code winners.
This is from the crypto professor who's asking, does the world need another
infrastructure abstraction layer when existing solutions are already implementing
intent like mechanisms?
And more importantly, can Anoma's distributed opera system approach actually deliver on its ambitious promises of seamless crushing interoperability and unlimited scalability?
Yes. Essentially, what currently people are doing is they're calling
like they're applying a tiny sort of patch to a sucking chest wound and saying oh this is intense
that will solve everything um no one has spent any significant amount of time actually trying to solve
solve the fundamental problems of we are living in a world of thousands of chains, how do we get state compatibility going?
How do we cross-state, cross-domain state
compatibility going?
All these kinds of things are just things
that people don't like to worry about right now.
So Anoma is the first time that really we've
tried to tackle this problem.
So I'm not worried about this at all um what was the second part of this question second part was um basically you know how hard is it going to be to
deliver on the ambitious promise of uh across-chain interoperability and unlimited scalability with this architecture? I mean, it's going to be a long road, right?
Bitcoin didn't become wildly adopted in a single month,
neither did Ethereum.
This is a multi-year process, but I'm pretty bullish on it.
Nice.
And I guess, I mean, the first part of that question
on existing intent-like mechanisms,
that comes down to, doesn't it like generalized intents versus like the sort of domain specific or specialized int yet that i mean you can swap across two chains but
like because they just call both sides of both systems but it's not because they have an action
like the system doesn't have an understanding of what it means to be a multi-domain system yeah
right um okay we'll take a couple more from Twitter and Discord before we open it up to some live
questions.
CVXVCX asks, Anoma enables atomic settlement across chains using intents.
So how do you ensure finality and security when the chains involved have different trust
assumptions and consensus speeds?
Wait, could you repeat this last part of the question? security when the chains involved have different trust assumptions and consensus speeds?
Wait, could you repeat this last part of the question?
Yeah. How do you ensure finality and security when the chains involved have different trust assumptions and
consensus speeds?
You can be in a multi domain world, I have two separate
chains, for example, in a multi-domain world, I have two separate chains, for example.
You need either to use something like Typhon
so you get some shared consensus.
Essentially, you get an on-demand charted system
between these two chains.
So the valid assets agree to sort of run your piece of state
synchronously with each other, even though that piece of state
comes from two different systems.
Alternatively, you have to wait for finality on either of those systems.
Yeah, that is really, or you sort of decide that you move your application state.
So maybe your local environment, your local chain,
and then do the specific execution on your local system and then move it back.
I think those are three broad models you can pursue. and then do the specific execution on your local system and then move it back.
I think those are three broad models you can pursue.
That makes sense.
This is another one that we get, I think, every time we do an AMA,
but it's an interesting question, so worth going over again.
But how do you, this is from Eunice, who asks, how do you prevent centralized solver cartels
from forming as the intent economy scales?
So it's, in the end,
it's all going to be a latency and privacy game,
but mostly a latency game,
where if you want the fastest speed,
and here speed generally equates to cost,
you are going to go with a local solver.
So there's sort of like physics and speed of light constraints make it very likely that you'll see
many localized solvers because there's nothing the other solvers can do about this. Like a solver in
the US cannot compete with a solver in Europe if you care about speed, because the solver in Europe is just going to be faster because you don't have to send your intent over the transatlantic fiber cables.
So that's, I think, the major component, actually.
The other component is even if you get one mega solver, it's OK, because as long as the underlying infrastructure is open source and sort of
publicly available if that mega solver starts screwing with users they can just decide to
switch so like the switching cost is super low and this is sort of the other reason why i'm not
that worried about solver centralization nice okay um no, that's a common question that we get. All right, let's
wrap it up with a couple last ones here. One from Reagan, ReaganSolWeb3, who's asking about
Anoma's intent-centric applications relating to the Web2 market as well, right? Like,
are there Web2 overlap use cases for what anoma is building
yes every web 2 player in the world is going to need this kind of architecture mostly because
if you're web 2 player right now you have an existing so think of a company just as a number
of databases connected to each other um and generally the way that they have their customers
interface with those databases is via
emails or via some chatbot or via physical mail
right like when you want to
update a record with your car manufacturer
you send them a physical mail
a physical letter
so what Anoma allows you to do is to run Anoma
in sovereign instances so like individual companies can decide to run Anoma as you to do is to run Anoma in sovereign instances. So like individual companies
can decide to run Anoma as their database layer. And this doesn't mean that they publicize the
entire database layer or that the database layers are publicly readable or publicly writable. It
just means we've agreed on the state format. And now when a user wants to, for example, update a car record, they can do this from their mobile phone.
Because the application on their phone, if it's also a normal application, knows how to update that database, even though this is not a public database.
This is like the company can just expose a tiny sliver of their database to the rest of the world.
Similar between on the B2B side, right?
Like a lot of time is spent faxing around invoices.
This is kind of very stupid and wasteful.
And so one way for actually blockchains
to really help existing companies
is to make parts of their databases
readable and writable under certain conditions.
The problem with things like Ethereum and Solana
is that they were never designed for this hybrid model,
where they were always only designed,
this must be a public system and everything must be public.
And really, we don't worry about how
we get interoperability between many different deployments.
And this is one of the areas where no more green shines.
One really good example here is actually stable coins.
I live in Switzerland at the moment,
and the Swiss government is never going to give up
its monetary authority to Ethereum,
to the Ethereum validator set.
So they're not going to issue the national currency on Ethereum.
What they may very well do is issue this on a Swiss chain, essentially.
And then they can decide how much do we
want to integrate the Swiss chain with the rest of the ecosystem.
But if they just do this by
running a carbon copy of Ethereum,
well, you get none of the interoperability
stuff. That shit doesn't work.
Whereas with Anoma, you can then start
moving small pieces of state, make small pieces of state publicly readable or writable, and start moving them from the Swiss chain into the rest of the ecosystem.
right when we sort of like eventually why why do we have this distinction to begin with it should
there should just be one web and it's integrated with the sort of apps that you use every day and
the sort of crypto payment rails and everything else that comes with web3 uh so yeah yeah exactly
um one last really quick one that i can answer really fast here is from um newsron who who says man i really love your graphics who is the designer
um so shout out to chris holt here who is the magician behind the enoma designs um you can
follow him on x at i think it's what is it c r c h r i five h zero l t he's got a funny spelling
in his name but yeah he's he's great he's great. Um, all right. So
last couple of minutes here, why don't we open it up to a few questions from the live audience? Um,
so if you are one of the 45 or so people who requested to speak, um, get ready to potentially
be called on here. Um, let's see, how about Luther?
O1X Luther, are you there?
Give him a minute here.
Luther, did you have a question for the team?
Luther, did you have a question for the team?
All right, we can try calling on someone else
while we see if Luther connects here.
How about json.eth?
Jason or Luther, feel free to chime in here.
Otherwise, I will keep looking for new folks here.
How about OX Harsh?
Did you have a question?
you there harsh hey there gmgm everyone so right now i'm working on anoma architecture
series and yesterday i made post about on solver so my question is to adrian that
how does enoma stop solver centralization while staying private
now we kind of have this question already but we have this yeah i mean just very like users
fundamentally make the choice which solvers send their intents to.
They can make the choice that they send to their local solver.
They can even do a staggered broadcast where they decide to send to their local solver first, and if that solver doesn't solve it, then they send it to maybe
do global broadcast.
In the end, if we all want to use this if we like if for example Wintermute decides
every time you send an intent to their
solver they pay you $100
and then we all start doing this
there's very little we can do from a protocol
design perspective to sort of like
prevent those economics
so in the end
like whether a system is centralized or not
is very much it's a user very much a user choice of how involved users want to get.
Anoma is very topology agnostic,
so Anoma supports everything in terms of that user choice.
But in the end, it comes down to the user choice.
I would always encourage people, and I always say this,
that run your own infrastructure.
Don't just hope that someone else will figure out
how to run a failure-resistant local communications
infrastructure.
Do it yourself.
Thanks for clearing the question.
Nice.
Thanks for the question, Harsh.
How about Kratos?
Kratos, are you there?
Did you have a question from the team? Yes, I'm here. I the question, Harsh. How about Kratos? Kratos, are you there? Did you have a question for the team?
Yes, I'm here. I'm here, Jim. My question is about the three codes you mentioned about Anomar testnet giving three codes daily later on in the future to those who are already on the testnet. Does this apply to those who get referred?
Like if someone should refer me,
can I also get the trickles daily?
That's my question.
Yes, basically every...
...daily as soon as that system goes live.
You cut out for me.
I don't know if that was just me.
If that was just me, then that's fine.
You cut out. Maybe repeat that because I need to know i need to know as well um yeah as
far as i understand everyone who's logged in on the testnet will get three uh invites per day
oh okay so thank you
um let's take maybe one or two more questions here before we wrap it up.
Ruth, it looks like you got your hand up.
Are you there?
Hello, everyone.
I have a question.
How many users do you plan to take to testnet or will you make the testnet public?
I think MRG answered this one earlier. testnet public?
I think MRG answered this one earlier. Say that again.
Sorry.
Say that one more time.
What was the question?
The question was how many users were going to open the testnet to and if it will ever
be public.
I think MRG answered this earlier.
Yeah. will ever be public. I think MRG answered this earlier. Yeah, so I think basically to be decided about number of users, I think the current
plan is to never fully open it public because we want to reward community and loyalty and
all of that stuff. But yeah, we haven't decided on the total number of users yet, but we're
monitoring it.
That being said, I think the idea is to greatly expand the numbers in the coming weeks, right?
That's it.
Open the floodgates.
Exactly.
All right.
Do we have any last questions?
Let me call on samcode.sol in case he has one last one for us.
Or Ashley. node.soul in case he has one last one for us or ashley if not we will wrap it up
going once going twice oh damn did you have something? Yeah, GM.
I was going to ask, how do you guys plan to, how do I put it,
stress test your network if you're going to have a gated number of testers?
How do we flood the network and make sure that it's stress test?
Is this about the test net?
Yes, yes.
Yeah, yeah.
So like we say, I think with three invites a day
and us dropping codes, we're going to see a gradual increase.
We should never see a jump of like, I mean, tons in one day, right?
So this should be a gradual process
and we'll be monitoring the performance
and scaling if we need to.
But we think with the approach that we have
and we're taking,
I think we're going to be pretty good.
All right, thank you.
Nice.
All right, well, thanks everyone
for joining this week.
We will get back to those of you
who have won
a code shortly.
But yeah, hopefully everyone's
having fun. Can I just say one thing really quickly
on that front? If you
won a code, don't
expect it immediately. We are still
working through some of the testnet issues.
We will give you the codes and
all the rest of the codes that we promised
once we've sorted out all these issues,
just so you don't have any hiccups when joining.
So don't panic.
If you haven't got it immediately, we've got you all saved.
It's all good.
Yeah, better to get it all running smoothly before we let folks in.
So all right.
Thanks to everyone who joined.
And stay tuned.
We'll see you.
Keep an eye out on all of our channels,
especially next week as we sort of open the floodgates
for more testnet codes here.
All right.
Thanks, everyone.
Thanks, Majors.
Bye-bye.
Bye. Thank you.
