Skip to content

Add invariant validation to compliment policy (Bitcoin)#36

Closed
neavra wants to merge 20 commits intomasterfrom
33-add-invariant-validation-to-compliment-policy
Closed

Add invariant validation to compliment policy (Bitcoin)#36
neavra wants to merge 20 commits intomasterfrom
33-add-invariant-validation-to-compliment-policy

Conversation

@neavra
Copy link
Contributor

@neavra neavra commented Jul 1, 2025

DRAFT - Depends on #35

This PR implements Bitcoin transaction invariant validation to ensure Bitcoin transfers always follow security requirements. This is currently a draft because it depends on vault utilities from PR1. I will rebase it once #35 merges, leaving it here so I dont lose it.

Related Issue: Closes #33
Dependencies: PR #[PR1_NUMBER] (vault utilities must merge first)

Adds transaction invariant validation for Bitcoin to prevent malicious transactions by enforcing that:

  1. Bitcoin transactions follow expected structure patterns (e.g. 1 input, 2 output for transfers, can be expanded)
  2. Change outputs always go back to sender (derived from vault)

Core Implementation

  • Add ValidateInvariants method to Chain interface
  • Implement Bitcoin validation logic with two checks:
    • checkTransactionStructure: Validates transaction has 1-2 outputs
    • validateChangeOutput: Ensures change goes to vault-derived address
  • Add Ethereum stub no implementation yet

Engine Integration

  • Call ValidateInvariants in Engine.Evaluate after policy rules match
  • Add vault parameter to Evaluate method signature
  • Fail transaction if invariants don't pass, even if policy allows it

Test: One input One output, should pass. To test the validation of the change output is more complex as it also needs the corresponding vult file, refer to engine_test.go

go run cmd/vulticheck/main.go \
  -policy testdata/payroll.json \
  -chain bitcoin \
  -vault testdata/test-vault.vult \
  -password "password" \
  -tx "010000000100000000000000000000000000000000000000000000000000000000000000000000000000ffffffff01404b4c00000000001976a91462e907b15cbf27d5425399ebf6f0fb50ebb88f1888ac00000000"

@neavra neavra linked an issue Jul 1, 2025 that may be closed by this pull request
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 1, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@neavra
Copy link
Contributor Author

neavra commented Jul 27, 2025

Replaced by #51

@neavra neavra closed this Jul 27, 2025
@neavra neavra deleted the 33-add-invariant-validation-to-compliment-policy branch July 27, 2025 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add invariant validation to compliment policy

1 participant