I looked over the Stacks site and didn't see a clear answer to this question.
I looked over the Stacks site and didn't see a clear answer to this question.
Moving Bitcoin to Stacks is a bit more complicated and there are several ways:
a) Wrapped assets. Tokensoft + Anchorage (custodian) have a solution that they're calling xBTC where a "wrapped Bitcoin" is issued on the Stacks chain. Such wrapped assets exist on other chains like Ethereum as well with one main difference that xBTC is secured by Bitcoin itself.
b) There are more decentralized solutions similar to Keep network, where threshold signatures can be used to move the assets by a group of nodes.
c) The most decentralized way of doing this is by locking your BTC directly on BTC chain, using Clarity to monitor funds, and then having Clarity trigger release of funds on Bitcoin chain. This requires Clarity logic to trigger Bitcoin state changes. This is theoretically possible but at R&D stage currently.
The question was about how you move Stacks to Bitcoin.
I take from this handwaving answer that it isn't actually possible.
Or let's rephrase the question in Bitcoin terms: While the BTC are locked up on the Bitcoin blockchain, which key is necessary to unlock them? Surely one controlled by Blockstack, no?
What exactly do you mean by "xBTC is secured by Bitcoin itself?"
Do you mean that Stacks writes out its own block hashes to the Bitcoin blockchain, or something?
Yes; the entire history of attempts of mining Stacks blocks, as well as the entire history cryptographic sortitions that select Stacks blocks (including forks), is written to the Bitcoin chain. See SIP-001 for details: https://github.com/stacksgov/sips/blob/main/sips/sip-001/sip...
Is this fine with p2sh?