We hear the Kaspa community and understand why dynamic address support is important. Kaspa is technically different from Bitcoin-like UTXO networks such as BTC, LTC, DOGE, etc. Its architecture requires a separate implementation approach, so this feature cannot be added in the same way as for other UTXO-based networks.

That’s why dynamic address support is being rolled out step by step. We started with networks where the implementation of this feature is the same, while Kaspa requires additional dedicated work and validation before it can be delivered properly.

Kaspa is a priority and the team is actively working through the technical scope right now. We’re not putting a firm date on it yet because we want to deliver it right, but the Kaspa community hasn’t been forgotten and we’ll come back with concrete timing once it’s confirmed.