Skip to content

Introduce scenario bundles for multi-transaction attack workflows #68

Description

@knytcomics-ui

Category

Advanced

Summary

Add a versioned scenario format grouping ordered transactions, destinations, labels, and expected warning outcomes.

Current Behavior

Fixtures represent isolated destinations and individual unsigned transactions; notes describe behavior but do not encode sequences.

Problem

The corpus cannot test risk patterns that emerge across timing, funding relationships, and state transitions.

Why This Matters

Behavior-level scenarios are required to evaluate sweeps, phishing drainers, and rug pulls realistically.

Proposed Scope

Define scenario metadata, participant references, ordered transaction steps, expected state transitions, and a deterministic replay/validation command.

Acceptance Criteria

  • A documented scenario schema exists.
  • References and ordering are validated.
  • At least one attack sequence is executable.
  • Expected warning points are machine-checkable.
  • Existing point fixtures remain compatible.

Technical Considerations

Coordinate destinations, scores, transactions, and research evaluation; retain synthetic-only semantics.

Testing Requirements

Test missing references, duplicate steps, incomplete scenarios, and outcome mismatches.

Cross-Repository Impact

Research runner, extension integration tests, and adapter loading.

Out of Scope

Do not build a live indexer.

Complexity

New data model, validator, replay semantics, and consumers.

Impact

Critical — enables behavior-level fraud evaluation.

Suggested Labels

advanced, area: fixtures, area: testing, area: cross-repo

Metadata

Metadata

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardThird CampaignCampaign: Third CampaignadvancedRequires deep domain knowledge or cross-repo contextarea: cross-repoContracts with sibling Gryd-lock reposarea: fixturesDestination and transaction fixture coveragearea: testingTest infrastructureenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions