Releases: blockchain-certificates/cert-verifier-js
Releases · blockchain-certificates/cert-verifier-js
v6.3.0
v6.2.1
v6.2.0
6.2.0 (2022-08-23)
Bug Fixes
- Deps: globally replace base58-universal with jest working version (82ecd2e)
- Ed25519: retrieve issue public key after did key provider change (a84c638)
- Node: prevent require to old core-js path from old jsonld dep (cc30950)
Features
- Issuer: allow issuer profile to contain similar information as DID documents (6514908)
- MultiSign: add support for EcdsaSecp256k1Signature2019 (cd3d5c1)
- MultiSign: code verifies in node if deps (base58, secp256k1Verification) are adjusted (a837b24)
- VerificationMethod: handle default DID case (ba02c52)
- Verifier: allow singleton verification of non merkleproof documents (40f755e)
v6.1.0
v6.0.2
v6.0.1
v6.0.0
6.0.0 (2022-06-13)
Bug Fixes
- Deps: point to fork packages with 'main' fallback property as entry point (4890206)
- DidResolver: update default did resolver address (41e5cc2)
- Mocknet: prevent failure on mocknet and regtest (57f526a)
- MultiSign: prevent failure when data is undefined (0343d9b)
- Types: correct import path (c77f1f6)
- Verification: make verification as expected when only one signature (54b6e3f)
- VerificationProcess: do not verify identity if no did (de989d2)
- Verifier: use correct method for expected value (4606aaf)
Features
- DID: expand issuer profile from did:key (1577437)
- MultiSign: abstract MerkleProof2019 verification from verifier (f846e08)
- MultiSign: add chain to signers object (6e5d70f)
- MultiSign: add issuerName to signers object (71058f1)
- MultiSign: add issuerProfileDomain to signers object (c8983ba)
- MultiSign: add issuerProfileUrl to signers object (5c61038)
- MultiSign: add issuerPublicKey to signers object (3134d67)
- MultiSign: add signatureSuiteType to signers object (5944e13)
- MultiSign: add transactionId to signers object (67afe4e)
- MultiSign: add transactionLink to signers object (52d3821)
- MultiSign: allow for suites to use the same verification substeps. Identify parent suite (be0a76f)
- MultiSign: blockchain anchored certificate MerkleProof2017 verified from proof handler (971b493)
- MultiSign: expose rawTransactionLink to signers (88152d9)
- MultiSign: expose signers object (7dbd8a4)
- MultiSign: fill issuer url and domain for ed25519 (3ab606c)
- MultiSign: fill issuerName for ed25519 (aa59bc5)
- MultiSign: fill issuerPublicKey for ed25519 (13d8a46)
- MultiSign: fill signingDate for ed25519 (61681fe)
- MultiSign: format and internationlize ed25519 verification (83f1c12)
- MultiSign: instantiate supported proof verifiers (5102a46)
- MultiSign: mocknet regtest MerkleProof2017 test passing (20a921c)
- MultiSign: pass individual proof to suite verifier (6d50c99)
- MultiSign: remove properties from certificate as exposed in signers property (90fc079)
- MultiSign: sequentially call signature suites (d0d68dd)
- MultiSign: shape verification steps to match multiple signatures (9a17e75)
- Multisign: update final verification step message for multisigned certs (5582248)
- MultiSign: update issuer profile at suite level if ChainedProof (92cc941)
- MultiSign: verify Ed25519 signed certificate (5c85048)
- MultiSign: verify MerkleProof of proof chain certificate (31dabb2)
- MultiSign: working browser verification (1a2a741)
- ProofChain: define proof as potential array (4cc7f9c)
- PublicKey: re-enable issuer public key availability (4d52891)
- Status: use enum for statuses, include blockcerts-verifier status to the list (e92267a)
- Substeps: define default status (2c4cf4f)
- Verification: actually enable verification of revocation of mocknet/regtest certs (410db60)
- VerificationCallback: expose parent step as part of the callback object (196add2)
- VerificationSteps: expose final object as per contract including signature verification steps (72ec680)
BREAKING CHANGES
- MultiSign: Some properties formerly exposed as first level properties of Certificate are now available through the
Certificate.signers
property. - MultiSign: Globally speaking with MultiSign we have redefined the structure of the verification substeps, which may occur either at the parent step level with
subSteps
(like before) or at the parent step level with the child suite(s) for verifying the various signatures. This means that implementers of a verification flow (as UI or otherwise) now need to read in thesubSteps
property or thesuites
property of theverificationProcess
.