Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
Partner Spotlight: Story Protocol
Recorded: May 1, 2025 Duration: 0:54:30Space Recording
Short Summary
In a recent discussion, Andrea from Story unveiled the launch of a groundbreaking layer one blockchain designed to revolutionize intellectual property management. The conversation explored the partnership with Anchor for decentralized infrastructure, the impact of AI on content creation, and the urgent need for modernized IP solutions, highlighting significant trends and innovations in the crypto space.
Full Transcription
Music Thank you. Music Thank you. Music
Music
Music
Music
Music Thank you. Music Thank you. Music Well, hi everyone.
Andrea, are you there?
I'm here.
Hello.
Great.
Thank you for joining.
Yeah, well, I think we have waited, you know, the typical courtesy five minutes and we should be ready to go now.
Let's do it.
Great. Yeah, thank you for that. I can hear you loud and clear.
So let's get started.
Welcome, everyone. Welcome back to the Anchor Partner Spotlight,
where we unpack innovations in Web3 and, of course,
explore how decentralized infrastructure... Banker Partner Spotlight, where we unpack innovations in Web3 and of course explore
how decentralized infrastructure is shaping the future of the internet.
I'm your host and today we are diving into something that affects every creator, builder
and thinker out there, which is intellectual property or IP and well how blockchain
might finally be the game changer we have all been waiting for this is well especially exciting
for me as well since well talking about intellectual property I don't have too much of the first and
definitely none of the second so the idea of owning both at once sounds like a dream
and hey if you're tuning in today yes um it is labor day but apparently well crypto didn't get
the notification um the industry never sleeps and well neither do we um so a big thank you to Andrea for joining us today on a bank holiday because as of 2025, crypto is still allergic to days off.
And joining me, well, yes, Andrea?
No, I was going to say, yes, you're absolutely right.
But happy to be here on a bank holiday with you.
Same, same, same.
Joining us, well, he has just uh spoke to everyone is a friend from uh
or is a friend of ours from story a uh well he's also a neighbor of mine actually at a country
level um story is a purpose-built layer one blockchain that's redefining how we manage
and enforce ip in the digital age if If you've ever created something called content, music, a meme, maybe, I have created a bunch of these.
You've probably wondered, like, how do I protect this?
How do I make sure it's used on my terms?
And, well, Story is working on exactly that, unless I'm wrong.
But, yeah, we have Andrea today here to well correct me you know in
at any point if I'm wrong and anchor is of course super proud to support story by providing the
decentralized infrastructure so that's nodes and points you know the chain and make it reliable and scalable from day one, hopefully.
Hopefully we get a nice review from Andrea.
And before we dive in, I would like to invite our guest to introduce himself and tell us a bit about the role and story.
So hi, Andrea.
Hey.
Hey, everyone. Great to be here.
Thank you so much for having me on and for the opportunity to chat about IP
and, you know, and story, but most of all, IP.
I think it's it's a very much top of mind topic now
with AI content generation.
Everyone is basically able to create
anything they want at any time, right?
And a lot of that is created on stuff
that they've seen already, that they love as fans right so like if you want to
create a version of your favorite character or a remix of your favorite
song everything is now at everyone's fingertips which is amazing but if you
think about it from the point of view of who created the originals you know
they're probably wondering like,
hey, can't this probably get a little bit out of hand?
And so, I think it's,
I'm not getting into whether it's right or wrong.
I think it's amazing that everyone has these tools now,
but it's definitely a topic that over the course
of the next five, 10 years,
is gonna be something like we're basically going through a transformative shift
in how content is being created and content is being consumed, right?
A bit like how 20 years ago we went from reading, you know, to generating content and social media.
Now we're like in a new era of content. And we're in a new era of content.
And so we need a new era of IP.
But yeah, I realized I didn't really introduce myself,
so I should probably do that as well.
Sorry, I got a little carried away.
My name is Andrea, aka Marcus Devrelia on Twitter.
And I'm part of the story team.
I currently lead the foundation and have been very involved in a lot of different areas of story.
And yeah, let's just dive right into it.
Yeah, so thank you, Andrea, for the introduction to everything.
Just wanted to say this is pretty normal.
You know, it happens to everyone.
We just get carried away, you know, and yeah, and get into the topic like straight away,
you know.
But yeah, let's now set the scene.
So IP management, as you mentioned, right, has traditionally been wrapped in kind of
in red tape, right, has traditionally been wrapped in kind of in red tape, right? So it's expensive, complicated legal systems, you know, slow enforcement.
I assume jurisdiction, you know, issues and the list goes on.
Probably, you know, some jurisdictions are a bit more friendly.
Some others, you know, they don't apply the same rules.
So from your point of view, right,
what are the biggest main pain points that creators face today
when either managing or enforcing their IP?
Yeah, definitely.
I think the biggest bottleneck today is we're trying to adapt an old model to a modern problem, right?
An antiquated solution to a modern problem.
So the current way that we think about intellectual property, even just saying the words intellectual property makes people bored.
And just thinking like, oh my God, this is the most boring topic in the world.
And, and, you know, like, it doesn't have to be that way. Um, and, and the main reason for that is intellectual property was, has traditionally been managed and enforced and, know in in a very thick layer of bureaucracy of paper pen and paper
lawyers courts antiquated databases and and all of that thick layer of bureaucracy is just not
going to keep up with the expressiveness and the constant creation that's
happening every day on, on the internet, uh, through either by humans or by models, right?
There's just endless content being pumped out, whether good or bad, endless content being pumped
out every day. Like I'm talking millions of petabytes per day. It's on a scale that we can't even comprehend.
And so imagine trying to
protect and register all of that content the old way.
It's just impossible. So I think the biggest bottleneck
Neck is we're trying to solve a modern problem with an old solution
is we're trying to solve a modern problem with an
old solution.
Well, yeah, thank you Andrea for you know the insights and clarification
Andrea mentioned a
Petabyte right and I think this is not new to many of us, but
You know probably some still haven't heard of this um well what's what's this
called um of this scale right um i just wanted to to add on that one petabyte please correct me if
i'm wrong is 1024 terabytes um if i remember correctly. And one terabyte was, well, another thousand gigabytes.
So, yeah, quite a big and heavy load.
Yeah, so thank you.
Thank you for that, Andrea.
And I just wanted to add that.
And following on that as well, we also often hear about artists, small developers, you bigger, either corporations or bigger,
let's say maybe more influential artists, et cetera.
So actually it's kind of dangerous.
Like anyone can take it, right?
Big players, right?
And we don't have like real way to fight back, right?
I mean, and when I say real way,
I mean some practical, right? like something that you can actually do um why is it so hard right um to enforce the ip terms today
and i bet this is a you know a complex topic but yeah if you could share um like on a general, you know, lines. Yeah, sure.
I think the biggest question or like the,
I think the biggest obstacle today is actually one step,
one step before that,
which is people don't really think about their content as being IP yet.
And because they associate IP as being this complex thing
that only companies do, and it's only for valuable stuff.
But if you think about it, anything today can become a viral moment
in a couple minutes, and the whole world knows about them.
And it becomes a valuable IP, right?
Even the most random fragments of a video can become massive.
And so I think what needs to change is everything that you create
like everything that comes from human creation or ai creation is some form of ip especially
human creation that's the whole point of intellectual property right it's like creative
works is one type of ip and and, and starting with, you know,
going back to your point about like, Hey, like, why is it difficult for, you know, the, the small
players, the small, like the individual creators to, to protect their IP is because they, you know,
we were used to an internet where you could share your content and it, you know, um, you didn't really put
license terms around it.
You didn't really think about setting conditions.
Like, you know, it was like, okay, I'm going to upload it to social media and people will
consume it.
But that's, but that's about it.
Now you have people remixing your content constantly and on platforms like TikTok and you have
AI models training on your content consistently right and and so that creates like a like everything
that is created is consumed and re redistributed in different ways. And so people really need to start thinking about their content as IP and having an easy
way to register it and set terms means that when the next AI crawler finds your content
and wants to use it for AI training, they don't have the excuse of, oh, there was no
terms attached to this.
So I just, fair use, I'm just using it, right?
But if you do have terms attached,
then it's a different story.
Then, like, there's no excuse, right?
And I think that's the biggest shift
that needs to happen,
is everyone should be a lot more aware
of everything that they create
and set terms that they are comfortable with.
But it's very important for that to be done easily and seamlessly on the apps that people
use every day.
And so that's what we're trying to achieve on Story.
Yeah, 100%.
You know, when pretty much researching Story and checking, you know, what you guys are doing. It reminded me of a case that happened in China, actually,
which is from an actor.
The actor is 70 years old or around that.
And, well, he's been acting since, I don't know, since he was young.
And, you know, all over Chinese social media, there was this case, people took a screen snap of him reclining in a coach with a kind of funny face.
And they have been using it all over social media for years without any issues until the said actor he got into legal battles with everyone you
know and he received compensation over over well the in in i think uh it was what what what was
brought up to to court was that well he he never really approved you know anyone to use that and
court was that, well, he never really approved, you know, anyone to use that. And he got,
I think around a million or something like that in USD terms. I'm sorry, I'm not exactly sure
right now because, you know, the rates are changing. But yeah, following that example,
do you have like a real world story, you know, examples, maybe from your community, your own experience,
you know, something that, well, of how, an example of how it's being made easier.
Because in this case, well, this was a renowned actor, you know, who had the resources to
go on this kind of lawsuit.
Yeah, well, I think one one of like a classic example
that's happened on the first day of story being launched on mainnet is that our on the first day
yeah is our okay our official mascot was used to create uh derivatives right and that was done
completely permissionlessly so we registered our story mascot, which is Ippy.
And we registered it on story and we set the terms for it.
And then different, especially one team on day one,
and I think Exo here, who was listening, you know you you know this well but uh we uh they they created a um
like a pfp collection called pippy uh that was built on the mascot so it was like all derivatives
of of the mascot and it was completely permissionless and and they licensed uhppi's likeness permissionlessly
and created the collection.
That's just one simple example,
but that's an organic example that happened on day one.
If you think about it,
the real thing that was special about that is that team was able to,
and then there was actually a follow-up team that wanted to do the same thing,
and they could just do it permissionlessly.
They didn't need to ask us for permission,
they just needed to mint a license and run with it.
So obviously in the Web2 world,
this is a, if we extrapolate this behavior to the Web2 world,
it's like, you know, I think there's individuals who want to use IP.
That's one thing.
But what's becoming more and more pressing is AI models training on content
and being able to generate content in the same style in the same
uh you know uh using the same let's say artificial skills of a specific artist or
studio right like like studio ghibli uh that craze that happened a month ago that was
like you can't blame every person in the world that tried to turn their family photos into stupidly for doing it.
Because, you know, like, that's not who you should go after.
Who you should go after is, why doesn't the model have mechanics built in to reward back what made that craze possible, right?
And you can't do that unless at the model level,
you have ideas and you track attribution
and you know the terms for all the content
that you're using for training.
So, you know, I'm imagining, I'm imagining a future where every AI model,
every time you use it for something,
it has different heat maps in the weights
that correspond to different clusters of data
that is being used to generate that output.
And each specific cluster of data
is tied back to who contributed to that cluster.
So if you create an image in the style of Studio Ghibli,
it's going to trigger a very specific cluster
in the training dataset
where most of those images belong to Studio Ghibli,
and that should give back some part of the subscription fees,
some part of the API fees back to Studio Ghibli.
That's the only sustainable way for things to happen.
But again, just to close off on this topic,
what needs to happen is there needs to be an easy way
to at least start attributing who has what,
and what data was used for AI training,
and registering them and tracking them that way
is already a big first step.
Yeah, thank you, Andrea.
And that's really, well, smart,
because, you know, honestly, and innovative,
I think is the word,
because the first thought that came to my mind was,
oh, wow, you know, what we are going to do is we're going to restrict.
Well, ideally, you know, restrict the AI models.
And whenever, you know, they are trying to use some kind of intellectual property that, well, they are not allowed to, it would just jump on and say, oh, sorry, but, you know, we can't do this.
it would just jump on and say, oh, sorry, but, you know, we can't do this.
But, yeah, actually, what you have said, you know, giving back to the actual either creators, owners, you know, call it whatever,
that makes a lot more sense.
And, well, I mean, you're the professionals, right?
So, yeah, thank you for the insights.
And I'm definitely already learning, right, thank you for the insights and I'm definitely already learning from you guys.
And well, now that we have established the problem, I think it's time to talk about the solution or the potential solutions that you have and you have brought to us today.
And of course, which is what makes story such an interesting player in the space
so what exactly is story right and um how does it solve the issues that you have just been
talking about um well i think we've been talking about them for the last 20 minutes.
But, yeah, maybe, is there specific points that maybe you want me to dive into?
You mean, like, what's, yeah, can you just repeat the question?
Like, yeah, so we have already spoke about the problem.
We have spoke about what are the potential solutions.
Yeah.
But I, like, to be really honest with you.
Oh, like how a story works.
Yeah.
Yeah, we were talking about, so I thought we were talking about in general lines, what were the ideas, right?
What were the potential solutions?
And now I wanted to deep dive into what the story is actually doing.
But if I now understood correctly, all that you have said is already what the story is doing.
Well, I think some of... No, no, no, you're absolutely right.
I think some of the things that we discussed are what the story is already doing,
but some of them are obviously, you know, they were more general questions.
So absolutely, yeah, I think to give everyone a TLDR of how a story works,
it's anything that gets created, any form of IP can be programmatically registered.
Either, you know, on a no-code platform, which we call the IP portal,
by anyone, even artists that don't know how to code,
or even better, through different applications
that integrate with Stories.
So anytime you create, let's say, a piece of art,
once you're finished, it gets registered.
And without you having to do anything yourself, right?
Because people are lazy, and they never want to do extra steps if they can help it.
And what happens is practically, right?
Like if you want to, I'll give you like a little bit of the, for those that are technical here and want to know a little bit of the details.
is every IP on story has an IP account
that is token bound to an NFT
that represents the IP asset, right?
And the NFT is just used to have
something that represents something unique, right?
What's interesting is the IP account.
The IP account is where you set terms for your IP.
You can choose, we have something called the programmable IP license, which is called the PIL.
And that license is a standard copyright license that anyone can use and configure however they want programmatically.
So like all the terms are mapped in code.
And so you can like write code around different conditions of the terms.
You could, for example, browse different IP based on
different terms, is this enabled for commercial use?
What's the revenue share?
What are the attribution clauses?
Blah, blah, blah.
But we make it super easy for anyone to register
the IP because you don't need to be a lawyer to
to configure it we already have some some some defaults that are like you know what people
usually choose which is like non-commercial remixing open domain commercial use uh
commercial remixing like there's like couple of presets, which we call flavors,
that anyone can use or you can configure it on manually.
Usually that's done either on the app that you're using,
or via the SDK,
or via the IP portal if you don't know or don't want to code.
I actually recommend everyone to try the portal because it's a great way to actually
tangibly see what happens when you register IP,
like, and what it means.
You go to portal.story.foundation,
and you try to register your first IP,
maybe an image that you have that you've created a long time ago,
or maybe your picture, right?
And you'll see what the flow is like.
And then anytime you, once you've set terms to your IP,
anyone can mint a license to use that IP, however, you know, you set based on the terms that you set.
And yeah, and that's pretty much,
like I could get into more technical details,
but I think that's pretty much like a high-level overview.
Also, one interesting thing about the programmable IP license,
going back to our earlier conversation, is you can, in the license,
you can set whether your content can be used for AI training or not.
So you explicitly set your terms around AI training,
which is a massive first step for content on the internet.
Because if you think about it, content on the internet,
as we were discussing earlier, doesn't have any terms attached, most of it, right?
Or some content is just, let's say, in air quotes,
protected by standard terms and conditions of massive social platforms
that are already striking deals with AI companies
to give your data.
So by individually registering your content
and explicitly opting in and out of AI training,
you are protecting your IP on a legal layer, right,
from AI training, if that's something that you don't want.
Well, thank you, Andrea.
And yeah, definitely insightful.
Let me just tidy it up a little bit,
or if, you know, just to check if I understood correctly.
So let's say me, for example, I produced this one image for a recent announcement that we have made.
Right. And so I make this picture and then I download the app that you mentioned.
So it's super easy.
I just go there and select what kind of protection, you know, terms, conditions, etc.
I want to give it.
Yep.
And that's it and that's it and then you click register and it's done and you can share that link with anyone in the world and
they can come and legally license your content and use it uh based on their terms that's how easy it
is and what what's even more interesting is once they do create a license, mint a license and use your work, right?
Whether it's to create their own version of it,
whether it's to remix it,
whether it's to use it on a t-shirt and sell it,
they can register that as a derivative of your work.
So you can start to populate a graph
of everything that happens from your original content.
Oh, that's interesting.
Yes.
So definitely recommend going to portal.story.foundation
and try to register.
Yeah, definitely.
Thank you for that.
You know, you're like always a step ahead, right?
Like I have just gotten there
and then you come to me already with the derivatives, which is I hadn't even thought about that.
So that's super interesting.
And yeah, we've been talking also about minting, you know, and you mentioned the accounts are also linked to a token.
You mentioned that they're token bound to
the ip asset yeah token bound right so um i think people might be surprised to hear that the story
is its own l1 blockchain um and especially in a world that's full of l2s, right? And also modular layers, etc. So that's kind of a unique move, quote
unquote, right? So why did you guys decide to build a brand new layer one?
It was actually, it's one of the few cases in Web3 where we actually started with the
problem and worked our way to the solution. where we actually started with the problem and worked
our way to the solution.
So we actually didn't want to build a blockchain at all.
So two or three years ago, we started wanting to build a protocol, right?
And we built it, which we call the proof of creativity protocol um that was just the
collection of smart contracts that make story possible right that that make program that make
ip programmable so that represents legal code uh royalties uh you know revenue um disputes all of
like it's millions of like no no not not millions, but it's like hundreds of contracts
and probably like a hundred. Okay, I have to check the line count, but it's like tens of thousands,
if not a hundred thousand lines. It will potentially be millions someday. It could
potentially be millions in the future. Yes. And once we finished
right the original plan was to just
deploy it on different chains
and have the protocol live on different chains
right but then
we realized two things
the first thing was
if we do that then
all of the state
across different chains will be
fragmented
and we'll need to anyways build a, you know,
like a metalayer that condenses all of the state, right?
And secondly, the gas on different chains would cost,
like potentially, for example, on Ethereum would cost a lot.
And so how do we solve the state fragmentation and how do we solve gas?
Well, that's an L2. We said, let's build an L2.
And so not many people know this, but last year we were very close to launching an L2.
We were days away from launching it. We had built it. We had built an L2.
And we were so close to launching an L2. We were days away from launching it. We had built it. We had built an L2. And we were, you know, so close to launching it,
but we quickly realized, like,
when we really started doing, like, stress testing is...
An L2 is kind of limited by how it has to roll up to its L1, right?
And we, you know, we were doing it on,
I don't even remember
whether it was optimism or whatever,
but we had an L2.
And the protocol to regulate IP
and to regulate all of the terms
and to regulate all of the royalty payments,
once you get complex structures of IP
where you have hundreds of parents, right?
Because let's say you create an IP that's based off of 50 different artworks
and 30 different songs or whatever it is, right?
Or like one sound from this guy, one soundtrack from another.
There's a lot of hierarchy and complex relationships that go into IP.
hierarchy and complex relationships that go into IP. And unfortunately, the gas limitations of the
L2 were way, way, way too restrictive. And so we could only have like four parents for any given IP.
And if we got lucky, we could have eight. But anything above that would just fail completely.
That's quite limited right yes yes so so basically we just realized like okay we need a single consolidated
state we need to uh make the execution we need to have full control of the execution environment
and the consensus layer so that we can basically optimize it for something that is very relational in,
in, you know, in form and, and, in, um,
in the way that it works, uh,
where it can have many complex relationships.
And so we enshrined the whole proof of creativity protocol on the L1 and,
and we have full control of the stack. So, um,
all IP related operations are very efficient and very fast.
And we're continuing to basically customize more and more of the stack vertically
to be as purpose-built for IP as possible.
So even swapping out standard databases for more relational, like graph-like
relation type of databases, right? Where you have to traverse complex trees of relationships.
You have to check different license terms across different parents. You have to
do checks and balances of royalty flows across multiple layers of hierarchy,
not just parents and child,
but also grandparents and grandparents and grandparents, right?
So it really could balloon very, very quickly.
And so that's like, yeah,
it was obviously not an easy decision to basically throw away the L2 and start from scratch,
days away from launching it, but that's what we decided to do.
And that's the reason why Story is where it is today.
So we really had something in mind that we needed to create,
and we just kept going further down the stack as we created it until we didn't face the roadblocks that were stopping us from from achieving it. Of course and you know how you so first of all thank you so
much Andrea and you know I think it makes perfect sense actually and how
you presented it you know in a super clear way and you provided so much
context. I know many people will say oh but you already had it built why didn't
you launch it
anyways? You know, and blah, blah, blah. And you have wasted resources, whatever. But sometimes,
you know, this is just what happens. And well, I'm not trying to justify anything, right? But
there's so many things going on in the behind the scenes always. And sometimes it's just, it just doesn't
make sense. Right. Or maybe it's not as suitable as we first thought. And well, we have to
abandon things. Right. And it happens all the time. So that's a hundred percent understandable.
And yeah, I realized, so there are some voices out there that say, oh, but layer ones are so inefficient or layer ones call it whatever, right?
That, hey, they're trying all these maybe more efficient, quote-unquote,
layer twos, layer threes.
I saw someone claiming layer four.
I was like, what?
But, yeah, sometimes it just doesn't suit, right?
And now it seems that we are back to the, well, let's create a layer one
for a specialized use case, right?
And, well, I don't want to show too much.
But, yeah, you know, we have been recently working really closely
with the layer one as well, which was, well, Testnet was launched yesterday.
And yeah, it just made me realize that
and just wanted to share these thoughts.
Sorry for, you know, just taking so much of this time
and also for being carried on.
Now, Andrea, just shifting gears a little bit,
very quickly to talk about infrastructure, right?
Which is, well, as you all know,
this is where Anchor comes in.
Just a real quick question, you know,
to provide a little bit of context to our listeners,
to our community as well.
So, Andrea, what role does Anchor play in the infrastructure stack?
What does it enable for your team, your community developers, etc.?
If you could share a bit about that.
share a bit about that?
Yeah, sure.
Well, you know,
I think
infrastructure
is...
People always say that
Web3 needs more apps and less infra.
And that's true, but we also
need the infra to make the app smooth,
right? And obviously at Story
we're focusing a lot on the
app layer. but it's only
thanks to the fact that we have like a solid infrastructure behind the scenes right and so
anchor is definitely one of uh one of those examples where um you know we're we you know you
you you guys and and the fact that anyone can run uh an an RPC very easily makes it super smooth for anyone to just onboard onto story and run their own node very, very easily.
And we work with infrastructure partners that can supercharge and empower all the devs building on stories.
all the devs building on stories and and anchor does exactly this um so making um accessibility
And Anchor does exactly this.
to all the on-chain activity and all the on-chain data um very very easy so very very excited for
our partnership together and and um and i think you guys also have, you know, a premium RPC plan, but that is pretty beefy and very, very performant.
So that's always useful for the power users out there.
Yeah, gracias a think, you know, I would like to try to represent Anchor in this regard.
We love seeing, you know, how you've been able to deploy and give developers, of course, the tools that they need to build.
build um yeah hopefully you know we can continue to do so for a very very long time which would
also mean that the blockchain and crypto continues to grow right um and yeah um thank you for that i
will you know make sure to uh to tell our listeners well our listeners have already listened in this
case right but to tell our community well that if they want to know what Anchor is doing with the
story, they will, they can learn from you firsthand.
And yeah, thank you again for that, Andrea.
Now, zooming out a little bit, I would love to explore what, you know, the existence,
right, of story means for the broader ecosystem.
So in this case, we've been talking about IP all the time,
but this should be called decentralized IP, right?
Quick, quick, quick question.
It should be called programmable IP.
So, I mean, it is decentralized because if you think about it,
having a decentralized, immutable registry where IP can be registered to
and read from and licensed, I think, is the perfect use case for blockchain.
IP is one of those few use cases that make perfect sense to have on blockchain
for that reason but the fact that it's decentralized is just like a
I like to put it this way it's like everybody can contribute to, like, everybody can register their IP on Story and license their IP on Story and
manage their IP on Story, but not just anybody, right? Like, the fact that it's decentralized
doesn't mean that whoever registers their IP and sets the terms doesn't have control over it. So,
is doesn't have control over it so um yeah i that's why like i think the the the distinguishing
factor of story is not that it's uh you know uh decentralizing ip which it is which it is but
like the real the real shift in how ip works in the world is that now IP can be programmable.
You can actually write code around IP.
You can register IP programmatically.
You can license IP programmatically.
You can register derivatives of IP programmatically.
And so when creation happens at the speed of the internet,
when creation happens at the speed of prompting and AI models,
all of that can be reflected programmatically as well.
Right.
And that's just not possible without a programmatic IP layer.
Right.
Right.
Well,
yeah,
it was,
you know,
I had this question in my,
in my list of questions,
but then I suddenly,
you know,
just,
it was like,
is it,
you know, how should we is it you know how should
we call it like um so yeah thank you thank you so much for the clarification and for the insights
you know and um i think also you have covered um a lot of ground today you know and how this could
change industries especially when it came to to music i think that was quite an enlightening kind of analogy, right?
And especially with all the remixes, et cetera.
Do you have anything else you would like to add on this regard?
You know, maybe what kind of ripple effects
you think it could have on industries?
We have talked a bit on, well, I think we could say it's art, right?
And music as well.
Licensing, even AI.
Or should we just move to, you know, what's next for a story?
I think the biggest, I would say, call to action for anyone listening
is to three things.
The first one is, as we discussed earlier, check out and try to register your first IP on the IP portal.
So go to portal.story.foundation and see what it means to, in a couple clicks, register and own your IP for once.
for once. Second is for any builders and developers,
you know, we have a very, very obsessively curated
documentation by our amazing DevRel team. So definitely go to
our docs and check out any of the getting started tutorials
and like try to program IP yourself. And I would say
thirdly is, you know is try out the ecosystem.
There's a lot of apps right now that support
and have integrated with Story.
And to answer your question around what's coming,
we're definitely working along a lot of different angles
from working with governments
to working with Web2 applications that are excited to use Story because finally their
artists, their creators can own their IP for once, right?
So one example is a collaborative painting tool that has 3 million Web2 users,
and they're integrating with Story so that anytime artists finish their work,
they can register it from the app that they're using.
So not having to go to Story and not having to use any other application
except for the painting tool that they're using.
So that's a very, very important example of IP should be where the users are,
not expecting the users to go to different applications to register it.
No, that last quote was great.
The thing is, before we wrap up, we always like to give the final word to
guests, but I think we have a
quote here already. Typically
I ask, hey, do you
have any kind of quote,
any kind of remark that you would like to make?
And yeah,
that's actually
all the questions that
I had for Andrea.
Andrea, do we still have a little bit of time um to go through maybe you know community questions if they have anything sure
i have uh i have 10 minutes oh cool um yeah let me just go through the comment section real quick. And then, yeah, if anyone has any
kind of question for
Andrea, which either is
regarding the
layer 1, the IP,
any kind of question, please.
Well, just
request to speak, and
we'll be there with you.
GMIP, GMIP.
Okay, what I see is people saying GM and hi. to speak and we will be there with you. GMIP, GMIP. Okay.
What I see is people saying GM and hi.
GMIP, GMIP.
Oh, well, sorry about that.
I thought we had some questions in the comment section.
But yeah, again, we have covered a lot of ground today.
I've covered a lot of ground today.
So it's understandable.
So it's understandable, you know, if, well, if there are no questions left from community, from me.
Let me see, we have another new, okay, just again, GMIP.
Well, let me check real quick.
GMIP to everyone back. That is the, you know, that's the best form of quick. GMIP to everyone back.
That's the best form of question, GMIP.
Oh, okay.
Okay.
So I assume that's GM and IP put together, right?
That's a great assumption, yes.
Oh, okay.
Okay, cool.
I was wondering, to be honest, but then I was too afraid to ask.
Not gonna lie.
But yeah, thanks everyone. And also GMIP.
So before we wrap up, well, I typically like to, you know, hand you the mic as well.
Of course, not physically, unfortunately, Andrea.
I'd like to hand the mic to our guests for a call to action.
You know, where can we learn more, where can we, etc.
Could you do it one final time?
Where should we go?
How do we learn more about story?
You know, how do we get hands-on?
Yeah, just as I mentioned earlier,
register your first IP on the portal,
portal.story.foundation.
Definitely follow the
story
Twitter handles, at storyprotocol
and at storyecosystem
if you want to learn more
about what's happening in the ecosystem.
And yeah, for all
the builders, go to docs.story.foundation
and get started there.
Right, thank you. Yeah, you all the builders, go to docs.story.foundation and get started there. Right, thank you.
Yeah, you see both accounts over here.
So, you know, it would be great if you could give them a follow.
Also, follow Andrea as well.
And, yeah, if you would like to read more about what's IP and also how we are working with IP,
more about what's IP and also how we are working with IP.
You have over here attached also the well, some content from the anchor channel.
And well, and at anchor, as I was saying, Andrea, we always like to give our guests
the final word.
So whether it's a piece of advice, a favorite quote, a personal kind of sign off,
which I think you, you already did.
Right. a favorite quote, a personal kind of sign off, which I think you already did, right?
But yeah, if you would like to close it again any way you like, you're more than welcome
to do so.
If not, I would just directly do the outro.
Let's do the outro.
Thanks, everyone, for joining.
All right.
So thank you.
Thank you again, Andrade.
And thanks again for being here, especially on the holiday. Thanks, everyone, for listening and spending your time with us. It's been great. If you enjoyed this episode, you know, hit follow, share it with your community. Give Andrea, give Story a follow as well. And of course, tune in next time as we continue highlighting the builders and projects, right? Redefining what's possible in Web3.
This time a really, really important topic,
which is intellectual property.
Just a final reminder.
And well, until then, you know, stay curious and keep building.
We'll catch you in the next one.
So thank you again, Andrea, and super happy to have you here today.
Bye, everyone.
Thanks. So bye, everyone. Take care. Andrea and super happy to have you here today thank you bye everyone thanks so bye everyone take care
