惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - Franky
C
CXSECURITY Database RSS Feed - CXSecurity.com
S
Schneier on Security
Know Your Adversary
Know Your Adversary
Security Latest
Security Latest
Spread Privacy
Spread Privacy
Project Zero
Project Zero
T
The Exploit Database - CXSecurity.com
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
AI
AI
N
News | PayPal Newsroom
A
Arctic Wolf
NISL@THU
NISL@THU
W
WeLiveSecurity
Security Archives - TechRepublic
Security Archives - TechRepublic
Hacker News: Ask HN
Hacker News: Ask HN
P
Palo Alto Networks Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
大猫的无限游戏
大猫的无限游戏
L
Lohrmann on Cybersecurity
Last Week in AI
Last Week in AI
T
Threatpost
The Last Watchdog
The Last Watchdog
博客园_首页
C
Cybersecurity and Infrastructure Security Agency CISA
酷 壳 – CoolShell
酷 壳 – CoolShell
量子位
Engineering at Meta
Engineering at Meta
爱范儿
爱范儿
aimingoo的专栏
aimingoo的专栏
S
Security Affairs
P
Privacy & Cybersecurity Law Blog
B
Blog RSS Feed
AWS News Blog
AWS News Blog
P
Proofpoint News Feed
雷峰网
雷峰网
T
Tenable Blog
Schneier on Security
Schneier on Security
H
Heimdal Security Blog
V2EX - 技术
V2EX - 技术
V
V2EX
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
S
Secure Thoughts
Latest news
Latest news
Help Net Security
Help Net Security
Jina AI
Jina AI
Stack Overflow Blog
Stack Overflow Blog
The Cloudflare Blog
V
Vulnerabilities – Threatpost
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org

博客园 - 杨义金

Csla One or more properties are not registered for this type unomp 矿池运行问题随记 矿池负载运行监测记录 MySql 数据库移植记录 后台服务运行后无故停止运行,原因不明 缓存过期时间的设置 关于 CSLA 服务器部署WCF访问出错的问题 AR 不同 继承映射的问题总结 当事人角色 变更映射策略引起的问题 Castle ActiveRecord 二级缓存使用 异常记录 VS2013 抛出 stackoverflow exception 的追踪 CastleActiveRecord在多线程 事务提交时数据库资源竞争导致更新失败的测试结果记录 WF4.0 工作流设计器 传入参数问题记录? Solving GitHub FetchHead (MergeConflict) in Visual Studio 2013 昆明光标科技有限公司简介 Castle.ActiveRecord 多对多关系 引发的错误处理 String PK StringBuilder,传说就是传说,只有动手实验,才能得出确定的答案 .net mvc Bundle 问题解决方案 .net 4.0 自定义本地缓存策略的不同实现
Bitcoin 使用及配置记录
杨义金 · 2019-02-12 · via 博客园 - 杨义金

bitcoin-qt.exe -testnet -printtoconsole -conf=D:\Bitcoin\bitcoin.conf -datadir=D:\Bitcoin\Data

bitcoin-qt.exe -testnet -printtoconsole -conf=D:\Bitcoin\bitcoin-0.15.2\bin\bitcoin.conf -datadir=D:\Bitcoin\Data

bitcoin-cli -rpcport=18332 -rpcuser=rpcuser -rpcpassword=rpcpassword getblockchaininfo

bitcoin-cli -rpcport=18333 -rpcuser=rpcuser -rpcpassword=rpcpassword getinfo

bitcoin-cli -rpcconnect=192.168.101.142 -rpcport=8332 -rpcuser=rpcuser -rpcpassword=rpcpassword getblockchaininfo

 配置文件如下:

##

## bitcoin.conf configuration file. Lines beginning with # are comments.

##

# Network-related settings:

# Run on the test network instead of the real bitcoin network.

testnet=1

# Run a regression test network

#regtest=0

# Connect via a SOCKS5 proxy

#proxy=127.0.0.1:9050

# Bind to given address and always listen on it. Use [host]:port notation for IPv6

#bind=<addr>

# Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6

#whitebind=<addr>

##############################################################

##            Quick Primer on addnode vs connect            ##

##  Let's say for instance you use addnode=4.2.2.4          ##

##  addnode will connect you to and tell you about the      ##

##    nodes connected to 4.2.2.4.  In addition it will tell ##

##    the other nodes connected to it that you exist so     ##

##    they can connect to you.                              ##

##  connect will not do the above when you 'connect' to it. ##

##    It will *only* connect you to 4.2.2.4 and no one else.##

##                                                          ##

##  So if you're behind a firewall, or have other problems  ##

##  finding nodes, add some using 'addnode'.                ##

##                                                          ##

##  If you want to stay private, use 'connect' to only      ##

##  connect to "trusted" nodes.                             ##

##                                                          ##

##  If you run multiple nodes on a LAN, there's no need for ##

##  all of them to open lots of connections.  Instead       ##

##  'connect' them all to one node that is port forwarded   ##

##  and has lots of connections.                            ##

##       Thanks goes to [Noodle] on Freenode.               ##

##############################################################

# Use as many addnode= settings as you like to connect to specific peers

#addnode=69.164.218.197

#addnode=10.0.0.2:8333

# Alternatively use as many connect= settings as you like to connect ONLY to specific peers

#connect=69.164.218.197

#connect=10.0.0.1:8333

# Listening mode, enabled by default except when 'connect' is being used

#listen=1

# Maximum number of inbound+outbound connections.

#maxconnections=

#

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

#

# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands

server=1

# Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6.

# This option can be specified multiple times (default: bind to all interfaces)

#rpcbind=<addr>

# If no rpcpassword is set, rpc cookie auth is sought. The default `-rpccookiefile` name

# is .cookie and found in the `-datadir` being used for bitcoind. This option is typically used

# when the server and client are run as the same user.

#

# If not, you must set rpcuser and rpcpassword to secure the JSON-RPC API.

#

# The config option `rpcauth` can be added to server startup argument. It is set at initialization time

# using the output from the script in share/rpcauth/rpcauth.py after providing a username:

#

# ./share/rpcauth/rpcauth.py alice

# String to be appended to bitcoin.conf:

# rpcauth=alice:f7efda5c189b999524f151318c0c86$d5b51b3beffbc02b724e5d095828e0bc8b2456e9ac8757ae3211a5d9b16a22ae

# Your password:

# DONT_USE_THIS_YOU_WILL_GET_ROBBED_8ak1gI25KFTvjovL3gAM967mies3E=

#

# On client-side, you add the normal user/password pair to send commands:

rpcuser=rpcuser

rpcpassword=rpcpassword

#

# You can even add multiple entries of these to the server conf file, and client can use any of them:

# rpcauth=bob:b2dd077cb54591a2f3139e69a897ac$4e71f08d48b4347cf8eff3815c0e25ae2e9a4340474079f55705f40574f4ec99

# How many seconds bitcoin will wait for a complete RPC HTTP request.

# after the HTTP connection is established. 

#rpcclienttimeout=30

# By default, only RPC connections from localhost are allowed.

# Specify as many rpcallowip= settings as you like to allow connections from other hosts,

# either as a single IPv4/IPv6 or with a subnet specification.

# NOTE: opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED,

# because the rpcpassword is transmitted over the network unencrypted.

# server=1 tells Bitcoin-Qt to accept JSON-RPC commands.

# it is also read by bitcoind to determine if RPC should be enabled 

#rpcallowip=10.1.1.34/255.255.255.0

#rpcallowip=1.2.3.4/24

#rpcallowip=2001:db8:85a3:0:0:8a2e:370:7334/96

#rpcallowip=192.168.101.149

rpcallowip=192.168.101.0/24

# Listen for RPC connections on this TCP port:

rpcport=8332

# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind

# running on another host using this option:

rpcconnect=127.0.0.1

# Wallet options

# Create transactions that have enough fees so they are likely to begin confirmation within n blocks (default: 6).

# This setting is over-ridden by the -paytxfee option.

#txconfirmtarget=n

# Pay a transaction fee every time you send bitcoins.

#paytxfee=0.000x

# Miscellaneous options

# Pre-generate this many public/private key pairs, so wallet backups will be valid for

# both prior transactions and several dozen future transactions.

#keypool=100

# Set gen=1 to attempt to generate bitcoins

gen=1

# Enable pruning to reduce storage requirements by deleting old blocks. 

# This mode is incompatible with -txindex and -rescan.

# 0 = default (no pruning).

# 1 = allows manual pruning via RPC.

# >=550 = target to stay under in MiB. 

#prune=550

# User interface options

# Start Bitcoin minimized

#min=1

# Minimize to the system tray

#minimizetotray=1