Trying to figure that out, I've been wondering the same thing about all that extra hashrate. Doesn't seem to be coming from anywhere. Maybe it's one of those Chinese solo miners with that supposedly working X11 FPGA? There was a picture floaing around with something like 25 MH from a single one.

Your wallet has nothing to do with it. http://mag.pool.pe/ has the highest network hashrate if you want to get paid faster, put you'll be paid less.

P2pool is only like 30 mH, the total hashrate for this coin is several tens of gH. So it's likely chances of finding a block is very low.
And yes, it requires a block to be found in order to get payment.

Darn man, might have some trouble cause there's some mega pools -- try and get word out about the coin to get people and come to your pool.

Stratum and frontend are both online for me?

Pool owners, please check for latency. You should be using P2P, not RPC. P2P notifications are very streamlined!

ATTENTION MPOS POOL OWNERS:
$config['getbalancewithunconfirmed'] = true;
SHOULD BE
$config['getbalancewithunconfirmed'] = false;

Also, our block explorer got DDoSed to shit so that will not be around for a little bit.

Working with minerpools as we speak on the issue. Should be done soon.

It's fucked up, man. Try messaging him ask him if he can shut registrations?


Wallet is fine, just confirmations that are being an issue.


Yes, they are, he's working on a coinbase issue with confirmations/maturity. He messaged me a few minutes ago. BTW the issue is, it's set at 30 so the confirmations are not the same timing as MPOS.

Everything should be working now, a small delay (6 minutes) because Windows wallet mix-up. Mac wallet confirmed working.


Sorry to hear that. My sincere apologies for the wallet mixup.


I don't have a miner ready, unfortunately. Also, these blocks are low-value because difficulty is low.
My address is mHkSBvZHxSBV98RsCfBxpjLZF2MxdiC7z1


Please put the CONF file in your AppData directory first. If you still have problems, please message me with PM.


I made a mistake, I realize. But it was caught early thanks to you guys! So everything is back on track. BTW those first blocks were forked anyway so the Mac miners didn't receive block rewards.


Hey now...


THANK YOU! Someone actually doing something besides shitting on everything.

This is the updated wallet: https://mega.co.nz/#!HEkTibRK!aYpMGbl87nDbX-Lymc3gsomEsP65Hv7n3hR503rcCg0

OP has been updated with correct link.


MarkCoin was a pet project, and the prototype. The binary was outdated. It has now been updated.


MRK was the prototype for MAG. The wallet has been updated.


My team also made MRK, yes. But it was very basic and only used scrypt.

Hey man, you're awesome. Just wanted you to know that.


I wasn't aware page count was a direct measurement of crypto importance/quality


Last time I contributed to the development of a crypto, they did that -- and someone promptly cracked the ZIP's password with a cluster. Not taking that chance, sorry

Well, hopefully, this coin can change your mind!

Think it's a bit too late to be changing entire algorithms, haha. NIST5 does sound cool, though. Any specific advantages you had in mind?

So, I've been doing some dev work and I'm a little stuck. I managed to change most parameters of bitcoinj to match my coin -- merkel hash, genesis hash, the works!

However, under NetworkParameters, I can't seem to crack the second hex value.

I've determined as much that the first is simply the scriptSig from the genesis block, so difficulty bits + timestamp message.

Here's a snippet of the try catch around it:

try {
            // A script containing the difficulty bits and the following message:
            //
            //   "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"
            byte[] bytes = Utils.HEX.decode
                    ("04ffff001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f7 2206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73");
            t.addInput(new TransactionInput(n, t, bytes));
            ByteArrayOutputStream scriptPubKeyBytes = new ByteArrayOutputStream();
            Script.writeBytes(scriptPubKeyBytes, Utils.HEX.decode
                    ("04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef3 8c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f"));
            scriptPubKeyBytes.write(ScriptOpCodes.OP_CHECKSIG);
            t.addOutput(new TransactionOutput(n, t, FIFTY_COINS, scriptPubKeyBytes.toByteArray()));
        } catch (Exception e) {
            // Cannot happen.
            throw new RuntimeException(e);
        }

How does one even find the second value? It appears to be a public key of sorts.

I'd honestly be more flattered than anything if I got anything close to that, heh
But we ran it with the lowest difficult 256 bits could support and put it through a few MH and it just responded instantly. Scaled up, I'm confident it'll perform similarly in the range of a few hundred MH. The key is not absolute hashpower, it's the relative increase. Calculations fall based on the percentage spike. So going to 2 MH to 4 MH is the same as 10 MH to 20 MH. Adjustment is going to slow the price change significantly enough that stability will be basically insured.

I think you meant : "this coin will survive... a matter of days "
But point taken, we'll see huh