I am still here Jims.  I am not asking for anything from you. If you stay that's awesome. If you leave, nothing lost nothing gained. 

All of us Jims and Jimanthas will have our day.

The source of this problem is not as simple as it seems.  There is not a "maximum" parameter set in the code that restricts the number of coins that can be sent in one transaction but rather there is a limit on the size of the data that one transaction can consist of (block size).  Whats likely happening here is that your coins have too many inputs and the transaction gets bloated because of it.  A transaction with many transfers being used as input will cause the size of the transaction to go over the block size limit.  So for now try to consolidate your coins manually with smaller transactions. I've found the easiest way to do this is to use simplewallet from the binaries and copy/paste the command to send chunks of coins one at a time. When you send a group of coins that has a bunch of inputs into one destination address any future transfers of those coins will use that one transaction as an input.  In time, this problem will resolve itself. 

Hope that helps a bit.

-Jim

I am aware.  This is on my to do list but thank you for pointing it out.

Also, official pool is unstuck.

Jims,

Lets spread the hashpower out a bit and get some miners on the new pool.  jim.npool.pw is up and running and has a significantly lower fee!  I've tested and it is working very well with regular payouts.  This will reward the Jim who made the pool for the community, help secure the network, and prevent chain splits.

Eventually I will seek out exchanges to list Jim but if the community wants it you are all free to submit listing requests on any exchanges.  Ultimately it is up to an exchange to list a coin but if you require any information or for a dev or core member to provide anything for a listing let me know and I will do what I can to help.


Thanks for the interest and caution Jim,

The best way to throw large amounts of hash without risking splitting the chain is to solo mine so that one pool does not acquire too large a percentage of the total network hashrate.  Let me know if you need help setting this up but there are already posts on how to solo mine if you look through this thread.

Good day,

Jim

For anyone wondering about difficulty in regards to pool mining the ideal difficulty allows you to get at the very least 1 share per block so you are rewarded for your mining.  In my opinion you should target your difficulty so that you are consistently submitting multiple shares in a 2 minute period since the target block time is 2 minutes.  If you target your difficulty too high you might not submit any shares during the mining of a block and therefore not be rewarded at all.  On the other hand if you set your difficulty too low you will waste time getting new work.  It is best to find a good medium that allows you to utilize your computational power appropriately.  I have my pool set to adjust difficulty for miners and automatically targets having each miner submit a share every 20 seconds. This should allow roughly 6 shares every block and in my opinion allows miners to be rewarded accurately for their mining.  Hope this helps those wanting to set their difficulty manually. 

Jim, you are a gentleman and a scholar.  I will add your pool to the announcement post and block explorer asap.  Also, I will make your pool's domain in the default pool list on the next wallet release assuming it is still up and running at that time.

I'm sick, it sucks. For now we mine, soon we will work.

-Jim

At the moment the only way to solo gpu mine is to set up your own pool and point an existing GPU miner at it.  There may be an alternative in the future.

Absolutely not.


I absolutely won't.

For solo mining on Windows download the CLI wallet in the announcement post on page 1 and run jimcoind.exe (your wallet must be closed to run the CLI daemon but copy your receiving address first) and once the daemon is synced with the network issue the command,


It should display that the miner has started on each thread and if you want to see your hashrate use
On linux the commands are the same except for starting the daemon which is done with the command ./jimcoind from within the directory that jimcoind is in.

Alright Jims,

I think we need to take the pool offline for a while and get some solo mining going.  I thought it would be really nice for people to just download a wallet and start getting Jim payouts the click of a button but this is the 4th time having so much hashrate concentrated in on one node has caused a fork and its getting more and more difficult to fix as the blockchain grows.  I will do my best to find the time to write some step by step guides for various methods of solo mining to help the new Jims out but for the time being google is your friend.  The PoW is cryptonight so get to searching and i'm sure you will figure it out.  I will bring the pool back up when I have the time/money to set up another one to spread the hashes out, when the network hashrate has grown to the point that it wont dominate the network or when someone else can get a functional pool up to compete with it.  Apologies to the pool participants but this is whats best for all Jims.  In the meantime I urge every solo mining Jim to re-sync your blockchain so we are all on the same chain moving forward.

edit: I'm working on getting pool payouts to send but this last fork really muddied things up.  Regardless, all mined Jims will get to their rightful owners.
edit2: It will likely take a while for the blockchain to start moving at a normal pace again since the network lost so much hashrate when I turned the pool off.  This is normal and the difficulty will adjust soon enough to match the network hashrate.

-Jim

Stats on the pool are a little messed up right now and a lot of orphaned blocks need to be re-mined since the pool was mining on the wrong fork for a while.  As long as your wallet syncs to the same block height the block explorer you are on the right chain.

OK so at this point we have 2 chains going, if you have a block height higher than the block explorer be.jimcoin.net you need to delete your blockchain and sync from scratch.  On windows close your wallet and search %appdata% in your search bar and delete blockindexes.dat and blocks.dat from the JimCoin folder then open wallet again.  On linux, close your wallet and navigate to the .JimCoin folder in your root directory and delete blockchainindices.dat  blockscache.dat blockindexes.dat       and blocks.dat then re-start wallet.  Once done we should all be on the same chain matching the block explorer.

There are currently no plans for one.

It looks like there might be a split in the chain.  If your wallet is not syncing please make sure you save your jimcoinwallet.wallet file somewhere safe and delete your jimcoin folder in the windows appdata folder for windows, and if on linux delete the .JimCoin folder that should be located as your users root directory.  Once deleted open your wallet again and let it sync from scratch.  WARNING: if you delete your wallet file, your Jims will be gone forever so back it up!

Been a crazy weekend Jims. Dead battery in my truck, girlfriends water pump failed in her car, numerous PC issues.  I've been working like a dog to fix all the breaking shit in my life.  New battery in my truck, replaced gf's water pump, PC fixed and running again, pool is now fully functional and blockchain is rolling again.  For all you non-Jims out there taking shit and spreading doubt.. take a deep breath, sit down in a comfortable chair, and literally fuck yourself. 

Yours truly,

Jim

New version of OSX wallet is linked on jimcoin.net getting started page but only works on Yosemite because...Apple. Will have High Sierra compatible app soonish.  Compiling on OSX when you don't have one isn't fun.

Absolutely it is.