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 @fuel-ts/asm to support script building using SDK #332

Closed
luizstacio opened this issue Jun 16, 2022 · 0 comments · Fixed by #987
Closed

Create @fuel-ts/asm to support script building using SDK #332

luizstacio opened this issue Jun 16, 2022 · 0 comments · Fixed by #987
Assignees
Labels
feat Issue is a feature

Comments

@luizstacio
Copy link
Member

As an SDK user needing to create app-specific scripts like a multi-call or others, we should be able to build scripts using the fuel-vm supported instructions like what is possible today on the rust SDK that uses https://github.com/FuelLabs/fuel-asm.

This would replace the current solution that uses [build-time solutions to create script binary].

And delivering a good extendability to the fuels-ts SDK users.

Notes;

  • We should keep in mind memoization patterns to avoid rebuilding scripts every time and replace just what is needed.
  • Use fuel-asm input/outputs as specs to create = outputs/

Meta code:

const foo = 2;
const program = [
    Op.CALL("0x10", foo, ....), 
    Op.RET(0x01),
];

Reference: #281

@luizstacio luizstacio added feat Issue is a feature P: medium labels Jun 16, 2022
@luizstacio luizstacio moved this to Todo in Fuel Network Jun 16, 2022
@luizstacio luizstacio changed the title Create e @fuel-ts/asm to support script building using SDK Create @fuel-ts/asm to support script building using SDK Jun 16, 2022
@luizstacio luizstacio removed this from Fuel Network Sep 7, 2022
@camsjams camsjams self-assigned this May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Issue is a feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants