| Crates.io | apex-sdk |
| lib.rs | apex-sdk |
| version | 0.1.5 |
| created_at | 2025-11-15 09:09:59.305046+00 |
| updated_at | 2026-01-13 19:51:21.209506+00 |
| description | Compile-time safe, unified Rust SDK for cross-chain blockchain development across Substrate and EVM ecosystems |
| homepage | https://apexsdk.dev/ |
| repository | https://github.com/carbobit/apex-sdk |
| max_upload_size | |
| id | 1934172 |
| size | 323,842 |
Build secure, multichain blockchain applications with compile-time safety
Apex SDK Protocol is a compile-time safe, unified Rust SDK that enables developers to build multichain applications spanning Substrate and EVM ecosystems. With a single, intuitive API, reduce development complexity while ensuring type safety and native performance across Polkadot, Kusama, Ethereum, and more.
Get started with Apex SDK in under 5 mins:
# Install Apex SDK CLI
cargo install apex-sdk-cli
# Create a new multi-chain project
apex new my-multi-chain-app
# Navigate to project directory
cd my-multi-chain-app
# Build and test
cargo build
cargo test
# Add to your Cargo.toml
[dependencies]
apex-sdk = "0.1.0"
apex-sdk-substrate = "0.1.0"
apex-sdk-evm = "0.1.0"
# Clone the repository
git clone https://github.com/carbobit/apex-sdk.git
cd apex-sdk
# Build from source
cargo build --release
# Run tests
cargo test --all-features
# Install locally
cargo install --path ./cli
Apex SDK includes comprehensive testing infrastructure with unit tests, integration tests, and Docker-based testing against local blockchain nodes.
# Run all unit tests
cargo test
# Run with all features
cargo test --all-features
# Run doc tests
cargo test --doc
Test against actual blockchain nodes running in Docker containers:
# Start test nodes (Hardhat + Substrate)
./docker/scripts/start-nodes.sh
# Run EVM integration tests
INTEGRATION_TESTS=1 cargo test --test evm_integration_test -- --include-ignored
# Run Substrate integration tests
INTEGRATION_TESTS=1 cargo test --test substrate_integration_test -- --include-ignored
# Stop test nodes
./docker/scripts/stop-nodes.sh
See docker/README.md for detailed documentation on the Docker integration test infrastructure.
| Chain | Type | Status | Features |
|---|---|---|---|
| Polkadot | Substrate | Stable | Full support |
| Kusama | Substrate | Stable | Full support |
| Ethereum | EVM | Stable | Full support |
| BSC | EVM | Stable | Full support |
| Polygon | EVM | Stable | Full support |
| Avalanche | EVM | Stable | Full support |
| Moonbeam | Hybrid | Stable | Substrate + EVM |
| Astar | Hybrid | Stable | Substrate + EVM |
Complete Documentation Hub - Your one-stop guide
| Resource | Description |
|---|---|
| Quick Start | Get started in 5 minutes |
| API Reference | Complete API documentation |
| CLI Guide | Command-line tools guide |
| Roadmap | Development roadmap & priorities |
| Security | Security policies & reporting |
Quick access via dedicated subdomains:
See DOMAINS.md for the complete domain structure.
Check out the examples/ directory for complete working examples:
evm-transfer/ - Execute actual ETH transfers on testnet with wallet signingevm-contract-call/ - Type-safe ERC-20 contract interactions using Alloyaccount-manager/ - Multi-chain account managementprice-oracle/ - Multi-chain price aggregationcontract-orchestration/ - Smart contract deploymentparachain-assets/ - Parachain asset managementWe welcome contributions! See CONTRIBUTING.md for guidelines
Quick Start:
git clone https://github.com/carbobit/apex-sdk.git
cd apex-sdk
cargo test --all-features
Setup Git Hooks (Recommended):
Install pre-commit hooks to catch CI failures before pushing:
./scripts/install-git-hooks.sh
This will automatically run format checks, clippy lints, and builds before each commit.
To bypass (use sparingly): git commit --no-verify
Report vulnerabilities: security@apexsdk.dev
Security Policy | Security Profiles | Security Audit
Apex SDK includes multiple security-hardened build profiles:
# Production build with maximum security
cargo build --profile release-secure
# Standard production build
cargo build --release
# See SECURITY_PROFILES.md for detailed information