Primecoin deployment and start-up services on Windows

Source: Internet
Author: User

Tags: inux local tno leveldb byte bcache bytes default cal

Primecoin Deployment and startup services on Windows:

One, from the official access to the Primecoin Windows version of the installation package:

Two or one-way installation like installing the client:

Third, after the installation is successful it will automatically eject the client to run, synchronize the data, we turn it off:

Four, the service mode Kai Primecoin. (Non-client way OH)

Method One: Pure command interface

1. Under command line to D:\primecoin-server\Primecoin\daemon directory, execute the PRIMECOIND.EXT program under this directory:


Primecoind.ext-printtoconsole #-printtoconsole This parameter prints the result of the run, otherwise it will not show anything.

2, after running the server will synchronize the block height, this and Linux is the same. At the same time open another command interface, through the primecoin-cli getblockcount command to detect if you can see the height of synchronization, if so, the service is normal.

method Two: With a graphical interface.

1, to the \primecoin-server\primecoin directory

2, because the start with the graphical interface of the primecoin-qt.exe command in this.

3, with-server parameters can be used as a server to start.

4, with -rpcuser=user-rpcpassword=password These 2 parameters, or will be an error without account and password.

5, at the same time in another command interface ready to use primecoin-cli -rpcuser=user-rpcpassword=password getblockcount The command detects if the service is normal (can see the height of the chunk being synchronized).

6, note the primecoin-cli command directory and primecoin-qt.exe directory is not the same.

D:\primecoin-server\primecoinprimecoin-qt.exe-server-rpcuser=user-rpcpassword=passwordd:\primecoin-server\ Primecoin\daemonprimecoin-cli-rpcuser=user-rpcpassword=password Getblockcount

7, then the graphical interface will also be started, patient waiting:

8, after the graphical interface started successfully, then use primecoin-cli-rpcuser=user-rpcpassword=password getblockcount command to detect the success of the service:

9, also need to use a few commands to detect whether the service port is normal:

Netstat-ano | findstr 9911 Netstat-ano | Findstr 9912

As mentioned above, it indicates that the service is working properly, and that the Primecoin deployment and startup service on Windows is successful!

The following are the official Primecoin parameters:

Primecoin Core version V0.16.1.0-c58f796-dirty (64-bit)

BITCOIN-QT [command line Options]


Print out this help message and exit
Print version information and exit
Execute the command when a reminder is received or when we see a long fork (%s will be replaced with a message)
Executes a command when the best chunk changes (the%s in the command line is replaced with a block hash)
If this block was in the chain assume then it and its ancestors be valid and potentially skip their script verification (0 To verify all, default:0000000000000000000000000000000000000000000000000000000000000000, testnet: 0000000000000000000000000000000000000000000000000000000000000000)
Specify configuration file (default: bitcoin.conf)
Specify Data Directory
Set the database cache size in megabytes (4 to 16384, default: 450)
blk000 from other sources at startup??. DAT file Import chunks
Specify location of debug log file:this can is an absolute path or a path relative to the data directory (Default:debug. Log
Up to <n> off trades in memory (default: 100)
Keep the transaction memory pool size below &LT;N&GT;MB (default: 300)
Do not leave a transaction in the memory pool for more than <n> hours (default: 336)
Whether to save the memory pool on exit and reload at startup (default: 1)
Extra transactions to keep in memory for compact block reconstructions (default:100)
Set Script Validation Program (-4 to 16, 0 = auto, <0 = Reserved free core, default value: 0)
Reduce storage requirements by enabling pruning (deleting) of the old blocks. This allows the Pruneblockchain RPC to is called to delete specific blocks, and enables automatic pruning of old blocks if A target size in MiB is provided. This mode is incompatible With-txindex And-rescan. Warning:reverting This setting requires re-downloading the entire blockchain. (default:0 = Disable pruning blocks, 1 = Allow manual pruning via RPC, >550 = automatically prune block files to stay Under the specified target size in MiB)
Rebuilds the chain state from the current indexed chunk
Rebuild chain State and block index from the Blk*.dat files on disk
Maintain a complete trading index for Getrawtransaction RPC calls (default: 0)
Maintain a full address index, used by the Searchrawtransactions RPC call (default:0)

Connection options:

ADD a node to connect to and attempt to keep the connection open (see the ' addnode ' RPC command Help for more info)
Disconnect the threshold of the Indecent assault node (default: 100)
Restrict the indecent assault node from connecting in a few seconds (default: 86400)
Binds the specified IP address to start listening. IPV6 address please use [host]:p ORT format
Connect only to the specified node (s); -connect=0 disables automatic connections (the rules for this peer is the same as For-addnode)
Find your own IP address (default: 1 when listening and no-externalip or-proxy)
Allow querying of DNS when using-addnode,-seednode and-connect options (default: 1)
Query for peer addresses via DNS lookup, if low on addresses (default:1 Unless-connect used)
Specify your public address
Always query the node address via DNS (default: 0)
Accept connections from external (default: If the Or-connect parameter is set to 1 without the-proxy)
Automatically build Tor stealth service (default: 1)
Keep up to <n> node connections (default: 125)
Maximum receive cache per connection, <n>*1000 bytes (default: 5000)
Maximum send cache per connection, <n>*1000 bytes (default: 1000)
Maximum allowed median peer time offset adjustment. Local perspective of time is influenced by peers forward or backward by this amount. (default:4200 seconds)
Use different SOCKS5 proxies when connecting nodes via Tor hidden service (default:-proxy)
Connect only nodes in the <net> network (IPv4, IPv6 or onion)
Whether to forward multi-signature transactions in non-P2SH format (default: 1)
Support for filtering chunks and trades with Bloom filters (default: 1)
Use port <port> Listen connection (default: 9911; testnet:9913)
Connect via SOCKS5 Proxy
The randomization credentials are connected for each agent. This will enable Tor stream Isolation (default: 1)
Connect a node and get the peer address, then disconnect
Specify the number of connections timeout milliseconds (min: 1, default: 5000)
Tor control port number when listening for onion connection (default:
Tor Control port Password (default: blank)
Use UPnP to map listening ports (default: 0)
A whitelist node bound to the specified address and connection. IPV6 using [host]: Port format
-whitelist=<ip address or network>
Whitelist peers connecting from the given IP address (e.g. or CIDR notated network (e.g. Can be specified multiple times. A whitelist node cannot be banned by DOS and forwards all transactions from them (even if those transactions already exist in Mempool), often used in gateways
Try to keep upload bandwidth below (mib/24h), 0 = unrestricted (default: 0)

Wallet Options:

What type of addresses-use ("Legacy", "P2sh-segwit", or "Bech32", Default: "Legacy")
What type of change is use ("legacy", "P2sh-segwit", or "Bech32"). Default is same as-addresstype, except when-addresstype=p2sh-segwit a native Segwit output are used when sending to a NAT Ive segwit address)
Do not load wallets and disable RPC calls for wallets
Set the private key pool size to <n> (default: 1000)
Rate that will be enabled when cost estimate data (DEFAULT:BTC) is insufficient (in 0.0002/kb)
The fee rate (in btc/kb) is indicates your tolerance for discarding change by adding it to the fee (default:0.0001). Note:an output is discarded if it's dust at this rate, but we'll always have discard up to the dust relay fee and a discard Fee above that's limited by the fee estimate for the longest target
If a transaction fee per kilobyte (KB) is lower than this value (in BTC) when a trade is generated, it is treated as a no-charge (default: 0.00001)
Add transaction fee (BTC/KB) for payment transactions (default: 0.00)
Re-scan the blockchain to find missing wallet transactions
Try to recover the private key from the damaged wallet file at startup
Allow the use of unconfirmed change when making payment (default: 1)
If the transaction fee is not set, a sufficient transaction fee is automatically added to ensure that the transaction is confirmed within the average of n blocks (default: 6)
Send transactions with FULL-RBF opt-in enabled (RPC-only, default:0)
Upgrade wallet to latest format when program starts
Specify wallet file (in Data directory) (default: Wallet.dat)
Wallet broadcast transaction processing (default: 1)
Specify directory to Wallets (default: <datadir>/wallets if it exists, otherwise <datadir>)
Executes the command when the best chunk changes (the%s in the command line is replaced with a chunk hash value)
Delete all transactions for the wallet and only start the client with the-rescan parameter to retrieve the transaction (1 = Keep TX meta data, such as account owner and payment request information, 2 = Do not keep TX Meta data)

ZeroMQ notification Options:

Allow hash chunks in <address> broadcast
Allow hash transactions on <address> broadcast
Allow the original chunk to be broadcast in <address>
Allow the original transaction to be broadcast in <address>

Debug/Test options:

Attaching a description to the user agent string
Output debug Information (default: 0, provide <category> is optional). If <category> is not provided or <category> = 1, all debug information is output. <category> may be: NET, Tor, Mempool, HTTP, bench, ZMQ, DB, RPC, Estimatefee, Addrman, Selectcoins, Reindex, Cmpctblock , Rand, prune, proxy, Mempoolrej, libevent, Coindb, QT, Leveldb.
Exclude a class of debug information. Can be used with-debug=1 to output debug logs in addition to the specified category.
Show all debugging options (usage:--help-Help debugging)
Include IP address in debug output (default: 0)
When debugging information is output, precede it with a timestamp (default: 1)
Maximum single wallet or original transfer fee (BTC), setting too low may result in large size trading failure (default: 1000000000.00)
Trace/debug Information output to the console, not output to the Debug.log file
Compress the Debug.log file when client starts (default: No-debug mode is 1)

Blockchain selection options:

Using the test chain

Node Relay options:

Equivalent bytes per sigop in transactions for relay and Mining (DEFAULT:20)
Relay and mine data carrier transactions (DEFAULT:1)
Maximum size of data in data carrier transactions we relay and Mine (default:83)
Ensure transaction replacement in the memory pool (default: 1)
Transaction fee (in btc/kb) is smaller than this will be treated as a 0 fee transaction (default: 0.01) when correlating, mining, and generating transactions
Accept affiliate transactions from Whitelisted peers even when unrelated transactions (default: 1)
Force relay of transactions from whitelisted peers even if they violate local relay policy (DEFAULT:1)

Data Block Creation Options:

Set BIP141 maximum chunk weight (default: 3996000)
Set Maximum BIP141 block weight to this * 4. Deprecated, use Blockmaxweight
Set Lowest fee rate (in btc/kb) for transactions to is included in block creation. (default:0.00001)

RPC Server Options:

Accept command line and JSON-RPC command
Accept public REST requests (default: 0)
-rpcbind=<addr>[:p ORT]
Bind to given address to listen for JSON-RPC connections. This option was ignored UNLESS-RPCALLOWIP is also passed. Port is optional and overrides-rpcport. Use [host]:p ort notation for IPV6. This option can be specified multiple times (default: and:: 1 i.e., localhost, or if-rpcallowip have been specif IED, and:: i.e., all addresses)
Location of the authentication cookie (default: Data directory)
JSON-RPC Connection User Name
JSON-RPC Connection Password
Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <username>:<salt>$<hash>. A canonical Python script is included in Share/rpcuser. The client then connects normally using the rpcuser=<username>/rpcpassword=<password> pair of arguments. This option can be specified multiple times
Use the <port> port to monitor the JSON-RPC connection (default: 9912; testnet:9914)
Allows JSON-RPC connections from the specified address. <ip> for single IP (e.g., network/mask (e.g., network/CIDR (for example: This option can be specified more than once.
Sets the serialization of raw transaction or block Hex returned in non-verbose mode, Non-segwit (0) or Segwit (1) (Default: 1)
Set the number of RPC service threads (default: 4)

Interface options:

Select a directory at startup (default 0)
Set language, such as "ZH-CN" (Default: System language)
Minimized at startup
Set up SSL root certificates for payment requests (default:-System-)
Display splash screen (default: 1)
Reset all change settings in the graphical interface

Primecoin deployment and start-up services on Windows

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

Tags Index: