比特幣Bitcoin,以太幣ETH,達世幣Dash,挖礦與電腦軟硬體

網路服務 => [虛擬幣] Bitcoin比特幣(位元幣)(ビットコイン)(BTC) => 主題作者是: 苦勞礦工 於 2014 三月 22, 下午 06:24



主題: [比特幣Bitcoin] Bitcoin-Qt 錢包軟體 新版本 0.9.0 (64bit可用)
作者: 苦勞礦工2014 三月 22, 下午 06:24
[比特幣Bitcoin] Bitcoin-Qt 錢包軟體 新版本 0.9.0 (64bit可用)

Bitcoin Core version 0.9.0 is now available from:

  https://bitcoin.org/bin/0.9.0/

This is a new major version release, bringing both new features and
bug fixes.

Please report bugs using the issue tracker at github:

  https://github.com/bitcoin/bitcoin/issues

How to Upgrade
--------------

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), uninstall all
earlier versions of Bitcoin, then run the installer (on Windows) or just copy
over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

If you are upgrading from version 0.7.2 or earlier, the first time you run
0.9.0 your blockchain files will be re-indexed, which will take anywhere from
30 minutes to several hours, depending on the speed of your machine.

On Windows, do not forget to uninstall all earlier versions of the Bitcoin
client first, especially if you are switching to the 64-bit version.

Windows 64-bit installer
-------------------------

New in 0.9.0 is the Windows 64-bit version of the client. There have been
frequent reports of users running out of virtual memory on 32-bit systems
during the initial sync. Because of this it is recommended to install the
64-bit version if your system supports it.

NOTE: Release candidate 2 Windows binaries are not code-signed; use PGP
and the SHA256SUMS.asc file to make sure your binaries are correct.
In the final 0.9.0 release, Windows setup.exe binaries will be code-signed.

OSX 10.5 / 32-bit no longer supported
-------------------------------------

0.9.0 drops support for older Macs. The minimum requirements are now:
* A 64-bit-capable CPU (see http://support.apple.com/kb/ht3696);
* Mac OS 10.6 or later (see https://support.apple.com/kb/ht1633).

Downgrading warnings
--------------------

The 'chainstate' for this release is not always compatible with previous
releases, so if you run 0.9 and then decide to switch back to a
0.8.x release you might get a blockchain validation error when starting the
old release (due to 'pruned outputs' being omitted from the index of
unspent transaction outputs).

Running the old release with the -reindex option will rebuild the chainstate
data structures and correct the problem.

Also, the first time you run a 0.8.x release on a 0.9 wallet it will rescan
the blockchain for missing spent coins, which will take a long time (tens
of minutes on a typical machine).

Rebranding to Bitcoin Core
---------------------------

To reduce confusion between Bitcoin-the-network and Bitcoin-the-software we
have renamed the reference client to Bitcoin Core.


OP_RETURN and data in the block chain
-------------------------------------
On OP_RETURN:  There was been some confusion and misunderstanding in
the community, regarding the OP_RETURN feature in 0.9 and data in the
blockchain.  This change is not an endorsement of storing data in the
blockchain.  The OP_RETURN change creates a provably-prunable output,
to avoid data storage schemes -- some of which were already deployed --
that were storing arbitrary data such as images as forever-unspendable
TX outputs, bloating bitcoin's UTXO database.

Storing arbitrary data in the blockchain is still a bad idea; it is less
costly and far more efficient to store non-currency data elsewhere.

Autotools build system
-----------------------

For 0.9.0 we switched to an autotools-based build system instead of individual
(q)makefiles.

Using the standard "./autogen.sh; ./configure; make" to build Bitcoin-Qt and
bitcoind makes it easier for experienced open source developers to contribute
to the project.

Be sure to check doc/build-*.md for your platform before building from source.

Bitcoin-cli
-------------

Another change in the 0.9 release is moving away from the bitcoind executable
functioning both as a server and as a RPC client. The RPC client functionality
("tell the running bitcoin daemon to do THIS") was split into a separate
executable, 'bitcoin-cli'. The RPC client code will eventually be removed from
bitcoind, but will be kept for backwards compatibility for a release or two.

`walletpassphrase` RPC
-----------------------

The behavior of the `walletpassphrase` RPC when the wallet is already unlocked
has changed between 0.8 and 0.9.

The 0.8 behavior of `walletpassphrase` is to fail when the wallet is already unlocked:

    > walletpassphrase 1000
    walletunlocktime = now + 1000
    > walletpassphrase 10
    Error: Wallet is already unlocked (old unlock time stays)

The new behavior of `walletpassphrase` is to set a new unlock time overriding
the old one:

    > walletpassphrase 1000
    walletunlocktime = now + 1000
    > walletpassphrase 10
    walletunlocktime = now + 10 (overriding the old unlock time)

Transaction malleability-related fixes
--------------------------------------

This release contains a few fixes for transaction ID (TXID) malleability
issues:

- -nospendzeroconfchange command-line option, to avoid spending
  zero-confirmation change
- IsStandard() transaction rules tightened to prevent relaying and mining of
  mutated transactions
- Additional information in listtransactions/gettransaction output to
  report wallet transactions that conflict with each other because
  they spend the same outputs.
- Bug fixes to the getbalance/listaccounts RPC commands, which would report
  incorrect balances for double-spent (or mutated) transactions.
- New option: -zapwallettxes to rebuild the wallet's transaction information

Transaction Fees
----------------

This release drops the default fee required to relay transactions across the
network and for miners to consider the transaction in their blocks to
0.01mBTC per kilobyte.

Note that getting a transaction relayed across the network does NOT guarantee
that the transaction will be accepted by a miner; by default, miners fill
their blocks with 50 kilobytes of high-priority transactions, and then with
700 kilobytes of the highest-fee-per-kilobyte transactions.

The minimum relay/mining fee-per-kilobyte may be changed with the
minrelaytxfee option. Note that previous releases incorrectly used
the mintxfee setting to determine which low-priority transactions should
be considered for inclusion in blocks.

The wallet code still uses a default fee for low-priority transactions of
0.1mBTC per kilobyte. During periods of heavy transaction volume, even this
fee may not be enough to get transactions confirmed quickly; the mintxfee
option may be used to override the default.

0.9.0 Release notes
=======================

RPC:

- New notion of 'conflicted' transactions, reported as confirmations: -1
- 'listreceivedbyaddress' now provides tx ids
- Add raw transaction hex to 'gettransaction' output
- Updated help and tests for 'getreceivedby(account|address)'
- In 'getblock', accept 2nd 'verbose' parameter, similar to getrawtransaction,
  but defaulting to 1 for backward compatibility
- Add 'verifychain', to verify chain database at runtime
- Add 'dumpwallet' and 'importwallet' RPCs
- 'keypoolrefill' gains optional size parameter
- Add 'getbestblockhash', to return tip of best chain
- Add 'chainwork' (the total work done by all blocks since the genesis block)
  to 'getblock' output
- Make RPC password resistant to timing attacks
- Clarify help messages and add examples
- Add 'getrawchangeaddress' call for raw transaction change destinations
- Reject insanely high fees by default in 'sendrawtransaction'
- Add RPC call 'decodescript' to decode a hex-encoded transaction script
- Make 'validateaddress' provide redeemScript
- Add 'getnetworkhashps' to get the calculated network hashrate
- New RPC 'ping' command to request ping, new 'pingtime' and 'pingwait' fields
  in 'getpeerinfo' output
- Adding new 'addrlocal' field to 'getpeerinfo' output
- Add verbose boolean to 'getrawmempool'
- Add rpc command 'getunconfirmedbalance' to obtain total unconfirmed balance
- Explicitly ensure that wallet is unlocked in `importprivkey`
- Add check for valid keys in `importprivkey`

Command-line options:

- New option: -nospendzeroconfchange to never spend unconfirmed change outputs
- New option: -zapwallettxes to rebuild the wallet's transaction information
- Rename option '-tor' to '-onion' to better reflect what it does
- Add '-disablewallet' mode to let bitcoind run entirely without wallet (when
  built with wallet)
- Update default '-rpcsslciphers' to include TLSv1.2
- make '-logtimestamps' default on and rework help-message
- RPC client option: '-rpcwait', to wait for server start
- Remove '-logtodebugger'
- Allow `-noserver` with bitcoind

Block-chain handling and storage:

- Update leveldb to 1.15
- Check for correct genesis (prevent cases where a datadir from the wrong
  network is accidentally loaded)
- Allow txindex to be removed and add a reindex dialog
- Log aborted block database rebuilds
- Store orphan blocks in serialized form, to save memory
- Limit the number of orphan blocks in memory to 750
- Fix non-standard disconnected transactions causing mempool orphans
- Add a new checkpoint at block 279,000

Wallet:

- Bug fixes and new regression tests to correctly compute
  the balance of wallets containing double-spent (or mutated) transactions
- Store key creation time. Calculate whole-wallet birthday.
- Optimize rescan to skip blocks prior to birthday
- Let user select wallet file with -wallet=foo.dat
- Consider generated coins mature at 101 instead of 120 blocks
- Improve wallet load time
- Don't count txins for priority to encourage sweeping
- Don't create empty transactions when reading a corrupted wallet
- Fix rescan to start from beginning after importprivkey
- Only create signatures with low S values

Mining:

- Increase default -blockmaxsize/prioritysize to 750K/50K
- 'getblocktemplate' does not require a key to create a block template
- Mining code fee policy now matches relay fee policy

Protocol and network:

- Drop the fee required to relay a transaction to 0.01mBTC per kilobyte
- Send tx relay flag with version
- New 'reject' P2P message (BIP 0061, see
  https://gist.github.com/gavinandresen/7079034 for draft)
- Dump addresses every 15 minutes instead of 10 seconds
- Relay OP_RETURN data TxOut as standard transaction type
- Remove CENT-output free transaction rule when relaying
- Lower maximum size for free transaction creation
- Send multiple inv messages if mempool.size > MAX_INV_SZ
- Split MIN_PROTO_VERSION into INIT_PROTO_VERSION and MIN_PEER_PROTO_VERSION
- Do not treat fFromMe transaction differently when broadcasting
- Process received messages one at a time without sleeping between messages
- Improve logging of failed connections
- Bump protocol version to 70002
- Add some additional logging to give extra network insight
- Added new DNS seed from bitcoinstats.com

Validation:

- Log reason for non-standard transaction rejection
- Prune provably-unspendable outputs, and adapt consistency check for it.
- Detect any sufficiently long fork and add a warning
- Call the -alertnotify script when we see a long or invalid fork
- Fix multi-block reorg transaction resurrection
- Reject non-canonically-encoded serialization sizes
- Reject dust amounts during validation
- Accept nLockTime transactions that finalize in the next block

Build system:

- Switch to autotools-based build system
- Build without wallet by passing `--disable-wallet` to configure, this
  removes the BerkeleyDB dependency
- Upgrade gitian dependencies (libpng, libz, libupnpc, boost, openssl) to more
  recent versions
- Windows 64-bit build support
- Solaris compatibility fixes
- Check integrity of gitian input source tarballs
- Enable full GCC Stack-smashing protection for all OSes

GUI:

- Switch to Qt 5.2.0 for Windows build
- Add payment request (BIP 0070) support
- Improve options dialog
- Show transaction fee in new send confirmation dialog
- Add total balance in overview page
- Allow user to choose data directory on first start, when data directory is
  missing, or when the -choosedatadir option is passed
- Save and restore window positions
- Add vout index to transaction id in transactions details dialog
- Add network traffic graph in debug window
- Add open URI dialog
- Add Coin Control Features
- Improve receive coins workflow: make the 'Receive' tab into a form to request
  payments, and move historical address list functionality to File menu.
- Rebrand to `Bitcoin Core`
- Move initialization/shutdown to a thread. This prevents "Not responding"
  messages during startup. Also show a window during shutdown.
- Don't regenerate autostart link on every client startup
- Show and store message of normal bitcoin:URI
- Fix richtext detection hang issue on very old Qt versions
- OS X: Make use of the 10.8+ user notification center to display Growl-like
  notifications
- OS X: Added NSHighResolutionCapable flag to Info.plist for better font
  rendering on Retina displays.
- OS X: Fix bitcoin-qt startup crash when clicking dock icon
- Linux: Fix Gnome bitcoin: URI handler

Miscellaneous:

- Add Linux script (contrib/qos/tc.sh) to limit outgoing bandwidth
- Add '-regtest' mode, similar to testnet but private with instant block
  generation with 'setgenerate' RPC.
- Add 'linearize.py' script to contrib, for creating bootstrap.dat
- Add separate bitcoin-cli client




主題: [比特幣Bitcoin] Bitcoin-Qt 錢包軟體 新版本 0.9.0 (64bit可用) 參數指令
作者: 苦勞礦工2014 三月 22, 下午 06:29
[比特幣Bitcoin] Bitcoin-Qt 錢包軟體 新版本 0.9.0 (64bit可用) 參數指令

位元幣核心 版本 v0.9.0.0-g92d25e4-beta

用法:
  bitcoin-qt [命令列選項]                    

選項:
  -?                     這些說明訊息
  -conf=<file>           指定設定檔(預設值: bitcoin.conf)
  -datadir=<dir>         指定資料目錄
  -testnet               使用測試網路
  -pid=<file>            指定行程識別碼(PID)檔(預設值:  bitcoind.pid)
  -gen                   生產位元幣(預設值: 0)
  -dbcache=<n>           Set database cache size in megabytes (4 to 4096, default: 100)
  -timeout=<n>           指定連線在幾毫秒後逾時(預設值: 5000)
  -proxy=<ip:port>       透過 SOCKS 代理伺服器來連線
  -socks=<n>             選擇 -proxy 指定代理伺服器的 SOCKS 協定版本(4 或 5, 預設值: 5)
  -onion=<ip:port>       使用另外的 SOCK5 代理伺服器,來透過 Tor 隱藏服務跟節點聯繫(預設值: 同 -proxy)
  -dns                   允許對 -addnode, -seednode, -connect 的參數使用域名查詢
  -port=<port>           在通訊埠 <port> 聽候連線(預設值: 8333, 或若是測試網路: 18333)
  -maxconnections=<n>    維持連線節點數的上限為 <n> 個(預設值: 125)
  -addnode=<ip>          增加一個要連線的節線,並試著保持對它的連線暢通
  -connect=<ip>          只連線到指定節點(可多個)
  -seednode=<ip>         連線到某個節點來取得其它節點的位址,然後斷線
  -externalip=<ip>       指定自己的公開位址
  -onlynet=<net>         只和 <net> 網路上的節點連線(IPv4, IPv6, 或 Tor)
  -discover              找出自己的網際網路位址(預設值: 當有聽候連線且沒有 -externalip 時為 1)
  -checkpoints           只接受跟內建的檢查段點吻合的區塊鏈(預設值: 1)
  -listen                是否接受外來連線(預設值: 當沒有 -proxy 或 -connect 時為 1)
  -bind=<addr>           和指定的位址繫結,並總是在指定位址聽候連線。IPv6 請用 [主機]:通訊埠 這種格式
  -dnsseed               是否允許在找節點時使用域名查詢(預設值: 當沒用 -connect 時為 1)
  -banscore=<n>          把異常節點斷線的臨界值(預設值: 100)
  -bantime=<n>           拒絕跟異常節點連線的秒數(預設值: 86400)
  -maxreceivebuffer=<n>  每個連線的接收緩衝區大小上限為 <n>*1000 個位元組(預設值: 5000)
  -maxsendbuffer=<n>     每個連線的傳送緩衝區大小上限為 <n>*1000 位元組(預設值: 1000)
  -upnp                  是否要使用通用即插即用(UPnP)協定,來設定聽候連線的通訊埠的對應(預設值: 當有聽候連線時為 1)
  -debug=<category>      輸出除錯資訊(預設值: 0, 可以不指定 <category>)
                         如果沒有提供 <category> 就會輸出所有的除錯資訊。
                         <category> 可以是: addrman, alert, coindb, db, lock, rand, rpc, selectcoins, mempool, net, qt.
  -logtimestamps         在除錯輸出內容前附加時間(預設值: 1)
  -shrinkdebugfile       客戶端軟體啓動時把 debug.log 檔縮小(預設值: 當沒有 -debug 時為 1)
  -printtoconsole        在終端機顯示追蹤或除錯資訊,而不是寫到檔案 debug.log 中
  -regtest               進入回歸測試模式,使用可以立即解出區塊的特殊區塊鏈。
                         這是設計用來給回歸測試工具和應用程式開發用的。
  -server                接受指令列和 JSON-RPC 指令

  -rpcuser=<user>        JSON-RPC 連線使用者名稱
  -rpcpassword=<pw>      JSON-RPC 連線密碼
  -rpcport=<port>        在通訊埠 <port> 聽候 JSON-RPC 連線(預設值: 8332, 或若是測試網路: 18332)
  -rpcallowip=<ip>       允許指定的來源 IP 位址進行 JSON-RPC 連線
  -rpcthreads=<n>        設定處理 RPC 服務請求的執行緒數目(預設值: 4)
  -blocknotify=<cmd>     當最新區塊改變時要執行的指令(指令中的 %s 會被取代成區塊雜湊值)
  -alertnotify=<cmd>     當收到相關警示,或發現相當長的分支時,所要執行的指令(指令中的 %s 會被取代成警示訊息)
  -keypool=<n>           設定密鑰池大小成 <n> (預設值: 100)
  -checkblocks=<n>       啓動時檢查的區塊數(預設值: 288, 指定 0 表示全部)
  -checklevel=<n>        區塊檢查的仔細程度(0 到 4, 預設值: 3)
  -txindex               維護全部交易的索引(預設值: 0)
  -loadblock=<file>      從其它來源的 blk000??.dat 檔匯入區塊
  -reindex               從目前的區塊檔 blk000??.dat 重建區塊鏈的索引
  -par=<n>               設定指令碼驗證的執行緒數目(最多為 16, 若為 0 表示程式自動決定,小於 0 表示保留不用的處理器核心數目,預設值: 0)

錢包選項:
  -disablewallet         不要載入錢包,並且拿掉錢包相關的 RPC 功能呼叫。
  -paytxfee=<amt>        交易時每一千位元組(kB)加付的交易手續費
  -rescan                重新掃描區塊鏈,來尋找錢包可能漏掉的交易。
  -zapwallettxes         Clear list of wallet transactions (diagnostic tool; implies -rescan)
  -salvagewallet         嘗試從壞掉的錢包檔 wallet.dat 復原密鑰
  -upgradewallet         把錢包檔案升級成最新的格式
  -wallet=<file>         指定錢包檔(會在資料目錄中)
  -walletnotify=<cmd>    當錢包有交易改變時要執行的指令(指令中的 %s 會被取代成交易識別碼)
  -spendzeroconfchange   Spend unconfirmed change when sending transactions (default: 1)

區塊製造選項:
  -blockminsize=<n>      設定區塊大小下限成多少位元組(預設值: 0)
  -blockmaxsize=<n>      設定區塊大小上限成多少位元組(預設值: 750000)
  -blockprioritysize=<n> 設定高優先度或低手續費的交易資料大小上限成多少位元組(預設值: 50000)

SSL 選項: (SSL 設定程序請見 Bitcoin Wiki)
  -rpcssl                                  在 JSON-RPC 連線使用 OpenSSL (https)
  -rpcsslcertificatechainfile=<file.cert>  伺服器憑證檔(預設值: server.cert)
  -rpcsslprivatekeyfile=<file.pem>         伺服器私鑰檔(預設值: server.pem)
  -rpcsslciphers=<ciphers>                 可接受的加密演算法 (預設值: TLSv1.2+HIGH:TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!3DES:@STRENGTH)

使用界面選項:
  -lang=<lang>           設定語言,比如說 de_DE (預設值: 系統語系)
  -min                   啓動時縮到最小
  -splash                顯示啓動畫面(預設值: 1)
  -choosedatadir         啓動時選擇資料目錄(預設值: 0)