Jump to content

Monero

  • entries
    225
  • comment
    1
  • views
    24377

Bitcoin <-> Monero atomic swaps are now live


Snider

174 views

We are happy to announce that the Atomic Swap implementation developed by the COMIT team is mature enough to be used on Monero's network. For now, makers must buy Bitcoin and takers must buy Monero, but anyone can be a maker or taker. It is easier at the moment to sell Bitcoin for Monero than the other way around. To try a swap yourself, download the asb software developed by the COMIT team, follow the instructions and let them know if you find any issues (works also over Tor!). Remember this is brand new technology and might have unexpected bugs. Be careful and only test with small amounts. To find swap providers, visit unstoppableswap.net.

What are Atomic Swaps?

Atomic swaps are a way to exchange two cryptocurrencies (in our case Monero and Bitcoin) without relying on a trusted third party (like a cryptocurrency exchange company) and without needing to trust the person on the other side of the swap. These swaps are called "atomic" because they only have two possible outcomes: either the trade is successfully completed and each trader receives the other one's funds, or nothing happens and both traders keep the funds they started with. Since the protocol forces both parties to follow the rules, it is not possible to run away with the other party's coins, which is the main reason trusted third parties are required when exchanging cryptocurrencies.

Two teams are working on developing Atomic Swaps for Monero:

View the full article

0 Comments


Recommended Comments

There are no comments to display.

Guest
Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      426.56 GH
    • Avg Hashrate
      178.78 MH
    • Total Miners
      2386
    • Miners Paid
      48447
    • Total Payments
      1416103
    • Total Hashes
      9.23 EX
    • Blocks Found
      2719468
  • Posts

    • Buenos dias, no se me abre pool monero,des de hace dias. Me comenta al abrir k puede haver cambiado de pagina.alguien sabe algo
    • How can I tell HiveOS how many cores or threads I want to use for mining? My Ryzen 3600 has been lowered to 55w. In order to avoid clogging GPUs, I only want to use 11 threads for mining, with 1 thread for system-specific purposes. fnf
    • ./xmrig --url pool.hashvault.pro:80 --user *** --pass x -a cn-heavy/xhv * ABOUT XMRig/6.17.0 gcc/9.3.0 * LIBS libuv/1.43.0 OpenSSL/1.1.1m hwloc/2.7.0 * HUGE PAGES supported * 1GB PAGES disabled * CPU AMD EPYC-Rome Processor (1) 64-bit AES VM L2:0.5 MB L3:16.0 MB 1C/1T NUMA:1 * MEMORY 0.6/1.9 GB (31%) DIMM 0: 2 GB RAM @ 0 MHz DIMM 0 * MOTHERBOARD Vultr - VHP * DONATE 1% * ASSEMBLY auto:ryzen * POOL #1 pool.hashvault.pro:80 algo cn-heavy/xhv * COMMANDS hashrate, pause, resume, results, connection [2022-05-22 12:49:13.205] net use pool pool.hashvault.pro:80 131.153.76.130 [2022-05-22 12:49:13.205] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (7 tx) [2022-05-22 12:49:13.205] cpu use argon2 implementation AVX2 [2022-05-22 12:49:13.207] msr cannot read MSR 0xc0011020 [2022-05-22 12:49:13.207] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW [2022-05-22 12:49:13.207] randomx init dataset algo rx/0 (1 threads) seed 6ac097ea635e9d1d... [2022-05-22 12:49:13.207] randomx not enough memory for RandomX dataset [2022-05-22 12:49:13.235] randomx failed to allocate RandomX dataset, switching to slow mode (27 ms) [2022-05-22 12:49:13.517] randomx dataset ready (282 ms) [2022-05-22 12:49:13.517] cpu use profile rx (1 thread) scratchpad 2048 KB [2022-05-22 12:49:13.519] cpu READY threads 1/1 (1) huge pages 100% 1/1 memory 2048 KB (1 ms) [2022-05-22 12:49:17.487] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (52 tx) [2022-05-22 12:49:20.337] signal Ctrl+C received, exiting [2022-05-22 12:49:20.345] cpu stopped (8 ms I run xmrig and set the algorithm `cn-heavy/xhv`, but it still response `rx/0`.How to solve this problem?
    • Yes, I like the content of this article.  LOL Beans
    • Yeah, it does, but apparently it's not so transparent. So if we > mention that we'd better indicate in the same paragraph that you > probably don't actually want to use it. How about the attached?  UNO Online
×
×
  • Create New...