samourai-dojo issueshttps://code.samourai.io/dojo/samourai-dojo/-/issues2023-01-04T21:57:45Zhttps://code.samourai.io/dojo/samourai-dojo/-/issues/160Lack of .cookie auth for Bitcoin Core2023-01-04T21:57:45ZDanielPXLack of .cookie auth for Bitcoin CoreIn DIY set up of Dojo, only way to connect BTC core is by using plain text credentials. While this can be mitigated by restricting access to config file, it would be nice and security friendly feature to use .cookie file for authenticati...In DIY set up of Dojo, only way to connect BTC core is by using plain text credentials. While this can be mitigated by restricting access to config file, it would be nice and security friendly feature to use .cookie file for authentication / maybe not that complicated to implementhttps://code.samourai.io/dojo/samourai-dojo/-/issues/147Docker Memory Use Windows 102021-03-04T09:56:14ZNathan JenkinsDocker Memory Use Windows 10Just a small documentation thing, if users are trying to run Samourai within a Docker container on Windows 10 they will need to create %HOMEPATH%/.wslconfig with the following lines:
[wsl2]
memory=4GB # Where 4 GB < total system memory
...Just a small documentation thing, if users are trying to run Samourai within a Docker container on Windows 10 they will need to create %HOMEPATH%/.wslconfig with the following lines:
[wsl2]
memory=4GB # Where 4 GB < total system memory
Finally they will have to run **Restart-Service LxssManager** from an administrative PowerShell.https://code.samourai.io/dojo/samourai-dojo/-/issues/144Synology setup broken2020-10-20T06:14:48ZDanSynology setup brokenI am trying to install Dojo on a Synology device. DSM version: 6.2.3-25426 Update 2
I followed the instructions here: https://code.samourai.io/dojo/samourai-dojo/-/blob/master/doc/DOCKER_synology_setup.md
Once the docker containers sta...I am trying to install Dojo on a Synology device. DSM version: 6.2.3-25426 Update 2
I followed the instructions here: https://code.samourai.io/dojo/samourai-dojo/-/blob/master/doc/DOCKER_synology_setup.md
Once the docker containers start to boot, I get a large number of Permission denied errors.
A few examples:
tor | /bin/bash: /restart.sh: Permission denied
whirlpool | /bin/bash: /restart.sh: Permission denied
explorer | /bin/bash: /home/node/app/restart.sh: Permission denied
I believe this is due to how the images create users and groups. I have seen other issues with users created in Docker images not working on Synology. I believe the custom user management system on Synology does not play well with this sort of design.https://code.samourai.io/dojo/samourai-dojo/-/issues/103BTCPayServer-Docker integration2020-02-28T21:23:01Zkenshin-samouraiBTCPayServer-Docker integration*Created by: Kukks*
**Is your feature request related to a problem? Please describe.**
We have a similar docker-compose builder system for btpayserver at https://github.com/btcpayserver/btcpayserver-docker, which also deploys a full bi...*Created by: Kukks*
**Is your feature request related to a problem? Please describe.**
We have a similar docker-compose builder system for btpayserver at https://github.com/btcpayserver/btcpayserver-docker, which also deploys a full bitcoin node(and optionally with txindex and unpruned) along with a tor node.
**Describe the solution you'd like**
It would be nice to either or else find a simplified wayc to deploy dojo through the plugin system inbtcpayserver-docker(some info here: https://github.com/btcpayserver/btcpayserver-docker#how-can-i-customize-the-generated-docker-compose-file). I think it should be fairly easy:
* build and publish docker images for dojo( no need for bitcoind, tor and mysql from what I can tell)
* allow specifying all needed options to connect dojo to custom mysql, bitcoind and tor
* allow auto generation of the auth token stuff
* create docker fragment in BTCPay( started messing about with this at https://github.com/Kukks/btcpayserver-docker/commit/031e6470f840ad22b523e86bbc9a064f38fa2d89)
**Describe alternatives you've considered**
Have an option here to interoperate with that setup but I think it would just be overhead here
https://code.samourai.io/dojo/samourai-dojo/-/issues/36Maintenance Tool - Display error messages2019-07-12T15:11:49Zkenshin-samouraiMaintenance Tool - Display error messages*Created by: LaurentMT*
Suggestion from a user: display error messages related to the rescan of an address/xpub in the UI of the Maintenance Tool (instead of the generic "Rescan complete").*Created by: LaurentMT*
Suggestion from a user: display error messages related to the rescan of an address/xpub in the UI of the Maintenance Tool (instead of the generic "Rescan complete").https://code.samourai.io/dojo/samourai-dojo/-/issues/23Add a random delay to broadcast scheduled transactions2019-07-01T01:47:07Zkenshin-samouraiAdd a random delay to broadcast scheduled transactions*Created by: Technifocal*
Assuming I'm reading the code correctly, [scheduled transactions are broadcast immediately after a new block is mined](https://github.com/Samourai-Wallet/samourai-dojo/blob/b4cd156301093659ff487fff48fa5e844959f...*Created by: Technifocal*
Assuming I'm reading the code correctly, [scheduled transactions are broadcast immediately after a new block is mined](https://github.com/Samourai-Wallet/samourai-dojo/blob/b4cd156301093659ff487fff48fa5e844959fcb7/pushtx/orchestrator.js#L85-L148).
For example, imagine we had a transaction scheduled for block 3:
Block height|Time|Transaction broadcast/time
-|-|-
1|+0 minutes|False
2|+10 minutes|False
3|+20 minutes|True, at +20 minutes
4|+30 minutes|False
An attacker could assume that this transaction might have been scheduled. Compare this to:
Block height|Time|Transaction broadcast/time
-|-|-
1|+0 minutes|False
2|+10 minutes|False
3|+20 minutes|True, at +25 minutes
4|+30 minutes|False
Where an attacker could be sure the transaction was not scheduled as it came between two different blocks (and thus was not triggered by a block being mined).
Adding a random time after the target block (say, 0 seconds to 20 minutes) would prevent an attacker from determining that any transactions broadcast between two blocks were not broadcasted by Dojo's implementation of scheduled transactions.https://code.samourai.io/dojo/samourai-dojo/-/issues/63Make upgrade process more resilient to extra characters2019-08-17T20:50:51Zkenshin-samouraiMake upgrade process more resilient to extra characters*Created by: LaurentMT*
If extra characters (like space or tab) are mistakenly added before the name of a property in a docker-*.conf file, the upgrade process overwrites the value of the property with the default value set in the docke...*Created by: LaurentMT*
If extra characters (like space or tab) are mistakenly added before the name of a property in a docker-*.conf file, the upgrade process overwrites the value of the property with the default value set in the docker-*.conf.tpl file.
We should make the upgrade process more tolerant to this kind of error.https://code.samourai.io/dojo/samourai-dojo/-/issues/17Suggestion: alternatives for initial block download2019-06-26T14:19:11Zkenshin-samouraiSuggestion: alternatives for initial block download*Created by: pxsocs*
Initial block download is still a bottleneck for any Bitcoin project requiring a full synch.
Although this is a somewhat controversial topic (particularly a torrent for a recent synched blockchain), there is a t...*Created by: pxsocs*
Initial block download is still a bottleneck for any Bitcoin project requiring a full synch.
Although this is a somewhat controversial topic (particularly a torrent for a recent synched blockchain), there is a tradeoff. Users could be up and running faster if the process is optimized.
A suggestion is to include on the Dojo script something similar to what the [RaspiBlitz](https://github.com/rootzoll/raspiblitz) project has done, giving users other alternatives:
![ssh5-blockchain2](https://user-images.githubusercontent.com/40473443/59975239-5d03c900-958c-11e9-9c96-72690e756728.png)
The script to perform this action is available [here](https://github.com/rootzoll/raspiblitz/blob/master/home.admin/50torrentHDD.sh)