Hi Neil, thanks for the candid feedback and for taking the time to review the project.
I completely own the misrepresentations regarding the “proprietary” framing. I let the narrative drift into an adversarial tone that doesn’t reflect the open-source reality of Bark. I’ve added an Author’s Note to the Delving post acknowledging this, updated the naming, and rewritten the vpack README to focus on the core technical problem of lightweight no_std parsing for hardware wallets.
I just posted a more detailed reply over on the Delving thread regarding your points on mempool policy and CPFP.
I strongly believe a neutral, ultra-lightweight parser is important for the L2 ecosystem, and I’d love to continue the technical discussion over on Delving to make sure vpack accurately supports Bark’s architecture. Thanks again to the whole team for the rigorous review.