...

Enterprise enabling software for Distributed Ledger Technology and Multi-Party Systems and the Applications, Frameworks, Tools, and Libraries that support and enable those systems.

...

Allow projects that are explicitly single platform.  These projects need to cover features and capabilities that should not be included in the core of the platform they are servicing. 

• A project needs to have large enough scope and community to exist separately from the core platform 

Examples:

• Subject matter specific extensions
• Optional Tooling and Services such as block explorers
• Frameworks to build dApps on the platform

\[No consensus on this policy change\]

Projects and Themes

• Operational support of specific DLT/MPS platforms
  • Alerting
  • Monitoring dashboards
  • Integration into enterprise data systems
  • Tools to set up chains
• End user focused projects
  • Wallets
  • Secret storage/vaults
  • Credential storage
• Cross chain interoperability
  • (But needs to provide distinct features from existing projects)
• Application support and libraries
  • Tokens
    • Specifically novel uses such as confidential tokens, CBDC scale, etc.
  • NFTs
    • Specifically novel areas, not just profile picture collections.
    • White label marketplace?
    • Utility frameworks for NFTs?
  • UX libraries
• Domain specific toolkits
  • Supply chain (Grid already occupies some space)
  • Provenance 
  • IP
  • Exchanges (DEX or CEX)
• Low level DLT/MPS libraries
  • Common consensus libraries

...

• Operating a specific network
  • Projects may support the network but the governance of such networks must be entirely separate from HLF in inception and operation.
  • Example: Ethereum Mainnet 
• Hosting a specific application
  • HLF may support the software for a particular project, but it will hot host the front end instance of it.  Member companies should provide that service
  • Example: Block Explorers
• Running and operating a formal standards process
  • Standards work may run in parallel to a project, but HLF is interested in the software implementation and community around the software, not the standards making process.
  • Projects may become de facto standards, but formal processes must run outside of HLF.
  • HLF invites projects that are implementations of formal standards processes.

Labs Projects

• Solang
  • Solidity→WASM compiler.
  • Solana, substate, ewasm
  • Applied for incubation in the past.  Rejected for not enough maintainers, now has 3 maintainers
• Perun
  • Confidential state channels across DLTs
• Business Partner Agent
• Orion
  • Centralized key/value ledger
• Fabric (may not be top level, may be absorbed into fabric proper)
  • Operations Console
  • Operator
  • ...
• ...

Labs exits may want to go to being integrated into an existing project instead of becoming an incubating project.

• Example: Weaver/Cactus integration

Elephant in the room

What's Hyperledger's public network story?  There's an opportunity and a threat.

...