mirror of
https://github.com/pezkuwichain/awesome-hez.git
synced 2026-04-22 05:37:59 +00:00
Refactor deeply nested lists in bizdevbible.md for better readability
Converted 4-5 level nested lists into clearer hierarchical structure using section headings and bold text. This improves scannability and maintainability while preserving all original content. Changes: - Polkadot Cloud section: Added "High-Volume Businesses" and "Custom Web3 Solutions" headings - Polkadot Hub onboarding: Organized into clear categories with level-4 headings - Polkadot Hub limitations: Restructured into "Large Scale Operations" and "Advanced Customization Needs" The refactored structure reduces cognitive load and makes the document easier to navigate.
This commit is contained in:
+60
-44
@@ -17,23 +17,31 @@ The Polkadot Cloud is targeted toward large scale Web3 applications which plan t
|
||||
One Core on the Polkadot Cloud can execute 1,500 transactions per second, which is approximately 4 billion transactions per month. We have seen applications easily execute nearly 10 million transactions in a month without an issue.
|
||||
|
||||
The Polkadot Cloud will be the best place to onboard:
|
||||
- Businesses that want to migrate already existing large volumes of traffic.
|
||||
- Custom Web3 solutions, which gain access to low level building primitives.
|
||||
- Privacy Chains
|
||||
- Trusted Execution Environments (TEEs)
|
||||
- Zero-Knowledge Systems
|
||||
- Large State Chains
|
||||
- Large File Storage (IPFS, Filecoin, large individual files)
|
||||
- Large State Trees (billions of items)
|
||||
- Social Networks
|
||||
- Feeless transactions
|
||||
- Subsidized operations and usage
|
||||
- Businesses looking to abstract the blockchain from their users.
|
||||
- Low Latency Applications
|
||||
- Gaming
|
||||
- MEV Resistance / Control Over Transaction Ordering
|
||||
- Specific kinds of DeFi
|
||||
- etc..
|
||||
|
||||
#### High-Volume Businesses
|
||||
- Businesses that want to migrate already existing large volumes of traffic
|
||||
|
||||
#### Custom Web3 Solutions
|
||||
Custom Web3 solutions gain access to low level building primitives:
|
||||
|
||||
**Privacy Chains:**
|
||||
- Trusted Execution Environments (TEEs)
|
||||
- Zero-Knowledge Systems
|
||||
|
||||
**Large State Chains:**
|
||||
- Large File Storage (IPFS, Filecoin, large individual files)
|
||||
- Large State Trees (billions of items)
|
||||
|
||||
**Social Networks:**
|
||||
- Feeless transactions
|
||||
- Subsidized operations and usage
|
||||
- Businesses looking to abstract the blockchain from their users
|
||||
|
||||
**Low Latency Applications:**
|
||||
- Gaming
|
||||
|
||||
**MEV Resistance / Control Over Transaction Ordering:**
|
||||
- Specific kinds of DeFi
|
||||
|
||||
The Polkadot Cloud will not be the best place for:
|
||||
- New businesses that are still trying to create a customer base.
|
||||
@@ -60,35 +68,43 @@ The Polkadot Hub also has Polkadot native features such as:
|
||||
These should appeal to non-developer audiences in addition to developers passionate about the Web3 space.
|
||||
|
||||
The Polkadot Hub will be the best place to onboard:
|
||||
- Low Time Investment Builders
|
||||
- New Developers
|
||||
- Tinkerers
|
||||
- Explorers (i.e. experts from other ecosystems)
|
||||
- Short-Term Projects
|
||||
- Hackathons
|
||||
- Fundraising
|
||||
- Executing Legal Contracts
|
||||
- Low Overhead / Small Teams
|
||||
- Meme coins
|
||||
- Whitepaper deployment
|
||||
- Passionate Users
|
||||
- Active Polkadot Community
|
||||
- Active Users of Polkadot Hub Applications
|
||||
- Stablecoin Users
|
||||
- Polkadot Native Extensions
|
||||
- Account Abstractions
|
||||
- DAOs
|
||||
- Staking Pools
|
||||
|
||||
#### Low Time Investment Builders
|
||||
- New Developers
|
||||
- Tinkerers
|
||||
- Explorers (i.e. experts from other ecosystems)
|
||||
|
||||
#### Short-Term Projects
|
||||
- Hackathons
|
||||
- Fundraising
|
||||
- Executing Legal Contracts
|
||||
|
||||
#### Low Overhead / Small Teams
|
||||
- Meme coins
|
||||
- Whitepaper deployment
|
||||
|
||||
#### Passionate Users
|
||||
- Active Polkadot Community
|
||||
- Active Users of Polkadot Hub Applications
|
||||
- Stablecoin Users
|
||||
|
||||
#### Polkadot Native Extensions
|
||||
- Account Abstractions
|
||||
- DAOs
|
||||
- Staking Pools
|
||||
|
||||
The Polkadot Hub will not be the best place for:
|
||||
- Doing things at large scale
|
||||
- Large volume of traffic
|
||||
- Potential issues with transaction inclusion
|
||||
- Spikes in fees
|
||||
- Large volume of data
|
||||
- Expensive for the business and/or the end users
|
||||
- Those who need more control over their application
|
||||
- See Polkadot Cloud for customizability options.
|
||||
|
||||
#### Large Scale Operations
|
||||
**Large volume of traffic:**
|
||||
- Potential issues with transaction inclusion
|
||||
- Spikes in fees
|
||||
|
||||
**Large volume of data:**
|
||||
- Expensive for the business and/or the end users
|
||||
|
||||
#### Advanced Customization Needs
|
||||
- Those who need more control over their application (see Polkadot Cloud for customizability options)
|
||||
|
||||
These kinds of users should go to the Polkadot Cloud.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user