Before I was at 79-85c depending on the board...
After I was as low as 62-65c but now I tuned it to 72-74c so that I can heat my house... we getting cold nights here so having the GPUs heat helps us save on the Heating bills.


Undervolting will not damage your card... Overvolting it will.


I would think it is all a matter of timing between memory and gpus... since they are not overclocked to push more and produce lots of heat they work in unison.  I was shocked too when I saw the results.  If I tried to overclock while undervolted, it would then drop in performance.  I think the bell curve gets shifted downwards as you undervolt.

Theoretically that is how I understood it as well but in practice, it does not seem like so.  When I opened up the ports to listen, poof I was able to sync correctly thereafter.

Maybe the Dev can shed some light on this issue?

Yes I did see it.  Just mentioning that the Windows GUI version did not mention the -upnp option as in the help menu.  It should be updated to have the same options as the starcoind.exe is all I am saying.

Wow woke up to this
0.00785895 BTC/24h @ 3.38 mh/s

My first working was at 15 diff and 70kh/s
second worker at 267 diff and 3310 kh/s

It is sad that we can't stop the decline of Alt Coins.

Here are Starcoin's command line options.. no option for -upnp.  Not sure if it is in the source but I will check.
**Update: Checked source... it was defaulted to USE_UPNP=0 when compiled and therefore reason why it was not visible.  For next version could you please ensure it is compiled with USE_UPNP=1 so that it will automatically work for Windows.

Options:
  -?                     This help message
  -conf=<file>           Specify configuration file (default: StarCoin.conf)
  -pid=<file>            Specify pid file (default: StarCoind.pid)
  -gen                   Generate coins
  -gen=0                 Don't generate coins
  -datadir=<dir>         Specify data directory
  -dbcache=<n>           Set database cache size in megabytes (default: 25)
  -dblogsize=<n>         Set database disk log size in megabytes (default: 100)
  -timeout=<n>           Specify connection timeout in milliseconds (default: 5000)
  -proxy=<ip:port>       Connect through socks proxy
  -socks=<n>             Select the version of socks proxy to use (4-5, default: 5)
  -tor=<ip:port>         Use proxy to reach tor hidden services (default: same as -proxy)
  -dns                   Allow DNS lookups for -addnode, -seednode and -connect
  -port=<port>           Listen for connections on <port> (default: 18216 or testnet: 28216)
  -maxconnections=<n>    Maintain at most <n> connections to peers (default: 125)
  -addnode=<ip>          Add a node to connect to and attempt to keep the connection open
  -connect=<ip>          Connect only to the specified node(s)
  -seednode=<ip>         Connect to a node to retrieve peer addresses, and disconnect
  -externalip=<ip>       Specify your own public address
  -onlynet=<net>         Only connect to nodes in network <net> (IPv4, IPv6 or Tor)
  -discover              Discover own IP address (default: 1 when listening and no -externalip)
  -irc                   Find peers using internet relay chat (default: 1)
  -listen                Accept connections from outside (default: 1 if no -proxy or -connect)
  -bind=<addr>           Bind to given address. Use [host]:port notation for IPv6
  -dnsseed               Find peers using DNS lookup (default: 0)
  -nosynccheckpoints     Disable sync checkpoints (default: 0)
  -banscore=<n>          Threshold for disconnecting misbehaving peers (default: 100)
  -bantime=<n>           Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
  -maxreceivebuffer=<n>  Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
  -maxsendbuffer=<n>     Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
  -detachdb              Detach block and address databases. Increases shutdown time (default: 0)
  -paytxfee=<amt>        Fee per KB to add to transactions you send
  -server                Accept command line and JSON-RPC commands
  -testnet               Use the test network
  -debug                 Output extra debugging information. Implies all other -debug* options
  -debugnet              Output extra network debugging information
  -logtimestamps         Prepend debug output with timestamp
  -shrinkdebugfile       Shrink debug.log file on client startup (default: 1 when no -debug)
  -printtoconsole        Send trace/debug info to console instead of debug.log file
  -printtodebugger       Send trace/debug info to debugger
  -rpcuser=<user>        Username for JSON-RPC connections
  -rpcpassword=<pw>      Password for JSON-RPC connections
  -rpcport=<port>        Listen for JSON-RPC connections on <port> (default: 18217 or testnet: 28217)
  -rpcallowip=<ip>       Allow JSON-RPC connections from specified IP address
  -rpcconnect=<ip>       Send commands to node running on <ip> (default: 127.0.0.1)
  -blocknotify=<cmd>     Execute command when the best block changes (%s in cmd is replaced by block hash)
  -upgradewallet         Upgrade wallet to latest format
  -keypool=<n>           Set key pool size to <n> (default: 100)
  -rescan                Rescan the block chain for missing wallet transactions
  -salvagewallet         Attempt to recover private keys from a corrupt wallet.dat
  -checkblocks=<n>       How many blocks to check at startup (default: 2500, 0 = all)
  -checklevel=<n>        How thorough the block verification is (0-6, default: 1)
  -loadblock=<file>      Imports blocks from external blk000?.dat file

Block creation options:
  -blockminsize=<n>      Set minimum block size in bytes (default: 0)
  -blockmaxsize=<n>      Set maximum block size in bytes (default: 250000)
  -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
  -rpcssl                                  Use OpenSSL (https) for JSON-RPC connections
  -rpcsslcertificatechainfile=<file.cert>  Server certificate file (default: server.cert)
  -rpcsslprivatekeyfile=<file.pem>         Server private key (default: server.pem)
  -rpcsslciphers=<ciphers>                 Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)

UI options:
  -lang=<lang>           Set language, for example "de_DE" (default: system locale)
  -min                   Start minimized
  -splash                Show splash screen on startup (default: 1)

Kind of curious what did you do to change your starcoin.conf to weed out the bad clients...

do a getpeerinfo
are all your peers have
"inbound" : false,
or any of them
"inbound" : true,

If they are all false, then you are on a different blockchain.
I have 11 of 18 connections that are set to true.

Setting up the uPNP port fixed my issue and now I am fully synced.

Litecoin will be replaced by Goldcoin (as someone keeps yelling it out in Cryptsy Chat).
IF it gets put on Cryptsy, I hope the DEV has every right to tell Cryptsy to Turn off Autosell for the COIN.  Ever since that option came into play, 95% of the Alt coins tanked.
I would love to see COL without ANY Autosell feature just to see how it will react...  Will it be the next pre-autosell IFC (shooting up to 400) or stay low like post-autosell ADT.

Honestly, I would rather see it @ Coinex.pw.  I find their trade engine is actually faster and smoother than at Cryptsy (for non C programmed exchanges)

Another day in the gutters or
with Cryptsy down and out, will the other exchanges pick up and make the coin values increase?
I think trading on other exchanges will increase and help bring the coins back up.

Ok found the listen=1 bug.  Starcoin has no uPnP capability and therefore the ports don't get forwarded to your Router.
You will need to add an entry into your Router or uPnP settings within Windows to allow users to connect to you.

The IP addresses in getpeerinfo is public domain.  Anyone can get this information either way.  Not posting IPs does not mean it makes you safe.  All they need to get your IPs are to run getpeerinfo themselves.  Hack attempts are not welcomed but this is the only way letting the general public know of possible issues.

If you are afraid of getting hacked, start learning about security and setting up defenses or the Internet is not a place for you to toy around in.

Personally, I am not afraid of people getting my IP Address.  My Honeypots will do their job in detecting intrusions and record/report infiltrations.

Paranoid users can simply do one thing right... power off their Internet connection.

Can you update page 1 with the proper version we need to run?  I am still running the version that is from 2013/09/20 as per Page 1. 

These are the only clients connected to Starcoin and they are not sharing their blockchains.  Please update your wallets so they act as listeners on the network and help others to get the chain.  Otherwise, Starcoin will die.

02:33:31

getpeerinfo


02:33:31

[
{
"addr" : "63.246.129.56:18216",
"services" : "00000001",
"lastsend" : 1382250810,
"lastrecv" : 1382250810,
"conntime" : 1382249788,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202964,
"banscore" : 0
},
{
"addr" : "216.155.151.242:18216",
"services" : "00000001",
"lastsend" : 1382250810,
"lastrecv" : 1382250810,
"conntime" : 1382249838,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202965,
"banscore" : 0
},
{
"addr" : "82.9.77.178:18216",
"services" : "00000001",
"lastsend" : 1382250811,
"lastrecv" : 1382250810,
"conntime" : 1382249855,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202966,
"banscore" : 0
},
{
"addr" : "188.252.16.109:18216",
"services" : "00000001",
"lastsend" : 1382249983,
"lastrecv" : 1382249997,
"conntime" : 1382249982,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 129451,
"banscore" : 0
},
{
"addr" : "37.229.117.57:18216",
"services" : "00000001",
"lastsend" : 1382250811,
"lastrecv" : 1382250811,
"conntime" : 1382250006,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202970,
"banscore" : 0
},
{
"addr" : "212.119.171.18:18216",
"services" : "00000001",
"lastsend" : 1382250810,
"lastrecv" : 1382250810,
"conntime" : 1382250028,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202971,
"banscore" : 0
},
{
"addr" : "81.53.162.166:18216",
"services" : "00000001",
"lastsend" : 1382250732,
"lastrecv" : 1382250746,
"conntime" : 1382250730,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 202999,
"banscore" : 0
},
{
"addr" : "198.211.116.19:18216",
"services" : "00000001",
"lastsend" : 1382250782,
"lastrecv" : 1382250783,
"conntime" : 1382250780,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 129451,
"banscore" : 0
}
]

This could be because most if not all your peer connections have listen=0 set in their config.  I am having difficulty getting updated to latest version because nobody wants their wallet to be shared with others...

add
listen=1
maxconnections=15

to allow others to download/update your wallet correctly and hopefully it would fix your issue too.

I just checked my wallet and all peer clients (8 of them) has listen set to 0.  Therefore, it tells me I need to download blocks but can't cause none of them are allowing me to download it.  Guys check your starcoin.conf and add the 2 lines listed above.  Help the community to grow and work together.

Still waiting for support, never received the coins nor the TXIDs.  

I had checked the Block explorers but there are no functional ones (search by wallet address) for these coins.

**Update**: Went to the IRC forum and they got me the info.  Faster to goto the Forum if you need immediate action.

Looks like we still are stuck on Stake issues again.

Maybe a few ideas to help further?
- Anyway to hard code the Stake Diff to 15 instead of 502 so that Stakes can process faster and therefore POW can start computing?  By lowering the POS DIFF, it will force it to stake faster (since it is CPU based and those who use el cheapo/low hash powered AMD or Intel Processors for their mining rigs)
- Can we add hard coded counters for blocks and alternate between POS and POWs? (1 POS to every 3 POWs)
- Add CPU hash speed check prior to setting the POS DIFF

Hopefully COL will clear up and get moving again... waiting patiently until it does.

This is what I did.  If it gets stuck, close Wallet, delete the PEERS.DAT, reopen wallet and it will continue syncing.
some reason it sticks with some wallets.
Mine got synced after doing this 4 times.

That is good.  You have your full amount on Stake.
That means you will get a stake for your full amount.  Once your CPU computes the Stake it will release it out of stake and you will gain Interest on that full amount.

Nothing is wrong here. Just you need to ensure your CPU is fast enough to compute the stake for it.

DId you issue the command "checkwallet" after syncing?

goto the console and type help