Service APIs

These services comprise a backbone of core services for peer-to-peer applications to use.

• CADET
• CORE
  • The CORE Client-Service Protocol
    • Setup2
    • Notifications
    • Sending
  • The CORE Peer-to-Peer Protocol
    • Creating the EphemeralKeyMessage
    • Establishing a connection
    • Encryption and Decryption
    • Type maps
• CONG
  • Key exchange
    • Next Steps
    • Handshake Protocol (Current)
    • Handshake Protocol (Draft)
  • Unified Address Format for L2O and libp2p
  • Peer IDs
    • Reasoning
      • Attacker Model
    • Implications
      • DHT
      • Scope of Peer ID for higher Layers
      • Reconnects
      • Messenger
    • Details on how
    • Open questions
    • Ownership of Peer IDs
    • Implications
      • Transport
      • Other
    • Details on how
  • libp2p Underlay
  • Protocol-Versioning
  • Open Design Questions
    • Peer ID changes and connectivity
    • Peer ID Terminology
  • Requirements
  • Use Cases and Scenarios
    • Peer ID
    • GNS
    • CADET
    • Messenger
• DHT
  • The API of libgnunetblock
  • Queries
  • Sample Code
  • Conclusion2
  • GET
  • PUT
  • MONITOR
  • DHT Routing Options
    • The DHT Client-Service Protocol
  • PUTting data into the DHT
  • GETting data from the DHT
  • Monitoring the DHT
    • The DHT Peer-to-Peer Protocol
  • Routing GETs or PUTs
  • PUTting data into the DHT
  • GETting data from the DHT
• FS
  • Namespace Advertisements
  • KSBlocks
    • File-sharing persistence directory structure
• GNS
  • Looking up records
  • Accessing the records
  • Creating records
  • Future work
    • libgnunetgnsrecord
  • Value handling
  • Type handling
    • GNS plugins
    • The GNS Client-Service Protocol
    • Hijacking the DNS-Traffic using gnunet-service-dns
  • Network Setup Details
    • Importing DNS Zones into GNS
  • Conversions between DNS and GNS
  • DNS Zone Size
  • Performance
• IDENTITY
  • Connecting to the service
  • Operations on Egos
  • The anonymous Ego
  • Convenience API to lookup a single ego
  • Associating egos with service functions
    • The IDENTITY Client-Service Protocol
• MESSENGER
  • Messages
    • NAME-message
    • INVITE-message
    • TEXT-message
    • FILE-message
    • DELETE-message
    • TICKET-message
    • TAG-message
    • SUBSCRIBE-message
    • TALK-message
  • Member sessions
• NAMECACHE
  • The NAMECACHE Client-Service Protocol
    • Lookup
    • Store
  • The NAMECACHE Plugin API
    • Lookup2
    • Store2
• NAMESTORE
  • Editing Zone Information
  • Transactional operations
  • Iterating Zone Information
  • Monitoring Zone Information
• NSE
  • Results
  • Examples
    • The NSE Client-Service Protocol
    • The NSE Peer-to-Peer Protocol
• PEERSTORE
  • libgnunetpeerstore
• REST
  • Namespace considerations
  • Endpoint documentation
• REVOCATION
  • Querying for revoked keys
  • Preparing revocations
  • Issuing revocations
    • The REVOCATION Client-Service Protocol
    • The REVOCATION Peer-to-Peer Protocol
• Peer-to-Peer Set Operations
  • SET
    • Sets
    • Listeners
    • Operations
    • Supplying a Set
    • The Result Callback
      • The SET Client-Service Protocol
    • Creating Sets
    • Listeners
    • Initiating Operations
    • Modifying Sets
    • Results and Operation Status
    • Iterating Sets
      • The SET Intersection Peer-to-Peer Protocol
    • The Bloom filter exchange
    • Salt
      • The SET Union Peer-to-Peer Protocol
  • SETI
    • Intersection Set API
    • Intersection Listeners
    • Intersection Operations
    • Supplying a Set for Intersection
    • The Intersection Result Callback
      • The SETI Client-Service Protocol
    • Creating Intersection Sets
    • Listeners for Intersection
    • Initiating Intersection Operations
    • Modifying Intersection Sets
    • Intersection Results and Operation Status
      • The SETI Intersection Peer-to-Peer Protocol
    • The Bloom filter exchange in SETI
    • Intersection Salt
  • SETU
    • Union Set API
    • Union Listeners
    • Union Operations
    • Supplying a Set for Union
    • The Union Result Callback
      • The SETU Client-Service Protocol
    • Creating Union Sets
    • Listeners for Union
    • Initiating Union Operations
    • Modifying Union Sets
    • Union Results and Operation Status
    • The SETU Union Peer-to-Peer Protocol
• STATISTICS
  • Statistics retrieval
  • Setting statistics and updating them
  • Watches
    • The STATISTICS Client-Service Protocol
  • Statistics retrieval
  • Setting and updating statistics
  • Watching for updates
• TRANSPORT
  • Address validation protocol
  • NAT library
  • Distance-Vector plugin
  • SMTP plugin
  • Why use SMTP for a peer-to-peer transport?
  • How does it work?
  • How do I configure my peer?
  • How do I test if it works?
  • How fast is it?
  • Bluetooth plugin
  • What do I need to use the Bluetooth plugin transport?
  • How does it work2?
  • What possible errors should I be aware of?
  • How do I configure my peer2?
  • How can I test it?
  • The implementation of the Bluetooth transport plugin
    • Linux functionality
    • THE INITIALIZATION
    • THE LOOP
    • Details about the broadcast implementation
    • Pending features
  • WLAN plugin