-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Taker Sends >B pays the dex fee so that A will start the process by locking his coins.2) Maker Successfully Sends >A picks randomNumber: `secret_A`A creates a utxo on the Bitcoin blockchain with value: 1 BTC encumbrance: the value can be claimed by A after 20 hours or by B if he knows the secret `secret_A`3) Taker Successfully Sends After seeing the above utxo, B creates the following utxo on the KMD blockchain: value: 100 KMD encumbrance: the value can be claimed by B after 10 hours or by A if he knows the secret `secret_A`4) Maker Spends A uses the `secret_A` and claims the KMD, thereby revealing the secret5) Taker Spends B now uses the public `secret_A` to claim the BTCThe times can be adjusted based on requirements of security and "ease of use" Normally, A should have a longer locktime so that B can have sufficient time to get his coins back if A doesn't reveal the secret `secret_A`for eth, CLTV and other bitcoin specific OP\_CODES are replaced by a smart contract, whose code is here: [https://github.com/artemii235/etomic-swap](https://github.com/artemii235/etomic-swap))the cross-platform implementation of the protocol is here: [https://github.com/KomodoPlatform/atomicDEX-API/](https://github.com/KomodoPlatform/atomicDEX-API/))Its [android GUI is in beta and can be tested right now](https://play.google.com/store/apps/details?id=com.komodoplatform.atomicdex&hl=en), iOS version is in [testflight](https://testflight.apple.com/join/c2mOLEoC)You can read about the Komodo team's implementation of the protocol [here](https://developers.komodoplatform.com/basic-docs/start-here/core-technology-discussions/atomicdex.html#introducing-taker-and-maker) and instructions to use the DEX through the CLI [here](https://developers.atomicdex.io)The atomicDEX application needs access to privkeys currently, but they never leave your device. We are also planning Hardware wallet support in the 0.6.0 release. This should alleviate most concerns with privkey access.
Taker Sends >B pays the dex fee so that A will start the process by locking his coins.2) Maker Successfully Sends >A picks randomNumber: `secret_A`A creates a utxo on the Bitcoin blockchain with value: 1 BTC encumbrance: the value can be claimed by A after 20 hours or by B if he knows the secret `secret_A`3) Taker Successfully Sends After seeing the above utxo, B creates the following utxo on the KMD blockchain: value: 100 KMD encumbrance: the value can be claimed by B after 10 hours or by A if he knows the secret `secret_A`4) Maker Spends A uses the `secret_A` and claims the KMD, thereby revealing the secret5) Taker Spends B now uses the public `secret_A` to claim the BTCThe times can be adjusted based on requirements of security and "ease of use" Normally, A should have a longer locktime so that B can have sufficient time to get his coins back if A doesn't reveal the secret `secret_A`for eth, CLTV and other bitcoin specific OP\_CODES are replaced by a smart contract, whose code is here: [https://github.com/artemii235/etomic-swap](https://github.com/artemii235/etomic-swap))the cross-platform implementation of the protocol is here: [https://github.com/KomodoPlatform/atomicDEX-API/](https://github.com/KomodoPlatform/atomicDEX-API/))Its [android GUI is in beta and can be tested right now](https://play.google.com/store/apps/details?id=com.komodoplatform.atomicdex&hl=en), iOS version is in [testflight](https://testflight.apple.com/join/c2mOLEoC)You can read about the Komodo team's implementation of the protocol [here](https://developers.komodoplatform.com/basic-docs/start-here/core-technology-discussions/atomicdex.html#introducing-taker-and-maker) and instructions to use the DEX through the CLI [here](https://developers.atomicdex.io)The atomicDEX application needs access to privkeys currently, but they never leave your device. We are also planning Hardware wallet support in the 0.6.0 release. This should alleviate most concerns with privkey access.