Gerard Persoon

Solidity security reviews
@cantinasecurity

[Gerard Persoon @gpersoon]

Congratulations @0xPolygon with your 6 years anniversary, up to the next trillions!
And thanks for the nice gift from https://t.co/tgvXodR20D
P.S. Whatever you do, don't ask your LLM to search for an easter egg

[Polygon | POL @0xPolygon]

$2.5 trillion+ in stablecoin value moved. Translated into things you know.

Explore them at: https://t.co/u3gyDxfdHx

[cmichel @cmichelio]

It's not the end, it's still living on in the LLM data training sets. That's why you see so many zero-address check suggestions and inflated severities. (My feeling is that it has improved with recent models though?)
The very early 2021 days with @0xRajeev @gpersoon @sockdrawermoney were peak fun.

What ruined contests from an SR's POV was:
Fewer real bugs because devs and tooling got a lot better, once foundry came along devs started actually testing their code with high coverage. This led to more (arguably) out-of-scope bug submissions which made the highest-impact move arguing about your own & others' issues. The difference between a high and a medium was not well defined in practice & there were some incompetent judges (sorry). Pool sizes also never kept up with the increase in participants.
In the end, the audit contest payout structure changed so much that many were just pre-deployment bug bounties (different pool size unlocks for H/M).

Ironically, now would be a great time for contests again as everyone is boasting about their AI being the best. Would love to see more real results instead of vagueposting.

[Gerard Persoon @gpersoon]

@rsquare @SafeLabs_ @cantinasecurity

[Gerard Persoon @gpersoon]

@hrkrshnn Microsoft office

[Gerard Persoon @gpersoon]

Cool idea. Why not use the exact bounty amount as liquidity? That removes the uncertainty if the white hat pays back the 90%. And that is the amount that the protocol should reserve anyway.

[RajΞΞv @0xRajeev]

@cyfrin Interesting initiative. Curious:
1. Why will a protocol want to deploy here with real liquidity?
2. Is this meant to replace a protocol's BB?

[Gerard Persoon @gpersoon]

@_weidai Check https://t.co/SxI3V1o9Eb

[Sock @sockdrawermoney]

prompt injection is social engineering for software.

we've long given up trying to harden humans. instead we built systems that assume people will be fooled.

we haven't done this for LLMs. not really.

here's why and how we can close the gap:

[Gerard Persoon @gpersoon]

Cool idea by @sockdrawermoney : Label data, enforce policies to manage AI security & prompt injections. See https://t.co/6LCidT0xcC https://t.co/AMAK2ofJOh

[Sock @sockdrawermoney]

I've spent every day for the last 14 months building a language for scripting LLMs because I believe we need new primitives to defend against prompt injection.

Here's why:

https://t.co/6EKVdbb1jt

[Gerard Persoon @gpersoon]

@taalas_inc Wow, this is extremely fast inference. https://t.co/FWa01zHWnD

[Gerard Persoon @gpersoon]

@thedaofund There is a lot of reinventing the same thing. This could potentially be improved with more generic modules / libraries, which are well tested and reviewed.

[Gerard Persoon @gpersoon]

When you compress the time between intent and finality, you also compress the time between mistake and catastrophe.

[Odysseus | phylax.systems @odysseas_eth]

https://t.co/MHXqfYjkhg

[Gerard Persoon @gpersoon]

@GalloDaSballo See Verifiable Delay Function

[Gerard Persoon @gpersoon]

@mudgen @originary_joe @VALIPOKKANN Changed it a bit to ERC721

[Gerard Persoon @gpersoon]

Cool idea from @iphelix :
Competitive incident response

[Gerard Persoon @gpersoon]

@p_misirov @zigtur @Montyly @GalloDaSballo @AliceAndB0b What happened before:

[Gerard Persoon @gpersoon]

@p_misirov @zigtur @Montyly @GalloDaSballo @AliceAndB0b Wow

[Gerard Persoon @gpersoon]

Vitalik on Why trustlessness now? @trustlessconf

[Gerard Persoon @gpersoon]

Vitalik on Why trustlessness now? @trustlessconf

[Gerard Persoon @gpersoon]

Vitalik explaining the blockchain