Topic: [ANN][ARG] Argentum || Secure. Rare. Fast. || Randomized reward system commodity - page 6. (Read 19439 times)

I don't understand.  How is cryptopools wrong?

I don't think Altexplorer has been updated.

all coins which were mined above the 426,606 block aren't legit. It means no reason to mine Argentum at this moment till Baritus update the wallet.

and



Where my money!!!!?

That's the reply I was looking for.  Thanks man!

Updating cryptsy tonight

Cryptsy support said
Thank you for responding.
The official block count we have is at 426,606 based on this link: altexplorer.net/chain/Argentum

Just sent a test transaction to Cryptsy and it never showed up.  Would a support ticket help?

cryptopools showing 442600+

442582 at two different wallets

Which block is everybody on?

Cryptsy probably hasn't patched their wallet yet, so they can't get the new blocks.  Once they patch they should sync to the current longest chain and the new transactions should come in.

what happened to Argentum? difficulty 0.01, pools do not work

Hey guys,

I have the same blockchain that is passed block 426490, but I think whatever coins generated after block 426490 are not accepted by exchanges like cryptsy. They are probably "stuck" on blockchain with block "426490".

The "working" blockchain I could find is here: https://altexplorer.net/chain/Argentum and it is also on a latest block of 426490.

Now, I wounder if blockchain passed 426490 is legit.

There are more peers with this block vs. newer. what do we do?

[my@srv /d2/altcoins]$ argentumd -conf=argentumd.conf getpeerinfo
[
    {
        "addr" : "162.243.226.39",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401148940,
        "conntime" : 1401102131,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "46.119.36.123",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401149327,
        "conntime" : 1401102131,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "54.201.183.106",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401149025,
        "conntime" : 1401102131,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "192.99.44.51",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401149191,
        "conntime" : 1401102131,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "72.78.100.9",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401149548,
        "conntime" : 1401102210,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "89.29.69.214:3326",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401150640,
        "conntime" : 1401110806,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 434143,
        "banscore" : 0
    },
    {
        "addr" : "86.30.167.243:36203",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401150581,
        "conntime" : 1401124171,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    },
    {
        "addr" : "192.99.135.85:49393",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401150639,
        "conntime" : 1401125395,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 434569,
        "banscore" : 0
    },
    {
        "addr" : "176.9.63.136:16543",
        "services" : "00000001",
        "lastsend" : 1401150604,
        "lastrecv" : 1401150639,
        "conntime" : 1401126166,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 434589,
        "banscore" : 0
    },
    {
        "addr" : "81.99.241.164:34902",
        "services" : "00000001",
        "lastsend" : 1401150639,
        "lastrecv" : 1401145298,
        "conntime" : 1401144684,
        "version" : 1030000,
        "subver" : "/ARG V1.2:1.0.3/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 426490,
        "banscore" : 0
    }
]
[my@srv /d2/altcoins]$

[my@srv /d2/altcoins]$ argentumd -conf=argentumd.conf getinfo
{
    "version" : 1000300,
    "protocolversion" : 1030000,
    "walletversion" : 60000,
    "blocks" : 435360,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 0.06793071,
    "testnet" : false,
    "keypoololdest" : 1392347456,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}
[my@srv /d2/altcoins]$

how do I force my daemon not to drift away from "main" chain that currently stuck on block "426490"?
Am I lost?

ARG's code has many major differences. It would take much longer than I have available to do the port. That's why I am looking for a solution. I contacted Alpha, Argentum's dev, and asked him to take a look.

well done!

This is a reasonable plan, to maximize the convenience
 

MyWl.lt never had the database problem, but I implemented the fix and re-synchronized the block chain. Here's the current status (01:17 PST):

"blocks" : 433542,
"connections" : 16,
"difficulty" : 0.06581028

Since both block explorers are down can ppl please post what block you're at, I want to know if it's safe to reenable this..

i handed the solution to you on a golden platter. Upgrade arg to a newer version of the btc/ltc codebase supporting leveldb and then the issue will be fixed

Ahmed