Add Kaspa namespace with CAIP-2 and CAIP-10 profiles

[elldeeone]

This PR introduces the Kaspa namespace to the ChainAgnostic namespaces registry.

Added Files

• kaspa/README.md - Namespace profile for the Kaspa ecosystem
• kaspa/caip2.md - CAIP-2 chain identification profile for Kaspa
• kaspa/caip10.md - CAIP-10 account identification profile for Kaspa addresses

Summary

Kaspa is a proof-of-work Layer 1 with a native UTXO transaction model that uses GHOSTDAG consensus to order parallel blocks in a blockDAG.

This PR establishes the kaspa namespace for identifying Kaspa networks and native recipient or locking addresses.

Chain Identification (CAIP-2)

Networks in the Kaspa namespace are identified by the names defined by the Rusty Kaspa NetworkId implementation.

Network	Native NetworkId	CAIP-2 identifier
Mainnet	mainnet	kaspa:mainnet
Testnet 10	testnet-10	kaspa:testnet-10

The identifier can be resolved through a Kaspa node's getBlockDagInfo RPC method.

The profile also records the configured genesis hashes for the registered networks and limits the initial namespace to mainnet and the stable public testnet-10 network.

Account Identification (CAIP-10)

Native Kaspa addresses use the form <prefix>:<payload>.

Because CAIP-10 does not allow : inside account_address, this profile uses the native address payload without its prefix:

kaspa:<reference>:<address_payload>

The native prefix is restored from the CAIP-2 identifier before validating the address version, body length, and prefix-dependent checksum.

The profile includes canonicalization guidance and valid and invalid vectors for Schnorr public-key, ECDSA public-key, and script-hash addresses.

References

• Kaspa ecosystem website
• Kaspa builder documentation
• Rusty Kaspa full-node implementation and related SDK libraries
• Kaspa community discussion