We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem statement Currently TAP Agent ignores payment faults.
Expectation proposal Faults can be invalid receipts (wrong value, receipt replay, etc), invalid RAVs, or aggregation denial.
For each type of fault, criteria should be determined for deciding when to stop doing business with a problematic sender.
The signal to reject a sender should be communicated promptly to the service instances for it to be effective.
service
EDIT: Sender denial move to issue #103
Additional context
indexer-rs/tap-agent/src/tap/sender_allocation_relationship.rs
Lines 324 to 325 in 1178c63
The text was updated successfully, but these errors were encountered:
aasseman
Successfully merging a pull request may close this issue.
Problem statement
Currently TAP Agent ignores payment faults.
Expectation proposal
Faults can be invalid receipts (wrong value, receipt replay, etc), invalid RAVs, or aggregation denial.
For each type of fault, criteria should be determined for deciding when to stop doing business with a problematic sender.The signal to reject a sender should be communicated promptly to theservice
instances for it to be effective.EDIT:
Sender denial move to issue #103
Additional context
indexer-rs/tap-agent/src/tap/sender_allocation_relationship.rs
Lines 324 to 325 in 1178c63
The text was updated successfully, but these errors were encountered: