Messages
The module exposes the following messages (d.vcv.v1.Msg, see proto/d/vcv/v1/tx.proto). UpdateParams is restricted
to the module authority (the gov module address). All route- and issuer-management messages must be sent by the
admin of the targeted route.
MsgExtendedProposalTxn
Not a user-submitted message. This is the block-proposer injection: the proposer marshals it and prepends it as the
first transaction of every block (tx[0]). It carries:
vp— the proposer's verifiable presentation, verified byProcessProposalagainst thed.vcv.v1.MsgProcessProposalroute (the VP's disclosedvalidatorclaim must equal the proposer's consensus address).extended_commit_info— the proposer's local view of the previous commit, marshaled as a CometBFTabci.ExtendedCommitInfo. It contains, for every validator, the vote-extension bytes and the validator's consensus-key signature over aCanonicalVoteExtension.ProcessProposalauthenticates this viabaseapp.ValidateVoteExtensions(per-vote signature check, >2/3 total commit power, exact pin against the node's ownProposedLastCommit) before accepting the block. ThePreBlockerre-authenticates the same structure and derives the suspicious-validator counters from it. The proposer is a transport for signed evidence; it adds no judgement of its own. A validator can therefore never be accused of vote-extension bytes it did not sign with its consensus key.
Fields 2 and 3 (vote_extensions, suspicious_validators) are reserved; they carried proposer-derived lists that were
removed as a security fix (finding C3) because proposer-supplied conclusions were unverifiable.
MsgUpdateParamsRequest
Updates the module Params. The sender must be the module authority. Note that max_presentation_len is fixed in
this Dchain version and cannot be changed; only suspicious_threshold is effectively updatable.
MsgAddRouteRequest
Adds a new verification Route for a given route_id. The route_id follows the routeId convention (the gated
message's proto name, optionally suffixed with :<id>, e.g. /d.notary.v1.MsgNotarise:1). The supplied Route carries
the route admin, the RouteType (ROUTE_TYPE_SD_JWT), and the map of issuers with their requirements and
verification materials. Adding a route that already exists fails.
MsgRemoveRouteRequest
Removes an existing Route by route_id. The sender must be the route's admin. Deleting a required route (such as
cosmos.gov.v1.MsgVote:extop) blocks the corresponding transactions rather than ungating them. This can clean up the
orphaned cosmos.staking.v1beta1.MsgCreateValidator:extop route, which has been ignored since v1.0.0-rc.3.
MsgAddIssuerRequirementsRequest
Appends content_requirements and/or extension_requirements for a given issuer on an existing route. The sender
must be the route's admin.
MsgReplaceIssuerRequirementsRequest
Replaces (rather than appends) the content_requirements and/or extension_requirements for an existing issuer on a
route. The sender must be the route's admin.
MsgAddIssuerVerificationMaterialRequest
Adds a single VerificationMaterial (an issuer public key, e.g. a Jwk) for a given issuer on a route. The sender
must be the route's admin.
MsgRotateVerificationMaterialRequest
Replaces all of an issuer's verification_materials with a new list - used to rotate the issuer's signing keys. The
sender must be the route's admin.