So it fixed it? 

Last time, I promise.  I found the bug with the script, so it should work now, {}s and all.
Turns out bash was gobbling the "run-miner" file section.  I forgot that "!" has special meaning at the command line.

If you want to verify CPU usage:

If you want numbers:

Try something for me real quick?  Remove the first line, the one that starts "#!/bin/bash" and try again?
Let me know if that works.

I've updated the script and removed the "#!/bin/bash", so hopefully that fixes it.

Is that hashrate as listed on the sidebar or as listed on the worker page?
The worker page is per-round, so it's not 100% accurate.

For those having issues with ">", try the script again.

I had a few lingering tab characters and I added a few newlines at the end for good measure.

Has anybody had any luck with VanityGen and SRC?

The base58.h file reports the [urlhttps://github.com/securecoin/Securecoin/blob/master/src/base58.h#L275]PUBKEY_ADDRESS[/url] as 125, which should give you a resulting address that starts with s (which it does).

However, whenever I generate a privkey with vanitygen, the privkey always starts with "9", so SecureCoin reports it as invalid.
Whenever I dump a privkey from SecureCoin, it always starts with "L".

Any ideas?

edit:

It gets stranger.  According to http://gobittest.appspot.com/PrivateKey the keys generated by SecureCoin give the error "Private key is not on curve".
The keys generated from vanitygen report no such error.

What?

DigitalOcean doesn't see which flags, that's the job of the compiler.  When you supply "-march=native", the compiler tries to determine which CPU architecture you have, then generates object code based on what instructions your CPU has available.
I think the problem is with DigitalOcean and "-march=native" is how their virtualization works.  It reports the CPU architecture as K5 (don't quote me) but then complains that there's no valid target architecture.

Also, mining at 100% doesn't mean much, only your speeds do, so be sure to check your miner's output to see which works best for you.

I do too.  I left it out for maximum compatibility though.
Some VPS services like DigitalOcean crap their britches when you include it though, so your mileage may vary.

Well, it's official.  I've now uploaded my newest VPS mining guide, this time for pool mining SecureCoin.
If anybody is interested, feel free to check out the post over here.

The script even works on Amazon AWS!

Hey guys, quick announcement!

I just posted my newest guide on VPS pool mining SecureCoins.

However, because SecureCoin and QuarkCoin use the same hash algorithm, you can just configure the script to mine at a QuarkCoin pool and you'll be good to go!

RESERVED

Notes:

• The script automatically runs the SecureCoin miner whenever the node is rebooted.  You can use this to your advantage!
  
  • Shut down your mining node and make a snapshot or backup image of it.
  • Create new nodes based on the snapshot/backup.
  • The new nodes will begin mining as soon as they boot!
• SecureCoin uses the same hash algorithm as QuarkCoin.  If you want to mine QuarkCoins instead of SecureCoins, just change the pool info to point to a QuarkCoin pool!  See below for an example.

Quark Mining Config (example):

Hey guys!  This guide is going to be a bit shorter than the other ones.  I'm going to assume you know some of the basics of setting up a VPS node as outlined in my previous guides.  You'll also be needing to set up a pool mining account.

Once you have an Ubuntu 64-bit VPS running, this should be a walk in the park.

QUARKCOIN USERS: follow the instructions in this first post, then read the information in the second post for additional info.

Setting up a Securecoin Pool Miner on VPS for Absolute Noobs
Donations are appreciated!  If you enjoyed the guide, feel free to sign up using one of the referral links or maybe even send a few coins my way!  
BTC: 1E2egHUcLDAmcxcqZqpL18TPLx9Xj1akcV
Ψ: AWHJbwoM67Ez12SHH4pH5DnJKPoMSdvLz2
SRC: sMCD2p55fkPD6s8EzDrL7vVp8EYqPkJ6mo

Before You Begin

• Set up a SecureCoin pool mining account.  I would recommend one of the following pools:
  
  • http://src.coinmine.pl - Support stratum
  • http://crypto-expert.com/SRC - Supports longpoll
  • http://pool.bounceme.net:44397/static/ - p2pool variant, mining URL is http://pool.bounceme.net:44397 (worker name = payout address; password = anything)
• Set up SecureCoin-QT on a computer and generate a SecureCoin address to receive your coins.
• Download PuTTY (putty.exe) so you can connect to your VPS when the time comes.
• Sign up for a DigitalOcean or Linode account.
  
  • During the creation process, be sure to create a node running Ubuntu 13.04/12.04 x64 (not x86)
• If you signed up for DigitalOcean, check your email for your root password.  If you signed up for Linode, your password will be what you specified.
• Run PuTTY and paste the node's IP address into the "Host Name" slot, then hit "Open" at the bottom. (figure 1)
• PuTTY will ask you to confirm the SSH key, press Yes (it will only ask once) (figure 2)
• Type or paste your password into PuTTY and press enter.  To paste, simply right click.
  
  • Note: You will not see the password characters!  This is normal.

Getting Down to Business

• If you chose DigitalOcean, it's time to change the root password!  Type passwd, press enter, then enter a new password.  Just like before, the password characters will not show up. (figure 3)
• Copy this automated setup script to notepad. (highlighted version)
• At the top of the script, there are fields starting with "SECURECOIN_".  Fill these out with your desired info.  Be sure to keep the quotes!
  
  • SECURECOIN_POOL is the URL for the mining pool.  The script includes two example URLs to get you started.
  • SECURECOIN_WORKER is your SecureCoin pool worker name.  It's usually in the format of "username.workername"
  • SECURECOIN_PASS is your SecureCoin pool worker's password.  Usually it will be short and simple, like "x".  DO NOT USE YOUR ACCOUNT PASSWORD FOR YOUR WORKER PASSWORD.
• Copy the entire modified script from notepad and paste it into your PuTTY window (right click), then hit enter.
• The setup is now running.  It will take approximately 10 minutes to complete.
• Once the script completes, you will see a brief help message and list of commands.[/url]

Congratulations!  You're now mining SecureCoins!

If you'd like to maximize your mining potential, please see my mini-guide on How to Clone DigitalOcean Droplets.

---

Changelog

• 29 August 2013 - Fixed some issues, the script now runs correctly!  Sorry about that!
• 29 August 2013 - Initial release!

I had really odd stuff go down when I tried to solo RPC mine.

On windows, I could only connect from localhost, even if rpcallowip=*.*.*.* was set.
When I set up a VPS and connected remotely, it would stall.  Miners wouldn't report disconnects, but the daemon stopped responding to commands.

Might just be my luck though. 

Just checked your post history.  This isn't the first time you've cried wolf.

They probably don't bundle the conf files because they go in such a different location.

Your best bet if you're still having issues is to manually run the addnode commands via the debug console:

Also try turning off your firewall, it may be limiting you.

I'm having a hard time thinking of a scenario where a user would need a password in order to buy something.

Maybe it's my lack of imagination.

What's the prefix byte for SRC addresses for use with vanitygen?  I tried 125, but they result in invalid private keys.
The supposed public address starts with an "s", but you can't import them.

https://en.bitcoin.it/wiki/List_of_address_prefixes

FOR THE LOVE OF ALL THAT'S HOLY, DON'T PASTE YOU ENTIRE DAMN ERROR LOG.

USE CODE TAGS: [ code][ /code]

Try the super generic: