As you can see, I am starting a ponzi. How to enter: Send no more than 0.01 and not less than 0.005 BTC to 1Dg74LcegcwcGcjMzKazZecWVBcgzRKcr https://blockchain.info/address/1Dg74LcegcwcGcjMzKazZecWVBcgzRKcrTransactions: None yet I will send payment to the first guy after 2 more people have sent me, then from then on every person who sends me the BTC I'm interested actually. Send coins to 125EfLJBDGvTPrGwqwFVYwCt4PaDcwMLYG. I'll look after the money and give it back but will earn you 120% interest per megabyte! |
|
|
|
This forum is hilarious, how do you actually post a Ponzi scheme where its known that it does not give any real profit?
You have to be careful on this forum indeed! Ponzis are popular among some gamblers It's not a used Hyundai... it's a fucking Ponzi. There's only one way the gamble will work out... with the investor losing. WHat next? "Throw in some herpes and I'll gamble on your Ponzi scheme!" You'd be better gambling on...Moolah. If only ponzi could get some good PR change behind it and give the Ponzi scheme idea negative connotations; similar to pyramid scams or something... hmmm. |
|
|
|
|
Can you tell me why this is self moderated?
|
|
|
|
As I pointed out in the original article I published at CoinJoint, this coin was clearly a scam until the the developers had transparent vaults and transparency behind the coins that were being mined through Proof-of-work/mining. http://coinjoint.info/midascoin-launches-gold-backed-proof-mining-pom-blockchain/Everyone was warned these developers were using your hashing power to mine other coins. I hope the crypto world has finally learned their lesson about demanding transparency FIRST AND FOREMOST. I regret not coming here and telling people to get out of this coin, but I probably would have been labeled a troll anyways. You know, I said the same on Twitter and the dev told me to stop spreading fud and harassing customers. I have an honest question though: how can anyone in this climate believe the dev's claims WITHOUT PROOF of any kind? 1. Dev had no proof of gold. Ever. And price based on 333g increase in gold stores daily. So 700oz + 333g daily but no proof of this means 0g/on gold 2. How can a dev claim his scrypt mining is triple in profitability with a given hashrate? It's impossible and furthermore it was opaque. Re 1) I posted here showing the bank emailed me denying any safe deposit boxes were at an investment/portfolio only branch 2) If you mine the only way to triple profit is to triple hashrate. You're not mining money, it's needs to be exchanged! I am not trying to rub salt in the wound; I want to understand why people would believe this dev. If someone came up to them on the street and said "I've got a fortune in gold and you'll be working for free but will get paid eventually" would you back them? It's an honest question. I'll share with you what is happening to the dev; he's going to be arrested for commodities fraud as complaints were made to the relevant authorities. This is not trivia at all and there will be recourse for this. If not today then for another scam. Take this is a lesson and please, share with everyone how you got convinced and it'll help humanize this scam and help others later on given your responses. |
|
|
|
That is excellent news. Huge for the value of the currency because it lets it actually BE a currency. Anywhere BTC is accepted. Makes it much easier for merchants to get on board too. Win/win.
Can you comment on above query re coingateway? |
|
|
|
We are proud to present our first deal, in this case with CoinGateway. We have made an agreement, by which Munne will be present in their services since day 1 (post-ico). With this agreement, Munne investors will benefit from his service An honest question which isn't just applicable to MUNNE (how's it pronounced btw, like money or rhyming with hoof?) .... Why would people want to pay a 1% premium and also trust a third party (coingateway) to use MUNNE when they can use ฿ and avoid fees and relying on middleman trust? I'm not an expert so correct me if these details are wrong, but can you clarify this point? |
|
|
|
Its an interesting choice to see you change from an unmoderated to self-moderated topic so quickly.
Because an user insulted us twice for no reason. We tried to talk to him by message, and he continued insulting us. We think that if this happens in the first day, then it will be worse in the next days. We had the desire to create an unmoderated thread but now we realize that it would be unsustainable with people like that, so it’s better to take actions as soon as possible So you want to start a community called Commune but you're not ok with standard community debate. Don't you think you're totally screwing the pooch by saying "we're all about community and understanding their needs" but then deciding the community needs to be in line with your financial goals? Obviously the ICO is contractual, and now, so is this with self-moderation (contract being you'll defintelt delete anyone who "insults" you; which is kind of vague!) Good luck is all I can say. Volume bombing out on Bittrex and you've got nothing of any value besides redesigned UI when you show your community spirit only extends to valuing their input when it aligns with your values. So a dictatorship of sorts. It outlines how any problems will be dealt with too. I'd really consider taking off moderation because you lost me from the outset |
|
|
|
You know what? I've spent a good 50 hours on this and it's not about the money. It was fun. But with the total lack of updates on solved clues I am getting a bitter taste in my mouth regarding RushWallet altogether.
Yeah, they definitely need to release the rest of the solved solutions. You want us to have fun solving puzzles? Then don't throw clues like the following at us and then expect us to mind-meld with a methamphetamine addict schizophrenic who sees clues in this: "Dimitri says:" igeuapowhasfqewja;l87c347289rhn6yyfd043fqe54(**&^&^&^)90SDLKCDLSKMmDSHKKALGCHGlkholhhjkfhdsjkvbk())(*0u989y9y090E4455656>>>>>,,,,,!!!!!!!&PY8UCLICKCLACK He also says Rushwallet is not so easy to use, just like the contest! The funny thing is, at this point, I can't tell whether that clue is a joke or not! lolol Hahaha, it was a joke but point taken |
|
|
|
You know what? I've spent a good 50 hours on this and it's not about the money. It was fun. But with the total lack of updates on solved clues I am getting a bitter taste in my mouth regarding RushWallet altogether. Don't have technically minded people solving cryptic puzzles then offer to give clues via email which are distributed via a Poisson distribution where: Pr(email clue being sent) = |0.4| < [i]x[/i] < |0.6| for x R  where s = | the number of shits Kryptokit gives |, for all logical solutions of  You want us to have fun solving puzzles? Then don't throw clues like the following at us and then expect us to mind-meld with a methamphetamine addict schizophrenic who sees clues in this: "Dimitri says:" igeuapowhasfqewja;l87c347289rhn6yyfd043fqe54(**&^&^&^)90SDLKCDLSKMmDSHKKALGCHGlkholhhjkfhdsjkvbk())(*0u989y9y090E4455656>>>>>,,,,,!!!!!!!&PY8UCLICKCLACK He also says Rushwallet is not so easy to use, just like the contest! |
|
|
|
The only thing I haven't seen anyone mention yet is the 225 digit number.
Umm.. where exactly? Here: Scan the QR code  EDIT: To those qho are lazy or can't scan QR it's: 318596801091013404252109058498462849748 031058067101415476009525945888311527640 976738400000000000000000000000000000000 000000000000000000000000000000000000000 000000000000000000000000000000000000000 000000000000000000000000000000 FYI: goQR.me Qr link. So that's what your 225 digit number looks like in QR code. Look similar? AT ALL? Actually, no it doesn't. But, can I ask how did you find use for that number? Sorry, I am not much into QR but your discovery seems interesting. Hi mate, just saw this post. I made the QR code using the 225 digit number you quoted... unsure where you got that number from? the QR code for me came up as bitcoin:1J......... (the btc address above, not with info atm). Also, re QR codes rotated: Not so apparently as software rotates the code each time |
|
|
|
I wouldn't call it a scam "yet". Unless they failed to deliver orders in appropriate time. Thats why I ask if other people made any orders. My pending order still have about 2 weeks time for processing (saw somewhere 7-10 days processing) if they don't count weekends. However, I believe something has to be done to clarify backing of their currency and bolster trust. If this whole thing is a scam then they probably won't care. But if its legit, the current price on bittrex will drive them to bankruptcy if everyone orders gold off them. Or maybe they believe it is good promotion and have tons of spare gold to give?
All of the coins are accounted for when mining?? How would they go bankrupt? They don't care what the price on Bittrex is. I've been calling this a Fool's Gold Ponzi Pyramid from the outset. 1. There is no proof of gold 2. There is no proof of gold which they increase in quantity daily to justify the price 3. The mining "king" shows no proof of where the diverted hash rate is going 4. Midascoin claims their scrypt mining is 3x more profitable. How the fuck is that possible? 5. There's no proof of anything. Nothing. I honestly felt bad about people being scammed but at this stage I wonder if people would invest in something scrawled on a double ply white paper with the words "Midas = gold, Bittrex!" Btw, the bank where Midascoin claimed they stored gold says themselves they only do portfolio mgmt, from Twitter, this was the email reply; http://pastebin.com/QGWsA8NF |
|
|
|
The only thing I haven't seen anyone mention yet is the 225 digit number.
Umm.. where exactly? Here:  Scan the QR code EDIT: To those qho are lazy or can't scan QR it's: 318596801091013404252109058498462849748 031058067101415476009525945888311527640 976738400000000000000000000000000000000 000000000000000000000000000000000000000 000000000000000000000000000000000000000 000000000000000000000000000000 I scan it and get the BTC address horizontally found under the url; 1JmBVdo5fpkwYiDzFHFPcaiWkihc6WhxdB |
|
|
|
Considering the amount of utter hatred a lot of Bitcoin users have for Paypal I don't think the scenario will play out as you imagine and lets not forget that Bitcoin is open source and there are plenty of altcoins out there, I personally think software like Open Bazaar is going to be used more for trading in Bitcoin than Paypal/Ebay and those bastards at Paypal have been boasting and dragging their feet about Bitcoin adoption for months which makes me think they're going to do a shitty job implementing it.
Oh, did I also mention that they're trying to partner with GoCoin which has Brock Pierce in it's staff? Yeah, things are going to go really well for them, it's going to be fun to watch.
You think they just decided to implement BTC at PayPal recently? Dragging their feet is not my impression of how a company who specialises in payment processing approaches these matters. They didn't cave in to pressure. Now they're going to see first hand how to tweak BTC to their own ends. Oh it won't be called Bitcoin, but to think PayPal or even Apple turning around is from the minuscule amount of money they're losing in the big picture... You know how Google, Apple, Microsoft etc made it big? Not by letting the little guy win. If PayPal becomes the de facto cryptocurrency service provider then who's to say they'll implement updated BTC protocol? Maybe they'll find mining too expensive when it can be secured for less money. You know, business. It's going to be fun to watch only in the same way the weddings from Game of Thrones was fun to watch; the outcome was a massacre. Just not for the little guy. |
|
|
|
This smells like a troll / fud post to me. Paypal won't take it over. They'll just be a payment processor at the most just like any other.
You know, I'd love for talk to be an integral part of BitcoinTalk again. Satoshi once said it was unwise for Wikileaks to adopt BTC at that juncture. If it were anyone else that post would've been shot down as FUD or trolling. Can we talk about the grey clouds instead of pretending it's blue skies for eternity? Anyone who thinks Bitcoin has overcome all the challenges needs to remember Satoshi's quote (paraphrased); that Bitcoin is a grey metal, which is not entirely special. Can we entertain the premise that corporate interests can copy this technology and use it to their own ends, and if you think the Bitcoin community outweighs corporate America then think again; the community is no more useful in avoiding all debate than college protestors knowing their pickets change the world. I think we should discuss this rather than call troll. But let's see where we stand.... |
|
|
|
They will be able to control the price of Bitcoin.
Its practically a takeover and theres nothing you could do about it.
This is the only conclusion I have come to because the corporate world doesn't partner with such outmatched competition. They keep their enemies close. This is not good no matter how you look at it, IMO. |
|
|
|
Code 2/2: listreceivedbyaccount ( minconf includeempty )
List balances by account.
Arguments:
1. minconf (numeric, optional, default=1) The minimum number of confirmations before payments are included.
2. includeempty (boolean, optional, default=false) Whether to include accounts that haven't received any payments.
Result:
[
{
"account" : "accountname", (string) The account name of the receiving account
"amount" : x.xxx, (numeric) The total amount received by addresses with this account
"confirmations" : n (numeric) The number of confirmations of the most recent transaction included
}
,...
]
Examples:
> bitcoin-cli listreceivedbyaccount
> bitcoin-cli listreceivedbyaccount 6 true
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listreceivedbyaccount", "params": [6, true] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:53

help listreceivedbyaddress
20:32:53

listreceivedbyaddress ( minconf includeempty )
List balances by receiving address.
Arguments:
1. minconf (numeric, optional, default=1) The minimum number of confirmations before payments are included.
2. includeempty (numeric, optional, dafault=false) Whether to include addresses that haven't received any payments.
Result:
[
{
"address" : "receivingaddress", (string) The receiving address
"account" : "accountname", (string) The account of the receiving address. The default account is "".
"amount" : x.xxx, (numeric) The total amount in btc received by the address
"confirmations" : n (numeric) The number of confirmations of the most recent transaction included
}
,...
]
Examples:
> bitcoin-cli listreceivedbyaddress
> bitcoin-cli listreceivedbyaddress 6 true
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listreceivedbyaddress", "params": [6, true] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:55

help listsinceblock
20:32:55

listsinceblock ( "blockhash" target-confirmations )
Get all transactions in blocks since block [blockhash], or all transactions if omitted
Arguments:
1. "blockhash" (string, optional) The block hash to list transactions since
2. target-confirmations: (numeric, optional) The confirmations required, must be 1 or more
Result:
{
"transactions": [
"account":"accountname", (string) The account name associated with the transaction. Will be "" for the default account.
"address":"bitcoinaddress", (string) The bitcoin address of the transaction. Not present for move transactions (category = move).
"category":"send|receive", (string) The transaction category. 'send' has negative amounts, 'receive' has positive amounts.
"amount": x.xxx, (numeric) The amount in btc. This is negative for the 'send' category, and for the 'move' category for moves
outbound. It is positive for the 'receive' category, and for the 'move' category for inbound funds.
"fee": x.xxx, (numeric) The amount of the fee in btc. This is negative and only available for the 'send' category of transactions.
"confirmations": n, (numeric) The number of confirmations for the transaction. Available for 'send' and 'receive' category of transactions.
"blockhash": "hashvalue", (string) The block hash containing the transaction. Available for 'send' and 'receive' category of transactions.
"blockindex": n, (numeric) The block index containing the transaction. Available for 'send' and 'receive' category of transactions.
"blocktime": xxx, (numeric) The block time in seconds since epoch (1 Jan 1970 GMT).
"txid": "transactionid", (string) The transaction id. Available for 'send' and 'receive' category of transactions.
"time": xxx, (numeric) The transaction time in seconds since epoch (Jan 1 1970 GMT).
"timereceived": xxx, (numeric) The time received in seconds since epoch (Jan 1 1970 GMT). Available for 'send' and 'receive' category of transactions.
"comment": "...", (string) If a comment is associated with the transaction.
"to": "...", (string) If a comment to is associated with the transaction.
],
"lastblock": "lastblockhash" (string) The hash of the last block
}
Examples:
> bitcoin-cli listsinceblock
> bitcoin-cli listsinceblock "000000000000000bacf66f7497b7dc45ef753ee9a7d38571037cdb1a57f663ad" 6
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listsinceblock", "params": ["000000000000000bacf66f7497b7dc45ef753ee9a7d38571037cdb1a57f663ad", 6] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:58

help listtransactions
20:32:58

listtransactions ( "account" count from )
Returns up to 'count' most recent transactions skipping the first 'from' transactions for account 'account'.
Arguments:
1. "account" (string, optional) The account name. If not included, it will list all transactions for all accounts.
If "" is set, it will list transactions for the default account.
2. count (numeric, optional, default=10) The number of transactions to return
3. from (numeric, optional, default=0) The number of transactions to skip
Result:
[
{
"account":"accountname", (string) The account name associated with the transaction.
It will be "" for the default account.
"address":"bitcoinaddress", (string) The bitcoin address of the transaction. Not present for
move transactions (category = move).
"category":"send|receive|move", (string) The transaction category. 'move' is a local (off blockchain)
transaction between accounts, and not associated with an address,
transaction id or block. 'send' and 'receive' transactions are
associated with an address, transaction id and block details
"amount": x.xxx, (numeric) The amount in btc. This is negative for the 'send' category, and for the
'move' category for moves outbound. It is positive for the 'receive' category,
and for the 'move' category for inbound funds.
"fee": x.xxx, (numeric) The amount of the fee in btc. This is negative and only available for the
'send' category of transactions.
"confirmations": n, (numeric) The number of confirmations for the transaction. Available for 'send' and
'receive' category of transactions.
"blockhash": "hashvalue", (string) The block hash containing the transaction. Available for 'send' and 'receive'
category of transactions.
"blockindex": n, (numeric) The block index containing the transaction. Available for 'send' and 'receive'
category of transactions.
"txid": "transactionid", (string) The transaction id. Available for 'send' and 'receive' category of transactions.
"time": xxx, (numeric) The transaction time in seconds since epoch (midnight Jan 1 1970 GMT).
"timereceived": xxx, (numeric) The time received in seconds since epoch (midnight Jan 1 1970 GMT). Available
for 'send' and 'receive' category of transactions.
"comment": "...", (string) If a comment is associated with the transaction.
"otheraccount": "accountname", (string) For the 'move' category of transactions, the account the funds came
from (for receiving funds, positive amounts), or went to (for sending funds,
negative amounts).
}
]
Examples:
List the most recent 10 transactions in the systems
> bitcoin-cli listtransactions
List the most recent 10 transactions for the tabby account
> bitcoin-cli listtransactions "tabby"
List transactions 100 to 120 from the tabby account
> bitcoin-cli listtransactions "tabby" 20 100
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listtransactions", "params": ["tabby", 20, 100] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:01

help listunspent
20:33:01

listunspent ( minconf maxconf ["address",...] )
Returns array of unspent transaction outputs
with between minconf and maxconf (inclusive) confirmations.
Optionally filter to only include txouts paid to specified addresses.
Results are an array of Objects, each of which has:
{txid, vout, scriptPubKey, amount, confirmations}
Arguments:
1. minconf (numeric, optional, default=1) The minimum confirmationsi to filter
2. maxconf (numeric, optional, default=9999999) The maximum confirmations to filter
3. "addresses" (string) A json array of bitcoin addresses to filter
[
"address" (string) bitcoin address
,...
]
Result
[ (array of json object)
{
"txid" : "txid", (string) the transaction id
"vout" : n, (numeric) the vout value
"address" : "address", (string) the bitcoin address
"account" : "account", (string) The associated account, or "" for the default account
"scriptPubKey" : "key", (string) the script key
"amount" : x.xxx, (numeric) the transaction amount in btc
"confirmations" : n (numeric) The number of confirmations
}
,...
]
Examples
> bitcoin-cli listunspent
> bitcoin-cli listunspent 6 9999999 "[\"1PGFqEzfmQch1gKD3ra4k18PNj3tTUUSqg\",\"1LtvqCaApEdUGFkpKMM4MstjcaL4dKg8SP\"]"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listunspent", "params": [6, 9999999 "[\"1PGFqEzfmQch1gKD3ra4k18PNj3tTUUSqg\",\"1LtvqCaApEdUGFkpKMM4MstjcaL4dKg8SP\"]"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:04

help lockunspent
20:33:04

lockunspent unlock [{"txid":"txid","vout":n},...]
Updates list of temporarily unspendable outputs.
Temporarily lock (unlock=false) or unlock (unlock=true) specified transaction outputs.
A locked transaction output will not be chosen by automatic coin selection, when spending bitcoins.
Locks are stored in memory only. Nodes start with zero locked outputs, and the locked output list
is always cleared (by virtue of process exit) when a node stops or fails.
Also see the listunspent call
Arguments:
1. unlock (boolean, required) Whether to unlock (true) or lock (false) the specified transactions
2. "transactions" (string, required) A json array of objects. Each object the txid (string) vout (numeric)
[ (json array of json objects)
{
"txid":"id", (string) The transaction id
"vout": n (numeric) The output number
}
,...
]
Result:
true|false (boolean) Whether the command was successful or not
Examples:
List the unspent transactions
> bitcoin-cli listunspent
Lock an unspent transaction
> bitcoin-cli lockunspent false "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
List the locked transactions
> bitcoin-cli listlockunspent
Unlock the transaction again
> bitcoin-cli lockunspent true "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "lockunspent", "params": [false, "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:07

help move
20:33:07

move "fromaccount" "toaccount" amount ( minconf "comment" )
Move a specified amount from one account in your wallet to another.
Arguments:
1. "fromaccount" (string, required) The name of the account to move funds from. May be the default account using "".
2. "toaccount" (string, required) The name of the account to move funds to. May be the default account using "".
3. minconf (numeric, optional, default=1) Only use funds with at least this many confirmations.
4. "comment" (string, optional) An optional comment, stored in the wallet only.
Result:
true|false (boolean) true if successfull.
Examples:
Move 0.01 btc from the default account to the account named tabby
> bitcoin-cli move "" "tabby" 0.01
Move 0.01 btc timotei to akiko with a comment and funds have 6 confirmations
> bitcoin-cli move "timotei" "akiko" 0.01 6 "happy birthday!"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "move", "params": ["timotei", "akiko", 0.01, 6, "happy birthday!"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:10

help ping
20:33:10

ping
Requests that a ping be sent to all other nodes, to measure ping time.
Results provided in getpeerinfo, pingtime and pingwait fields are decimal seconds.
Ping command is handled in queue with all other commands, so it measures processing backlog, not just network ping.
Examples:
> bitcoin-cli ping
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "ping", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:12

help sendfrom
20:33:12

sendfrom "fromaccount" "tobitcoinaddress" amount ( minconf "comment" "comment-to" )
Sent an amount from an account to a bitcoin address.
The amount is a real and is rounded to the nearest 0.00000001.
Requires wallet passphrase to be set with walletpassphrase call.
Arguments:
1. "fromaccount" (string, required) The name of the account to send funds from. May be the default account using "".
2. "tobitcoinaddress" (string, required) The bitcoin address to send funds to.
3. amount (numeric, required) The amount in btc. (transaction fee is added on top).
4. minconf (numeric, optional, default=1) Only use funds with at least this many confirmations.
5. "comment" (string, optional) A comment used to store what the transaction is for.
This is not part of the transaction, just kept in your wallet.
6. "comment-to" (string, optional) An optional comment to store the name of the person or organization
to which you're sending the transaction. This is not part of the transaction,
it is just kept in your wallet.
Result:
"transactionid" (string) The transaction id.
Examples:
Send 0.01 btc from the default account to the address, must have at least 1 confirmation
> bitcoin-cli sendfrom "" "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.01
Send 0.01 from the tabby account to the given address, funds must have at least 6 confirmations
> bitcoin-cli sendfrom "tabby" "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.01 6 "donation" "seans outpost"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "sendfrom", "params": ["tabby", "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd", 0.01, 6, "donation", "seans outpost"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:15

help sendmany
20:33:15

sendmany "fromaccount" {"address":amount,...} ( minconf "comment" )
Send multiple times. Amounts are double-precision floating point numbers.
Requires wallet passphrase to be set with walletpassphrase call.
Arguments:
1. "fromaccount" (string, required) The account to send the funds from, can be "" for the default account
2. "amounts" (string, required) A json object with addresses and amounts
{
"address":amount (numeric) The bitcoin address is the key, the numeric amount in btc is the value
,...
}
3. minconf (numeric, optional, default=1) Only use the balance confirmed at least this many times.
4. "comment" (string, optional) A comment
Result:
"transactionid" (string) The transaction id for the send. Only 1 transaction is created regardless of
the number of addresses.
Examples:
Send two amounts to two different addresses:
> bitcoin-cli sendmany "tabby" "{\"1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ\":0.01,\"1353tsE8YMTA4EuV7dgUXGjNFf9KpVvKHz\":0.02}"
Send two amounts to two different addresses setting the confirmation and comment:
> bitcoin-cli sendmany "tabby" "{\"1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ\":0.01,\"1353tsE8YMTA4EuV7dgUXGjNFf9KpVvKHz\":0.02}" 6 "testing"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "sendmany", "params": ["tabby", "{\"1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ\":0.01,\"1353tsE8YMTA4EuV7dgUXGjNFf9KpVvKHz\":0.02}", 6, "testing"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:17

help sendrawtransaction
20:33:17

sendrawtransaction "hexstring" ( allowhighfees )
Submits raw transaction (serialized, hex-encoded) to local node and network.
Also see createrawtransaction and signrawtransaction calls.
Arguments:
1. "hexstring" (string, required) The hex string of the raw transaction)
2. allowhighfees (boolean, optional, default=false) Allow high fees
Result:
"hex" (string) The transaction hash in hex
Examples:
Create a transaction
> bitcoin-cli createrawtransaction "[{\"txid\" : \"mytxid\",\"vout\":0}]" "{\"myaddress\":0.01}"
Sign the transaction, and get back the hex
> bitcoin-cli signrawtransaction "myhex"
Send the transaction (signed hex)
> bitcoin-cli sendrawtransaction "signedhex"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "sendrawtransaction", "params": ["signedhex"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:19

help sendtoaddress
20:33:19

sendtoaddress "bitcoinaddress" amount ( "comment" "comment-to" )
Sent an amount to a given address. The amount is a real and is rounded to the nearest 0.00000001
Requires wallet passphrase to be set with walletpassphrase call.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to send to.
2. "amount" (numeric, required) The amount in btc to send. eg 0.1
3. "comment" (string, optional) A comment used to store what the transaction is for.
This is not part of the transaction, just kept in your wallet.
4. "comment-to" (string, optional) A comment to store the name of the person or organization
to which you're sending the transaction. This is not part of the
transaction, just kept in your wallet.
Result:
"transactionid" (string) The transaction id.
Examples:
> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1
> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1 "donation" "seans outpost"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "sendtoaddress", "params": ["1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd", 0.1, "donation", "seans outpost"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:22

help setaccount
20:33:22

setaccount "bitcoinaddress" "account"
Sets the account associated with the given address.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to be associated with an account.
2. "account" (string, required) The account to assign the address to.
Examples:
> bitcoin-cli setaccount "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" "tabby"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setaccount", "params": ["1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ", "tabby"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:24

help setgenerate
20:33:24

setgenerate generate ( genproclimit )
Set 'generate' true or false to turn generation on or off.
Generation is limited to 'genproclimit' processors, -1 is unlimited.
See the getgenerate call for the current setting.
Arguments:
1. generate (boolean, required) Set to true to turn on generation, off to turn off.
2. genproclimit (numeric, optional) Set the processor limit for when generation is on. Can be -1 for unlimited.
Note: in -regtest mode, genproclimit controls how many blocks are generated immediately.
Examples:
Set the generation on with a limit of one processor
> bitcoin-cli setgenerate true 1
Check the setting
> bitcoin-cli getgenerate
Turn off generation
> bitcoin-cli setgenerate false
Using json rpc
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "setgenerate", "params": [true, 1] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
settxfee amount
Set the transaction fee per kB.
Arguments:
1. amount (numeric, required) The transaction fee in BTC/kB rounded to the nearest 0.00000001
Result
true|false (boolean) Returns true if successful
Examples:
> bitcoin-cli settxfee 0.00001
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "settxfee", "params": [0.00001] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:29

help signmessage
20:33:29

signmessage "bitcoinaddress" "message"
Sign a message with the private key of an address
Requires wallet passphrase to be set with walletpassphrase call.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to use for the private key.
2. "message" (string, required) The message to create a signature of.
Result:
"signature" (string) The signature of the message encoded in base 64
Examples:
Unlock the wallet for 30 seconds
> bitcoin-cli walletpassphrase "mypassphrase" 30
Create the signature
> bitcoin-cli signmessage "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" "my message"
Verify the signature
> bitcoin-cli verifymessage "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" "signature" "my message"
As json rpc
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "signmessage", "params": ["1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ", "my message"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:32

help signrawtransaction
20:33:32

signrawtransaction "hexstring" ( [{"txid":"id","vout":n,"scriptPubKey":"hex","redeemScript":"hex"},...] ["privatekey1",...] sighashtype )
Sign inputs for raw transaction (serialized, hex-encoded).
The second optional argument (may be null) is an array of previous transaction outputs that
this transaction depends on but may not yet be in the block chain.
The third optional argument (may be null) is an array of base58-encoded private
keys that, if given, will be the only keys used to sign the transaction.
Requires wallet passphrase to be set with walletpassphrase call.
Arguments:
1. "hexstring" (string, required) The transaction hex string
2. "prevtxs" (string, optional) An json array of previous dependent transaction outputs
[ (json array of json objects, or 'null' if none provided)
{
"txid":"id", (string, required) The transaction id
"vout":n, (numeric, required) The output number
"scriptPubKey": "hex", (string, required) script key
"redeemScript": "hex" (string, required) redeem script
}
,...
]
3. "privatekeys" (string, optional) A json array of base58-encoded private keys for signing
[ (json array of strings, or 'null' if none provided)
"privatekey" (string) private key in base58-encoding
,...
]
4. "sighashtype" (string, optional, default=ALL) The signature hash type. Must be one of
"ALL"
"NONE"
"SINGLE"
"ALL|ANYONECANPAY"
"NONE|ANYONECANPAY"
"SINGLE|ANYONECANPAY"
Result:
{
"hex": "value", (string) The raw transaction with signature(s) (hex-encoded string)
"complete": n (numeric) if transaction has a complete set of signature (0 if not)
}
Examples:
> bitcoin-cli signrawtransaction "myhex"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "signrawtransaction", "params": ["myhex"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:35

help stop
20:33:35

stop
Stop Bitcoin server.
20:33:37

help submitblock
20:33:37

submitblock "hexdata" ( "jsonparametersobject" )
Attempts to submit new block to network.
The 'jsonparametersobject' parameter is currently ignored.
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
Arguments
1. "hexdata" (string, required) the hex-encoded block data to submit
2. "jsonparametersobject" (string, optional) object of optional parameters
{
"workid" : "id" (string, optional) if the server provided a workid, it MUST be included with submissions
}
Result:
Examples:
> bitcoin-cli submitblock "mydata"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "submitblock", "params": ["mydata"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:39

help validateaddress
20:33:39

validateaddress "bitcoinaddress"
Return information about the given bitcoin address.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to validate
Result:
{
"isvalid" : true|false, (boolean) If the address is valid or not. If not, this is the only property returned.
"address" : "bitcoinaddress", (string) The bitcoin address validated
"ismine" : true|false, (boolean) If the address is yours or not
"isscript" : true|false, (boolean) If the key is a script
"pubkey" : "publickeyhex", (string) The hex value of the raw public key
"iscompressed" : true|false, (boolean) If the address is compressed
"account" : "account" (string) The account associated with the address, "" is the default account
}
Examples:
> bitcoin-cli validateaddress "1PSSGeFHDnKNxiEyFrD1wcEaHr9hrQDDWc"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "validateaddress", "params": ["1PSSGeFHDnKNxiEyFrD1wcEaHr9hrQDDWc"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:42

help verifychain
20:33:42

verifychain ( checklevel numblocks )
Verifies blockchain database.
Arguments:
1. checklevel (numeric, optional, 0-4, default=3) How thorough the block verification is.
2. numblocks (numeric, optional, default=288, 0=all) The number of blocks to check.
Result:
true|false (boolean) Verified or not
Examples:
> bitcoin-cli verifychain
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "verifychain", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:44

help verifymessage
20:33:44

verifymessage "bitcoinaddress" "signature" "message"
Verify a signed message
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address to use for the signature.
2. "signature" (string, required) The signature provided by the signer in base 64 encoding (see signmessage).
3. "message" (string, required) The message that was signed.
Result:
true|false (boolean) If the signature is verified or not.
Examples:
Unlock the wallet for 30 seconds
> bitcoin-cli walletpassphrase "mypassphrase" 30
Create the signature
> bitcoin-cli signmessage "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" "my message"
Verify the signature
> bitcoin-cli verifymessage "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" "signature" "my message"
As json rpc
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "verifymessage", "params": ["1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ", "signature", "my message"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:48

help walletlock
20:33:48

walletlock
Removes the wallet encryption key from memory, locking the wallet.
After calling this method, you will need to call walletpassphrase again
before being able to call any methods which require the wallet to be unlocked.
Examples:
Set the passphrase for 2 minutes to perform a transaction
> bitcoin-cli walletpassphrase "my pass phrase" 120
Perform a send (requires passphrase set)
> bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 1.0
Clear the passphrase since we are done before 2 minutes is up
> bitcoin-cli walletlock
As json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletlock", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:50

help walletpassphrase
20:33:50

walletpassphrase "passphrase" timeout
Stores the wallet decryption key in memory for 'timeout' seconds.
This is needed prior to performing transactions related to private keys such as sending bitcoins
Arguments:
1. "passphrase" (string, required) The wallet passphrase
2. timeout (numeric, required) The time to keep the decryption key in seconds.
Note:
Issuing the walletpassphrase command while the wallet is already unlocked will set a new unlock
time that overrides the old one.
Examples:
unlock the wallet for 60 seconds
> bitcoin-cli walletpassphrase "my pass phrase" 60
Lock the wallet again (before 60 seconds)
> bitcoin-cli walletlock
As json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["my pass phrase", 60] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:53

help walletpassphrasechange
20:33:53

walletpassphrasechange "oldpassphrase" "newpassphrase"
Changes the wallet passphrase from 'oldpassphrase' to 'newpassphrase'.
Arguments:
1. "oldpassphrase" (string) The current passphrase
2. "newpassphrase" (string) The new passphrase
Examples:
> bitcoin-cli walletpassphrasechange "old one" "new one"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrasechange", "params": ["old one", "new one"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:33:55
stop |
|
|
|
I posted Bitcoin Core 0.9.2.1 RPC Calls Extended List over at Bitcoin SE and linked to the full copy/paste at PastebinThere's a few rough formatting issues but I found this hard to find so perhaps it'll help people like myself. help addmultisigaddress
help addnode
help backupwallet
help createmultisig
help createrawtransaction
help decoderawtransaction
help decodescript
help dumpprivkey
help dumpwallet
help getaccount
help getaccountaddress
help getaddednodeinfo
help getaddressesbyaccount
help getbalance
help getbestblockhash
help getblock
help getblockchaininfo
help getblockcount
help getblockhash
help getblocktemplate
help getconnectioncount
help getdifficulty
help getgenerate
help gethashespersec
help getinfo
help getmininginfo
help getnettotals
help getnetworkhashps
help getnetworkinfo
help getnewaddress
help getpeerinfo
help getrawchangeaddress
help getrawmempool
help getrawtransaction
help getreceivedbyaccount
help getreceivedbyaddress
help gettransaction
help gettxout
help gettxoutsetinfo
help getunconfirmedbalance
help getwalletinfo
help getwork
help help
help importprivkey
help importwallet
help keypoolrefill
help listaccounts
help listaddressgroupings
help listlockunspent
help listreceivedbyaccount
help listreceivedbyaddress
help listsinceblock
help listtransactions
help listunspent
help lockunspent
help move
help ping
help sendfrom
help sendmany
help sendrawtransaction
help sendtoaddress
help setaccount
help setgenerate
help settxfee
help signmessage
help signrawtransaction
help stop
help submitblock
help validateaddress
help verifychain
help verifymessage
help walletlock
help walletpassphrase
help walletpassphrasechange
addmultisigaddress nrequired ["key",...] ( "account" )
Add a nrequired-to-sign multisignature address to the wallet.
Each key is a Bitcoin address or hex-encoded public key.
If 'account' is specified, assign address to that account.
Arguments:
1. nrequired (numeric, required) The number of required signatures out of the n keys or addresses.
2. "keysobject" (string, required) A json array of bitcoin addresses or hex-encoded public keys
[
"address" (string) bitcoin address or hex-encoded public key
...,
]
3. "account" (string, optional) An account to assign the addresses to.
Result:
"bitcoinaddress" (string) A bitcoin address associated with the keys.
Examples:
Add a multisig address from 2 addresses
> bitcoin-cli addmultisigaddress 2 "[\"16sSauSf5pF2UkUwvKGq4qjNRzBZYqgEL5\",\"171sgjn4YtPu27adkKGrdDwzRTxnRkBfKV\"]"
As json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "addmultisigaddress", "params": [2, "[\"16sSauSf5pF2UkUwvKGq4qjNRzBZYqgEL5\",\"171sgjn4YtPu27adkKGrdDwzRTxnRkBfKV\"]"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
addnode "node" "add|remove|onetry"
Attempts add or remove a node from the addnode list.
Or try a connection to a node once.
Arguments:
1. "node" (string, required) The node (see getpeerinfo for nodes)
2. "command" (string, required) 'add' to add a node to the list, 'remove' to remove a node from the list, 'onetry' to try a connection to the node once
Examples:
> bitcoin-cli addnode "192.168.0.6:8333" "onetry"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "addnode", "params": ["192.168.0.6:8333", "onetry"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
backupwallet "destination"
Safely copies wallet.dat to destination, which can be a directory or a path with filename.
Arguments:
1. "destination" (string) The destination directory or file
Examples:
> bitcoin-cli backupwallet "backup.dat"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "backupwallet", "params": ["backup.dat"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
createmultisig nrequired ["key",...]
Creates a multi-signature address with n signature of m keys required.
It returns a json object with the address and redeemScript.
Arguments:
1. nrequired (numeric, required) The number of required signatures out of the n keys or addresses.
2. "keys" (string, required) A json array of keys which are bitcoin addresses or hex-encoded public keys
[
"key" (string) bitcoin address or hex-encoded public key
,...
]
Result:
{
"address":"multisigaddress", (string) The value of the new multisig address.
"redeemScript":"script" (string) The string value of the hex-encoded redemption script.
}
Examples:
Create a multisig address from 2 addresses
> bitcoin-cli createmultisig 2 "[\"16sSauSf5pF2UkUwvKGq4qjNRzBZYqgEL5\",\"171sgjn4YtPu27adkKGrdDwzRTxnRkBfKV\"]"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "createmultisig", "params": [2, "[\"16sSauSf5pF2UkUwvKGq4qjNRzBZYqgEL5\",\"171sgjn4YtPu27adkKGrdDwzRTxnRkBfKV\"]"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
createrawtransaction [{"txid":"id","vout":n},...] {"address":amount,...}
Create a transaction spending the given inputs and sending to the given addresses.
Returns hex-encoded raw transaction.
Note that the transaction's inputs are not signed, and
it is not stored in the wallet or transmitted to the network.
Arguments:
1. "transactions" (string, required) A json array of json objects
[
{
"txid":"id", (string, required) The transaction id
"vout":n (numeric, required) The output number
}
,...
]
2. "addresses" (string, required) a json object with addresses as keys and amounts as values
{
"address": x.xxx (numeric, required) The key is the bitcoin address, the value is the btc amount
,...
}
Result:
"transaction" (string) hex string of the transaction
Examples
> bitcoin-cli createrawtransaction "[{\"txid\":\"myid\",\"vout\":0}]" "{\"address\":0.01}"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "createrawtransaction", "params": ["[{\"txid\":\"myid\",\"vout\":0}]", "{\"address\":0.01}"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
decoderawtransaction "hexstring"
Return a JSON object representing the serialized, hex-encoded transaction.
Arguments:
1. "hex" (string, required) The transaction hex string
Result:
{
"txid" : "id", (string) The transaction id
"version" : n, (numeric) The version
"locktime" : ttt, (numeric) The lock time
"vin" : [ (array of json objects)
{
"txid": "id", (string) The transaction id
"vout": n, (numeric) The output number
"scriptSig": { (json object) The script
"asm": "asm", (string) asm
"hex": "hex" (string) hex
},
"sequence": n (numeric) The script sequence number
}
,...
],
"vout" : [ (array of json objects)
{
"value" : x.xxx, (numeric) The value in btc
"n" : n, (numeric) index
"scriptPubKey" : { (json object)
"asm" : "asm", (string) the asm
"hex" : "hex", (string) the hex
"reqSigs" : n, (numeric) The required sigs
"type" : "pubkeyhash", (string) The type, eg 'pubkeyhash'
"addresses" : [ (json array of string)
"12tvKAXCxZjSmdNbao16dKXC8tRWfcF5oc" (string) bitcoin address
,...
]
}
}
,...
],
}
Examples:
> bitcoin-cli decoderawtransaction "hexstring"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "decoderawtransaction", "params": ["hexstring"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
decodescript "hex"
Decode a hex-encoded script.
Arguments:
1. "hex" (string) the hex encoded script
Result:
{
"asm":"asm", (string) Script public key
"hex":"hex", (string) hex encoded public key
"type":"type", (string) The output type
"reqSigs": n, (numeric) The required signatures
"addresses": [ (json array of string)
"address" (string) bitcoin address
,...
],
"p2sh","address" (string) script address
}
Examples:
> bitcoin-cli decodescript "hexstring"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "decodescript", "params": ["hexstring"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
dumpprivkey "bitcoinaddress"
Reveals the private key corresponding to 'bitcoinaddress'.
Then the importprivkey can be used with this output
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address for the private key
Result:
"key" (string) The private key
Examples:
> bitcoin-cli dumpprivkey "myaddress"
> bitcoin-cli importprivkey "mykey"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "dumpprivkey", "params": ["myaddress"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
dumpwallet "filename"
Dumps all wallet keys in a human-readable format.
Arguments:
1. "filename" (string, required) The filename
Examples:
> bitcoin-cli dumpwallet "test"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "dumpwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
getaccount "bitcoinaddress"
Returns the account associated with the given address.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address for account lookup.
Result:
"accountname" (string) the account address
Examples:
> bitcoin-cli getaccount "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getaccount", "params": ["1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
getaccountaddress "account"
Returns the current Bitcoin address for receiving payments to this account.
Arguments:
1. "account" (string, required) The account name for the address. It can also be set to the empty string "" to represent the default account. The account does not need to exist, it will be created and a new address created if there is no account by the given name.
Result:
"bitcoinaddress" (string) The account bitcoin address
Examples:
> bitcoin-cli getaccountaddress
> bitcoin-cli getaccountaddress ""
> bitcoin-cli getaccountaddress "myaccount"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getaccountaddress", "params": ["myaccount"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
getaddednodeinfo dns ( "node" )
Returns information about the given added node, or all added nodes
(note that onetry addnodes are not listed here)
If dns is false, only a list of added nodes will be provided,
otherwise connected information will also be available.
Arguments:
1. dns (boolean, required) If false, only a list of added nodes will be provided, otherwise connected information will also be available.
2. "node" (string, optional) If provided, return information about this specific node, otherwise all nodes are returned.
Result:
[
{
"addednode" : "192.168.0.201", (string) The node ip address
"connected" : true|false, (boolean) If connected
"addresses" : [
{
"address" : "192.168.0.201:8333", (string) The bitcoin server host and port
"connected" : "outbound" (string) connection, inbound or outbound
}
,...
]
}
,...
]
Examples:
> bitcoin-cli getaddednodeinfo true
> bitcoin-cli getaddednodeinfo true "192.168.0.201"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getaddednodeinfo", "params": [true, "192.168.0.201"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:27:36

help getaddressesbyaccount
20:27:36

getaddressesbyaccount "account"
Returns the list of addresses for the given account.
Arguments:
1. "account" (string, required) The account name.
Result:
[ (json array of string)
"bitcoinaddress" (string) a bitcoin address associated with the given account
,...
]
Examples:
> bitcoin-cli getaddressesbyaccount "tabby"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getaddressesbyaccount", "params": ["tabby"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:27:40

help getbalance
20:27:40

getbalance ( "account" minconf )
If account is not specified, returns the server's total available balance.
If account is specified, returns the balance in the account.
Note that the account "" is not the same as leaving the parameter out.
The server total may be different to the balance in the default "" account.
Arguments:
1. "account" (string, optional) The selected account, or "*" for entire wallet. It may be the default account using "".
2. minconf (numeric, optional, default=1) Only include transactions confirmed at least this many times.
Result:
amount (numeric) The total amount in btc received for this account.
Examples:
The total amount in the server across all accounts
> bitcoin-cli getbalance
The total amount in the server across all accounts, with at least 5 confirmations
> bitcoin-cli getbalance "*" 6
The total amount in the default account with at least 1 confirmation
> bitcoin-cli getbalance ""
The total amount in the account named tabby with at least 6 confirmations
> bitcoin-cli getbalance "tabby" 6
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getbalance", "params": ["tabby", 6] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:27:44

help getbestblockhash
20:27:44

getbestblockhash
Returns the hash of the best (tip) block in the longest block chain.
Result
"hex" (string) the block hash hex encoded
Examples
> bitcoin-cli getbestblockhash
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getbestblockhash", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:27:49

help getblock
20:27:49

getblock "hash" ( verbose )
If verbose is false, returns a string that is serialized, hex-encoded data for block 'hash'.
If verbose is true, returns an Object with information about block <hash>.
Arguments:
1. "hash" (string, required) The block hash
2. verbose (boolean, optional, default=true) true for a json object, false for the hex encoded data
Result (for verbose = true):
{
"hash" : "hash", (string) the block hash (same as provided)
"confirmations" : n, (numeric) The number of confirmations
"size" : n, (numeric) The block size
"height" : n, (numeric) The block height or index
"version" : n, (numeric) The block version
"merkleroot" : "xxxx", (string) The merkle root
"tx" : [ (array of string) The transaction ids
"transactionid" (string) The transaction id
,...
],
"time" : ttt, (numeric) The block time in seconds since epoch (Jan 1 1970 GMT)
"nonce" : n, (numeric) The nonce
"bits" : "1d00ffff", (string) The bits
"difficulty" : x.xxx, (numeric) The difficulty
"previousblockhash" : "hash", (string) The hash of the previous block
"nextblockhash" : "hash" (string) The hash of the next block
}
Result (for verbose=false):
"data" (string) A string that is serialized, hex-encoded data for block 'hash'.
Examples:
> bitcoin-cli getblock "00000000c937983704a73af28acdec37b049d214adbda81d7e2a3dd146f6ed09"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblock", "params": ["00000000c937983704a73af28acdec37b049d214adbda81d7e2a3dd146f6ed09"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:27:54

help getblockchaininfo
20:27:54

getblockchaininfo
Returns an object containing various state info regarding block chain processing.
Result:
{
"chain": "xxxx", (string) current chain (main, testnet3, regtest)
"blocks": xxxxxx, (numeric) the current number of blocks processed in the server
"bestblockhash": "...", (string) the hash of the currently best block
"difficulty": xxxxxx, (numeric) the current difficulty
"verificationprogress": xxxx, (numeric) estimate of verification progress [0..1]
"chainwork": "xxxx" (string) total amount of work in active chain, in hexadecimal
}
Examples:
> bitcoin-cli getblockchaininfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockchaininfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:00

help getblockcount
20:28:00

getblockcount
Returns the number of blocks in the longest block chain.
Result:
n (numeric) The current block count
Examples:
> bitcoin-cli getblockcount
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockcount", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:05

help getblockhash
20:28:05

getblockhash index
Returns hash of block in best-block-chain at index provided.
Arguments:
1. index (numeric, required) The block index
Result:
"hash" (string) The block hash
Examples:
> bitcoin-cli getblockhash 1000
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockhash", "params": [1000] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:10

help getblocktemplate
20:28:10

getblocktemplate ( "jsonrequestobject" )
If the request parameters include a 'mode' key, that is used to explicitly select between the default 'template' request or a 'proposal'.
It returns data needed to construct a block to work on.
See https://en.bitcoin.it/wiki/BIP_0022 for full specification.
Arguments:
1. "jsonrequestobject" (string, optional) A json object in the following spec
{
"mode":"template" (string, optional) This must be set to "template" or omitted
"capabilities":[ (array, optional) A list of strings
"support" (string) client side supported feature, 'longpoll', 'coinbasetxn', 'coinbasevalue', 'proposal', 'serverlist', 'workid'
,...
]
}
Result:
{
"version" : n, (numeric) The block version
"previousblockhash" : "xxxx", (string) The hash of current highest block
"transactions" : [ (array) contents of non-coinbase transactions that should be included in the next block
{
"data" : "xxxx", (string) transaction data encoded in hexadecimal (byte-for-byte)
"hash" : "xxxx", (string) hash/id encoded in little-endian hexadecimal
"depends" : [ (array) array of numbers
n (numeric) transactions before this one (by 1-based index in 'transactions' list) that must be present in the final block if this one is
,...
],
"fee": n, (numeric) difference in value between transaction inputs and outputs (in Satoshis); for coinbase transactions, this is a negative Number of the total collected block fees (ie, not including the block subsidy); if key is not present, fee is unknown and clients MUST NOT assume there isn't one
"sigops" : n, (numeric) total number of SigOps, as counted for purposes of block limits; if key is not present, sigop count is unknown and clients MUST NOT assume there aren't any
"required" : true|false (boolean) if provided and true, this transaction must be in the final block
}
,...
],
"coinbaseaux" : { (json object) data that should be included in the coinbase's scriptSig content
"flags" : "flags" (string)
},
"coinbasevalue" : n, (numeric) maximum allowable input to coinbase transaction, including the generation award and transaction fees (in Satoshis)
"coinbasetxn" : { ... }, (json object) information for coinbase transaction
"target" : "xxxx", (string) The hash target
"mintime" : xxx, (numeric) The minimum timestamp appropriate for next block time in seconds since epoch (Jan 1 1970 GMT)
"mutable" : [ (array of string) list of ways the block template may be changed
"value" (string) A way the block template may be changed, e.g. 'time', 'transactions', 'prevblock'
,...
],
"noncerange" : "00000000ffffffff", (string) A range of valid nonces
"sigoplimit" : n, (numeric) limit of sigops in blocks
"sizelimit" : n, (numeric) limit of block size
"curtime" : ttt, (numeric) current timestamp in seconds since epoch (Jan 1 1970 GMT)
"bits" : "xxx", (string) compressed target of next block
"height" : n (numeric) The height of the next block
}
Examples:
> bitcoin-cli getblocktemplate
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblocktemplate", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:13

help getconnectioncount
20:28:13

getconnectioncount
Returns the number of connections to other nodes.
bResult:
n (numeric) The connection count
Examples:
> bitcoin-cli getconnectioncount
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getconnectioncount", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:26

help getdifficulty
20:28:26

getdifficulty
Returns the proof-of-work difficulty as a multiple of the minimum difficulty.
Result:
n.nnn (numeric) the proof-of-work difficulty as a multiple of the minimum difficulty.
Examples:
> bitcoin-cli getdifficulty
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getdifficulty", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:31

help getgenerate
20:28:31

getgenerate
Return if the server is set to generate coins or not. The default is false.
It is set with the command line argument -gen (or bitcoin.conf setting gen)
It can also be set with the setgenerate call.
Result
true|false (boolean) If the server is set to generate coins or not
Examples:
> bitcoin-cli getgenerate
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getgenerate", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:28:59

help gethashespersec
20:28:59

gethashespersec
Returns a recent hashes per second performance measurement while generating.
See the getgenerate and setgenerate calls to turn generation on and off.
Result:
n (numeric) The recent hashes per second when generation is on (will return 0 if generation is off)
Examples:
> bitcoin-cli gethashespersec
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "gethashespersec", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:02

help getinfo
20:29:03

getinfo
Returns an object containing various state info.
Result:
{
"version": xxxxx, (numeric) the server version
"protocolversion": xxxxx, (numeric) the protocol version
"walletversion": xxxxx, (numeric) the wallet version
"balance": xxxxxxx, (numeric) the total bitcoin balance of the wallet
"blocks": xxxxxx, (numeric) the current number of blocks processed in the server
"timeoffset": xxxxx, (numeric) the time offset
"connections": xxxxx, (numeric) the number of connections
"proxy": "host:port", (string, optional) the proxy used by the server
"difficulty": xxxxxx, (numeric) the current difficulty
"testnet": true|false, (boolean) if the server is using testnet or not
"keypoololdest": xxxxxx, (numeric) the timestamp (seconds since GMT epoch) of the oldest pre-generated key in the key pool
"keypoolsize": xxxx, (numeric) how many new keys are pre-generated
"unlocked_until": ttt, (numeric) the timestamp in seconds since epoch (midnight Jan 1 1970 GMT) that the wallet is unlocked for transfers, or 0 if the wallet is locked
"paytxfee": x.xxxx, (numeric) the transaction fee set in btc/kb
"relayfee": x.xxxx, (numeric) minimum relay fee for non-free transactions in btc/kb
"errors": "..." (string) any error messages
}
Examples:
> bitcoin-cli getinfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:06

help getmininginfo
20:29:06

getmininginfo
Returns a json object containing mining-related information.
Result:
{
"blocks": nnn, (numeric) The current block
"currentblocksize": nnn, (numeric) The last block size
"currentblocktx": nnn, (numeric) The last block transaction
"difficulty": xxx.xxxxx (numeric) The current difficulty
"errors": "..." (string) Current errors
"generate": true|false (boolean) If the generation is on or off (see getgenerate or setgenerate calls)
"genproclimit": n (numeric) The processor limit for generation. -1 if no generation. (see getgenerate or setgenerate calls)
"hashespersec": n (numeric) The hashes per second of the generation, or 0 if no generation.
"pooledtx": n (numeric) The size of the mem pool
"testnet": true|false (boolean) If using testnet or not
}
Examples:
> bitcoin-cli getmininginfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getmininginfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:09

help getnettotals
20:29:09

getnettotals
Returns information about network traffic, including bytes in, bytes out,
and current time.
Result:
{
"totalbytesrecv": n, (numeric) Total bytes received
"totalbytessent": n, (numeric) Total bytes sent
"timemillis": t (numeric) Total cpu time
}
Examples:
> bitcoin-cli getnettotals
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnettotals", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:12

help getnetworkhashps
20:29:12

getnetworkhashps ( blocks height )
Returns the estimated network hashes per second based on the last n blocks.
Pass in [blocks] to override # of blocks, -1 specifies since last difficulty change.
Pass in [height] to estimate the network speed at the time when a certain block was found.
Arguments:
1. blocks (numeric, optional, default=120) The number of blocks, or -1 for blocks since last difficulty change.
2. height (numeric, optional, default=-1) To estimate at the time of the given height.
Result:
x (numeric) Hashes per second estimated
Examples:
> bitcoin-cli getnetworkhashps
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnetworkhashps", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:16

help getnetworkinfo
20:29:16

getnetworkinfo
Returns an object containing various state info regarding P2P networking.
Result:
{
"version": xxxxx, (numeric) the server version
"protocolversion": xxxxx, (numeric) the protocol version
"timeoffset": xxxxx, (numeric) the time offset
"connections": xxxxx, (numeric) the number of connections
"proxy": "host:port", (string, optional) the proxy used by the server
"relayfee": x.xxxx, (numeric) minimum relay fee for non-free transactions in btc/kb
"localaddresses": [, (array) list of local addresses
"address": "xxxx", (string) network address
"port": xxx, (numeric) network port
"score": xxx (numeric) relative score
]
}
Examples:
> bitcoin-cli getnetworkinfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnetworkinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:19

help getnewaddress
20:29:19

getnewaddress ( "account" )
Returns a new Bitcoin address for receiving payments.
If 'account' is specified (recommended), it is added to the address book
so payments received with the address will be credited to 'account'.
Arguments:
1. "account" (string, optional) The account name for the address to be linked to. if not provided, the default account "" is used. It can also be set to the empty string "" to represent the default account. The account does not need to exist, it will be created if there is no account by the given name.
Result:
"bitcoinaddress" (string) The new bitcoin address
Examples:
> bitcoin-cli getnewaddress
> bitcoin-cli getnewaddress ""
> bitcoin-cli getnewaddress "myaccount"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getnewaddress", "params": ["myaccount"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:23

help getpeerinfo
20:29:23

getpeerinfo
Returns data about each connected network node as a json array of objects.
bResult:
[
{
"addr":"host:port", (string) The ip address and port of the peer
"addrlocal":"ip:port", (string) local address
"services":"00000001", (string) The services
"lastsend": ttt, (numeric) The time in seconds since epoch (Jan 1 1970 GMT) of the last send
"lastrecv": ttt, (numeric) The time in seconds since epoch (Jan 1 1970 GMT) of the last receive
"bytessent": n, (numeric) The total bytes sent
"bytesrecv": n, (numeric) The total bytes received
"conntime": ttt, (numeric) The connection time in seconds since epoch (Jan 1 1970 GMT)
"pingtime": n, (numeric) ping time
"pingwait": n, (numeric) ping wait
"version": v, (numeric) The peer version, such as 7001
"subver": "/Satoshi:0.8.5/", (string) The string version
"inbound": true|false, (boolean) Inbound (true) or Outbound (false)
"startingheight": n, (numeric) The starting height (block) of the peer
"banscore": n, (numeric) The ban score (stats.nMisbehavior)
"syncnode" : true|false (booleamn) if sync node
}
,...
}
Examples:
> bitcoin-cli getpeerinfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getpeerinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:28

help getrawchangeaddress
20:29:28

getrawchangeaddress
Returns a new Bitcoin address, for receiving change.
This is for use with raw transactions, NOT normal use.
Result:
"address" (string) The address
Examples:
> bitcoin-cli getrawchangeaddress
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getrawchangeaddress", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:40

help getrawmempool
20:29:40

getrawmempool ( verbose )
Returns all transaction ids in memory pool as a json array of string transaction ids.
Arguments:
1. verbose (boolean, optional, default=false) true for a json object, false for array of transaction ids
Result: (for verbose = false):
[ (json array of string)
"transactionid" (string) The transaction id
,...
]
Result: (for verbose = true):
{ (json object)
"transactionid" : { (json object)
"size" : n, (numeric) transaction size in bytes
"fee" : n, (numeric) transaction fee in bitcoins
"time" : n, (numeric) local time transaction entered pool in seconds since 1 Jan 1970 GMT
"height" : n, (numeric) block height when transaction entered pool
"startingpriority" : n, (numeric) priority when transaction entered pool
"currentpriority" : n, (numeric) transaction priority now
"depends" : [ (array) unconfirmed transactions used as inputs for this transaction
"transactionid", (string) parent transaction id
... ]
}, ...
]
Examples
> bitcoin-cli getrawmempool true
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getrawmempool", "params": [true] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:44

help getrawtransaction
20:29:44

getrawtransaction "txid" ( verbose )
Return the raw transaction data.
If verbose=0, returns a string that is serialized, hex-encoded data for 'txid'.
If verbose is non-zero, returns an Object with information about 'txid'.
Arguments:
1. "txid" (string, required) The transaction id
2. verbose (numeric, optional, default=0) If 0, return a string, other return a json object
Result (if verbose is not set or set to 0):
"data" (string) The serialized, hex-encoded data for 'txid'
Result (if verbose > 0):
{
"hex" : "data", (string) The serialized, hex-encoded data for 'txid'
"txid" : "id", (string) The transaction id (same as provided)
"version" : n, (numeric) The version
"locktime" : ttt, (numeric) The lock time
"vin" : [ (array of json objects)
{
"txid": "id", (string) The transaction id
"vout": n, (numeric)
"scriptSig": { (json object) The script
"asm": "asm", (string) asm
"hex": "hex" (string) hex
},
"sequence": n (numeric) The script sequence number
}
,...
],
"vout" : [ (array of json objects)
{
"value" : x.xxx, (numeric) The value in btc
"n" : n, (numeric) index
"scriptPubKey" : { (json object)
"asm" : "asm", (string) the asm
"hex" : "hex", (string) the hex
"reqSigs" : n, (numeric) The required sigs
"type" : "pubkeyhash", (string) The type, eg 'pubkeyhash'
"addresses" : [ (json array of string)
"bitcoinaddress" (string) bitcoin address
,...
]
}
}
,...
],
"blockhash" : "hash", (string) the block hash
"confirmations" : n, (numeric) The confirmations
"time" : ttt, (numeric) The transaction time in seconds since epoch (Jan 1 1970 GMT)
"blocktime" : ttt (numeric) The block time in seconds since epoch (Jan 1 1970 GMT)
}
Examples:
> bitcoin-cli getrawtransaction "mytxid"
> bitcoin-cli getrawtransaction "mytxid" 1
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getrawtransaction", "params": ["mytxid", 1] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:47

help getreceivedbyaccount
20:29:47

getreceivedbyaccount "account" ( minconf )
Returns the total amount received by addresses with <account> in transactions with at least [minconf] confirmations.
Arguments:
1. "account" (string, required) The selected account, may be the default account using "".
2. minconf (numeric, optional, default=1) Only include transactions confirmed at least this many times.
Result:
amount (numeric) The total amount in btc received for this account.
Examples:
Amount received by the default account with at least 1 confirmation
> bitcoin-cli getreceivedbyaccount ""
Amount received at the tabby account including unconfirmed amounts with zero confirmations
> bitcoin-cli getreceivedbyaccount "tabby" 0
The amount with at least 6 confirmation, very safe
> bitcoin-cli getreceivedbyaccount "tabby" 6
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getreceivedbyaccount", "params": ["tabby", 6] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:50

help getreceivedbyaddress
20:29:50

getreceivedbyaddress "bitcoinaddress" ( minconf )
Returns the total amount received by the given bitcoinaddress in transactions with at least minconf confirmations.
Arguments:
1. "bitcoinaddress" (string, required) The bitcoin address for transactions.
2. minconf (numeric, optional, default=1) Only include transactions confirmed at least this many times.
Result:
amount (numeric) The total amount in btc received at this address.
Examples:
The amount from transactions with at least 1 confirmation
> bitcoin-cli getreceivedbyaddress "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ"
The amount including unconfirmed transactions, zero confirmations
> bitcoin-cli getreceivedbyaddress "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" 0
The amount with at least 6 confirmation, very safe
> bitcoin-cli getreceivedbyaddress "1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ" 6
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getreceivedbyaddress", "params": ["1D1ZrZNe3JUo7ZycKEYQQiQAWd9y54F4XZ", 6] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:53

help gettransaction
20:29:53

gettransaction "txid"
Get detailed information about in-wallet transaction <txid>
Arguments:
1. "txid" (string, required) The transaction id
Result:
{
"amount" : x.xxx, (numeric) The transaction amount in btc
"confirmations" : n, (numeric) The number of confirmations
"blockhash" : "hash", (string) The block hash
"blockindex" : xx, (numeric) The block index
"blocktime" : ttt, (numeric) The time in seconds since epoch (1 Jan 1970 GMT)
"txid" : "transactionid", (string) The transaction id.
"time" : ttt, (numeric) The transaction time in seconds since epoch (1 Jan 1970 GMT)
"timereceived" : ttt, (numeric) The time received in seconds since epoch (1 Jan 1970 GMT)
"details" : [
{
"account" : "accountname", (string) The account name involved in the transaction, can be "" for the default account.
"address" : "bitcoinaddress", (string) The bitcoin address involved in the transaction
"category" : "send|receive", (string) The category, either 'send' or 'receive'
"amount" : x.xxx (numeric) The amount in btc
}
,...
],
"hex" : "data" (string) Raw data for transaction
}
bExamples
> bitcoin-cli gettransaction "1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "gettransaction", "params": ["1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:55

help gettxout
20:29:55

gettxout "txid" n ( includemempool )
Returns details about an unspent transaction output.
Arguments:
1. "txid" (string, required) The transaction id
2. n (numeric, required) vout value
3. includemempool (boolean, optional) Whether to included the mem pool
Result:
{
"bestblock" : "hash", (string) the block hash
"confirmations" : n, (numeric) The number of confirmations
"value" : x.xxx, (numeric) The transaction value in btc
"scriptPubKey" : { (json object)
"asm" : "code", (string)
"hex" : "hex", (string)
"reqSigs" : n, (numeric) Number of required signatures
"type" : "pubkeyhash", (string) The type, eg pubkeyhash
"addresses" : [ (array of string) array of bitcoin addresses
"bitcoinaddress" (string) bitcoin address
,...
]
},
"version" : n, (numeric) The version
"coinbase" : true|false (boolean) Coinbase or not
}
Examples:
Get unspent transactions
> bitcoin-cli listunspent
View the details
> bitcoin-cli gettxout "txid" 1
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "gettxout", "params": ["txid", 1] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:29:58

help gettxoutsetinfo
20:29:58

gettxoutsetinfo
Returns statistics about the unspent transaction output set.
Note this call may take some time.
Result:
{
"height":n, (numeric) The current block height (index)
"bestblock": "hex", (string) the best block hash hex
"transactions": n, (numeric) The number of transactions
"txouts": n, (numeric) The number of output transactions
"bytes_serialized": n, (numeric) The serialized size
"hash_serialized": "hash", (string) The serialized hash
"total_amount": x.xxx (numeric) The total amount
}
Examples:
> bitcoin-cli gettxoutsetinfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "gettxoutsetinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:30:04

help getunconfirmedbalance
20:30:04

getunconfirmedbalance
Returns the server's total unconfirmed balance
20:32:18

help getwalletinfo
20:32:18

getwalletinfo
Returns an object containing various wallet state info.
Result:
{
"walletversion": xxxxx, (numeric) the wallet version
"balance": xxxxxxx, (numeric) the total bitcoin balance of the wallet
"txcount": xxxxxxx, (numeric) the total number of transactions in the wallet
"keypoololdest": xxxxxx, (numeric) the timestamp (seconds since GMT epoch) of the oldest pre-generated key in the key pool
"keypoolsize": xxxx, (numeric) how many new keys are pre-generated
"unlocked_until": ttt, (numeric) the timestamp in seconds since epoch (midnight Jan 1 1970 GMT) that the wallet is unlocked for transfers, or 0 if the wallet is locked
}
Examples:
> bitcoin-cli getwalletinfo
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:21

help getwork
20:32:21

getwork ( "data" )
If 'data' is not specified, it returns the formatted hash data to work on.
If 'data' is specified, tries to solve the block and returns true if it was successful.
Arguments:
1. "data" (string, optional) The hex encoded data to solve
Result (when 'data' is not specified):
{
"midstate" : "xxxx", (string) The precomputed hash state after hashing the first half of the data (DEPRECATED)
"data" : "xxxxx", (string) The block data
"hash1" : "xxxxx", (string) The formatted hash buffer for second hash (DEPRECATED)
"target" : "xxxx" (string) The little endian hash target
}
Result (when 'data' is specified):
true|false (boolean) If solving the block specified in the 'data' was successfull
Examples:
> bitcoin-cli getwork
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwork", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:24

help help
20:32:24

help ( "command" )
List all commands, or get help for a specified command.
Arguments:
1. "command" (string, optional) The command to get help on
Result:
"text" (string) The help text
20:32:27

help importprivkey
20:32:27

importprivkey "bitcoinprivkey" ( "label" rescan )
Adds a private key (as returned by dumpprivkey) to your wallet.
Arguments:
1. "bitcoinprivkey" (string, required) The private key (see dumpprivkey)
2. "label" (string, optional) an optional label
3. rescan (boolean, optional, default=true) Rescan the wallet for transactions
Examples:
Dump a private key
> bitcoin-cli dumpprivkey "myaddress"
Import the private key
> bitcoin-cli importprivkey "mykey"
Import using a label
> bitcoin-cli importprivkey "mykey" "testing" false
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "importprivkey", "params": ["mykey", "testing", false] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:31

help importwallet
20:32:31

importwallet "filename"
Imports keys from a wallet dump file (see dumpwallet).
Arguments:
1. "filename" (string, required) The wallet file
Examples:
Dump the wallet
> bitcoin-cli dumpwallet "test"
Import the wallet
> bitcoin-cli importwallet "test"
Import using the json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "importwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:34

help keypoolrefill
20:32:34

keypoolrefill ( newsize )
Fills the keypool.
Requires wallet passphrase to be set with walletpassphrase call.
Arguments
1. newsize (numeric, optional, default=100) The new keypool size
Examples:
> bitcoin-cli keypoolrefill
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "keypoolrefill", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:43

help listaccounts
20:32:43

listaccounts ( minconf )
Returns Object that has account names as keys, account balances as values.
Arguments:
1. minconf (numeric, optional, default=1) Only onclude transactions with at least this many confirmations
Result:
{ (json object where keys are account names, and values are numeric balances
"account": x.xxx, (numeric) The property name is the account name, and the value is the total balance for the account.
...
}
Examples:
List account balances where there at least 1 confirmation
> bitcoin-cli listaccounts
List account balances including zero confirmation transactions
> bitcoin-cli listaccounts 0
List account balances for 6 or more confirmations
> bitcoin-cli listaccounts 6
As json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listaccounts", "params": [6] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:46

help listaddressgroupings
20:32:46

listaddressgroupings
Lists groups of addresses which have had their common ownership
made public by common use as inputs or as the resulting change
in past transactions
Result:
[
[
[
"bitcoinaddress", (string) The bitcoin address
amount, (numeric) The amount in btc
"account" (string, optional) The account
]
,...
]
,...
]
Examples:
> bitcoin-cli listaddressgroupings
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listaddressgroupings", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
20:32:48

help listlockunspent
20:32:48

listlockunspent
Returns list of temporarily unspendable outputs.
See the lockunspent call to lock and unlock transactions for spending.
Result:
[
{
"txid" : "transactionid", (string) The transaction id locked
"vout" : n (numeric) The vout value
}
,...
]
Examples:
List the unspent transactions
> bitcoin-cli listunspent
Lock an unspent transaction
> bitcoin-cli lockunspent false "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
List the locked transactions
> bitcoin-cli listlockunspent
Unlock the transaction again
> bitcoin-cli lockunspent true "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
As a json rpc call
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listlockunspent", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
|
|
|
|
How much time I need to sync the blockchain from zero using bitcoin-qt and how much with torrent?
I have a 7mb adsl.
It took me 3 days with a 100MBit connection with bitcoin-core. As has been said: you sync only with one client, if you are lucky they have a fast connection. With the torrent you will use your line at ~90% (keep 10% for orga/surfing) or even fully*. It went up to When you are done keep seeding to help others. * Edit: just did a test. The torrent runs at ~ 24MBit/s after ~30 seconds. bitcoin-core is never going to achieve that rate. I'm in Australia on ADSL2+ (24Mbps max is quoted by companies so I'd think ~10Mbps is true speed as max torrent DL speed I get is ~1150kbps ~= 10/8). I am getting 450kBps rate presently, which I'd have to think is ~50x faster than Bitcoin Core. There must be a better way than having 1 peer sending the blockchain; the upload bandwidth jammed to a halt for 4-5 days is infeasible at the painful induction crapshoot. Best way to resolve the issue? If you've either 1) DLd the torrent once before or 2) waited while BTC Core did its thing for 4-5 days, or 3) like Bitcoin ... seed the torrent!  |
|
|
|
I am always suspicious when a third party steps in and becomes a potential centralized regulating body. I know POD is a major issue with many, I and I am in agreement with it... But it's always CryptoAsian, blah blah blah. You hit the nail on the head. CryptoAsian seems like a cool dude, but seriously, Bittrex basically delegated him to vetting code for them and so now it's this one dude vouching for code/projects? That is bullshit and another reason why the Wild West is changing and that bullshit (or even flash pump and dumps -remember those in April-May? ahh, nostalgia) won't be eaten. Either you have a service or platform which is going to rise outta this shit or you don't. The smart people aren't making clones, they're working out how to apply the technology to corporate investment. |
|
|
|
|
Show Posts
