HenrikJannsen
e1b332c32d
Remove price node and seed nodes of @miker and @mrosseel
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-20 12:55:57 -05:00
Christoph Atteneder
9e3b28bf0f
Add back distribution tar generation for daemon and cli
...
This is required in finalize.sh script for creating the release bundle
2022-12-20 13:32:27 +01:00
Christoph Atteneder
d99452c978
Not use additional -%d in name format because of refactoring
2022-12-20 11:36:42 +01:00
Christoph Atteneder
a726d826c8
Not use additional -%d in name format because of refactoring
2022-12-20 11:29:14 +01:00
HenrikJannsen
30afccb2d6
Use ThreadPoolExecutor with custom set queueCapacity instead of CachedThreadPool
...
The previously used newCachedThreadPool carries higher risk for execution exceptions if exceeded.
Originally we had only one executor with a corePoolSize of 15 and a maximumPoolSize of 30 and queueCapacity was set to maximumPoolSize.
This was risky when the 15 corePool threads have been busy and new messages or connection creation threads are
queued up with potentially significant delay until getting served leading to timeouts.
Now we use (if maxConnections is 12) corePoolSize of 24, maximumPoolSize 36 and queueCapacity 10. This gives
considerable headroom. We also have split up the executors in 2 distinct ones.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 16:50:55 +01:00
jmacxx
9f8b3df1ac
Base initial limit from users max past trade size if applicable.
2022-12-19 16:49:39 +01:00
Christoph Atteneder
f66e693605
Merge pull request #6473 from jmacxx/user_trade_limits_fix
...
Base initial limit from user's max past trade size if applicable.
2022-12-19 16:49:23 +01:00
sqrrm
c76ee16a2b
Merge pull request #6468 from HenrikJannsen/change_threadpool
...
Use ThreadPoolExecutor with custom set queueCapacity instead of CachedThreadPool
2022-12-19 16:42:47 +01:00
jmacxx
64e0ab8832
Base initial limit from users max past trade size if applicable.
2022-12-19 09:14:15 -06:00
dependabot[bot]
c9b6a423dc
Bump actions/checkout from 3.1.0 to 3.2.0
...
Bumps [actions/checkout](https://github.com/actions/checkout ) from 3.1.0 to 3.2.0.
- [Release notes](https://github.com/actions/checkout/releases )
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md )
- [Commits](93ea575cb5...755da8c3cf
2022-12-19 14:03:53 +00:00
dependabot[bot]
755a3452c3
Bump actions/setup-java from 3.8.0 to 3.9.0
...
Bumps [actions/setup-java](https://github.com/actions/setup-java ) from 3.8.0 to 3.9.0.
- [Release notes](https://github.com/actions/setup-java/releases )
- [Commits](c3ac5dd0ed...1df8dbefe2
2022-12-19 14:03:50 +00:00
HenrikJannsen
8eb555df8f
Add INVALID_SNAPSHOT_HEIGHT to AvailabilityResult.
...
Use AvailabilityResult.INVALID_SNAPSHOT_HEIGHT instead of AckMessage with error.
Show description in error popup instead of enum name.
Return PRICE_CHECK_FAILED instead of UNKNOWN_FAILURE at error at price check also for non api users.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:32:00 +01:00
HenrikJannsen
0b849800f9
Fix test
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:32:00 +01:00
HenrikJannsen
bd85958c9e
Add sanity check for a min. block height for the snapshot height
...
We don't allow to get further back than 767950 (the block height from Dec. 18th 2022)
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:32:00 +01:00
HenrikJannsen
f834fbdda6
Add sanity check that max share of a non-legacy BM is 20% over MAX_BURN_SHARE (taking into account potential increase due adjustment)
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:59 +01:00
HenrikJannsen
618e610f3e
Exclude legacy BM from DAO balance
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:59 +01:00
HenrikJannsen
109c200650
Add balance fields for DAO revenue with total burned BSQ and total distributed BTC/BSQ
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:59 +01:00
HenrikJannsen
2be5d2fbd8
Increase GENESIS_OUTPUT_AMOUNT_FACTOR and ISSUANCE_BOOST_FACTOR
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:59 +01:00
HenrikJannsen
c268cc46cb
Add new average bsq price after historical data
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:58 +01:00
HenrikJannsen
1b182743a2
Update BurningManAccountingStore_BTC_MAINNET
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:58 +01:00
HenrikJannsen
a76267b6f3
Use static fields for opReturnData instead of hardcoded mainnet hashes
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:58 +01:00
HenrikJannsen
a263ca5cd6
Remove numIssuance and numBurnOutputs columns to save space
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:57 +01:00
HenrikJannsen
16bfdd6154
Remove regtest value for DEFAULT_ESTIMATED_BTC_TRADE_FEE_REVENUE_PER_CYCLE
...
Adjust reimbursement amounts as we do not reimburse 100% of the DPT
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:57 +01:00
HenrikJannsen
80063d735c
Add custom handling of legacy BM.
...
Refactoring: rename variables
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:57 +01:00
HenrikJannsen
3e362c3207
Refactor: move out fields used the same way in both if/else branches.
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:57 +01:00
HenrikJannsen
1aa5a9b17a
Don't allow the myBurnAmount to be larger than the upperBaseTarget
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:56 +01:00
HenrikJannsen
7eed7a4cda
In case we have capped burn shares we redistribute the share from the over-burned amount to the non capped candidates.
...
This helps to avoid that the legacy BM would get the rest in case there are capped shares.
It still can be that a candidate exceeds the cap and by the adjustment becomes capped. We take that into account and the legacy BM would get some share in that case.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:56 +01:00
HenrikJannsen
709f0e1b85
Change burn target calculation.
...
Left side is amount to burn to reach the max allowed receiver share based on the burned amount of all BM.
The right side is the amount to burn to reach the max allowed receiver share based the boosted max burn target.
Increase ISSUANCE_BOOST_FACTOR from 3 to 4.
Add help overlay to burn target table header.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:56 +01:00
HenrikJannsen
2f9f66280a
Remove try catch. Will be handled in Future fault handler
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:55 +01:00
HenrikJannsen
1dd83e5789
Add check for price==0
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:31:55 +01:00
Christoph Atteneder
40d949cbc9
Merge pull request #6463 from HenrikJannsen/adjust_burn_target
...
Adjust burn target
2022-12-19 09:29:55 +01:00
jmacxx
9ce2964ff4
Fix divide by zero errors in Trade history summary.
2022-12-19 09:28:42 +01:00
sqrrm
1cf51be56c
Update sqrrm provided btc onion addresses
2022-12-19 09:28:21 +01:00
HenrikJannsen
ddf5239800
Increase timeouts from 3 to 4 min.
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:27:44 +01:00
HenrikJannsen
6aad3a8dc5
Reduce getDataResponse size from 9 MB to 6 MB
...
Reduce number of blocks at GetBlocksResponse from 4000 to 3000
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-19 09:27:27 +01:00
HenrikJannsen
21541d6880
Add INVALID_SNAPSHOT_HEIGHT to AvailabilityResult.
...
Use AvailabilityResult.INVALID_SNAPSHOT_HEIGHT instead of AckMessage with error.
Show description in error popup instead of enum name.
Return PRICE_CHECK_FAILED instead of UNKNOWN_FAILURE at error at price check also for non api users.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-18 13:13:36 -05:00
HenrikJannsen
2a8d1b3426
Fix test
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-18 12:57:15 -05:00
HenrikJannsen
c36c9b214c
Add sanity check for a min. block height for the snapshot height
...
We don't allow to get further back than 767950 (the block height from Dec. 18th 2022)
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-18 12:27:29 -05:00
Alejandro García
55fdae4418
Merge pull request #6469 from HenrikJannsen/reduce_get_data_and_get_blocks_response_size
...
Reduce Response size
2022-12-18 17:35:43 +02:00
Alejandro García
51f9e8bac3
Merge pull request #6467 from HenrikJannsen/increase_timeouts
...
Increase timeouts from 3 to 4 min.
2022-12-18 17:34:14 +02:00
Alejandro García
5ba966786b
Merge pull request #6455 from bisq-network/dependabot/github_actions/actions/setup-java-c3ac5dd0ed8db40fedb61c32fbe677e6b355e94c
...
Bump actions/setup-java from 19eeec562b37d29a1ad055b7de9c280bd0906d8d to c3ac5dd0ed8db40fedb61c32fbe677e6b355e94c
2022-12-18 17:32:51 +02:00
Alejandro García
582893a6c7
Merge pull request #6466 from jmacxx/fix_issue_6464
...
Fix divide by zero errors in Trade history summary.
2022-12-18 17:32:16 +02:00
Alejandro García
55c55a6aae
Merge pull request #6465 from sqrrm/update-btc-nodes
...
Update sqrrm provided btc onion addresses
2022-12-18 17:30:30 +02:00
Alejandro García
959ac9ace4
Merge pull request #6462 from alvasw/gradle_move_protoc_build_logic_into_own_build_gradle_file
...
Gradle: Move protoc build-logic into its own build.gradle
2022-12-18 17:29:41 +02:00
HenrikJannsen
72372970f8
Add sanity check that max share of a non-legacy BM is 20% over MAX_BURN_SHARE (taking into account potential increase due adjustment)
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-17 20:15:28 -05:00
HenrikJannsen
9efab7e7de
Exclude legacy BM from DAO balance
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-17 20:00:43 -05:00
jmacxx
a09dae16be
Fix divide by zero errors in Trade history summary.
2022-12-16 20:36:03 -06:00
HenrikJannsen
049caab89c
Reduce getDataResponse size from 9 MB to 6 MB
...
Reduce number of blocks at GetBlocksResponse from 4000 to 3000
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-16 17:45:10 -05:00
HenrikJannsen
14c188afbe
Use ThreadPoolExecutor with custom set queueCapacity instead of CachedThreadPool
...
The previously used newCachedThreadPool carries higher risk for execution exceptions if exceeded.
Originally we had only one executor with a corePoolSize of 15 and a maximumPoolSize of 30 and queueCapacity was set to maximumPoolSize.
This was risky when the 15 corePool threads have been busy and new messages or connection creation threads are
queued up with potentially significant delay until getting served leading to timeouts.
Now we use (if maxConnections is 12) corePoolSize of 24, maximumPoolSize 36 and queueCapacity 10. This gives
considerable headroom. We also have split up the executors in 2 distinct ones.
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-16 17:38:23 -05:00
HenrikJannsen
6fedc8177e
Increase timeouts from 3 to 4 min.
...
Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-12-16 17:23:17 -05:00
