Topic: NOMP pool Blocks Pending Problem (Read 1164 times)

to add necromancy on top of necromancy....

For anyone coming to this thread from search (forum or goggle):
means that the block was orphaned and NOMP and its 12 bajillion forks are poor at handling such things (especially if it was orphaned due to a reorg like the OP chain is prone to experience).

PEOPLE LIKE THIS ARE WHY WE HAVE NO PROGRAMMERS, NO POOLS, AND NOT AS MUCH DECENTRALIZATION OR ACCEPTANCE.

I know this is a 3 year grave dig but I was searching for related information and it pissed me off that much I had to recover my password to post. This happens WAY too often in the crypto and dev spheres.

We want to think this is "our" thing and no one elses... Well it isn't only "ours", and we want it to survive...

You should NEVER discourage a noob from learning to code, mine, or set up a pool. people like YOU are the reason we have so few pools.

If pool operators don't learn, we get stuck with Antpool having 75% share or whatever. Without an in-flow of new dev's and pool operators, CryptoCurrency is DOOMED.

Think about that next time you give someone hell for asking about CPU mining or pool issues.

We all have to start somewhere. Discourage a noob today, hurt crypto tomorrow.

I hope you left the crypto community (kano, others), we don't need you here.

Good day!

Firstly ... you run alt coin pools ... why are you asking here?

Secondly, find whoever wrote it and their thread and ask them ...

This is one of the reasons why I say people who run pools should know what they are doing ...
If you run a pool it's your job to keep it running and working, not stop and then say "hey can someone help me, the pool is stuck"
I wonder why anyone would mine on a pool run by someone who can't maintain it when a problem happens ...

this is the gettranaction result of one of the block in question 396733

{
    "txid" : "6741784a4955589b78230ce6dbeaa59ced1c040c061aeb10f0d5cd1c936b2548",
    "version" : 2,
    "time" : 1428662732,
    "locktime" : 0,
    "tx-comment" : "https://github.com/zone117x/node-stratum",
    "vin" : [
        {
            "coinbase" : "03bd0d06062f503253482f04cda927550830000014230000000d2f6e6f64655374726174756d2f",
            "sequence" : 0
        }
    ],
    "vout" : [
        {
            "value" : 49.50000000,
            "n" : 0,
            "scriptPubKey" : {
                "asm" : "032ce806158599155c0403a818c8c06b3a5b78705b309f273e3a31d5dc5030a9db OP_CHECKSIG",
                "hex" : "21032ce806158599155c0403a818c8c06b3a5b78705b309f273e3a31d5dc5030a9dbac",
                "reqSigs" : 1,
                "type" : "pubkey",
                "addresses" : [
                    "Ni6Ajbp2G5Q3cchzL1aDH61qy8PKJH5KtA"
                ]
            }
        },
        {
            "value" : 0.50000000,
            "n" : 1,
            "scriptPubKey" : {
                "asm" : "OP_DUP OP_HASH160 f34091494b11e93fc6bc449746ef5064cfde9005 OP_EQUALVERIFY OP_CHECKSIG",
                "hex" : "76a914f34091494b11e93fc6bc449746ef5064cfde900588ac",
                "reqSigs" : 1,
                "type" : "pubkeyhash",
                "addresses" : [
                    "Ni6Ajbp2G5Q3cchzL1aDH61qy8PKJH5KtA"
                ]
            }
        }
    ],
    "amount" : 0.00000000,
    "confirmations" : -1,
    "generated" : true,
    "blockhash" : "00000000000004112a25ebb5f9ef689f0517351158b76b8ce5a9734cfc314e1a",
    "blockindex" : 0,
    "blocktime" : 1428662789,
    "txid" : "6741784a4955589b78230ce6dbeaa59ced1c040c061aeb10f0d5cd1c936b2548",
    "time" : 1428662762,
    "timereceived" : 1428662762,
    "tx-comment" : "https://github.com/zone117x/node-stratum",
    "details" : [
        {
            "account" : "",
            "category" : "immature",
            "amount" : 50.00000000
        }
    ]
}

Hello guys, hopefully someone can shed some light on my situation.
I have a couple of pools set up using NOMP.
eupool.ozbtcminers.com & pool.ozbtcminers.com
The problem I am having is that every now and then when a block is found, it obviously goes into the "Block Pending" stats until confirmed.
What seems to be happening is after a certain amount of time the block isn't being confirmed (in this case the coin in question is eMark DEM which needs 100 confirmations)
I get the transaction details using emarkd and it displays the details of the block etc. The block that stay as pending are showing -1 confirmations.
and are not maturing. I am assuming these blocks have not been accepted to the blockchain. My real question is how do I either resubmit these blocks so they can be either orphaned or accepted on the block chain, and not continue to show as pending on my stats.
Regards
Troy

PS this is one of the blocks in question on the DEM eMark block explorer
http://crypto2.net/dem/block.php?chain=1&hash=515e7d47782976e83a863c1fdb2d1624b1811c07afe43854033b28eaa72280ea

and below is my gettransaction of the same block