more clarity on how taproot assets are received

[ZZiigguurraatt]

I think there needs to be more clarity on how taproot assets are received. There are some key differences between normal bitcoin transactions.

Need to add/change some things here:

docs.lightning.engineering/the-lightning-network/taproot-assets/taproot-assets-protocol.md

Lines 141 to 149 in dede15c

	### Taproot Assets Addresses <a href="#docs-internal-guid-9dd22c77-7fff-d40d-b240-51c0f6f07a08" id="docs-internal-guid-9dd22c77-7fff-d40d-b240-51c0f6f07a08"></a>
	Taproot Assets addresses are bech32m encoded identifiers of the asset ID, the asset script hash, the internal key of the sparse Merkle sum tree and an amount, prefixed with Taproot Assets or `taptb1` (testnet).
	`bech32(hrp=TapHrp, asset_id || asset_script_hash || internal_key || amt)`
	The issuer or asset holder can use the information in your Taproot Assets address to create or modify the sparse Merkle sum tree as explained below. This address format can also be used to request a specific proof over the amounts held by the address.
	[Read the BIPs: Taproot Assets On Chain Addresses](https://github.com/Roasbeef/bips/blob/bip-tap/bip-tap-addr.mediawiki)

• Need to standardize on TapHrp or taproot_asset_hrp which is used at https://github.com/Roasbeef/bips/blob/bip-tap/bip-tap-addr.mediawiki

• A taproot asset address includes a specific amount that can be received. We need some explanation on why that also has to be included.

• When a sender sends taproot assets, they make an on chain transaction. They also mush share proof data as well. That needs to be published via a universe server, or they need to send it via hashmail. The taproot asset address format includes a hashmail server for the sender to use to communicate this information. If the receiver never gets the proof, the sender never proved they actually did it, so it's almost as if the payment was never made. So, it's critical that the receiver get this information too.