runtimeverification / runtimeverification/haskell-backend
Claim not applied
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
At step 2, claim 1 is not applied. I think that it should be applied, and small changes to seemingly unrelated things in the claim or the starting configuration make things work. However, I didn't manage to minimize it enough to actually understand what happens.
- The proof should not pass
- The only expected thing is that, at the second step, claim c1 is applied, perhaps together with normal rules
To reproduce: claim-not-applied.tar.gz
In the repl:
step 2
graph
check that claim c1 was not applied.
Note for myself: the original proof is protocol-correctness/proof/malicious-user/can-be-deleted/proof-can-be-deleted.k
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied claim-not-applied.tar.gz reproduction and run step 2 followed by graph in the REPL. Compare the result with the original proof at protocol-correctness/proof/malicious-user/can-be-deleted/proof-can-be-deleted.k; done means claim c1 is applied at step 2 and the proof does not pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100