-
Notifications
You must be signed in to change notification settings - Fork 106
dev: replace starknet_crypto::FieldElement
with starknet-types-core
#1233
Comments
This will probably lead us to need to bump Katana as well no? Are we blocked there or would that be possible? |
Yes that's true, just put a blocked tag to remind us that we need to update Katana as well and it's blocked at the moment due to fork issue. |
blocked by #1245 |
I think you can start this whenever you want @eugypalu |
I think this is already work in progress as far as I understood with our week discussions |
Current status of the issue:
|
Can you push a draft pr so that we can check what happens with the update of blockifier? |
Sure, opened: #1296 |
Describe the enhancement request
At the moment, we are using an old version of
starknet-rs
crypto crate. Following the merge of xJonathanLEI/starknet-rs#562, we should migrate to the new version and replace our currentFieldElement
around the codebase with the newFelt
type.This update involves replacing all instances of the
FieldElement
type in our codebase with the newFelt
type introduced in the update.Benefits
The text was updated successfully, but these errors were encountered: