opendex.network
opendex.network copied to clipboard
opendexnetwork
Website 👋
The OpenDEX protocol still has JSON [in various places](https://opendex.network/read/02-peer-protocol#sessioninit-message-0-x00), which is bad because JSON can't be guaranteed to always be UTF-8 conform and requires implementations to use e.g. https://www.npmjs.com/package/json-stable-stringify in...
Moved here from https://github.com/ExchangeUnion/xud/issues/881: Problem description: Read [this](https://coinjournal.net/flaw-discovered-in-lightning-networks-cross-chain-functionality/) or watch [this](https://youtu.be/AmFC9dhtemo?t=3093), [this](https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-December/001752.html) for the full mailing list version. **TL,DR**: the preimage holder (in our case always the taker) can delay...
From the original issue: https://github.com/ExchangeUnion/xud/issues/1219 Current status: > Lightning’s protocol as a model for xud: > The Lightning code implementation (in Go) is clear and has some anti-abuse features. Like...
Problem: Currently we are only supporting [order invalidation (0x07)](https://opendex.network/read/03-trade-protocol#orderinvalidation-message-0-x07) and re-issuing a [new order (0x06)](https://opendex.network/read/03-trade-protocol#order-message-0-x06) which is not ideal and somewhat error prone since implementations need to take care of...
The order id is nominally a UUID but since the originator of the order can make it up, this id can't be trusted to be unique. As long as there...
Since buy of BTC/LTC is precisely the same as a sell of LTC/BTC, the protocol allows for two ways to express the same intent, which gives rise to potential bugs...
There is a PR describing something very similar: https://github.com/opendexnetwork/opendex/pulls
For now we have following situation: 1. Alice has buy 1 BTC/LTC 10 order in order book 2. Alice node know nothing about Bob's node 3. Bob has sell 1...
