mempool related url params explained #576
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TymKh
requested review from
odysseus0,
sketsdever,
sukoneck and
zeroXbrock
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Collaborator
|
Incorporated these updates into a larger PR here: #578 If that looks good, we can close this PR in favor of it. |
Collaborator
|
Closing in favor of the linked PR which has been merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Documenting
rpc-endpointfeatures developed for rainbow:useMempool,mempoolRpc,canReverturl parameters to allow proxying txs to mempool and reverting txsThose are probably not so customer facing features, but mostly for wallet integrators. Should we update our
protectbutton with those new fields?