Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Current Web3 systems are often slow and expensive to run. JAM takes a different approach, focusing on built-in interoperability and execution closer to the hardware to make things faster and more efficient.

18,927 görüntüleme • 2 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

🔦 ✨ Spotlight on: JAM Day at Sub0 Reset Polkadot co-founder, educator and DJ, Gavin Wood closed out Sub0 Reset with JAM Day: A deep dive into the latest project that plans to transform Web3 and Polkadot. Missed the talk? Here are some key highlights 👇 🍓 First, what is JAM? JAM (Join-Accumulate Machine) is the next-generation, trustless, multicore supercomputer. More specifically: • JAM forms the basis of a “Web3 Cloud” to run services without servers • Combines data hosting and compute functionality • Set to transform Polkadot and permanently change the architecture of Web3. 🏛️ The Web3 Maxims Innovation sometimes requires going back to the roots... → Resilience: Decentralized networks mitigate risks associated with single points of failure. → Generality: Supports diverse dApp needs, such as Governance, Finance, etc. → Performance & Coherency: JAM boosts performance and coherence with advanced synchronization across multiple platforms. → Accessibility: Designed for different user bases, e.g. developers, creators, non-crypto natives, etc. 💬 How does JAM fit into Web3 Barriers still exist for widespread Web3 adoption: • High txn fees • Slow interoperability • High incoherence • Escalating costs Polkadot's Agile Coretime, solves this by ⤵️ 🔸 Lowering barriers to entry 🔸 Optimizing resource allocation and cost savings 🔸 Efficiently allocating blockspace where needed How does JAM stand out? 🔹 Multi-core with mostly coherent shared RAM for smoother functionality 🔹 Strong decentralization with a high degree of resilience 🔹 Better performance optimization 🛠️ Overview of JAM Services Designed as a persistent, workload system on the JAM computer, JAM features a multi-core execution model that is asynchronous, co-schedulable, and orderable ✅ Think of it like a busy coffee shop, and each waiter (a core in JAM) handles multiple orders independently, either in sequence or simultaneously. Payment (bundled gas), is settled upfront, covering every stage of the process from start to finish, ensuring each order is completed efficiently. The JAM Services Pipeline is divided up into 4️⃣ crucial stages: → Authorize: Checks workload is paid for in-core → Refine: Where all work and computation is done → Accumulate: The database → Transfers: Acts as a handler script that coordinates any cross-service signaling or balance transfers 🥾 JAM Roadmap & What to Expect From the initial draft, JAM has seen immense development and continues to optimize — expect to see ⤵️ Soon: Rust JAMSDK for Services & Authorizers 🔥 Q4-2024: Coreboot Q1-2025: CoreVM Q2+Q3-2025: CoreChains Q4-2025: CorePlay Hear it all straight from Gav 👇

Polkadot

57,539 görüntüleme • 1 yıl önce