[Screenshot 2024-10-15 at 16.45.06] This post discusses renaming “parachains” to a more widely accepted and known term. The intent is to reflect the evolving nature of the Polkadot ecosystem while improving visibility and accessibility. Why Consider a Name Change? I understand that renaming “para…

Hey @shawntabrizi , in my view, “rollup data” is intended to refer to anything being pushed through Polkadot cores. Now, it’s just chains, but in JAM, it could be anything, as you pointed out. See the illustration below. [Screenshot 2024-10-24 at 07.52.37] Rollup data incoming into a core (box).…

Thanks for the clarification. Then we are totally aligned on concepts and vision. My questions would be: Is the term rollup used anywhere in existing computing BEYOND blockchain? If not, I think we benefit to not try to rebrand rollup as something bigger than it is, but for us to use a term, whi…

I just read through this entire thread so far and the impression I was left with is that some people believe that marketing and documentation can somehow be divorced from one another, and I think that’s a mistake. Marketing lives everywhere the rubber hits the road. I say this as someone who is pri…

I’m proposing we consider renaming “parachains” to something more universally recognized, like “Polkadot Rollups.” This isn’t about discarding the term entirely; rather, it’s about making Polkadot more accessible, future-proofing our language for updates like JAM, and boosting visibility across the …

I think the “rollup-reactor” terminology can be helpful in positioning Polkadot within specifically the Ethereum ecosystem. We need to remember that rollups refer specifically to validity-scaling, not availability-scaling. For the latter we need DDA systems, which Polkadot Relay and to a much greate…

[image] gavofyork: As a nit-pick I interpret the term “roll-up”, now at least, as “rolling up general computation into some lesser computation, either using CE or ZK tech”, rather than “rolling up transactions”. What is CE here? If i understand your view on rollup, I think we should NOT call…

I’m planning to initiate a significant update to the Wiki, which will include: Replacing “Parachains” with “Rollups”: We’ll transition terminology from “parachains” to “rollups” to align with the latest discussions. Enhancing the Comparison Section: I’ll revamp the comparison section to clarify th…

[image] filippoweb3: Simultaneously, IMO we should work on a comprehensive narrative for Polkadot Hub (L1) and Polkadot Cloud (L0) IMO, I don’t think we should use the terms L1 and L0 to describe the Hub and the Cloud. I understand the logic behind using the terms L1 and L0 for talking to tec…

[image] shawntabrizi: Why call these chains? If you mean the CoreChains service: The “CoreChains service” is named so because a) it’s a JAM (“Polkadot Cloud”) service; b) it uses JAM cores; c) it the transitions of isolated, linear state transition functions aka block-chains. I guess it could…

[image] shawntabrizi: Web3 Applications Where do DApps fit into the definition of “Web3 Applications”? A DApp being (typically a serverless) application (usually a web app) that interacts with a blockchain (or perhaps more broadly with JAM services). Can we just load a DApp up into the Polk…

Renaming "Parachains" to a More Generic Term

Ecosystem

shawntabrizi November 11, 2024, 2:00pm 51

There is a dedicated thread here: The Polkadot Cloud

Topic		Replies	Views
The Polkadot Cloud Ecosystem ux	41	3913	February 24, 2025
Polkadot 3.0 - the JAM upgrade Ecosystem community , marketing	16	4124	August 10, 2025
Polkadot Messaging/Positioning/Narrative Thoughts Ecosystem	14	3418	August 8, 2023
Polkadot Developers Ecosystem ux	19	1002	May 5, 2025
Introducing a new JAM Token? Ecosystem	55	5495	June 22, 2026

Renaming "Parachains" to a More Generic Term

Related topics