Add klv namespace for the Klever Blockchain

[nickgs1337]

This PR adds a new namespace klv for the Klever Blockchain, a layer-1 proof-of-stake chain with ed25519 keys, Bech32 addresses prefixed klv1..., Wasmer-based smart contracts, and a native multi-asset model (KDA — Klever Digital Asset) that handles fungible tokens, NFTs, and SFTs as first-class on-chain primitives. The namespace covers chain identification (CAIP-2), account references (CAIP-10), and KDA asset references (CAIP-19).

What changed

A new klv/ folder containing:

• README.md — namespace overview, governance pointer, references to the Klever ecosystem.
• caip2.md — chain id profile. References are the integer klv_chain_id exposed at /node/status. Test cases: klv:108 (mainnet), klv:109 (testnet), klv:100001 (devnet).
• caip10.md — account id profile. Bech32 addresses with HRP klv, ed25519 keypairs, 32-byte raw address, 62-char total Bech32 string. Documents the smart-contract address pattern (klv1qqqqqqqqqqqq...) and includes a real on-chain SC address example from the protocol test suite.
• caip19.md — asset id profile. Single asset namespace kda covering fungible / NFT / SFT (type lives in metadata, not the identifier). Documents the TICKER-NONCE shape where NONCE is a 4-character base36 suffix generated deterministically by the protocol.

Why

Klever has been live on mainnet since 2022 and operates a public block explorer, REST API, and TypeScript SDK, but does not yet have a CAIP-2 namespace registered. Adopting CAIP-2 / CAIP-10 / CAIP-19 lets cross-chain tooling — wallets, indexers, bridges, agent-driven signing surfaces — refer to Klever chains, accounts, and KDA tokens unambiguously without each tool inventing its own shape.

Every technical claim in the namespace files is traced to a specific path in the Klever node source (klever-io/klever-go) so reviewers can verify directly:

• HRP klv with fromBits=8, toBits=5, pad=true — crypto/pubkeyConverter/bech32PubkeyConverter.go
• ed25519 keypairs — crypto/signing/ed25519/
• Smart-contract address layout (8 zero bytes + 2 VM-type bytes = 10-byte prefix) — core/address.go (constants NumInitCharactersForScAddress = 10, VMTypeLen = 2)
• KDA asset type enum (Fungible = 0, NonFungible = 1, SemiFungible = 2) — data/transaction/contracts.pb.go
• Asset identifier generation (deterministic base36 4-char suffix after - separator) — core/process/kda/assetHelper.go (CreateNewAssetIdentifier) and core/process/kda/kdautils/utils.go (TickerSeparator = "-", TickerRandomSequenceLength = 4)

The integer chain IDs in CAIP-2 (klv:108 mainnet, klv:109 testnet, klv:100001 devnet) were verified live against https://node.mainnet.klever.org/node/status (the klv_chain_id field).

SLIP-44 coin type 690 (registered as KLV / KleverChain) is documented in the SLIP-44 registry.

References

• Klever — main website.
• KleverChain explorer — block explorer for mainnet, testnet, devnet.
• Klever node REST API — public REST endpoint used to verify chain identity and asset metadata in this PR.
• klever-go — reference Go node implementation; every code citation in the namespace files links here.
• Klever Connect SDK — TypeScript reference for address encode/decode.