Skip to content

PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631

Open
Open
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631

Description

@anjor
anjor
opened on Feb 27, 2026

Summary

I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.

This issue captures the full reproduction, exact chain evidence, and the fixes that were required.

Environment

  • Date: 2026-02-27
  • Repo: data-preservation-programs/singularity
  • Network: calibnet
  • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
  • DB used: singularity_v2
  • Wallet used:
    • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
    • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De

Repro Timeline and Findings

1) createDataSet sybil fee gate

Initial schedule execution failed with:

  • revert reason=[Error(sybil fee not met)]

This required sending value in CreateProofSet.

2) createDataSet listener behavior mismatch

After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....

In local probing:

  • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
  • listener=0x000...000 + value >= 1 FIL => estimate succeeds

3) addPieces failed due fixed gas cap path

Observed failed tx:

  • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
  • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
  • Receipt status: 0x0
  • Filecoin receipt: ExitCode=7, GasUsed=5000000

This matched a hard gas-limit path (5_000_000) in local adapter code.

4) CommPv2 compatibility gap in validations

PDP contract rejected legacy piece CID with:

  • Error(Cid must be CommPv2)

But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:

  • dataprep add-piece validation
  • schedule create/update allowed-piece-cid validation

5) Schedule state / metadata behavior

A completed schedule retained prior error_message text, which is confusing for operational status.

Successful On-Chain Evidence (after fixes/workarounds)

Proof set created:

  • set_id=11849

DataSetCreated:

  • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
  • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
  • Receipt: status=0x1, block 0x355a3c (3496508)

PiecesAdded:

  • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
  • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
  • Receipt: status=0x1, block 0x355a90 (3496592)
  • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3

Final Singularity state:

  • schedule_id=2 => completed
  • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)

Local Changes That Unblocked E2E

  • service/dealpusher/pdp_onchain.go
    • include value on CreateProofSet
    • listener handling change for createDataSet
    • switched add-roots submission to manager path (gas estimation-based)
  • added CID compatibility helper + wired validation sites:
    • util/piececid.go
    • handler/dataprep/piece.go
    • handler/deal/schedule/create.go
    • handler/deal/schedule/update.go

Requested Fixes

  1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
  2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
  3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
  4. Clear or segregate stale error_message once schedule transitions to completed.
  5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.

Reference

I also wrote a runbook with exact commands and outputs:

  • docs/en/topics/pdp-calibnet-e2e.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
       blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
      Skip to content
      PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
      Open
      Open
      PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
      Description
      @anjor
      anjor
      opened on Feb 27, 2026
      Summary
      I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
      This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
      Environment
      • Date: 2026-02-27
      • Repo: data-preservation-programs/singularity
      • Network: calibnet
      • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
      • DB used: singularity_v2
      • Wallet used:

        • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
        • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
      Repro Timeline and Findings
      1) createDataSet sybil fee gate
      Initial schedule execution failed with:
      • revert reason=[Error(sybil fee not met)]
      This required sending value in CreateProofSet.
      2) createDataSet listener behavior mismatch
      After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
      In local probing:
      • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
      • listener=0x000...000 + value >= 1 FIL => estimate succeeds
      3) addPieces failed due fixed gas cap path
      Observed failed tx:
      • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
      • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
      • Receipt status: 0x0
      • Filecoin receipt: ExitCode=7, GasUsed=5000000
      This matched a hard gas-limit path (5_000_000) in local adapter code.
      4) CommPv2 compatibility gap in validations
      PDP contract rejected legacy piece CID with:
      • Error(Cid must be CommPv2)
      But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
      • dataprep add-piece validation
      • schedule create/update allowed-piece-cid validation
      5) Schedule state / metadata behavior
      A completed schedule retained prior error_message text, which is confusing for operational status.
      Successful On-Chain Evidence (after fixes/workarounds)
      Proof set created:
      • set_id=11849
      DataSetCreated:
      • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
      • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
      • Receipt: status=0x1, block 0x355a3c (3496508)
      PiecesAdded:
      • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
      • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
      • Receipt: status=0x1, block 0x355a90 (3496592)
      • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
      Final Singularity state:
      • schedule_id=2 => completed
      • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
      Local Changes That Unblocked E2E
      • service/dealpusher/pdp_onchain.go
        • include value on CreateProofSet
        • listener handling change for createDataSet
        • switched add-roots submission to manager path (gas estimation-based)
      • added CID compatibility helper + wired validation sites:

        • util/piececid.go
        • handler/dataprep/piece.go
        • handler/deal/schedule/create.go
        • handler/deal/schedule/update.go
      Requested Fixes
      1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
      2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
      3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
      4. Clear or segregate stale error_message once schedule transitions to completed.
      5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
      Reference
      I also wrote a runbook with exact commands and outputs:
      • docs/en/topics/pdp-calibnet-e2e.md
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        No labels
        No labels
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
          Skip to content
          PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
          Open
          Open
          PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
          Description
          @anjor
          anjor
          opened on Feb 27, 2026
          Summary
          I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
          This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
          Environment
          • Date: 2026-02-27
          • Repo: data-preservation-programs/singularity
          • Network: calibnet
          • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
          • DB used: singularity_v2
          • Wallet used:

            • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
            • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
          Repro Timeline and Findings
          1) createDataSet sybil fee gate
          Initial schedule execution failed with:
          • revert reason=[Error(sybil fee not met)]
          This required sending value in CreateProofSet.
          2) createDataSet listener behavior mismatch
          After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
          In local probing:
          • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
          • listener=0x000...000 + value >= 1 FIL => estimate succeeds
          3) addPieces failed due fixed gas cap path
          Observed failed tx:
          • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
          • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
          • Receipt status: 0x0
          • Filecoin receipt: ExitCode=7, GasUsed=5000000
          This matched a hard gas-limit path (5_000_000) in local adapter code.
          4) CommPv2 compatibility gap in validations
          PDP contract rejected legacy piece CID with:
          • Error(Cid must be CommPv2)
          But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
          • dataprep add-piece validation
          • schedule create/update allowed-piece-cid validation
          5) Schedule state / metadata behavior
          A completed schedule retained prior error_message text, which is confusing for operational status.
          Successful On-Chain Evidence (after fixes/workarounds)
          Proof set created:
          • set_id=11849
          DataSetCreated:
          • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
          • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
          • Receipt: status=0x1, block 0x355a3c (3496508)
          PiecesAdded:
          • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
          • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
          • Receipt: status=0x1, block 0x355a90 (3496592)
          • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
          Final Singularity state:
          • schedule_id=2 => completed
          • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
          Local Changes That Unblocked E2E
          • service/dealpusher/pdp_onchain.go
            • include value on CreateProofSet
            • listener handling change for createDataSet
            • switched add-roots submission to manager path (gas estimation-based)
          • added CID compatibility helper + wired validation sites:

            • util/piececid.go
            • handler/dataprep/piece.go
            • handler/deal/schedule/create.go
            • handler/deal/schedule/update.go
          Requested Fixes
          1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
          2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
          3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
          4. Clear or segregate stale error_message once schedule transitions to completed.
          5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
          Reference
          I also wrote a runbook with exact commands and outputs:
          • docs/en/topics/pdp-calibnet-e2e.md
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            No labels
            No labels
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
              Skip to content
              PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
              Open
              Open
              PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
              Description
              @anjor
              anjor
              opened on Feb 27, 2026
              Summary
              I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
              This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
              Environment
              • Date: 2026-02-27
              • Repo: data-preservation-programs/singularity
              • Network: calibnet
              • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
              • DB used: singularity_v2
              • Wallet used:

                • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
                • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
              Repro Timeline and Findings
              1) createDataSet sybil fee gate
              Initial schedule execution failed with:
              • revert reason=[Error(sybil fee not met)]
              This required sending value in CreateProofSet.
              2) createDataSet listener behavior mismatch
              After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
              In local probing:
              • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
              • listener=0x000...000 + value >= 1 FIL => estimate succeeds
              3) addPieces failed due fixed gas cap path
              Observed failed tx:
              • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
              • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
              • Receipt status: 0x0
              • Filecoin receipt: ExitCode=7, GasUsed=5000000
              This matched a hard gas-limit path (5_000_000) in local adapter code.
              4) CommPv2 compatibility gap in validations
              PDP contract rejected legacy piece CID with:
              • Error(Cid must be CommPv2)
              But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
              • dataprep add-piece validation
              • schedule create/update allowed-piece-cid validation
              5) Schedule state / metadata behavior
              A completed schedule retained prior error_message text, which is confusing for operational status.
              Successful On-Chain Evidence (after fixes/workarounds)
              Proof set created:
              • set_id=11849
              DataSetCreated:
              • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
              • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
              • Receipt: status=0x1, block 0x355a3c (3496508)
              PiecesAdded:
              • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
              • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
              • Receipt: status=0x1, block 0x355a90 (3496592)
              • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
              Final Singularity state:
              • schedule_id=2 => completed
              • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
              Local Changes That Unblocked E2E
              • service/dealpusher/pdp_onchain.go
                • include value on CreateProofSet
                • listener handling change for createDataSet
                • switched add-roots submission to manager path (gas estimation-based)
              • added CID compatibility helper + wired validation sites:

                • util/piececid.go
                • handler/dataprep/piece.go
                • handler/deal/schedule/create.go
                • handler/deal/schedule/update.go
              Requested Fixes
              1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
              2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
              3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
              4. Clear or segregate stale error_message once schedule transitions to completed.
              5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
              Reference
              I also wrote a runbook with exact commands and outputs:
              • docs/en/topics/pdp-calibnet-e2e.md
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                No labels
                No labels
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
                  Skip to content
                  PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
                  Open
                  Open
                  PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
                  Description
                  @anjor
                  anjor
                  opened on Feb 27, 2026
                  Summary
                  I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
                  This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
                  Environment
                  • Date: 2026-02-27
                  • Repo: data-preservation-programs/singularity
                  • Network: calibnet
                  • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
                  • DB used: singularity_v2
                  • Wallet used:

                    • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
                    • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
                  Repro Timeline and Findings
                  1) createDataSet sybil fee gate
                  Initial schedule execution failed with:
                  • revert reason=[Error(sybil fee not met)]
                  This required sending value in CreateProofSet.
                  2) createDataSet listener behavior mismatch
                  After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
                  In local probing:
                  • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
                  • listener=0x000...000 + value >= 1 FIL => estimate succeeds
                  3) addPieces failed due fixed gas cap path
                  Observed failed tx:
                  • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
                  • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
                  • Receipt status: 0x0
                  • Filecoin receipt: ExitCode=7, GasUsed=5000000
                  This matched a hard gas-limit path (5_000_000) in local adapter code.
                  4) CommPv2 compatibility gap in validations
                  PDP contract rejected legacy piece CID with:
                  • Error(Cid must be CommPv2)
                  But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
                  • dataprep add-piece validation
                  • schedule create/update allowed-piece-cid validation
                  5) Schedule state / metadata behavior
                  A completed schedule retained prior error_message text, which is confusing for operational status.
                  Successful On-Chain Evidence (after fixes/workarounds)
                  Proof set created:
                  • set_id=11849
                  DataSetCreated:
                  • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
                  • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
                  • Receipt: status=0x1, block 0x355a3c (3496508)
                  PiecesAdded:
                  • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
                  • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
                  • Receipt: status=0x1, block 0x355a90 (3496592)
                  • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
                  Final Singularity state:
                  • schedule_id=2 => completed
                  • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
                  Local Changes That Unblocked E2E
                  • service/dealpusher/pdp_onchain.go
                    • include value on CreateProofSet
                    • listener handling change for createDataSet
                    • switched add-roots submission to manager path (gas estimation-based)
                  • added CID compatibility helper + wired validation sites:

                    • util/piececid.go
                    • handler/dataprep/piece.go
                    • handler/deal/schedule/create.go
                    • handler/deal/schedule/update.go
                  Requested Fixes
                  1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
                  2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
                  3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
                  4. Clear or segregate stale error_message once schedule transitions to completed.
                  5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
                  Reference
                  I also wrote a runbook with exact commands and outputs:
                  • docs/en/topics/pdp-calibnet-e2e.md
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    No labels
                    No labels
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
                      Skip to content
                      PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
                      Open
                      Open
                      PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
                      Description
                      @anjor
                      anjor
                      opened on Feb 27, 2026
                      Summary
                      I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
                      This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
                      Environment
                      • Date: 2026-02-27
                      • Repo: data-preservation-programs/singularity
                      • Network: calibnet
                      • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
                      • DB used: singularity_v2
                      • Wallet used:

                        • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
                        • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
                      Repro Timeline and Findings
                      1) createDataSet sybil fee gate
                      Initial schedule execution failed with:
                      • revert reason=[Error(sybil fee not met)]
                      This required sending value in CreateProofSet.
                      2) createDataSet listener behavior mismatch
                      After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
                      In local probing:
                      • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
                      • listener=0x000...000 + value >= 1 FIL => estimate succeeds
                      3) addPieces failed due fixed gas cap path
                      Observed failed tx:
                      • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
                      • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
                      • Receipt status: 0x0
                      • Filecoin receipt: ExitCode=7, GasUsed=5000000
                      This matched a hard gas-limit path (5_000_000) in local adapter code.
                      4) CommPv2 compatibility gap in validations
                      PDP contract rejected legacy piece CID with:
                      • Error(Cid must be CommPv2)
                      But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
                      • dataprep add-piece validation
                      • schedule create/update allowed-piece-cid validation
                      5) Schedule state / metadata behavior
                      A completed schedule retained prior error_message text, which is confusing for operational status.
                      Successful On-Chain Evidence (after fixes/workarounds)
                      Proof set created:
                      • set_id=11849
                      DataSetCreated:
                      • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
                      • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
                      • Receipt: status=0x1, block 0x355a3c (3496508)
                      PiecesAdded:
                      • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
                      • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
                      • Receipt: status=0x1, block 0x355a90 (3496592)
                      • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
                      Final Singularity state:
                      • schedule_id=2 => completed
                      • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
                      Local Changes That Unblocked E2E
                      • service/dealpusher/pdp_onchain.go
                        • include value on CreateProofSet
                        • listener handling change for createDataSet
                        • switched add-roots submission to manager path (gas estimation-based)
                      • added CID compatibility helper + wired validation sites:

                        • util/piececid.go
                        • handler/dataprep/piece.go
                        • handler/deal/schedule/create.go
                        • handler/deal/schedule/update.go
                      Requested Fixes
                      1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
                      2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
                      3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
                      4. Clear or segregate stale error_message once schedule transitions to completed.
                      5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
                      Reference
                      I also wrote a runbook with exact commands and outputs:
                      • docs/en/topics/pdp-calibnet-e2e.md
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        No labels
                        No labels
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
                          Skip to content
                          PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
                          Open
                          Open
                          PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
                          Description
                          @anjor
                          anjor
                          opened on Feb 27, 2026
                          Summary
                          I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
                          This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
                          Environment
                          • Date: 2026-02-27
                          • Repo: data-preservation-programs/singularity
                          • Network: calibnet
                          • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
                          • DB used: singularity_v2
                          • Wallet used:

                            • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
                            • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
                          Repro Timeline and Findings
                          1) createDataSet sybil fee gate
                          Initial schedule execution failed with:
                          • revert reason=[Error(sybil fee not met)]
                          This required sending value in CreateProofSet.
                          2) createDataSet listener behavior mismatch
                          After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
                          In local probing:
                          • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
                          • listener=0x000...000 + value >= 1 FIL => estimate succeeds
                          3) addPieces failed due fixed gas cap path
                          Observed failed tx:
                          • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
                          • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
                          • Receipt status: 0x0
                          • Filecoin receipt: ExitCode=7, GasUsed=5000000
                          This matched a hard gas-limit path (5_000_000) in local adapter code.
                          4) CommPv2 compatibility gap in validations
                          PDP contract rejected legacy piece CID with:
                          • Error(Cid must be CommPv2)
                          But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
                          • dataprep add-piece validation
                          • schedule create/update allowed-piece-cid validation
                          5) Schedule state / metadata behavior
                          A completed schedule retained prior error_message text, which is confusing for operational status.
                          Successful On-Chain Evidence (after fixes/workarounds)
                          Proof set created:
                          • set_id=11849
                          DataSetCreated:
                          • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
                          • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
                          • Receipt: status=0x1, block 0x355a3c (3496508)
                          PiecesAdded:
                          • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
                          • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
                          • Receipt: status=0x1, block 0x355a90 (3496592)
                          • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
                          Final Singularity state:
                          • schedule_id=2 => completed
                          • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
                          Local Changes That Unblocked E2E
                          • service/dealpusher/pdp_onchain.go
                            • include value on CreateProofSet
                            • listener handling change for createDataSet
                            • switched add-roots submission to manager path (gas estimation-based)
                          • added CID compatibility helper + wired validation sites:

                            • util/piececid.go
                            • handler/dataprep/piece.go
                            • handler/deal/schedule/create.go
                            • handler/deal/schedule/update.go
                          Requested Fixes
                          1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
                          2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
                          3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
                          4. Clear or segregate stale error_message once schedule transitions to completed.
                          5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
                          Reference
                          I also wrote a runbook with exact commands and outputs:
                          • docs/en/topics/pdp-calibnet-e2e.md
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            No labels
                            No labels
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases · Issue #631 · data-preservation-programs/singularity · GitHub
                              Skip to content
                              PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases #631
                              Open
                              Open
                              PDP calibnet E2E: CommPv2 validation gaps, addPieces gas-limit failure, and listener/createDataSet edge cases#631
                              Description
                              @anjor
                              anjor
                              opened on Feb 27, 2026
                              Summary
                              I ran a full PDP calibnet E2E flow with Singularity and found multiple blockers/inconsistencies. I was able to complete a successful on-chain run after local code and config changes, but the current UX/path has several sharp edges.
                              This issue captures the full reproduction, exact chain evidence, and the fixes that were required.
                              Environment
                              • Date: 2026-02-27
                              • Repo: data-preservation-programs/singularity
                              • Network: calibnet
                              • PDPVerifier: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
                              • DB used: singularity_v2
                              • Wallet used:

                                • delegated: t410fmcffelu4okurnsxqcs352bgqmvxww566spsdeii
                                • EVM: 0x608a522E9C72a916CAF014b7dD04D0656f6B77De
                              Repro Timeline and Findings
                              1) createDataSet sybil fee gate
                              Initial schedule execution failed with:
                              • revert reason=[Error(sybil fee not met)]
                              This required sending value in CreateProofSet.
                              2) createDataSet listener behavior mismatch
                              After sending value, createDataSet still reverted (no reason) when listener was set to EOA 0x608a....
                              In local probing:
                              • listener=0x608a... + value >= 1 FIL => revert at contract path (no reason)
                              • listener=0x000...000 + value >= 1 FIL => estimate succeeds
                              3) addPieces failed due fixed gas cap path
                              Observed failed tx:
                              • Eth tx: 0x86fbed6d5ac86716992761880da64b52702caf5c7425c5e1bc7d3781af0cb60d
                              • Message CID: bafy2bzacec33cynncg55yfyxaj5tv4kdswu26drdxabxsqug7crtmtfop6lze
                              • Receipt status: 0x0
                              • Filecoin receipt: ExitCode=7, GasUsed=5000000
                              This matched a hard gas-limit path (5_000_000) in local adapter code.
                              4) CommPv2 compatibility gap in validations
                              PDP contract rejected legacy piece CID with:
                              • Error(Cid must be CommPv2)
                              But CLI/API validation paths for piece CIDs only accepted cid.FilCommitmentUnsealed (“commp”), which prevented using CommPv2 CIDs in normal flows:
                              • dataprep add-piece validation
                              • schedule create/update allowed-piece-cid validation
                              5) Schedule state / metadata behavior
                              A completed schedule retained prior error_message text, which is confusing for operational status.
                              Successful On-Chain Evidence (after fixes/workarounds)
                              Proof set created:
                              • set_id=11849
                              DataSetCreated:
                              • Eth tx: 0xb0c98f4d18f401c8d4aeb0042887ae1dea0f74f71a5fd003b51501cdd74f7576
                              • Msg CID: bafy2bzacechskzxpw7krv3tdoi433hfipqgjczr3ncvztrqfrdpg6qdmbso4k
                              • Receipt: status=0x1, block 0x355a3c (3496508)
                              PiecesAdded:
                              • Eth tx: 0xb1aacc2469a081743d3a1a8d48af671ff63d5c729422115592e89645e543c7c0
                              • Msg CID: bafy2bzaceaiqtzx2rjcrzskpshqjpowgrkx7jm2r4zkd7ztrflvhtmcmenqzg
                              • Receipt: status=0x1, block 0x355a90 (3496592)
                              • Added piece: bafkzcibd6adqmxxmxtat74d6vqbczd5v3kvg5mdbhtkuawcyfeqvegqd4skzqqy3
                              Final Singularity state:
                              • schedule_id=2 => completed
                              • PDP deal row created (deal_type=pdp, state=proposed, proof_set_id=11849)
                              Local Changes That Unblocked E2E
                              • service/dealpusher/pdp_onchain.go
                                • include value on CreateProofSet
                                • listener handling change for createDataSet
                                • switched add-roots submission to manager path (gas estimation-based)
                              • added CID compatibility helper + wired validation sites:

                                • util/piececid.go
                                • handler/dataprep/piece.go
                                • handler/deal/schedule/create.go
                                • handler/deal/schedule/update.go
                              Requested Fixes
                              1. First-class CommPv2 support in all relevant piece-CID validations for PDP workflows.
                              2. Remove hard fixed gas-limit behavior for addPieces path (or make it adaptive/configurable with safe default).
                              3. Clarify/standardize expected listener address semantics for createDataSet on calibnet/mainnet.
                              4. Clear or segregate stale error_message once schedule transitions to completed.
                              5. (Optional UX) add explicit guidance/docs for PDP CID format requirements and wallet/address expectations.
                              Reference
                              I also wrote a runbook with exact commands and outputs:
                              • docs/en/topics/pdp-calibnet-e2e.md
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                No labels
                                No labels
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions