Java Connector
  • Java Connector
  • Concepts
    • Feature Summary
    • Terminology
    • Account Model
    • Packet Switching Fabric
    • Exchange Rates
    • Routing Table Design
    • Destination Address Handling
    • Balance Tracking
    • Settlement
  • Connector Configuration
  • Connector Configuration Properties
  • Persistence Initialization
  • Local STREAM Packet Termination
  • Connector Operation
  • Running with Docker
  • Peering: ILP-over-HTTP
  • Settlement: XRP Ledger
  • Running on GCP
  • Security Guide
    • Connector Crypto
    • test-jwt.io
    • Generating Keys
    • Spring Boot with TLS
  • API References
    • Admin API
  • Tutorials
    • ILP TestNet: Getting Started
  • Contributing
    • Connector Development
    • Project Testing
  • Releases
    • Changelog
Powered by GitBook
On this page
  • Feature request?
  • Overview
  • Disclaimer

Was this helpful?

Java Connector

A Java implementation of an Interledger Connector supporting ILPv4.

This site contains documentation for the Java implementation of an Interledger Connector.

Github project source code: https://github.com/interledger4j/ilpv4-connector Docs source code: https://github.com/interledger4j/java-ilpv4-connector-docs Documentation Website: https://connector.interledger4j.dev/

Feature request?

Have an idea or a feature request for the ILP Connector? We'd love to hear about it! Submit your ideas/requests/etc on feedback.interledger4j.dev.

Overview

This implementation is a high-performance Interledger Connector that supports many incoming and outgoing connections that are tied together by an ILPv4 packet-switching fabric.

This implementation supports the following features:

  • ILPv4: Interledger Protocol version for as defined in IL-RFC-27.

  • ILDCP: Interledger Dynamic Configuration Protocol as specified in IL-RFC-31.

  • ILP-over-HTTP: Allows for sending and receiving ILPv4 packets over HTTP as defined in IL-RFC-30.

  • Route Broadcast Protocol: Defines how Connectors can exchange routing table updates as defined in Route Broadcast Protocol.

  • Balance Tracking: Durably tracks account balance updates in a high-performance manner using Redis.

  • Persistent Data Storage: Account and other data can be stored using Postgres, MySQL, Oracle, MSSQL, and more.

To learn more about how this implementation is designed, see Connector Design.

To contribute to this project read more in Connector Development.

Disclaimer

WARNING: This implementation is currently an "alpha" prototype and SHOULD NOT be used in a production deployment!

NextFeature Summary

Last updated 4 years ago

Was this helpful?