-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Find push solution for order publishing #1
Labels
Comments
Closed
@ManfredKarrer is this issue still critical for v0.1? |
Nevermind—I was misreading the milestone here as v0.1, when it's actually v1.0. |
ManfredKarrer
changed the title
Use broadcast/multicast for order publishing
Find push solution for order publishing
Nov 29, 2014
Closed
bodymindarts
pushed a commit
to bodymindarts/bisq
that referenced
this issue
Nov 19, 2019
Compilation fixes
sqrrm
pushed a commit
that referenced
this issue
May 26, 2020
This omission is currently not disruptive, since the next case clause only contains a break.
ghubstan
referenced
this issue
in ghubstan/bisq
Jun 13, 2020
This addresses task #1 in issue bisq-network#4257. This new gRPC WalletService method displays the BTC wallet's list of receiving addresses. The balance and number of confirmations for the most recent transaction is displayed to the right of each address. Instead of returning a gRPC data structure to the client, the service method returns a formatted String. If the BTC wallet has no unused addresses, one will be created and included in the returned list, and it can be used to fund the wallet. The new method required injection of the BtcWalletService into CoreWalletsService, and the usual boilerplate changes to grpc.proto, CliMain, and GrpcWalletService. Some of the next PRs (for bisq-network#4257) will require some common functionality within CoreWalletsService, so these additional changes were included: * a private, class level formatSatoshis function * a public getNumConfirmationsForMostRecentTransaction method * a public getAddressBalance method * a private getAddressEntry method A unit test that verifies a successful return status was added to cli/test.sh.
eigentsmis
pushed a commit
to eigentsmis/bisq
that referenced
this issue
Jun 26, 2020
This addresses task bisq-network#1 in issue bisq-network#4257. This new gRPC WalletService method displays the BTC wallet's list of receiving addresses. The balance and number of confirmations for the most recent transaction is displayed to the right of each address. Instead of returning a gRPC data structure to the client, the service method returns a formatted String. If the BTC wallet has no unused addresses, one will be created and included in the returned list, and it can be used to fund the wallet. The new method required injection of the BtcWalletService into CoreWalletsService, and the usual boilerplate changes to grpc.proto, CliMain, and GrpcWalletService. Some of the next PRs (for bisq-network#4257) will require some common functionality within CoreWalletsService, so these additional changes were included: * a private, class level formatSatoshis function * a public getNumConfirmationsForMostRecentTransaction method * a public getAddressBalance method * a private getAddressEntry method A unit test that verifies a successful return status was added to cli/test.sh.
ripcurlx
added a commit
that referenced
this issue
Jan 10, 2022
Rename API method keepfunds -> closetrade (#1)
ripcurlx
added a commit
that referenced
this issue
Feb 14, 2022
Modify .proto file comments to be parsed by bisq-grpc-api-doc [#1]
ripcurlx
added a commit
that referenced
this issue
Feb 24, 2022
…-changes Prepare API Offers .proto defs for significant changes [#1]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use polling at the moment, but a push based solution (multicast like) would be better. No concrete idea yet how to impl. that based on TomP2P.
The text was updated successfully, but these errors were encountered: