Search results

  1. chaeplin

    v0.10.9.x Help test RC2 forking issues

    I have changed my daemon outgoing to 64(default 8) static const int MAX_OUTBOUND_CONNECTIONS = 64; no of p2p connection < no of masternode is possible. Anyway, I will check existence of masternode by adding masternode ip to addnode. http://tdrk.poolhash.org/blocks/subver.txt (maybe by old...
  2. chaeplin

    v0.10.9.x Help test RC2 forking issues

    blocknotify scripts has error. fixed.
  3. chaeplin

    v0.10.9.x Help test RC2 forking issues

    @eduffield As current http://tdrk.poolhash.org/blocks/masterpay.txt has no correction on orphaned block, I have added http://tdrk.poolhash.org/blocks.html .
  4. chaeplin

    v0.10.9.x Help test RC2 forking issues

    NOMP is on another server. It doesn't show other information. I will make a stat page for nomp. edit: http://54.183.73.24:8080/nomp.txt update : every 2min, darkcoind listtransactions 1 200 0
  5. chaeplin

    v0.10.9.x Help test RC2 forking issues

    One of my job was help desk for internet connection ;D added : dial-up
  6. chaeplin

    v0.10.9.x Help test RC2 forking issues

    eduffield http://tdrk.poolhash.org/blocks/masterlist/16684.txt bottom masternode vote result is interesting.
  7. chaeplin

    v0.10.9.x Help test RC2 forking issues

    Oh.. local ip should be listed in remote server, not in local. Meaning remote 19999 is not opened or remote is not 54.215~~.
  8. chaeplin

    v0.10.9.x Help test RC2 forking issues

    can you post remote server getpeerinfo and getinfo ?
  9. chaeplin

    v0.10.9.x Help test RC2 forking issues

    2 "subver" : "/Satoshi:0.10.9.4/", 4 "subver" : "/Satoshi:0.10.9.9/", 1 "subver" : "/Satoshi:0.9.4.11/", 1 "subver" : "/Satoshi:0.9.5.8/", 3 "subver" : "/Satoshi:0.9.5.9/", This is connected peer's subver of my one node. With this client subver distribution of testnet, it's more like testing in...
  10. chaeplin

    v0.10.9.x Help test RC2 forking issues

    Hmm please test this. at local, add addnode=remoteip to conf. check if remoteip is connected, getpeerinfo will show remoteip if connected. after then, start masternode.
  11. chaeplin

    v0.10.9.x Help test RC2 forking issues

    sent darkcoind sendtoaddress mkRrX4Lg3nPeecTmsWdPpwCMMN9ViwUfu3 1000 79a1199e5246e024d2fe198510320aa660809ce89d12bf887462e6fd25307fd9
  12. chaeplin

    v0.10.9.x Help test RC2 forking issues

    Have you checked ip address of remote node ?
  13. chaeplin

    v0.10.9.x Help test RC2 forking issues

    Yes. I have checked. I think mpos and nomp has different masternode list.
  14. chaeplin

    v0.10.9.x Help test RC2 forking issues

    from block 16267, current masterlist is logged. Masternode Payee[from confirmed block] is linked to logged masterlist. ex) http://tdrk.poolhash.org/blocks/masterlist/16279.txt
  15. chaeplin

    v0.10.9.x Help test RC2 forking issues

    You paid 56 mins ago. 1 hour ago06/09 05:34:162162470.367151mposmnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu430.200
  16. chaeplin

    v0.10.9.x Help test RC2 forking issues

    I think stop at least 10 min, and restart. As removed from masternode list, NM will not be paid. First do update.
  17. chaeplin

    v0.10.9.x Help test RC2 forking issues

    I have restated darkcoind of nomp at block 16232 ~ 16233. nomp found a block at 16235, 16237, 16238, 16239. 16238 has no masternode payment.
  18. chaeplin

    v0.10.9.x Help test RC2 forking issues

    updated to github It's like dsee storm. 2014-06-08 16:25:16 ProcessMessage(dsee, 249 bytes) FAILED 2014-06-08 16:25:16 ProcessMessage(dsee, 249 bytes) FAILED 2014-06-08 16:25:16 ProcessMessage(dsee, 249 bytes) FAILED 2014-06-08 16:25:16 ProcessMessage(dsee, 249 bytes) FAILED 2014-06-08...
Back
Top