VanityTXID-Plugin VS research

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.

It is non-custodian betting on price of supported assets paired against BCH, both parties put their money into the contract's pot and later the contract parses an oracle message and calculates how much they can take out. Made possible with Introspection opcodes and int64 upgrades to Bitcoin-tech Script VM, which activated in May '22 on Bitcoin Cash blockchain.

I dug around a bit and it seems to be this one: CHIP-2021-02-Bigger-Script-Integers.

native introspection

The latest "Group" proposal (v4.2) is more than just "tokenization". It got simpler and more powerful at the same time. It now enables generic BCH output groups that can be used to create persistent Script covenant contracts that can prove their genuineness. This is something that current contracts cannot do, even with the new Introspection opcodes. Group would make it possible because the groupID is a commitment to the whole genesis transaction, but this is not a post about that.

Will you soon shut up about BCH being shit against "superior chains" when I point you to the CHIPs such as Native Introspection Opcodes, Bigger Script Integers which allows better smart contract functionality coming in 2022, and PMv3 and Group Tokens which allow better token and transaction formats that are coming in 2023?

You can't, because it requires a sibling output (same prevout txid as the contract, but index 1 instead of 0) to be spent alongside it and it verifies it using introspection opcodes that will be available in May. Only the owner of the sibling can spend the contract.