test(indexer): forged-event regression test for limit placements (#285) #750
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!750
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/285-forged-placement-test"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up on #285. The merged fix added forged-attribution tests for fills and cancels; the acceptance criteria also name placements. Placement is already closed at source (the placement parse paths route through the same reserved
_contract_addresspredicate), but it had no named regression test like fill/cancel.Adds
forged_contract_address_placement_not_attributed_to_victim_pair: a malicious emitter stamps_contract_address=terra1attackerand forgescontract_address=terra1victimpairbefore the action; the test asserts the placement scopes to the attacker, not the victim.Parser forged-attack tests 3/3 (fill, cancel, placement). No closing keyword.
mentioned in issue #285
mentioned in commit
223128fbda