-
Notifications
You must be signed in to change notification settings - Fork 777
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
RPC endpoint adaptation #583
RPC endpoint adaptation #583
Conversation
✅ Deploy Preview for starknetjs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
…-specs), rpc.ts fix coming next
c50587e
to
eb095c5
Compare
Hello @YohanTz, and thank you for contributing. |
Hey @tabaktoni ! I paused this one as I was waiting for your new pathfinder node so I can test everything :) Is it set up now ? |
I think Infura is running the pathfinder 0.5.3, so it should be able to test over there! |
Ok perfect 👍 |
…pc-endpoint-adaptation
Related for local testing: 0xSpaceShard/starknet-devnet#467 |
superseded by #621 |
Motivation and Resolution
Commits from starknet-specs:
felt encoding change - no leading zeros: [#72](felt encoding: no leading zeros starkware-libs/starknet-specs#72)(nothing to change)I can squash commits if preferred!
After starkware-libs/starknet-specs#84 is merged, we should be able to automatically generate the types of the starknet openrpc API but for now we have to modify them manually.
RPC version (if applicable)
0.2.1
Usage related changes
Development related changes
None
Checklist: