TradeMed Installation & Configuration on Linux Server
Budget: £20 – £250 GBP
I need someone to install TradeMed on my Linux server. It's a straightforward task. Post installation, I require assistance with specific configurations: setting up a database, configuring SSL/TLS, and establishing user roles.
Skills and Experience Needed:
- Proficiency in Linux server management
- Experience with TradeMed installation
- Knowledge in database setup
- Familiarity with SSL/TLS configuration
- Ability to setup user roles
- Understanding of server security
Please note, I do have root access to the server.
TradeMed implements a basic web application for listing products for sale in exchange for bitcoin.
Who might use this software? Anyone who wants to sell items online and receive bitcoin while having total control over the process and with the minimal amount of software.
The main distinction from other alternatives such as WooCommerce is that privacy and anonymity are the primary design goals. Both the website operator and all users of the web application can conduct business while remaining anonymous. This is achieved by running the web service as a TOR hidden service and encouraging PGP communication between users. TOR is recommended but if anonymity is not required, it can be used without TOR.
To prevent deanonymization of users there is no use of client side scripting languages. This means a tradeoff has been made in favor of security and anonymity resulting in a basic 1990s appearance and minimal features. The application does not utilize email in any way because it is insecure and can reveal identities.
A design goal is to be self reliant and have minimal dependencies on third party APIs or services. The only third party dependency required is for exchange rates. There is no support for external payment processors. Apart from bitcoind, it has no other software dependences other than a few standard OS utilities.
The software automates the process of generating a set of bitcoin addresses and uploading them to the market ready to be assigned to new orders. They are signed with PGP. See "automated pre-generated method" here. The addresses are saved as "watch-only" on the web server. It was designed to use only bitcoind so support for xpub addresses was not developed.
Other digital currencies such as Litecoin can be enabled in addition to bitcoin if they use the same RPC API as bitcoind. Customers choose which payment method when placing the order. Although the software requires bitcoind on the market system to monitor payments, the private wallet could run any wallet software. When bitcoind is used for the private wallet then this application will automate tasks like address generation, uploading addresses to market, and processing refunds. But if another wallet software is used, then these features would not work and a custom script to load the address set into the market would be needed. This could be achieved by using the admin HTTP API or else updating the database table directly.
It can be run by a single vendor or it can be setup for use by multiple vendors and operate like a darknet market where all participants are anonymous.
The software has been used in production for many years both in a single vendor setup and a multi-vendor setup. Issues with usability have been improved incrementally during that time.
Skills and Experience Needed:
- Proficiency in Linux server management
- Experience with TradeMed installation
- Knowledge in database setup
- Familiarity with SSL/TLS configuration
- Ability to setup user roles
- Understanding of server security
Please note, I do have root access to the server.
TradeMed implements a basic web application for listing products for sale in exchange for bitcoin.
Who might use this software? Anyone who wants to sell items online and receive bitcoin while having total control over the process and with the minimal amount of software.
The main distinction from other alternatives such as WooCommerce is that privacy and anonymity are the primary design goals. Both the website operator and all users of the web application can conduct business while remaining anonymous. This is achieved by running the web service as a TOR hidden service and encouraging PGP communication between users. TOR is recommended but if anonymity is not required, it can be used without TOR.
To prevent deanonymization of users there is no use of client side scripting languages. This means a tradeoff has been made in favor of security and anonymity resulting in a basic 1990s appearance and minimal features. The application does not utilize email in any way because it is insecure and can reveal identities.
A design goal is to be self reliant and have minimal dependencies on third party APIs or services. The only third party dependency required is for exchange rates. There is no support for external payment processors. Apart from bitcoind, it has no other software dependences other than a few standard OS utilities.
The software automates the process of generating a set of bitcoin addresses and uploading them to the market ready to be assigned to new orders. They are signed with PGP. See "automated pre-generated method" here. The addresses are saved as "watch-only" on the web server. It was designed to use only bitcoind so support for xpub addresses was not developed.
Other digital currencies such as Litecoin can be enabled in addition to bitcoin if they use the same RPC API as bitcoind. Customers choose which payment method when placing the order. Although the software requires bitcoind on the market system to monitor payments, the private wallet could run any wallet software. When bitcoind is used for the private wallet then this application will automate tasks like address generation, uploading addresses to market, and processing refunds. But if another wallet software is used, then these features would not work and a custom script to load the address set into the market would be needed. This could be achieved by using the admin HTTP API or else updating the database table directly.
It can be run by a single vendor or it can be setup for use by multiple vendors and operate like a darknet market where all participants are anonymous.
The software has been used in production for many years both in a single vendor setup and a multi-vendor setup. Issues with usability have been improved incrementally during that time.