[ANN][APT] Aptcoin★ASIC Resistant Scrypt In-Motion(NM) w/Aptcurve Retargeting

[q327K091]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

[1715261586]

1715261586

[1715261586]

1715261586

[mig6r]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

Same problem for me

[q327K091]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

Same problem for me

interesting coin , if it works of course   looking at the white paper its going to be quite hard to code GPU miner for it, ASIC next to impossible

it's funny, we all gravitate towards the same solutions... anyways.. come back later and retry wallet, he (dev) needs to build in difficulty adjustment algorithm

[Singman33]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

What is the problem ? Will you post each time a block take one hour or more to resolv ?
Use "aptcoind getmininginfo" the view the hashrate, and I see no reason why you should worry for a block to take 1, 2 or 3 hours to be found.
Currently block 1792, nFactor to 13 (+1 from previous hour).

[aptcoin]

For CPU miner, try :
minerd.exe --url=http://xx.xx.xx.xx:12946 --userpass=user:password
for window or
minerd --url=http://xx.xx.xx.xx:12946 --userpass=user:password
for linux.
Algo to Scrypt-NM by default.

BTW, i will study theses sources to see how you get nFactor from getwork.

This is correct, thanks!

An example of the alternate syntax is:

minerd -o http://localhost:19246 -O rpcuser:rpcpass

[hybrid2]

Dev after how much confirmations immature is confirmed ?

    {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 36,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

Also about mining i am mining at port 30200 with that config:

rpcuser=root
rpcpassword=password
addnode=199.127.225.232
addnode=199.127.225.195
addnode=199.127.225.191
addnode=199.127.225.164
addnode=50.7.47.93
rpcallowip=192.168.1.*
rpcthreads=10
rpcport=30200
server=1
daemon=1

[q327K091]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

What is the problem ? Will you post each time a block take one hour or more to resolv ?
Use "aptcoind getmininginfo" the view the hashrate, and I see no reason why you should worry for a block to take 1, 2 or 3 hours to be found.
Currently block 1792, nFactor to 13 (+1 from previous hour).

it's wallet syncing that I am referring to.. ok let me try to run CPU miners for few hours and network to sync up at some point, a strange way to operate but ok

indeed, Sun Aug 24 12:52:05 2014 1792 block was last found

find it all a bit funny + this interesting algorithm , so ok, lets see, difficulty level is 0.23203980, but if blocks move so slow does not mean a thing

---

ok engaged CPU miners one of the cores is indeed reporting nFactor 13

thread 2: 2064 hashes, 0.41 khash/s [n_factor=13, hpb=3730623783]

temperature went up (naturally) we shall see , will let it run despite wallets not synced (not sure how this will work)

and that's it for now we revisit in 3 hours (many cores are at work)

-- also this but since generate is false as CPU miner is used externally, everything is setup right

./aptcoind getmininginfo
{
    "blocks" : 1792,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.23203980,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 546089,
    "pooledtx" : 0,
    "testnet" : false
}

--

in 3 hours if block not found at the # of cores I have and general machines speed I will have to turn off operation (unfortunately) till core of this coin is fixed

[aptcoin]

Dev after how much confirmations immature is confirmed ?

    {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 36,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

Also about mining i am mining at port 30200 with that config:

rpcuser=root
rpcpassword=password
addnode=199.127.225.232
addnode=199.127.225.195
addnode=199.127.225.191
addnode=199.127.225.164
addnode=50.7.47.93
rpcallowip=192.168.1.*
rpcthreads=10
rpcport=30200
server=1
daemon=1

Coinbase Maturity (i.e. blocks that are mined) change status after 100 confirmations (same as bitcoin/litecoin).

You can mine on any port you want by specifying, but that's non-standard.  12946 is the default port.

[q327K091]

stuck at 1785  (last block processed 2 hours ago) anyone has working nodes ? thanks

What is the problem ? Will you post each time a block take one hour or more to resolv ?
Use "aptcoind getmininginfo" the view the hashrate, and I see no reason why you should worry for a block to take 1, 2 or 3 hours to be found.
Currently block 1792, nFactor to 13 (+1 from previous hour).

it's wallet syncing that I am referring to.. ok let me try to run CPU miners for few hours and network to sync up at some point, a strange way to operate but ok

indeed, Sun Aug 24 12:52:05 2014 1792 block was last found

find it all a bit funny + this interesting algorithm , so ok, lets see, difficulty level is 0.23203980, but if blocks move so slow does not mean a thing

---

ok engaged CPU miners one of the cores is indeed reporting nFactor 13

thread 2: 2064 hashes, 0.41 khash/s [n_factor=13, hpb=3730623783]

temperature went up (naturally) we shall see , will let it run despite wallets not synced (not sure how this will work)

and that's it for now we revisit in 3 hours (many cores are at work)

-- also this but since generate is false as CPU miner is used externally, everything is setup right

./aptcoind getmininginfo
{
    "blocks" : 1792,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.23203980,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 546089,
    "pooledtx" : 0,
    "testnet" : false
}

--

in 3 hours if block not found at the # of cores I have and general machines speed I will have to turn off operation (unfortunately) till core of this coin is fixed

nothing, 0 zip, nada block 1803 , exit, is this true: Block time – 5 minutes or a joke by developer to eat up people's computing  resources 

[Singman33]

In the meantime....

Code:

$ aptcoind getmininginfo
{
    "blocks" : 1807,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.15469320,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 446809,
    "pooledtx" : 0,
    "testnet" : false
}

Yep, block 1807. But note that global hashrate is decreasing regulary since yesterday, nFactor is now 12.

[GimmeMyCoins]

Has anyone compiled the aptcoin cpuminer for windows?

[sukamasoto]

very easy to do mining
when it will be released in exchange

[Singman33]

Has anyone compiled the aptcoin cpuminer for windows?

I have but wont release the download address publicly. Send me a PM if you want.

[hybrid2]

Dev after how much confirmations immature is confirmed ?

    {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 36,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

Also about mining i am mining at port 30200 with that config:

rpcuser=root
rpcpassword=password
addnode=199.127.225.232
addnode=199.127.225.195
addnode=199.127.225.191
addnode=199.127.225.164
addnode=50.7.47.93
rpcallowip=192.168.1.*
rpcthreads=10
rpcport=30200
server=1
daemon=1

Coinbase Maturity (i.e. blocks that are mined) change status after 100 confirmations (same as bitcoin/litecoin).

You can mine on any port you want by specifying, but that's non-standard.  12946 is the default port.

   {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 110,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

And ? Why they are not confirmed yet ?

[aptcoin]

Dev after how much confirmations immature is confirmed ?

    {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 36,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

Also about mining i am mining at port 30200 with that config:

rpcuser=root
rpcpassword=password
addnode=199.127.225.232
addnode=199.127.225.195
addnode=199.127.225.191
addnode=199.127.225.164
addnode=50.7.47.93
rpcallowip=192.168.1.*
rpcthreads=10
rpcport=30200
server=1
daemon=1

Coinbase Maturity (i.e. blocks that are mined) change status after 100 confirmations (same as bitcoin/litecoin).

You can mine on any port you want by specifying, but that's non-standard.  12946 is the default port.

   {
        "account" : "",
        "address" : "AXPEEnA9WLamNzarxVMhHfGfzWB4v7Ad2w",
        "category" : "immature",
        "amount" : 42.00000000,
        "confirmations" : 110,
        "generated" : true,
        "blockhash" : "f1d644f887e4c2b245a67206f264439b37968586d668da09902aae4a50623495",
        "blockindex" : 0,
        "blocktime" : 1408718115,
        "txid" : "774f633b75b7071fdbd5385f7fdcf6ad103e7a5531e61d59998c7dfe26cd2afd",
        "normtxid" : "aa3fb1a5c6c3c620ffa2d28e80ee2765d1275af8eae9cb43427912cc0aaf478f",
        "time" : 1408718115,
        "timereceived" : 1408718375
    }

And ? Why they are not confirmed yet ?

The default client does not consider them confirmed until 120 confirmations.  That's different than the network/protocol limit of 100.

[aptcoin]

The question that anyone who's been watching has is: What's up with the block generation times?

In short, it's off. But we're in the process of testing a change that should help fix this by changing how we re-target difficulty. The good news is that we hope to see more stable block generation times. The bad news is that it's not only experimental, but it's also going to require a mandatory update to all wallets.

Since there are no pools or exchanges yet, it's up to YOU to update when the new wallet is released.

Thank you to everyone who has supported us thus far, we'll continue innovating to make sure this coin reaches the moon.

[Singman33]

The default client does not consider them confirmed until 120 confirmations.  That's different than the network/protocol limit of 100.

Code:

"account" : "",
        "address" : "AXjeZskVxRgPFSfGqRsMZvmfHsBi3Vjew9",
        "category" : "generate",
        "amount" : 42.00000000,
        "confirmations" : 120,
        "generated" : true,
        "blockhash" : "bfc6b881c078512e4c1ad2cb4d5e30f1e234c600fa1995aefcdb37cf2b352945",
        "blockindex" : 0,
        "blocktime" : 1409076489,
        "txid" : "c6ad4ebd4c71bed8ed2020e7b4e3627618e04af399f6ef45585ccfe90f1ebb10",
        "normtxid" : "f0abed1793d24198c72817505547f0dabe88c0d8015abe4995e029e9811afd0c",
        "time" : 1409076489,
        "timereceived" : 1409076492

[SpiderCoin]

Finding blocks again  such happy!!!!!!!!!

[radus]

this coin has literally no value until it hits an exchange - please make that happen

[tiger5056]

interesting one but definitely need exchange.