Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Structural Questions

  • What is the viability/appetite for "single chain" top level projects?
    • i.e. a project that only runs on fabric/besu/indy/<non-hyperledger-dlt>
    • Should it be top level?  Some limited scope?  A sub project of the chain?
      • If sub-project, are they subject to parent's maintainer and other policies?
  • What about gaps that are "features" rather than a stand alone project.

  • How close to DLT core code do projects need to be?  
    • example: application frameworks, such as a Ruby on Rails for DLT Apps.

Grouping from Discovery Sessions

  • End User Focused Projects
    • Wallets
    • Secret Storage/Vaults
    • Credential Storage
  • Applications
    • General App Feature Libraries
      • Tokens
      • NFTs
      • UX libraries
    • Domain specific toolkits
      • Supply Chain (Grid)
      • Provenance 
      • Exchange, DEX or CEX
  • Cross-chain interoperability
    • private/private
    • public/private
    • public/public
  • Operating and running a chain
    • Alerting
    • Monitoring Dashboards
    • Integration into enterprise data systems
    • Tools to set up chains
  • Protocol
    • Common Consensus interfaces
    • New DLTs


  • No labels