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
Infrastructure / Activities
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
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.
02Solana staking & blockchain infrastructure
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.
Continuity planning and disciplined change, subject to operational arrangements.
Safeguards appropriate to the assets involved, subject to internal controls.
Reconciliation procedures and reporting that support review.
03Reference architecture
A generic representation of how SDIF organises infrastructure. It intentionally omits providers, locations, hostnames and configuration.
The public Solana cluster: gossip, consensus and block propagation. SDIF's systems connect to it but do not control it.
Access to chain state for research, review and reconciliation procedures, subject to network controls.
Node software that participates in voting and block production, supported by continuity planning.
Custody safeguards appropriate to company-owned assets, subject to applicable operational arrangements.
04Network participation & technical development
Evaluation of client implementations, configuration choices, hardware profiles and network conditions, and their effect on vote performance, block production and resilience.
Tracking of client releases and network upgrades, with staged evaluation before changes reach production systems.
Software supporting operational review, reconciliation procedures and reporting, developed for internal use.
Post-incident and periodic reviews that feed findings back into procedures, configuration and research priorities.
05Boundaries
Inquiries
Infrastructure providers, vendors and researchers may contact SDIF through the inquiry process.