VanityTXID-Plugin VS Bitcoin

One future possibility is traders could look for PoW in the token ID, like it starts with 0000000. VanityTXID can do this with SLP tokens. PoW is a voluntary anti-spam technique, whereas fees are compulsory and may enrich holders in a PoS system. With much greater difficulty, minting NFTs could require an ASIC (either indirectly or directly).

I recommend trying the SLP Ed. of EC, download here. I've created lots of NFTs, but I've never tried selling one (I just burn them and make another one). VanityTXID enables vanity NFT IDs, if anyone's interested.

A couple days ago I posted in r/btc that CashFusion required about $500 (or a few hundred $) minimum. However that was with several coins, half of which could easily be traced (the 3 inputs on top, here). Then I thought of the mono-coin challenge, and it took me another day to succeed. My only input to this fusion was the 6.19 BCH on top (VanityTXID starting with 000000). Technically 6.2 BCH is sufficient.

This is the fusion I eventually got (fee was well under a cent). Three of my inputs are on top, because I used VanityTXID to get those coins' TXIDs to start with 00000, which puts them on top of a CashFusion.

I last posted after v1.5.0 enabled vanity addresses. The latest version can be downloaded here.

The plugin can be downloaded here. The example from the screenshot is

Investor. I only "mine" vanity TXIDs & addresses, eg with VanityTXID. If I'm ever rich, or a rich person wants Electron Cash plugins to use ASICs, I might have to buy an ASIC. :)

VanityTXID would be the first to use it, to make vanity addresses with vanity TXIDs. If any other plugin devs want it I'd be more enthusiastic.

If you wanna have some fun with Electron Cash you can try out the VanityTXID plugin I've developed. It comes with an example to toy with.

Every transaction (TX) has an ID # called the TXID, 64 hex digits. Normally it's (nearly) guaranteed within a few seconds of your payment. However we may prefer a TXID which starts with a certain vanity pattern, like '2dad', 'c0ffee' or '0000000'. In that case we can use special addresses whose TXID is only guaranteed after several minutes (block confirmation). The exact details require installing a plugin to Electron Cash, like VanityTXID.

Ubuntu/Debian: Install LND: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#install-lnd Install Bitcoin Core: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md#linux-instructions

To be able to follow along, you must have both bitcoind and lnd installed.

As mentioned previously, ScriptPubKeys are scripts that embody the locking conditions of bitcoins in a Bitcoin transaction. They are a crucial element of a Bitcoin transaction that specifies the requirements that must be met before an unspent transaction output (UTXO) is used. The ScriptPubKey, combined with the Amount, creates an output of a Bitcoin transaction. Like every other script, ScriptPubKeys are made up of operators and data. During the encoding of a transaction, both data and the operands are represented in hexadecimal format. You can find the hex representation for all operands used in Bitcoin Scripts here.

Which article? Have a look at Luke's CVE and pull request https://nvd.nist.gov/vuln/detail/CVE-2023-50428 https://github.com/bitcoin/bitcoin/pull/28408

From github pull request discussion: https://github.com/bitcoin/bitcoin/pull/28408

See: https://github.com/bitcoin/bitcoin/issues/10494