Connecting to a AWS instance of multichain in bitcoin style

+2 votes
Hi Multichain Team

I have installed an multichain instance in amazon AWS (attach params.dat just relevant parameters below) , I have a MSigna wallet used normally for bitcoin , the problem is this wallet doesnt connects to multichain even when I have configured the chain in bitcoin mode , the wallet keeps on trying to connect and only shows connecting but never does it! What can it be? P:D No native assets just native currency requiered.

Thanks in advance

# ==== MultiChain configuration file ====

# Created by multichain-util
# Protocol version: 10009

# This parameter set is VALID.
# To join network please run "multichaind ecupaybeta2".

# The following parameters can only be edited if this file is a prototype of another configuration file.
# Please run "multichain-util clone ecupaybeta2 <new-network-name>" to generate new network.

# Basic chain parameters

chain-protocol = bitcoin                # Chain protocol: multichain (permissions, native assets) or bitcoin
chain-description = MultiChain ecupaybeta # Chain description, embedded in genesis block coinbase, max 90 chars.
root-stream-name = root                 # Root stream name, blank means no root stream.
root-stream-open = true                 # Allow anyone to publish in root stream
chain-is-testnet = false                # Content of the 'testnet' field of API responses, for compatibility.
target-block-time = 15                  # Target time between blocks (transaction confirmation delay), seconds. (2 - 86400)
maximum-block-size = 8388608            # Maximum block size in bytes. (1000 - 1000000000)

# Global permissions

anyone-can-connect = true               # Anyone can connect, i.e. a publicly readable blockchain.
anyone-can-send = true                  # Anyone can send, i.e. transaction signing not restricted by address.
anyone-can-receive = true               # Anyone can receive, i.e. transaction outputs not restricted by address.
anyone-can-receive-empty = true         # Anyone can receive empty output, i.e. without permission grants, asset transfers and zero native currency.
anyone-can-create = false               # Anyone can create new streams.
anyone-can-issue = false                # Anyone can issue new native assets.
anyone-can-mine = true                  # Anyone can mine blocks (confirm transactions).
anyone-can-activate = false             # Anyone can grant or revoke connect, send and receive permissions.
anyone-can-admin = false                # Anyone can grant or revoke all permissions.
support-miner-precheck = true           # Require special metadata output with cached scriptPubKey for input, to support advanced miner checks.
allow-arbitrary-outputs = false         # Allow arbitrary (without clear destination) scripts.
allow-p2sh-outputs = true               # Allow pay-to-scripthash (P2SH) scripts, often used for multisig. Ignored if allow-arbitrary-outputs=true.
allow-multisig-outputs = true           # Allow bare multisignature scripts, rarely used but still supported. Ignored if allow-arbitrary-outputs=true.

# Defaults for node runtime parameters

lock-admin-mine-rounds = 10             # Ignore forks that reverse changes in admin or mine permissions after this many mining rounds have passed. Integer only. (0 - $
mining-requires-peers = true            # Nodes only mine blocks if connected to other nodes (ignored if only one permitted miner).
mine-empty-rounds = 10                  # Mine this many rounds of empty blocks before pausing to wait for new transactions. If negative, continue indefinitely (ignore$
mining-turnover = 0.5                   # Prefer pure round robin between a subset of active miners to minimize forks (0.0) or random equal participation for all permi$

# Native blockchain currency (likely not required)

initial-block-reward = 1000000          # Initial block mining reward in raw native currency units. (0 - 1000000000000000000)
first-block-reward = -1                 # Different mining reward for first block only, ignored if negative. (-1 - 1000000000000000000)
reward-halving-interval = 52560000      # Interval for halving of mining rewards, in blocks. (60 - 1000000000)
reward-spendable-delay = 1              # Delay before mining reward can be spent, in blocks. (1 - 100000)
minimum-per-output = 0                  # Minimum native currency per output (anti-dust), in raw units.
                                        # If set to -1, this is calculated from minimum-relay-fee. (-1 - 1000000000)
maximum-per-output = 100000000000000    # Maximum native currency per output, in raw units. (0 - 1000000000000000000)
minimum-relay-fee = 0                   # Minimum transaction fee, per 1000 bytes, in raw units of native currency. (0 - 1000000000)
native-currency-multiple = 10           # Number of raw units of native currency per display unit. (0 - 1000000000)

only-accept-std-txs = true              # Only accept and relay transactions which qualify as 'standard'.
max-std-tx-size = 4194304               # Maximum size of standard transactions, in bytes. (1024 - 100000000)
max-std-op-returns-count = 10           # Maximum number of OP_RETURN metadata outputs in standard transactions. (0 - 1024)
max-std-op-return-size = 2097152        # Maximum size of OP_RETURN metadata in standard transactions, in bytes. (0 - 67108864)
max-std-op-drops-count = 5              # Maximum number of OP_DROPs per output in standard transactions. (0 - 100)
max-std-element-size = 8192             # Maximum size of data elements in standard transactions, in bytes. (128 - 32768)
# The following parameters were generated by multichain-util.
# They SHOULD ONLY BE EDITED IF YOU KNOW WHAT YOU ARE DOING.

default-network-port = 8300             # Default TCP/IP port for peer-to-peer connection with other nodes.
default-rpc-port = 2654                 # Default TCP/IP port for incoming JSON-RPC API requests.
chain-name = ecupaybeta2                # Chain name, used as first argument for multichaind and multichain-cli.
protocol-version = 10009                # Protocol version at the moment of blockchain genesis.
network-message-start = f9beb4d9        # Magic value sent as the first 4 bytes of every peer-to-peer message.
address-pubkeyhash-version = 00         # Version bytes used for pay-to-pubkeyhash addresses.
address-scripthash-version = 05         # Version bytes used for pay-to-scripthash addresses.
private-key-version = 80                # Version bytes used for exporting private keys.
address-checksum-value = 00000000       # Bytes used for XOR in address checksum calculation.
asked Feb 13, 2018 by davotrade

1 Answer

0 votes

There are a number of things to take care of when trying to connect a bitcoin wallet to a MultiChain network (even if it's running the bitcoin protocol). This is covered in detail here: https://www.multichain.com/developers/peer-handshaking/#bitcoin

answered Feb 14, 2018 by MultiChain
...