Hi - Previously before Cake integrated MWEB, I would send from an MWEB in my Litecoin core to Cake and would be able to spend the coins after one confirmation. This is also true with Stack Wallet.
Since the introduction of MWEB to cake it seems you guys are following the protocol standard to wait for 6 confirmations before coins can be spent. This is just a soft limit and not actually enforced unless going from ltc → MWEB or MWEB → MWEB but not enforcible going from MWEB → ltc as I have done it many times in the past and can still do it in stack.
Screenshot below
Please disregard this message if you haven’t already. I tested it last night in stack and yes 6 confs is a hard limit. I was mistaken. Sorry about that fellas
Okay nevermind. I did some research. Please see LIP-0003. This was a peg-in from the canonical chain after 1 confirmation.
Per Peg-In Transactions (lips/lip-0003.mediawiki at master · litecoin-project/lips · GitHub) there is no 6 confirmation requirement to peg-in to the extension block (MWEB).
Also, per the same section, there is no 6 block requirement for the pegged-in coins as there is no time lock. So, peg-in can be spent immediately after confirmed.
However, per Peg-Out transactions (lips/lip-0003.mediawiki at master · litecoin-project/lips · GitHub) there is a 6 confirmation lock of the UTXO on the canonical chain.
I think changing the restrictions in Cake will improve litecoin UX.
I did some tests with Litecoin core:
- I could Peg-in (send to MWEB) after 1 confirmation
- I could spend Pegged-In (MWEB) coins either to another MWEB address or back to the canonical chain after 1 confirmation.
- Coins sent from MWEB-> Canonical chain (Peg-out) have a 6 confirmation lock and are considered “Immature” by core until then.
Thanks for sharing. This will looked into an modified accordingly.