We are implementing a guarded, testnet-only protocol adapter and need an authoritative current DeFi or tokenized-RWA deployment on X Layer testnet (chain ID 1952). Official documentation currently identifies chain metadata and some system/payment contracts, but we have not found a maintained registry for reversible lending, staking, vault, or RWA protocols. One protocol team's published chain-1952 addresses currently return empty bytecode, which makes community address lists unsafe to use. Could X Layer publish or point to a maintained testnet registry containing protocol owner/source, target and asset addresses, deployment transaction hashes, proxy implementation/admin details, matching source commits, documented entry and exit calls, and applicable audits? A chain-196 mainnet deployment or an independently deployed fork would not satisfy this testnet provenance requirement.
We are implementing a guarded, testnet-only protocol adapter and need an authoritative current DeFi or tokenized-RWA deployment on X Layer testnet (chain ID 1952). Official documentation currently identifies chain metadata and some system/payment contracts, but we have not found a maintained registry for reversible lending, staking, vault, or RWA protocols. One protocol team's published chain-1952 addresses currently return empty bytecode, which makes community address lists unsafe to use. Could X Layer publish or point to a maintained testnet registry containing protocol owner/source, target and asset addresses, deployment transaction hashes, proxy implementation/admin details, matching source commits, documented entry and exit calls, and applicable audits? A chain-196 mainnet deployment or an independently deployed fork would not satisfy this testnet provenance requirement.