🧪 Sphere10 Framework

Developer: Herman Schoenfeld
Copyright: © 2018-Present Herman Schoenfeld
License: MIT NON-AI
Status: Production-Ready

---

📋 Project Overview

Sphere10 Framework is a low-level, high-performance .NET utility library providing composable data structures and persistence primitives. It excels at scenarios requiring fine-grained control over memory, serialization, and transactional semantics—think blockchain systems, embedded databases, high-volume analytics, and custom storage layers.

Unlike general-purpose libraries, Sphere10 Framework doesn't provide application frameworks or abstractions. Instead, it offers:

• 50+ collection types (extended lists, stream-mapped, paged, recyclable, merkle-aware)
• Advanced serialization framework (polymorphism, references, versioning, constant-size encoding)
• Transactional ACID primitives (scopes, streams, collections with commit/rollback)
• Merkle-tree implementations (flat, simple, long, partial) for integrity proofs
• Cryptographic utilities (hashing, signatures, key derivation, VRF, post-quantum schemes)
• Clustered streams (multi-stream storage, dynamic allocation, attachments)
• Thread-safe concurrent collections and producer-consumer patterns
• 50+ string, enumerable, task, stream, and type extension methods

Key Attributes

• Language: C# targeting .NET 8+ (with .NET Standard 2.0 compatibility where applicable)
• Dependencies: Zero external dependencies for core functionality (optional: BouncyCastle, Newtonsoft.Json)
• Platform Support: Windows, Linux, macOS, iOS, Android
• Philosophy: Composable, explicit, performance-conscious, extensible, correct
• Tests: Comprehensive test suite with 25+ subsystems and 2000+ tests
• Maturity: Production-ready (v2.0.2) with battle-tested core subsystems

� Installation

dotnet add package Sphere10.Framework

�🛠️ Tools.* Namespace — Global Tooling Framework

The Tools namespace is a defining feature of Sphere10 Framework, providing a global, IntelliSense-discoverable collection of static utility methods organized by domain. This acts as a single point of discovery for developers—instead of searching for the right helper class, simply type Tools. and explore available operations across the entire framework.

📖 Getting Started: See the Tools Reference for the complete catalog and usage patterns.

Core Tools Classes

Framework-Wide Utilities

• Tools.Array – Array manipulation, copying, resizing, searching
• Tools.Collection – Collection operations, iteration, filtering, transformation
• Tools.Crypto – Hashing, signatures, cryptographic operations
• Tools.DateTime – Date/time parsing, formatting, calculations
• Tools.Enum – Enumeration utilities, descriptions, conversion
• Tools.Exception – Exception handling, formatting, analysis
• Tools.Expression – LINQ expression building and manipulation
• Tools.FileSystem – File I/O, directory operations, temp file management
• Tools.Json – JSON serialization, parsing, transformation
• Tools.Lambda – Lambda expression utilities and manipulation
• Tools.Mail – Email composition and sending utilities
• Tools.Math / Tools.MathPlus – Mathematical operations, RNG, advanced calculations
• Tools.Memory – Buffer operations, memory allocation, byte formatting
• Tools.Network – Network utilities, IP operations, connectivity
• Tools.Object – Object cloning, copying, inspection
• Tools.Operator – Generic operator invocation (Add, Subtract, etc.)
• Tools.Parse – String parsing, type conversion
• Tools.Reflection – Reflection utilities, type analysis, member inspection
• Tools.Runtime – Runtime environment, version detection, diagnostics
• Tools.Scope – Transactional scope management
• Tools.Span – Span and memory utilities
• Tools.Stream – Stream operations, decoration, reading/writing
• Tools.Text – String manipulation, formatting, generation
• Tools.Thread – Threading utilities, synchronization, async helpers
• Tools.Url – URL parsing, encoding, manipulation
• Tools.Value – Value type utilities and conversions
• Tools.Xml – XML serialization, parsing, transformation

Platform-Specific Tools

Windows Integration

• Tools.WinTool – Windows registry, services, events, privileges
• Tools.WindowsTool – Advanced Windows operations
• Tools.Tool (WinForms) – WinForms-specific utilities

Web & Networking

• Tools.Web.Html – HTML generation, parsing, manipulation
• Tools.Web.AspNetCore – ASP.NET Core integration
• Tools.Web.Downloader – HTTP downloads and streaming

Database Access

• Tools.Data – Generic database operations
• Tools.Sqlite – SQLite-specific utilities
• Tools.MSSql – SQL Server-specific utilities
• Tools.NHibernate – NHibernate ORM integration
• Tools.Xml – XML data handling
• Tools.Json – JSON data handling

Mobile Platforms

• Tools.iOSTool – iOS-specific utilities
• Tools.AndroidTool – Android-specific utilities (as available)

Application Framework

• Tools.Config – Configuration and settings management
• Tools.NUnit – NUnit testing utilities
• Tools.Drawing – Graphics and drawing operations
• Tools.Debugger – Debug-time utilities

Usage Pattern

using Sphere10.Framework; // Import the framework namespace to access Tools // String operations string sanitized = Tools.Text.RemoveWhitespace(userInput); string truncated = Tools.Text.Truncate(longString, 100); // Collection operations var filtered = Tools.Collection.Where(items, x => x.IsActive); var flattened = Tools.Collection.Flatten(nestedList); // Cryptographic operations byte[] hash = Tools.Crypto.SHA256(data); bool isValid = Tools.Crypto.VerifySignature(data, signature); // JSON serialization string json = Tools.Json.Serialize(obj); var deserialized = Tools.Json.Deserialize<MyType>(json); // File operations string tempFile = Tools.FileSystem.GenerateTempFilename(); Tools.FileSystem.WriteAllText(path, content); // Database access var dbConnection = Tools.Sqlite.Create(connectionString); var dataAdapter = Tools.MSSql.CreateAdapter(connectionString); // Network utilities bool isOnline = Tools.Network.IsInternetAvailable(); string publicIP = Tools.Network.GetPublicIPAddress(); // Windows-specific (Windows platform only) bool serviceRunning = Tools.WinTool.IsServiceRunning("MyService"); Tools.WinTool.StartService("MyService"); // Web utilities (ASP.NET Core context) string sanitized = Tools.Web.Html.SanitizeHtml(userHtml); var actionResult = Tools.Web.AspNetCore.CreateResponse(data);

Design Philosophy

The Tools namespace embodies several key principles:

1. Discovery-First: Type Tools. to explore all available operations in IntelliSense
2. Consistency: Related operations grouped under consistent tool names
3. Extensibility: Projects extend with their own Tools.* classes (e.g., Tools.WinTool, Tools.iOSTool)
4. Composability: Tools methods work together seamlessly for complex operations
5. Performance: Methods optimized for production use, with zero-allocation variants where possible
6. Type Safety: Generic methods preserve type information, avoiding casts

Extending with Custom Tools

New projects in the framework define their own tool classes:

// In Sphere10.Framework.Windows namespace Tools; public static class WinTool { public static bool IsServiceRunning(string serviceName) { /* ... */ } public static void StartService(string serviceName) { /* ... */ } } // In Sphere10.Framework.Data.MSSQL namespace Tools; public static class MSSqlTool { public static IDataAccessCommand CreateAdapter(string connectionString) { /* ... */ } } // In Sphere10.Framework.Web.AspNetCore namespace Tools.Web; public static class AspNetCoreTool { public static IActionResult CreateResponse<T>(T data) { /* ... */ } }

When a new domain adds its own tool class, it automatically becomes discoverable alongside all other tools.

🚀 Quick Navigation

Core Sphere10 Framework Library Domains

Data Structures & Collections

• 📦 Collections/ – Extended lists, stream-mapped, recyclable, paged, observable, synchronized variants
• 🌳 Merkle/ – Merkle-tree implementations: flat, simple, long, partial
• 🔗 ClusteredStreams/ – Multi-stream storage, attachments, dynamic allocation

Persistence & Serialization

• 💾 Serialization/ – Item serializers, polymorphism, references, versioning
• 📊 ObjectSpaces/ – Typed dimensions, indexing, integrity proofs, transactions
• 🔄 ObjectStream/ – Stream-backed object storage with indexes

Transactions & Scoping

• 🎯 Scopes/ – Transactional boundaries, commit/rollback, isolation levels
• 💳 Transactions/ – Transaction management and coordination

Cryptography & Security

• 🔐 Crypto/ – Hashing, signatures, key derivation, VRF algorithms
• 🔑 Protocol/ – Protocol abstractions and messaging

Streams & I/O

• 📝 Streams/ – Stream decorators, bounded, fragmented, extended memory
• 📄 IO/ – File I/O operations and utilities

Utilities & Extensions

• ✂️ Text/ – String extensions, formatting, case operations, validation
• 🔤 Encoding/ – VarInt, CVarInt, compact integer encoding
• 🧠 Memory/ – Buffer operations, memory allocation, management
• ⚡ Threading/ – Synchronization, producer-consumer patterns
• 💾 Cache/ – Action caches, reaping policies, session management
• 🗄️ Repository/ – Repository pattern implementations
• 🔍 Mapping/ – Object mapping and transformation
• 🎲 Conversion/ – Type conversions and parsing
• 📐 Maths/ – Mathematical utilities
• 📅 Values/ – Value types and structures
• 🏗️ Comparers/ – Comparison and equality implementations

Type System & Reflection

• 🔎 Introspection/ – Reflection and type analysis
• 📦 Types/ – Type utilities and checks
• 🏷️ Attributes/ – Custom attributes
• 📋 Framework/ – Framework abstractions
• 🔌 Extensions/ – Framework extension methods

Data & Resources

• 🌍 DataSource/ – Data source abstractions
• 🔌 Peripherals/ – Hardware peripherals access
• 🌐 Network/ – Network utilities
• 🎯 Environment/ – Environment and system information
• ⚙️ Misc/ – Miscellaneous utilities
• 📦 Objects/ – Object utilities
• 🎛️ Filter/ – Filtering abstractions
• 📊 Functional/ – Functional programming utilities
• ♻️ Disposables/ – Disposable pattern utilities
• 🔗 Events/ – Event handling utilities
• ⚠️ Exceptions/ – Exception handling
• 📖 Loadable/ – Loadable resource abstractions
• 📝 Logging/ – Logging utilities
• 💾 Persistable/ – Persistence abstractions
• 🔧 Saveable/ – Save/load patterns
• ⏰ Scheduler/ – Task scheduling
• 📏 Sizing/ – Size calculations and measurements
• 🎯 Spans/ – Span and memory utilities
• 📝 TextWriters/ – Text writing abstractions

Related Projects

Data Access & Persistence

• Sphere10.Framework.Data – Database abstraction layer (SQL Server, SQLite, Firebird)
• Sphere10.Framework.Data.Sqlite – SQLite-specific integration
• Sphere10.Framework.Data.MSSQL – SQL Server integration
• Sphere10.Framework.Data.Firebird – Firebird integration
• Sphere10.Framework.Data.NHibernate – NHibernate ORM integration
• Sphere10.Framework.Windows.LevelDB – High-performance embedded key-value store

Networking & Communications

• Sphere10.Framework.Communications – Multi-protocol networking (RPC, TCP, UDP, WebSockets)
• Sphere10.Framework.Web.AspNetCore – ASP.NET Core integration and middleware

Cryptography & Consensus

• Sphere10.HashLib4CSharp – Hashes & checksums (SHA-1/2/3, BLAKE2, CRC; stream/file APIs)
• Sphere10.Framework.CryptoEx – Extended cryptography (ECDSA, ECIES, Schnorr, post-quantum)
• Sphere10.Framework.Consensus – Blockchain consensus mechanisms

Desktop & Platform Integration

• Sphere10.Framework.Windows – Windows utilities (registry, services, events, security)
• Sphere10.Framework.Windows.Forms – WinForms component integration
• Sphere10.Framework.Windows.Forms.Sqlite – SQLite integration for WinForms
• Sphere10.Framework.Windows.Forms.MSSQL – SQL Server integration for WinForms
• Sphere10.Framework.Windows.Forms.Firebird – Firebird integration for WinForms
• Sphere10.Framework.Drawing – Graphics and drawing utilities

Application Framework

• Sphere10.Framework.Application – Lifecycle management, DI, configuration, settings

Testing & Quality

• Sphere10.Framework.NUnit – NUnit testing utilities
• Sphere10.Framework.NUnit.DB – Database testing utilities

Cross-Platform & Generators

• Sphere10.Framework.Android – Android platform integration
• Sphere10.Framework.iOS – iOS platform integration
• Sphere10.Framework.macOS – macOS platform integration
• Sphere10.Framework.Generators – Code generation utilities

Test Suites

Core Library Tests

• Sphere10.Framework.Tests – Comprehensive test suite for all Sphere10 Framework domains

Related Project Tests

• Sphere10.Framework.Communications.Tests – Networking and protocol tests
• Sphere10.Framework.CryptoEx.Tests – Extended cryptography tests
• Sphere10.Framework.Data.Tests – Database integration tests
• Sphere10.Framework.Windows.Tests – Windows utilities tests
• Sphere10.Framework.Windows.LevelDB.Tests – LevelDB integration tests
• Sphere10.HashLib4CSharp.Tests – Cryptographic hash tests

---

🎨 Design Philosophy

Core Principles

Composability: The library is structured around small, focused abstractions that compose predictably. Decorators, adapters, and interfaces allow developers to layer functionality without tight coupling.

Explicit Control: Sphere10 Framework favors explicitness over magic. Memory allocation strategies, serialization formats, caching policies, and locking semantics are configurable rather than hidden behind opaque defaults.

Performance-Conscious: Many components are optimized for batch operations, memory locality, and reduced allocations. The library provides both in-memory and stream-backed variants of collections to accommodate different performance/capacity tradeoffs.

Extensibility: Core abstractions like IItemSerializer<T>, IExtendedList<T>, and ITransactionalScope are designed to be implemented or decorated by user code. The library provides building blocks rather than closed systems.

Correctness: Transaction-aware data structures emphasize ACID semantics where applicable. Merkle tree implementations prioritize cryptographic correctness. Thread-safety guarantees are explicit and documented.

❌ Non-Goals

• High-level Application Frameworks: Sphere10 Framework does not provide MVC frameworks, dependency injection containers, or application scaffolding.
• Platform Abstractions: The library does not abstract away platform-specific APIs beyond what .NET Standard requires.
• Opinionated Workflows: While the library enables patterns like repositories and transactional scopes, it does not enforce specific architectural patterns.

🗂️ Domains Covered

Collections

Sphere10 Framework provides an extensive suite of collection types that extend beyond the standard .NET collections:

• Extended Lists and Collections: Interfaces like IExtendedList<T> and IExtendedCollection<T> support range-based operations (batch reads, writes, insertions, deletions) for improved performance when working with large datasets.
• Stream-Mapped Collections: Collections such as StreamMappedList<T>, StreamMappedDictionary<TKey, TValue>, and StreamMappedHashSet<T> persist their data to streams, enabling collections that exceed available memory while maintaining list/dictionary/set semantics.
• Recyclable Lists: IRecyclableList<T> and its implementations maintain a pool of reusable indices for deleted items, optimizing scenarios with frequent insertions and deletions.
• Paged Collections: Both memory-paged and file-paged lists partition data into pages, supporting arbitrarily large datasets with configurable memory footprints.
• Observable Collections: Observable variants of standard collections expose events for monitoring mutations, supporting use cases like change tracking and logging.
• Synchronized Collections: Thread-safe variants like SynchronizedExtendedList<T>, SynchronizedDictionary<TKey, TValue>, and ProducerConsumerQueue<T> for concurrent scenarios.
• Specialized Data Structures: Bloom filters, binary heaps, circular lists, bounded lists, and bidirectional dictionaries address specific algorithmic needs.

🔗 Clustered Streams

The ClusteredStreams subsystem provides a sophisticated mechanism for managing multiple logical streams within a single underlying stream. This enables:

• Multi-Stream Storage: A single file or stream can host multiple independent logical streams, each with its own lifecycle and addressing.
• Dynamic Allocation: Streams grow and shrink dynamically, with clusters allocated and linked as needed.
• Metadata Storage: Headers and metadata are stored alongside stream data, supporting features like indexing and merkle-tree integration.
• Attachments: Pluggable IClusteredStreamsAttachment components allow behaviors like indexing, merkle-tree maintenance, and key storage to be composed declaratively.

This architecture underpins the library's stream-mapped collections and object spaces, providing a flexible foundation for custom persistence schemes.

🌌 Object Spaces

Object spaces abstract the storage and retrieval of typed objects across multiple "dimensions" (logical tables). Key capabilities include:

• Typed Dimensions: Each dimension stores objects of a specific type, with configurable serialization and indexing strategies.
• Indexing: Automatic or custom indexes accelerate lookups by projected keys. Both unique and non-unique indexes are supported.
• Merkle-Tree Integration: Optional merkle-tree attachments provide cryptographic proofs of data integrity.
• ACID Transactions: Object spaces can participate in transactional scopes, supporting commit/rollback semantics.

Object spaces are suitable for lightweight embedded databases, event stores, and other scenarios requiring structured persistence without a full database engine.

🌳 Merkle Trees

Sphere10 Framework includes multiple merkle-tree implementations optimized for different use cases:

• Flat Merkle Trees: Store all nodes in contiguous memory, optimized for fast random access and proof generation.
• Simple Merkle Trees: Lazily compute parent nodes, suitable for smaller trees where memory is less constrained.
• Long Merkle Trees: Designed for very large datasets, retaining only sub-root hashes in memory while supporting append and proof operations.
• Partial Merkle Trees: Maintain only a subset of nodes, useful for constructing and verifying multi-item proofs.

These implementations integrate with collections, enabling IMerkleList<T>, IMerkleDictionary<TKey, TValue>, and IMerkleSet<T> variants that maintain cryptographic integrity proofs alongside their data.

🔐 Cryptography

The library provides cryptographic primitives and utilities:

• Hashing: Wrappers for standard hash functions (SHA-256, SHA-512, SHA-3, etc.) plus specialized implementations like BLAKE2b and MurMur3.
• Digital Signatures: Abstractions for signature schemes, including stateless schemes (ECDSA, EdDSA, Schnorr) and post-quantum candidates (W-OTS, W-OTS#, AMS).
• Key Derivation: PBKDF2 and custom key derivation functions.
• Verifiable Random Functions (VRF): Primitives for generating cryptographically verifiable random outputs.
• Data Protection: Secure memory handling and encryption utilities for sensitive data.

📦 Serialization

Sphere10 Framework's serialization framework is designed for efficiency, control, and extensibility:

• Item Serializers: The IItemSerializer<T> abstraction enables custom serialization logic for any type. Serializers can be composed, decorated, and registered in a SerializerFactory.
• Polymorphic Serialization: Support for serializing and deserializing class hierarchies with type discrimination using [KnownSubType] attributes.
• Reference Handling: Automatic tracking and resolution of object references and cycles within a serialization context.
• Constant-Size Serialization: Specialized serializers for fixed-width data, enabling efficient indexing and random access.
• Versioning: Support for versioned serialization strategies, allowing schemas to evolve over time.

The framework integrates deeply with the library's collections and storage primitives, ensuring that persistence strategies are explicit and customizable.

⚙️ Transactions

The transactional subsystem provides ACID guarantees for in-memory and file-backed data structures:

• Transactional Scopes: ITransactionalScope defines a protocol for commit/rollback operations. Context-aware scopes allow nested transactions and isolation.
• Transactional Collections: TransactionalList<T>, TransactionalDictionary<TKey, TValue>, and TransactionalHashSet<T> provide ACID semantics over persistent storage.
• Transactional Streams: TransactionalStream wraps a stream with commit/rollback capabilities, enabling atomic multi-operation updates.
• File Transactions: FileTransaction and FileTransactionScope coordinate file-system operations within a transactional boundary.

These primitives enable building robust, crash-recoverable data stores without relying on external database engines.

💾 Caching

The caching subsystem offers flexible, policy-driven caching mechanisms:

• Action Caches: Populate cache entries on-demand using delegates.
• Bulk-Fetch Caches: Refresh all entries in a single operation when any entry becomes stale.
• Session Caches: Expire entries based on last-access time, suitable for session-style semantics.
• Reaping Policies: Both isolated and pooled reaper implementations manage capacity constraints across single or multiple cache instances.

📡 Protocol and Communication

The protocol subsystem facilitates structured, bidirectional communication between peers:

• Protocol Definition: Define protocols with typed messages, commands, requests, responses, and handshakes.
• Orchestration: ProtocolOrchestrator manages message dispatch, handshake workflows, and request/response correlation.
• Extensibility: Handlers for commands, requests, responses, and handshakes can be implemented via interfaces or delegates.

This framework is suitable for building custom RPC mechanisms, control protocols, or peer-to-peer communication layers.

📲 Streams and I/O

Sphere10 Framework extends .NET's stream abstractions with specialized implementations:

• Bounded Streams: Restrict read/write operations to a defined segment of an underlying stream.
• Fragmented Streams: Compose multiple disparate byte fragments into a single logical stream.
• Extended Memory Streams: Use IBuffer as the backing store instead of a contiguous byte array, enabling arbitrarily large in-memory streams with paging support.
• Transactional Streams: Wrap streams with commit/rollback semantics.
• Decorator Streams: Read-only, write-only, non-closing, and profiling stream wrappers.

📝 Logging

A flexible, composable logging framework:

• Logger Abstractions: ILogger defines a simple, level-based logging interface.
• Decorators: Prefix, timestamp, thread-ID, and synchronization decorators compose to customize log output.
• Sinks: Built-in loggers for console, debug output, files, and custom delegates.
• Multicast Logging: Route log messages to multiple sinks simultaneously.

🔄 Threading and Concurrency

Utilities for managing concurrency and synchronization:

• Custom Synchronization Primitives: ProducerConsumerLock, NonReentrantLock, FastLock, and minimal semaphore implementations.
• Serial Thread Pool: Execute actions serially on a background thread, with configurable lifecycle policies.
• Critical Sections: Critical<T> and CriticalObject encapsulate objects with lock-based access.
• Producer-Consumer Queue: ProducerConsumerQueue<T> provides bounded/unbounded thread-safe queuing with async support.

⏰ Scheduling

A job scheduling framework with support for various triggers:

• Job Definitions: Wrap actions or async functions as jobs.
• Schedules: Interval-based, day-of-week, and day-of-month schedules trigger job execution.
• Policies: Control job behavior on failure, completion, and rescheduling.

:pencil2: Text Extensions & String Utilities

Comprehensive string manipulation and validation helpers:

• Case Conversion: Convert between camelCase, PascalCase, snake_case, kebab-case, and UPPERCASE_SNAKE_CASE.
• Truncation & Padding: Pad strings to exact lengths or truncate with ellipsis.
• Validation: Check for numeric, alphabetic, alphanumeric, hexadecimal, and custom patterns.
• Parsing: Safe parsing with tuple results, parse integers, GUIDs, decimals, and custom types.
• Whitespace Operations: Split on whitespace, trim variants, normalize line endings.
• String Replacement: Pattern-based and regex replacements with proper escaping.

🔤 Encoding Utilities

Efficient, space-optimizing encoding schemes:

• Variable-Length Integer Encoding (VarInt): Compress small integers into fewer bytes, with sign-aware variants.
• Compact Variable-Length (CVarInt): Further optimize encoding for extremely small or sparse datasets.
• Binary Encoding: Efficient methods for encoding multiple values into contiguous buffers.
• Bidirectional Encoding: Reversible encoding schemes that preserve ordering properties for indexed storage.

🧠 Memory Management

Utilities for controlling and optimizing memory usage:

• Buffer Abstractions: IBuffer represents a sequence of bytes that can be memory-resident or memory-mapped.
• Memory Pools: Reusable memory pools to reduce allocation pressure in high-throughput scenarios.
• Buffer Decorators: Add synchronization, capacity tracking, or transaction support to buffers.
• Byte Array Utilities: Comparison, concatenation, and transformation helpers for byte arrays.

🔍 Object Mapping & Transformation

Map and transform objects between representations:

• Property Mapping: Copy values between objects with matching or custom property mappings.
• Conversion Chains: Compose multiple converters to transform between unrelated types.
• Specialized Mappers: Collections, dictionary, and array mapping with configurable merge strategies.

🎲 Type Conversion & Parsing

Flexible conversion utilities for type coercion:

• Bidirectional Conversion: Convert between any two types using registered converters.
• Numeric Conversions: Safe conversions between integer types with overflow checking.
• Enum Conversions: String to/from enum with case-insensitive options.
• Collection Conversions: Convert between array, list, set, and dictionary representations.
• Custom Converters: Register converters for application-specific types.

📐 Mathematical Utilities

Low-level math helpers and calculations:

• Bit Manipulation: Bit-counting, set/clear operations, endian conversions.
• GCD and LCM: Greatest common divisor and least common multiple calculations.
• Prime Number Operations: Primality testing and prime enumeration.
• Modular Arithmetic: Modular exponentiation and inversion.
• Rounding: Floor, ceiling, and banker's rounding for financial calculations.

📅 Value Types & Structures

Utilities for working with value types and immutable structures:

• Date/Time Wrappers: Normalized date/time representations for storage.
• Numeric Types: Custom numeric wrappers for specialized domains (e.g., hash values, checksums).
• Struct Utilities: Struct cloning, comparison, and hashing helpers.

🏗️ Comparison & Equality

Build custom comparison and equality implementations:

• Comparer Factories: Create IComparer<T> instances with fluent composition (field-by-field, descending, custom).
• Equality Comparers: Implement IEqualityComparer<T> for custom equality logic.
• Structural Comparison: Compare complex objects field-by-field with customizable rules.
• Tolerance-Based Comparison: Compare floating-point values with configurable epsilon.

🔎 Introspection & Reflection

Reflection utilities and type analysis:

• Type Discovery: Find derived types, implementations of interfaces, and generic arguments.
• Property/Field Analysis: Discover properties, fields, and their attributes with caching.
• Method Resolution: Find methods by name, signature, and attributes.
• Attribute Retrieval: Efficiently retrieve custom attributes from types, methods, and properties.
• Generic Type Analysis: Decompose and analyze generic type definitions and arguments.

📦 Type Utilities

Helpers for type checks and resolution:

• Type Verification: Check if a type is numeric, nullable, enumerable, etc.
• Type Classification: Categorize types (value, reference, generic, etc.).
• Type Conversion Checks: Verify if one type can be converted to another.
• Default Value Generation: Create default instances for arbitrary types.

🏷️ Attributes & Metadata

Custom attributes for annotating types and members:

• Serialization Attributes: Mark fields/properties for serialization with options.
• Validation Attributes: Declarative validation rules (required, length, range).
• Mapping Attributes: Customize property mapping behavior.
• Custom Attributes: Base classes for creating domain-specific attributes.

📋 Framework Abstractions

Core abstractions for building extensible frameworks:

• Loadable: Abstract base for objects with load/reload semantics.
• Persistable: Abstract base for objects that need to save/restore state.
• Saveable: Simplified save pattern for simpler scenarios.
• Disposables: Helpers for implementing safe disposal patterns.
• Environment: Abstract environment information (OS, runtime, configuration).

🔌 Extension Methods on Core Types

Fluent extensions for .NET types:

• Enumerable Extensions: Batch, Chunk, Distinct, GroupBy variants with custom comparers.
• Dictionary Extensions: TryAdd, AddOrUpdate, GetOrAdd with custom logic.
• Task Extensions: Timeout, retry, async coordination helpers.
• Functional Extensions: Map, FlatMap, Filter for more expressive LINQ alternatives.

🌍 Data Source Abstractions

Abstractions for querying data from various sources:

• IDataSource: Generic interface for querying objects from a source (database, file, API).
• Caching Data Sources: Wrap data sources with caching layers.
• Composed Data Sources: Combine multiple sources with fallback semantics.
• Filtering Data Sources: Add filtering and projection to any data source.

🔌 Peripherals & Hardware Access

Utilities for hardware and peripheral interaction:

• Device Detection: Discover and enumerate hardware peripherals.
• Serial Communication: Serial port abstractions for embedded systems.
• GPIO Abstractions: General-purpose I/O operations (where applicable).

🌐 Network Utilities

Low-level network helpers:

• Address Resolution: DNS and IP address utilities.
• Port Scanning: Network connectivity testing.
• Socket Wrappers: Extended socket abstractions with timeout support.

🎯 Environment & System Information

Query system and runtime information:

• Runtime Detection: Detect .NET version, platform, architecture.
• Resource Availability: Check available memory, processor count, disk space.
• Configuration: Access environment variables, system settings.
• Process Information: Query process details, threading, memory usage.

⚙️ Miscellaneous Utilities

Catch-all category for specialized helpers:

• Range Calculations: Compute overlaps, unions, and intersections of value ranges.
• Enum Utilities: Enum iteration, flag manipulation, parsing.
• Bitfield Helpers: Work with bitfields and bit arrays.
• Weak References: Managed weak reference pools to track objects without preventing GC.

📦 Object Utilities

Helpers for object manipulation and introspection:

• Cloning: Deep and shallow cloning with customizable strategies.
• Comparison: Object equality and comparison without reflection overhead (when possible).
• Hashing: Consistent hashing for distributed scenarios.

🎛️ Filtering Abstractions

Generic filtering framework:

• Predicates: Composable IFilter<T> implementations for filtering collections.
• Composite Filters: Combine filters with AND, OR, and NOT logic.
• Range Filters: Filter by numeric or comparable ranges.

📊 Functional Programming Utilities

Support for functional programming patterns:

• Monads: Maybe/Option and Result types for error handling.
• Function Composition: Compose functions with automatic currying.
• Lazy Evaluation: Lazy sequences and deferred computation.
• Partial Application: Bind arguments to create specialized functions.

♻️ Disposable Pattern Helpers

Simplify implementing proper disposal:

• Base Classes: DisposableBase and DisposableObject handle disposal protocol.
• Safe Finalization: Finalization helpers to ensure cleanup occurs.
• Resource Guards: RAII-style resource management patterns.

🔗 Event Handling Utilities

Framework for event routing and aggregation:

• Event Aggregators: Pub/sub patterns for decoupled event routing.
• Event Priorities: Route events in priority order.
• Event Filtering: Conditionally route events based on predicates.

⚠️ Exception Handling

Utilities for robust error handling:

• Exception Wrapping: Preserve stack traces while wrapping exceptions.
• Retry Policies: Exponential backoff, jitter, and custom retry strategies.
• Exception Aggregation: Collect multiple exceptions and report together.
• Error Context: Attach context information to exceptions for debugging.

📖 Loadable Resources

Framework for loading and caching resources:

• Resource Loaders: Abstract protocol for loading resources (files, embedded, remote).
• Caching Loaders: Cache loaded resources with expiration policies.
• Lazy Loading: Load resources on-demand with automatic caching.

📝 Logging Framework

Already covered above in detail.

💾 Persistable Objects

Framework for objects that maintain persistent state:

• State Snapshots: Capture object state for persistence.
• Transactional Persistence: Integrate with transactional scopes.
• Version Tracking: Track object versions across saves.

🔧 Save/Load Patterns

Simplified persistence for straightforward scenarios:

• Serialization Delegates: Custom load/save functions per type.
• Stream-Based Saving: Write objects to streams with format flexibility.
• File-Based Persistence: High-level API for file-based saves.

📏 Sizing Utilities

Calculate sizes and offsets:

• Byte Size Calculation: Determine how many bytes a serialized object requires.
• Alignment Calculation: Compute aligned offsets for memory layout optimization.
• Capacity Planning: Estimate total storage needed for collections.

🎯 Span & Memory Utilities

Efficient working with Span<T> and Memory<T>:

• Span Slicing: Safe slicing with bounds checking.
• Memory Pooling: Rent and return Memory<T> from pools.
• Span Conversion: Convert between Span, Memory, and arrays safely.

📝 TextWriter Abstractions

Extensions and helpers for TextWriter:

• Formatted Output: Structured output writers (JSON, XML, CSV).
• Indented Writers: Automatic indentation for hierarchical data.
• Buffered Writers: Batch write operations for efficiency.

:hammer_and_wrench: Extensions & Utilities

50+ Extension Methods covering:

• StringExtensions: Truncation, case handling, validation, parsing, formatting
• EnumerableExtensions: Filtering, grouping, transformation, batching
• TaskExtensions: Async utilities, timeout handling, retry logic
• StreamExtensions: I/O operations, reading/writing helpers
• TypeExtensions: Reflection helpers, type resolution
• And many more...

💡 Key Concepts

Extended Lists

IExtendedList<T> extends the standard IList<T> interface with range-based operations: ReadRange, UpdateRange, InsertRange, and RemoveRange. These methods accept long indices and counts, supporting collections larger than 2GB. Implementations are expected to optimize batch operations rather than iterating element-by-element.

Stream-Mapped Collections

Stream-mapped collections persist their data to streams using serializers and cluster-based storage. They behave like standard collections but their contents reside on disk (or any stream) rather than entirely in memory. This enables collections to scale beyond available RAM while maintaining familiar APIs.

Object Streams

ObjectStream<T> is a low-level primitive for storing a sequence of serialized objects in a stream, along with metadata and indexes. It underpins stream-mapped collections and object spaces, providing features like:

• Recyclable item slots (deleted items can be reused)
• Pluggable indexes for fast lookups
• Merkle-tree integration for integrity proofs
• Metadata tracking (timestamps, checksums, etc.)

Serialization Context

SerializationContext tracks object references and cycles during serialization/deserialization. When a reference-type object is serialized, the context checks if it has been seen before. If so, a reference marker is emitted rather than re-serializing the object. This enables correct handling of cyclic graphs and repeated references.

Transactional Scopes

ITransactionalScope defines a protocol for ACID transactions:

• BeginTransaction(): Start a new transaction.
• CommitTransaction(): Persist changes.
• RollbackTransaction(): Discard changes.

Context-aware scopes (subclasses of ContextScope) track active transactions within the call context, enabling nested transactions and isolation semantics. Transactional collections and streams implement ITransactionalObject to participate in these scopes.

Merkle Coordinates and Proofs

A MerkleCoordinate identifies a node within a merkle tree by its level and index. Merkle proofs are represented as sequences of MerkleNode instances, which can be verified against a root hash to confirm the presence and position of specific leaves. The library's merkle implementations expose methods for generating proofs and verifying them efficiently.

Decorators and Adapters

Many components follow the decorator pattern, allowing behavior to be layered:

• StreamDecorator: Wrap a stream to add logging, profiling, or transaction support.
• ListDecorator<T>: Augment list behavior without reimplementing the entire interface.
• ItemSerializerDecorator<T>: Transform serialization logic (e.g., add null-handling or reference-tracking).

Adapters convert between related interfaces (e.g., IList<T> to IExtendedList<T>) to integrate external code with Sphere10 Framework's abstractions.

🎯 Typical Use Cases

Well-Suited Scenarios

• Embedded Databases: Build lightweight, file-based data stores with ACID transactions, indexing, and querying without a full database engine.
• Blockchain and Distributed Ledgers: Merkle-tree primitives and cryptographic utilities simplify integrity verification and proof generation.
• High-Volume Data Processing: Stream-backed collections and batch-optimized operations enable processing datasets larger than available memory.
• Custom Persistence Layers: Fine-grained control over serialization, storage layout, and transactional semantics.
• Cryptographic Applications: Post-quantum signature schemes and VRF implementations support advanced security requirements.
• Protocol Implementations: Structured communication frameworks for RPC, control protocols, or peer-to-peer messaging.
• LevelDB Integration: Native Windows LevelDB wrapper for high-performance key-value storage.

📊 Less-Suited Scenarios

• Simple CRUD Applications: If standard Entity Framework or Dapper suffice, Sphere10 Framework's low-level primitives may introduce unnecessary complexity.
• Web APIs with Standard ORMs: The library does not integrate with ASP.NET or Entity Framework out-of-the-box.
• UI-Centric Applications: Sphere10 Framework focuses on data structures and persistence, not UI frameworks or bindings.
• Rapid Prototyping: The library's emphasis on explicitness and control trades off against rapid development convenience.

🏗️ Architecture Overview

Sphere10 Framework's architecture is organized into largely independent subsystems that compose through well-defined interfaces:

1. Collections Layer: Extended list and collection interfaces define the foundation. Implementations range from simple in-memory structures to complex stream-mapped and paged variants.

2. Storage Layer: Clustered streams provide the underlying mechanism for multi-stream persistence. Object streams layer serialization, indexing, and metadata on top of clustered streams.

3. Serialization Framework: A registry-based system (SerializerFactory) maps types to serializers. Serializers compose via decorators for features like null-handling, polymorphism, and reference-tracking.

4. Transactional Framework: Transactional scopes coordinate commit/rollback across multiple objects. Collections, streams, and object spaces implement ITransactionalObject to participate.

5. Merkle Trees: Separate implementations provide different tradeoffs. Merkle-aware collections integrate tree maintenance into their mutation operations.

6. Utilities and Extensions: Comparers, operators, logging, threading, and I/O utilities provide cross-cutting functionality without coupling to core abstractions.

Data typically flows from application code through collections or object spaces, which delegate to object streams for persistence. Object streams use clustered streams for storage and serializers for encoding. Transactional scopes coordinate mutations, and merkle trees provide integrity proofs where enabled.

🚀 Getting Started

Installation

NuGet Packages:

# Core library dotnet add package Sphere10 Framework # Platform-specific (optional) dotnet add package Sphere10.Framework.Windows # Windows utilities dotnet add package Sphere10.Framework.Windows.Forms # WinForms integration dotnet add package Sphere10.Framework.Windows.LevelDB # Native LevelDB wrapper dotnet add package Sphere10.Framework.CryptoEx # Extended cryptography (ECDSA, ECIES) dotnet add package Sphere10.Framework.Communications # Networking & protocols dotnet add package Sphere10.Framework.Web.AspNetCore # ASP.NET Core integration

Or reference compiled assemblies directly in your project.

10-Second Example

using Sphere10.Framework; using System.IO; // BinarySerializer: Efficient binary serialization var serializer = new BinarySerializer<string>(); var stream = new MemoryStream(); var context = new SerializationContext(); serializer.Serialize(context, "Hello World", stream); // StreamMappedList: Disk-backed collection (no memory limit) using var fileStream = new FileStream("data.bin", FileMode.Create, FileAccess.ReadWrite); var list = new StreamMappedList<string>(fileStream, new StringSerializer(Encoding.UTF8)); list.Add("Persisted Item 1"); list.Add("Persisted Item 2"); list.Save(); // FlatMerkleTree: Cryptographic proof of integrity var tree = new FlatMerkleTree(CHF.SHA2_256); tree.Leafs.AddRange(Encoding.UTF8.GetBytes("Block 1"), Encoding.UTF8.GetBytes("Block 2")); var root = tree.Root; // Root hash proves all items // Synchronized collections: Thread-safe variants var syncList = new SynchronizedExtendedList<int>(); syncList.Add(42); // Automatically locked during mutation

💻 Core Examples

BinarySerializer: Efficient Binary Serialization

using Sphere10.Framework; using System.IO; // Serialize primitive types var binarySerializer = new BinarySerializer<int>(); var stream = new MemoryStream(); var context = new SerializationContext(); // Write an integer binarySerializer.Serialize(context, 42, stream); // Read it back stream.Position = 0; var value = binarySerializer.Deserialize(context, stream); Console.WriteLine(value); // 42 // For custom objects, use ItemSerializer class Product { public int Id { get; set; } public string Name { get; set; } } var productStream = new MemoryStream(); var prodContext = new SerializationContext(); var productBytes = new Product { Id = 1, Name = "Widget" }; // BinarySerializer compresses data efficiently // Best used with constant-size serializers for indexed access var constSizeSerializer = new BinarySerializer<int>(); var offsets = new List<long>(); for (int i = 0; i < 1000; i++) { offsets.Add(productStream.Position); constSizeSerializer.Serialize(prodContext, i, productStream); } // Now you can seek directly to any index without scanning productStream.Seek(offsets[500], SeekOrigin.Begin);

StreamMappedList: Disk-Backed Collections

using Sphere10.Framework; using System.IO; // Create a collection that persists to disk using var fileStream = new FileStream("inventory.dat", FileMode.Create, FileAccess.ReadWrite); // StreamMappedList supports massive collections (limited only by disk space) var inventory = new StreamMappedList<Product>( fileStream, new CustomProductSerializer(), // Your serializer autoLoad: false ); // Add items (written to disk immediately) inventory.Add(new Product { Id = 1, Name = "Widget", Price = 9.99m }); inventory.Add(new Product { Id = 2, Name = "Gadget", Price = 19.99m }); inventory.Add(new Product { Id = 3, Name = "Doohickey", Price = 14.99m }); // Efficient batch operations inventory.AddRange(new[] { new Product { Id = 4, Name = "Thingamajig", Price = 24.99m }, new Product { Id = 5, Name = "Whatsit", Price = 12.99m } }); // Save index to disk inventory.Save(); // Later, reload from disk (only index is loaded into memory) using var reloadStream = new FileStream("inventory.dat", FileMode.Open, FileAccess.Read); var reloaded = new StreamMappedList<Product>(reloadStream, new CustomProductSerializer(), autoLoad: true); // Access items (loaded from disk as needed) var firstItem = reloaded[0]; // Reads from disk var batch = reloaded.ReadRange(1, 3); // Batch read is more efficient // StreamMappedList with checksums for integrity using var checkedStream = new FileStream("checked.dat", FileMode.Create, FileAccess.ReadWrite); var checkedList = new StreamMappedList<string>( checkedStream, new StringSerializer(Encoding.UTF8), itemChecksummer: new ObjectHashCodeChecksummer<string>(), reservedStreams: 1, policy: ClusteredStreamsPolicy.Default ); checkedList.Add("Important data"); checkedList.Save(); // Checksums verify data wasn't corrupted on disk

StreamPagedList: Memory-Paged Disk Collections

using Sphere10.Framework; using System.IO; // StreamPagedList loads pages into memory as needed (more efficient for sequential access) using var pagedStream = new FileStream("pages.dat", FileMode.Create, FileAccess.ReadWrite); var pagedList = new StreamPagedList<string>( new StringSerializer(Encoding.UTF8), pagedStream, pageSize: 4096 // 4KB pages, tuned for your access patterns ); // Add thousands of items for (int i = 0; i < 100_000; i++) { pagedList.Add($"Item {i}"); } // Sequential access is fast (page already in memory) for (int i = 0; i < 10; i++) { Console.WriteLine(pagedList[i]); } // Random access loads the needed page var item50000 = pagedList[50000]; // For constant-size items, use constant-size serializer for direct indexing var constSizeList = new StreamPagedList<string>( new StringSerializer(Encoding.UTF8).AsConstantSize(50), // Fixed 50-byte strings pagedStream, pageSize: 4096 ); // Now can directly calculate position: position = itemIndex * itemSize // Without scanning through variable-length items

FlatMerkleTree: Cryptographic Integrity Proofs

using Sphere10.Framework; using System.Security.Cryptography; // Create a flat merkle tree (all nodes in memory, optimal for proof generation) var tree = new FlatMerkleTree(CHF.SHA2_256); // Add data (hashed immediately) var data = new[] { Encoding.UTF8.GetBytes("Transaction 1"), Encoding.UTF8.GetBytes("Transaction 2"), Encoding.UTF8.GetBytes("Transaction 3"), Encoding.UTF8.GetBytes("Transaction 4") }; tree.Leafs.AddRange(data); // Get root hash (proof that all items are included) var rootHash = tree.Root; Console.WriteLine($"Root: {Convert.ToHexString(rootHash)}"); // Generate proof for a specific item (prove item 2 is in tree) var proof = tree.GenerateProof(2); // Generates merkle path var leaf = tree.Leafs[2]; // Verify the proof (can be done independently) bool verified = MerkleTreeUtilities.VerifyProof( leaf, proof, rootHash, CHF.SHA2_256 ); // FlatMerkleTree is ideal for: // - Blockchain blocks (fixed number of transactions) // - Smaller merkle trees where full tree fits in memory // - Frequent proof generation // Compare with LongMerkleTree for massive datasets var longTree = new LongMerkleTree(CHF.SHA2_256); // LongMerkleTree only keeps sub-root hashes in memory // Can handle millions of items with minimal memory overhead // But proof generation requires computing intermediate hashes

LongMerkleTree: Memory-Efficient Merkle Trees

using Sphere10.Framework; // LongMerkleTree: For massive datasets (millions of items) // Only stores sub-root hashes, not all nodes var tree = new LongMerkleTree(CHF.SHA2_256); // Append items efficiently for (int i = 0; i < 1_000_000; i++) { var data = Encoding.UTF8.GetBytes($"Item {i}"); tree.Leafs.AddRange(data); } // Root hash proves integrity of all million items var root = tree.Root; // Generate proof for an item var proof = tree.GenerateProof(500_000); // Verify proof (works same as FlatMerkleTree) var leaf = tree.Leafs[500_000]; bool verified = MerkleTreeUtilities.VerifyProof( leaf, proof, root, CHF.SHA2_256 ); // LongMerkleTree advantages: // - O(1) memory for append operations // - Can handle unlimited items // - Perfect for blockchain, event logs, append-only stores // Size information var size = tree.Size; Console.WriteLine($"Leaf count: {size.LeafCount}"); Console.WriteLine($"Tree depth: {size.Depth}");

Synchronized Collections: Thread-Safe Wrappers

using Sphere10.Framework; using System.Collections.Generic; using System.Threading.Tasks; // SynchronizedExtendedList: Thread-safe variant of ExtendedList var syncList = new SynchronizedExtendedList<int>(); // Safe for concurrent access from multiple threads var tasks = new List<Task>(); for (int t = 0; t < 10; t++) { tasks.Add(Task.Run(() => { for (int i = 0; i < 1000; i++) { syncList.Add(i); // Automatically locked } })); } Task.WaitAll(tasks.ToArray()); Console.WriteLine($"Total items: {syncList.Count}"); // 10,000 safely // SynchronizedDictionary: Thread-safe key-value pairs var syncDict = new SynchronizedDictionary<string, Account>(); var producer = Task.Run(() => { for (int i = 0; i < 100; i++) { syncDict[$"account_{i}"] = new Account { Id = i, Balance = 100m }; } }); var consumer = Task.Run(() => { System.Threading.Thread.Sleep(50); // Let producer add some foreach (var key in syncDict.Keys) { var account = syncDict[key]; Console.WriteLine($"{key}: {account.Balance}"); } }); Task.WaitAll(producer, consumer); // SynchronizedRepository: Cached, thread-safe data access var syncRepo = new SynchronizedRepository<int, Product>( loadFunc: id => FetchProductFromDatabase(id) ); // Thread-safe get (with automatic caching) var product1 = syncRepo.Get(1); var product2 = syncRepo.Get(2); // Multiple threads can safely access the cache var readTasks = Enumerable.Range(0, 100) .Select(i => Task.Run(() => syncRepo.Get(i % 10))) .ToArray(); Task.WaitAll(readTasks); // Synchronized collection types available: // - SynchronizedExtendedList<T> // - SynchronizedDictionary<TKey, TValue> // - SynchronizedSet<T> // - SynchronizedQueue<T> // - SynchronizedHeap<T> // All use internal locking for thread safety class Account { public int Id { get; set; } public decimal Balance { get; set; } } class Product { public int Id { get; set; } public string Name { get; set; } public decimal Price { get; set; } } Product FetchProductFromDatabase(int id) { return new Product { Id = id, Name = $"Product {id}", Price = 9.99m }; } class CustomProductSerializer : IItemSerializer<Product> { public void Serialize(ISerializationContext context, Product item, Stream stream) { // Custom serialization logic } public Product Deserialize(ISerializationContext context, Stream stream) { // Custom deserialization logic return new Product(); } }

💾 Persistence & Transactions

Advanced StreamMappedList Usage:

The StreamMappedList shown above demonstrates the core disk-backed storage pattern. For additional persistence options:

• Use itemChecksummer to verify data integrity (detects corruption)
• Use reservedStreams to attach additional metadata streams
• Configure ClusteredStreamsPolicy to control cluster allocation

Transactional Scopes:

// Transactional boundaries for ACID operations var dict = new TransactionalDictionary<string, Account>(); using (var scope = dict.BeginScope()) { using (var txn = scope.BeginTransaction()) { dict["acc1"] = new Account { Balance = 1000 }; dict["acc2"] = new Account { Balance = 500 }; // Auto-rollback if exception occurs txn.Commit(); // Explicit commit for atomicity } } // Transactional dictionary backed by file var persistedDict = new TransactionalDictionary<string, Account>(); using (var scope = persistedDict.BeginScope()) { using (var txn = scope.BeginTransaction()) { persistedDict["acc001"] = new Account { Balance = 1000 }; persistedDict["acc002"] = new Account { Balance = 500 }; txn.Commit(); // Atomic commit to disk } // If exception occurs, automatic rollback } // Verify persistence using (var scope2 = persistedDict.BeginScope()) { using (var txn2 = scope2.BeginTransaction()) { var acc1 = persistedDict["acc001"]; // Data persisted Console.WriteLine(acc1.Balance); // 1000 } }

📦 Advanced Serialization Patterns

The serialization system supports reference-tracked graphs, polymorphic types, and custom decorators. See the Core Examples section above for BinarySerializer patterns. Refer to IItemSerializer<T> interface and SerializerFactory for custom implementations.

Merkle List with Integrity Proofs:

using Sphere10.Framework; using System.Security.Cryptography; // Create a merkle-aware list with SHA-256 var hasher = new HashAlgorithmAdapter(SHA256.Create()); var merkleList = new FlatMerkleList<string>( ItemSerializer.Default<string>(), hasher ); merkleList.Add("Block 1"); merkleList.Add("Block 2"); merkleList.Add("Block 3"); // Get root hash (commitment to entire list) byte[] rootHash = merkleList.MerkleTree.Root; // Generate proof that \"Block 2\" is at index 1 var proof = merkleList.MerkleTree.GenerateProof(1); // Verify proof independently var isValid = merkleList.MerkleTree.VerifyProof( merkleList.GetItemHash(1), 1, proof, rootHash ); Console.WriteLine($"Proof valid: {isValid}"); // true

Merkle Dictionary (Multiple Keys):

var merkleDictionary = new MerkleListAdapter<KeyValuePair<string, int>>( new ExtendedList<KeyValuePair<string, int>>(), hasher ); merkleDictionary.Add(new KeyValuePair<string, int>("Alice", 100)); merkleDictionary.Add(new KeyValuePair<string, int>("Bob", 50)); // Prove integrity of multi-item state var multiProof = merkleDictionary.MerkleTree.GenerateMultiProof(new[] { 0, 1 });

📦 Serialization Examples

Built-in Serializers (Default):

using Sphere10.Framework; // Simple type serialization var intSerializer = ItemSerializer<int>.Default; byte[] bytes = intSerializer.Serialize(42); int restored = intSerializer.Deserialize(bytes); // Supports complex types automatically var listSerializer = ItemSerializer<ExtendedList<string>>.Default; var list = new ExtendedList<string> { "a", "b", "c" }; var serialized = listSerializer.Serialize(list); var deserialized = listSerializer.Deserialize(serialized);

Custom Serializer Factory with Type Registration:

var factory = new SerializerFactory(); // Register primitives with specific strategies factory.Register( typeof(string), new StringSerializer(SizeDescriptorStrategy.UseVarInt) ); // Register custom type factory.Register( typeof(MyObject), new MyObjectSerializer(factory) ); // Retrieve and use var serializer = factory.GetSerializer(typeof(MyObject)); var data = serializer.Serialize(myObj);

Polymorphic Serialization (Inheritance Support):

// Animal is abstract; Dog and Cat inherit from it // Mark subtypes with [KnownSubType] [KnownSubType(typeof(Dog))] [KnownSubType(typeof(Cat))] public abstract class Animal { /* ... */ } // Default serializer automatically handles polymorphism var animalSerializer = ItemSerializer<Animal>.Default; var animals = new ExtendedList<Animal> { new Dog("Fido"), new Cat("Mittens") }; byte[] bytes = animalSerializer.Serialize(animals); var restored = animalSerializer.Deserialize(bytes); Console.WriteLine(restored[0].GetType()); // Dog ✓ Console.WriteLine(restored[1].GetType()); // Cat ✓

Reference-Tracked Serialization (Graph Preservation):

// When serializing object graphs with repeated references // or cycles, use reference serializers to preserve identity class Node { public string Value { get; set; } public Node Next { get; set; } } var factory = new SerializerFactory(); var refSerializer = new NodeSerializer().AsReferenceSerializer(); factory.Register(typeof(Node), refSerializer); // Circular linked list: A -> B -> A var a = new Node { Value = "A" }; var b = new Node { Value = "B", Next = a }; a.Next = b; byte[] data = refSerializer.Serialize(a); var restored = refSerializer.Deserialize(data); // Identity preserved: restored.Next.Next == restored ✓

Compact Integer Encoding (VarInt/CVarInt):

using Sphere10.Framework; // VarInt: Variable-length signed integers (more compact for small numbers) using (var ms = new MemoryStream()) { VarInt.Write(ms, 300); ms.Position = 0; int v = VarInt.Read(ms); // 300 // 300 encoded as 3 bytes instead of 4 } // CVarInt: Compact unsigned, extreme compression for typical ranges var bytes = CVarInt.ToBytes(10000); // Few bytes only var value = CVarInt.From(bytes); // Typical usage in custom serializers class CompactSerializer : ItemSerializerBase<int> { public override void Serialize(ISerializationContext context, int item) { CVarInt.Write(context.Writer, (ulong)item); } public override int Deserialize(IDeserializationContext context) { return (int)CVarInt.Read(context.Reader); } }

Cryptographic Hashing:

using Sphere10.Framework; var data = "Hello, World!"; // Standard hash functions byte[] sha256 = Tools.Hashing.SHA256(data); byte[] sha512 = Tools.Hashing.SHA512(data); byte[] blake2b = Tools.Hashing.BLAKE2b(data); byte[] murmurhash = Tools.Hashing.MurmurHash3(data); // Hash files byte[] fileHash = Tools.Hashing.SHA256File("path/to/file.bin"); // Compute multiple simultaneously var hashes = Tools.Hashing.ComputeMultipleHashes(data, CHF.SHA2_256, CHF.SHA3_256); // Hash files byte[] fileHash = Tools.Hashing.SHA256File("path/to/file.bin"); // Compute multiple simultaneously var hashes = Tools.Hashing.ComputeMultipleHashes(data, CHF.SHA2_256, CHF.SHA3_256);

📝 String Extensions (50+ helpers)

using Sphere10.Framework; var text = "Hello World"; // Formatting & validation var padded = text.PadToLength(20); // Pad or truncate to exact length var truncated = text.Truncate(5); // Truncate with ellipsis bool isEmpty = text.IsNullOrEmpty(); bool isWhitespace = " ".IsNullOrWhiteSpace(); // Type checking bool isNumeric = "12345".IsNumeric(); bool isAlpha = "abc".IsAlpha(); bool isAlphaNumeric = "abc123".IsAlphaNumeric(); bool isHex = "DEADBEEF".IsHex(); // Case conversion var camelCase = "hello_world".ToCamelCase(); // helloWorld var pascalCase = "hello_world".ToPascalCase(); // HelloWorld var snakeCase = "HelloWorld".ToSnakeCase(); // hello_world // Parsing & extraction var (success, number) = "42".TryParseInt(); var guid = "550e8400-e29b-41d4-a716-446655440000".TryParseGuid(); var words = "The quick brown fox".SplitOnWhitespace(); // Splitting & joining var lines = "line1\nline2\nline3".ToLines(); var csv = new[] { "a", "b", "c" }.JoinWith(", ");

LevelDB Integration (High-Performance Key-Value Store):

using Sphere10.Framework.Windows.LevelDB; // Open database using var db = new DB("./mydata"); // Basic operations var key = Encoding.UTF8.GetBytes("user:42"); var value = Encoding.UTF8.GetBytes(JsonSerializer.Serialize(user)); db.Put(key, value); var retrieved = db.Get(key); if (retrieved != null) { var restored = JsonSerializer.Deserialize<User>(Encoding.UTF8.GetString(retrieved)); } // Batch operations (atomic) using (var batch = db.CreateBatch()) { for (int i = 0; i < 1000; i++) { batch.Put(Encoding.UTF8.GetBytes($"key:{i}"), Encoding.UTF8.GetBytes($"value:{i}")); } db.Write(batch); } // Iteration & range queries using (var iterator = db.CreateIterator()) { iterator.SeekToFirst(); while (iterator.IsValid()) { var k = Encoding.UTF8.GetString(iterator.Key()); var v = Encoding.UTF8.GetString(iterator.Value()); Console.WriteLine($"{k} = {v}"); iterator.Next(); } }

🔧 Extensibility & Customization

The library's design encourages extending core abstractions rather than modifying built-in types. Here are the main extension points:

Custom Serializers

Implement IItemSerializer<T> (or inherit ItemSerializerBase<T>) to define custom serialization logic:

public class UserSerializer : ItemSerializerBase<User> { private readonly IItemSerializer<string> _stringSerializer; private readonly IItemSerializer<int> _intSerializer; public UserSerializer(SerializerFactory factory) { _stringSerializer = factory.GetSerializer<string>(); _intSerializer = factory.GetSerializer<int>(); } public override void Serialize(ISerializationContext context, User user) { _stringSerializer.Serialize(context, user.Name); _intSerializer.Serialize(context, user.Age); } public override User Deserialize(IDeserializationContext context) { var name = _stringSerializer.Deserialize(context); var age = _intSerializer.Deserialize(context); return new User { Name = name, Age = age }; } } // Register and use var factory = new SerializerFactory(); factory.Register(typeof(User), new UserSerializer(factory)); var serialized = factory.GetSerializer<User>().Serialize(user);

Serializer Decorators

Wrap serializers to add cross-cutting concerns (null-handling, encryption, compression, etc.):

// Add null-substitution var baseSerializer = ItemSerializer<int>.Default; var nullableSerializer = new WithNullSubstitutionSerializer<int>( baseSerializer, defaultValue: -1 // Use -1 when null ); // Chain decorators var encrypted = new EncryptedSerializer<MyType>(nullableSerializer, encryptionKey); var compressed = new CompressedSerializer<MyType>(encrypted);

Custom Indexes on Object Streams

Implement IProjectionIndex<TItem, TKey> to add custom indexing strategies:

public class LastNameIndex : ProjectionIndexBase<Person, string> { public LastNameIndex(ObjectStream<Person> objectStream) : base(objectStream) { } public override string ProjectKey(Person item) => item.LastName; protected override void OnIndexAdded(Person item, long index) { // Store index mapping } public override long? TryGetIndex(string lastName) { // Lookup by last name return _indexStore.TryGetValue(lastName, out var idx) ? idx : null; } } // Attach to ObjectStream var objectStream = new ObjectStream<Person>(clusteredStreams, serializer); var index = new LastNameIndex(objectStream); objectStream.RegisterIndex(index); // Query via index var personIndex = index.TryGetIndex("Smith"); var person = objectStream[personIndex.Value];

Custom Transactional Scopes

Subclass TransactionalScopeBase to implement custom transaction semantics:

public class FileBackedTransactionalScope : TransactionalScopeBase { private readonly FileStream _logFile; private List<Operation> _operations = new(); protected override void OnBeginTransaction() { _operations.Clear(); // Write transaction start marker to log } protected override void OnCommitTransaction() { // Flush all operations to file atomically _logFile.Write(Encoding.UTF8.GetBytes("[COMMIT]")); _logFile.Flush(); } protected override void OnRollbackTransaction() { _operations.Clear(); // Discard pending operations } } // Use in transactional collections var dict = new TransactionalDictionary<string, int>(); using (var scope = new FileBackedTransactionalScope()) { using (var txn = scope.BeginTransaction()) { dict["key"] = 42; txn.Commit(); } }

Extending Collections

Decorate existing collections to add custom behavior:

// Add logging to list operations public class LoggingList<T> : ExtendedListDecorator<T> { private readonly ILogger _logger; public LoggingList(IExtendedList<T> inner, ILogger logger) : base(inner) { _logger = logger; } public override void Add(T item) { _logger.Info($"Adding {item}"); base.Add(item); } public override void InsertRange(long index, T[] items) { _logger.Info($"Inserting {items.Length} items at {index}"); base.InsertRange(index, items); } } // Use transparently var baseList = new ExtendedList<int>(); IExtendedList<int> logged = new LoggingList<int>(baseList, logger); logged.Add(42); // "Adding 42" logged

⚠️ Threading / Performance / Safety Notes

Thread Safety

• Most collections are NOT thread-safe by default. Use SynchronizedList<T>, SynchronizedDictionary<TKey, TValue>, SynchronizedExtendedList<T>, or wrap with ConcurrentStream where concurrent access is required.
• Transactional scopes are single-threaded. Transactions are isolated per call context; concurrent transactions require separate scope instances.
• Caches: Thread-safety depends on implementation. SynchronizedRepository<T> and SynchronizedLogger provide synchronized wrappers.
• ProducerConsumerQueue: Fully thread-safe for concurrent producers and consumers.

Performance Considerations

• Range Operations: Prefer ReadRange, UpdateRange, and InsertRange over element-by-element operations for large datasets.
• Paging Configuration: Tune page sizes and in-memory page counts for memory-paged and file-paged collections based on access patterns.
• Serialization: Constant-size serializers enable efficient random access. Variable-size serializers require sequential scans.
• Merkle Trees: Flat merkle trees optimize for proof generation but consume O(n log n) memory. Long merkle trees trade memory for computation.
• ClusteredStreams: Default cluster size is 4KB; adjust based on typical object sizes and access patterns.

Safety Constraints

• Stream Position Management: Many components assume exclusive control over stream position. Concurrent stream access without synchronization is unsafe.
• Serialization Context: Contexts are NOT thread-safe. Use separate contexts per thread or synchronize access.
• Disposal: Disposable resources (streams, transactions, scopes) must be disposed to release locks and persist changes. Use using statements.

✅ Status & Maturity

Sphere10 Framework is a mature library that has evolved over multiple years. Core subsystems (collections, serialization, transactions, merkle trees) are stable and production-tested. Some components (post-quantum cryptography, protocol orchestration) may be less battle-tested and should be evaluated carefully for production use.

Compatibility

• Target Framework: .NET 8.0+ (primary), with support for .NET Standard 2.0 where applicable
• Backward Compatibility: The library does not guarantee API stability across major versions. Serialization formats may evolve, requiring migration strategies for persistent data.
• Platform Support: Windows, Linux, macOS, iOS (via Xamarin/MAUI), Android (via Xamarin/MAUI)

🧪 Experimental Components

• Post-quantum signature schemes (W-OTS, AMS) are reference implementations. Audit and validate before use in production cryptographic systems.
• Some advanced merkle-tree variants and indexing strategies are optimized for specific use cases and may have edge-case limitations.

📦 Platform-Specific Packages

• Sphere10.Framework.Windows - Windows-specific utilities
• Sphere10.Framework.Windows.Forms - WinForms integration
• Sphere10.Framework.Windows.LevelDB - Native LevelDB wrapper
• Sphere10.Framework.Application - Cross-platform application framework
• Sphere10.Framework.Communications - Networking and protocol layers
• Sphere10.Framework.Web.AspNetCore - ASP.NET Core integration
• Sphere10.Framework.CryptoEx - Extended cryptography (ECDSA, ECIES, etc.)

Dependencies

• .NET 8.0 or higher (primary target)
• No external dependencies for core functionality
• Optional: BouncyCastle for advanced cryptography
• Optional: Newtonsoft.Json for JSON support
• Optional: Microsoft.Extensions.DependencyInjection for DI integration

⚖️ License

Distributed under the MIT NON-AI License.

This license encourages ethical AI development and prevents use in certain AI/ML contexts without explicit permission. See the LICENSE file for full details.

More information: Sphere10 NON-AI-MIT License

📖 Resources

• GitHub: Herman Schoenfeld
• Website: sphere10.com

👤 Author

Herman Schoenfeld - Software Engineer