why don't you have audio andres no no no no
this is experiencing technical difficulties and just go in there on
your personal account and port it over with your personal account. What is your personal account Anders?
Now I got it. We can hear you from the twitter space.
Hello everybody. We are experiencing technical difficulties of various different kinds. Please
hold tight and we will solve these technical difficulties directly and be able to get you guys
up and running and learn more about covalent and data layers in the blockchain space momentarily.
All right everybody. I think we might have this thing solved now.
I'm going to need some sort of indication if you guys are getting this information across
on twitter as well as on youtube. Once we have that confirmation then we can
do this introduction one more time and get the ball rolling.
As you can tell this is a crack team of very very technically savvy individuals that are coming
together to help enlighten you guys on the finer points of how to execute and deploy
technical solutions in the space.
All right. Let's see what we got here.
Okay. Are we ready to go? Good. We're ready to go. Fine. Super everybody. So I would like to
reintroduce everybody to the two guests that we're having here today. We're having a
in-depth look at the data layer on blockchains in particular on the mail blockchain. We're going
to be working closely with Covellent. They're one of the leading data layers in the blockchain
space. We've been working with them for a while. We have here Harish who is head of business
development at Covellent and we have Yousuf who all of you guys already know. He's head of
special projects at Meld and we're going to take it from the top down like we did the last spaces
where we're going to try to walk through the basic overview of what the data layer is in the
blockchain space, how Covellent works, what they're actually building, why it matters and why it's
relevant. Talk a little bit about what's happening on the backend and then I'm going to hand off to
Yousuf who will then take away and we'll be able to look at more technical in-depth discussion,
more sort of developer-related type stuff and then take some questions towards the end.
So again, I apologize for all of the technical hiccups that we've had so far but it looks like
we're more or less working as we're supposed to. Harish, thanks for joining.
Okay, so I would like to start out on sort of a high level and talk a little bit about
not particularly Covellent but more kind of what the vertical you guys are working in
in the crypto space and so to sort of set the stage,
blockchains are technically databases but they're really crappy databases.
So with that it means that you have to take and build an entire database and data infrastructure
on top of it in order to make blockchains valuable or usable. So this kind of sets the
stage for how critical the type of work that Covellent is doing and in particular Covellent
in collaboration with Meld. So they're effectively taking that core value proposition of a blockchain
and making it valuable and usable. So if you can kind of take that as a starting point and give
us a kind of an overview of Covellent and the basic service offering. Yeah, you bet and thank
you so much Ken and team for having me. We always enjoy the conversations we have with the Meld team
and sort of love the product itself. So let me just give you a little bit of context around where
we sort of fit in the data space because as you pointed out Ken, I mean there's definitely a lot
of different facets, a lot of very interesting facets to the data layer and Covellent essentially
started at an hackathon back in 2017 with essentially a very simple approach. We took
and scraped on chain data, put that into a Postgres database and then you could write SQL queries
to access that data. And so the idea was well can you take what looks like
you know basically raw spaghetti if you look at the underlying you know transaction records that
live on on blockchains and then start to make a little bit more meaning from it. I think anyone
who's maybe attempted to you know index any data or even you know make RPC queries to pull nodes
and directly fetch on chain data can probably appreciate the challenges and the nuances
with trying to do this you know effectively and at scale. And so that's the the core challenge
that we immediately saw was that you know being able to pull data and you know when you look at
the ecosystem not just from one chain but across many chains who all may have you know slightly
different standards you know nomenclature different different ways of handling data
and be able to create some sort of sort of normalized way so that developers who don't
really care about the underlying details they just want access to data to be able to incorporate
that into their their applications. Is there a way for us to do that effectively and at scale
and that was sort of the the key problem that Covalent set out to to try to solve.
And so you know there's a lot of I mentioned there's a lot of interesting facets to the problem
there is how do you actually you know access the data how do you actually store it in a way that
could be optimized and indexed in a way that's that's quite you know performant and then what
are all the different interfaces to be able to access that data. Is it just SQL and you're
targeting that particular developer set is it you know through a REST API is it through writing
GraphQL. So there's all these very interesting different interfaces that you could be building
on top of this sort of data data database essentially and so those are also other
interesting challenges that we've been we've been tackling to figure out what are some of the ways
that developers want to access this data and how do we optimize for that. So to set the stage here
for for a lot of people that don't work in the weeds when it comes to dApps and and blockchain.
If you're looking at just a simple tool like a wallet the information you're getting off chain
is negligible you're not getting any price information you're not getting any historic
information you can't show a graph of how much your asset has gone up or down you can show some
not even all of the transactions that your wallet is doing. So in order to do the basic
things that you would expect that your wallet should be able to do things like all the transactions
that have come in all the transactions that have gone out what type of transactions they are the
price of my asset how much that asset has changed over time a graph on the asset for how whether
for how long you've had it or for how long that the asset has been on the blockchain.
These are really basic things that we take for granted as a user on the blockchain but the
reality of it is that this stuff is just not available and so you have to use a data layer
like covalent in order to do that and it's not just as simple as being able to query that
information it's how that covalent structures that data and makes it accessible via an API
that determines a lot of what you can do and how sophisticated information you can actually
provide in inside of your DAP or connected to other types other parts of technology in your
blockchain ecosystem. So really when it comes down to it like we talked about on the last spaces
around oracles this is a primitive in the development of blockchain applications and
blockchain tools and ecosystem so you have to have this asset in order to have anything that
is vaguely related to user-friendly. So you've you've kind of outlined okay covalent started in
2017 you started indexing ethereum though when did you guys move out past ethereum and start
looking at the sort of ecosystem in a more wide in a broader context?
Yeah so that would have been pretty pretty early in 2020 as we start to see you know DeFi summer
start to see you know pickup of some of these alternate you know ethereum scalable solutions
like polygon like avalanche and so when we started to see you know the ecosystem expand beyond
ethereum it became quite clear especially looking at things like gas fees on on ethereum
that you know some of these other you know scaling solutions would be gaining
traction and so we firmly believe in this in this multi-chain future and so once we started to see
that it made sense you know you're going to get you know developers trying to pick out the best
features of various ecosystems as they they build their application and so having the ability to
fetch data across chains I think became quite apparent to us and so to do that effectively
also meant having something like a standardized or a normalized schema so that doesn't matter how
you sort of qualify things on these in these various ecosystems the way developers fetch it
should be very consistent you can think of this as having sort of common columns in like a
spreadsheet for example as opposed to each ecosystem having a different convention for
you know all sorts of features that they offer in their ecosystem right and so what we've largely
talked about right now is data connected to tokens and to transactions related to tokens and
to coins but you guys also have a specialized set of products for nfts and being able to
capture and track the metadata and data around nfts yeah so i mean when we started it was as
you pointed out it was pretty simple you had these native token transfers the transaction sort of
receipt was actually very simple to to read and understand and now as i'm sure you know
the folks at milk can attest when you look at some of the transactions through their their
application when you look at it on a on a block explorer it becomes almost really difficult to
decipher what actually happened and so you know in addition to just more complex applications
you get applications like you know the nft ecosystem where a lot of the data that's
sort of meaningful and valuable like the image asset or the the media asset and the metadata
doesn't actually live on chain it might live in aws it might live in ipfs it could it could live
anywhere and so being able to to pull that data as well and then stitch it together with the on-chain
stuff you know is another sort of challenge and and something that we've attempted to address with
our nft suite of apis super so we've set the stage for why this data layer is critical um and
the sort of basic elements connected to it the transactions the the different sort of ways that
the transactions interact tokens interact the different types of assets like nfts so um that's
kind of where most of my knowledge ends so now i'm going to hand off to uh usuf um he's not only
head of special projects and has worked in most of the sort of moving parts of meld he also works
very very closely and in depth in our technology department so he's going to sort of talk to you
more on the kind of developer focused side of things yeah absolutely and i'd kind of like to
start off with a little story because as you as you were talking i was remembering when we were
developing staking um during the initial testing phase we had like a moment in time where the
initially we didn't have the back end data ready so we were going to try to get all of the data
points just so that it would appear correctly in the ui so we could assess if we're showing all
the data points correctly we had that using specific we're using actual rpc calls to the
blockchain so we were directly interacting with uh with the blockchain and saying hey
giving the data for x y and z thing and you can imagine that you know initially in the dev
environment it was perhaps you know a couple positions a couple staking pools but once you
scale it up we were already making a couple hundred rpc calls you just get the data for one
specific uh for a few specific assets and then as you bring more and more pools more and more
transactions more and more um just in general staking activities happening then it would be
entirely unscalable to try to attempt to get all the data using rpc calls and and so that's why we
indexing is so important and i also see it in in my personal projects as well where i initially i
think i don't come from a web2 background i kind of am native to web3 and i've never had to kind
of worry about databases a lot because for example for some products you can actually build out a
whole dapp without a backend you can just use indexing products like covalent and and different
hooks and that people provide that are already doing that work for you and essentially you can
launch a dapp with only a frontend that's that's speaking to covalent that's getting all of the
nft transactions that's getting all of the token transactions and all that pricing that data so it
makes it actually really easy to uh to to launch and build a dapp uh a dapp so i i kind of empathize
a lot with the with what you guys are building because it makes it makes developers life so much
easier um so yeah but i have a few questions i'm really curious as as someone who's using your
products every day i wonder how you guys are kind of able to ensure essentially the the scalability
and efficiency of your of your of your systems as kind of more stuff happens in every chain
and you support more blockchains how do you guys are how are you guys able to do that in a way that's
able to provide kind of the data to for any moment in time the history the entire history i'm sure
there's a lot of like engineering efforts like involved in that so how you guys were able to
achieve that yeah the short answer is very carefully because there's so many things that
that could go wrong so i think just to give you a feel of the different like layers that we have
to deal with so we're kind of a you know full stack data middleware solution for our first
structured on-chain data so if you think through the layers first we have to to scrape uh the data
so um you know we started by just using um you know external or third-party provided notes
and realized very quickly that when you look at uh you know the volume on ethereum or polygon or
arbitrum or some of these roll-up solutions optimism like just the amount of data explodes
very quickly and so it became quite apparent that for us to scale uh we would for those ecosystems
we would have to look at you know basically running bare metal run our own notes uh be able
to to handle that traffic with sort of our level of optimization that our engineers apply uh to
those those chains we still use you know third parties we we support over 200 networks so
to run nodes for every single one of them um sort of a dedicated manner would be would be quite
cost prohibitive so that's sort of the first stage is just you know looking at um you know where a
large part of the volume is how to optimize that and we we sort of came to a middle ground where
you know we we run our own nodes then you've got the indexing level um so having sort of uh
the the database index having a normalized schema to organize and structure data and so the way we
kind of looked at this was uh you know what are developers asking for okay so they're asking for
transactions you know we can we can pull that up but we know uh that just transactions uh the
receipt in in a vacuum isn't very meaningful you need to apply some pricing data to that so we
stitch you know pricing feeds so that you get the fiat value associated with that transaction
and then there's all sorts of interesting log events that kind of tell you the story
of what happened in that transaction and so we're like okay let's pull the log events and attach
that to the transaction and that's what we can serve but the the log events themselves are you
know just look like gobbledygook you know it's just alphanumeric hex uh hexadecimal value so
we then sort of ran this decoding uh process where we would decode those log events apply to
the transactions and serve that up through an api so when you think of all those different
nuance steps it's really designed to make it as simple as possible for developers to consume
on-chain data with the context of um you know the enrichment that makes it useful for them
they don't need to go to another provider and get the price fee they don't need to go and run their
own decoder and and have to to decode those log events we kind of structure it uh for them to
make it make it even easier and then the third layer as a data provider is well how do i actually
access this data um you know there's apis some developers like to have uh framework specific
sdks and um you know recently what you and i have talked about is you know just some front-end
components that are powered uh by by on-chain data so we're constantly looking for different
ways to provide you know this enriched data to developers um in the context of what they're
trying to accomplish for their customers yeah that makes absolute sense but i'm i'm assuming
you must come with so much responsibility because you can imagine that you guys are powering so many
dapps if for whatever reason your one of your nodes goes down or something along those lines
happen then essentially it's kind of like a um almost like a centralized point of failure because
then it's all of the dapps suddenly stop working you go on them and none of the data is showing
properly how do you guys do you guys have any ways to kind of like have fallback mechanisms
of some sort to make sure that maybe you know if something fails we have this to protect uh
kind of all for ourselves and also all the other dapp developers who are using your products
yeah for sure uh just like any other you know uh key service provider uh having redundancies
in place is absolutely critical so that applies to the you know the nodes themselves where we're
pulling this data for that ingest process and having sort of a router mechanism where if any
one particular node uh fails we can go to the uh the alternative and we can continue the ingest
process uh to just how we you know serve up data uh through again a network of various nodes this
is actually one area that we're doubling down with our decentralized network and i think as you
pointed out that's going to be key to ensure that you get you know reliable data um from
you know a various mechanism of trying to get the most efficient route um to get that data
and then also you know with the decentralized approach you don't have a single point of failure
so that's actually what we're building out right now there's a few different stages for that the
first is just the ingest process which we've uh we've decentralized so there's actually a network
of validators that will pull on-chain data review it process it and then put it uh put it
into the destructor database and then you know we've got the storage and the query layers that
we're going to be focused on next but um all part of the the process to exactly your point you see
if you want to ensure that um you know it's a reliable data source um and and there's definitely
multiple points uh of redundancies involved that's super cool yeah i'm looking forward to kind of
seeing how you guys achieve that um and and how you guys and you're essentially going to be
building a a blockchain on top of all the indexing that you do so that you can or at least some sort
of decentralized solutions that you guys can provide that data in a way that's that's that's like
avoids uh any issues like that happening um very cool i want to ask you guys obviously you've seen
a lot of developers use the covalence products and you've seen them um build various various
kind of dApps i'm curious do you have you seen kind of like a unique combination of the different
api or like endpoints that you guys provide to build something that kind of is very unique and
you didn't expect maybe that the api would be used in that way maybe a combination of token
balances with pricing with x and y and z i'm not sure if you've seen this before or whatever but
obviously the typical things are kind of showing wallet showing balances but have you seen any
combination of the endpoints in a way that surprised you yeah we're always surprised by
the creativity of developers i think that's what's exciting about this space is uh there's always
really cool uh creative elements uh displayed so i mean we were we were quite big on um and still
are quite big on uh you know promoting you know hackathons and and ecosystems with grants uh and
the reason for that is you know trying to see you know what sort of interesting innovation
innovation comes out i think of of late you know there's definitely been a big push towards
ai um so you know just to highlight some of the examples there where you know it's predominantly
prompt base at this point but being able to you know ask questions around you know give me some
understanding of a wallet or a contract uh and then you know leveraging our api to sort of stitch
together that narrative of what's actually happening you know give me a sense of you know
if there's any you know suspicious activity happening with these sets of wallets and then
you know leveraging our historical data to look at maybe trends or uh you know anything that
might be flagged as a as a concern during the the empty craze we saw some really cool stuff so
tying in sort of the uh you know the various 3d libraries that exist out there and engines like
like unity to be able to you know build out walkthroughs of your your nft gallery so i remember
one i believe this was a hackathon submission where it would basically pull your wallet take
all the nfts and then put them on this like basically this digital museum that you could
walk through with all the nfts hanging off the the wall and it was just an incredible experience
just another way to be able to you know navigate through your your digital asset the your portfolio
just a very cool visual and then of course all the you know the various d5 projects that were
that we're seeing um you know everything from being able to understand and contextualize
you know the rewards the the liquid staking positions that you might have
and be able to you know pull all of that across chain through through one interface
we've been seeing you know all sorts of dashboards and reports and analytic pages being built
using our api for for that purpose so yeah a lot a lot of very cool interesting projects
and that's just you know some of the more creative ones of course for like wallets and
you know taxation accounting tools um you know doubt tooling those are sort of the the standard
use cases yeah i can imagine sorry i don't mean to inject um i just wanted to let the audience
know that if you guys have any questions we'll we'll open up for questions in a few minutes
but you're also able to ask questions either on twitter or on youtube and we'll do our best to
try and field those questions on this uh on this basis very cool yeah i was just going to end up
i end up saying that uh i can imagine how you kind of incorporate these api endpoints with
some sort of prompting tool because you could just say something like oh um what are the most
recent transactions that happened in my wallet and then it would go and use the right endpoint
or use the right covariance endpoint to get that data and then display to the user so
it's actually something that's yeah super that's super sleek and maybe maybe maybe something for
the meld up who knows but um very cool i wanted to ask also regarding um we barely we kind of
briefly touched on it but the uh gold rush page so i know that um maybe not a lot of people or
it's it's a fairly new feature that you guys are dishing out and essentially if i can kind of
summarize it it it takes these api endpoints that you guys have already kind of battle tested
and and and and made sure that you know everything works properly and now it's given it a visual
component so instead of having to go and essentially get the data from the apn which is great it kind
of makes everything super super easy but then you still have to go and create like a box that's
going to show the wall the wallet the symbol the amount the fiat amount etc etc you've kind of
said okay well you know what let's actually make the developer's life even more easier
and let's give them out of the box kind of components for specific uh or like common types
of of of pages of features and let's get let's directly integrate the covariance api and make
it super simple for them to see it so i personally use for example your wallet or token balances
overview kit which essentially show into all of your all of your all of your assets all of your
balances all of the um the dollar amounts per balance of per token and that's essentially
instead of me spending an hour trying to figure out how i want to design it and all that stuff
like that i can just plug and play essentially and have a whole page that's supposed to take me
maybe a couple hours to design and now it's done in a few seconds so if you can elaborate on that
that would be great yeah thanks i think you did a pretty good job of giving a good context so yeah
if you go to go to our website for villainhq.com you'll get the link to the open source gold rush
kit repo and so the whole idea behind this as you kind of articulated there you sif is you know we
want to make developer lives as easy as possible and but but we also want to take you know some
of the most common elements of a web 3 ecosystem so things like block explorers wallets and a few
galleries and have these ready to go components that can be customized and stylized to reflect an
extension of your brand i think part of the challenge with some of the maybe some of the
existing uh tooling that's out there is it's quite rigid in terms of what you can do it may have some
of the core feature sets but in order for it to look and feel like your brand it kind of comes
across as a completely standalone product and so that was really the the key motivation for us is
like can we build things that are completely configurable so that if you are embedding a wallet
or your own custom block explorer or your own custom transaction receipt uh can it look and feel
like your product as opposed to just a standalone lot and so that's really the uh the motivation
there you can think of gold rush is like this next sort of interface where you know we first started
with the rest api um you know and that's applicable for a very broad set of developers and you can
kind of use it in any existing framework but it's headless like you can actually see
you know anything visual with that it's just um you know a json response and then you had you
know this uh you know these sdks that we built so now i don't need to actually leave you know the
javascript environment i can just do npm install and i've got my um typescript SDK that i can use
with all the the methods um built into the um into the the module so it's super easy to integrate
um the third level of sort of abstraction here is this ui component so now i have these data powered
um you know components that i can effectively drop into my application and as you said it's
all visual so if i want a list of all the tokens of all it has across chains i have a nicely
formatted table that i can just stylize and make it look and feel like my you know my product
if i want a list of transactions if i want a transaction receipt if i want an nft detail page
if i want um you know for the uh dexes if i want an analytics page all of this is kind of like built
as ready to use templates and then really your effort is to stylize this and incorporate that
into your your application not you know wrangle with the underlying data and try to like make it
fit with all the things that you want like pricey pricing or um you know just some decoding that
you might want so that's really the essence of what gold rush kit is and again we've we've
open sourced it anyone can can uh can use it fork it and then um be able to build uh build on top of
it that's very cool yeah i mean i can i can only imagine how much time it's going to save developers
and it's already saved a lot of time for myself when i'm when i'm doing various products so
very cool stuff i wonder i mean you mentioned you know the json response now the ui component
what is what is the stage three on top of that for general question about you know what are the
what's the future for for for covalent and for indexing and and and we it's all about ai it's
everything is ai just replace all of us i wanted to hear it from him i i hear from yeah i mean uh
i think ken kind of summed it up in those three words but uh i think so there's definitely some
cool stuff i'll give you i'll give you um you know some some context and we've actually i think
just released a few of these neat features so i definitely encourage you to check it out so the
the first one um is just around uh you know where we see this gold rush uh you know kit so obviously
adding some more components will be actually i think we just launched it and if we haven't
just launched it it will be coming out i think like literally today um is this idea of a custom
decoder and so if you want to basically create any customized transaction view you can basically
write this decoder script uh and we've got templates for for doing this so that you can get your
transaction view to look and feel exactly as you want it so what do i mean by that let's say there
are some nuances for how a mail transaction um looks and feels if i go to uh you know block
explorer um you know i'll see like some you know fairly typical stuff i can see a token flow you
know all text space but i can sort of see okay this wallet address you know received this token
this wallet address sent this token but imagine if you can basically have the underlying data to
create this beautiful flow of seeing you know from wallet a i saw this uh these funds flow into
wallet b wallet b sent it to a contract and then you kind of get this just flow map of how everything
happened in that transaction um now with the decoder you can actually get the the the core data
to be able to create something like that super seamlessly in fact you can just create a component
and then every time you have this type of swap event it'll automatically populate this visual
and so you'll be able to see that um for every single transaction uh with that particular swap
event so it's kind of like a like a dead like a customizable transaction view versus you know what
you might typically see as a fairly static um you know type of transaction view on on various block
explorers very cool so is this something like a it reminds me like bubble maps or or i've seen
these on twitter when when especially like in cases of like hacks or whatever where it shows
kind of one wallet and all of the transactions all where all the funds went to uh to various other
wallets and uh and you kind of see all these lines kind of going in between and showing where all
these wallets are intertwined is it kind of a similar idea where you kind of see a a essentially
a contract and you see kind of like a line or a flow showing to another place and kind of having
essentially the block explorer data but then more in a visual road map is it kind of uh kind of way
or is that is that what you're trying to say is you can easily build that visual because we'll
give you the underlying data in exactly the format that you need and you need to to sort of format
that so the decoder basically takes this you know the the raw transaction and gives you the ability
to customize that lens so in a way it's like um almost customizing your your like an api
endpoint essentially um and be able to have the response data look exactly like you want it to
power the visual that you that you want to to display so the first thing that comes to mind is
for example open sees a transaction history for a specific nft where you see that initially was
meted by this guy then this guy bought it then this other wallets transferred it and then
it was burnt and whatever that entire flow is kind of what how what this would power essentially
yeah and we've already got a decoder for open sees so if you check out the um the uh the gold rush
kit you'll be able to actually see that um what that looks like we've currently got it like a nice
basically like if you get like a strike receipt or like any type of receipt you can kind of see it
very cleanly um what's happened uh between um you know the various parties that have interacted
and so that's the idea behind um the decoders that allows you to build these types of beautiful
interfaces that make it very clear what happened in that transaction awesome yeah so that's actually
what we're going to work with you guys on um and and help you sort of create these
these customized transaction views for uh for melt transactions awesome can't wait can't wait
i'm sure ken is going to have a lot of uh opinions on on how it should be designed and what is it
supposed to look like beyond each can by doing okay we don't hear you yeah i mean data is the
way forward right so anybody who's ever played with a block explorer you know melt um melts
can ether scan whatever you know as soon as you get into anything beyond a basic token transaction
it becomes incredibly difficult for you to be able to you know decrypt that information and so if we
can make it so people can have a basic understanding of what what is happening under the hood and they
can actually you know be able to have enough information to be able to make decisions about
that then we've taken a massive step from this kind of like cryptic web 3 and made that ux much
more important so you know this is kind of the we're dealing with the basic problems still we're
not onto the sophisticated problems we're still working with the basic problems and so things like
this while it might sound small and trivial to someone who's not familiar with it um when it
comes down to developing of the product and developing of you incredibly critical to be
able to use that and to have that so that it doesn't take you you know months to produce
something it takes you hours to produce it absolutely so i think that um we want to open
up now for the audience if anybody has any questions you guys can raise your hand and
we're happy to sort of either bring you up on stage or you can leave questions in twitter
or on youtube so we'll monitor and check and see what you guys have and yeah we'll just wait for
for hands to come up and we'll bring you up on stage so in the meantime how long have you guys
been working on this gold rush and what kind of was the what was the rationale for you guys
to start to develop this or why did why did you see this as a critical component
yeah great uh great question so i think uh you know fundamentally um as a as a data provider
um you know you're kind of heads down sort of building up the pipeline doing the the formatting
being able to you know offer like an api that makes it easy for for developers to pull on-chain data
but it's headless there's there's no visual component to it and so in kind of looking at
the developer journey with what they want to do with on-chain data it became quite apparent to us
you know that we could uh create like a toolkit of some of the most common types of um on-chain
use cases so if you think about like any type of you know wallet they need to show token balances
they need to show some token transactions if you think about any type of gaming um or anything
that involves nft um they want to be able to see that that uh that media asset with some of the
attributes or traits and so we kind of just looked through and said all right well these are the most
common things why not just build out this kit um that's already you know got the underlying data
feed plugged into it and then it just makes their lives a lot easier they can customize it
format or if they decide you know they don't need to to even use it at least they've got some ideas
of you know what they can quickly build um with a with a kit like this and maybe they're already
using some some other kits um so the whole idea was let's just make developer lives easy and then
the side benefit was that it actually made our lives a lot more uh easier in the sense that
you know we could understand what the end user challenges were like if there's any data gaps or
if there's data missing or data not formatted correctly when you're looking at something that's
that's headless it's really hard to sort of you know understand that but if i'm looking at an
nft detail page and i can see that i'm missing you know maybe some of the pricing information
or i'm missing some of the attributes or the image comes out looking all funny then it's very evident
to me that for a user they can't actually use our api because it's it's not you know formatted
correctly or the underlying you know um asset that's provided is not formatted correctly
so became a great you know debugging and and validation tool for us as well um and now we
could actually you know put ourselves in the shoes of the end user and say okay how am i
actually going to use this on-chain data uh and if we can't do it then you know there's no way that
the end user would actually be be be able to do it so that was that was the motivation there
makes complete sense and that's great that you guys had a chance to kind of
use it and kind of look in the mirror and see where where there were gaps and be able to fix
that that's always super critical so okay um i don't think we have any more questions coming
from the audience there was one question we got from youtube in relationship to uh tradfi data
or off-chain data is that anything you guys deal with so our off-chain data is currently
just limited to any of the nft um metadata or media asset data um we don't typically you know
and i should say pricing pricing data of course um but apart from that um i guess that qualifies
under uh tradfi but um beyond that um our focus has been on just optimizing for um on-chain data
um you know to some extent yeah exactly to some extent you know we we would leave it up to the end
user to tie in on-chain data with whatever other data whether it's social maybe there's a crm that
they're plugging this into uh and so we just kind of like default to them to to deal with
with that some of this data we might not actually even want to touch um just from a privacy
consideration good point good point great then um thank you very much harish um i really appreciate
it and uh i think that that's wrapping everything up with regards to the data layer and covalent
if you guys need or want more information you can go to covalent's website uh covalent hq.com was it
that's right um you can tell i've been there many many many times i know i can remember
um um you can also follow on twitter um or x and you can also come uh to meld's twitter we're
going to be continuously be doing use cases and we have a lot of really really interesting stuff
that we're collaborating with covalent on uh over the coming months so expect some really really
exciting stuff as well as obviously a lot of meld's products are being powered by covalent
so thank you everybody and have a great day thanks thanks everyone ciao