GATEWAY PROVIDERS
Connect Kronex to infrastructure beyond Kronex.
Gateways provide bridges between the Kronex marketplace and external infrastructure.
01 · WHAT THIS PROVIDER DOES
What this provider does
Connects Kronex orders with external infrastructure.
02 · WHAT ORDERS IT RECEIVES
What orders it receives
A Gateway Provider may:
- 01accept Kronex orders
- 02translate them into external protocols
- 03route workloads
- 04monitor execution
- 05measure delivery
- 06return results
- 07generate execution receipts
03 · REQUIREMENTSSpecification pending
Requirements
Indicative until specified. These are the categories a gateway provider is expected to satisfy, not the values it must meet.
- Protocols
- Which external protocols a gateway can translate an order into.
- Delivery measurement
- How a routed request is shown to have been delivered.
- Availability
- The uptime a gateway commits to for the requests it accepts.
- Collateral
- What is staked against the delivery a gateway accepts.
Requirements will be published with the provider framework.
04 · HOW IT IS PAID
How it is paid
Gateway fees are one of the protocol's fee sources. A provider is paid a fee on the requests it routes and returns, settled against verified request delivery.
05 · HOW IT IS MEASURED
How it is measured
- verified request delivery
- uptime
- response time
- dispute history
- collateral
Applications can automatically choose providers according to their own requirements.
06 · RISKS AND OBLIGATIONSSpecification pending
Risks and obligations
A gateway stands between a Kronex order and infrastructure Kronex does not control. It commits collateral against the delivery it accepts, and remains answerable for the request even where the failure occurred outside the network. A provider that fails to deliver is exposed to economic penalties where appropriate.
The penalty mechanism is not designed.
- answerable for the routed request
- collateral at stake
- penalties where appropriate
07 · ROADMAP DEPENDENCY
Roadmap dependency
Phase 6
Gateway Networkplanned
allow Kronex to coordinate infrastructure across multiple networks and protocols
- decentralized gateways
- external protocol adapters
- execution routing
- provider verification
- gateway reputation
Gateways allow Kronex to coordinate resources without requiring every external protocol to become part of Kronex consensus.
Related