Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create compiler warning when using StateMachine API #11

Open
zygomeb opened this issue Oct 12, 2021 · 3 comments
Open

Create compiler warning when using StateMachine API #11

zygomeb opened this issue Oct 12, 2021 · 3 comments

Comments

@zygomeb
Copy link

zygomeb commented Oct 12, 2021

Summary

State Machine API isn't usable due to it compiling down to a size too large to submit due to the TX size limit.

Expected behavior

We should be able to use our contract on-chain if we write it using the API.

Additional context

We've known this issue for a while now -- initially discovered by one of our clients.

Solution

Use regular plutus -- And this is what we've been doing instead. If there's no clear warning or notice about the API being unusable then many developers will run into this problem and will have to do costly refactors.

@anton-k
Copy link
Contributor

anton-k commented Oct 14, 2021

We have also run into that

@ak3n
Copy link
Contributor

ak3n commented Oct 18, 2021

Sorry, but the title seems incorrect. The problem is not with the API but with the contract size. I'm closing the issue as there is IntersectMBO/plutus#3582 tracks this problem.

@ak3n ak3n closed this as completed Oct 18, 2021
@zygomeb zygomeb changed the title State Machine API isn't usable Create compiler warning when using StateMachine API Oct 18, 2021
@zygomeb
Copy link
Author

zygomeb commented Oct 18, 2021

@ak3n updated the title given the conversation we've had in DMs :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants