Give it awhile.  This coin has a 256 second block time, and steam is still building to achieve that.  Currently 63 blocks have been found.  The rate is improving as more people join in but we just don't have enough yet to achieve target block times.

Please let any of your idle CPUs work on this coin.  I'm personally expecting to mine blocks per week, not blocks per minute.  This coin is for those interesting in putting their otherwise useless (for Bitcoin) or virtually useless (for Litecoin) or marginally useful (for other scrypt coins) to good long term use.

As with any other coin, the most profitable way to mine is solo mining.  That is also currently about the only way TO mine this coin.  We have not found a public n-scrypt miner that can handle N=16, although we have not tested them all.  Technically: Most current miners will need to change their scratchpad allocation to heap based instead of stack based.  Its not hard to do, but the 16MB scratchpad associated with a N of 16 eats through stack space pretty darn quick.

Note that since the scratchpad is 16mb in size, this coin is highly influenced by the Memory architecture of the system and number of cores more than the speed.  Things like L2 cache or Intels "Smart Cache" are overwhelmed by the coins memory reference patterns.  THAT is why the coin is ASIC proof and GPU difficult.  (All currently announced, much less delivered, ASICs can only handle an N of 14 (sometimes marketed as N of 16384 but that is 2^N, not N - not that marketing folks care.))

This is the coin to mine if you want to fight back against large Corporate Data Centers talking over mining.  Help us help you!

Hope you set N=16 for your miner.  Would also love to know which miner your using, most we tested crash with a stack overflow running with that high of an N.

Those mining that we are aware of are all using the coin wallet to do so (both Windows and Linux)

Welcome back to Independent Mining!

This coin is for everyone with a normal PC or server wanting to mine without being obliterated by Corporate Data Center ASIC based mining!

What is IMAcredit?
----------------

IMACredit is focused on creating a truly ASIC free and GPU resistant crypto coin.  It accomplishes this goal by utilizing the N-Scrypt algorithm with a much bigger N than any other coin to date.  At launch, N=16.  This is 2 higher than the latest ASIC technology will support and high enough that current graphic miners will crash with stack overflows.  e.g.  This is a CPU only targeted coin.

What is the Independent Miners Alliance?

Well, honestly, its the name of one of the four factions in the apparently defunct game "The Crypto Void" by 1BillionHash.  However the name also reflects the goal of having a coin that is independent of the big data center driven coins like Bitcoin and the popular Scypt based coins.

Key Stats:

    Launched on 9/1/2014
    256 second (~4.3) minute block targets
    16 coin payout per block
    No half life
    subsidy constant for life of coin
    ~92B coins (limit of 64 bit math)
     Every block to retarget difficulty with Kimotos Gravity Well algorithm
    ZERO pre-mine, ZERO special blocks, no IPO, nothing hidden,  RAID RESISTANT

As mentioned on the Home page, IMACredit is designed to be CPU bound - a coin for the masses.

Due to its high N factor, each hashing process will require 16MB of memory.  Nothing significant for today's PCs, but an absolute killer for ASICs.  Early testing has also found IMACredit to resist GPU usage, with sgminer crashing due to a stack overflow within minutes.  This testing also shows substantially smaller khash rates than most have gotten use to:  Where bitcoin ASICs are measured in GigaHash, and scrypt ASICs are measured in 10s or 100s of MH, and GPUs generally deliver 100s of KH, IMAcredit's wallet will hash in the 10-100KH range.

Let us be perfectly clear:   This is a coin for the masses, designed to require large numbers of users to meet its block time target.  No handful of users will be able to dominate this coin.    Until N-Scrypt mining code like sgminer implement fixes GPUs and Pool mining will not make sense.  Pool mining may never make sense - this code is designed to be run from the wallet!

Hashing Algorithm:  N-Scrypt, initial N=16.  Codebase tested through N=20 representing 7 generations of ASIC's to come and expected to work at higher Ns.  (for the coders out there:  Heap based scratchpad allocation vs. the typical Stack based which would break at N=15)

Difficulty Algorithm:  Kimoto Gravity Well, with Time Warp Patch
Source:  https://github.com/IMACredit/imacredit
Windows Wallet:  http://www.mediafire.com/download/1vzyh5h0dg5bljh/imacredit-qt.exe
    If you do not setup a imacredit.conf file, please make sure you use the Console window and "setgenerate true".
MacOS Wallet:  not currently available
Linux Wallet:  Build from Github source for maximum compatibility

Block Explorer:  <needed>

Pools:  http://mpos.imacredit.org (stratum+tcp://mpos.imacredit.org:10052) - This is a VERY basic, lightly maintained pool.  We REALLY REALLY recommend doing local machine mining.   If you locally mine, give it time:  expect to find blocks per week, not blocks per hour.


Ports:
        Listen:  64097 (54097 for testnet)
        JSON-RPC:  64096 (54096 for testnet)

Sample Configuration file (completely optional for Windows users)
       rpcuser=<yourname>
       rpcpassword=<some very random long password>
       listen=1
       gen=1

Like all high quality coins, IMACredit maintains an active DNSSEED network.  You should NEVER have to specify addnodes.  All wallets should work upon launching.

Social:   IRC Freenode:  #imacredit  

Website: http://www.imacredit.org

Other information:

IRC is NOT used by the codebase for anything (unlike many coins)

UPnP is disabled for your protection!

Development team:  The same folks that brought you YACCoin and 1Credit.

Cassey

Welcome back to Independent Mining!

This coin is for everyone with a normal PC or server wanting to mine without being obliterated by Corporate Data Center ASIC based mining!

What is IMAcredit?
----------------

IMACredit is focused on creating a truly ASIC free and GPU resistant crypto coin.  It accomplishes this goal by utilizing the N-Scrypt algorithm with a much bigger N than any other coin to date.  At launch, N=16.  This is 2 higher than the latest ASIC technology will support and high enough that current graphic miners will crash with stack overflows.  e.g.  This is a CPU only targeted coin.

What is the Independent Miners Alliance?

Well, honestly, its the name of one of the four factions in the upcoming game "The Crypto Void" by 1BillionHash.  However the name also reflects the goal of having a coin that is independent of the big corporate data center driven coins like Bitcoin and the popular Scypt based coins.

Key Stats:

    Launched on 9/1/2014
    256 second (~4.3) minute block targets
    16 coin payout per block
    No half life
    subsidy constant for life of coin
    ~92B coins (limit of 64 bit math)
     Every block to retarget difficulty with Kimotos Gravity Well algorithm
    ZERO pre-mine, ZERO special blocks, no IPO, nothing hidden,  RAID RESISTANT

As mentioned on the Home page, IMACredit is designed to be CPU bound - a coin for the masses.

Due to its high N factor, each hashing process will require 16MB of memory.  Nothing significant for today's PCs, but an absolute killer for ASICs.  Early testing has also found IMACredit to resist GPU usage, with sgminer crashing due to a stack overflow within minutes.  This testing also shows substantially smaller khash rates than most have gotten use to:  Where bitcoin ASICs are measured in GigaHash, and scrypt ASICs are measured in 10s or 100s of MH, and GPUs generally deliver 100s of KH, IMAcredit's wallet will hash in the 10-100KH range.

Let us be perfectly clear:   This is a coin for the masses, designed to require large numbers of users to meet its block time target.  No handful of users will be able to dominate this coin.    Until N-Scrypt mining code like sgminer implement fixes GPUs and Pool mining will not make sense.  Pool mining may never make sense - this code is designed to be run from the wallet!

Hashing Algorithm:  N-Scrypt, initial N=16.  Codebase tested through N=20 representing 7 generations of ASIC's to come and expected to work at higher Ns.  (for the coders out there:  Heap based scratchpad allocation vs. the typical Stack based which would break at N=15)

Difficulty Algorithm:  Kimoto Gravity Well, with Time Warp Patch
Source:  https://github.com/IMACredit/imacredit
Windows Wallet:  http://www.mediafire.com/download/1vzyh5h0dg5bljh/imacredit-qt.exe
    If you do not setup a imacredit.conf file, please make sure you use the Console window and "setgenerate true".
MacOS Wallet:  not currently available
Linux Wallet:  Build from Github source for maximum compatibility

Block Explorer:  http://ima.thedigitalmint.org/

Pools:  NONE BY DESIGN - Download your wallet and mine with it

Ports:
        Listen:  64097 (54097 for testnet)
        JSON-RPC:  64096 (54096 for testnet)

Sample Configuration file (completely optional for Windows users)
       rpcuser=<yourname>
       rpcpassword=<some very random long password>
       listen=1
       gen=1

Like all high quality coins, IMACredit maintains an active DNSSEED network.  You should NEVER have to specify addnodes.  All wallets should work upon launching.

Social:   IRC Freenode:  #imacredit   Developers Twitter Account:  @YACCoin

Game:  3rd coin in "The Crypto Void" by 1BillionHex, but totally usable outside of the game

Website: http://www.imacredit.org

Other information:

IRC is NOT used by the codebase for anything (unlike many coins)

UPnP is disabled for your protection!

Development team:  The same folks that brought you YACCoin and 1Credit.

Wow!  That sure would have saved me a few hours.  Looks like I still have a bit of cleanup to do.

Thanks!!!

Hi all...

I'm the dev for 1Credit and YACCoin.  Started fooling around with hosting p2pools for each last night and it was pretty straight forward.  Thought everything was fine when I left at 3am - pools were hashing, 99.5% credits were being paid out (0.5% to the author), etc.

Looking at the web interface, I would see a single user - me, which was as I expected.

Per my coin log, around 7am this morning, while I was soundly asleep, something changed.  Instead of receiving 99.5% of the coins, I started ONLY receiving the 0.5% associated with discovering a block. The rest was going to a valid, but totally unknown, coin address.  I checked the /users webpage and for this:

http://puu.sh/acBhT/aed46ecb76.png


Those all appear to be valid YACCoin addresses, although I don't see any of them hashing in the p2pool log.  I have also not publicly advertised the pool (until now) nor the connection port, so am surprised by this.

Any thoughts?

FYI:  ADDRESS_VERSION is set to 31, which is correct for my coin, and matches the leading digit in those in the link above.

Possibly related:  I failed to find definitions for IDENTIFER and PREFIX and left those the same as in the litecoin.py?  Should I have randomized those to avoid coin conflicts?

Unrelated:  Can someone tell me what PERSIST does?  I had to set it to False to get things hashing...

Thanks in advance!

Cassey

His post has been reported to the moderator, please feel free to do the same.

Responded to that one already.  See previous post asking for clarification regarding what you are furious at.   Without such input your just screaming to scream.

Just curious... are you willing to donate about a month of your life, say 6 hours a day during the week and 12 hour weekends, for free, to develop software for other people to use?  If not, why would you EXPECT, nah, DEMAND that other people do this for you?

Well... since your asking for help from other users, providing a bit of background on what your using and being willing to try a few things would be considered polite.

Which of the half-dozen or so forks of support code are you running?

If bfgminer, have you tried a "bfgminer -S zeus:all -d?" and see which devices it detects?

Your furious?  At what?  At buying hardware hoping to make money and not doing your homework to see if there was software to support it?  At presuming the graciousness of the open source community would provide you perfectly working software the moment your hardware arrived for free?  At presuming such free software would come with a lifetime of support guaranteeing that you never had any issues, concerns, problems, etc?  At thinking you are the only person in the whole world that isn't going through exactly the same thing you are?

I confused.  Please help me understand.

And see what?  That you are using the DMAXL branch that is over-reporting Hash rate and under-delivering WUs?  Go yell at him... not us.

Ah, maybe read past the first line of my post and you will see my suggestion...

Recognize that I don't blame the distributors one lick - in fact, I'm happy they spent their time creating cgminer 3.1.1 - without it we would have had paperweights.  But also recognize that they do NOT directly profit from doing such work.  Sure, they benefit from it, but why would one distributor be responsible in any way-shape-or-form for creating, or paying to have created (now there is a thought!) software that every other distributor could profit from?

Zeus is the company we should be pissed at.  They have promised firmware updates to reduce power consumption and not delivered.  They are hopefully working on firmware updates so that all equipment actually identifies itself right (3 of my 11 fury's do not), but again no word or honestly much hope of such a delivery.

And who is to blame for that?  Probably us... since we order the crap in hopes of making a profit no matter what shape it is in.

How many people actually send donations to Luke or Nate?  With likely 10s of thousands of users of their code, I bet one could count on two hands how many donations they have received for their work...

Cassey

OK - here is the bottom line on the Zeus equipment

For full disclosure:  I started with a week 1 GAW Fury (same thing as a Zeus Blizzard except that mine actually shipped on time), now own 11 of them and a Black Widow (the GAW 62 chip one).  I like GAW, they do their best to delivery, and I'm an affiliate of theirs.  OK, think that covers that.  The rest of what I'm saying comes under the disclosure of "To the best of my knowledge".

1)  Terry (aka Panda) over at Zeus promised delivery dates and full software support for his product line.
2)  Luke and Nate and others hear about the new chipset and ask for samples and specs in order to develop drivers - nothing happens
3)  Equipment arrives at the distributors with software for one specific mining device.  Shipments are due to go out in days.  Most users don't have such a device.  Raspberry PIs are somewhat kinda cheap, lets use those.  Distributors panic and hack together cgminer 3.1.1 and make emergency alliances with others, like Zenminer.  And believe me, cgminer 3.1.1 for Zeus is a total hack:  No attempt to identify chips - just presume everything attached is a Zeus and that they are all the same.
4)  Others start the long process of reverse engineering 3.1.1 and trying to figure out how to do it right.  Many are partially successful using equipment they bought themselves.  Note this is mostly all volunteer efforts - people spending their weekends and evening trying to make the world a little better - much like Luke and Nate.  Thus we end up with DarkWinde's efforts and several others.  I believe Starminer sponsors DMAXL to try and get it right - probably the first guy to actually receive payment for this efforts.
5)  Nate finally, about 5 weeks after first ships, gets a single low end Blizzard to test against.  Prior to this, he has looked at a few volunteers systems (like mine) to try and get a grasp on whats going on.
6)  Nate - who is the responsible party for All-Things-Scrypt within bfgminer's codebase gets to work, burning more of his weekends and evenings (fact:  been online with Nate at 3am testing things - and yes, he has a regular day job!)
7)  bfgminer gets fully functional code, that does detection, allows concurrent use of gridseeds, multiple Zesu devices, etc. with full command line support and integration into the code base about 6 weeks after the first equipment was available to look at.
 People bitch "what took you so long!".  Assholes.  This is volunteer work guys.  It gets done when it gets done.  If you need to scream at someone, go scream at Terry for not delivering specs, ever, or early test units to the community, and instead focusing on maximizing HIS profits.

Cassey

Suggest popping over to http://asic.usertalk.info/index.php?topic=66.0 and reading the 2nd post in that thread.  It should get you started.

Cassey
Sysop @ asic.usertalk.info

Mandatory ugprade on 1CRedit as of 8pm CST 6/10/14...

Despite weeks of testing utilizing the -testnet world, a bug cropped up in the new fork for 1CRedit.

You MUST upgrade to the current release in order to participate in any future coins.

You should see version as 90400 or 9.4.0 and protocolversion of 70016 (if you do a "getinfo")

Cassey

Absolutely none taken!  I'm just glad you actually read it!

Sorry about that, went to put a proper title and fix a few bolding mistakes, but this forum doesn't allow me to delete my own post apparently.

Today, we are announcing some dramatic improvements to the 1CR coin to address some of the impediments to adoption that have occurred in the past few months.

The coin was designed to be very secure, have little adoption by the multipools, and to be used for longer term investment uses (such as banking in the simulated worlds of OneBillionHex. One of the chief complaints to many of the pool operators was the extended time before pool users were able to receive their first payouts.  This was due to two security measures of 1CR: 1) 256 required confirmations, and 2) a defensive difficulty retargeting, designed to discourage mulitipool raiding of the coin during low diff periods.

Without pool cooperation, we found that general adoption of the coin was low, and the coin would be mined in a very dramatic roller coaster difficulty fashion, which led many to give up.

After careful lab testing – a new source code has been release, that goes into effect at block 4000 – probably within the next day or so.

The new source code will reduce the confirmations to a still very secure 156.  Note that most wallets add 20 to this.  As well, the difficulty retargeting has been ‘dampened’ to still discourage multipool raiding but provide a more consistant coin time.  We hope these changes will encourage pool owners to re-adopt the 1Credit Coin (1CR).  This should start to produce a bit more coins daily, and allow the pool users to receive their coins in a targeted 25 hours, versus 3-4 days the old settings yielded.

The coin is still a very rare coin, and is designed to have minimal forks (several months old and still not a single fork!), and minimal risk of double spend attacks.  There was zero premine, there are not secret payouts in the code, no IPO, and the only way the Dev or the team can make money on this is the same way you can, mining the coin.  It has held a pretty good value on Poloniex so far, even with the earlier design inconveniences, and we expect it to be a great coin to buy and hold as it gets integrated into the Crypto Ecosystems.

We need some community support, in the form of a few new pool operators, to really make this relaunch a success.  PM the Dev and he can introduce you to a few experts if you need a hand.

Mission:
•   To create the investment coin for long term security and stability
•   To avoid Mulitpool Mining that drives the value down
•   To create a stable coin to encourage long term mining (set it and forget it)

Supply:
•   To date – there are less than 4000 coins
•   Each block generates 1 new 1Credit coin
•   No IPO
•   Total Supply – The current block number!  One coin per block of course!
   
Current specs:
•   Algorithm: Scrypt PoW
•   Started: April 19th
•   Blocktime: 8.5 Minutes
•   Blocks confirm: 156 confirms (most wallets add 20)
•   Transaction Confirms: 16
•   Retarget: every block (Modified KGW)
•   Block rewards: 1

Website and forums:
www.1creditcoin.org  
https://cryptocointalk.com/forum/1225-1credit-1cr/

Wallets:
Source https://github.com/1credit/1credit
Windows Wallet
http://www.mediafire.com/download/n851l3345n5yitd/1credit-qt.exe
Mac Wallet
http://www.mediafire.com/download/gci1u4n5l5654ie/1CRedit-Qt.dmg

Ports:
        Listen:   6666 (16666 for testnet)
        JSON-RPC: 6667 (16667 for testnet)

Sample Configuration file (totally optional!):
        /* 1credit.conf */
        rpcuser=<yourname>
        rpcpassword=<some very random long password>
        listen=1
        gen=1

Like all high quality coins, 1CRedit maintains an active DNSSEED network.  You should NEVER have to specify addnodes.  All wallets should simply work upon launching.

Pools:   http://mpos.1creditcoin.org - basic site available for the health of the coin
http://mineblocks.no-ip.org:2627/pool/1CR/
Block Explorers:  https://prohashing.com/explorer/1CRedit/
Exchanges:   https://www.poloniex.com
Social:  IRC Freenode:  #1credit
Game:  4th coin in 1BillionHex game.

Other information:
IRC is NOT used by the codebase for anything (unlike many coins)
UPnP is disabled for your protection!
Blocksize limited to 16KB for fast propagation.  Note this significantly restricts the number of transactions/second supported by 1CRedit, but as an investment coin, designed for fewer, larger, mostly paid transactions, this is not viewed as an issue.