Latest posts of: haoqian

Show Posts
Pages: [1]

Bitcoin / Bitcoin Technical Support / Re: Unstable Bitcoin Connection

on: May 12, 2018, 06:42:30 AM

Quote from: achow101 on May 08, 2018, 09:13:00 PM addnode does not guarantee that a connection to the specified node will be attempted. If you want to guarantee that a connection will be attempted, then you need to use the `-connect` option. Solved! Thanks!

Bitcoin / Bitcoin Technical Support / Unstable Bitcoin Connection

on: May 07, 2018, 02:21:51 PM

I fork bitcoin core 16.0 and create my own alt coin. I run two bitcoind: Code: sudo ~/bitcoin/src/bitcoind -addnode=127.0.0.1:9332 -port=8963 -rpcport=8962 -debug=rpc -dns=0 -dnsseed=0 sudo ~/bitcoin/src/bitcoind -datadir=$HOME/.bitcoin2 -addnode=127.0.0.1:8962 -port=9333 -rpcport=9332 -debug=rpc -dns=0 -dnsseed=0 However, the connection between them seems very unstable. When I use bitcoin-cli -getinfo, sometimes the connection=0 I run locally, So I think the connection should be pretty stable? What's wrong? Thank you very much.

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 06, 2018, 05:57:26 AM

Quote from: hushan on May 05, 2018, 02:07:02 PM Quote from: haoqian on May 04, 2018, 01:04:34 PM Quote from: hushan on May 04, 2018, 12:29:09 AM Quote from: haoqian on May 03, 2018, 02:26:22 PM Thank you for your reply. I do generate my own genesis block. It seems that it is just keeping downloading. It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. Thank you very much for your reply. Those are the changes I made: https://github.com/zhq422194011/bitcoin/commit/e0b0d5c9b4be209cf640cf6e8ae29bf1525c58da My bitcoin.conf is: Code: server=1 gen=1 rpcbind=0.0.0.0 rpcuser=rpcuser rpcpassword=111111 rpcallowip=127.0.0.1 rpcallowip=0.0.0.0/0 listen=1 I run the following two bitcoinds: Code: sudo ~/bitcoin/src/bitcoind -addnode=127.0.0.1:9332 -port=8963 -rpcport=8962 -debug=rpc -dns=0 -dnsseed=0 sudo ~/bitcoin/src/bitcoind -datadir=$HOME/.bitcoin2 -addnode=127.0.0.1:8962 -port=9333 -rpcport=9332 -debug=rpc -dns=0 -dnsseed=0 When I run ./bitcoin-cli getblocktemplate, I got: Code: error code: -10 error message: Bitcoin is downloading blocks... The code change looks right, for the first node, don't use -addnode, becuase the second node hasn't started yet, also add "-connect=0 -listen=1 -maxtipage=$((246060*5000))" to it, for second node, use addnode to add the first node. One more question, I found that the first node will not download the blocks from second one (first node is still at block 0). I also run a third node which connects to the second node. The third node will also not download the blocks (still at block 0 and the getblocktemplate works fine). Why?

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 06, 2018, 05:48:31 AM

Quote from: hushan on May 05, 2018, 02:07:02 PM Quote from: haoqian on May 04, 2018, 01:04:34 PM Quote from: hushan on May 04, 2018, 12:29:09 AM Quote from: haoqian on May 03, 2018, 02:26:22 PM Thank you for your reply. I do generate my own genesis block. It seems that it is just keeping downloading. It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. Thank you very much for your reply. Those are the changes I made: https://github.com/zhq422194011/bitcoin/commit/e0b0d5c9b4be209cf640cf6e8ae29bf1525c58da My bitcoin.conf is: Code: server=1 gen=1 rpcbind=0.0.0.0 rpcuser=rpcuser rpcpassword=111111 rpcallowip=127.0.0.1 rpcallowip=0.0.0.0/0 listen=1 I run the following two bitcoinds: Code: sudo ~/bitcoin/src/bitcoind -addnode=127.0.0.1:9332 -port=8963 -rpcport=8962 -debug=rpc -dns=0 -dnsseed=0 sudo ~/bitcoin/src/bitcoind -datadir=$HOME/.bitcoin2 -addnode=127.0.0.1:8962 -port=9333 -rpcport=9332 -debug=rpc -dns=0 -dnsseed=0 When I run ./bitcoin-cli getblocktemplate, I got: Code: error code: -10 error message: Bitcoin is downloading blocks... The code change looks right, for the first node, don't use -addnode, becuase the second node hasn't started yet, also add "-connect=0 -listen=1 -maxtipage=$((246060*5000))" to it, for second node, use addnode to add the first node. It works! Thank you very much! Your instruction is very useful! Fews details I want to ask you. Mining only works for second node. So the connection is one way only? I found that connects is pretty unstable (sometime connections would be disconnected). why?

Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error

on: May 04, 2018, 02:46:53 PM

Quote from: achow101 on May 03, 2018, 08:49:13 PM Quote from: haoqian on May 03, 2018, 04:27:06 PM How can I spend money using createrawtransaction? I am not familiar with Segwit... createrawtransaction is unrelated to this or to segwit. The problem is that the wallet assumes segwit is enabled by default, but segwit is not enabled according to your network rules. So you either have to enable segwit in the network rules, or change the wallet to assume segwit is disabled. How you do that you will need to figure out yourself. Thank you. You gave me a helpful info.

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 04, 2018, 01:43:16 PM

Quote from: hushan on May 04, 2018, 12:29:09 AM Quote from: haoqian on May 03, 2018, 02:26:22 PM Thank you for your reply. I do generate my own genesis block. It seems that it is just keeping downloading. It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. Changes including this... (with 0x, did not show on the git diff) consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000000000000000000100010001"); The bitcoind is still keep downloading.

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 04, 2018, 01:04:34 PM

Quote from: hushan on May 04, 2018, 12:29:09 AM Quote from: haoqian on May 03, 2018, 02:26:22 PM Thank you for your reply. I do generate my own genesis block. It seems that it is just keeping downloading. It would be a lot helpful if you could run a git diff on your workspace and paste the change you have made, so that we can identify the problem. Thank you very much for your reply. Those are the changes I made: https://github.com/zhq422194011/bitcoin/commit/e0b0d5c9b4be209cf640cf6e8ae29bf1525c58da My bitcoin.conf is: Code: server=1 gen=1 rpcbind=0.0.0.0 rpcuser=rpcuser rpcpassword=111111 rpcallowip=127.0.0.1 rpcallowip=0.0.0.0/0 listen=1 I run the following two bitcoinds: Code: sudo ~/bitcoin/src/bitcoind -addnode=127.0.0.1:9332 -port=8963 -rpcport=8962 -debug=rpc -dns=0 -dnsseed=0 sudo ~/bitcoin/src/bitcoind -datadir=$HOME/.bitcoin2 -addnode=127.0.0.1:8962 -port=9333 -rpcport=9332 -debug=rpc -dns=0 -dnsseed=0 When I run ./bitcoin-cli getblocktemplate, I got: Code: error code: -10 error message: Bitcoin is downloading blocks...

Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error

on: May 03, 2018, 04:27:06 PM

Quote from: achow101 on May 03, 2018, 04:22:52 PM

Quote from: haoqian on May 03, 2018, 03:40:21 PM

Code:

      "txid": "551ba4bde3460bca6a6cae7da57ffd8b3f1baf18ad7a2e6d50f8d4f5b0a94e14",
      "vout": 1,
      "scriptSig": {
        "asm": "0014620cfaeb631c99d45490cc6560a7258835c260f8",
        "hex": "160014620cfaeb631c99d45490cc6560a7258835c260f8"
      },
      "txinwitness": [
        "3045022100a1e4403c6327fb787ef498cfaf6c54f8372f2792c06a7156cad6cf15c729de2802201eb1b48e2443b04688091897caf0fc9afbfc002227c05441a5f1723be9a532e401",
        "02533dc7b0e2d8f359fb235fd52bcda6135cfb0e39c6d9d93a10704457ff30e6ff"
      ],
      "sequence": 4294967295
    }

This is your problem, the input you are spending is a segwit input. You will need to figure out how to prevent your fork from creating segwit outputs that can be spent as inputs.

Thank you very much for your reply.

How can I spend money using createrawtransaction? I am not familiar with Segwit...

Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error

on: May 03, 2018, 03:40:21 PM

Quote from: achow101 on May 03, 2018, 03:35:16 PM

Can you also post what your final signed transaction looks like?

Quote from: haoqian on May 03, 2018, 03:29:30 PM

getrawchangeaddress shows this:

Code:

3PgBJaR5fCw9nBtij7THqfHbbENdCdFEuv

This will be a problem for you later because that is a segwit address and you do not have segwit enabled.

Thank you for your reply.

It looks like this:

Code:

{
  "txid": "391c0428614cb7f966bba368c3b83050d81f17190125b686e1434562bb82edd4",
  "hash": "6dc00133fa2043cda29d610f087c739fcc65f4a4efc4f0bc5058bcd003bd7f61",
  "version": 2,
  "size": 251,
  "vsize": 169,
  "locktime": 0,
  "vin": [
    {
      "txid": "551ba4bde3460bca6a6cae7da57ffd8b3f1baf18ad7a2e6d50f8d4f5b0a94e14",
      "vout": 1,
      "scriptSig": {
        "asm": "0014620cfaeb631c99d45490cc6560a7258835c260f8",
        "hex": "160014620cfaeb631c99d45490cc6560a7258835c260f8"
      },
      "txinwitness": [
        "3045022100a1e4403c6327fb787ef498cfaf6c54f8372f2792c06a7156cad6cf15c729de2802201eb1b48e2443b04688091897caf0fc9afbfc002227c05441a5f1723be9a532e401",
        "02533dc7b0e2d8f359fb235fd52bcda6135cfb0e39c6d9d93a10704457ff30e6ff"
      ],
      "sequence": 4294967295
    }
  ],
  "vout": [
    {
      "value": 0.00000000,
      "n": 0,
      "scriptPubKey": {
        "asm": "OP_RETURN 4d79206e616d65206973205a68616e672048616f7169616e",
        "hex": "6a184d79206e616d65206973205a68616e672048616f7169616e",
        "type": "nulldata"
      }
    },
    {
      "value": 48.99984900,
      "n": 1,
      "scriptPubKey": {
        "asm": "OP_HASH160 360ba84dc5961b64e67d75dd623a26c31d98beb9 OP_EQUAL",
        "hex": "a914360ba84dc5961b64e67d75dd623a26c31d98beb987",
        "reqSigs": 1,
        "type": "scripthash",
        "addresses": [
          "36cnNsjRuaP6cLGPFRXycaetmvmog5Wnyn"
        ]
      }
    }
  ]
}

Bitcoin / Bitcoin Technical Support / Re: Using Createrawtransaction Got no-witness-yet Error

on: May 03, 2018, 03:29:30 PM

Quote from: achow101 on May 03, 2018, 03:24:12 PM

Quote from: haoqian on May 03, 2018, 03:17:43 PM

I did not include any Segwit in any transaction. why does it show here?

Are you sure? If you forked from the latest Bitcoin Core, it uses segwit by default. Can you post what the changeaddress looks like and what the output of listunspent looks like?

Thank you for your reply.

I forked 0.16 bitcoin core.

getrawchangeaddress shows this:

Code:

3PgBJaR5fCw9nBtij7THqfHbbENdCdFEuv

listunspent shows this:

Code:

  {
    "txid": "4bffb171833ca3fe5fe5f272a482161809be371131f89f6c116d695096c60afe",
    "vout": 0,
    "address": "1A6csP8jrpyruyW4a9tX9Nonv4R8AviB1y",
    "account": "",
    "scriptPubKey": "76a91463c9274bf6297bd724ad66eafab4fd94f7c9714488ac",
    "amount": 50.00000000,
    "confirmations": 21,
    "spendable": true,
    "solvable": true,
    "safe": true
  },
  {
    "txid": "efd172501ea2760738987a3d4865dc41aae2cc988d02e08860f939166ad97bff",
    "vout": 0,
    "address": "1A6csP8jrpyruyW4a9tX9Nonv4R8AviB1y",
    "account": "",
    "scriptPubKey": "76a91463c9274bf6297bd724ad66eafab4fd94f7c9714488ac",
    "amount": 50.00000000,
    "confirmations": 46,
    "spendable": true,
    "solvable": true,
    "safe": true
  }

Bitcoin / Bitcoin Technical Support / Using Createrawtransaction Got no-witness-yet Error

on: May 03, 2018, 02:32:40 PM

Hi, I am trying to use createrawtransaction.

When I use following code:

Code:

op_return_data="4d79206e616d65"
utxo_txid=$(~/bitcoin/src/bitcoin-cli listunspent | jq -r '.[0] | .txid')
utxo_vout=$(~/bitcoin/src/bitcoin-cli listunspent | jq -r '.[0] | .vout')
utxo_balance=$(~/bitcoin/src/bitcoin-cli listunspent | jq -r '.[0] | .amount')
new_balance=$(echo "$utxo_balance - 0.0001" | bc | awk '{printf "%f", $0}')
changeaddress=$(~/bitcoin/src/bitcoin-cli getrawchangeaddress)
rawtxhex=$(~/bitcoin/src/bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''{ "data": "'$op_return_data'", "'$changeaddress'": "'$new_balance'" }''')
signedhex=$(~/bitcoin/src/bitcoin-cli signrawtransaction $rawtxhex | jq -r .hex)
~/bitcoin/src/bitcoin-cli sendrawtransaction $signedhex

It will get :

Code:

error code: -26
error message:
64: no-witness-yet

I do not know why. How to solve it? Could you help me?

Thanks!

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 03, 2018, 02:26:22 PM

Thank you for your reply. I do generate my own genesis block. It seems that it is just keeping downloading.

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: May 03, 2018, 09:25:01 AM

Thank you very much for your reply. One more question is that I do not know why it is keeping "Bitcoin is downloading blocks..." Because of this, the getblocktemplate will not work.

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 30, 2018, 04:04:00 AM

Quote from: hushan on April 29, 2018, 09:18:35 PM Quote from: haoqian on April 29, 2018, 02:46:01 PM Thank you very much for your reply. Run ./bitcoin-cli getblocktemplate , I got following: error code: -9 error message: Bitcoin is not connected! In debug log: 2018-04-29 14:41:29 Bitcoin Core version v0.16.0.0-9ea62a3dc-dirty (release build) Oh, sorry I forgot to mention, in order to mine, the node has to connect to at least one peer node. So you need to run another instance of bitcoind and let it connect to the first node, like: Code: bitcoind -addnode=127.0.0.1:6333 -port=9333 -rpcport=9332 .... other arguments replace 6333 with your first node's port. After this, try restart the miner again. Also from the debug.log you posted, it looks you didn't remove the dns seeds servers, that's ok, you can add "-dns=0 -dnsseed=0" to bitcoind command line arguments to disable them. If you are running your private network, there is no point to connect to public bitcoin nodes. I use Code: sudo ./bitcoind -addnode=10.211.55.5:8963 -debug=rpc -dns=0 -dnsseed=0 And run Code: ./bitcoin-cli getblocktemplate I got: error code: -10 error message: Bitcoin is downloading blocks... And debug.log is 2018-04-30 03:32:36 init message: Rewinding blocks... 2018-04-30 03:32:36 init message: Verifying blocks... 2018-04-30 03:32:36 block index 17ms 2018-04-30 03:32:36 init message: Loading wallet... 2018-04-30 03:32:36 nFileVersion = 160000 2018-04-30 03:32:36 Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total 2018-04-30 03:32:36 wallet 26ms 2018-04-30 03:32:36 setKeyPool.size() = 2000 2018-04-30 03:32:36 mapWallet.size() = 0 2018-04-30 03:32:36 mapAddressBook.size() = 0 2018-04-30 03:32:36 mapBlockIndex.size() = 1 2018-04-30 03:32:36 nBestHeight = 0 2018-04-30 03:32:36 Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there 2018-04-30 03:32:36 torcontrol thread start 2018-04-30 03:32:36 Bound to [::]:8963 2018-04-30 03:32:36 Bound to 0.0.0.0:8963 2018-04-30 03:32:36 init message: Loading P2P addresses... 2018-04-30 03:32:36 Loaded 1168 addresses from peers.dat 2ms 2018-04-30 03:32:36 init message: Loading banlist... 2018-04-30 03:32:36 init message: Starting network threads... 2018-04-30 03:32:36 DNS seeding disabled 2018-04-30 03:32:36 net thread start 2018-04-30 03:32:36 addcon thread start 2018-04-30 03:32:36 init message: Done loading 2018-04-30 03:32:36 opencon thread start 2018-04-30 03:32:36 msghand thread start 2018-04-30 03:32:36 New outbound peer connected: version: 70015, blocks=0, peer=0 2018-04-30 03:32:42 connect() to [2001:0:9d38:90d7:10aa:20c7:aa6f:d318]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:43 connect() to [2001:0:9d38:6ab8:302b:340f:e723:b15e]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:43 connect() to [2a01:4f8:192:34d0::2]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:49 ThreadRPCServer method=getblocktemplate 2018-04-30 03:32:50 connect() to 43.229.76.45:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:56 connect() to [2001:41d0:1:8b26::1]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:56 connect() to [2002:b4b2:3612::b4b2:3612]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:58 connect() to [2a02:c205:2008:7160::1]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:59 connect() to [2001:0:9d38:6ab8:34f7:15b2:3012:3a74]:8333 failed after select(): Connection refused (111) 2018-04-30 03:32:59 connect() to [2604:a880:2:d0::22fa:3001]:8333 failed after select(): Connection refused (111) 2018-04-30 03:33:01 connect() to [2a01:4f8:10a:3718::2]:8333 failed after select(): Connection refused (111) 2018-04-30 03:33:02 connect() to [2601:646:4101:1603:5809:1bff:fe55:6678]:8333 failed after select(): Connection refused (111) 2018-04-30 03:33:08 connect() to 5.45.75.15:8333 failed after select(): Connection refused (111) 2018-04-30 03:33:09 connect() to 79.46.194.163:8333 failed after select(): Connection refused (111)

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 30, 2018, 02:25:36 AM

Thank you very much for your reply. I did delete all the DNS seeds followed your instructions. However, it seems that it is still try to connect bitcoin network. By the way, how can you run two bitcoinds in the same machine? I tried, however, it failed to obtain the lock of .bitcoin

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 29, 2018, 02:46:01 PM

Thank you very much for your reply. Run ./bitcoin-cli getblocktemplate , I got following: error code: -9 error message: Bitcoin is not connected! In debug log: 2018-04-29 14:41:29 Bitcoin Core version v0.16.0.0-9ea62a3dc-dirty (release build) 2018-04-29 14:41:29 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2018-04-29 14:41:29 Assuming ancestors of block 0000000000000000005214481d2d96f898e3d5416e43359c145944a909d242e0 have valid signatures. 2018-04-29 14:41:29 Setting nMinimumChainWork=0000000000000000000000000000000000000000000000000000000100010001 2018-04-29 14:41:29 Using the 'sse4' SHA256 implementation 2018-04-29 14:41:29 Using RdRand as an additional entropy source 2018-04-29 14:41:29 Default data directory /home/zhq/.bitcoin 2018-04-29 14:41:29 Using data directory /home/zhq/.bitcoin 2018-04-29 14:41:29 Using config file /home/zhq/.bitcoin/bitcoin.conf 2018-04-29 14:41:29 Using at most 125 automatic connections (1024 file descriptors available) 2018-04-29 14:41:29 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2018-04-29 14:41:29 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2018-04-29 14:41:29 Using 2 threads for script verification 2018-04-29 14:41:29 scheduler thread start 2018-04-29 14:41:29 Binding RPC on address 0.0.0.0 port 8962 failed. 2018-04-29 14:41:29 HTTP: creating work queue of depth 16 2018-04-29 14:41:29 Starting RPC 2018-04-29 14:41:29 Starting HTTP RPC server 2018-04-29 14:41:29 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation. 2018-04-29 14:41:29 HTTP: starting 4 worker threads 2018-04-29 14:41:29 Using wallet directory /home/zhq/.bitcoin 2018-04-29 14:41:29 init message: Verifying wallet(s)... 2018-04-29 14:41:29 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2018-04-29 14:41:29 Using wallet wallet.dat 2018-04-29 14:41:29 CDBEnv::Open: LogDir=/home/zhq/.bitcoin/database ErrorFile=/home/zhq/.bitcoin/db.log 2018-04-29 14:41:29 Cache configuration: 2018-04-29 14:41:29 * Using 2.0MiB for block index database 2018-04-29 14:41:29 * Using 8.0MiB for chain state database 2018-04-29 14:41:29 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2018-04-29 14:41:29 init message: Loading block index... 2018-04-29 14:41:29 Opening LevelDB in /home/zhq/.bitcoin/blocks/index 2018-04-29 14:41:29 Opened LevelDB successfully 2018-04-29 14:41:29 Using obfuscation key for /home/zhq/.bitcoin/blocks/index: 0000000000000000 2018-04-29 14:41:29 LoadBlockIndexDB: last block file = 0 2018-04-29 14:41:29 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=305, heights=0...0, time=2018-04-18...2018-04-18) 2018-04-29 14:41:29 Checking all blk files are present... 2018-04-29 14:41:29 LoadBlockIndexDB: transaction index disabled 2018-04-29 14:41:29 Opening LevelDB in /home/zhq/.bitcoin/chainstate 2018-04-29 14:41:29 Opened LevelDB successfully 2018-04-29 14:41:29 Using obfuscation key for /home/zhq/.bitcoin/chainstate: d5db8947d9371fc8 2018-04-29 14:41:29 Loaded best chain: hashBestChain=00000000ad913538b8764573d00c3eb4a87723e11d8bd008f9125246c58e0252 height=0 date=2018-04-18 03:12:39 progress=0.000000 2018-04-29 14:41:29 init message: Rewinding blocks... 2018-04-29 14:41:29 init message: Verifying blocks... 2018-04-29 14:41:29 block index 21ms 2018-04-29 14:41:29 init message: Loading wallet... 2018-04-29 14:41:29 nFileVersion = 160000 2018-04-29 14:41:29 Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total 2018-04-29 14:41:29 wallet 25ms 2018-04-29 14:41:29 setKeyPool.size() = 2000 2018-04-29 14:41:29 mapWallet.size() = 0 2018-04-29 14:41:29 mapAddressBook.size() = 0 2018-04-29 14:41:29 mapBlockIndex.size() = 1 2018-04-29 14:41:29 nBestHeight = 0 2018-04-29 14:41:29 Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there 2018-04-29 14:41:29 Bound to [::]:8963 2018-04-29 14:41:29 Bound to 0.0.0.0:8963 2018-04-29 14:41:29 init message: Loading P2P addresses... 2018-04-29 14:41:29 torcontrol thread start 2018-04-29 14:41:29 Loaded 1191 addresses from peers.dat 3ms 2018-04-29 14:41:29 init message: Loading banlist... 2018-04-29 14:41:29 init message: Starting network threads... 2018-04-29 14:41:29 net thread start 2018-04-29 14:41:29 init message: Done loading 2018-04-29 14:41:29 opencon thread start 2018-04-29 14:41:29 msghand thread start 2018-04-29 14:41:29 addcon thread start 2018-04-29 14:41:29 dnsseed thread start 2018-04-29 14:41:30 connect() to [2600:3c02::f03c:91ff:fe8e:bcd9]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:31 connect() to [2001:0:9d38:6abd:180b:29be:3429:fede]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:31 connect() to [2001:0:9d38:6abd:180b:29be:3429:fede]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:37 connect() to [2001:0:9d38:953c:3445:1bcb:b8b5:9653]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:37 ThreadRPCServer method=getblocktemplate 2018-04-29 14:41:39 ThreadRPCServer method=getblocktemplate 2018-04-29 14:41:40 Loading addresses from DNS seeds (could take a while) 2018-04-29 14:41:40 0 addresses found from DNS seeds 2018-04-29 14:41:40 dnsseed thread exit 2018-04-29 14:41:43 connect() to [2001:0:9d38:6ab8:d3:69e:d0a0:1b73]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:43 connect() to [2001:0:5ef5:79fb:2851:c:524c:a180]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:44 connect() to [2001:0:9d38:6ab8:878:21cf:2b5b:2860]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:45 connect() to [2a01:4f8:140:524a::2]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:46 connect() to [2002:d917:d95::d917:d95]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:47 connect() to [2a03:b0c0:3:d0::23fb:6001]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:47 connect() to [2001:41f0:61:0:72f3:95ff:fe09:7521]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:48 connect() to [2a03:b0c0:3:d0::44b9:4001]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:48 connect() to [2001:0:9d38:90d7:3c2c:10a4:bbfa:e09d]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:49 connect() to [2a02:c207:2002:9013::1]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:49 connect() to [2001:0:9d38:6ab8:183d:3649:b8f5:35d9]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:50 connect() to [2a00:ee2:1200:1900:20c:29ff:fe81:a0a3]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:50 connect() to [2601:186:c100:6bcd:16bd:cea1:235d:1c19]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:52 connect() to [2400:dd01:1034:e00:f21f:afff:fedc:164d]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:53 connect() to [2a01:680:10:10::1]:8333 failed after select(): Connection refused (111) 2018-04-29 14:41:53 connect() to [2001:0:9d38:6abd:1c96:24dc:a753:d6f2]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:06 connect() to [2001:0:9d38:6ab8:868:1baa:b174:b764]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:06 connect() to [2001:0:9d38:6abd:9e:3294:c2b5:67d7]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:07 connect() to [2001:0:4137:9e76:3424:211:b600:b4cb]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:07 connect() to [2002:b4b2:3612::b4b2:3612]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:08 connect() to [2001:0:9d38:6abd:3470:346d:af23:d41b]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:09 connect() to [2604:a880:400:d0::2004:c001]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:10 connect() to [2001:980:231b:1:8e89:a5ff:fee3:f8be]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:10 connect() to [2002:9247:4cec::9247:4cec]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:11 connect() to [2a02:c205:2008:272::1]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:12 connect() to [2600:1f18:609f:da02:b283:b16e:aac4:749f]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:19 connect() to [2001:0:9d38:6abd:2436:3c96:91e9:2de3]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:19 connect() to [2001:0:9d38:90d7:34f3:3584:d0a4:aa5]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:37 connect() to [2a01:4f8:10a:3fe4::2]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:38 connect() to 208.100.137.204:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:39 connect() to [2001:0:9d38:78cf:3cb3:2773:4da3:d4c]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:40 connect() to 99.198.237.76:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:41 connect() to [2a01:4f8:171:d4a::2]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:43 connect() to [2001:0:5ef5:79fb:281c:2085:518d:9c97]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:49 connect() to [2a02:7b40:50d0:e335::1]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:49 connect() to [2001:0:9d38:6ab8:2436:3c78:431d:d559]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:50 connect() to [2001:0:9d38:6abd:109f:379e:aeff:3957]:8333 failed after select(): Connection refused (111) 2018-04-29 14:42:50 connect() to [2606:df00:7:4:4caa:2c79:b619:27c9]:8333 failed after select(): Connection refused (111)

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 29, 2018, 10:34:20 AM

Hi, thank you very much for your reply. I am now using the 0.16 version and I used the following: ./minerd --user rpcuser --pass 111111 --url http://127.0.0.1:8961/ --threads 4 --coinbase-addr XQg3PmNxX9oEbxsymqtQHir6dkPpVPTJ6P --coinbase-sig "my test coins" -a sha256d -D My bitcoin.conf is: server=1 gen=0 rpcuser=rpcuser rpcpassword=111111 rpcallowip=127.0.0.1 rpcport=8961 listen=1 However, I still get the same error: [2018-04-29 03:21:00] Binding thread 0 to cpu 0 [2018-04-29 03:21:00] 4 miner threads started, using 'sha256d' algorithm. [2018-04-29 03:21:00] Binding thread 3 to cpu 1 [2018-04-29 03:21:00] Binding thread 2 to cpu 0 [2018-04-29 03:21:00] Binding thread 1 to cpu 1 [2018-04-29 03:21:00] HTTP request failed: The requested URL returned error: 500 Internal Server Error [2018-04-29 03:21:00] json_rpc_call failed, retry after 30 seconds [2018-04-29 03:21:30] HTTP request failed: The requested URL returned error: 500 Internal Server Error [2018-04-29 03:21:30] json_rpc_call failed, retry after 30 seconds [2018-04-29 03:22:00] HTTP request failed: The requested URL returned error: 500 Internal Server Error [2018-04-29 03:22:00] json_rpc_call failed, retry after 30 seconds [2018-04-29 03:22:30] HTTP request failed: The requested URL returned error: 500 Internal Server Error

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 29, 2018, 07:52:09 AM

May I know which version of bitcoin core you are using?

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 29, 2018, 07:11:25 AM

I opened the debug mode and it shows that: 2018-04-29T07:10:19Z ThreadRPCServer method=getblocktemplate user=rpcuser It looks that something wrong with getblocktemplate

Alternate cryptocurrencies / Altcoin Discussion / Re: *** Complete Guide on How to Create a New Alt Coin – Update 2018 ***

on: April 29, 2018, 06:52:31 AM

Hi, Thank you very much for your post. It helps me a lot. Now I encountered a problem. When I try CPU Mining, it shows a 500 Internal Server Error. How to solve it? [2018-04-28 23:39:50] Binding thread 0 to cpu 0 [2018-04-28 23:39:50] Binding thread 1 to cpu 1 [2018-04-28 23:39:50] 2 miner threads started, using 'scrypt' algorithm. [2018-04-28 23:39:50] HTTP request failed: The requested URL returned error: 500 Internal Server Error [2018-04-28 23:39:50] json_rpc_call failed, retry after 30 seconds My Bitcoin.conf is: server=1 gen=0 rpcuser=rpcuser rpcpassword=111111 rpcallowip=127.0.0.1 rpcport=8962 listen=1

Pages: [1]