It found a sha256d hash with the right amount of zero bits. It thought it was valid because it checks sha256.
Valid means the number of zero bits matched the difficulty target.
The pool and coin would reject it immediately as it was done with the wrong proof of work. It was an invalid hash with the right amount of zero bits.

You can conclude that cgminer worked with your sha256 asic, and if it had been a sha256 coin it would have worked.

You will nee a cpu (slow), or a gpu (medium), or a scrypt-asic (fast) for this scrypt coin.

I have pm'd him also, my own "pending" and "total" balance has changed many times. I do not know how they are calculated, but it does not say estimate.
Since it his business I am sure ethought will confirm, and hopefully correct any errors if errors are present.

24 hour earnings are estimated, and depend on the other miners hashing power, and the pools success at finding blocks on the network. It will change often and means little when a coin is young.

For network health, we should look at some more pools.
I would like to avoid multipools and pools which auto convert to other currencies.
Perhaps we should research and approach some mining pools.

We should also create the IPM pool soon, it is a 5% donation but that goes to the foundation for the future of the coin and strengthens the value of any coins earned.

All fiat is debt. They were originally promissory notes, "to pay the bearer on demand" an amount of gold. The link to gold was removed. They are just worthless IOUs.

Use http://ck.kolivas.org/apps/cgminer/old/3.7/ on linux
That is how it should run, but you were using sha256 which is why you got banned.


In IRC SecondPlace_ writes: "so how many coins are there in total? and is anyone selling some?"
To answer the first question: Total Supply: ~27.58 million coins (27,579,894.73108000 to be exact).
You can read about all of these things on the wiki


The difficulty will jump again soon to maybe 45.

Yes, you can open "help > debug window" then type "setgenerate true" to turn on mining, or "setgenerate false" to turn it off.
you can always mine from startup by setting "gen=1" in bitmark.conf

with the network hashrate, it might not be worth it.


where username and password are rpcuser and rpcpassword from your bitmark.conf

you need to use cgminer 3.7.2 or earlier for scrypt support.

Please contact miningpool.co support for this. Perhaps there was an orphan block?

Remember that Bitmark takes 721 confirmations to mature, which is normally 1 full day. The rationale for this decision can be found on the wiki.

Update

1. We have successfully launched Bitmark.

2. The difficulty has already re-targeted twice by the maximum amount, currently it is 16.

3. Here are some links

• A Bitmark Block Explorer on cryptexplorer.com, thank you
• A Bitmark mining pool at miningpool.co, thank you
• A Bitmark sub forum at cryptocointalk, thank you

I would like to thank everybody for their kind words, excellent discussion, helpfulness, donations, and support.

Today was a good day, it was only the foundation, tomorrow our work to earn value by being useful and easy to adopt begins.

Bitmark Foundation BTM donation address: bQmnzVS5M4bBdZqBTuHrjnzxHS6oSUz6cG

It was scrapped and replaced with a donation based bitmark foundation.

There is also to be a long running IPM, voluntary and entirely optional to raise funds for the foundation.

BTC Donations will be used in line with the IPM Proposal, tl;dr: used to lease mining rigs to support the network, 5% of the generated bitmarks would go to a foundation, 95% distributed to investors. This has extra benefits for network health and miners.

Our target is 0 BTC and 70,000 BTM. The BTMs in the foundation will not be touched until after 2015-07-13, longer if we can. We encourage donations of BTM, it will ensure this project lives long and can achieve what we plan.

This week we will create an automated IPM pool, each donor will be able to associated a BTC address with a BTM address, any donated BTC will be spent on leased miners up to 35% of the network hashrate, the BTM produced will distributed to donors according to the amount they donated. 5% will go to the foundation, to be locked for future development.

Development over the first year, or longer if possible, is voluntary.

The Bitmark Foundation
./bitmarkd sendtoaddress bQmnzVS5M4bBdZqBTuHrjnzxHS6oSUz6cG 200 "the bitmark foundation"
d3c1b75d68333d95c8e1c9db4f4ba5b4719bce97008fe73c0cfb5f551d7f3b2d

I have sent the first 200 coins to the bitmark foundation address: bQmnzVS5M4bBdZqBTuHrjnzxHS6oSUz6cG

The difficulty has jumped 4x already.
The network is at 2.5GH/s.

I did not expect this. These coins have no value, yet.

Thank you everybody, I think we can say we have launched successfully.

rpcallowip = allow JSON-RPC connections from specified IP address
server = accept command line and JSON-RPC commands
daemon = run in the background
rpcconnect does not exist
listen is enabled by default

rpcallowip can accept wildcards, for example *, 192.*, 192.168.*, 192.168.0.*

So we can conclude that this should work.

Yes, that is all you need to do.

There is an issue with stratum-mining documented here: https://github.com/Crypto-Expert/stratum-mining/issues/349

It creates blocks incorrectly until the height is above 16. I had hoped this would not be a problem.

I have informed miningpool.co, and used funds from the most recent donation to hire a miner which will use getblocktemplate on bitmarkd, it is going to generate the first 16 blocks,

We are at height=7 as I write this.

After block 16, miningpool.co will work properly.

To confirm, this is a bug in stratum-mining, not bitmark or miningpool. The bug had not been spotted before because no other coins appear to use a new codebase with v2 blocks from the start.

edit your bitmark.conf to include


and then use those details in cgminer to connect to your node on port 9266.

wow, yes:
"addr" : "174.36.9.130:9265",
"addr" : "173.192.30.99:9265",
"addr" : "2.82.42.33:53906",
"addr" : "92.210.23.27:56630",
"addr" : "144.76.64.123:9265",
"addr" : "90.156.62.44:57422",
"addr" : "110.255.184.251:9265",
"addr" : "128.90.15.164:58628",
"addr" : "84.24.204.134:51074",
"addr" : "79.103.61.218:9265",
"addr" : "68.59.115.9:50448",
"addr" : "176.104.121.135:65095",

I think you may be the only one not auto getting nodes.

Here.
The announcement in 2 hours is already prepared and tested cross compiled releases for all 32/64bit platforms are ready to download immediately upon release

I have no idea, the difficulty for the first 720 blocks is set to 1, which needs about 30MH/s, we may get more or less.

If you are planning to rent some hashing, please try to choose a lower amount for longer, rather than a high amount for a short period of time.


As far as I know there will be one from miningpool.co very quickly.

Hired rigs will work with your own bitmark instance, as long as they support solo mining with getblocktemplate.

No pools have been organized to be setup, as that would be against the principals of the project (no hype, natural adoption and all).

miningpool.co have stated that they will be adding support when bitmark launches, so that is one for sure.

I would say could instead of should.

If putting money towards the IPM, then 95% of the coins you would generate will be sent to you, with 5% for the foundation.

Or you can mine yourself, and if you like donate any percentage to the foundation.

Until we have documented or created a way to keep track of things for the IPM, it may be better to just mine yourself, and donate to the Bitmark Foundation BTM address if you like. There is no rush, and the first bitmarks mined cannot be sent until 720 blocks later, roughly one day.

The release is tested and ready.

You can also solo mine, all common scrypt miners have been tested, they are all supported

I will be solo mining, we do not need a pool, although a few will be nice to have.