Connect things in flexible ways using a simple config system edit this diagram

Routes have sets of inputs and outputs, and may optionally perform some processing on or with their inputs. The config defines the initial inputs to the system and the connections between routes.

Middleware is a type of route that performs some processing. An Endpoint is a type of middleware that connects to external resources.

• simple acyclical routing and example middleware - just process data.
• route manager for loops and stuff - process data persistently.
• config parser that talks to route manager - make it easy to process data.
• implement jsonrpc endpoints for parity-ethereum - make it easy to process ethereum.
• some non-trivial interaction between two nodes.
• do everything parity-bridge currently does.
• parse parts of configs provided directly by endpoints - make it meta.
• offload middleware tasks to other software using endpoints - everything is pluggable.

• Port parity-bridge to simple middleware; port it's jsonrpc client logic to simple endpoints.
• Implement endpoints for substrate chains; implement a substrate module that works with parity-bridge middleware.
• Implement a substrate-ethereum bridge.
• Do crazy things this isn't designed for.