Skip to main content

Which Blockchain

How do you decide which protocol is best to invest your precious time and energy to build the skillset required to engineer systems for business models that have sustainable value propositions?

To be trustworthy code should be open source? In that case what prevents your code from copy and paste vampire attacks?

Intent​

Evolve a standardized framework for navigating the decision maze in identifying the best blockchain strategy for your business model and engineering expertise.

Boundaries​

Confirmation Rules

  1. Ledger Growth
  2. Censorship Resistance
  3. Data Availability
  4. Reorg Resistance
  5. Validity

What makes an L2 and L2?

Roles​

Comparison Table​

Primary development environments, EVM vs SVM vs SUI

ItemEVMSVMSUI
BlockchainEthereum, L2sSolanaSUI
LanguageSolidityRustMove
PlaygroundRemix
WalletsMetamaskPhantom
ExplorersEtherscanSolscan
Dev ToolsReview

Standards​

Onchain primitives.

ItemEVMSVM
StandardsERC, EIP?
TokensERC20
Single NFTERC721
Multi NFTsERC1155
Embedded NFTsTrue
EventsContact Events
PatternsTrue

Problems​

What are the biggest problems for onboarding new users and use cases?

What problems cause a shit user experience?

What are the biggest hurdles for software developers to ship valuable solutions?

Checklist​

Decision checklist for choosing best fit blockchain architecture for your business model.

  1. Define Business Requirements
  2. Assess Technical Capabilities
  3. Evaluate Security and Decentralization Needs
  4. Consider Interoperability and Ecosystem Integration
  5. Long-term Vision and Scalability

Define Business Requirements​

  • Transaction Volume: High (Modular) vs. Low to Moderate (Integrated)
  • Latency Sensitivity: Low latency required (Integrated) vs. Tolerable latency (Modular)
  • Resource Availability: High resources (Integrated) vs. Variable resources (Modular)

Assess Technical Capabilities​

  • Development Expertise: High expertise in blockchain (Modular) vs. General development skills (Integrated)
  • Complexity Management: Ability to handle complex systems (Modular) vs. Preference for simplicity (Integrated)

Evaluate Security and Decentralization Needs​

  • Security Prioritization: High security needs (Integrated) vs. Balanced security with flexibility (Modular)
  • Decentralization Importance: High decentralization (Integrated) vs. Acceptable centralization risks (Modular)

Consider Interoperability and Ecosystem Integration​

  • Interoperability Needs: High need for integration with other networks (Modular) vs. Self-contained system (Integrated)
  • Ecosystem Participation: Active participation in a diverse ecosystem (Modular) vs. Focus on a single ecosystem (Integrated)

Long-term Vision and Scalability​

  • Scalability Requirements: Future-proof scalability (Modular) vs. Current needs met (Integrated)
  • Innovation and Flexibility: Need for continuous innovation (Modular) vs. Stability and predictability (Integrated)

Primary Constraints​

Define the key constraints.

  • Time Horizion?
  • Lock In?
  • Censorship Resistance

What components required to make up the stack?

  • Programming Languages

What Network Effects?

Dimensions​

What attributes matter most?

  • Gas Fees
  • Throughput

Attachments​