Infrastructure / Activities

Capital, staking and infrastructure, operated as one system.

SDIF's activities are conducted for its own account. This page describes what the company does and how its infrastructure is organised — at a level of generality that protects operational security.

01Proprietary investment & trading

Positions taken for the company's own account.

SDIF holds and trades digital assets using proprietary capital. The activity is principal-only: the company does not execute orders for others, offer managed accounts or provide recommendations to anyone.

Positions are taken within limits that are set in writing before capital is committed, covering matters such as asset eligibility, concentration, venue and counterparty exposure, liquidity and the use — or exclusion — of leverage. Limits are reviewed on a defined cadence and whenever market or operational conditions change materially.

Strategy specifics, positions, venues, counterparties and results are confidential and are not published.

  • BasisPrincipal-only, proprietary capital
  • LimitsWritten and approved before deployment
  • ReviewPeriodic and event-driven
  • DisclosureNo positions, venues or results published

02Solana staking & blockchain infrastructure

Participation in proof-of-stake with company-owned assets.

On proof-of-stake networks, staked assets help secure the network and validators are rewarded for voting on and producing blocks. SDIF participates in Solana's staking system using company-owned assets and studies the mechanics that govern it: delegation, epochs, vote credits, commission, inflation and the operational behaviour that determines validator performance.

SDIF approaches digital asset infrastructure with an emphasis on security, operational resilience, risk management, and transparent reporting. Our infrastructure strategy incorporates appropriate custody safeguards, continuity planning, and reconciliation procedures, subject to applicable operational arrangements and internal controls.

SDIF does not stake on behalf of customers, operate a public staking service or accept delegations as a business.

Resilience

Continuity planning and disciplined change, subject to operational arrangements.

Custody safeguards

Safeguards appropriate to the assets involved, subject to internal controls.

Transparent reporting

Reconciliation procedures and reporting that support review.

03Reference architecture

Four layers and an oversight plane.

A generic representation of how SDIF organises infrastructure. It intentionally omits providers, locations, hostnames and configuration.

SDIF infrastructure architecture (generic) Four layers: network, RPC and data access, validator operations and key management, with an oversight plane spanning all layers. L4L3L2L1 Public networkSolana cluster · gossip · consensus · block propagation RPC & data accessRead paths · state queries · indexing Edge & network controlsFirewalling · rate limits · segmentation Validator nodeVote & block production · client software ContinuityContinuity planning · change control Key managementCustody safeguards · subject to internal controls Custody safeguards Internal controls Approval records Continuity planning Oversight& reporting plane SecurityResilienceRisk managementInternal controlsReconciliationReporting SDIF infrastructure layers (generic): network, RPC and edge, validator operations, key management, with oversight across all layers. L4Public networkSolana cluster · consensusL3RPC & edgeData access · network controlsL2Validator operationsValidator node · continuityL1Key managementCustody safeguards OVERSIGHT & REPORTING Oversight spans every layer: security,resilience, reconciliation, reporting.
Fig. 1 — Generic layered architecture. Not a network map.
L4

Network

The public Solana cluster: gossip, consensus and block propagation. SDIF's systems connect to it but do not control it.

  • Cluster and client release tracking
  • Participation in testnet where appropriate
L3

RPC, data & edge

Access to chain state for research, review and reconciliation procedures, subject to network controls.

  • Interfaces governed by internal controls
  • Exposure considered in design
L2

Validator operations

Node software that participates in voting and block production, supported by continuity planning.

  • Upgrades evaluated before adoption
  • Changes subject to internal controls
L1

Key management

Custody safeguards appropriate to company-owned assets, subject to applicable operational arrangements.

  • Safeguards governed by internal controls
  • Continuity considered in planning

04Network participation & technical development

Research that runs on real systems.

Validator-related research

Evaluation of client implementations, configuration choices, hardware profiles and network conditions, and their effect on vote performance, block production and resilience.

Client diversity & upgrades

Tracking of client releases and network upgrades, with staged evaluation before changes reach production systems.

Internal tooling

Software supporting operational review, reconciliation procedures and reporting, developed for internal use.

Operational review

Post-incident and periodic reviews that feed findings back into procedures, configuration and research priorities.

05Boundaries

What SDIF does not do.

  • Hold, stake or trade assets on behalf of customers
  • Operate an exchange, broker, payment or money-transmission service
  • Offer validator, staking or RPC services to third parties
  • Publish return figures or performance claims

Inquiries

Infrastructure and technical inquiries.

Infrastructure providers, vendors and researchers may contact SDIF through the inquiry process.

Submit an inquiry