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

feat(sozo): add support for v3 transactions #2498

Closed
wants to merge 2 commits into from
Closed

Conversation

lambda-0x
Copy link
Contributor

No description provided.

@kariy
Copy link
Member

kariy commented Oct 7, 2024

not necessarily blocked, but katana is yet to fully support v3 transactions due to no STRK token declared ref #2405

kariy added a commit that referenced this pull request Oct 14, 2024
ref #2498 #2405 

- update the default predeployed account class implementation to OZ `0.17.0` account [preset](/~https://github.com/OpenZeppelin/cairo-contracts/blob/v0.17.0/packages/presets/src/account.cairo)
- rename class constants

is it required to change the account implementation because the version we're using doesn't support transaction version > 1 as seen below:

/~https://github.com/OpenZeppelin/cairo-contracts/blob/6ab91b5cf57d6a7d02f2d5c5abfc7b5712bc8e47/src/account/account.cairo#L75C1-L77C14

technically v3 support is later added in OZ `0.8.1`. so going all the way to `0.17.0` may seem exaggerated, but `0.8.1` is ~8 months old now so better to just use the latest compatible version. tbh i dont exactly know how different `0.17.0` is compared to `0.8.1`.
@glihm
Copy link
Collaborator

glihm commented Oct 17, 2024

@lambda-0x since @kariy merged the STRK token, when core will be merged let's rebase this one to unlock v3.

As @kariy mentioned if by default we could have sozo choosing the token that has balance, it could be great for UX. But we should keep a simple way with a flag to actually chose the token to use if specified by the user.

@glihm
Copy link
Collaborator

glihm commented Oct 31, 2024

@lambda-0x if you still want to tackle this, with the rc.0 should be much simpler for the invoker. Just about how the token fee is carried by the transaction config.

@glihm
Copy link
Collaborator

glihm commented Nov 7, 2024

Simplified in #2650.

@glihm glihm closed this Nov 7, 2024
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

Successfully merging this pull request may close these issues.

3 participants