Hot answers tagged

5

No, the Liquid system isn't using Bulletproofs yet. The code has been written to use them, but switching over will require more review, and a hardfork upgrade once deployed.


5

It has always been the case that the full Bit Machine would be "exposed"[1] by allowing arbitrary Simplicity. This is because the combinators that let you compose the high-level jets are exactly the same combinators that define low-level Simplicity. Thus even if only a few high-level jets are chosen to be exposed, it would still be the case that the low-...


5

The lightning-network (LN) is an instant payment system built on top of Bitcoin. Its relationship to Bitcoin is akin to that of Visa card payments and the US banking system. The LN is a convenient and efficient way to pay directly from one user to another, especially for smaller amounts. Under the hood, the Lightning Network works by spanning payment ...


4

Fees are collected to a "fee address". Blockstream uses this to fund the BTC fees incurred by "burning" the L-BTC needed to pay fees. Fees are intended to be anti-spam rather than a revenue source. Monetization of Liquid is based on providing products and services on top of Liquid.


4

You can easily verify the liquid circulation, in fact any liquid node can do this in realtime as part of its operation if you run a Bitcoin node along side it. Pegins can't, however, be reconized until after they're claimed on the sidechain. Before then the addresses are cryptographically indistinguishable from other similar multisig transactions on ...


3

The error hints that you're not signing the transaction correctly. In fact, you're generating a signature with: txHash := updater.Data.UnsignedTx.TxHash() sig, err := privkey.Sign(txHash[:]) But the current transaction hash is not what you need to sign. Instead, you should use HashForSignature for legacy input types: sigHash, err := updater.Data.UnsignedTx....


3

destroyamount is the rpc call you are looking for https://github.com/Blockstream/liquid/blob/3f937d39f7c516e49f62d05c12d41b63b79ca043/src/wallet/rpcwallet.cpp#L586


2

Short answer: yes. However that depends on the question if liquid supports segwit and creation of a lightning network. I have not looked at the details of liquid but I believe it does. The lightning network protocol itself is pretty agnostic to the underlaying blockchain. If you look at the channel announcement messages defined in BOLT7 you will see that ...


2

According to the documentation, anyone running a Liquid node can generate and fund a peg-in transaction. And anyone can run a Liquid node. You'll need a participant, which can be an exchange, to peg-out and exchange your L-BTC for BTC though. The peg-in is explained in more details here.


2

There is no maximum that can be created, however you may run into issues with RPC-APIs in Elements if any wallet contains more than 92,233,720,368.54775807 at any time. Confidential transactions will function with any realistic amount (you would have to re-issue an asset more times than possible to overload the 256-bit confidential amount type, however the ...


2

Bob:~$ getaddressinfo $ADDR You should see a long value for the “confidential_key” property within the JSON formatted results. It will look something like this: "confidential_key": "030788da8d9ca229cbe57e346daaf8d94cba3ed548b41922a8abefaec91ff1abb1" The confidential_key is the public blinding key, which has been added to the address and ...


2

In the following I focus on Confidential Transactions (instead of the extension Confidential Assets) for simplicity, but all of what I say is also true for Confidential Assets. Yes, it's possible to use cryptographic protocols to organize the CoinJoin transaction in a privacy-preserving manner. The ValueShuffle protocol is designed for exactly this purpose. ...


2

Lightning Network: TLDR: If you are sending 50,000 sats to your coffee shop 100 times in a week, not all these transactions need to be on-chain and works better off-chain. Example: I want to use a service online, pay with bitcoin and and it involves micro payments. I will lock 0.1 BTC in multisig and we keep record of all the things I use and payments for ...


1

What exactly are "Bitcoin Lightning" and "Bitcoin Liquid"? Those are protocols built upon Bitcoin. They are responsible for their stuff to be both Lightning/Liquid spec AND Bitcoin compatible while Bitcoin nodes are only responsible for Bitcoin-side validation. Why do they exist? Reason 1: scalability: Instead of keeping everything on-...


1

Tx: 802dc4c4a08fcf4f50e4320bdb5eb596afc01c95dd0ff6afb83304aeb989be15 Inputs: 38V6gLL6kVCWhfXPo4t5x1gMfg5BKe3Rv H18z1ifzs184pzwTABag5gv47AAxZSi1qg Outputs: H38V6gLL6kVCWhfXPo4t5x1gMfg5BKe3Rv H4UWQS836njW4QJ6WfkGAPjaYtK2twLnZE GnHogGZpDCwmskKFJoVhuvgUg6gKhWQjy6 Tx: 81efc96bea93fcb5992831d8311dec63a0b1d17072ec2e6f1263901b1bd26000 Inputs: ...


1

Ok it turned out I was a bit confused about the way fees and change is handled here. Here are the commands that worked for me: createrawtransaction "[]" "[{\"$UADDR\":1.2},{\"$UCHANGE\":1.8}]" 0 false "{\"$UADDR\":\"$ASSET\",\"$UCHANGE\":\"$ASSET\"}" fundrawtransaction ...


1

Liquid wallets are open and accessible to anyone. This could either be SPV wallets such as Blockstream Green or the Elements Liquid node. With these wallets you can verify transactions (your own transactions with Green, all transactions with the node). However, you can't produce blocks. To do that, you need to be one of the Liquid members. To become such a ...


Only top voted, non community-wiki answers of a minimum length are eligible