In MultiChain, nodes prove their identity when connecting to other nodes How private networks work For now, please consult the MultiChain White Paper.MultiChain handshaking protocol For MultiChain blockchains, the version and verack messages in the bitcoin protocol are replaced with three messages (version, verack and verackack) which perform the following additional functions: Check both peers are on a blockchain with the same name.If necessary, download the blockchain parameters from the other side, otherwise check both are using identical parameters.Each node identifies a public address which has connection permissions and for which it has the private key.Each node sends a challenge message to the other node which it must sign using the private key corresponding to the address it presented.Support for bitcoin protocol handshaking If a MultiChain chain has anyone-can-connect set to true in the blockchain parameters, then MultiChain nodes will also accept incoming connections from wallets that use regular bitcoin-style handshaking, without the extra stages above.

This can be helpful if you want to connect to a MultiChain network from a regular bitcoin (e.g.However you should note the following caveats: You should change the wallet’s connection port to the default-network-port set in the blockchain parameters.Before starting the chain, set protocol-version=10002 and network-message-start=f9beb4d9 in the blockchain parameters, to match bitcoin’s peer-to-peer protocol.The bitcoin wallet will choke on MultiChain addresses, so you should also configure the chain to use bitcoin-style addresses by setting address-pubkeyhash-version=00, address-scripthash-version=05, private-key-version=80, address-checksum-value=00000000 in the blockchain parameters.Depending on the wallet in question, it may also not like other aspects of the blockchain which are different to bitcoin’s, such as the content of the genesis block, the block reward schedule and non-standard transactions.So you might want to start by using the bitcoin-compatible params file for your blockchain parameters, and making only minor modifications from there, such as the chain-name, default-network-port and global permissions.

The chain-name must match the name of the chain’s directory inside ~/.multichain/.The wallet’s interface will be focused on the native blockchain currency, rather than any native assets issued on the chain.This also means that it will build transactions incorrectly if they contain native assets in their inputs.See also these instructions for creating a bitcoin-style network using MultiChain, with no native assets or permissions.In the event of a contentious hard fork and a possible coin split, user's wealth may be in danger without a proper "replay protection" being implemented.This holds true even more so when a user runs a lightweight wallet such as Electrum.Electrum's developer Thomas Voegtlin has published a document on how to safely split coins should such event occur.However, this method relies on 3rd party servers that the wallet connects to.In the Bitcoin world, 3rd parties should not be trusted under any circumstances.I'll show you how to overcome this limitation by setting up your own Electrum server.

This tutorial is aimed at Mac OS X and Debian-based Linux distributions.It should work with other Linux distros too.Sorry, I don't have a Windows machine.Before you start, make sure to install a full Bitcoin node first and set at least the following minimum options in bitcoin.conf: Use random string generator for rpcuser and rpcpassword.The longer, the better.If you already have bitcoin node installed, you need to reindex the blockchain: When running Bitcoin-Qt it should be enough to just close and reopen the wallet.bitcoin fiabiliteIt will reindex the chain automatically.bitcoin charts difficultyElectrumX developer decided to use newer Python 3 which isn't installed on many operating systems by default.bitcoin ticker downloadInstalling the latest version of Python on Apple's OS X is very easy using homebrew: There are many different options to install Python 3.6 based on your Linux distribution.bitcoin difficulty increase time

The latest Ubuntu (16.10 as of now) only comes with Python 3.5.You will have to install the newer version from a 3rd party repository: Some Debian-based distributions may already be shipped with the latest Python.In a case of an error try using the following option instead.If you can't install it from a repository, just compile it from the source code.It should work for most distros.Please note that the compilation will take "forever".However, if your CPU has more than 4 cores, you can speed it up a bit by using make -j8 instead.bitcoin whatsapp group indiaYou will also need to install some Python 3.6 dependencies for ElectrumX.then install some required packages:If the above command gives you an error, try installing it with sudo (try to avoid it as much as possible, though).bitcoin calculator iosClone the ElectrumX code from a GitHub repository using git: /kyuupichan/electrumx.gitcd electrumx Next, create a data folder where the blockchain data will be stored: To allow Electrum wallets to connect to your server over SSL you need to create a self-signed certificate.Go to the data folder:Follow the on-screen information.

It will ask for certificate details such as your country and password.You can leave those fields empty.When done, create a certificate:These commands will create 2 files: server.key and server.crt.When configuring the ElectrumX instance, make sure to add server.key to SSL_KEYFILE and server.crt to SSL_CERTFILE.More on this in the next step.First, make sure a fully validating Bitcoin node is running:If you've installed Bitcoin-Qt the chances are bitcoin-cli is not present.It should output information about your node such as block height, open connections etc.If it doesn't, run the node first.OS X lacks Systemd to manage system services, so we will use UNIX's default svscan instead.Create a service folder that will hold symlinks to ElectrumX scripts.Copy daemontools scripts from the GitHub repo to your home directory:Set up ENV variables within ~/scripts/electrumx/env folder.Each variable is located in a separate file.Please refer to ElectrumX's documentation or have a look at my settings and change it accordingly.When finished open the log/run file:and edit the log path.

In my case it is /Users/bitcoin/ElectrumX/logs, yours may be different.Save the file by pressing ESC and typing :wqa followed by ENTER.Change the permissions for the file so it can be executed:Also, change the permission for another file that executes the server:Initialize svscan process to monitor electrumx services:Add services to the folder:They should be immediately recognized by svscan.Check the last few lines of the log to see whether the service outputs any errors: If it does, check your configuration again.Errors are pretty self-explanatory but if you're stuck, let me know in the comments section.ElectrumX is very resource intensive when it comes to open files so it needs a higher limit:Make sure the limit is set after every restart:If the above method doesn't work, try the following:Restart the service for new changes to take effect.Always wait for the service to be terminated properly by checking with logs.Above commands will only execute when svscan is already initialized.

You can check the service's status with: Most if not all Debian-based distribution use Systemd by default.Make sure that is the case for your system:If it outputs something like File: '/proc/1/exe' -> '/lib/systemd/systemd' you're good to go.Open a sudo session and copy a service file from the ElectrumX repo to your Systemd directory:Edit the file to match your setup:You need to edit at least ExecStart and User variables.When you're happy with the changes, hit ESC and type :wqa followed by ENTER.Create a configuration file for the server: and configure it according to your environment.Please refer to ElectrumX's documentation or have a look at my settings.If it gives you no errors, enable the service: You can exit the sudo session now:Say hi to connecting Electrum wallets (via Electrum console) using a banner file.It may contain any information such as your server version, donation address, contacts and even info on other services you offer.It's purely up to you.The content of my banner.txt file looks like this:and is located in the data folder ~/electrumx.You can save it to any location and let ElectrumX know via BANNER_FILE variable in either env/ folder or /etc/electrumx.conf depending on your operating system.Don't forget to restart the server after changing any server's settings.If you want to help the network and let others connect to your server, you have to open specific TCP ports.For a default Electrum set up, those ports are 50001 and 50002.On Linux, this can be easily done via iptables:However, Mac OS X users will need to install some kind of firewall.

The built-in one only manages outgoing connections.There are a few options such as Little Snitch but none of them are free to my knowledge.If you know about one, please let me know.Also, don't forget to open ports on your router if applicable.There are too many routers to cover them in this tutorial.Sorry.To test the connection, open your Electrum wallet.Start it with an argument --oneserver for extra privacy.On Mac OS X the command is:Click a green/red dot in the bottom right corner.A server configuration will pop up.Unclick "Select server automatically" and type in your server's local/remote IP address or a hostname.Click "Use SSL" and confirm.If you did everything right, your wallet should start synchronizing the chain data immediately.It shouldn't take more than 10 seconds to finish.Congratulations!You no longer rely on "trusted" 3rd parties.You also made yourself protected from contentious hard forks and coin splits.Please let me know in the comments section below if you have any questions or suggestions.My big thank you goes to Mashuri Clark that gave me some useful tips and corrected some steps for the OS X part.