Contents Menu Expand Light mode Dark mode Auto light/dark mode
CCF documentation
  • Overview
    • What is CCF?
    • Governance
    • Performance
    • Frequently Asked Questions
    • Maintenance
    • Glossary
  • Build Apps
    • Quick Start
    • Install CCF
    • C++ Application
      • Example app (C++)
      • Example app RPC API
    • TypeScript Application
    • JavaScript Application Bundle
    • Logging
    • Build and Sign CCF Applications
    • Running CCF Applications
    • User Authentication
      • JWT Authentication
      • Certificate Authentication
    • Key-Value Store
      • Key-Value Store How-To
      • Key-Value Serialisation
      • Key-Value Store API
    • Developer API
    • Cryptography API
    • Release and compatibility policy
  • Use Apps
    • Issuing Commands
    • Verifying Transactions
    • Verifying Quote
    • RPC API
  • Operations
    • Setup CCF Runtime Environment
    • Running a CCF Service
    • Configuration
    • Ledger and Snapshots
    • Code Upgrade
    • Certificates
    • Disaster Recovery
    • Data Persistence
    • Networking
    • Platforms
      • Intel SGX
      • AMD SEV-SNP
      • Insecure Virtual
    • Troubleshooting CCF
    • Resource Usage
    • Operator RPC API
  • Governance
    • Constitution
    • Proposing and Voting for a Proposal
    • JavaScript Runtime Options
    • Opening a Network
    • Accepting Recovery and Submitting Shares
    • Common Governance Operations
    • Adding New Members
    • Using Member Keys Stored in HSM
    • Member RPC API
  • Audit
    • Receipts
    • Built-in Maps
    • Python Library
    • Read-Write Permissions On KV Maps
  • Contribute
    • Onboarding
    • Create Azure SGX VM
    • CCF Development Setup
    • Build CCF from Source
    • Release or patch a CCF release
    • CCF Build Images
  • Architecture
    • Consensus Protocols
      • One-transaction Reconfiguration
      • Two-transaction Reconfiguration
    • Cryptography
    • Request Flow
    • Threading
    • Merkle Tree
    • Ledger
    • TLA+ Specification
    • Node-to-Node Channels
    • Indexing
    • Receipts
    • TLS Internals
    • TCP Internals
    • QUIC Internals
    • Piccolo
      • Generator
      • Submitter
      • Analyzer
  • Research
Back to top

Key-Value Store#

The key-value store represents the internal state of the network. It is used by applications to store data to and read from the ledger.

  • Key-Value Store How-To
    • Map Naming
    • Transaction Semantics
    • Accessing Map content via a Handle
    • Read/Write safety
    • Removing a key
    • Global commit
    • Miscellaneous
      • foreach()
      • Applying and reverting writes
  • Key-Value Serialisation
    • Custom key and value types
  • Key-Value Store API
    • Map
    • Transaction
    • Handles
    • Serialisation
Next
Key-Value Store How-To
Previous
Certificate Authentication
Copyright © 2018, Microsoft Research
Made with Sphinx and @pradyunsg's Furo