๐—•๐—ถ๐˜๐—ฐ๐—ผ๐—ถ๐—ป ๐˜๐—ผ ๐˜๐—ต๐—ฒโ€ฆ๐— ๐—ฒ๐—ฟ๐—ฐ๐˜‚๐—ฟ๐˜†?

๐˜ ๐˜ฐ๐˜ถ๐˜ณ ๐˜จ๐˜ถ๐˜ช๐˜ฅ๐˜ฆ ๐˜ต๐˜ฐ ๐˜ต๐˜ฉ๐˜ช๐˜ด ๐˜ช๐˜ฏ๐˜ฏ๐˜ฐ๐˜ท๐˜ข๐˜ต๐˜ช๐˜ท๐˜ฆ ๐˜ญ๐˜ข๐˜บ๐˜ฆ๐˜ณ 2 ๐˜ฑ๐˜ณ๐˜ฐ๐˜ต๐˜ฐ๐˜ค๐˜ฐ๐˜ญ

A new scaling and privacy layer for #Bitcoin has been released: ๐— ๐—ฒ๐—ฟ๐—ฐ๐˜‚๐—ฟ๐˜† ๐—Ÿ๐—ฎ๐˜†๐—ฒ๐—ฟ

Hereโ€™s what you should know about it๐Ÿ‘‡

The Mercury Layer is a relatively new system designed to streamline Bitcoin transactions, making them faster and more cost-effective. Functioning as a 'second layer' over Bitcoin's base layer, it offers a way to transfer bitcoin ๐˜ธ๐˜ช๐˜ต๐˜ฉ๐˜ฐ๐˜ถ๐˜ต ๐˜ต๐˜ฉ๐˜ฆ ๐˜ถ๐˜ด๐˜ถ๐˜ข๐˜ญ ๐˜ค๐˜ฐ๐˜ฏ๐˜ง๐˜ช๐˜ณ๐˜ฎ๐˜ข๐˜ต๐˜ช๐˜ฐ๐˜ฏ ๐˜ต๐˜ช๐˜ฎ๐˜ฆ๐˜ด ๐˜ฐ๐˜ณ ๐˜ง๐˜ฆ๐˜ฆ๐˜ด, much like other layer 2 protocols like Lightning, Liquid, and ARK.

When you transact in Bitcoin, you're essentially exchanging digital units of bitcoin called UTXOs (Unspent Transaction Outputs). Think of a UTXO as a digital version of cash, except it can be any amount, and not limited to 1s, 5s, 10s, etc. ๐—ง๐—ต๐—ฒ ๐— ๐—ฒ๐—ฟ๐—ฐ๐˜‚๐—ฟ๐˜† ๐—Ÿ๐—ฎ๐˜†๐—ฒ๐—ฟ ๐—ฒ๐—ป๐—ฎ๐—ฏ๐—น๐—ฒ๐˜€ ๐˜†๐—ผ๐˜‚ ๐˜๐—ผ ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ณ๐—ฒ๐—ฟ ๐˜๐—ต๐—ฒ๐˜€๐—ฒ ๐—จ๐—ง๐—ซ๐—ข๐˜€ ๐—ฑ๐—ถ๐—ฟ๐—ฒ๐—ฐ๐˜๐—น๐˜†, akin to handing cash to a friend, without recording every transaction on Bitcoin's timechain.

What makes Mercury stand out is its method for changing ownership of UTXOs. It cleverly uses divided parts of a digital key, akin to a shared secret. This key is essential for a user to prove their ownership of the UTXO. By altering parts of this key, ๐˜†๐—ผ๐˜‚ ๐—ฐ๐—ฎ๐—ป ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ณ๐—ฒ๐—ฟ ๐—ผ๐˜„๐—ป๐—ฒ๐—ฟ๐˜€๐—ต๐—ถ๐—ฝ ๐˜€๐—บ๐—ผ๐—ผ๐˜๐—ต๐—น๐˜†, avoiding the need to broadcast the transaction to the world.

Mercury also incorporates backup transactions as a safety net. These act like emergency measures, allowing you to reclaim your Bitcoin, ๐—ฒ๐˜ƒ๐—ฒ๐—ป ๐—ถ๐—ณ ๐˜๐—ต๐—ฒ ๐—ฆ๐˜๐—ฎ๐˜๐—ฒ๐—ฐ๐—ต๐—ฎ๐—ถ๐—ป ๐—˜๐—ป๐˜๐—ถ๐˜๐˜†, ๐—ผ๐—ฟ ๐—ฆ๐—˜, ๐—ฑ๐—ผ๐—ฒ๐˜€ ๐—ป๐—ผ๐˜ ๐—ฐ๐—ผ๐—ผ๐—ฝ๐—ฒ๐—ฟ๐—ฎ๐˜๐—ฒ. This system ensures that only the current owner can use these backup measures, thereby preventing any fraudulent claims to your bitcoin.

The process of using Mercury begins with an on-chain transaction of sending your UTXO to an address where ๐˜ฃ๐˜ฐ๐˜ต๐˜ฉ ๐˜บ๐˜ฐ๐˜ถ ๐˜ข๐˜ฏ๐˜ฅ ๐˜ต๐˜ฉ๐˜ฆ ๐˜š๐˜Œ have shared private key control. When transferring your UTXOs within the system, Mercury updates the secret key. Each time it's transferred, an updated emergency plan is created for the new owner.

Mercury ensures transaction integrity by counting how many times it assists in transfers. However, it does not delve into transaction details, ๐˜๐—ต๐˜‚๐˜€ ๐—บ๐—ฎ๐—ถ๐—ป๐˜๐—ฎ๐—ถ๐—ป๐—ถ๐—ป๐—ด ๐˜†๐—ผ๐˜‚๐—ฟ ๐—ฝ๐—ฟ๐—ถ๐˜ƒ๐—ฎ๐—ฐ๐˜† ๐˜„๐—ต๐—ถ๐—น๐—ฒ ๐˜€๐˜๐—ถ๐—น๐—น ๐˜ƒ๐—ฒ๐—ฟ๐—ถ๐—ณ๐˜†๐—ถ๐—ป๐—ด ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ฎ๐—ฐ๐˜๐—ถ๐—ผ๐—ป ๐—น๐—ฒ๐—ด๐—ถ๐˜๐—ถ๐—บ๐—ฎ๐—ฐ๐˜†.

When you're ready to exit Mercury back to Bitcoinโ€™s base layer, you can close your transaction at will, finalizing it on Bitcoin's timechain. This closure ๐˜ฆ๐˜ฏ๐˜ด๐˜ถ๐˜ณ๐˜ฆ๐˜ด ๐˜ต๐˜ฉ๐˜ข๐˜ต ๐˜ต๐˜ฉ๐˜ฆ ๐˜œ๐˜›๐˜Ÿ๐˜– ๐˜ค๐˜ข๐˜ฏ'๐˜ต ๐˜ฃ๐˜ฆ ๐˜ค๐˜ช๐˜ณ๐˜ค๐˜ถ๐˜ญ๐˜ข๐˜ต๐˜ฆ๐˜ฅ ๐˜ธ๐˜ช๐˜ต๐˜ฉ๐˜ช๐˜ฏ ๐˜”๐˜ฆ๐˜ณ๐˜ค๐˜ถ๐˜ณ๐˜บ ๐˜ข๐˜จ๐˜ข๐˜ช๐˜ฏ, keeping the process orderly and secure.

However, ๐—ฒ๐˜ƒ๐—ฒ๐—ฟ๐˜†๐˜๐—ต๐—ถ๐—ป๐—ด ๐—ฐ๐—ผ๐—บ๐—ฒ๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐˜๐—ฟ๐—ฎ๐—ฑ๐—ฒ๐—ผ๐—ณ๐—ณ๐˜€, so it should be noted that Mercury requires ๐˜ด๐˜ฐ๐˜ฎ๐˜ฆ trust in the systemโ€™s main coordinators, the Statechain Entities. While ๐˜š๐˜Œ๐˜ด ๐˜ค๐˜ข๐˜ฏ'๐˜ต ๐˜ฎ๐˜ฐ๐˜ท๐˜ฆ ๐˜ง๐˜ถ๐˜ฏ๐˜ฅ๐˜ด ๐˜ฐ๐˜ฏ ๐˜ต๐˜ฉ๐˜ฆ๐˜ช๐˜ณ ๐˜ฐ๐˜ธ๐˜ฏ, their role is crucial, and their security and integrity are paramount.

Another tradeoff is ๐˜๐—ต๐—ฒ ๐—ฟ๐—ถ๐˜€๐—ธ ๐—ผ๐—ณ ๐—ป๐—ฒ๐˜๐˜„๐—ผ๐—ฟ๐—ธ ๐—ฐ๐—ฒ๐—ป๐˜๐—ฟ๐—ฎ๐—น๐—ถ๐˜‡๐—ฎ๐˜๐—ถ๐—ผ๐—ป. If a few SEs begin to dominate the Mercury system, it could centralize a significant portion of transaction facilitation. This would diverge from Bitcoin's decentralized ethos, so ๐˜ช๐˜ตโ€™๐˜ด ๐˜ช๐˜ฎ๐˜ฑ๐˜ฆ๐˜ณ๐˜ข๐˜ต๐˜ช๐˜ท๐˜ฆ ๐˜ต๐˜ฉ๐˜ฆ๐˜ณ๐˜ฆ ๐˜ฃ๐˜ฆ ๐˜ข๐˜ด ๐˜ฎ๐˜ข๐˜ฏ๐˜บ ๐˜š๐˜Œ๐˜ด ๐˜ข๐˜ด ๐˜ฑ๐˜ฐ๐˜ด๐˜ด๐˜ช๐˜ฃ๐˜ญ๐˜ฆ.

The Mercury Layer introduces simplicity and enhanced security to Bitcoin transactions. It makes transferring bitcoin ๐˜ข๐˜ด ๐˜ฆ๐˜ข๐˜ด๐˜บ ๐˜ข๐˜ด ๐˜ฆ๐˜น๐˜ค๐˜ฉ๐˜ข๐˜ฏ๐˜จ๐˜ช๐˜ฏ๐˜จ ๐˜ค๐˜ข๐˜ด๐˜ฉ, as long as concerns around trust, privacy, and centralization are mitigated. Mercury highlights Bitcoin's ongoing evolution, and is a further reminder that we're all still very, ๐˜ท๐˜ฆ๐˜ณ๐˜บ early.

Remember to ๐—Ÿ๐—ถ๐—ธ๐—ฒ๐Ÿค™, ๐—ฆ๐—ต๐—ฎ๐—ฟ๐—ฒ๐Ÿ”„, and ๐—•๐—ผ๐—ผ๐—ธ๐—บ๐—ฎ๐—ฟ๐—ธ๐Ÿ”– this for later.

What do ๐˜บ๐˜ฐ๐˜ถ think of the ๐— ๐—ฒ๐—ฟ๐—ฐ๐˜‚๐—ฟ๐˜† ๐—Ÿ๐—ฎ๐˜†๐—ฒ๐—ฟ?

Let me know in the ๐—–๐—ผ๐—บ๐—บ๐—ฒ๐—ป๐˜๐˜€โฌ‡๏ธ

#asknostr

Would all you wonderful bitcoin and nostr experts and devs please weigh in on this? How hard will it be to set up an SE (Statechain Entity) so we can have as many and as much liquidity as possible? Will this integrate smoothly with nostr for zapping and transacting?

๐Ÿ‘‡๐Ÿ‘‡This sounds very bullish.๐Ÿ‘‡

nostr:nevent1qqsypxqvjpc8nq5yghwtp2gxg4s9c3jywjq62dp2cdpkzhj4r4dzgzgpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3qtayp5jjjfqx4ufukxqamsl28wd5pggvteqe6u9n3svjn62lfr0hsxpqqqqqqzx3nfep

Reply to this note

Please Login to reply.

Discussion

I will be happy to weigh in on this.

Mercury is still in its very early development stages, and the code was only recently released. Read more about it here: https://www.nobsbitcoin.com/mercury-layer-released

This news is certainly bullish, but it may be a little premature to start building Statechain Entities at this point, since doing so will require adequate technical expertise, proper security measures, and significant underlying infrastructure.

As for its compatibility with Lightning, in its present form, Mercury is not interoperable with Lightning. It may be possible for that capability to be added to Mercury and/or Lightning in the future, but it is not presently possible. The same goes to Nostr integration and zaps.

The Mercury Layer is an exciting development, but a lot of work still needs to be done to prepare it for general use.