Very strange that both of your wallets either don't work at all or don't support Taproot. I just checked again - both wallets generate a Taproot address by default for receiving Bitcoin, and treat Taproot addresses as valid when sending.
But yes, I agree that in both cases the Taproot support is implemented very specifically: only receiving and sending are supported, not direct on-chain storage.
Maybe that's because Phoenix is supposed to be a wallet meant for the Lightning Network. Does it keep on-chain bitcoin deposits at all or are all on-chain bitcoins immediately swapped for LN funds? It would be weird if they only did it with Taproot addresses.
Regarding the Phoenix wallet, Taproot support is organized like this:
- User sets the maximum on-chain fee they are willing to pay.
- User receives an incoming on-chain transfer to a Taproot address (Taproot is the default, and I'm not exactly sure if there is an option to receive on-chain Bitcoin to other address formats). In general case, the user's private key does not allow controlling the funds at this address.
- Wallet gets from its server an estimated fee size that is required to move the received coins into a payment channel.
- - If the fee does not exceed the threshold set by the user, the funds are moved into a payment channel. If it does exceed the threshold, the funds remain unusable until the estimated fee drops and the wallet is able to move the coins to the Lightning Network.
- - If the fee does not decrease within 4 months, the user's private key becomes usable to control those coins. For example, the Phoenix seed phrase can be imported into Blue Wallet to create a transaction and spend the funds.