Welcome to the next crypto level
← Nexorena

Blockchain

Ethereum prototype separates attestations within one nontransferable credential

On November 13, the author of an Ethereum Magicians proposal published a first implementation. It supports multiple records within one credential, with separate authorities and revisions.

Nexorena Editorial Team

Ethereum prototype separates attestations within one nontransferable credential

One credential can hold multiple independent registers

An Ethereum Magicians contributor announced on November 13, 2026, that they had published a prototype for a nontransferable digital credential. The design lets one token hold multiple registers, such as community contributions and training attestations. Each register keeps its own state and revision. The authority that recognizes a contribution in one register does not automatically gain the ability to change attestations in another.

The prototype uses an ERC-721 token permanently locked under ERC-5192. The holder can burn the token, but its identifier will not be reused. An interface lets users read the accepted state and its governing policy, then submit an update. Separate registers allow an application to consult only the categories it needs. The interface sets no common scoring rules for recorded activities or qualifications.

Updates must start from the correct revision

When an update is submitted, the contract checks the revision and hash of the previous state, the request deadline and the required authorizations. In this first version, an issuer authorizes adding or correcting an attestation. A register controller authorizes initialization and certain management operations. Initialization also requires the holder’s consent. Authorizations are bound to the contract and network to prevent a signature from being replayed on another deployment.

A correction appends a record and preserves the original. It retains the identifier of the underlying experience, so a new attestation identifier alone cannot count the same activity twice. The published version limits each register to 32 records per credential, including corrections. Once the limit is reached, no attestations can be added or corrected in that register. Lifecycle operations remain available.

The prototype uses public data

The documentation says the evidence submitted to the contract, states and events are observable. A content hash alone does not make the content confidential. Signature checks establish that the designated authority approved an update. Verifying activity on another protocol would require additional rules or tools. Deduplication applies within a register and does not establish that the credential holder is unique.

The author says the initial version passed 51 tests, including cases involving competing updates and replayed authorizations. The code is presented as an experimental reference. Private qualification checks, independent revocation of individual attestations and one-time entitlement consumption are among the functions still to be developed. The interface may change in response to feedback on the first version.

Written with love byEthan BrooksMeet this editorial pen name ↗

Explorer Nexorena