Show Posts
|
Pages: [1]
|
3
|
Bitcoin / Development & Technical Discussion / Pybitcointools txhash function, and SIGHASH_ALL = 0
|
on: August 06, 2015, 07:48:11 AM
|
pybitcointools has a txhash function which returns the singable form of a transaction, with SIGHASH appended. However the code returns a reversed hash without the appended SIGHASH bytes for SIGHASH=None, as seen here: https://github.com/vbuterin/pybitcointools/blob/master/bitcoin/transaction.py#L177-L178def txhash(tx, hashcode=None): if isinstance(tx, str) and re.match('^[0-9a-fA-F]*$', tx): tx = changebase(tx, 16, 256) if hashcode: return dbl_sha256(from_string_to_bytes(tx) + encode(int(hashcode), 256, 4)[::-1]) else: return safe_hexlify(bin_dbl_sha256(tx)[::-1])
That doesn't seem right; is it? Also, how is a SIGHASH_ALL value of zero (rare case) calculated? (See this related SE question) Is it just changing the 00 to 01?
|
|
|
4
|
Bitcoin / Development & Technical Discussion / Validating DER sig (brainwallet Tx eg)
|
on: July 28, 2015, 12:58:12 AM
|
https://blockchain.info/tx/54a44539ada32ea5eb218ed5d853a08712be6129d8ec752b8c77f6c88bfe721aSo we have: - sha256("cat")
- sha256("password")
'01000000020fa5ed9983859c6703c5469bdda6f30ee2b59febe89d3e9755e601a35bfe837c020000007f3c303902153b78ce563f89a0ed9414f5aa28ad0d96d6795f9c6302205eff1e344551d115b708155eed631cafa4fe719be5ec68c1f3abbf8670d34e11014104a45ebc40f95cc06ef93a5f5e9daa22774a5c9a120ac14d87c328b44c1158f81cddd109246a4d8bff5f93cbba79a17f2dc6e7c73da8d6bd0d98615d1bf353f8beffffffff0fa5ed9983859c6703c5469bdda6f30ee2b59febe89d3e9755e601a35bfe837c030000007f3c303902153b78ce563f89a0ed9414f5aa28ad0d96d6795f9c6302201e74d38e5abd2836e9e17acf1b94f267b4f99704e2b22eac02ab136ec4740b76014104b568858a407a8721923b89df9963d30013639ac690cce5f555529b77b83cbfc76950f90be717e38a3ece1f5558f40179f8c2502deca11183bb3a3aea797736a6ffffffff01dc05000000000000232103d68f90ba81455256cb7a0df14fb3930d6df61393207f2f3e71659414d296e0f0ac00000000'
dersig1 = "3c303902153b78ce563f89a0ed9414f5aa28ad0d96d6795f9c6302205eff1e344551d115b708155eed631cafa4fe719be5ec68c1f3abbf8670d34e11" dersig2 = "3c303902153b78ce563f89a0ed9414f5aa28ad0d96d6795f9c6302201e74d38e5abd2836e9e17acf1b94f267b4f99704e2b22eac02ab136ec4740b76" How, using pybitcointools (or Python), does one validate these DER sigs (given we know both privkeys)? ( PS: if someone can weigh on this related question, I'd greatly appreciate it
|
|
|
5
|
Bitcoin / Development & Technical Discussion / Using pybitcointools to validate tx_valid.json test vectors
|
on: July 27, 2015, 09:37:06 AM
|
I'm using this fork of the pybitcointools library and am trying to use the Bitcoincore JSON test vectors for unittesting. Can someone advise: 1. How ECDSA is used to verify transactions..? 2. Ideally, how pybitcointools can be used do #1 From tx_valid.json, the first test vector is: [ ["The following are deserialized transactions which are valid."], ["They are in the form"], ["[[[prevout hash, prevout index, prevout scriptPubKey], [input 2], ...],"], ["serializedTransaction, enforceP2SH]"], ["Objects that are only a single string (like this one) are ignored"],
["The following is 23b397edccd3740a74adb603c9756370fafcde9bcc4483eb271ecad09a94dd63"], ["It is of particular interest because it contains an invalidly-encoded signature which OpenSSL accepts"], ["See http://r6.ca/blog/20111119T211504Z.html"], ["It is also the first OP_CHECKMULTISIG transaction in standard form"], [[["60a20bd93aa49ab4b28d514ec10b06e1829ce6818ec06cd3aabd013ebcdc4bb1", 0, "1 0x41 0x04cc71eb30d653c0c3163990c47b976f3fb3f37cccdcbedb169a1dfef58bbfbfaff7d8a473e7e2e6d317b87bafe8bde97e3cf8f065dec022b51d11fcdd0d348ac4 0x41 0x0461cbdcc5409fb4b4d42b51d33381354d80e550078cb532a34bfa2fcfdeb7d76519aecc62770f5b0e4ef8551946d8a540911abe3e7854a26f39f58b25c15342af 2 OP_CHECKMULTISIG"]], "0100000001b14bdcbc3e01bdaad36cc08e81e69c82e1060bc14e518db2b49aa43ad90ba26000000000490047304402203f16c6f40162ab686621ef3000b04e75418a0c0cb2d8aebeac894ae360ac1e780220ddc15ecdfc3507ac48e1681a33eb60996631bf6bf5bc0a0682c4db743ce7ca2b01ffffffff0140420f00000000001976a914660d4ef3a743e3e696ad990364e555c271ad504b88ac00000000", true] Now, we have the following: # inputs ins = ["%s:%d" % ("60a20bd93aa49ab4b28d514ec10b06e1829ce6818ec06cd3aabd013ebcdc4bb1", 0)] # ins = ["prevout hash:prevout index"]
# scriptPubKey of inputs scriptPubKey = '514104cc71eb30d653c0c3163990c47b976f3fb3f37cccdcbedb169a1dfef58bbfbfaff7d8a473e7e2e6d317b87bafe8bde97e3cf8f065dec022b51d11fcdd0d348ac4410461cbdcc5409fb4b4d42b51d33381354d80e550078cb532a34bfa2fcfdeb7d76519aecc62770f5b0e4ef8551946d8a540911abe3e7854a26f39f58b25c15342af52ae'
outs = [{'value': 1000000, 'script': '76a914660d4ef3a743e3e696ad990364e555c271ad504b88ac'}] raw = mktx(ins, outs) # "0100000001b14bdcbc3e01bdaad36cc08e81e69c82e1060bc14e518db2b49aa43ad90ba2600000000000ffffffff0140420f00000000001976a914660d4ef3a743e3e696ad990364e555c271ad504b88ac00000000"
# from test_vector ()or fetching the Tx: 23b397edccd3740a74adb603c9756370fafcde9bcc4483eb271ecad09a94dd63:0) signed = "0100000001b14bdcbc3e01bdaad36cc08e81e69c82e1060bc14e518db2b49aa43ad90ba26000000000490047304402203f16c6f40162ab686621ef3000b04e75418a0c0cb2d8aebeac894ae360ac1e780220ddc15ecdfc3507ac48e1681a33eb60996631bf6bf5bc0a0682c4db743ce7ca2b01ffffffff0140420f00000000001976a914660d4ef3a743e3e696ad990364e555c271ad504b88ac00000000"
der_sig = "0048304402203f16c6f40162ab686621ef3000b04e75418a0c0cb2d8aebeac894ae360ac1e780220ddc15ecdfc3507ac48e1681a33eb60996631bf6bf5bc0a0682c4db743ce7ca2bab01" # NOTE: this signature is not canonical because both the r and s values have the highest bit set (ie ideally r and s should be padded with nullbytes)
So given all the information from the test vectors, how does one verify the signature against the raw transaction? (NB. I'm doing this as a means to learn the way Bitcoin signs/verifies transactions. So far I've had no issue with these unittests)
|
|
|
8
|
Alternate cryptocurrencies / Altcoin Discussion / Altcoin Ecosphere TL;DR required... Been Away For 6 Months
|
on: April 08, 2015, 09:55:04 AM
|
As the thread title says, I've been away from Altcoins for 6 months... I see XMR is still around, which is great, but anyone wanna give me a TL:DR on what the new trends are, or where to look? - Still POW/POS?
- Bittrex still King?
- Ninja launches, pre/postmines
- What is/are the most promising Alts now? Darkcoin & Blackcoin?
PS. I would do the research myself, but I get 1 hour Internet privs per month (long story  )
|
|
|
9
|
Bitcoin / Armory / 0.93 stuck ~323000ish blk: "Somehow tried to add header that's already in map"?
|
on: April 01, 2015, 06:46:32 AM
|
-WARN - 1427685617: (..\Blockchain.cpp:47) Somehow tried to add header that's already in map -WARN - 1427685617: (..\Blockchain.cpp:48) Header Hash: 00000000ad4e4c886567776c89e752614f251cca28b7dfcaf16867677ba0245a Screenshot: https://imgur.com/tuF8uBPWin7 x64, Armory 0.93, BitcoinCore 0.10: Flags: -testnet -rest -txindex=1 -server --testnet --datadir=d:\data\armorynew\testnet3 --satoshi-datadir="d:\data\bitcoincore" --rpcport=8332 --debug --netlog --mtdebug --logfile=d:\data\armorynew Have deleted the d:\data\armory and tried to start again but same shit! HOW DO I FIX THIS GODDAMNED STUCK BLOCKCHAIN ISSUE? PLEASE! Thank you kindly, HOT
|
|
|
10
|
Bitcoin / Bitcoin Technical Support / Database (Re-indexing) Core 0.9.3 from 3-day old %appdata% backup?
|
on: February 11, 2015, 12:27:31 PM
|
I'm getting a corrupted database warning with Win7 x64 0.9.3. Power outage reset the machine and upon reboot there were problems. The database started re-indexing but is taking forever. LUCKILY, I have 2 backups of the %appdata%\bitcoin directory (which is usually a junction to d:\data\bitcoincore). Anyhow, I ran it with datadir flag as e:\bitcoincore (one of 2 dirs which I backed up the entire dir to on Feb 8th) and it's not solving the problem. db.log:Program version 4.8 doesn't match environment version 4.7 debug.loghttps://gist.github.com/anonymous/d1c9a35ae4971d226c072015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 03:22:15 UpdateTip: new best=0000000000000000094a953f2412f7ff058b83356e9500187cbc684f6051f8b3 height=342944 log2_work=82.207776 tx=59274330 date=2015-02-11 02:00:45 progress=0.999887 2015-02-11 03:22:15 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:15 ProcessBlock: ACCEPTED 2015-02-11 03:22:18 UpdateTip: new best=00000000000000000a1ad22a8c0b5471f0511a22041629b0f2b1adf1bd45cd4a height=342945 log2_work=82.207825 tx=59275092 date=2015-02-11 02:21:38 progress=0.999916 2015-02-11 03:22:18 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:18 ProcessBlock: ACCEPTED 2015-02-11 03:22:21 UpdateTip: new best=00000000000000000889dc00d6aac3bda42a7e79662f5f0ce2dba020484d8d52 height=342946 log2_work=82.207875 tx=59275997 date=2015-02-11 02:37:27 progress=0.999938 2015-02-11 03:22:21 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:21 ProcessBlock: ACCEPTED 2015-02-11 03:22:24 UpdateTip: new best=0000000000000000004983ddbc0ea812045fe542003b1cf9cb00810bee87518f height=342947 log2_work=82.207924 tx=59276650 date=2015-02-11 02:49:45 progress=0.999955 2015-02-11 03:22:24 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:24 ProcessBlock: ACCEPTED 2015-02-11 03:22:25 UpdateTip: new best=00000000000000000eba9e65987d2b01cd1851933df42556a2d5d808624ba45f height=342948 log2_work=82.207973 tx=59277041 date=2015-02-11 02:56:06 progress=0.999964 2015-02-11 03:22:25 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:25 ProcessBlock: ACCEPTED 2015-02-11 03:22:26 UpdateTip: new best=0000000000000000118cb7f49c62d573ed033266bd843c464b5a9b51b35b844e height=342949 log2_work=82.208023 tx=59277722 date=2015-02-11 03:19:16 progress=0.999996 2015-02-11 03:22:26 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:22:26 ProcessBlock: ACCEPTED Requesting initialize Running AppInit2 in thread 2015-02-11 03:24:33 Initialization result: 0 2015-02-11 03:24:33 Requesting shutdown 2015-02-11 03:24:33 Running Shutdown in thread 2015-02-11 03:24:33 Shutdown : In progress... 2015-02-11 03:24:33 StopNode() 2015-02-11 03:24:33 Shutdown : done 2015-02-11 03:24:33 Shutdown finished 2015-02-11 03:24:33 Shutdown result: 1 2015-02-11 03:24:33 Stopping thread 2015-02-11 03:24:33 Stopped thread 2015-02-11 03:24:42 keypool reserve 5 2015-02-11 03:24:42 keypool return 5 2015-02-11 03:25:20 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:47160 2015-02-11 03:26:18 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:54709 2015-02-11 03:26:29 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.19/: version 70001, blocks=342804, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=73.170.6.150:47790 2015-02-11 03:26:29 Added time data, samples 38, offset +24 (+0 minutes) 2015-02-11 03:26:56 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:3085 2015-02-11 03:28:31 ResendWalletTransactions() 2015-02-11 03:28:56 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=148.251.249.69:0, peer=148.251.249.69:15873 2015-02-11 03:29:00 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:38602 2015-02-11 03:30:42 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=127.0.0.1:47640, peer=46.105.210.248:47640 2015-02-11 03:30:42 Added time data, samples 39, offset +25 (+0 minutes) 2015-02-11 03:30:42 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:31:27 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:41220 2015-02-11 03:31:37 socket recv error An existing connection was forcibly closed by the remote host. (10054) 2015-02-11 03:31:37 receive version message: /Satoshi:0.9.3/: version 70002, blocks=342949, us=XXX.XXX.129.69:50236, them=71.166.38.146:8333, peer=71.166.38.146:8333 2015-02-11 03:31:37 Added time data, samples 40, offset +26 (+0 minutes) 2015-02-11 03:31:37 receive version message: : version 32100, blocks=308636, us=XXX.XXX.129.69:8333, them=46.4.121.99:8333, peer=46.4.121.99:35062 2015-02-11 03:31:37 Added time data, samples 41, offset +24 (+0 minutes) 2015-02-11 03:31:37 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:34:39 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.194.231.211:7997 2015-02-11 03:35:13 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.67.102.19:64097 2015-02-11 03:35:15 receive version message: /Satoshi:0.8.1/: version 70001, blocks=342949, us=127.0.0.1:6378, them=XXX.XXX.129.69:8333, peer=54.82.89.182:37026 2015-02-11 03:35:15 Added time data, samples 42, offset +24 (+0 minutes) 2015-02-11 03:36:39 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:43888 2015-02-11 03:37:19 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:30280 2015-02-11 03:38:23 connected to self at 127.0.0.1:51088, disconnecting 2015-02-11 03:39:17 receive version message: /Satoshi:0.9.1/: version 70002, blocks=342582, us=XXX.XXX.129.69:51112, them=24.35.17.153:8333, peer=24.35.17.153:8333 2015-02-11 03:39:17 Added time data, samples 43, offset +8 (+0 minutes) 2015-02-11 03:39:17 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:39:44 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:18062 2015-02-11 03:40:04 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:9663 2015-02-11 03:40:14 UPnP Port Mapping successful. 2015-02-11 03:41:54 receive version message: /Satoshi:0.8.6/: version 70002, blocks=275686, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=46.63.26.63:32570 2015-02-11 03:41:54 Added time data, samples 44, offset +25 (+0 minutes) 2015-02-11 03:45:30 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:23815 2015-02-11 03:47:37 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=0, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:12834 2015-02-11 03:47:55 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342948, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:9035 2015-02-11 03:51:13 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.153.147.74:32502 2015-02-11 03:51:50 receive version message: /BitCoinJ:0.11.2/MultiBit:0.5.18/: version 70001, blocks=342949, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=71.246.193.126:60033 2015-02-11 03:51:50 Added time data, samples 45, offset +17 (+0 minutes) 2015-02-11 03:51:50 nTimeOffset = +24 (+0 minutes) 2015-02-11 03:52:13 receive version message: /Shibetoshi:0.1/: version 70002, blocks=0, us=[::]:0, them=[::]:0, peer=192.155.84.55:54857 2015-02-11 03:52:25 receive version message: /Satoshi:0.8.6/: version 70001, blocks=329127, us=XXX.XXX.129.69:8333, them=24.86.204.139:8333, peer=24.86.204.139:53768 2015-02-11 03:52:25 Added time data, samples 46, offset +24 (+0 minutes) 2015-02-11 03:53:46 Pre-allocating up to position 0x200000 in rev00229.dat 2015-02-11 03:53:47 UpdateTip: new best=00000000000000001182cc7fc6569bd8612107af6abe696ccb56de8d16d7e85d height=342950 log2_work=82.208072 tx=59279136 date=2015-02-11 03:49:44 progress=0.999994 2015-02-11 03:53:47 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:53:47 ProcessBlock: ACCEPTED 2015-02-11 03:54:21 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:30528 2015-02-11 03:54:48 UpdateTip: new best=000000000000000012e7874c34155d89897c58014c86f02925f32748a35c0867 height=342951 log2_work=82.208121 tx=59279585 date=2015-02-11 03:54:40 progress=1.000000 2015-02-11 03:54:48 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 03:54:48 ProcessBlock: ACCEPTED 2015-02-11 03:56:23 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:45423 2015-02-11 03:56:29 ResendWalletTransactions() 2015-02-11 03:56:52 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:64086 2015-02-11 03:56:58 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.194.231.211:31393 2015-02-11 03:58:13 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.67.102.19:29820 2015-02-11 03:59:56 receive version message: /Shibetoshi:0.1/: version 70002, blocks=0, us=[::]:0, them=[::]:0, peer=192.155.84.55:59985 2015-02-11 04:00:14 UPnP Port Mapping successful. 2015-02-11 04:01:09 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:3357 2015-02-11 04:02:28 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:37536 2015-02-11 04:03:48 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:35467 2015-02-11 04:03:59 receive version message: /getaddr.bitnodes.io:0.1/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:27052 2015-02-11 04:06:44 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342951, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:11396 2015-02-11 04:07:48 UpdateTip: new best=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 log2_work=82.208171 tx=59280195 date=2015-02-11 04:07:33 progress=1.000000 2015-02-11 04:07:48 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 04:07:48 ProcessBlock: ACCEPTED 2015-02-11 04:08:10 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:51813 2015-02-11 04:08:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:22 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:22 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:08:23 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2015-02-11 04:12:45 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.94.223.66:17730 2015-02-11 04:13:03 ResendWalletTransactions() 2015-02-11 04:13:20 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=342952, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=148.251.238.178:42671 2015-02-11 04:13:59 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:48226 2015-02-11 04:16:39 receive version message: /Satoshi:0.8.6/: version 70001, blocks=342949, us=XXX.XXX.129.69:8333, them=0.0.0.0:0, peer=54.152.68.195:40948 2015-02-11 04:16:51 receive version message: /Satoshi:0.9.2/: version 70002, blocks=447232, us=XXX.XXX.129.69:8333, them=128.8.124.7:8333, peer=128.8.124.7:50920 2015-02-11 04:16:51 Added time data, samples 47, offset +25 (+0 minutes) 2015-02-11 04:16:51 nTimeOffset = +24 (+0 minutes) 2015-02-11 04:17:47 keypool reserve 5 2015-02-11 04:17:47 keypool return 5 2015-02-11 04:20:14 UPnP Port Mapping successful. 2015-02-11 04:24:44 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=XXX.XXX.129.69:8333, them=127.0.0.1:8333, peer=82.130.103.162:54400 2015-02-11 04:24:58 UpdateTip: new best=000000000000000012a62978fcbe7bd3bf9ee105573b15efcddc26bf75330c38 height=342953 log2_work=82.20822 tx=59280949 date=2015-02-11 04:25:11 progress=1.000000 2015-02-11 04:24:58 SetBestChain: 1 of last 100 blocks above version 2 2015-02-11 04:24:58 ProcessBlock: ACCEPTED 2015-02-11 04:24:58 receive version message: /bitcoinj:0.12.2/Bitcoin Wallet:4.18/: version 70001, blocks=342952, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=31.134.143.131:50979 2015-02-11 04:24:58 Added time data, samples 48, offset +24 (+0 minutes) 2015-02-11 04:25:43 ERROR: AcceptToMemoryPool : inputs already spent 2015-02-11 04:50:57 2015-02-11 04:50:57 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:50:57 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:50:57 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:50:57 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:50:57 Using data directory d:\data\bitcoincore 2015-02-11 04:50:57 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:50:57 Using 8 threads for script verification 2015-02-11 04:50:57 Using wallet wallet.dat 2015-02-11 04:50:57 init message: Verifying wallet... 2015-02-11 04:50:57 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:50:57 Bound to [::]:8333 2015-02-11 04:50:57 Bound to 0.0.0.0:8333 2015-02-11 04:50:57 init message: Loading block index... 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:50:57 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:50:57 Opened LevelDB successfully 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:03 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:03 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:03 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999940 2015-02-11 04:51:03 init message: Verifying blocks... 2015-02-11 04:51:03 Verifying last 288 blocks at level 3 2015-02-11 04:51:04 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:04 : Error opening block database. Do you want to rebuild the block database now? 2015-02-11 04:51:04 Aborted block database rebuild. Exiting. 2015-02-11 04:51:04 Shutdown : In progress... 2015-02-11 04:51:04 StopNode() 2015-02-11 04:51:04 Shutdown : done Requesting initialize Running AppInit2 in thread 2015-02-11 04:51:20 2015-02-11 04:51:20 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15 +0200) 2015-02-11 04:51:20 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014 2015-02-11 04:51:20 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-02-11 04:51:20 Default data directory C:\Users\xxx\AppData\Roaming\Bitcoin 2015-02-11 04:51:20 Using data directory d:\data\bitcoincore 2015-02-11 04:51:20 Using at most 20 connections (2048 file descriptors available) 2015-02-11 04:51:20 Using 8 threads for script verification 2015-02-11 04:51:20 Using wallet wallet.dat 2015-02-11 04:51:20 init message: Verifying wallet... 2015-02-11 04:51:20 CDBEnv::Open : LogDir=d:\data\bitcoincore\database ErrorFile=d:\data\bitcoincore\db.log 2015-02-11 04:51:21 Bound to [::]:8333 2015-02-11 04:51:21 Bound to 0.0.0.0:8333 2015-02-11 04:51:21 init message: Loading block index... 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:21 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:21 Opened LevelDB successfully 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file = 229 2015-02-11 04:51:23 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=31, size=9390462, heights=342923...342953, time=2015-02-10...2015-02-11) 2015-02-11 04:51:23 LoadBlockIndexDB(): transaction index disabled 2015-02-11 04:51:23 LoadBlockIndexDB(): hashBestChain=000000000000000011cfdbe5968ce51177b0b0ded47e97ca964e2b35b3dafd72 height=342952 date=2015-02-11 04:07:33 progress=0.999939 2015-02-11 04:51:23 init message: Verifying blocks... 2015-02-11 04:51:23 Verifying last 288 blocks at level 3 2015-02-11 04:51:23 LevelDB read failure: Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:23 Invalid argument: not an sstable (bad magic number) 2015-02-11 04:51:29 init message: Loading block index... 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\blocks\index 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Wiping LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opening LevelDB in d:\data\bitcoincore\chainstate 2015-02-11 04:51:29 Opened LevelDB successfully 2015-02-11 04:51:29 Initializing databases... 2015-02-11 04:51:29 init message: Verifying blocks... 2015-02-11 04:51:29 block index 285ms 2015-02-11 04:51:29 init message: Loading wallet... 2015-02-11 04:51:29 nFileVersion = 90300 2015-02-11 04:51:29 Keys: 0 plaintext, 365 encrypted, 365 w/ metadata, 365 total 2015-02-11 04:51:29 wallet 269ms 2015-02-11 04:51:29 init message: Loading addresses... 2015-02-11 04:51:30 Reindexing block file blk00000.dat... 2015-02-11 04:51:30 Loaded 0 addresses from peers.dat 36ms 2015-02-11 04:51:30 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 log2_work=32.000022 tx=1 date=2009-01-03 18:15:05 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 Pre-allocating up to position 0x100000 in rev00000.dat 2015-02-11 04:51:30 UpdateTip: new best=00000000839a8e6886ab5951d76f411475428afc90947ee320161bbf18eb6048 height=1 log2_work=33.000022 tx=2 date=2009-01-09 02:54:25 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000006a625f06636b8bb6ac7b960a8d03705d1ace08b1a19da3fdcc99ddbd height=2 log2_work=33.584985 tx=3 date=2009-01-09 02:55:44 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000082b5015589a3fdf2d4baff403e6f0be035a5d9742c1cae6295464449 height=3 log2_work=34.000022 tx=4 date=2009-01-09 03:02:53 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000004ebadb55ee9096c9a2f8880e09da59c0d68b1c228da88e48844a1485 height=4 log2_work=34.32195 tx=5 date=2009-01-09 03:16:28 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000009b7262315dbf071787ad3656097b892abffd1f95a1a022f896f533fc height=5 log2_work=34.584985 tx=6 date=2009-01-09 03:23:48 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000003031a0e73735690c5a1ff2a4be82553b2a12b776fbd3a215dc8f778d height=6 log2_work=34.807377 tx=7 date=2009-01-09 03:29:49 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000071966c2b1d065fd446b1e485b2c9d9594acd2007ccbd5441cfc89444 height=7 log2_work=35.000022 tx=8 date=2009-01-09 03:39:29 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000408c48f847aa786c2268fc3e6ec2af68e8468a34a28c61b7f1de0dc6 height=8 log2_work=35.169947 tx=9 date=2009-01-09 03:45:43 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000008d9dc510f23c2657fc4f67bea30078cc05a90eb89e84cc475c080805 height=9 log2_work=35.32195 tx=10 date=2009-01-09 03:54:39 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000002c05cc2e78923c34df87fd108b22221ac6076c18f3ade378a4d915e9 height=10 log2_work=35.459454 tx=11 date=2009-01-09 04:05:52 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000097be56d606cdd9c54b04d4747e957d3608abe69198c661f2add73073 height=11 log2_work=35.584985 tx=12 date=2009-01-09 04:12:40 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000027c2488e2510d1acf4369787784fa20ee084c258b58d9fbd43802b5e height=12 log2_work=35.700462 tx=13 date=2009-01-09 04:21:28 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000005c51de2031a895adc145ee2242e919a01c6d61fb222a54a54b4d3089 height=13 log2_work=35.807377 tx=14 date=2009-01-09 04:23:40 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=0000000080f17a0c5a67f663a9bc9969eb37e81666d9321125f0e293656f8a37 height=14 log2_work=35.906913 tx=15 date=2009-01-09 04:33:09 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000b3322c8c3ef7d2cf6da009a776e6a99ee65ec5a32f3f345712238473 height=15 log2_work=36.000022 tx=16 date=2009-01-10 04:45:46 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=00000000174a25bb399b009cc8deff1c4b3ea84df7e93affaaf60dc3416cc4f5 height=16 log2_work=36.087485 tx=17 date=2009-01-10 04:45:58 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000003ff1d0d70147acfbef5d6a87460ff5bcfce807c2d5b6f0a66bfdf809 height=17 log2_work=36.169947 tx=18 date=2009-01-10 05:03:11 progress=0.000000 2015-02-11 04:51:30 ProcessBlock: ACCEPTED 2015-02-11 04:51:30 UpdateTip: new best=000000008693e98cf893e4c85a446b410bb4dfa129bd1be582c09ed3f0261116 height=18 log2_work=36.24795 t
|
|
|
11
|
Economy / Service Discussion / Bitpay INSIGHT API (advantages unclear)
|
on: February 10, 2015, 10:46:25 AM
|
I've been using various Python libraries, including Blockcypher, Chain.com, Blocktrail, etc so code a blockchain parser as a personal project. The API documentation for them all is quite reasonable. I was looking into Bitcoin ABE and understand Bitpay's Insight API advanced blockchain functionality, however the documentation seems incredibly lacking (I'm not well versed in Javascript yet). Can someone outline the advantages Insight's API and front end provide? Any related links (especially for Python!) would be greatly appreciated. TL:DR; what is so great about the Bitpay Insight API services?
|
|
|
12
|
Bitcoin / Bitcoin Discussion / Bitcoin Core 0.9.2.1 RPC Calls Extended List (Pastebin/BitcoinSE x-post)
|
on: September 28, 2014, 11:20:09 AM
|
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/
|
|
|
14
|
Alternate cryptocurrencies / Altcoin Discussion / Stop sponsoring ICO/IPOs without escrow!
|
on: August 27, 2014, 09:52:23 AM
|
https://bittrex.zendesk.com/hc/en-us/articles/203127460-ClusterCoin-Doing-the-Right-ThingClustercoin ICO investors were lucky to be covered by Bittrex's escrow in this case. If the "community" doesn't stop with these ICOs it's sponsoring scammers and destroying the altcoin landscape, and whatever regulation comes from this is going to bite Bitcoin in the ass to boot. The only ICOs to consider should have very strong escrow terms. AltcoinHerald did a great article on this. Quoted in part: The ‘get rich quick‘ mentality that is required to constantly get defrauded by ICOs stems from the same stream of human greed that is encouraging altcoin exchanges to constantly list them. The trouble is, as the malfeasance mounts and the dollar losses continue to sky-rocket, regulation is the only possible outcome. Escrow terms must be changed now. They must implement a solid legal framework written by a tech-savvy law firm that protects all parties during the transaction. Until this happens, altcoin ICOs must be avoided at all costs by anyone who is unwilling to lose all their money.
|
|
|
|