Specify the exact meaning of "pure" in the PIR optimizer · IntersectMBO/plutus#6077

(0 comments) (0 reactions) (0 assignees)Haskell (1,637 stars) (511 forks)batch import

Good first issueInternalPlutus IRstatus: triaged

説明

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?

コントリビューターガイド

技術スタック: なし
領域: backend
Issue 種別: research
難度: 4
推定時間: over 1 week
活動状況: stale
明確さ: mostly clear
前提条件: Understanding of PIR optimizerFamiliarity with Plutus languageKnowledge of purity in programming languages
初心者向け度: 15
調査方針: 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.