---
# System prepended metadata

title: Builders Problem Statement

---

# Builders Problem Statement

## Blockers for ecosystem teams trying to build with our tech

### Exploration Stage
- Rust and Substrate are difficult to grasp, no good documentation. To add to this, I understand (correct me if wrong) that internal legal has a say to limit documentation among products such that Polkadot and Substrate are separate topics.
### Building Stage
- Lack of understanding of XCM -> high expectations of what it can deliver.
   - don't know how to create a call
   - don't really understand how to use it with the asyncronos constrains
- Teams don't pay attention to weights, this might be one of the most common things spotted by SRLabs.
- Unfamiliarity with substrate primitives like StorageDoubleMap -> Lack of docs? 
- Error handling
- DevOps: not used to mantaining a network as Web3 Devs, therefore no team knowledge on this regard (lack of monitoring, debugging, maintainance, etc).
### Launching Stage
- Crowdloan and auction mechanism. They are afraid of the process, both for cost and for tech. If they don't win an auction, they are stuck with the wasm and genesis blob until they do.
- DevOps: not used to mantaining a network as Web3 Devs, therefore no team knowledge on this regard  (lack of monitoring, debugging, maintainance, etc).
### Live Stage
- Multisig usability
- UI/UX capabilities
   - What are the actual problems here? Hard to build UI?
   - Hard to interact with a node?
   - Understanding how to work with on-chain metadata.
   - Error handling: the order in which pallets is instanciated is important.
- Lack of a strong ecosystem of L1 DEXs (Eg. Mangata is still Kusama only)
- Lack of oracle primitives
### Others
- DevOps capabilities needed
   - What is so difficult about it?
- Unclear migration path for solo-para, or Polka-Para - Kusama-Para
- Migration from Solidity to Substrate

## Unique features we promote: Security, Trustless Interoperability, Flexibility, Scalability 
- Unique live features which are not possible with smart contract (EVM) systems
- Parachains
   - Bring your own gas (paying gas with any asset)
   - Turing complete processes (no forced ending)
   - Two dimensional weights system, improving efficiency
   - Forkless upgrades by governance
   - MEV prevention by default (tapping into block producing)
   - Permissionless stablecoin (USDT) integration directly to Parachain through Statemint/Statemine
- Solochains
   - Own consensus mechanism (Subspace / Aleph Zero / Cloudwalk).

## What to explore
- Milestone Reviews
- SRLabs Reviews
- Ask on SBP channel
- New vs Old builders
 
How to go around this:
- Actionable items: what needs to change.
- What evidence we have.
- Deployed vs Substrate. Focus on things that are deployed now.
- Are there crazy things built on Solo chains? What do they need to be a parachain?
- Making substrate extremely good for parachains, and extremely easy for parathreads
