You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
following #1284 we have an anvil node that acts as the settlement layer used with Katana.
in .katana/messaging_config.json we hardcoded the address of the StarknetMessaging contract - but it would be better to, in the docker-compose, deploy the StarknetMessaging and L1KakarotMessaging contracts and put them in the .env to make it more robust.
The text was updated successfully, but these errors were encountered:
## Pull request type
Please check the type of change your PR introduces:
- [ ] Bugfix
- [x] Feature
- [ ] Code style update (formatting, renaming)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] Documentation content changes
- [ ] Other (please describe):
## What is the current behavior?
Accounts have their own implementation and needs to be upgraded when
Kakarot is.
Resolveskkrt-labs#1280Resolveskkrt-labs#1275
## What is the new behavior?
Accounts class is never updated and is a transparent proxy. Each call to
the account starts by fetching
the current implementation in Kakarot, then make a `library_call`.
<!-- Reviewable:start -->
- - -
This change is [<img src="https://reviewable.io/review_button.svg"
height="34" align="absmiddle"
alt="Reviewable"/>](https://reviewable.io/reviews/kkrt-labs/kakarot/1285)
<!-- Reviewable:end -->
---------
Co-authored-by: enitrat <[email protected]>
no, this is still relying on the dynamic addresses deployed on the anvil node. As long as the order of deployment and the key account used to deploy are the same, this is not an issue because they will always have the same addresses.
following #1284 we have an anvil node that acts as the settlement layer used with Katana.
in .katana/messaging_config.json we hardcoded the address of the StarknetMessaging contract - but it would be better to, in the docker-compose, deploy the StarknetMessaging and L1KakarotMessaging contracts and put them in the .env to make it more robust.
The text was updated successfully, but these errors were encountered: