You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It doesn't make sense to support this when users can't send them with an integrated function in the wallet but it will when we support sending.
Sending from non-zero-index is supported for inscriptions already when they are on (regenerated) taproot addresses.
We also want this for non-zero-index (i.e. m/86’/0’/0’/0/0 and m/86’/0’/0’/0/1 etc.) BTC balance and other assets on the native segwit address but we can create a seperate issue for that if that is not in scope right away.
I spoke to a user today that send assets to addresses generated in Ledger Live and that will give you a fresh address every time and hence assets will land on non-zero-index addresses. This could help them get them on the addresses that are supported by marketplaces (the 0 index: i.e. (account 1) m/86’/0’/0’/0/0 or (account 2) m/86’/0’/1’/0/0 ).
The text was updated successfully, but these errors were encountered:
It doesn't make sense to support this when users can't send them with an integrated function in the wallet but it will when we support sending.
Sending from non-zero-index is supported for inscriptions already when they are on (regenerated) taproot addresses.
We also want this for non-zero-index (i.e. m/86’/0’/0’/0/0 and m/86’/0’/0’/0/1 etc.) BTC balance and other assets on the native segwit address but we can create a seperate issue for that if that is not in scope right away.
I spoke to a user today that send assets to addresses generated in Ledger Live and that will give you a fresh address every time and hence assets will land on non-zero-index addresses. This could help them get them on the addresses that are supported by marketplaces (the 0 index: i.e. (account 1) m/86’/0’/0’/0/0 or (account 2) m/86’/0’/1’/0/0 ).
The text was updated successfully, but these errors were encountered: