COMIT's XMR-BTC swap project is currently unmaintained!
Help welcome! If you love the XMR-BTC swap tool, have some Rust knowledge and are willing to step up please reach out for becoming a maintainer. It'd be great if community members could step in to keep this project alive. Unfortunately, we currently don't have the capacity.
Bringing XMR-BTC swaps to the community is one of the most rewarding projects we have been working on. In this blogpost we summarize where we started, what the latest release has to offer and what is planned for the future!
Why you want it, why it doesn't work on present day1 Monero and what that means for applications on top.
Here's another post on one of our favourite privacy coins. This time we will take a look at the technical details of Monero transactions. Most of you will know that Monero transactions are confidential in terms of amounts and ownership of outputs, but here we'll explain what makes this work.
Our mission is to connect all the blockchains, without adding yet another one. Our vision is that we believe in a censorship-resistant & non-discriminating open financial market for everyone.
Bitcoin is the major player in the decentralised financial ecosystem but has a traceability issue, stopping it to be truly censorship-resistant & non-discriminating. Monero is a privacy focused coin, it is fungible and non-traceable and the most used privacy coin [1].
These characteristics make XMR-BTC cross-blockchain applications a great candidate to push towards our vision.
Over half a year ago we proved that Grin-Bitcoin atomic swaps were possible and now we're back to show you how it can be done for the monero-bitcoin pair. In our effort to connect all the blockchains without adding yet another, we have turned our attentions to Monero. Similar to Grin, Monero is a public ledger in which the source, destination and amount of a transaction remain hidden to observers.
The team has been interested in Monero for a long time, but until recently we assumed that atomic swaps involving it were unfeasible due to its lack of support for timelocks.
