We hear the Kaspa community and understand why dynamic address support is important. kaspa:native 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.
Unfortunately I was part of the group laid off from @coinbase today.
My whole tenure was protecting U.S. retail from tokens with actual utility like $XMR, $KAS, and quai-network:native.
Instead we focused on listing pristine crypto assets like $RAVE, $USELESS, $FARTCOIN, and $TRUMP.
Pictures unrelated.
@carlosrtruiz@furkncuci I think you dont understand that a Golf 7 has a 100x better outside and inside quality than a shit Peugeot. On top of that, you drive a crappy Peugeot, that would be embarrassing for me.
Toccata consensus feature freeze is finally here after a heroic last-mile push by kas core devs.
Aiming to reset TN12 tonight, or tomorrow at the latest.
Genesis update:
+ 0x6b617370612d746573746e6574 // kaspa-testnet
- 12, 2 // TN12, Launch 2
+ 0x544f4343415441 // TOCCATA
+ 12, 3 // TN12, Launch 3
@Grayscale@realvijayk arigato gozaimasu!
if Kaspa army showed up here, think how they'll show up when you provide a KAS digital asset..
by mid june Kaspa OP_CAT++ Bitcoin. worth the attention _/\_