Skip to content

Conversation

@the-headless-ghost
Copy link
Member

@the-headless-ghost the-headless-ghost commented Jan 15, 2026

List of changes

Closes #13

Checklist

  • related issue
  • My changes generate no new warnings
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works

Comment on lines +1 to +10
{-# LANGUAGE BangPatterns #-}
{-# LANGUAGE BlockArguments #-}
{-# LANGUAGE DerivingVia #-}
{-# LANGUAGE LambdaCase #-}
{-# LANGUAGE NamedFieldPuns #-}
{-# LANGUAGE ScopedTypeVariables #-}
{-# LANGUAGE TupleSections #-}
{-# OPTIONS_GHC -Wno-unrecognised-pragmas #-}

module DMQ.SigSubmission.Inbound.Decision
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can't we re-use the original decision logic?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had intended to reuse the original decision logic, but a type change required me to duplicate the entire implementation.

coot and others added 11 commits January 19, 2026 09:31
Verify that `Sig` encoding produces a valid CBOR.
`SigSubmissionV2` protocol based on `ObjectDiffusion` from Peras.  The
client requests signatures while the server provides them (dual to
`TxSubmission`).  The patch provides:

* protocol definition and GADT wrappers
* CBOR codec
* cddl specification checked against the codec
* codec provides valid CBOR encoding (checked as a regular QC test
  rather than with the `cddl` tool)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

SigSubmission node-to-node mini-protocol

3 participants