feat/rpc endpoints #783
feat/rpc endpoints #783
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was copy/pasta from Hiro's Stacks API overview page. I replaced the description with something specific to the RPC. I'm not sure if this is accurate / how we should position this against Hiro's API, so take a look and let me know what you think.
Swapped the name of the "Stacks Core RPC API" to "Stacks Node RPC API" Also updated some copy.
|
The copy on the overview page looks good, but we need to update the side bar to read "Stacks Node RPC" instead of "Stacks Core RPC" and I'm not sure where that lives. @ryanwaits Further, is it worth elaborating on this overview page when a developer would want to use the RPC API instead of Hiro's Stacks API? I'm inclined to say no - and that we want to point users to Hiro's Stacks API - but I want to flag that one omission from this overview page in its current form is when a user should use this API instead of ours. |
i dont think so. a better way to handle this would be referencing the right endpoints throughout docs in a contextual manner. like if we are talking about broadcasting a tx with stacks.js, we could also reference how to do it via rpc node api, etc |
What does this PR do?
Adds a new API Reference section for Stacks core RPC endpoints, making a clear distinction between the Stacks Blockchain API.
Ref: #782
v2endpoints inside of Stacks BlockchainAPI