Tor Hidden Services Load Balancing: OnionBalance Onion Mirror Links The OnionBalance software allows for Tor hidden service requests to be distributed across multiple backend Tor instances. OnionBalance provides load-balancing while also making onion services more resilient and reliable by
Tor Hidden Services Load Balancing
The OnionBalance software allows for Tor hidden service requests to be distributed across multiple backend Tor instances. OnionBalance provides load-balancing while also making onion services more resilient and reliable by eliminating single points-of-failure. This tool is designed to allow requests to Tor onion service to be directed to multiple back-end Tor instances, thereby increasing availability and reliability. The design involves collating the set of introduction points created by one or more independent Tor onion service instances into a single ‘master’ onion service descriptor.
The master descriptor is signed by the onion service permanent key and published to the HSDir system as normal. Clients who wish to access the onion service would then retrieve the master service descriptor and try to connect to introduction points from the descriptor in a random order. If a client successfully establishes an introduction circuit, they can begin communicating with one of the onion services instances with the normal onion service protocol defined in rend-spec.txt
OnionBalance is under active development and new features are being added regularly:
Load balancing between up to 60 backend hidden services
Storage of the hidden service private key separate to th hidden service hosts
Instance – A load-balancing node running an individual onion service.
Introduction Point – A Tor relay chosen by an onion service instance as a medium-term meeting-place for initial client connections.
Master Descriptor – An onion service descriptor published with the desired onion address containing introduction points for each instance.
Management Server – Server running OnionBalance which collates introduction points and publishes a master descriptor.
Metadata Channel – A direct connection from an instance to a management server which can be used for instance descriptor upload and transfer of other data.
is the machine running the OnionBalance daemon. It holds the master hidden service private key. This machine can be located geographically isolated from the machines hosting the hidden service content. It does not need to serve any content. OnionBalance requires that a recent version of Tor (>= 0.2.7.1-alpha) is installed on the management server system. This version might not be available in your operating system’s repositories yet.s.
The management server need to have its control port enabled to allow the OnionBalance daemon to talk to the Tor process. This can be done by uncommenting the ControlPort option in your torrc configuration file. Alternatively you can replace your torrc file with the following is suitable for the Tor instance running on the management server:
Each backend instance should be run a standard onion service which serves your website or other content. More information about configuring onion services is available in the Tor Project’s hidden service configuration guide. If you have used the onionbalance-config tool you should transfer the generated instance config files and keys to the Tor configuration directory on the backend servers.
# ControlPort 9051
# CookieAuthentication 1
# Configure each onion service instance with a unique permanent key.
# HiddenServiceDir tor-data/hidden_service/
# HiddenServicePort 80 127.0.0.1:80
OnionBalance requires at least one system that is running the OnionBalance management server. The OnionBalance software does not need to be installed on the backend servers which provide the hidden service content (i.e. web site, IRC server etc.). OnionBalance is not yet packaged for most Linux and BSD. The tool can be installed from PyPI or directly from the Git repository:
If you are running Debian unstable or testing, you can install OnionBalance with the following command:
# apt-get install onionbalance
You can start the OnionBalance management server once all of your backend onion service instances are running. You will need to create a configuration file which list the backend hidden services and the location of your hidden service keys.
$ onionbalance -c config.yaml
$ sudo service onionbalance start
The management server must be left running to publish new descriptors for your onion service.
How to create onion mirror links? This section of the file consists of groups of lines, each representing one onion service. Right now they are all commented out (the lines start with #), so onion services are disabled. Each group of lines consists of one HiddenServiceDir line, and one or more HiddenServicePort lines:
HiddenServiceDir is a directory where Tor will store information about that onion service. In particular, Tor will create a file here named hostname which will tell you the onion URL. You don’t need to add any files to this directory. Make sure this is not the same directory as the hidserv directory you created when setting up thttpd, as your HiddenServiceDir contains secret information!
HiddenServicePort lets you specify a virtual port (that is, what port people accessing the onion service will think they’re using) and an IP address and port for redirecting connections to this virtual port.
You’re going to want to change the HiddenServiceDir line, so it points to an actual directory that is readable/writeable by the user that will be running Tor. The above line should work if you’re using the OS X Tor package. On Unix, try “/home/username/hidden_service/” and fill in your own username in place of “username”. On Windows you might pick:
Darkweb Scripts download onion eCommerce Marketplace Script V2.2 This is a complete rewrite of my old script: onion eCommerce Marketplace Script. The two share some similarities (functional), but a new version is written from scratch, meaning no code is shared between them.
VPS with at least 2GB of RAM
Daemon for each coin that is enabled on marketplace
Server requirements: (what software is needed on VPS)
Elasticsearch (Search interface that will keep track of search records and provide great search performance)
Redis (Optional, but will greatly increase app performance )
Categories Category system is very dynamic. Categories can be nested indefinitely. Creating, deleting and editing of categories is handled in admin panel.
Detailed home page There is placeholder text on the home page at the moment that will represent the most important features of your marketplace. On top of that, all users can see Top Vendors (Vendors with most sales), Latest Orders (Products of orders completed most recently, as well as order value, but no information about buyer or seller), Rising Vendors (Vendors with most sales in specified time frame, defaults to 7 days). Official mirrors are a place where you can specify on what other links your website can be reached.
Password reset Password can be reset with PGP Key added on account (more about PGP below) or with Mnemonic key provided during signup. The mnemonic key is shown only once and should be written down on paper. During signup, it is hashed (bcrypt) instantly and only stored in operating memory for the short time during display after which is cleared from memory manually as an addition to automatic PHP Garbage Collection.
PGP Each user can add their on PGP key which is used for multiple features. Vendors must have PGP and 2FA enabled before they are allowed to upgrade from user to vendor status. If you have active PGP key you can reset your password with it or enable 2FA for your login. Each PGP key must be confirmed before is linked to account, and if you want to add new key you must first sign a message from the old one. Messages can also be encrypted with user’s PGP key if its present (this is not enforced, its user’s choice).
2FA (Two-Factor Authentication)
If user has PGP key linked to their account, they can enable 2FA. If enabled, log in to marketplace will be prevented unless a randomly generated message is signed from the key.
Buyers do not need to save product links for later. On each product there is “Add to wishlist” button that can be used, and they are stored in user’s personal list for later.
Normal users cannot post products on Marketplace. In order to post products you must become vendor. Before you can upgrade you must have PGP key and 2FA Enabled in your profile. Vendor price can be set in marketplace config. The vendor can use any of the coins available to purchase vendor status. Out of each vendor sale, a percentage of sale value goes to marketplace addresses.
Vendor profile customization
Vendors are able to customize their profile with pre-defined profile backgrounds and short personal description.
Vendor levels and XP
Each new vendor starts at Level 0 and progresses further based on performance. XP and the Amount of levels is dynamic and configurable. Multipliers determine how much XP is granted to/taken from vendors for each action. XP is granted/taken by formula: USDvalue*multiplier Example: product_delivered multiplier is 20 USD value of product is 100$ When vendor successfully delivers product, he will receive 100*20=2000 XP This is an example from experience config file: Code: 'multipliers' => [ 'product_delivered' => 10, 'product_dispute_lost' =>20, // How much XP per star (given/taken based on feedback type) 'feedback_per_star' => 2, // how much XP per USD value of transaction (given/taken based on feedback type) 'feedback_per_usd' => 5, ] Feedback
After each completed purchase, vendors are able to leave feedback. Feedback types are Positive, Neutral and Negative and they will affect vendor score as well as product score.
Probably the most important system is Coin System. Its completely dynamic, which means new coins can be added at any time. Standard version of marketplace comes with Bitcoin and Monero included. For each coin added, in marketplace config there can be set unlimited amount of marketplace addresses (used for receiving fees from purchases), and in case more than one address is present, address for receiving fee will be choosen randomly (for each purchase).
Product types There are two product types. Physical and Digital products. Based on the type, different options are displayed during product creating and purchase. Both Digital and Physical products support offers and custom units of measure (Item, kg, gram, piece …). With offers, vendors can give discounts on a purchase based on quantity. For example: Price for 1 product is 100$ Price for 10 products is 90$ Price for 20+ products is 80$ Each of those is considered an offer and can be added/removed at any time.
Digital products support automatic delivery which is optional. If checked, the autofill system is used. Each line in textarea is treated as a single item and will be the product’s quantity. It will be instantly sent on the user upon purchase.
Physical products have delivery options. Each delivery option consists of: Name, Price, Expected delivery duration, Minimum quantity for delivery, Maximum Quantity for delivery. Physical products can also include/exclude countries from shipping.
Markdown styling Instead of just plain text, product description and rules support markdown styling. Every tag is supported except URL tag.
When user chooses to purchase any product, he is able to pay with any coin supported by market (and vendor, since vendors can choose which coins they want on each product). There is no wallets or anything similar. Users do not need to keep money on marketplace at all times. For each purchase random address is generated, and its used for that purchase only.
Escrow is present on every purchase by default. Upon purchase, marketplace address is generated that will hold funds. If purchase is completed if its marked as delivered or dispute is resolved. If buyer is unhappy with purchase he can open dispute and potentially (based on admin’s decision) get his money back. Upon purchase completion, based on result money will be sent from temporary purchase address to buyer/vendor and to one of the marketplace holding addresses.
If user wants to buy more than one product (maybe from different sellers too), they can add them all in a cart and then checkout only once.
Most important feature of messages is security. Marketplace uses latest algorithms and standards in Public Key Cryptography (like XChaCha20-Poly1305-IETF) to encrypt messages between users. Upon registration, Public and Private keys are created for each user. Based on user’s password an encryption key is derived, and that key is used to encrypt Private key, while Public Key is exposed. When user A whats to send message to user B, a key exchange happens. User A encrypts message with User B’s public key, and that message is stored in database. Only user B can read that message when he logs in and decrypts his messages with password. This system makes messages secure and unreadable by anyone, including marketplace administrator or basically anyone who can possibly get access to the database.
Messages are organized in conversations. Multiple conversations can be started at the same time.
Users will get notifications for most actions that happen on marketplace regarding them. Some of the examples are: New message, Purchase status update (product sent, product delivered etc.), Vendor actions (Feedback) and so on. They can be read in User Account Panel and deleted at any time.
Marketplace can possibly connect to Bitmessage daemon. If connected, users can chose to add their Bitmessage addresses and get their notifications forwarded there. This means they will still get notifications even if they are not currently logged in, and they don’t need to refresh anything. Before being able to forward notifications, Bitmessage addresses must be confirmed first.
Users can open support tickets regarding any problem they encounter. Administrators/Moderators will see this tickets in admin panel and can reply, or close them.
Most of the stuff happening on marketplace can be viewed directly on admin panel. Administrators can access every feature on admin panel.
Moderators Modular permission system is currently supported, which means admins can give/take some access to moderators (For example, support staff can only answer tickets and resolve disputes, community manager can only send mass messages etc.). Currently supported features:
Index – Basic information
Categories – Add/Edit/Remove Categories
Mass Messages – Ability to send messages to users by marketplace (Can be filtered to user groups)
Users – View users, search, filter, and edit each user individually.
Products – View, search, filter by user, or edit product
Log – Activity log of all Administrators/Moderators inside Admin Panel Example:
Bitmessage – Status of Bitmessage service (performs test), and view of marketplace bitmessage address
Disputes – View and resolve purchase disputes
Tickets – View and resolve support tickets
Purchases – List of all purchases
Vendor Purchases – List of vendor purchases
Marketplace currently supports these coins:
Bitcoin – Included in standard version
Monero – Included in standard version
Marketplace installation instructions are included. These are not 100% copy paste but they do explain how must of the things work in detail.
Selling terms and conditions:
I’m selling the only script, I will help you install it with extra charges, edit it or whatever you want to do after you purchase it (I can do this for the right price and if I have time, contact me to check)
After purchase, you cannot resell or share this script
Script is tested for bugs but In case you find any, or any error in code it will be fixed with no additional charge
I will not give you files first in any case. I don’t care who you are, if you don’t trust me we will use escrow
In case of escrow I will deal only with bitcointalk trusted escrow (You can find list here)
Price stated below is for one copy of the script, which means I intend to sell it multiple times. In case you want to be the only buyer please contact me
Current price is: 400$ in BTC equivalent (please note that this can be changed at any time) For this price, you get a standard version of the marketplace with two coins (Bitcoin and Monero). If you want additional coins, they are charged separately. Litecoin, DASH, PIVX are 50$ each, Verge is 60$ and Bitcoin Cash is 90$
Multi-Currency Module Default marketplace currency is USD (converted to crypto at the moment of purchase). This module allows user to select local currency in profile (EUR, GBP, JPY…) and every price on marketplace will be converted to that. This module is optional and priced at 100$
There is 100$ discount available for anyone who bought original script onion eCommerce Marketplace Script In order to apply for a discount, you must sign a message from an address that sent coins for purchase.