DSS

DSS 2026 / Day 2 / Amber Hall

The Proof Lied: DeFi's Invisible Circuit Exploits

Kalp Shah

5:51 · Recording

Watch on YouTube ↗Open recording viewerOriginal programme entry
Download plain textDownload timestamped JSON

Source: YouTube automatic caption track · Exported 2026-11-16. Timestamps link to the source video. Cue end times were not supplied.

Transcript

0:01So have you guide heard about Zcash or

0:04Zcash vulnerability

0:06which happened in a Zcash anybody?

0:10Yo, so basically it's not expert. It's

0:1330 million you know wipe out by market.

0:17So let's you know deep dive into it.

0:21So

0:22I'm Kalpsha

0:24security researcher at QuillAudit and

0:26have working at

0:28almost 2.5 years.

0:31So

0:33the bug is about the proof verified and

0:35the constraint is missing in a circuit

0:38and and that caused the counterfeiting

0:40bug in a May 2026.

0:43So the bug is about like

0:46you know

0:48the nullifier duplicates

0:51and also the authorized keys duplicates

0:54that makes the bug possible. To

0:56understand that bug we need to

0:58understand a couple few things like a

1:01note. Note is a private coin and a value

1:05that contain the value owner and

1:07randomness and the nullifier that that

1:10is like

1:12the note does not use multiple times

1:14that make sure that

1:17that is like a one note and one

1:19nullifier that make sure and also the

1:22change of the key that create a

1:24nullifier different.

1:27Okay.

1:28So there is a one concept like a k and n

1:32k. The k is authorized key and n k is a

1:35nullifier key. a k

1:38authorized key basically provide how you

1:41can spend the money and the n k is a

1:44nullifier key which we discussed

1:45earlier.

1:46So a k and n k create IVK and with the

1:51multiplier of IVK into the GD which is

1:54which is a base point

1:56you can get p k underscore d.

1:59So this this is

2:01and which is used to you know like while

2:04we explaining the

2:06core part of the bug.

2:08So this is the several checks is

2:12for the ZK bug bug.

2:15All the the checks are in a different

2:18different contracts and the fourth one

2:20is about a k and n k which is about the

2:23private key and the nullifier.

2:26This is very important that create a

2:28issue.

2:29Also this is a vulnerable code

2:32where the creating a bug and if you see

2:35the code the assign

2:37and the you know

2:41assign k create a bug which is

2:44if you think think of it like a table

2:47if

2:48this is like scalar modular

2:52burning curve and that create an issue.

2:55If you see the

2:57table

2:58the verifier proves

3:00the value in the cells but the

3:03prover cannot prove it. So

3:06if you see the

3:08first value of the base which is a

3:11g_d which we see in earlier slide and

3:15also the if you see the last two

3:19cells it's also the three. So there is a

3:22check that first and last

3:26you know

3:27cells are same and there is no check in

3:31the middle of the row

3:32that create an issue.

3:34So what they check

3:36they put any random value

3:38and attacker can get p k _d

3:44exactly that value that they want. So

3:47think of it it's just a nuance. If you

3:49think two raised to the 255

3:54amount this is a very

3:56you know humongous amount of the

3:58possibility of nullifier and authorized

4:01key you can get.

4:05So this is the exploit part. This part

4:08create a fake

4:10nullifier and the below part get you

4:12know

4:13fake AK. So by using that you can create

4:17multiples nullifier and authorized key.

4:20To fix that you must be use

4:24multi copy of

4:26the original B underscore D rather than

4:29copying the copy of the other duplicates

4:33one.

4:34So

4:36the catch of the this issue this issue

4:38is found by the

4:40Taylor which was you know one of the

4:43researcher and this issue is just just

4:46found after the

4:48launching of Opus 4.8.

4:50So the the thing is

4:53thus they use same prompt customized

4:56prompt to the Opus 4.7. They did not

4:59find the issue but after the just launch

5:03Opus 4.8 they find this issues. So the

5:06main catch of this issue is like you

5:09have to continuously you know

5:13added the spikes invariant negative

5:15tests and formal verification. Meanwhile

5:18you add your custom prompts and while

5:21the LLM upgrading their you know

5:25versions you must you know like try

5:30audit that and pull make the skills and

5:34audit that and after the you know

5:37auditing you without any bias you can

5:41try that so that you can get the issues.

5:44Yeah.

5:48Thank you.

Source and accuracy details

Source export SHA256: 67244805dae1d5e1f952f5ab173717eca19e284065c081d4508612ca4e29b07b