Understand the project
Practical overview
When it fits
Use it when evaluating or setting up a Go-based matching-engine component for an exchange that matches orders off-chain and uses signed trade data for smart-contract settlement.
Who it is for
- Developers building or studying hybrid decentralized exchange backends.
- Teams evaluating an off-chain order-book component with documented token, pair and trade-data routes.
Documented uses
- Maintain token and trading-pair records for an exchange.
- Retrieve a pair's order book, an address's orders or balances, and trade history or OHLCV data.
- Represent signed orders and matched trades for a workflow that can proceed to an on-chain transaction.
Before you choose
Requirements & limits
The public GitHub repository identifies the project as MIT-licensed.
- The documented server prerequisites are MongoDB 3.6+, RabbitMQ 3.7.7+, Redis 4.0+ and dep.
- Only the exchange operator can register quote tokens; anyone can register a pair when its quote token is registered.
- The README says maker and taker fees are not implemented.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Source-based practical guide
Set up and start the matching-engine server
Install the documented dependencies and start the Go server.
Before you start
- MongoDB 3.6 or newer
- RabbitMQ 3.7.7 or newer
- Redis 4.0 or newer
- dep
Steps
Install dependencies with
dep ensure.Start the server with the command below.
go run server.go
Expected outcome
The README's documented server-start procedure has been followed.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- ProofSuite/amp-matching-engine · Official homepage title · retained in its source language