Skip to content

feat(oracle): add DRY_RUN mode to log settlements without submitting - #1888

Open
Folashade6788 wants to merge 1 commit into
StellarCheckMate:mainfrom
Folashade6788:fix/issue-1796-enhancement-oracle-service-should-support-a-dry
Open

Folashade6788 wants to merge 1 commit into
StellarCheckMate:mainfrom
Folashade6788:fix/issue-1796-enhancement-oracle-service-should-support-a-dry

Conversation

@Folashade6788

Copy link
Copy Markdown

Overview

This PR adds a DRY_RUN mode to the oracle service. When DRY_RUN=true, the service logs the settlement details it would have submitted, but skips the SorobanClient::submit_result call so no transactions are sent. This is intended for debugging and auditing against a live contract.

Related Issue

Changes

🔧 Configuration

  • [MODIFY] oracle-service/src/config.rs
    • Reads the DRY_RUN environment variable and exposes it on the service config (defaults to disabled).

🚀 Service Runtime

  • [MODIFY] oracle-service/src/main.rs
    • When dry-run is enabled, logs the settlement details and skips the SorobanClient::submit_result call.
    • Normal (non-dry-run) behavior is unchanged.

Verification Results

Tests for the dry-run path were part of the issue's task list but are not included in the changed-file list for this PR, so no test results are claimed here.

Acceptance Criteria Status
DRY_RUN env var is read in config.rs ✅ Implemented in oracle-service/src/config.rs
Settlement details are logged, and submit_result is skipped when enabled ✅ Implemented in oracle-service/src/main.rs
Test asserting no transactions are submitted in dry-run mode ⚠️ Not included in this PR's changed files; needs a follow-up

Closes #1796

@Folashade6788
Folashade6788 force-pushed the fix/issue-1796-enhancement-oracle-service-should-support-a-dry branch from d8b16af to 55fdd75 Compare November 10, 2026 21:53
@drips-wave

drips-wave Bot commented Nov 10, 2026

Copy link
Copy Markdown

Warning

Possible malicious code: please review before merging.

An automated security scan flagged files in this pull request that appear to contain malicious code. Code like this can run automatically when a project is opened in an editor or its dependencies are installed, so it could compromise the machine of anyone who checks out this branch.

Automated scans can be wrong, so this may be a false positive. Maintainers: please review the flagged files carefully before merging, on GitHub in your browser rather than by checking out the branch. The malicious part is often hidden far off to the right of an ordinary-looking line, so scroll sideways through each file.

@Folashade6788: this pull request adds or changes these files, possibly without your knowledge. Malware like this spreads by adding itself to repositories on machines it has infected, so your machine might be compromised. Please undo these changes in this pull request, and don't open or run other projects on that machine until you've checked it.

Flagged files at commit 55fdd75:

Only merge once you're confident these files are safe.

ℹ️ Posted automatically by Drips Wave. Questions? Contact support@drips.network.

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.

Enhancement: oracle service should support a DRY_RUN mode that logs settlements without submitting

1 participant