Join Discord
Created at 2pm, Mar 4
ilkeArtificial Intelligence
0
Epicenter - Illia Polosukhin: Near Protocol – From AI to High-Throughput Blockchain
Contract ID
eV2Zvj515vmI6Km3okE13vEaZbDWiJ34tIVkl3FaMpk
File Type
MP3
Entry Count
575
Embed. Model
jina_embeddings_v2_base_en
Index Type
hnsw

What began as an AI company trying to seek solutions in order to pay remote (unbanked) workers, Near AI became, in 2018, Near Protocol. Its sharded design was inspired by modern database architecture and large language model (LLM) training. Near Protocol aimed to solve the scalability trilemma, through a modular approach, combining data availability sharding with stateless validation. By abstracting away archaic blockchain standards, Near basically enabled decentralized full-stack development and, in terms of UX, a distributed custodial solution via chain abstraction and account aggregation. We were joined by Illia Poloshukhin, co-founder of Near Protocol, to discuss Near’s journey, from AI company to high-throughput L1 blockchain, and how LLM training influenced the modular design choice. Topics covered in this episode: Illia’s background in AI & ML Scaling large language models (LLMs) and the role of attention Stochastic Parrot vs. Understanding spectrum From Near AI to Near Protocol and the role of LLMs How Near abstracted the blockchain away and enabled decentralized full stack development Defining ecosystem standards to improve UX Chain abstraction, account aggregation and interoperability Chain threshold signature Near’s intent layer Near’s modularity, Nightshade sharding & stateless validation EigenLayer integration

RPC is a standard, but then the way it's implemented, right, can be very different.
Like underneath, you maybe like cached everything in database, maybe using Cloudflare, like whatever the architecture you want to use.
But the standard is there.
start: 45:26 - end: 45:27
And I think what we've been trying to do is define a standard and I mean, have a reference implementation, but for this more key pieces to make indeed the experience more aligned and kind of have this like singular journey for developers and users that is cohesive.
How to Retrieve?
# Search

curl -X POST "https://search.dria.co/hnsw/search" \
-H "x-api-key: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"rerank": true, "top_n": 10, "contract_id": "eV2Zvj515vmI6Km3okE13vEaZbDWiJ34tIVkl3FaMpk", "query": "What is alexanDRIA library?"}'
        
# Query

curl -X POST "https://search.dria.co/hnsw/query" \
-H "x-api-key: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"vector": [0.123, 0.5236], "top_n": 10, "contract_id": "eV2Zvj515vmI6Km3okE13vEaZbDWiJ34tIVkl3FaMpk", "level": 2}'