Feedback Public Testnet Evaluation

Discussion in 'Technical Development' started by tacotime, Jan 6, 2016.

  1. 2017/12/15 - Decred v1.1.2 released! → Release Notes  → Downloads
  1. Blizzy

    Blizzy Full Member

    Jan 4, 2016
    225
    109
    Male
    #121 Blizzy, Jan 30, 2016
    Last edited: Jan 30, 2016
    So now i can pow and pos togheter, this are the settings i have choose :

    --enablestakemining --balancetomaintain=20 --ticketmaxprice=50

    and my wallet have buyed these tickets:

    --wallet gettickets true /notls
    {
    "hashes": [
    "e764b06b70571d389ef907f76cb833dcc7bdd30503f07faa2e30a2dba45a8008",
    "b3af43f0a5ee39dc3a42cd403fcf16fd9178da7d64dead7c6a602122c7a02b14",
    "4e62101aa91b3d635c9a5654ba4387cb8ec536019bbeb543d3bac9e82fc4724b",
    "e70b1cc788fa1fc9a7b2b2980d8aab600a77be4dcd9e166ff8a3f76cc585164c",
    "39b919e96f13ca34aeb303522f919aed2b5ce951827b50ce2ccee36c32a2a356",
    "67779ecf92d8d7d5c2a1fb2eb542f8e48da0157cc0eef319d9b287f2bc66715d",
    "1cf453d816738645789af273bd0138d3fdc538af7606d5b4597174211ba7cb5e",
    "fea5060db46a6fcd9dcbab75ed781e7cca0807787701f3407cbe011ecf8aa988",
    "d393176bf0d6eb149a4cff2bab336ec4f97c4656217060e37d12e0452a20ae91",
    "9a33671a09bfc8789aa3d2742ac078f37a144290946c3cb36241bccc0298c4b4",
    "81ed118d966cac7f699606ba6c3cdd484697aea70d22363a4b21076a02bba7bb",
    "3a80fce8644d7461c760b6e88a2538ea395294d585fdb99d9d01ce7cad0f8cc4",
    "a14642b6bba192d42a6b8a91357706c74118a6f921a88708e573eb07519e9bc7",
    "735bac242c8b9068dee0b3e63fca1280fcac4fb92dbae298dc2cd73e1d1bbdc9",
    "4db25469966ad47c6bfba424c11dacd2baf5c80ef7ab302da6745c9c41e729d4",
    "4e2c17af2e2b4c8797391ece5476a5803f3b302b46a564652361e5e9aab235d7",
    "45e6749530212d496d408e06f5b0e144d5b60904f1fd737a07fcdaf2730b7fd7",
    "867e73040b6797cfe28f2c4e4b971dde01bc39e8da04b97999f92718126df8da",
    "6a3be71efccda41e4b1ebd8e0c30dc7b522e902ea640baede2af85045fac9ff9",
    "64f2c54d274b61c09d27a19f3c60e7d32b360ad5a996e418a91390190d60d1fa",
    "1e8edbbebc01c2a8a3264de7826dd4f772094c5bcdedcad941fb452778171134",
    "479d252b4a02de5ce19ae8ac45e250faf6e8d86bb3fa8c3a38503cb2101919bf"
    ]
    }

    but my question is i have choose --balancetomaintain=20 --ticketmaxprice=50 why my wallet balance now is 10 decred?(was 210 before the purchase). The --balancetomaintain=20 is not the limit of my wallet balance?

    My TX list looks also strange! (was different before..i cant even see the first 10 + 100 +100 decred i got yesterday from you)

    --wallet listtransactions /notls
    [
    {
    "account": "",
    "amount": -0,
    "category": "send",
    "confirmations": 0,
    "fee": -1e-05,
    "time": 1454166527,
    "timereceived": 1454166527,
    "txid": "6a3be71efccda41e4b1ebd8e0c30dc7b522e902ea640baede2af85045fac9ff9",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "category": "send",
    "confirmations": 0,
    "fee": -1e-05,
    "time": 1454166527,
    "timereceived": 1454166527,
    "txid": "81ed118d966cac7f699606ba6c3cdd484697aea70d22363a4b21076a02bba7bb",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "000000000051638cebacefb330917a437a4b9cb08f1feb65098171aed4c18b
    96",
    "blocktime": 1454166515,
    "category": "send",
    "confirmations": 1,
    "fee": -1e-05,
    "time": 1454166401,
    "timereceived": 1454166401,
    "txid": "67779ecf92d8d7d5c2a1fb2eb542f8e48da0157cc0eef319d9b287f2bc66715d",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "000000000051638cebacefb330917a437a4b9cb08f1feb65098171aed4c18b
    96",
    "blocktime": 1454166515,
    "category": "send",
    "confirmations": 1,
    "fee": -1e-05,
    "time": 1454166402,
    "timereceived": 1454166402,
    "txid": "3a80fce8644d7461c760b6e88a2538ea395294d585fdb99d9d01ce7cad0f8cc4",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "0000000000506c6983b1f5554dbbe50d551587dc5e4cae50eb2a98b2bc99c8
    62",
    "blocktime": 1454166358,
    "category": "send",
    "confirmations": 2,
    "fee": -1e-05,
    "time": 1454166251,
    "timereceived": 1454166251,
    "txid": "45e6749530212d496d408e06f5b0e144d5b60904f1fd737a07fcdaf2730b7fd7",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "0000000000506c6983b1f5554dbbe50d551587dc5e4cae50eb2a98b2bc99c8
    62",
    "blocktime": 1454166358,
    "category": "send",
    "confirmations": 2,
    "fee": -1e-05,
    "time": 1454166251,
    "timereceived": 1454166251,
    "txid": "64f2c54d274b61c09d27a19f3c60e7d32b360ad5a996e418a91390190d60d1fa",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "000000000039de351b6a3a1a8a10e920f3cb499b8d7127af35edd4df39ea4a
    bd",
    "blocktime": 1454166245,
    "category": "send",
    "confirmations": 3,
    "fee": -1e-05,
    "time": 1454166172,
    "timereceived": 1454166172,
    "txid": "39b919e96f13ca34aeb303522f919aed2b5ce951827b50ce2ccee36c32a2a356",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "000000000039de351b6a3a1a8a10e920f3cb499b8d7127af35edd4df39ea4a
    bd",
    "blocktime": 1454166245,
    "category": "send",
    "confirmations": 3,
    "fee": -1e-05,
    "time": 1454166172,
    "timereceived": 1454166172,
    "txid": "a14642b6bba192d42a6b8a91357706c74118a6f921a88708e573eb07519e9bc7",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "0000000000210f82a8d5bdfabd81489faf03b0c5cfb8887de7e91b1e32ae8f
    02",
    "blocktime": 1454166159,
    "category": "send",
    "confirmations": 4,
    "fee": -1e-05,
    "time": 1454165990,
    "timereceived": 1454165990,
    "txid": "1cf453d816738645789af273bd0138d3fdc538af7606d5b4597174211ba7cb5e",
    "vout": 1,
    "walletconflicts": []
    },
    {
    "account": "",
    "amount": -0,
    "blockhash": "0000000000210f82a8d5bdfabd81489faf03b0c5cfb8887de7e91b1e32ae8f
    02",
    "blocktime": 1454166159,
    "category": "send",
    "confirmations": 4,
    "fee": -1e-05,
    "time": 1454165990,
    "timereceived": 1454165990,
    "txid": "fea5060db46a6fcd9dcbab75ed781e7cca0807787701f3407cbe011ecf8aa988",
    "vout": 1,
    "walletconflicts": []
    }
    ]

    thanks!
     
  2. evilpan

    evilpan New Member

    Jan 5, 2016
    6
    1
    Male
    No issues with testnet.
    Everything seems working fine.
     
  3. WilderX

    WilderX New Member

    Dec 17, 2015
    13
    2
    Male
    Sir, I have questions.

    1. How come I have 50% Reject rate with mining? It seems to me like my other GPU's are finding the same block as the other or what is this about? Can I do something about it? I have crossfire enabled btw.. bad idea for mining?
    2. How do I adjust intensity it seems like it's defaulting to 9? this is my commandline: cgminer --blake256 -o 127.0.0.1:19109 -u ABC -p ABC
    3. What is this "without LP as user ABC" long poll about? It's feature for pools or what? Do I need to worry about it as solo mining?

    I run Windows 10 and 3 x Fury X GPU's driver 16.1
    Below my cgminer log (I have deleted the new block messages):

    cgminer version 3.7.2 - Started: [2016-01-30 18:06:43]
    --------------------------------------------------------------------------------
    (5s):8.161G (avg):8.184Gh/s | A:2724 R:2724 HW:0 WU:28877.8/m
    ST: 5 SS: 0 NB: 31 LW: 0 GF: 0 RF: 0
    Connected to 127.0.0.1 diff 681 without LP as user ABC
    Block: 78fc4600... Diff:1.18K Started: [18:54:45] Best share: 19.8K
    --------------------------------------------------------------------------------
    [P]ool management [G]PU management ettings [D]isplay options [Q]uit

    GPU 0: | 2.736G/2.749Gh/s | A: 681 R:1362 HW:0 WU:9536.3/m I: 9
    GPU 1: | 2.682G/2.694Gh/s | A: 681 R:1362 HW:0 WU:9558.7/m I: 9
    GPU 2: | 2.737G/2.746Gh/s | A:1362 R: 0 HW:0 WU:9813.6/m I: 9
    --------------------------------------------------------------------------------

    [2016-01-30 18:13:58] Accepted 423b1860 Diff 989/681 GPU 1
    [2016-01-30 18:13:59] Rejected 423b1860 Diff 989/681 GPU 0
    [2016-01-30 18:14:00] Rejected 520f405c Diff 799/681 GPU 1
    [2016-01-30 18:34:45] Accepted 5b5f185d Diff 717/681 GPU 2
    [2016-01-30 18:47:59] Found block for pool 0!
    [2016-01-30 18:47:59] Accepted 034f520d Diff 19.8K/681 BLOCK! GPU 2
    [2016-01-30 18:48:00] Found block for pool 0!
    [2016-01-30 18:48:00] Rejected 034f520d Diff 19.8K/681 BLOCK! GPU 0
    [2016-01-30 18:48:00] Found block for pool 0!
    [2016-01-30 18:48:00] Rejected 034f520d Diff 19.8K/681 BLOCK! GPU 1
     
  4. Michael

    Michael Jr. Member
    Designer

    Dec 26, 2015
    63
    35
    Male
    Online Business and Investment Strategy Explorer
    New Zealand

    I'm not sure if this will be much help
    I thought I might as well share it though, to show how many configuring settings I had once set up inside a cgminer.conf file
    We might be able to use many of these settings, in a same or similar fashion

    Here is the long config file that I once used, during mining a previous coin:

    {
    "pools" : [
    {
    "url" : "http://127.0.0.1:#####",
    "user" : "Username",
    "pass" : "Password"
    }
    ]
    ,
    "intensity" : "10",
    "vectors" : "1",
    "worksize" : "256",
    "kernel" : "phatk",
    "lookup-gap" : "0",
    "thread-concurrency" : "0",
    "shaders" : "0",
    "gpu-engine" : "0-0",
    "gpu-fan" : "0-85",
    "gpu-memclock" : "0",
    "gpu-memdiff" : "0",
    "gpu-powertune" : "0",
    "gpu-vddc" : "0.000",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "75",
    "api-port" : "4028",
    "expiry" : "120",
    "gpu-dyninterval" : "7",
    "gpu-platform" : "0",
    "gpu-threads" : "2",
    "log" : "5",
    "no-pool-disable" : true,
    "queue" : "1",
    "scan-time" : "60",
    "temp-hysteresis" : "3",
    "worktime" : true,
    "shares" : "0",
    "kernel-path" : "/usr/local/bin"
    }
     
  5. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    That config really bugs me - no offense to you, I'm sure you don't know what a lot of the options do - but a LOT are extraneous, and some are probably slightly detrimental over time. Allow me just to change a couple things...

    {
    "pools" : [
    {
    "url" : "http://127.0.0.1:#####",
    "user" : "Username",
    "pass" : "Password"
    }
    ]
    ,
    "intensity" : "10",
    "worksize" : "256",
    "gpu-fan" : "0-85",
    "temp-cutoff" : "95",
    "temp-overheat" : "85",
    "temp-target" : "75",
    "gpu-dyninterval" : "7",
    "gpu-threads" : "2",
    "queue" : "1",
    "scan-time" : "10",
    "temp-hysteresis" : "3",
    "worktime" : true
    }

    It's not your fault, it's just me being OCD - that really looks so much better.
     
    chappjc, tacotime and Michael like this.
  6. Michael

    Michael Jr. Member
    Designer

    Dec 26, 2015
    63
    35
    Male
    Online Business and Investment Strategy Explorer
    New Zealand

    I totally agree! :)
     
  7. HeapsIoN

    HeapsIoN New Member
    Advocate (Facebook)

    Dec 28, 2015
    45
    4
    Male
    Sorry if someone has already asked. Or has been answered elsewhere, but, is what is earned from test net worth anything?
    Or will it been wiped once main net launches?
     
  8. davecgh

    davecgh Hero Member
    Developer Organizer

    Dec 31, 2015
    642
    788
    Male
    United States
    No, it's not worth anything. It's only for testing purposes in order to make sure everything is working properly, everyone has a chance to get their setups configured properly, and other developers to have a chance to get their software ready (pools, exchanges, etc).
     
    HeapsIoN likes this.
  9. HeapsIoN

    HeapsIoN New Member
    Advocate (Facebook)

    Dec 28, 2015
    45
    4
    Male
    Ok thanks @davecgh just wanted to check. I'd say I'm all ready for main then :D
     
  10. WilderX

    WilderX New Member

    Dec 17, 2015
    13
    2
    Male
    Thans Michael and Wolf, but what am I missing because that config aint working for me? Also shouldn't the conf include the algo?

    [2016-01-31 13:10:10] Started cgminer 3.7.2
    [2016-01-31 13:10:10] Loaded configuration file cgminer.conf
    [2016-01-31 13:10:11] Probing for an alive pool
    [2016-01-31 13:10:11] Network diff set to 836 (target 1b524e4f)
    [2016-01-31 13:10:11] No suitable long-poll found for http://127.0.0.1:19109
    [2016-01-31 13:10:12] Unable to open phatk121016.cl or ./phatk121016.cl for reading
    [2016-01-31 13:10:12] Failed to init GPU thread 0, disabling device 0
    [2016-01-31 13:10:12] Restarting the GPU from the menu will not fix this.
    [2016-01-31 13:10:12] Try restarting cgminer.
     
  11. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    Oops. Put "blake256": true, right before intensity - yes, put the trailing comma there, as well.
     
    chappjc likes this.
  12. WilderX

    WilderX New Member

    Dec 17, 2015
    13
    2
    Male
    So much rejects? It's like the other GPU's are finding the same block or what is happening here? Is this because this is small test network or can I do something about this?

    cgminer version 3.7.2 - Started: [2016-01-31 14:45:04]
    --------------------------------------------------------------------------------
    (5s):8.548G (avg):8.426Gh/s | A:1585 R:7923 HW:0 WU:27432.1/m
    ST: 8 SS: 0 NB: 12 LW: 0 GF: 0 RF: 0
    Connected to 127.0.0.1 diff 792 without LP as user ABC
    Block: b5e83300... Diff:359 Started: [15:01:17] Best share: 1.16K
    --------------------------------------------------------------------------------
    [P]ool management [G]PU management ettings [D]isplay options [Q]uit
    GPU 0: 56.0C 2916RPM | 2.808G/2.809Gh/s | A: 0 R:3962 HW:0 WU:9138.9/m I:14
    GPU 1: 70.0C 2884RPM | 2.811G/2.808Gh/s | A:792 R:3962 HW:0 WU:9144.8/m I:14
    GPU 2: 72.0C 2931RPM | 2.809G/2.809Gh/s | A:792 R: 0 HW:0 WU:9148.4/m I:14
    --------------------------------------------------------------------------------

    [2016-01-31 14:45:03] Started cgminer 3.7.2
    [2016-01-31 14:45:03] Loaded configuration file cgminer.conf
    [2016-01-31 14:45:03] Probing for an alive pool
    [2016-01-31 14:45:04] Network diff set to 359 (target 1b52b635)
    [2016-01-31 14:45:04] No suitable long-poll found for http://127.0.0.1:19109
    [2016-01-31 14:48:52] New block detected on network
    [2016-01-31 14:51:57] Found block for pool 0!
    [2016-01-31 14:51:59] Found block for pool 0!
    [2016-01-31 14:51:59] Found block for pool 0!
    [2016-01-31 14:52:00] New block detected on network
    [2016-01-31 14:52:44] Found block for pool 0!
    [2016-01-31 14:52:44] Found block for pool 0!
    [2016-01-31 14:52:44] Accepted 4086cb2d Diff 1.02K/792 BLOCK! GPU 2 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (3.540) W:0.382 (0.000) S:0.0
    47 R:14:52:44
    [2016-01-31 14:52:44] Rejected 4086cb2d Diff 1.02K/792 BLOCK! GPU 0 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (3.500) W:0.382 (0.000) S:0.
    038 R:14:52:44
    [2016-01-31 14:52:44] Found block for pool 0!
    [2016-01-31 14:52:44] Found block for pool 0!
    [2016-01-31 14:52:44] Rejected 4086cb2d Diff 1.02K/792 BLOCK! GPU 1 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (3.529) W:0.382 (0.000) S:0.
    002 R:14:52:44
    [2016-01-31 14:52:44] Rejected 4086cb2d Diff 1.02K/792 BLOCK! GPU 1 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (3.541) W:0.383 (0.000) S:0.
    002 R:14:52:44
    [2016-01-31 14:52:45] Found block for pool 0!
    [2016-01-31 14:52:45] Rejected 4086cb2d Diff 1.02K/792 BLOCK! GPU 1 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (4.336) W:0.286 (0.000) S:0.
    001 R:14:52:45
    [2016-01-31 14:52:46] Found block for pool 0!
    [2016-01-31 14:52:46] New block detected on network
    [2016-01-31 14:52:46] Rejected 4086cb2d Diff 1.02K/792 BLOCK! GPU 1 <-93503400.24d255cf M:p D:792.330 G:14:52:40:0.001 O (5.373) W:0.383 (0.001) S:0.
    282 R:14:52:46
    [2016-01-31 14:54:12] New block detected on network
    [2016-01-31 14:54:36] New block detected on network
    [2016-01-31 14:56:21] New block detected on network
    [2016-01-31 14:57:30] New block detected on network
    [2016-01-31 14:58:15] Found block for pool 0!
    [2016-01-31 14:58:15] Accepted 38b9fb44 Diff 1.16K/792 BLOCK! GPU 1 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.002 O (3.950) W:0.382 (0.000) S:0.0
    47 R:14:58:15
    [2016-01-31 14:58:15] Found block for pool 0!
    [2016-01-31 14:58:15] Rejected 38b9fb44 Diff 1.16K/792 BLOCK! GPU 0 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.001 O (3.919) W:0.383 (0.000) S:0.
    002 R:14:58:15
    [2016-01-31 14:58:15] Found block for pool 0!
    [2016-01-31 14:58:15] Rejected 38b9fb44 Diff 1.16K/792 BLOCK! GPU 0 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.001 O (3.883) W:0.368 (0.000) S:0.
    001 R:14:58:15
    [2016-01-31 14:58:15] Found block for pool 0!
    [2016-01-31 14:58:15] Rejected 38b9fb44 Diff 1.16K/792 BLOCK! GPU 1 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.001 O (3.948) W:0.383 (0.000) S:0.
    001 R:14:58:15
    [2016-01-31 14:58:16] Found block for pool 0!
    [2016-01-31 14:58:16] Rejected 38b9fb44 Diff 1.16K/792 BLOCK! GPU 0 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.001 O (5.158) W:0.383 (0.000) S:0.
    004 R:14:58:16
    [2016-01-31 14:58:17] Found block for pool 0!
    [2016-01-31 14:58:17] Rejected 38b9fb44 Diff 1.16K/792 BLOCK! GPU 0 <-af970a00.9e05e0d0 M:p D:792.330 G:14:58:11:0.001 O (5.490) W:0.382 (0.000) S:0.
    001 R:14:58:17
    [2016-01-31 14:58:18] New block detected on network
    [2016-01-31 14:58:55] New block detected on network
    [2016-01-31 14:59:59] New block detected on network
    [2016-01-31 15:01:17] New block detected on network
     
  13. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    My bet is that you're on simnet and not the public testnet. Also, you're hitting a bug in the miner - look closer. Those shares are all the same share found by different cards, and therefore when the miner tries to submit them all, only one is gonna work.
     
  14. WilderX

    WilderX New Member

    Dec 17, 2015
    13
    2
    Male
    simnet? How could I have ended up there? This is my daemon command and log ->>>> dcrd --testnet -u ABC -P ABC --miningaddr=TsW77tVuw21iGbstNFsS6pc1mmd9gouSYWN --notls

    14:56:20 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m47.03s (1 transaction, height 4058, 2016-01-31 14:56:00 +0200 EET)
    14:57:27 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m7.48s (1 transaction, height 4059, 2016-01-31 14:57:12 +0200 EET)
    14:58:15 2016-01-31 [INF] RPCS: Block submitted via getwork accepted: 000000000038b9fb4458b79c756e22a131fc290dad07ccbe19f3ffedd849afe5
    14:58:15 2016-01-31 [INF] RPCS: Block submitted via getwork rejected: already have block 000000000038b9fb4458b79c756e22a131fc290dad07ccbe19f3ffedd849afe5
    14:58:15 2016-01-31 [INF] RPCS: Block submitted via getwork rejected: already have block 000000000038b9fb4458b79c756e22a131fc290dad07ccbe19f3ffedd849afe5
    14:58:15 2016-01-31 [ERR] RPCS: Block submitted via getwork has no matching template for merkle root 26078d4088787bad176c4637e82d333f1df11301cb2045d08d903da6f875ded5
    14:58:16 2016-01-31 [ERR] RPCS: Block submitted via getwork has no matching template for merkle root 26078d4088787bad176c4637e82d333f1df11301cb2045d08d903da6f875ded5
    14:58:17 2016-01-31 [ERR] RPCS: Block submitted via getwork has no matching template for merkle root 26078d4088787bad176c4637e82d333f1df11301cb2045d08d903da6f875ded5
    14:58:52 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m24.5s (1 transaction, height 4061, 2016-01-31 15:00:54 +0200 EET)
    14:59:57 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m4.98s (1 transaction, height 4062, 2016-01-31 15:01:06 +0200 EET)
    15:01:15 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m18.01s (1 transaction, height 4063, 2016-01-31 15:03:19 +0200 EET)
    15:04:15 2016-01-31 [INF] BMGR: Processed 1 block in the last 3m0.11s (1 transaction, height 4064, 2016-01-31 15:04:00 +0200 EET)
    15:05:13 2016-01-31 [INF] BMGR: Processed 1 block in the last 58.49s (1 transaction, height 4065, 2016-01-31 15:06:25 +0200 EET)
    15:06:32 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m18.89s (1 transaction, height 4066, 2016-01-31 15:05:51 +0200 EET)
    15:07:05 2016-01-31 [INF] BMGR: Processed 1 block in the last 32.62s (1 transaction, height 4067, 2016-01-31 15:08:15 +0200 EET)
    15:11:44 2016-01-31 [INF] BMGR: Processed 1 block in the last 4m39.02s (2 transactions, height 4068, 2016-01-31 15:11:33 +0200 EET)
    15:13:39 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m54.98s (1 transaction, height 4069, 2016-01-31 15:13:22 +0200 EET)
    15:15:12 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m33.35s (1 transaction, height 4070, 2016-01-31 15:14:44 +0200 EET)
    15:16:59 2016-01-31 [INF] BMGR: Processed 1 block in the last 1m47.12s (1 transaction, height 4071, 2016-01-31 15:16:48 +0200 EET)
    15:17:58 2016-01-31 [INF] BMGR: Processed 1 block in the last 58.52s (2 transactions, height 4072, 2016-01-31 15:18:38 +0200 EET)
     
  15. Wolf

    Wolf Jr. Member

    Jan 25, 2016
    107
    45
    Odd, then. You're finding blocks a little fast for the current diff.
     
  16. vuiltje

    vuiltje New Member

    Jan 28, 2016
    4
    0
    Male
    My tx doesn't seem to get confirmed. Any idea why.

    {
    "amount": 0,
    "fee": 0.99999,
    "confirmations": 0,
    "blockhash": "",
    "blockindex": 0,
    "blocktime": 0,
    "txid": "8502f4a2edd23ea55bb9e59948714001266d43828f73afc31993f6988d672db4",
    "walletconflicts": [],
    "time": 1454334587,
    "timereceived": 1454334587,
    "details": [
    {
    "account": "",
    "amount": -0.5,
    "category": "send",
    "fee": 0.99999,
    "vout": 0
    }
    ],
    "hex": "0100000001935a6b7930244123f0b28ecd34bb290ed8a3ff32390a0866ac3e8fc30b38
    46100000000000ffffffff0198ecfa020000000000001976a914359b6bc413148f18e60464e660b6
    b45df695debb88ac000000000000000001ffffffffffffffff00000000ffffffff6b483045022100
    f7641f87c24f7d41e50a13ffba40bfa075fc99f3af1d3a7f05dba9051ca0e99c022029958ffb525f
    624b9956d4c944a675212080a289316156359c8a29dcff6c49e8012103da5d8f2bf30ebfb95a2d11
    f182c7f7d6660d1fa2dac26d9f0218f6c6e5464b59"
    }

    Also i don't understand the numbers in the tx. I had a balance of 0.5 and set the fee to 0.00001
    I sent 0.49999, but the tx shows:
    amount: 0
    fee: 0.99999
    amount: -0.5 (again)
    fee: 0.99999

    Anybody who can clarify this?
     
  17. jrick

    jrick Member
    Developer

    Jan 4, 2016
    88
    81
    Male
    I can't give any insight about why the transaction hasn't been mined, but the bug for how the fee is reported for the gettransaction RPC has been fixed.
     
  18. WilderX

    WilderX New Member

    Dec 17, 2015
    13
    2
    Male
    Hey Sir or any dev can you look at my issue (messages in this thread) and as Mr. Wolf says there seems to be a bug in the cgminer other cards finding the same shares? Can you confirm this bug and could someone fix it before launch?
     
  19. Emilio Mann

    Emilio Mann Full Member
    Advocate (Facebook)

    Jan 9, 2016
    188
    162
    Male
    Hey all!

    The CEO of bleutrade exchange found the following bugs and asked if will be released a new version with the fix before the official release in feb/8?

    bugs:

    list transactions
    1 - fee: format is in scientific notation, decimal is correct
    2 - list order is incorrect, the most current to the oldest, must be the oldest to the most current
    3 - I can not list transactions with parameters: ./dcrctl --testnet --notls -u user1 -P passTest1 --wallet listtransactions "test" count=10 from=0 includewatchonly=false
    listtransactions command: parameter #2 'count' must parse to a int (code: ErrInvalidType)
    Usage:
    listtransactions ("account" count=10 from=0 includewatchonly=false)

    getaddressesbyaccount does not work to list all the untitled accounts addresses in the wallet
    getinfo
    1 - the balance is zero, but i can send coins
    2 - some formats are in scientific notation

    sendtoaddress does not send correctly, it works better when the previous transaction has been confirmed, have not figured out the real reason for the malfunction
    walletpassphrase - sometimes it takes more than 20 seconds, unnecessarily
     
    tacotime and David like this.
  20. jcv

    jcv Full Member
    Developer

    I think most of these bugs have been reported on github (and few already fixed). I'll try to match them up to the github issues to see what new things you've got.
     
    David likes this.

Share This Page