mlabs-haskell / mlabs-haskell/bot-plutus-interface
Direct connection
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 21
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we mostly use this project to deploy a pab for a bot, and have the bot only call said pab on the same machine.
I propose some way of having a haskell bot interact with the project directly, rather than risking http access externally.
Bots usually just need a way to run a contract, and see state changes. We could model this as some sort of runContract :: PABConfig -> Contract w s e a -> (StateChange -> IO ()) -> IO () passing a state handler in.
@gege251 Thoughts?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing PAB deployment and bot interaction paths, then define the direct-call API and state-change handling with maintainers; done is a reviewed design and an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100