chat gtp 4O answer there-
In the images you shared, the term "Sighash" refers to the "Signature Hash" or "Sighash" type used when signing Bitcoin transactions. This option determines which parts of the transaction are signed and, therefore, which parts can be modified later by others.
Here's what each option generally means:
1. **All (Recommended)**: This is the default and recommended setting. It signs all inputs and outputs, meaning the transaction cannot be altered in any way once signed.
2. **None**: This signs nothing. It allows anyone to modify both inputs and outputs, which is dangerous and not recommended for standard use, as it leaves your transaction completely insecure.
3. **Single**: This only signs one specific output, leaving other outputs and inputs open for modification by others. This is a specialized use case and is risky unless you know exactly what you're doing.
4. **All + Anyone Can Pay**: This signs all outputs, but allows anyone to add more inputs. It can be useful for certain complex transactions where multiple parties need to contribute to the transaction.
5. **None + Anyone Can Pay**: This doesn’t sign anything specific, but allows others to add inputs and outputs, which can be risky as it leaves the transaction open to manipulation.
6. **Single + Anyone Can Pay**: This only signs one output and allows other people to add inputs.
The "None" option, which was selected in the shared image, is dangerous for a typical user because it allows anyone to modify the transaction, including changing the recipient or the amount of Bitcoin being sent. This is likely what caused the 0.8 BTC loss mentioned in the post you shared.
It’s always advisable to stick with the recommended "All" unless you're doing advanced multi-party transactions and fully understand the risks involved with other options.
Isn't that option that ordinal guys use to snipe nfts on the mempool?
Oddbean new post about login | logout 
