IntersectMBO/plutus

Provide expected result of compress and uncompress builtins for UPLC conformance

Open

#5,814 opened on Mar 2, 2024

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Haskell (511 forks)batch import
BuiltinsGood first issueLow prioritySpecificationstatus: triagedtech debt

Repository metrics

Stars
 (1,637 stars)
PR merge metrics
 (Avg merge 6d 1h) (15 merged PRs in 30d)

Description

Describe the feature you'd like

To facilitate independent implementations of builtins that can not leverage the usage of the same blst dependency used in this repository, it would be useful to provide the expected results of the builtins.

this is not currently the case, especially for builtins expecting bls12_381_G1_element and bls12_381_G2_element arguments like

  • bls12_381_G1_compress
  • bls12_381_G1_uncompress
  • bls12_381_G2_compress
  • bls12_381_G2_uncompress

given that, as per section C.3.4 of the plutus-core-specification pdf; these are always represented in the "uncompressed" form;

This makes it really hard to prove the result of the builtin is the one intended

Describe alternatives you've considered

No response

Contributor guide

Research direction
Investigate the plutus core specification, particularly section C.3.4, to understand the uncompressed representation. Then, based on the existing implementation in the repository (using blst library), compute and document the expected compressed and uncompressed values for G1 and G2 elements. The expected results should be provided in a format that enables independent implementors to verify correctness.
Tech stack
None
Domain
documentation
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
BLS12-381 primitivesPlutus Core specification
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40