sripwoud
sripwoud
@nikitakent It seems you have built something already, haven't you? @vplasencia would https://github.com/nikitakent/semaphore-court-app close this issue (didn't try to run it or review it in details)
Can I take this?
@baumstern
> Before I open a PR, I like to make sure everything's checked out by testing different sections—like circuits and contracts—with some dummy changes in my forked repo. Typically, I'll...
I had a few mistakes in the workflow files that I fixed in the last commits. These workflows triggered on branches with fake changes demonstrate the expected behavior (what should...
> I'd say another review should be ok to merge. @baumstern how does it look?
Let's merge this before #757
Can you assign this to me? I would mirror what I did in https://github.com/privacy-scaling-explorations/zk-kit/pull/235
There are 2 different issues in that test(s): - Timeout for the proof generation: Increasing timeout can probably fix it. But I think the root cause is related to https://github.com/privacy-scaling-explorations/zk-kit/issues/280#issuecomment-2092459053...
I am not sure whether the failing test is related to my PR? https://github.com/semaphore-protocol/semaphore/actions/runs/8925027515/job/24512736232#step:7:426 Looks like a matchtick install/config error no?