datacarriersize affects standardness, not consensus rules, so if there is any unfair advantage related to this parameter, it is on relay step. If you consider this unfair, all you can do is changing the parameter locally, so your node doesn't relay or broadcast such txs, but other miners can still mine such transactions and you have to accept them, otherwise it is a fork. Anyway, my transactions pass and mine, so I don't care if their transactions mine as well, if they satisfy the consensus rules. You think their transactions should not be mined? Justify this, otherwise it is just an arbitrary censorship. Preventing them from relaying seems useless, since they already cooperate with miners.

I see that your purpose is just trolling!

My comment on lightning was not AI generated.

Antonopoulos is just right here and nothing has changed unless you prove otherwise. Whoever overbids others in a block, gets into the block. Everyone pays by the same rules, the discount is on signature part in case of using segwit, not on output part. Additionally, op_returns are not stored in utxo set, so they actually don't inflate anything, just spend space in blocks, which is fine if they pay enough. And they do pay a lot!

Can you provide an example of a transaction where ordinals unfairly gained an advantage in inflating the UTXO set by inserting a script into OP_RETURN, please? This seems nonsensical to me.

I'll set aside your judgment on my education for the moment. If you aim for your messages to carry influence, consider working on cultivating a more polite tone first.

With fees currently at a relatively low level following a price surge, one might question if someone were to conduct a spam attack, wouldn't it make sense for them to execute it at this moment?

Although LN presents a promising solution, the challenge of pinning attacks remains unresolved. With a current capacity of 5000 Bitcoins, users are still willing to pay for on-chain transactions. The sequence appears to be: a higher price leading to increased demand for affordable transactions, subsequent growth in Lightning capacity, emergence of pinning attacks, and finally, the implementation of a solution. Ideally, resolution should precede any actual attack.

Addressing the 7 billion bug, unintended glitches should not be accepted, yet it differs from the situation with ordinals. A fair price is paid for inflating the UTXO set, with no discount for the transaction outputs section, except for segwit (signatures), which is not stored in the UTXO set.

For insights on "spam" transactions, refer to Andreas Antonopoulos's 2016 perspective. I concur with his viewpoints. 👀

https://video.nostr.build/4af608af1757b4dd1d5c53ded1c36b253a4651b2dd8f214b099811905c75fa5f.mp4#m=video%2Fmp4&dim=1266x720&alt=THROWBACK%3A+%F0%9F%9F%A0+Andreas+Antonopoulos+speaking+about+%22spam%22+transactions+in+2016+%F0%9F%91%80&blurhash=i88M%3FS%3FG%5Ej%252oft6R%2Bofa%7D%7EAt7%251ofWXofS2s%3Aj%5BWVNHS2bGW%3AfkofkBj%5BWVjZs.ods.j%5Bs%3AWVa%7Ds%3Aj%5Bs%3AWVoej%5Bj%5Bj%5Bj%5B&x=03ae47f27ef14ff7dc9178be6da559a3f4ff5367c3edfd9d67f9861da00c535e

It is more an attack on susceptible people owning Bitcoin, who can buy JPEG with Bitcoin. Such people always existed and bought shitcoins with Bitcoin. Bitcoins moved to people who value them the most, that is actually a good thing for Bitcoin, isn't it?

Let's purple pill him :p

When testnet? :)

Does Spencer Schiff use Nostr?

... said in 2017 😁

Bullish? Such people normally buy at ATH ;)

I confirm reproducible build of LND v0.17.4 on linux-amd64.

Go version: 1.21.0.

```

make release tag=v0.17.4-beta sys="linux-amd64"

6efa226be3db5e8675c369c5d71fae5156142ec3f728f43191efa2ccd70d9fe6 lnd-linux-amd64-v0.17.4-beta.tar.gz

```

The binary with the same hash can be downloaded from https://github.com/lightningnetwork/lnd/releases/download/v0.17.4-beta/lnd-linux-amd64-v0.17.4-beta.tar.gz

Reports stopped

## How to open a channel in LND using combined funds from LND and external wallet

1. Select utxos to spend from output of `lncli listunspent`. Copy-paste involved addresses to a text file.

2. Add external addresses to the file.

3. Run recent Electrum version in watch-only mode and select "Import Bitcoin addresses or provate keys". Put the list of addresses there.

4. `lncli openchannel --psbt node_id amount_in_sats`

5. Copy the address and amount from the output and put them in Electrum's Send tab. Press Pay -> Advanced -> Finalize -> Export -> Copy to clipboard.

6. Save the PSBT to a file on the machine where LND is running (e.g. `/tmp/my.psbt`)

7. Write the file name to LND's prompt. Make sure it prints "PSBT verified by lnd"

8. Sign the PSBT on the external wallet. Copy second PSBT.

9. Complete signing on LND's side: `lncli wallet psbt finalize "Second PSBT"`

10. Copy-paste "final_tx" hex string to LND's prompt and press Enter.

More complex path, working if addresses are taproot or you know public keys of them. Use bitcoin-cli and descriptors.

Import your addresses to bitcoin core as watch-only wallet.

1. `bitcoin-cli -named createwallet wallet_name=testpsbt avoid_reuse=true descriptors=true load_on_startup=true disable_private_keys=true` where `testpsbt` is the name of the wallet used in commands below.

2. Write descriptors of your addresses. See https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md

For example, for taproot address, use `rawtr(public_key)` where `public_key` are the 32 bytes pushed in ScriptPubKey.

For pay-to-witness-pubkey-hash, use `wpkh(public_key)` and you need to know the public key (e.g. from xpub or from the wallet).

3. Add checksums to your descriptors: `bitcoin-cli getdescriptorinfo 'rawtr(xxx)'` and copy the version of descriptor with hash tag

4. Import descriptors into the wallet: `bitcoin-cli -rpcwallet=testpsbt importdescriptors '[{ "desc": "rawtr(xxx)#yyy", "timestamp":1700000000}, { "desc": "wpkh(xxx)#yyy", "timestamp":1700000000}]'` where timestamp must be before the first UTXO you want to add to the wallet.

5. Make sure bitcoin core sees all the utxos you need: `bitcoin-cli -rpcwallet=testpsbt listunspent`

6. Use LND to open a channel as described above. Copy the `walletcreatefundedpsbt` that LND provides for bitcoin-cli and modify it like this: `bitcoin-cli -named -rpcwallet=testpsbt walletcreatefundedpsbt outputs='[{"xxx":0.01000000}]' changeAddress=` Make sure to put a valid change address there.

7. Other steps are the same.

У меня 300 грамм стоит 7 евро. Примерно столько же. Дороговато, но вкусно!

А креветки жареные или варёные? Жареные намного вкуснее!

А креветки?

В какой валюте?)

Чтобы успешно построить карьеру в государстве, надо уметь переобуваться. Ну и говорить то, что сейчас от тебя хотят услышать 😃

Fee won't be higher than people can afford to pay. At fees 600 satoshi per byte the total fee reward is roughly equal to block subsidy. I don't think it can realistically grow much higher than that. Just wait for ordinal users to run out of money.

Regarding L2, people didn't adopt it enough in the past, because fees were low and incentive to adopt was also low. The ones, who did open channels at low fee periods, benefit now by using the channels and not paying fight fees. It is a lesson for everyone!

Bitcoin is working as expected! They pay for their transactions, even overpay.