mlabs-haskell / mlabs-haskell/cem-script

Better checks and error messages on L1 connection

Open
#71 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backends
Dominant language
Haskell
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

Description

TODO:

  • Catch Network.Socket.connect errors: no rights or socket not existing
  • Check slot number is not stall and overall correct
  • Check Plutus and Era match

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the L1 connection around Network.Socket.connect and identify where the slot number, Plutus version, and Era are checked. Review how connection failures and invalid values are currently surfaced. Done means the listed socket, slot, Plutus, and Era failures produce clear errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
blockchain, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.