I just tried it (without inscribe on Go88 Com App and hardware wallet) and it seems to work properly. While i really appreciate your effort, your website could add different burden to the users. 1. Without block explorer which automatically decode Ordinal's data, it's not trivial to get the encrypted descriptor. With your inscribed example, i had to copy hex data pushed by OP_PUSHDATA2 and use website/tool which convert hex to ASCII/UTF-8. 2. User either need to write down associated address/TXID somewhere in order to get encrypted descriptor easily in the future. Thanks for giving it a try! Just to clarify, you actually don't need to use a block explorer or write down the address, txid, or anything else. All you need to do is go to the "Recover" tab and input two master fingerprints in your multisig. In the inscribed example, the master fingerprints are 3abf21c8, a1a4bd46, and ed91913d, which correspond to the three seed phrases. Pick any two and press "Recover," and the tool hashes them and looks up the encrypted descriptor in an indexer. You can then decrypt and recover the descriptor using the xpubs. Hope this helps! I see. I didn't try inscribe on Go88 Com App, so i skipped "Recover Step 1" where i had to enter encrypted descriptor manually. In case the user perform inscription, additional burden i mentioned doesn't apply.
I just tried it (without inscribe on Go88 Com App and hardware wallet) and it seems to work properly. While i really appreciate your effort, your website could add different burden to the users. 1. Without block explorer which automatically decode Ordinal's data, it's not trivial to get the encrypted descriptor. With your inscribed example, i had to copy hex data pushed by OP_PUSHDATA2 and use website/tool which convert hex to ASCII/UTF-8. 2. User either need to write down associated address/TXID somewhere in order to get encrypted descriptor easily in the future. Thanks for giving it a try! Just to clarify, you actually don't need to use a block explorer or write down the address, txid, or anything else. All you need to do is go to the "Recover" tab and input two master fingerprints in your multisig. In the inscribed example, the master fingerprints are 3abf21c8, a1a4bd46, and ed91913d, which correspond to the three seed phrases. Pick any two and press "Recover," and the tool hashes them and looks up the encrypted descriptor in an indexer. You can then decrypt and recover the descriptor using the xpubs. Hope this helps! I see. I didn't try inscribe on Go88 Com App, so i skipped "Recover Step 1" where i had to enter encrypted descriptor manually. In case the user perform inscription, additional burden i mentioned doesn't apply.

I just tried it (without inscribe on Go88 Com App and hardware wallet) and it seems to work properly. While i really appreciate your effort, your website could add different burden to the users. 1. Without block explorer which automatically decode Ordinal's data, it's not trivial to get the encrypted descriptor. With your inscribed example, i had to copy hex data pushed by OP_PUSHDATA2 and use website/tool which convert hex to ASCII/UTF-8. 2. User either need to write down associated address/TXID somewhere in order to get encrypted descriptor easily in the future. Thanks for giving it a try! Just to clarify, you actually don't need to use a block explorer or write down the address, txid, or anything else. All you need to do is go to the "Recover" tab and input two master fingerprints in your multisig. In the inscribed example, the master fingerprints are 3abf21c8, a1a4bd46, and ed91913d, which correspond to the three seed phrases. Pick any two and press "Recover," and the tool hashes them and looks up the encrypted descriptor in an indexer. You can then decrypt and recover the descriptor using the xpubs. Hope this helps! I see. I didn't try inscribe on Go88 Com App, so i skipped "Recover Step 1" where i had to enter encrypted descriptor manually. In case the user perform inscription, additional burden i mentioned doesn't apply.

I just tried it (without inscribe on Go88 Com App and hardware wallet) and it seems to work properly. While i really appreciate your effort, your website could add different burden to the users. 1. Without block explorer which automatically decode Ordinal's data, it's not trivial to get the encrypted descriptor. With your inscribed example, i had to copy hex data pushed by OP_PUSHDATA2 and use website/tool which convert hex to ASCII/UTF-8. 2. User either need to write down associated address/TXID somewhere in order to get encrypted descriptor easily in the future. Thanks for giving it a try! Just to clarify, you actually don't need to use a block explorer or write down the address, txid, or anything else. All you need to do is go to the "Recover" tab and input two master fingerprints in your multisig. In the inscribed example, the master fingerprints are 3abf21c8, a1a4bd46, and ed91913d, which correspond to the three seed phrases. Pick any two and press "Recover," and the tool hashes them and looks up the encrypted descriptor in an indexer. You can then decrypt and recover the descriptor using the xpubs. Hope this helps! I see. I didn't try inscribe on Go88 Com App, so i skipped "Recover Step 1" where i had to enter encrypted descriptor manually. In case the user perform inscription, additional burden i mentioned doesn't apply.