All articles
Index
This is some text inside of a div block.
This is some text inside of a div block.

Akave Cloud: August 2025 Product & Protocol Updates

July and August marked another step forward in making decentralized storage enterprise-ready. We shipped deep upgrades across Akave O3 (S3 API), the protocol layer (akavenode + SDK), and smart contracts. Tightening security and compliance, increasing throughput, and smoothing operator workflows. Below, we break down everything that’s new, enhanced, and future-proofed across recent versions.
Angelo Schalley
September 5, 2025

About Akave O3

Akave O3 is the S3-compatible object storage API that runs on top of our decentralized data layer. It delivers three pillars our customers rely on: security, performance, and extensibility; without egress or request taxes and with verifiable, audit-friendly primitives.

‍

Security You Can Trust

  • Object Lock, Retention & Legal Hold (since O3 v0.5.3)
    • Governance/Compliance modes with retention enforcement.
    • Legal Hold APIs supported (Put/GetObjectLegalHold).
    • ACL/Policy maps extended to respect retention/hold operations.

  • Versioning you can reason about (since O3 v1.1.0)
    • Bucket versioning is always enabled for consistent behavior across read/write paths.
    • Version IDs are now read from URI parameters in ACL/Tagging/Retention/LegalHold handlers for predictable routing.
    • Versioning management APIs intentionally return UnsupportedOperation for clarity and safety.

  • Stricter request validation (since O3 v1.1.0)
    • Hardened byte-range validation (empty/invalid ranges rejected).
    • Improved presigned URL verification and signature handling (O3 v0.5.3).

  • Contract-level safety upgrades (Smart Contracts v0.0.6–v0.0.8)
    • Signature security fixes and cleaner access pathways.
    • Pagination and bool flags in search/view functions reduce edge-case ambiguity during reads.

‍

Performance & Stability

  • Zero-copy & parallel I/O (since O3 v1.0.0)
    • Gorilla Mux + refactored HTTP stack, splice-based zero-copy transfers, and ReadAt/WriteAt parallelism.
    • Buffer subsystem overhauled with larger tuned sizes and atomic tracking.

  • Lower-overhead file path (since O3 v1.1.0)
    • Truncate support, tighter open flags, and leaner checksum/read paths.
    • Cleaner resource cleanup and safer deferred operations.

  • Throughput wins in the protocol (since v0.2.0 → v0.3.0)
    • Single connection pool per upload in the SDK, not per chunk.
    • Upload/download pipelines made more granular; resume uploads supported.
    • Batch retrieval and indexed on-chain events reduce node → to → chain chatter during hot paths.

  • Caching where it matters
    • LRU caches on upload endpoints (protocol) and Ristretto caching for policy/ACL/bucket/object metadata (O3 v1.0.0).
    • Conditional “mustCached” code paths to keep latency predictable under load (O3 v1.1.0).

‍

Enterprise-Ready Features

  • S3 SelectObjectContent for CSV (since O3 v0.5.3)
    • SQL-like engine with streaming responses (50 MB limit), proper quoting, and expression support.

  • Lifecycle & Replication APIs (since O3 v1.0.0)
    • Config surfaces for lifecycle management and replication policies with test coverage.

  • Snowflake Iceberg compatibility (since O3 v0.5.3)
    • ETag formatting fixes, non-zero timestamps, idempotent DELETE, and MPU checksum correctness for external tables.

  • Pagination everywhere
    • IPC bucket pagination wired into O3 sync loops (since v1.1.0).
    • Smart contracts & protocol add pagination to files/buckets list methods (since SmartContracts v0.0.7–v0.0.8 and Protocol v0.3.0).

  • Operator ergonomics
    • CLI wallet balance (Protocol v0.3.0).
    • gRPC TLS for akavenode API with libp2p identity (Protocol v0.3.0).
    • Repositories, cache, and middleware refactors cut boilerplate and improve traceability.

‍

Protocol Layer Upgrades

Verified Data & Chain-Aware Uploads

We continue to push data verifiability and predictable onchain semantics:

  • Indexed storage events (create/commit/delete file) on akavenode with contract-query fallback for not-yet-indexed blocks.
  • Batch methods for chunk addition and block filling on the storage contract reduce round-trips during heavy uploads.
  • DAG size semantics clarified: chunk “size” = sum of encoded blocks (protobuf overhead excluded).

Node Block Repair & Resilience

  • Node repair command (since Protocol v0.2.0) reconstructs missing erasure-coded blocks using known metadata.
  • Transaction loop improvements (batch receipt queries, custom nonce/gas strategies) keep uploads flowing under chain variability.

Smarter Metadata & Back-Compat

  • Erasure code schema embedded in file metadata (Streaming API), decoupling download schema from SDK configuration.
  • SDK can download legacy EC format data and keeps actual size aligned with input length.

‍

Release Recap for O3 (July / August)

  • v0.5.3 , July 14
    • Snowflake Iceberg compatibility improvements
    • Object Lock, Retention, Legal Hold
    • SelectObjectContent (CSV), tracing (OTLP), Prometheus metrics
    • MPU buffer/checksum refactors; idempotent flows; better startup sequencing

  • v1.0.0 , August
    • Move from Gin → Gorilla Mux framework
    • Zero-copy transfer; parallel I/O; cache unification (Ristretto)
    • Policy/ACL caching, lifecycle & replication APIs
    • Checksum logic consolidated; reduced DB round-trips

  • v1.1.0 , August 28
    • Versioning always on; standardized UnsupportedOperation for versioning APIs
    • VersionId parsed from URI params
    • IPC pagination integrated into sync; stricter byte-range validation
    • File/Checksum pipeline refinements; safer cleanup

‍

Release Recap for Protocol (July / August)

  • v0.2.0 , July 3
    • Faster download (fewer contract calls) and upload (granular pipeline, pre-create chunks)
    • Node repair tooling; EC metadata on Streaming API
    • Resume uploads and SDK retries for bucket/file/chunk txs
  • v0.2.1 , July 25
    • Nonce handling fixes; dummy-tx hash correction; better pending-tx tooling

  • v0.3.0 , August
    • Pagination for buckets/files (contracts, SDK, akavenode)
    • Owner argument added to read queries; updated retrieval methods and event names
    • Upgradable proxy pattern for storage contract; batch chunk/block methods
    • LRU caches on hot endpoints; single connection pool per upload
    • gRPC TLS for akavenode; block-range checkpoints in indexer

‍

Release Recap for SmartContracts (July / August)

  • v0.0.6 , July 1 (Pre-release)
    • Signature security fixes; deployment script updates
    • PeerBlock entity removed; timestamp adjustments for ids
    • Storage SC usability improvements

  • v0.0.7 , July 24
    • Bool indicator for search functions
    • Pagination added to bucket view functions
    • Access Manager condition added for getValidateAccessToBucket

  • v0.0.8 , Latest
    • Pagination for files in view functions for consistent paging across layers

‍

Dev-Ops & Infra Team Updates(July / August)

  • Security posture: Emergency patch for a third-party library shipped across all environments; CI/CD now includes enhanced scanning.
  • Data & analytics: Redesigned dashboards rolled out with ~30% performance gains; mid-sprint tuning addressed range/edge cases.
  • Database scale: Phase-1 sharding completed; Phase-2 optimization queued for September.
  • Process: Bi-weekly FE/BE integration syncs added; documentation standards tightened and API docs refreshed.
  • Engineering hygiene: 20% capacity reserved for tech debt each sprint; detailed code reviews on critical components.

Quick Snippets

Check wallet balance (new CLI subcommand):

akavecli wallet balance --address <0xYourAddress>

‍

Use S3 Select on CSV (example):

aws s3api select-object-content \
  --bucket your-bucket \
  --key data.csv \
  --expression "SELECT s.* FROM s3object s WHERE s.amount > 1000" \
  --expression-type SQL \
  --input-serialization '{"CSV": {"FileHeaderInfo": "USE"}, "CompressionType":"NONE"}' \
  --output-serialization '{"CSV": {}}' \
  out.json

‍

Enable TLS on akavenode gRPC API (self-signed via libp2p identity):

akavenode start \
  --grpc.tls.enable \
  --grpc.addr 0.0.0.0:8443

‍

Coming Soon

We’re working on a hostable O3 option for a planned release at the end of Q4 (self-host the S3 API that speaks to Akave’s subnet), plus additional SDK ergonomics and admin tooling for smoother ops.

We invite partners, customers, and builders to integrate the latest releases and tell us what you want next.

Connect with Us

Akave Cloud is an enterprise-grade, distributed and scalable object storage designed for large-scale datasets in AI, analytics, and enterprise pipelines. It offers S3 object compatibility, cryptographic verifiability, immutable audit trails, and SDKs for agentic agents; all with zero egress fees and no vendor lock-in saving up to 80% on storage costs vs. hyperscalers.

Akave Cloud works with a wide ecosystem of partners operating hundreds of petabytes of capacity, enabling deployments across multiple countries and powering sovereign data infrastructure. The stack is also pre-qualified with key enterprise apps such as Snowflake and others. 

Get Started

Modern Infra. Verifiable By Design

Whether you're scaling your AI infrastructure, handling sensitive records, or modernizing your cloud stack, Akave Cloud is ready to plug in. It feels familiar, but works fundamentally better.
Get Started