The FUD currently encountered by Liquid requires the deployment party (I am not called the project party because decentralized projects do not have a project party, only the deployment party that deploys inscriptions) to sell Twitter accounts There shouldn't have been any issues originally, as fully decentralized tokens like ODI and Sats shouldn't have Twitter accounts either However, the BRC2.0 protocol has not yet been launched. When the protocol is launched, the deployment party must deploy the inscription in order to send it to everyone's hands If the deployment party sells the Twitter account and the private key of the deployment inscription, the newly taken over can perform the action of deploying inscription What if no one performs this action and the inscription cannot be sent out? The information I found is 1. Prepare a snapshot in advance; 2. Use the correct parameters to preemptively create a deploy; 3. Hand over TXID to mainstream indexes; So even if the original team disappears, LIQUID can still automatically map to everyone's address after the main network goes online.