IntersectMBO/plutus

Specify the exact meaning of "pure" in the PIR optimizer

Open

Aperta il 21 mag 2024

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)Haskell (1637 star) (511 fork)batch import
Good first issueInternalPlutus IRstatus: triaged

Descrizione

We have that PlutusIR.Purity.isPure and its semantics seems to be underspecified. You can see how it causes confusion here for example.

We need to properly specify the semantics of this function and the entire concept of purity. Ideally, even formalize it. Otherwise we may run into a situation where the PIR optimizer changes the behavior of the program potentially introducing a severe bug into the smart contract.

And do we need the same for UPLC?

Guida contributor

Tech stack
Nessuno
Dominio
backend
Tipo issue
research
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
4
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
over 1 week
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Understanding of PIR optimizerFamiliarity with Plutus languageKnowledge of purity in programming languages
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
15
Direzione di ricerca
Examine the function `PlutusIR.Purity.isPure` and its usage in the Plutus codebase. Review the discussion in the linked PR #5093 (https://github.com/input output hk/plutus/pull/5093#discussion r1092117897) to understand the confusion. Specify the semantics of purity for the PIR optimizer, potentially formalizing it, and consider whether the same specification is needed for UPLC.