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

JSON-RPC write extension #240

Closed
5 tasks done
Tracked by #249
Mirko-von-Leipzig opened this issue Apr 19, 2022 · 1 comment · Fixed by #266
Closed
5 tasks done
Tracked by #249

JSON-RPC write extension #240

Mirko-von-Leipzig opened this issue Apr 19, 2022 · 1 comment · Fixed by #266
Assignees

Comments

@Mirko-von-Leipzig
Copy link
Contributor

Mirko-von-Leipzig commented Apr 19, 2022

Support sending StarkNet transactions via the JSON-RPC API. This enables node service providers to use a single endpoint (pathfinder) to provide full access to StarkNet. Our implementation should simply pass these requests straight through to the sequencer.

Steps

  • add support in sequencer client
  • add support in JSON-RPC server (this is blocked by having a spec to implement against, but we can start taking an educated guess so long)

Required functions

  • deploy: deploys a starknet contract
  • invoke: invokes a starknet contract's function
  • declare: declares a StarkNet contract class (only available from StarkNet 0.9)

Additional info

The sequencer expects compressed data for a deployed contract's bytecode. We can expect that the caller will do this compression; but it's probably a good idea to document this explicitly in the JSON-RPC spec.

@kkovaacs
Copy link
Contributor

kkovaacs commented Jun 8, 2022

#318 adds support for the missing declare functionality.

@kkovaacs kkovaacs closed this as completed Jun 8, 2022
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 a pull request may close this issue.

2 participants