Skip to main content

Solana

In the best position to win industry adoption through DePIN business models?

Business Model​

What is the business case for investing time and resources into the Solana blockchain?

What is the North Star for the Solana blockchain?

Tokenomics​

MEV is a key component of Solana's tokenomics.

Leadership​

Clarity, Consistency, Commitment, Execution.

  • How clearly communicated is the vision?
  • How consistently is the vision communicated?
  • How well is the vision understood by the community?

Interviews:

Community​

Memecoins:

  • BONK: Solana culture coin.
  • WIF: Dog Wif Hat.

Groups:

Showcase​

What are top projects of each major category that prove the vision and mission? How do these projects compare to other blockchains?

PrimitiveProtocols
DEXsJupiter, Orca, Drift
LendingSolend, Marginfi, Kamino
StakingMarinade Finance, Jito
NFTsMad Lads, Tensorians
DePINHelium, Render Network

Identity​

RWAs​

DePIN​

Dominating infrastructural industry adoption?

DeFi​

Notable DeFi projects:

  1. Jupiter
  2. Drift
  3. Pump.fun
  4. Jito

DeSci​

Breakpoint Keynote

Gaming​

  1. Magic Block

Adoption​

Adoption by incumbent industry leaders.

Analyst Reports​

Engineering​

Clear and consistent focus on hardware integration to maximize performance.

Features​

  • Token Extensions, aligned focus on delivering customer value by providing native support for enterprise features
  • Designed to be the most scalable blockchain for mass adoption
  • High speed, low fees, and a single global state machine allowing composability
  • Extract maximal benefit from hardware evolution.
  • Blinks and Actions
  • Ex Qualcomm Engineering
  • MEV, has both healthy and unhealthy forms

Firedancer​

Firedancer is a new validator being developed by Jump Crypto in C language

  • Highly optimized for performance with zero technical debt
  • Expected to launch on mainnet in late 2024
  • Will provide true decentralization with a second independent validator implementation

Principles​

Principles for architecture and engineering are driven by answering "How minimal can I make the cognitive load for developers to understand the code, then how can I optimize data flow?"

Laser focus on data flow and locality:

  • Modern programming paradigms often hide data flow and locality, which are crucial for performance.
  • Systems should be designed with data flow in mind from the start.
  • Locality is critical for high-performance computing.

Resource planning and allocation:

  • Pre-allocate resources (memory, cores) at job startup rather than relying on dynamic allocation.
  • Be explicit about resource requirements and limitations.
  • Avoid using features like malloc that pretend resources are infinite.

Use a tile architecture:

  • Assign specific tasks to dedicated cores or "tiles".
  • This allows for specialization, efficient caching, and deterministic performance.
  • Provides natural security boundaries between components.

Rethink abstraction layers:

  • Many modern APIs and operating systems hide important low-level details.
  • Create abstractions that allow developers to express locality and data flow without needing to understand all low-level details.

Optimize for real-world constraints:

  • Consider physical limitations like the speed of light.
  • Design systems with concurrency budgets in mind (e.g., number of instruction pointers available).

Encourage proper resource management:

  • Provide developers with tools and abstractions that naturally lead to good resource allocation practices.
  • Avoid relying on the operating system or language runtime to magically handle resource management.

Focus on reliability and determinism:

  • Design systems to be hyper-deterministic and reliable.
  • This is crucial for financial applications that require quick, consistent responses.

Plan for scale from the beginning:

  • For systems like Solana, think in terms of millions of transactions per second and huge numbers of accounts.
  • Design for quick recovery from outages.

Rethink networking protocols:

  • Existing protocols like QUIC may not be optimal for validator needs.
  • Consider designing purpose-built protocols for high-performance blockchain systems.

Address implicit behaviors:

  • Spend time identifying and specifying all implicit behaviors in the system.
  • This is crucial for creating a reliable and consistent implementation across different clients.

Developer Roadmap​

Solana Rust Roadmap

Product Development​

Onboarding​

Participation progression. How good is the onboarding experience relative to other blockchains?

Learning Resources​

Official: Solana Developers

YouTube Creators:

Example Apps from simple to more complex.

Hackathons​

Attachments​