Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

🧑‍🚀 Introducing...Mission Commander 🧑‍🚀 Your new guide to Data Universe, through an #SN1 Apex-powered chat interface which can now: 💡 Identify the optimal hashtags and data sources for your query 🧩 Automatically populate your query with the data labels ⚡ Suggest improvements and extensions to your query Real-time social... show more

Macrocosmos

7,475 subscribers

13,256 просмотров • 1 год назад •via X (Twitter)

Игры Наука и технологии Образование #SN1

Anya Rossi• Live Now

Private livecam show

Комментарии: 6

Фото профиля Macrocosmos

Macrocosmos1 год назад

Tell Mission Commander what data you want, and it'll fill in the gaps 💥 It'll even name your project for you 🌟 You can then refine your datasets by manually deleting topics, or by getting Mission Commander to make changes ✅

Фото профиля Macrocosmos

Macrocosmos1 год назад

Ask Mission Commander for feedback on your queries 💡 Enter your subjects - Mission Commander will review them and offer suggestions. It doesn't just make the process easier, it actively helps refine your tasks 🦾

Фото профиля Macrocosmos

Macrocosmos1 год назад

Mission Commander is powered by SN1, Apex - our text prompting and generation subnet 💬 Giving you intelligent, forward-thinking and meaningful results ⚡

Фото профиля Macrocosmos

Macrocosmos1 год назад

💥 Try it out now 💥 Tell us what you think over at our Discord and Telegram 🗣️

Фото профиля Wonderchat

Wonderchat3 лет назад

Automate up to 70% of your customer support today. Save time and help your users find answers quickly. Try now at

Фото профиля TAO MAN

TAO MAN1 год назад

I'm a holder and I delegated a lot of TAO. My opinion is to not emphasize the role of Bittensor as an American foundation because many people are behaving an adverse feeling against Americans especially in Europe. It would be better to move to a neutral country like Switzerland

Похожие видео

Available to everyone: The new analytics lets you query your data directly from a report in real time using ShopifyQL, for more dynamic and customizable reporting. Everyone has a data warehouse now!

Available to everyone: The new analytics lets you query your data directly from a report in real time using ShopifyQL, for more dynamic and customizable reporting. Everyone has a data warehouse now!

tobi lutke

12,139 просмотров • 1 год назад

Introducing AgentKey by Chainbase Labs. AgentKey connects AI agents to the outside world. With one install, your agent can access web search, read pages, reach social platforms, query crypto data, and more. Try it now:

Introducing AgentKey by Chainbase Labs. AgentKey connects AI agents to the outside world. With one install, your agent can access web search, read pages, reach social platforms, query crypto data, and more. Try it now:

Chainbase (💜,💛)

23,102 просмотров • 5 месяцев назад

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:

Spenser Skates

32,464 просмотров • 11 месяцев назад

You can now chat directly with your Vercel Marketplace integrations. Ask questions, query data, or take action in plain English. Powered by MCP under the hood. Try it with Neon, Supabase, Dash0, Stripe, Prisma and Mux, and more coming soon →

You can now chat directly with your Vercel Marketplace integrations. Ask questions, query data, or take action in plain English. Powered by MCP under the hood. Try it with Neon, Supabase, Dash0, Stripe, Prisma and Mux, and more coming soon →

Vercel Developers

24,948 просмотров • 9 месяцев назад

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Akshay 🚀

65,672 просмотров • 11 месяцев назад

INTRODUCING THE NEW GECKOTERMINAL APP ✨ An all-new interface redesigned from scratch. With powerful features and lightning-fast data, you can now discover, analyze, and trade effortlessly—anytime, anywhere. Access data of millions of tokens at your fingertips.

INTRODUCING THE NEW GECKOTERMINAL APP ✨ An all-new interface redesigned from scratch. With powerful features and lightning-fast data, you can now discover, analyze, and trade effortlessly—anytime, anywhere. Access data of millions of tokens at your fingertips.

GeckoTerminal

67,921 просмотров • 1 год назад

🚀 Discover PublicAI Product Ecosystem – Your Gateway to contributes data to train AI and share revenues! 🚀 Unleash the power of PublicAI's Data Hunter Chrome Extension and transform your social media browsing into a treasure trove of valuable data. 📊 Upload your ChatGPT conversations with a simple click and earn rewards for your valuable contributions. 🔍 Use Data Hub to harness your intuition and refine data through community consensus. 🤖 Harness community-approved data to train AI models and craft your own AI Agent. Embark on the AI journey with PublicAI and redefine the future of AI interaction! 🌐🤖 #PublicAI

🚀 Discover PublicAI Product Ecosystem – Your Gateway to contributes data to train AI and share revenues! 🚀 Unleash the power of PublicAI's Data Hunter Chrome Extension and transform your social media browsing into a treasure trove of valuable data. 📊 Upload your ChatGPT conversations with a simple click and earn rewards for your valuable contributions. 🔍 Use Data Hub to harness your intuition and refine data through community consensus. 🤖 Harness community-approved data to train AI models and craft your own AI Agent. Embark on the AI journey with PublicAI and redefine the future of AI interaction! 🌐🤖 #PublicAI

PublicAI

19,805 просмотров • 2 лет назад

We can finally say it! is launching today! We spent a year building the data substrate for the agent economy, one MCP that allows your agents to query the world as a DB, so you can skip the data and focus on building what matters! Cala

We can finally say it! is launching today! We spent a year building the data substrate for the agent economy, one MCP that allows your agents to query the world as a DB, so you can skip the data and focus on building what matters! Cala

Elisenda Bou-Balust

18,688 просмотров • 5 месяцев назад

RAG can’t keep up with real-time data. Airweave builds live, bi-temporal knowledge bases so that your Agents always reason on the freshest facts. Supports fully agentic retrieval with semantic and keyword search, query expansion, and more across 30+ sources. 100% open-source.

RAG can’t keep up with real-time data. Airweave builds live, bi-temporal knowledge bases so that your Agents always reason on the freshest facts. Supports fully agentic retrieval with semantic and keyword search, query expansion, and more across 30+ sources. 100% open-source.

Avi Chawla

91,292 просмотров • 1 год назад

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.

We're excited to announce duckdb-skills, a DuckDB plugin for Claude Code! We think the embedded nature of DuckDB makes it a perfect companion for Claude in your local workflows. The skills supported include: + read-file and query – uses DuckDB's CLI to query data locally, unlocking easy access to any file that DuckDB can read. + read-memories – a clever idea to store your Claude memories in DuckDB and query them at blazing speed. These are powered by two additional skills: + attach-db – gives Claude a mechanism to manage DuckDB state through a .sql file linked to your project. + duckdb-docs – uses a remote DuckDB full-text search database to query the DuckDB docs and answer all of your (and Claude's own) questions.

DuckDB

60,855 просмотров • 6 месяцев назад

Introducing Onairos. Today, companies steal your data every second, lock it up, and use it to line their pockets. But at what cost? The cost is you. Your data is used to power algorithms that hijack your mind with social media, doomscrolling, rage, and endless consumption.

Introducing Onairos. Today, companies steal your data every second, lock it up, and use it to line their pockets. But at what cost? The cost is you. Your data is used to power algorithms that hijack your mind with social media, doomscrolling, rage, and endless consumption.

Zion

109,173 просмотров • 5 месяцев назад

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be *instantly* available *and already up to date with server*. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

Quick demo of Zero’s new background queries. Zero’s sync is query-based. Rather than specifying what data you want using rules or some other separate system, you just use queries. Right inside the client app, you do a query using a full sql-style language. You get filters, subqueries , limits, etc. Zero syncs the data backing these queries to the client. It’s important to realize Zero isn’t really a cache. It’s a replica. It’s eagerly replicating a precise snapshot of a slice of your database - the slice covered by the queries you have open. So there is never stale data in Zero. When you close a query we delete the rows uniquely returned by that query because we can no longer keep them up to date. Of course that kind of sucks for the common case of doing a query, navigating, then pressing “back”. Ideally we want that back nav to be fast. To address this Zero 0.17 adds background queries. You can add a ttl to a query and it will keep running and syncing in the background. This is much different than normal caching because this data stays up to date. If you make the same query again, the results will be instantly available and already up to date with server. If you make a different query the data from the background query is used client-side to answer the new query instantly if possible. This all happens completely automatically. Just by adding the ttl flag.

Aaron Boodman

18,808 просмотров • 1 год назад

The amount of user data being collected by threads is insane. They now have access to your text messages, financial data, health and fitness data, “sensitive info”, and more. I know this is somewhat normal for social media apps, but this much data seems unnecessary and an overreach.

The amount of user data being collected by threads is insane. They now have access to your text messages, financial data, health and fitness data, “sensitive info”, and more. I know this is somewhat normal for social media apps, but this much data seems unnecessary and an overreach.

John Pompliano

181,979 просмотров • 3 лет назад

The Graph's Sunray phase is complete 🌅 Now devs can harness subgraphs to supercharge their dapp's data on The Graph's decentralized network more easily than ever with newly unlocked benefits including: 📊 A free query plan ⚡A seamless upgrade interface 💳 Easy credit card payments Read on to learn about the new features, how to upgrade your subgraph to the network, and what to expect in the next two phases of The Sunrise of Decentralized Data #GraphRising 🌅 🔽

The Graph's Sunray phase is complete 🌅 Now devs can harness subgraphs to supercharge their dapp's data on The Graph's decentralized network more easily than ever with newly unlocked benefits including: 📊 A free query plan ⚡A seamless upgrade interface 💳 Easy credit card payments Read on to learn about the new features, how to upgrade your subgraph to the network, and what to expect in the next two phases of The Sunrise of Decentralized Data #GraphRising 🌅 🔽

The Graph

103,081 просмотров • 2 лет назад

$Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.$

Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.

Akshay 🚀

40,562 просмотров • 8 месяцев назад

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.

Denis Magda

28,597 просмотров • 8 месяцев назад

Introducing new data layers for building footprints, land parcels, and AI powered layers that spot infrastructure assets from Street View imagery. Try these new layers now ➡️ With information right at your fingertips you can spend less time combining data, manually identifying assets, and combing through imagery. These premium layers are now available for Professional & Professional Advanced customers on web and Android.

Introducing new data layers for building footprints, land parcels, and AI powered layers that spot infrastructure assets from Street View imagery. Try these new layers now ➡️ With information right at your fingertips you can spend less time combining data, manually identifying assets, and combing through imagery. These premium layers are now available for Professional & Professional Advanced customers on web and Android.

Google Earth

31,855 просмотров • 4 месяцев назад

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

MCP is mind-blowing. Here is a genius setup that will earn you a promotion with your manager. I have multiple data sources: data in S3, MySQL, and local files. Using Spice (an open-source project), I can co-locate all of that data behind a single SQL endpoint and augment it using MCP. Before, accessing data was slow, and I had to make multiple requests to get anything. After using Spice, I can query the data much faster (since it's mirrored locally), and I don't have to worry about where the data is coming from. Spice acts as an MCP server, so I can connect to it from my IDE or the Claude Desktop app and have access to all the data. But even more cool than that: Spice also acts as an MCP client, so it can connect to other MCP servers. This is where things get really interesting! Watch the video. I'm querying multiple data sources from my IDE and using the Google Maps MCP server for driving directions.

Santiago

142,696 просмотров • 1 год назад

A new roadmap. A New Era of The Graph 🗺️ The Graph’s new roadmap introduces a bold and transformative vision for the future of The Graph! The new R&D roadmap details an expansion of The Graph’s ability to serve web3’s growing demands for data access, while better serving builders and protocol contributors, and improving the overall simplicity and efficiency of the network. After three years of serving builders, The Graph Network is mature, reliable, and performant. The Graph ecosystem has followed through on its commitment to democratize access to blockchain data while also establishing subgraphs as a web3 standard. But The Graph’s innovation journey doesn’t end there. The New Era of The Graph is organized into five core objectives: 1️⃣ World of Data Services: Expanding to provide new data services beyond subgraphs to deliver a rich market of data on the network, serving novel use cases for data scientists and more. This will include more data sources, new query languages, and support for LLMs. 2️⃣ Developer Empowerment: Supporting developers through enhanced DevEx and tooling by introducing streamlined billing, clear pricing models, a new free query plan, and reduced gas fees. A more SaaS-like experience for devs, without compromising on decentralization! 3️⃣ Protocol Evolution & Resiliency: Delivering improvements resulting in a more resilient, flexible, and simple protocol, including updates to delegation. 4️⃣ Optimized Indexer Performance: Boosting network performance with improved Indexer tooling and operational capabilities to deliver increased scalability, reduce costs, and enhanced network reliability. 5️⃣ Interconnected Graph of Data: Creating tools for composable data and a global, organized knowledge graph – interlinking open data and making it easier to build upon. The new roadmap sets in motion an exciting evolution in web3 data infrastructure. In a phased rollout, The Graph will introduce many new features and benefits, including the integration of new data services, new query languages, enhanced developer tooling, improved UX + UI, alongside greater protocol efficiency and resilience. As this new era unfolds, The Graph crystallizes as the connective tissue across the many layers of the web3 stack, evolving into a comprehensive, interwoven graph of data equipped to serve every project dreamt up by web3’s innovators. Read the full announcement linked in the comment below!

A new roadmap. A New Era of The Graph 🗺️ The Graph’s new roadmap introduces a bold and transformative vision for the future of The Graph! The new R&D roadmap details an expansion of The Graph’s ability to serve web3’s growing demands for data access, while better serving builders and protocol contributors, and improving the overall simplicity and efficiency of the network. After three years of serving builders, The Graph Network is mature, reliable, and performant. The Graph ecosystem has followed through on its commitment to democratize access to blockchain data while also establishing subgraphs as a web3 standard. But The Graph’s innovation journey doesn’t end there. The New Era of The Graph is organized into five core objectives: 1️⃣ World of Data Services: Expanding to provide new data services beyond subgraphs to deliver a rich market of data on the network, serving novel use cases for data scientists and more. This will include more data sources, new query languages, and support for LLMs. 2️⃣ Developer Empowerment: Supporting developers through enhanced DevEx and tooling by introducing streamlined billing, clear pricing models, a new free query plan, and reduced gas fees. A more SaaS-like experience for devs, without compromising on decentralization! 3️⃣ Protocol Evolution & Resiliency: Delivering improvements resulting in a more resilient, flexible, and simple protocol, including updates to delegation. 4️⃣ Optimized Indexer Performance: Boosting network performance with improved Indexer tooling and operational capabilities to deliver increased scalability, reduce costs, and enhanced network reliability. 5️⃣ Interconnected Graph of Data: Creating tools for composable data and a global, organized knowledge graph – interlinking open data and making it easier to build upon. The new roadmap sets in motion an exciting evolution in web3 data infrastructure. In a phased rollout, The Graph will introduce many new features and benefits, including the integration of new data services, new query languages, enhanced developer tooling, improved UX + UI, alongside greater protocol efficiency and resilience. As this new era unfolds, The Graph crystallizes as the connective tissue across the many layers of the web3 stack, evolving into a comprehensive, interwoven graph of data equipped to serve every project dreamt up by web3’s innovators. Read the full announcement linked in the comment below!

The Graph

426,146 просмотров • 2 лет назад