Closed kilrau closed 4 years ago
Idea for architecture: daemon listening to xud subscribeorders
on machine -> EventSource HTTP stream -> frontend listening to stream
We could do some light research if we can use grpc-web to subscribeorders
directly in the future. At the moment this would also require that we have read-only macaroons because we wouldn't want the client being able to access other gRPC calls.
For now subscribeorders
-> wrapper service -> client/frontend would be the easiest to implement.
We could do some light research if we can use grpc-web to subscribeorders directly in the future.
Something for you? @hatmer
Something reusable from the exchange orderbook UI you built a while ago? @reliveyy
Something reusable from the exchange orderbook UI you built a while ago?
@kilrau I'd like to give is a try in watchdog container which combines my previous created reactjs app in the later PRs in xud-docker repo.
macaroons can be JSON serialized and grpc-web allows for custom headers, so Karl's idea would work
@reliveyy you could use JSON-serialized macaroons from reactjs too
I like https://github.com/ExchangeUnion/xud/issues/1495#issuecomment-618246954.
Interested in taking the xud "backend" part of this one? @hatmer @reliveyy can provide a simple orderbook frontend he already cooked a while ago I think :)
Yes sure, it will go nicely with the macaroons project
EDITed issue as per discussion with @reliveyy . Moved to @reliveyy , bumped prio to P1.
Step 1:
xud
's webproxy endpointStep 2:
What is the goal? An easy display into the OpenDEX network, a way to show the public what's going on on the network by clicking on a link, e.g. ob.kilrau.com will host the orderbook of my mainnet node.
What is not the goal? A performanet web UI to control xud, a trade UI. It is display only.