Projects
![]()
No projects found
Investors
New
DAO Treasuries
DATs
Lend / Borrow APRs
Chains
Categories
Spaces
TOOLS TALKS Episode 2 | A Sequence Recap
Recorded: July 29, 2025 Duration: 1:00:00Space Recording
Short Summary
In a dynamic discussion, Sequence and Scale leaders unveiled exciting developments, including the launch of Data 2073, a new gaming project, and the innovative FAIR blockchain, which promises MEV-free transactions and enhanced security. Their partnership continues to drive growth and innovation in the crypto space, setting the stage for a new era of decentralized applications.
Full Transcription
Thank you. Thank you. Thank you. Thank you. Music All right. E-G-N to all of us here for the final edition, final rendition of Tuesday Tools Day.
This is the culmination of a month-long of co-marketing, of information sharing, of getting
the word out about the relationship between sequence and scale. We are lucky enough today to have Sawyer here from the scale side
and James here from the sequence side.
Guys, can you please take a moment to introduce yourselves?
Maybe James will start off with you first as the guest.
Oh, what an honor. Thank you so much for the introduction. So yeah, really
excited about everything happening with the Tuesday Tools Day. I love the name. So yeah,
really excited that we got to showcase, you know, the partnership, the work together,
and the technical stuff that you can build on scale with Sequence. A little bit of myself,
I'm James Lawton. I'm the head of DevRel here at Sequence.
So I work with a lot of our partners,
everything from gaming to DeFi
to everything in between
on how to integrate the Sequence stack,
how to use it the most effectively.
And I've been in crypto for quite a while now.
So I'm an avid on-chain enthusiast.
So I'll go ahead and turn it over to you.
Awesome.
Thank you so much, James.
I don't know if I can follow that interrupt.
That was much more, I feel like, just exciting than mine always is.
Yeah, no, great to be here.
Always love speaking about scale and being allowed to represent the community here.
But my name is Sawyer.
I run Scales Developer Success Team and am one of the lead community developers, very active in the scale ecosystem.
Similar to James, I work with the majority of the projects building within the scale ecosystem, although these days, shout out to Manel, who actually does a lot of that for me as I take on other things within the community and within the ecosystem.
But, yeah, very excited to chat about building with scale and sequence.
It's one of my personal favorites, just in terms of how easy it is to kind of get up and running.
And the sequence team is just one of the best in the space. So yeah, let's kick things off.
Great. Yeah, I'll say, you know, I think, speaking from experience, anybody who works in the
developer relations, developer success field, not only has to be able to get in, roll their sleeves up and get dirty on the code, but also be able to communicate effectively to people like myself who sit on the marketing side or maybe those that are a little less technical.
So over the past month, we've talked about a lot of different stuff together.
You know, we've gone over, you know, the wallet SDK, taking a look at the sequence marketplace,
and then also the sequence indexer. And I thought instead of maybe diving directly into each of those
topics, we could take a look at it from a builder perspective. Now, say you're a builder of a specific project, and James,
I'll start with you on this. I mean, we can go one at a time on these, but at what stage of the
build or what stage as you're interacting with projects that are looking into Sequence or looking
to partner with Sequence, where are you stepping in and helping them to implement maybe each of these
different tooling options? Or maybe where are you recommending that they work with each of these
different things? Or how does that process work? That is a very interesting question.
So I think with most integrations, you know, they typically run the gambit of really when you start talking to a developer, when you start helping them with the integration.
I would say in general, it really depends, especially if they're like primarily on the gaming side.
I'll touch on that first. first, if they're like, let's say a typical game developer, but primarily in web two,
and then they're introducing blockchain technology into their game, into their app,
then it makes sense at a very early stage process of that. In order to make sure you're building
the scalability in mind, we can help you a lot, not only the technical side, obviously,
And we can help you a lot, like not only the technical side, obviously, like I'm here for that.
But we also have people that do like advisements on like game successful and report on it to you know grant
programs or advisors VCs whoever you're trying to you know showcase kind of your metrics to
so generally to sum up your question is early stage is better however because sequence is like
so modular that we frequently get people like they will come to us even later down kind of the development journey.
Maybe they already have a game or app built out and deployed and they come to us because they, you know, their indexer all of a sudden jumped up 5x in price.
Seen that happen in like numerous amounts of times.
And then they want to, they're looking for a different solution.
So even like a very simple integration, like replacing your indexer can be done like at
a later stage and kind of the development life cycle.
Got it.
Got it.
Yeah, no, thanks for that.
Yeah.
So if you want to get in and work with sequence, it's to start right away than um i guess wait a little
bit and wait a little bit figure out oh wait maybe i can't do this on my own and i should be plugging
in with somebody um and and sawyer i'll toss this in a similar vein over to you um as you're working
with projects that are building on scale what is your role in terms of also then turning around and connecting and saying, hey, you should take a look at what Sequence has over here and implement it?
Or how do you find what is the ideal fit for what Sequence provides for what the different types of partners that are building on scale?
for what the different types of partners that are building on scale.
For sure, for sure.
Before I answer that, I need to start by giving my very quick intro to scale
because I forgot to do so at the start, which seems to be happening a lot these days.
I see Falcor in the audience.
He should really yell at me because it keeps happening.
But really quickly, for everybody that is listening or will listen later,
Really quickly for everybody that is listening or will listen later.
Scale is a multi-chain EVM compatible network,
home of zero gas fee compute.
It is one of the top gaming blockchain networks in the world.
It has a variety of amazing features,
things like native RNG, native Oracle, native file storage, etc.
It allows you to take your existing
applications from ethereum or any l2 and bring them right to scale and start working with zero
gas fees uh instant finality and infinite scalability in pretty much just minutes so
yeah if you're a builder please let me know now as for how that plays in with, you know, when we work with projects and, you know, work with partners like Sequence, it's really dependent on the project, to be quite honest.
Every project is different.
And that may sound surprising, but I've talked to people about this for years.
And the reality is there's just no like standard process that works for everybody.
So in general, what kind of happens is, you know, when teams come and start building on scale, they come to us in a variety of different ways, right?
They're either introduced, they come in through our discord, they fill out a form online, you know, they're looking for, you know, grants and things like that.
Whatever it may be, we have a lot of projects that come to us and they go through various different processes and start working with different members of our team.
As that happens, usually at some point, usually relatively early in the process, if not right away, either myself or one of my colleagues on the developer success team will be looped in to chat with the developer, the technical founder, whoever it may be.
What we do on our side is we try out of the gate to get basically like a bird's eye view
of the project.
We want to understand everything we can, what they're trying to do, what tools are thinking
about using, what they want their experience to be like, things like that.
using, what they want their experience to be like, things like that. And from there, we then work to
connect the best partner, you know, and best partners to help them succeed. In some cases,
right, if people are trying to be, you know, super decentralized, like decentralized to the max,
they want only, you know, pure non-custodial wallets, right? We say, hey, go check out Sequence.
They may say, oh, well, I don't think that's what I want. We say, okay, that's okay, right?
But for most people, when they actually look at Sequence and they see it's heavily,
a very good decentralized option, they say, oh, this is great. I'd love an introduction to the
team. At that point, we go and basically make the introduction. So again, it's very dependent
on what the project needs, but whether it's wallets, marketplaces, on-ramps, indexers,
there's a variety of different components that make up building a project within the Web3 space.
And what we want to do is we want, you know, the best fit for them.
And, you know, obviously we're here today
talking about Sequence,
but I would definitely say that on our side,
Sequence is one of the most recommended,
one of the most recommended partners
that we introduce to our projects,
just because their history of, well of stability and just good support and having
what the developers needs has really been helpful for us.
We can help more projects get live faster and find success sooner on scale thanks to
partners like Sequence.
I love it.
Yeah, I'd say every time it seems like, you know, we end up working together.
I know from the marketing side, you know, there's a great relationship.
And it seems like from just across the board, there's a lot of alignment between, you know, the two projects.
Just, you know, kind of following on that thread a little bit, you know, when you think about how obviously there's a third party in a project, whether it's a game or a DeFi application, that both Sequence and Scale are getting integrated with.
sequence, and scale teams in those integration conversations,
in that integration that's actually taking place, you know,
with the third party project that's being, you know,
that's using both of us. So, you know, maybe I'll toss a coin over here and
Sawyer, you go first this time.
Sure thing. Yeah, I would say it really depends on the project. The deeper the project is,
Sure thing. Yeah, I would say it really depends on the project.
technically, I think we see a lot more overlap. A good example of that would probably be,
like I think, the last Monarchy. They're a project who uses Sequence. They're built on scale,
as well as a couple other chains. And when they were building out on sequence, we were all in a shared chat going back and
forth.
We were kind of debugging some various issues.
We were both helping with various pieces of guidance.
And then ultimately, you know, the sequence team was obviously handling more of the tooling
side.
You know, I believe the sequence team did help with some of the game economic pieces
there as well, if I'm not mistaken. And we were helping more so with just the scale specific
features, more of like the custom smart contract side, how to take best practices there. But I'd
say, again, it really depends on the project. This is something where good partners, we don't
have to have a, it's not
cookie cutter, right? We've had other projects where we've introduced them to sequence and
outside of just doing some, you know, quick, our standard kind of QA checks before the project went
live to mainnet, there was really no, like, kind of no commute there was no need for communication back and forth
between the scale DS team and the sequence developer relations team just due to the fact
that it was so smooth right it was just like put in the project it worked etc etc so really
depends on you know the project there but at the end of the day if projects are having
issues if there's new features on either side
that we're trying to integrate or make happen,
we're, I think from, at least on our side,
we're happy to go as deep as we need to go
to make it happen.
And from my experience with the sequence team,
I would say it seems like they're willing to do the same.
So, over to James.
Beautiful, you just summed it up, sorry.
You stole all the shilling I was going to do on scale.
So, yeah, personally, I recall many times,
we've been in chats, whether directly with partners
and working together to basically,
how do we optimize the sequence integration
in terms of scale for a particular game?
I think that's a big part of it.
And I think also, you know, not only on the technical side,
but like also the, you know, strategic side of like, okay,
how do you see how many NFTs were minted by a specific project
or transactions that were done is a pretty frequent ask
from like different chains.
And they want to analyze, okay,
what is the success of their project?
And like, are they really, you know,
generating all this activity?
And so I think those are also things that we work a lot
with the partner and a scale on is like,
how do we showcase these metrics in a way that makes sense?
So it's a win-win for everybody.
And I think in terms of like the actual game integration, like definitely from both parties, we work
pretty harmoniously together in order to have something that's scalable and it works great
with the technology that we've all built. And then there are those things that I find that probably a game or an app doesn't or shouldn't need to care about.
So like, for instance, we work together with scale of how do we optimize our indexer on specifically scale
and maybe configure like how we actually index the chain and how we do kind of like logging and these kinds of things that have a lot of nuance to them.
But does a game or an app really care
of how that kind of gets accomplished?
Probably in most cases not,
but that's an important consideration of like
when you're working with an infrastructure provider
and a blockchain of like,
how do you take advantage of both these technologies
and make sure that like the integration is done
in a way that's scalable and you have the same experience
and a scalable experience for the gamer app.
Yeah, to me, it feels, you know,
like both sequence and scale look at it, you know,
very user focused.
And that is like, what can we do to provide the user with the best possible experience at the end of the day?
And ultimately, that flows through providing the tooling, providing the support for developers to create those experiences.
And so, James, I'm going to ask you this question first here.
And, you know, as a tooling partner, how do you come across or how often do you come across
builders who believe that they can build, you know, what sequence provides, whether that's a
wallet, whether that's a marketplace or, you know, an index or whether they can build it better or faster, cheaper,
you know, in that capacity.
And how do you work with those type of developers who maybe look at, say,
this is my project. I want to do it myself.
I don't want to necessarily utilize a tooling partner.
That's a great question.
And that's the eternal struggle of every engineer, I think, in the world of like, what do you
buy versus build?
And I think especially when you talk with like, I like to think we have really talented
engineers on our team.
And I can attest working in this space for a long time, that they're the best that I've
worked with, is that you have the tendency a long time, that they're the best that I've worked with,
is that you have the tendency, even internally,
where you're like, oh, we can build this ourselves,
we can do it better, faster.
But then you also have to analyze, like, is this really, you know, in our wheelhouse
and something that we want to own
and then, like, be, you know, well-known for
and put into a production or scalable system.
So I think that's one thing like to analyze from like,
especially talking to a lot of developers.
Frequently when we talk to games or apps,
that's a pretty common thing.
But usually we talk to them with a sense of like,
what is your unique value proposition?
What is your app really want to achieve?
Because in the vast majority of cases,
you're simply going to save money by working with sequence.
And I've seen it many, many times.
Building your own indexer,
if like to do this requires a lot of engineering,
a lot of data storage, as an example.
Same thing with wallets.
You've got to go through a lot of auditing processes, months of research and work to actually integrate a wallet and so on.
So it's a non-trivial amount of overhead.
And the vast majority of people, they don't want to necessarily be a wallet provider if they're
building an application or game or having to maintain that infrastructure. So simply by
working with Sequence, you can accelerate kind of your go-to-market and save costs on like, you know,
your engineering perspective, and then double down on the things that like make you unique.
So that's what I always talk to projects about
that kind of raise this of like,
oh, we can build our own marketplace
and we can index all this information.
It's not a huge value add I can see.
And in most cases,
and I would say 99% of cases,
they want to be actually known
and have unique value proposition for something other than, like, the backend infrastructure.
That's the fun part about working on, quote-unquote, boring stuff, but really important to actually build a scalable gamer app.
Yeah, yeah, I mean, that makes a lot of sense, right?
It's, I think, the age-old question
of like money or time. And, you know, in this industry, right, a lot of times it comes down to
how can I get quickly to market? How can I get quickly users to be adopting my platform,
to adopting my product, to start getting, whether that's gamers or DeFi users,
how do I start to get that into my application? And, you know, that's the struggle I think a lot
of developers face is deciding where to allocate that time or those resources.
Sawyer, I want to ask you the same question, because I think it comes from a different perspective on your side.
How do you balance, you know, this same type of conversation with developers that are building on scale?
For sure.
You know, I have a very similar, I'd say identical opinion to James here is like, don't reinvent
I'd say identical thing to James here is like, don't reinvent the wheel.
the wheel.
It's one of the things that as most,
most engineers will at some point probably be told in their lives.
And if they haven't been, well, you heard it here. Don't reinvent the wheel.
It's kind of like the don't repeat yourself thing.
There's no reason to spend time on something that somebody else
has made a priority, right?
You as a company, if you're trying to be a game
or a DeFi app or a social something, right?
Like you're trying to build that
and you can convince yourself all you want
that you're good at multitasking or that you're,
you can juggle 10,000 things, but you can't.
It's just your end product won't be as good because that one thing that you thought was going to be really easy to implement that you self did now winds up becoming, you know, where you spend a majority of your time because maybe you're not a domain expert.
You don't have experience with it.
Right.
It has security holes, whatever it may be.
Right. it, right? It has security holes, whatever it may be, right? And so very similar, just like
philosophy, I think is use well audited public things that are good, right? And in blockchain,
that's, you know, using things like Open Zeppelin, right? Using things like, you know, Ethers, VM, you know, hard hat foundry, right?
Just use good tooling that does the trick.
And don't, you know, don't try to reinvent the wheel there.
And I mean, we see that a lot on the scale side.
I have a lot of people who come in and they're like,
oh, I want an NFT marketplace.
I'm going to build one.
And I'm like, don't do that.
Building NFT marketplace is really hard. People are like, And I'm like, don't do that. Building NFT marketplace is
really hard. People are like, no, no, no, it's easy. And I'm like, I promise you, it's not as
easy as you think. There's a lot of like intricate nuances and little things you have to worry about,
right? You're better off going with someone like a sequence who can create a white label marketplace
for you in a very short amount of time.
And I mean, same thing definitely with wallets, right? We see a lot of people that want invisible wallets.
Doing invisible wallets on scale is a little bit unique
because it is really easy to roll your own.
And it's something that we do often recommend to projects
depending on their use case
and their use of gasless transactions.
However, nine out of 10 times people want social recovery. They want login with Google,
stuff like that. And I mean, I would say most developers, just to give it context,
most developers don't know how to securely implement OAuth just for login.
So now you try to secure a wallet behind that and you just do all this extra stuff.
And again, it just becomes very, it's not slight in other developers, it's just the
stuff is very complicated.
And so, yeah, I would say it all comes back to the same thing, which is don't go out of
your way to implement things that somebody has made their livelihood.
They're probably doing it better in most cases.
And even if they're not, they can at least give you guidance on why you shouldn't do
maybe your own or something like that.
So that's kind of the approach that I take is let's just always guide people to using
the best.
Even if the best is a bit more expensive, time is valuable.
You learn that very quickly as well. So hopefully some good lessons in there for people.
As someone who launched an NFT marketplace in a prior lifetime,
don't try and launch an NFT marketplace.
I'll leave it at that.
Good insights, Sawyer.
James, thanks for taking the time on that question.
I kind of touched on this a little bit earlier
when I talked about how you guys have to be able to speak
to the different business units. In the work that each how you guys have to be able to speak to the different business units.
In the work that each of you guys do,
how often are you actually having to communicate
across different teams?
And how does that communication style change?
As, say, you're deep in the code with developers,
you're talking to maybe founders of projects if they're not developers, or you're talking to different people.
How are you having these conversations?
How are you explaining what Sequence can provide?
Or how are you diving into ensuring that everybody understands what you're trying to implement it, why you're trying to implement it?
And James, I'll start with you there.
Yeah, sure.
That's a great question.
Especially because in my experience, DevRel,
in crypto and Web3 in particular,
it really can like, your role is very like cross-functional.
So I frequently work with BD.
I work frequently with product and engineering,
everybody in between along with marketing.
And so I think that's one of the really fun things about working in DevRel
is you're not only, you know, heads down in the code the whole time,
because, you know, if you want that,
you can be an engineer, of course.
But I think it's really like you get to work with devs and you get to see how they integrate your solution
and also like help them resolve their problems
and troubles and all that good stuff.
So I personally find a lot of satisfaction from working in this like
cross-functional relationship.
And I would say, especially like on the dev rel side,
a few things is one is kind of like feedback from the market on what the
product should be and how that should translate technically into the product um i think
pretty commonly i guess crypto is pretty well known for building things that don't actually
really have product market fit or trying to find it after you spent years of work to actually build
something and i think devRel has a really strong connection
to builders of what people are asking for,
what problems they're facing,
and then probably most importantly,
a lot of cases, what they're willing to pay for
and pain points they want to solve.
So that's something that I really value of like,
how do you funnel kind of the market
and developer feedback to product and engineering
to help iterate on that, you know, life cycle
and, you know, make it better ultimately.
So that's one big one.
And then of course, another is centered around
like the marketing side and, you know,
how do you translate translate complicated technical topics?
You touched on this earlier actually,
it was like, even if you built the greatest technical
implementation possible, it's super scalable,
it's ZK proof and all this good stuff,
is how do you actually translate this into value
and do something that the market will understand?
That is, I think something where DevRel can really shine
in a cross-functional capacity of condensing this information,
even to technical audiences,
because frequently if people are even coming
from web two to web three,
they don't understand all the technical nuances
that look like the chain level that you have to communicate.
So I think kind of this translation is super important
to get people excited about what you're building
and what the impact is ultimately to them as a developer
them as a developer or to them as a builder?
or to them as a builder.
Yeah, I, you know, I think, you know, Sawyer mentioned Falcor is in the audience here,
and this is probably going to rub him a little bit the wrong way, but DevRel is, I think,
one of the most integral parts of any successful, you know, blockchain company. And that's just for that reason,
of being able to break down complex technical topics
into everyday to understand terms,
as well as be able to actually go in and do it.
It's not just being able to talk the talk,
but being able to, I guess, walk the walk.
Sawyer, I'm gonna ask you the same question.
Probably similar answer to what James had, but just curious as to what your thoughts are there, too.
Yeah, I think DevRel, in our case, our team is called developer success.
that I think early on, the leaders at PL Labs
recognized that this team wears many hats, right?
It was previously a solutions engineering team,
then it transitioned into developer success
as we kind of got more hands-on with customers
and did different things and did more marketing,
stuff like that.
So I definitely agree that there is a,
the DevRel unit is very critical
to a lot of cross-functional pieces.
If your DevRel team can't work,
if your DevRel team can't do sales,
if your DevRel team can't learn and execute on,
you know, marketing tasks that the marketing team needs you to do, if you can't talk, if you can't learn and execute on, you know, marketing tasks that the marketing team needs
you to do.
If you can't talk, if you can't explain to people how the product works, you don't know
how the product works, you know, never as good as the engineers, but trying to be as
good as the engineers.
And ultimately, if you don't love to help people, you're probably just not going to
be very successful at it. And I would
say that last one is really important. I see it in James and it's something that it took me a long
time to realize in myself was I really enjoy helping people. There's never something that I
really thought that I would want to do was help people learn to implement and learn to build. But
I really enjoy teaching people, you know,
about topics I'm interested in
and how to do different things within those.
And so I think that's a huge part of what we do, right?
Is we're helping people learn and understand
whether it's just information, whether it's code,
whether it's, you know, the amount of times, right?
That we've spent, you know, hours and days and days
trying to solve a bug and, you know, someone forgot a semicolon somewhere deep in the stack.
That's part of what makes a developer relations team so effective.
And so, yeah, I mean, when it comes to us specifically, I definitely see a lot of that.
We're kind of all over the place.
We do a lot of different things.
But it also allows us to help our projects right those
building in the scale community find the most success because we're not giving them suggestions
just based on a technical background we're giving them suggestions based on you know best practices
that you know ben and felcor and you know different members of the scale team are are recommending
you know different things that you that are business development team members
who have more experience with how token economics
and how different projects have failed or succeeded
and done different things.
It just gives us the flexibility to either provide guidance
or find someone who can.
And I think that's a really big, important piece here.
Um, when it comes to just like how we operate, but yeah, the TLDR there is.
Does many things.
And I think it's part of the fun is you're never just doing one thing.
You get to try a lot of different things.
Yeah, doing everything from, you know, marketing to development to communications to, you know of the business units and, as I said before,
Yeah.
be able to break things down in a very simple or maybe not so simple or easy to understand way,
but it comes across that way. So, Jane, both you and Sawyer do a great job with that.
And now here I have a question that is, you know, when you're thinking about
Now here, I have a question that is, you know, when you're thinking about who your ideal implementation partner is and what it is that they're looking for out of, you know, whether that's a blockchain partner or out of, you know, a tooling partner like Sequence.
You know, I guess, what are the things that you look for out of a partner? And Sawyer,
I think I've had James go first the last couple times. So I'm going to give him a few moments
to think about this. And I'm going to toss you that question first. Yeah, I think it's going to
also just very dependent on the situation. But I think the things that i'm always looking for are
um one you know having the right product and having a you know having a stable and strong
product is critical right and that's everything from you know if it is a product company right
if it's someone like sequence right you want the product to be good you want the documentation to
be good you also want the support system to be good. You want the documentation to be good.
You also want the support system to be good.
And ultimately, you also need them to be flexible within things like pricing.
So that way it's an option for as many of your customers as possible.
And ultimately, the biggest thing I think that I've started to look for is I want mutual win-wins.
I don't just want someone to
come in and try to sell every one of my customers. I want them to come in and say, here's how we're
going to help you succeed, right? And here's how we're going to help your customers succeed. And
they're getting more in the weeds. They're, you know, working to do different initiatives and
find opportunity where it is a mutual win-win. They're not just trying to get every project as
quick as they can and sell them a package that, you know, they don win-win. They're not just trying to get every project as quick as they can and sell them a package
that they don't necessarily need.
They're actually trying to help them find success
because at the end of the day, that's what we do, right?
If someone doesn't need something
or they wanna try something new,
we're here to help people succeed, help projects succeed.
We're not here to just sell, sell, sell.
And so that's a big part of what I look for
is how do we create these
mutually win-win partnerships? And how can we offer something they need? How can they offer
something our projects need? And then it just kind of grows out from there. But yeah, at the end of
the day, the biggest part, the most important thing is after we get through those initial pieces, the biggest part that I look for is that the customers are happy.
Right. So the last monarchy is the, you know, the data 2073s of the world.
Right. Like these amazing projects building on scale that have chosen sequence.
The biggest thing that I look for at the end of the day,
out of all that, is that they come back and say,
hey, we loved working with sequence.
They're solving our problems.
They're giving us what we need.
And that is a good sign that I should continue to push people in their direction.
And obviously, you know, we're continuing to do so.
So that should tell you a lot about how our relationship together is going.
So your turn, James.
So I just love your Sherlock sequence,
so it's just music to me.
So I, yeah, this is a really interesting question.
For me, I actually don't think I look for anything specific
in terms of like what the project is or what stage that they are.
I actually like working with, you know,
everything from an MVP to a founder led startup to a hackathon project all the
way up to like enterprise. Of course,
like how you interact with those different projects is usually
quite different um so depending on the maturity of like the specific company or like the project
but i think that's what's really fun about crypto is like you you also never know who will become
big in the future um and i think it's fun helping people along the way through that entire journey,
because we've seen many, many times across a variety of like verticals is, you know,
someone creates a new primitive, someone creates a new way to incentivize users to
use an application, or like there's a new meta that comes out. And then all of a sudden,
use an application or like there's a new meta that comes out and then all of a sudden a few apps just
Explode and they take over the market
and so I think that's really exciting about crypto in particular is
There's a lot of this innovation and a lot of the innovation is happening at the early stage
so I do like working with early stage projects and then of course like
When you're working with like larger
companies or just larger projects in general um i think the solutions can be a little more
interesting or there's more like feedback and ongoing kind of like work directly with the team
um so i think that's what's really neat is like the early stage projects can innovate more.
And then on the later stage projects, you can kind of focus on how do you make something more scalable?
How do you have something that like responds to millions of users interacting with this specific application?
So it's like a different scale that you're looking at.
So to answer your question, I don't think that I
vet a project at an early stage
but I
do love working across
the entire gauntlet and then augmenting
what we're doing of how we can help
them best depending on the stage that they're at
so I think that's really important
especially like in
a developer success role or
dev rel you
know as we said like the role takes on many different forms is how can you help someone
now at the stage that they're currently in um and as long as they're basically receptive to this
then those are the projects that i love working with the most
yeah i mean i think the buy-in is huge, right?
Like, the more a project is putting into everything,
the more, you know, you also feel like you're putting into everything.
Like, right?
It's a lot easier to work collaboratively together
than it is to feel like you're having to pull people
in one direction or another direction.
And I think part of the beauty about
the sequence and scale relationship is that if done correctly, the end users aren't feeling
the effects of either one, right? And so it's like you're obfuscating in a sense away the feeling that anybody is actually working with sequence
or scale. And so a job well done means that nobody knows that you even, I guess, in a sense, exist.
I know Data 2073 was just mentioned. And they're actually a project that is officially going live,
a project that is officially going live, being announced later today on Scale and a partner of both Scale and Sequence.
Sawyer, maybe just like very quickly, if you want to run through kind of like how Data 2073 has worked,
what they've worked to implement on Scale, and then James, you can tie in what they've been doing with Sequence.
implement on scale. And then James, you know, you can tie in what they've been doing with
sequence. But just, you know, for the audience to kind of get an understanding about this
project about this game that's, you know, now a part, I guess, of both ecosystems.
For sure, for sure. Yeah, the data 2073 game is really interesting. I'm pretty excited to see them go live.
So what they've done, at least from our side, right,
is they've integrated scale for essentially their auto-battling functionality. And so what that allows people to do is essentially have these games that are running and utilizing NFTs in their data token, which the NFTs and the tokens, last I checked, were powered by Sequence.
And then I know they're interested in expanding and putting even more on chain
um but a lot of their game is focused around a like call it like a progression system I guess
is the right is the way that I would think about it um so right as you continue to to play and and
earn these assets you you have more opportunity to grow, trade those NFTs to other
people and stuff like that.
So yeah, they're also using the Sequence wallets, if I'm not mistaken, but very excited to see
them continue to grow out.
I know they have more they want to build,
but I think they're off to a great start.
And I've had a number of the people that test games on our side have already given really incredible feedback about the game itself.
So, yeah, I'll stop there.
Beautiful.
Yeah, I think, I mean, sorry, you you hit the nail on the head so from our side we've been
we've been working with the team for quite a while now actually on a number of different like uh
verticals so like i'm really excited to see them actually going live so this is me also learning
that they're going live today so that's super exciting. I think something that we really like tying back
to what you asked previously is,
how do you work with partners
and how do you prefer to work with partners?
And how does this all tie together?
Is like, they've been super helpful on giving us feedback,
especially on the product side and how we can improve
our solutions.
So like as a tangible example, you know,
we're they're using our marketplace,
they're using our shop feature.
So we basically worked with them in an early access phase,
gave them, you know,
exclusive access to this feature early on
and kind of the development life cycle.
And so we've actually worked more or less hand in hand with them as they've kind of like raised
things, maybe things that were confusing or ways you can improve basically the user flow
and the developer experience. We've just taken that feedback and integrated it right into the
product. So I think this is really important. And this is, I know every product person and engineer just loves hearing this feedback because it makes it much easier
when you're hearing direct feedback from your users of really what to build and what will
improve their experience. So they've been super helpful during this entire process. And as you
mentioned, Sawyer, they're using our wall wallets they're using our marketplace and shop so really excited to see kind of like how the game progresses from there and how like you know
all the um basically distribution of their assets goes yeah it's a game that we're excited about um
we're hosting a game night tomorrow in the scale discord with the project as well so
game night tomorrow in the scale discord with the project as well so um if anybody wants to
you know take a spin and play data 2073 hop over to the scale discord um and check it out tomorrow
um we are 10 minutes out uh from wrapping this up so you know james i'll start with you here
just as i know sequence is always innovating,
I know you guys have new things always on the rise.
You have ever innovating, ever pushing the needle forward.
What's coming next?
What are you guys excited about over at Sequence?
What do you have coming?
What are some of the projects you're excited about?
Just take a few minutes
here and show what you guys have going on. Oh, okay. We got some, we got some cool stuff cooking.
So yeah, I'm, I'm really excited about kind of the, the next phase like of our product suite.
So a couple of things I know you've seen a little bit about it, but we're also going to be debuting basically
our ecosystem wallets very shortly.
This is really exciting.
So it allows you as an ecosystem,
whether you're like a game or a chain,
and you want to have multiple developers kind of building
on your platform,
it enables you to do this in a secure way.
And kind of the core innovation of this
is something that we call smart sessions.
So if you've ever used something like Privy
for an embedded wallet,
you know you basically log into one specific application.
And then in order to kind of share those credentials between different applications,
you need to like kind of authorize this wallet.
And there's some drawbacks there.
And this means that like you can potentially be exposed by like a rogue application
that integrates the specific wallet. So what's really cool about Smart Sessions
is the ecosystem can define how much value
any given application that integrates
that wallet can transfer.
So for example, I can say as James Lawton's ecosystem,
So for example, I can say as James Lawton's ecosystem
that application ABC can only use up to 100 USDC
from my user's wallet.
And this is really powerful because then all of a sudden
you can integrate it between different marketplaces,
between different applications and actually create and forge different partnerships
between numerous verticals.
So this is something that we're really excited about.
We have a lot of like partners in the works
and a lot of people integrating it right now.
So it's really cool.
And we especially love like how we built it to be
the number one, like most secure ecosystem wallet because of these smart
sessions. And so this provides a lot of protection for the user
and makes like integration, like from the app perspective,
like very simple. So that's one thing I can show.
And without getting too much into detail, the next exciting thing that we'll be
like pushing forward is also like a cross chain payment solution to like, you know, more easily
integrate and transfer value between different chains to make payments, to make swaps, all that
good stuff. So that'll be coming shortly. We'll reveal it as more like kind of comes out,
but that's some additional output for now. Just the littlest tease there. I love it.
And that ecosystem, while it sounds amazing, Sawyer, I'm assuming that that's something that
we'll be working with to get set up on the scale side. I hope at least, you know, that better be happening.
Anyways, I will now tee it up to Sawyer.
Put your marketing hat on for a moment.
I know you see the scale logo that I'm speaking from right now,
but we also have another logo on stage, Fair.
Maybe you can talk to us a little bit about what that one is,
what that brand is, and what's coming there.
For sure.
For sure.
Before I do that, though, I do have to call out that James just hit on something so near and dear to my heart, which is wallet-like configurability.
For those who don't know, I spent many years of my life building this type of technology.
It was way before its time, and no one cared.
And people do now care.
And so I'm so glad someone's finally doing stuff like that.
So thank you to Seekin's theme for actually building a wall that is designed for real
human beings.
That being said, let's talk about FAIR and what's coming for scale.
So for those of you that have been living under a rock of some shape and size,
you've not heard about FAIR. For everybody else, you definitely have. What is it? It is going to be
the only MEV-free layer one blockchain in the world. And the most important thing to note when
it comes to FAIR is that it will be the first blockchain that enables proof of encryption by default.
Okay.
What is proof of encryption?
Proof of encryption is the ability to have fully encrypted transactions at the consensus
level.
And so what this means is when you're sending transactions, you're doing swaps, trades,
limit orders, dollar cost averaging, you're playing PVP games on chain, you're
buying NFTs, you're launching tokens on a launchpad.
Everything you do is currently being MEV attacked, right?
You're being extracted from by validators and searchers and different people that run
parts of the actual blockchain.
And that is no more with there.
This proof of encryption enables all of those transactions
that have been fully protected,
and so you no longer have to worry about bleeding money
and value to parties who are, well, taking it from you.
Now, what's really, I think, amazing about FAIR
is there's proof points already that show
there's been billions of dollars lost to MEV over the last,
I think the statistic was like 2 billion or something since 2022 or something like that.
Someone correct me if I'm wrong.
But a lot of money, right?
Like I can't even comprehend how many dollar bills a billion dollars is, right?
It would like fill 10 of my apartments probably and then like 10 more then 10 more, and then 10 more, right? So it's
a lot of money. But what's so amazing about FAIR is not just that it's going to save individuals
and entities and people money that are doing these on-chain actions, it's that it's going to enable
potentially trillions of dollars in economic value to come on chain.
These are things like MEV free limit orders, doing fully automated indexes, dynamic vaults that are protected,
the ability to do agentic trading that is just automatically running to make you money, right? These are things that,
sure, you could attempt to do on other chains right now. We're seeing it happen.
But the problem is, is if you do it on an Ethereum, you do it on a Solana,
you're losing money to MEV. MEV stands for maximal extractable value. And it is essentially the act
of somebody who is building
the blockchain, reinserting or reordering transactions to make money from you. All of
those MEV blockers and RPCs that Ethereum claims is working, guess what? They're still back running
you. With there, that no longer happens. It's going to enable and bring about a new era of not just user excitement within DeFi
and the ability to use it.
It's going to bring the ability for developers and institutions and companies to build functionally
the new financial system on chain, right?
That's what everyone's been claiming they're trying to build for the last 10 years on Ethereum.
But well, we're mostly still in the same spot. We just have a few AMMs that are really good and
one really good lending borrowing platform. But the rest of it is pretty much just a fork of
somebody else. So TLDR, FAIR unlocks innovation. It's going to utilize this proof of encryption to make DeFi and agentic DeFi fair for everybody,
developers, users, builders, you name it.
And we're very excited for what it's going to unlock
on that front.
And then just because I don't want to continue rambling,
there's also a variety of benefits that it brings to scale.
Check out the fairchain.ai website for more
information on how it's going to benefit scale through a combination of the airdrop, the fair
SDK upgrade, and the movement of scale manager and the enhancement of operational efficiency
long-term. So lots of good stuff coming there.
A lot of information there, Sawyer, about FAIR. James, thank you for the TLDR
about what is coming on Sequence.
Everybody here, please make sure to follow
not only the Sequence and FAIR accounts,
but also Sawyer and James for insights
into the world of DevRel,
developer success, and just overall blockchain knowledge that is just oozing from both of these
PFPs right now. This wraps up the Tools Day campaign that has taken place across the month
of July. It has been hot and heavy over the summer months here
between sequence and scale.
Thank you all for joining today
and pay attention to what we have coming next.
Thanks so much.
Thanks, everyone.
Awesome. Thanks, everyone. Thank you.
