Cardanoscan Add Calidus Identity Keys to Cardano Stake Pools

Cardanoscan don add Calidus key information to Cardano stake pool profiles, wey give users direct way to see the authentication credentials wey pool operators don register. The update integrate CIP-151, standard wey dem design to separate everyday identity verification from the sensitive cryptographic keys wey dem dey use manage stake pools.

The new field dey allow applications and third-party services to identify authorized operators through public blockchain records. For delegators, e add another piece of verifiable information join the stake pool profiles wey dey already.

Cardanoscan Bring Calidus IDs Come Stake Pool Profiles

Cardanoscan now dey display Calidus ID side by side with the existing pool identifier once operator don register the credential on-chain. The identifier dey use Bech32 encoding with the prefix "calidus".

The explorer highlight Austrian stake pool ATADA as example of the integration. The pool get approximately 65.6 million ADA delegated as of November 3, according to the figures wey dem include for the original report.

Calidus keys dey use Ed25519 cryptography and dem dey provide separate signing identity wey link to registered stake pool. Compatible applications fit verify signatures against the public key wey dey recorded for Cardano, to confirm whether message or authentication request come from authorized credential.

The underlying CIP-151 proposal na Adam Dean and Martin Lang, the operator of ATADA, author am. Ecosystem tools and infrastructure providers wey include Cardano Signer, Koios, Blockfrost, and CNTools dey support the implementation.

How CIP-151 Take Separate Identity Verification From Cold Keys

Cardano stake pool operators dey rely on cold keys to authorize sensitive administrative operations. Dem normally keep these credentials offline, and that one no make am suitable for frequent authentication requests from external platforms.

CIP-151 introduce separate Calidus key wey operators fit authorize through one-time registration. The process dey link the public key to the stake pool through transaction metadata under label 867, with the registration wey dem authenticate using the pool cold key.

After registration, the Calidus private key fit sign messages and authentication requests. Supported services go verify those signatures against the on-chain record without needing further access to the cold key.

The registration mechanism build on top of CIP-0088 and e support compatible signing workflows wey involve hardware wallets, including Ledger, Trezor, and Keystone.

Calidus no replace the operational authority of stake pool cold key. In particular, Cardano native on-chain SPO governance votes still require the correct cold-key authorization. Calidus provide alternative for identity verification and application-level interactions, no be replacement for protocol-level voting credentials.

[NEWSBREAK]

Key Rotation and Public Verification Through Cardanoscan

CIP-151 still establish mechanism to replace Calidus credentials wey don compromise or don old.

Each registration get nonce value wey dem dey use determine which authorization dey current. New valid registration wey get higher nonce go supersede the previous credential, so operators fit rotate keys without changing their stake pool identity.

Operators fit also revoke existing authorization without registering replacement by submitting all-zero public key. Compatible services go recognize this registration as invalidating earlier Calidus credentials.

The mechanism dey support services wey require verified operator identities, including authentication systems, governance interfaces, and applications wey dey accept cryptographically signed messages.

With the Cardanoscan integration, delegators fit view registered Calidus identifiers side by side with existing pool information, including delegation levels, fees, and performance metrics.

The Calidus ID field dey available on Cardanoscan profiles for pools wey get registered credentials. Operators wey never register key fit use compatible tooling and the authorization procedure wey CIP-151 define to make their credentials publicly verifiable.