Add API method 'getnetwork' #6249
Merged
Conversation
This file contains 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
Don't depend on silent, UI purposed task runner errors if confirmpaymentstarted or confirmpaymentreceived msgs are sent outside the proper context. Throw a FailedPreconditionException instead, and it will be translated into the proper gPRC StatusRuntimeException before being sent to client. For BTC buyers and sellers, block the messaging attempt if the taker deposit tx has not been confirmed. For BTC sellers, block an attempt to send a confirmpaymentreceived message until after receiving a confirmpaymentstarted message has been sent from the buyer.
Replaced by BSQ Swaps, and will be deprecated.
- verifyPaymentSentMsgIsFromBtcBuyerPrecondition - verifyPaymentReceivedMsgIsFromBtcSellerPrecondition - verifyPaymentSentMsgDepositTxConfirmedPrecondition - verifyPaymentReceivedMsgDepositTxConfirmedPrecondition - verifyPaymentReceivedMsgAfterPaymentSentMsgPrecondition Changed a couple of related method names.
- verifyPaymentSentMsgIsFromBtcBuyerPrecondition - verifyPaymentReceivedMsgIsFromBtcSellerPrecondition - verifyPaymentSentMsgDepositTxConfirmedPrecondition - verifyPaymentReceivedMsgDepositTxConfirmedPrecondition - verifyPaymentReceivedMsgAfterPaymentSentMsgPrecondition
This change reverses the server-side sorting of returned altcoin offer lists, to match the UI altcoin offer-book views' price ordering.
Returns name of the BTC network API daemon is connected to. I am working on some Java bot examples in another repo, and want to stop worrying about accidentally simulating trade payments on mainnet, despite all the warnings I add in comments. The 'getnetwork' method allows bots to know what network the API daemon is connected to, and gives API bot devs and users a way to avoid one potential source of costly mistakes. API CLI manpage and apitest case are included in this commit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Returns name of the BTC network API daemon is connected to (
mainnet,testnet3, orregtest).I am working on some Java bot examples in another repo, and want to stop worrying about accidentally simulating trade payments on mainnet, despite all the warnings I add in comments. The
getnetworkmethod allows bots to know what network the API daemon is connected to, and gives API bot devs and users a way to avoid one potential source of costly mistakes.API CLI manpage and apitest case are included in this PR.
Based on #6248, branch
reverse-get-altcoin-offers-list-order.