Midnames Dey Test Identity and Domains for Midnight Preprod

Midnames dey build one identity layer wey join decentralized identifiers, verifiable credentials and human-readable domains for Midnight applications.

Builders fit use the stack through SDK, embeddable profiles and domain ownership checks, while Lace dey provide the wallet connection to the wider Cardano ecosystem. The session match working product flows with the technical limits wey still affect production use.

The Identity Wallet Connects DIDs, Devices and Credentials

Midnames long-term goal na to build proof-of-personhood layer for digital environment wey automated accounts and AI agents dey plenty. The current identity wallet first focus on microcredentials, like certificates for completed courses and acquired skills.

The wallet dey use decentralized identifiers, we dem dey call DIDs, and verifiable credentials. Organization fit digitally sign credential, and another party fit verify authenticity without to query the issuer central database.

Midnames talk say the standards-based credentials fit also work for compatible identity wallets, no be to lock dem inside one application.

This structure fit support checks for individual properties, like whether person meet age or compliance requirement, without to dey share full name, address or complete identity record every time.

For the demonstration, dem connect one credential to one DID wey dem deploy for Midnight preprod. Holder key fit get backup, while separate hardware key go remain bind to the mobile device wey issue the credential. Because of this, verifier fit know difference between restored credential and the one wey original device still confirm.

Midnames still add recovery through Google Drive, so users fit restore access to the wallet and stored certificates. The team describe am as usability choice, no be fully decentralized storage design.

Credential verification dey happen for server side for now. Midnames plan to replace that trusted step with zero-knowledge verification when the required circuits fit run for mobile devices. Compact, Midnight smart contract language, dey produce zero-knowledge circuits from contract logic, but the mobile flow wey dem show still rely on the Midnames server.

QR and NFC Bring Credentials Into Physical User Flows

The demonstration show how credential fit dey issue through QR code, confirm with biometric authentication and later check with NFC reader. Issuance fit also start with NFC tap, and Midnames dey develop phone-to-phone verification so businesses no go need dedicated readers for every location. Applications fit require the hardware key when credential must remain bind to im original device.

The team apply the same identity model to one coffee shop loyalty prototype. Customer go register by scanning code, then public key go connect to one DID. Each purchase go add digital stamp, and customer fit redeem reward after e reach the merchant configured threshold.

The QR codes wey dem use to add stamps get time limit and na single-use, to stop customers from reusing screenshot. Merchant interface dey display registrations, issued and redeemed coffees and basic activity data. Midnames talk say dem dey discuss the product with coffee shop owners for Buenos Aires, but the session no identify any live merchant deployment.

The loyalty application keep the DID and contract interactions behind familiar process of scanning, collecting stamps and redeeming reward. E show how the same credential infrastructure fit support educational certificates, verification for physical locations and commercial loyalty programs.

Midnames Opens Its Name Service to Midnight Builders

The Midnames name service don open for external testing for Midnight preprod. E connect human-readable name to wallet or contract address, similar to how internet domain dey replace IP address. Users fit access the application through Lace and im Midnight wallet support.

Each domain get target address and additional fields. The target fit resolve to wallet or smart contract, while the fields fit store profile type, links, application identifiers or other data. Applications fit define how dem go use and display those flexible records.

The team still show Discord integration wey bind token to specific domain name and contract. If person copy am go another domain, e no go reproduce the verified connection because the server dey check where dem originally assign am.

Midnames dey provide SDK and embeddable profile widgets. Application fit resolve domain, inspect im fields or display profile without to build separate naming system. Ownership fit also dey checked by asking user to store designated token inside the domain record and then verifying the corresponding contract update.

The presentation still document current limits. Sometimes the interface no save or display records correctly, one Midnight node dey drop some transactions, and domain transfers no dey available because wallets dey report addresses incorrectly. Midnames expect say transfers go work after dem correct the wallet-side issue, but dem no provide production date.

For the wider Cardano ecosystem, Midnames dey add user layer around Lace and Midnight applications. Builders fit now test domain resolution, profile widgets and application-specific records for preprod, while the wallet and loyalty prototype extend the same DID foundation beyond blockchain addresses.

Naming components don ready for integration testing, but private credential verification still need to move pass the trusted server before Midnames fit deliver the decentralized identity layer wey dem plan.