Most electronic signing proves someone had access to an email account. That is a low bar for a document that moves money, transfers property or commits a company.
Sign binds the signature to a cryptographically verified identity, presented from the signer's wallet, on their own device.
The wallet is the secure file vault for signed documents. Signing and holding belong together on the holder side rather than in a separate service that keeps a copy of everything you ever agreed to.
The signer presents a verified credential from the wallet. The same wallet then holds the signed document. One place proves the identity, and one place keeps the artefact.
The signer presents a verified credential and signs with a device-bound key. The identity is proven at the moment of signing, not assumed from an inbox.
Resolve confirms the signer holds the authority the document requires. Being logged in is not the same as being allowed.
How Resolve decidesMultiple signers in order, with each earlier signature preserved intact under the next.
The signed document is held on the holder side, in the same wallet that proved the identity.
The KeyFlux walletWhat was signed, by whom, with which credential, and when.
Advanced and simple electronic signatures are supported today.
Corporate authority and delegated approval. Customer agreements that currently need a branch visit. Field service sign-off. Anything where the question after the fact is not "did someone sign" but "was that person allowed to".
Sign is a function of the wallet, and the wallet is part of Verifiable Credential Core. Core issues and verifies the credential the signer presents. Resolve decides whether that signer holds the authority the document requires.
Sign becomes a standalone product once it verifies mDLs and other government and enterprise credentials from multiple issuers. That is the direction, not a date. Today Sign is part of Core, on the holder side.
If the question after the fact is whether the signer was allowed to sign, we should talk.
Request a Demo