Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Custom chain IDs cannot be represented #844

Closed
kkovaacs opened this issue Jul 19, 2023 · 0 comments · Fixed by #847
Closed

Custom chain IDs cannot be represented #844

kkovaacs opened this issue Jul 19, 2023 · 0 comments · Fixed by #847
Assignees
@SantiagoPittella
Milestone
0.3.1

Comments

@kkovaacs
Copy link
Contributor

StarknetChainId doesn't allow for arbitrary custom chain IDs.

We know of at least one such custom chain Starkware has created -- so it would be great if there were a way of using custom chain IDs (a chain ID is a just a felt value, after all).
@SantiagoPittella SantiagoPittella mentioned this issue Jul 19, 2023
Merged
5 tasks
@SantiagoPittella SantiagoPittella self-assigned this Jul 19, 2023
@juanbono juanbono added this to the 0.3.1 milestone Jul 20, 2023
@juanbono juanbono moved this to In Review in Starknet Jul 20, 2023
@github-project-automation github-project-automation bot moved this from In Review to Done in Starknet Jul 20, 2023
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees

@SantiagoPittella SantiagoPittella

Labels
None yet
Projects
Starknet
Status: Done
Milestone
0.3.1
Development

Successfully merging a pull request may close this issue.

use Felt252 for chain ids lambdaclass/starknet_in_rust
3 participants
@kkovaacs @juanbono @SantiagoPittella