Parachains are powerful, but may not be right for your project. Edgeware plans both EVM and Wasm smart contract modules giving you a quicker path to community and market-fit.

Why go Edgeware?

Turn-Key Community

  • Tap into an existing community of validators, holders, stakers, and governance participants instead of managing an entire chain’s community, letting you focus on your use-case and finding fit.
  • You have the option to manage your governance stack more simply by participating in Edgeware instead of growing and. managing a parachain governance system (plus monitoring relay-chain governance) by relying on a community of similarly-positioned developers to share the work.
  • Share in the technical support community and documentation of an existing chain.
  • Additionally, nested parachains repurpose validator infrastructure and node operators, who historically provide development tools, promotional efforts and more. When becoming a parachain, validators are no longer required because of the shared security model of the relaychain.
  • Nested parachains are possible — Edgeware may someday launch relaychain functionality, making transitions from dapp-to-chain more fluid, token-incentive aligned, and maintaining your community and ecosystem of tools.

Test Before You Invest

  • Launch, test, and scale on Edgeware while you consider whether to pursue a parachain and an appropriate token-economic model for that chain.
  • See if your product or dapp serves users before taking on the expenses of scaling to a parachain.
  • No slot auctions. Existing on a parachain doesn’t cost tokens to bond for limited slots, and you can never be removed from the ecosystem after that claim expires. You also don’t have to convince relay-chain token holders like DOT holders to participate in your crowdfunding on your behalf.

Flexible, functional, friendly.

  • Edgeware plans support for EVM, wasm smart contract modules, bridges to chains like ETH and BTC, and more. Being on Edgeware means having direct access to these functions, rather than using IBC to access a parachain on your relay-network with them, or incorporating their functions into your parachain.
  • Benefit from intra-blockchain communication with assets and dapps on Edgeware while Polkadot matures and finalizes XCMP.

Develop What Matters

  • Runtime development is a different beast than dapp development — on Edgeware you can focus on the stack that you excel in, instead of managing a parachain runtime.
  • Edgeware is a great fit if you don’t need specific data storage and transaction requirements for your use-case.
  • Edgeware supports user-submitted logic, which can’t be executed on a native chain. If you have users providing logic, it must be on a smart contract chain.

Why not to go Edgeware?

  • You don’t want on-chain governance to affect your tech stack.
  • You need a native token and native token engineering to support your economic model.
  • You need more comprehensive control over the runtime logic, have specific transaction or data storage requirements.
  • You don’t ingest user-submitted logic.
  • You want the flexibility of configuring your own runtime and have the talent to support that goal.
  • You have access to sufficient DOTs or methods of gaining the support of DOT holders to pursue a parachain slot.
  • You have your own community and want to control the narrative more tightly.