nethermindeth / rpc-request-builder Goto Github PK

Home Page: https://rpc-request-builder.voyager.online/

JavaScript 0.15% CSS 0.30% TypeScript 99.56%

rpc-request-builder's Introduction

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

Next.js Documentation - learn about Next.js features and API.
Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

rpc-request-builder's People

Contributors

Stargazers

Watchers

Forkers

saimeunt prabhat1308 dhirajs0 intldds acecoder7 richa-iitr aryangodara makluganteng abhijay007 aviral10x blazing-mike ash20pk dhruv035 0xcronus gostean xaxxoo

rpc-request-builder's Issues

Implement `starknet.rs` support for call endpoints

Implement autogenerated starknet.rs support for the following endpoints.

starknet_call
starknet_estimateFee
starknet_estimateMessageFee

Additional Context:

Add RPC Request Builder to Madara Tsukuyomi

Implement `starknet.go` support for call endpoints

Implement autogenerated starknet.go code for the following RPC endpoints

starknet_call
starknet_estimateFee
starknet_estimateMessageFee

Additional Context:

Support remove option

The builder currently lets you "Add another option" but there's no way to remove an option. We should include a way to remove an option.

Add missing starknet.js code

The following endpoints have missing starknet.js code

starknet_call
starknet_estimateFee
starknet_estimateMessageFee
starknet_addInvokeTransaction
starknet_addDeclareTransaction
starknet_addDeployAccountTransaction
starknet_simulateTransactions

Implement `starknet.go` support for transaction endpoints

Current State

The RPC Request Builder autogenerates starknet.go code snippets for StarkNet RPC endpoints. However, some endpoints are not yet supported.

Required Action

Add autogenerated starknet.go support for the following endpoints.

starknet_getTransactionStatus
starknet_getTransactionByHash
starknet_getTransactionByBlockIdAndIndex
starknet_getTransactionReceipt
starknet_getBlockTransactionCount
starknet_getEvents

Additional Context:

Implement `starknet.go` support for contract class endpoints

Add autogenerated starknet.go code for the following RPC endpoints

starknet_getClass
starknet_getClassHashAt
starknet_getClassAt

Additional Context:

Implement `starknet.rs` support for block endpoints

Implement autogenerated starknet.rs support for the following endpoints.

starknet_getBlockWithTxHashes
starknet_getBlockWithTxs
starknet_blockNumber
starknet_blockHashAndNumber
starknet_getStateUpdate
starknet_getStorageAt

Additional Context:

Implement `starknet.go` support for trace endpoints

Implement autogenerated starknet.go code for the following RPC endpoints

starknet_traceTransaction
starknet_traceBlockTransactions
starknet_simulateTransactions

Additional Context:

enable entry point selector hash as input

rpc request builder doesn't allow Entry point selector hash to be directly added.

Would appreciate that feature. Now when I enter it, it gets hashed again..

Implement `starknet.rs` support for contract class endpoints

Implement autogenerated starknet.rs support for the following endpoints.

starknet_getClass
starknet_getClassHashAt
starknet_getClassAt

Additional Context:

API Key and Endpoint State Reset on Page Refresh

Issue Description:

In the rpc-request-builder, there's an issue observed where, upon initially inserting an API key and selecting an endpoint, the functionality works as expected. However, upon refreshing the page, the API key reverts to empty in the input value, and the endpoint reverts to its initial state.

Expected Behavior:

It would be beneficial to maintain the state of the API key and selected endpoint even after a page refresh. This would enhance the user experience by eliminating the need to re-enter information after each refresh.

Steps to Reproduce:

Open the rpc-request-builder.
Input an API key and select an endpoint.
Refresh the page.
Observe that the API key becomes empty, and the endpoint reverts to the initial state.

Additional Information:

Starknet.JSON-RPC.Request.Builder.mp4

cc : @jelilat

Implement starknet.go support for write endpoints

Implement autogenerated starknet.go code for the following RPC endpoints

starknet_addInvokeTransaction
starknet_addDeployAccountTransaction

Additional Context:

Implement `starknet.go` support for block endpoints

Add autogenerated starknet.go code for the following endpoints.

starknet_getBlockWithTxHashes
starknet_getBlockWithTxs
starknet_blockNumber
starknet_blockHashAndNumber
starknet_getStateUpdate
starknet_getStorageAt

Additional Context:

Implement `starknet.rs` support for write endpoints

Implement autogenerated starknet.rs support for the following endpoints.

starknet_addInvokeTransaction
starknet_addDeployAccountTransaction

Additional Context:

Add starknet.go support

The RPC Request Builder currently autogenerates starknet.js code snippets for each Starknet RPC endpoint. We need to do the same for starknet.go. The Screenshot below shows an autogenerated code for starknet_specVersion. This should also be done for all the remaining RPC endpoints.