<source>Enterthenewpassphrasetothewallet.<br/>Pleaseuseapassphraseof<b>tenormorerandomcharacters</b>, or <b>eight or more words</b>.</source>
<source>Reuse one of the previously used receiving addresses. Reusing addresses has security and privacy issues. Do not use this unless re-generating a payment request made before.</source>
<source>An optional message to attach to the payment request, which will be displayed when the request is opened. Note: The message will not be sent with the payment over the Bitcoin network.</source>
<source>If the custom fee is set to 1000 satoshis and the transaction is only 250 bytes, then "per kilobyte" only pays 250 satoshis in fee, while "total at least" pays 1000 satoshis. For transactions bigger than a kilobyte both pay by kilobyte.</source>
<source>Paying only the minimum fee is just fine as long as there is less transaction volume than space in the blocks. But be aware that this can end up in a never confirming transaction once there is more demand for bitcoin transactions than the network can process.</source>
<source>The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here.</source>
<source>The Bitcoin address to send the payment to</source>
<translation>支払の送金先Bitcoinアドレス</translation>
</message>
<message>
<source>Alt+A</source>
<translation>Alt+A</translation>
</message>
<message>
<source>Paste address from clipboard</source>
<translation>クリップボードからアドレスを貼付ける</translation>
</message>
<message>
<source>Alt+P</source>
<translation>Alt+P</translation>
</message>
<message>
<source>Remove this entry</source>
<translation>この項目を削除する</translation>
</message>
<message>
<source>The fee will be deducted from the amount being sent. The recipient will receive less bitcoins than you enter in the amount field. If multiple recipients are selected, the fee is split equally.</source>
<source>A message that was attached to the bitcoin: URI which will be stored with the transaction for your reference. Note: This message will not be sent over the Bitcoin network.</source>
<source>Signatures - Sign / Verify a Message</source>
<translation>署名 - メッセージの署名/検証</translation>
</message>
<message>
<source>&Sign Message</source>
<translation>メッセージの署名 (&S)</translation>
</message>
<message>
<source>You can sign messages/agreements with your addresses to prove you can receive bitcoins sent to them. Be careful not to sign anything vague or random, as phishing attacks may try to trick you into signing your identity over to them. Only sign fully-detailed statements you agree to.</source>
<source>Enter the receiver'saddress,message(ensureyoucopylinebreaks,spaces,tabs,etc.exactly)andsignaturebelowtoverifythemessage.Becarefulnottoreadmoreintothesignaturethanwhatisinthesignedmessageitself,toavoidbeingtrickedbyaman-in-the-middleattack.Notethatthisonlyprovesthesigningpartyreceiveswiththeaddress,itcannotprovesendershipofanytransaction!</source>
<source>Generatedcoinsmustmature%1blocksbeforetheycanbespent.Whenyougeneratedthisblock,itwasbroadcasttothenetworktobeaddedtotheblockchain.Ifitfailstogetintothechain,itsstatewillchangeto"not accepted"anditwon't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.</source>
<source>Distributed under the MIT software license, see the accompanying file COPYING or <http://www.opensource.org/licenses/mit-license.php>.</source>
<source>Reduce storage requirements by pruning (deleting) old blocks. This mode disables wallet support and is incompatible with -txindex. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, >%u = target size in MiB to use for block files)</source>
<source>Warning: error reading wallet.dat! All keys read correctly, but transaction data or address book entries might be missing or incorrect.</source>
<source>Warning: wallet.dat corrupt, data salvaged! Original wallet.dat saved as wallet.{timestamp}.bak in %s; if your balance or transactions are incorrect you should restore from a backup.</source>
<source>Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified multiple times</source>
<source>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)</source>
<source>ThisproductincludessoftwaredevelopedbytheOpenSSLProjectforuseintheOpenSSLToolkit<https://www.openssl.org/> and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.</source>
<source>Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway</source>