Thanks Microguy,

Surely difficulty should have levelled out now but it seems broken I have still only got one block since the fork... haven't got another block since I last messaged here, did you hear anything back from the developers/debug team?

Now it is really broken I have only got 1 block  since, which doesn't work out considering my hashrate and the difficulty level..

99% blocks return this error..

11/05/13 17:52:07 BitcoinMiner:
11/05/13 17:52:07 proof-of-work found  
  hash: 00000014b36349748e82e4b826d597b2222ce922717742374e5603a91afb0246  
target: 000000179b9a0000000000000000000000000000000000000000000000000000
11/05/13 17:52:07 CBlock(hash=549aa0fbee8fafea2f68, PoW=00000014b36349748e82, ver=1, hashPrevBlock=9fb85e89054db9b47b05, hashMerkleRoot=ad746ac2eb, nTime=1383673997, nBits=1d179b9a, nNonce=3887268864, vtx=2)
11/05/13 17:52:07   CTransaction(hash=2d9a69b564, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 048d3079520169062f503253482f)
    CTxOut(nValue=45.00000000, scriptPubKey=022b9b7e900726b1183dc63aff5fc2)
  CTransaction(hash=0464d1117f, ver=1, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(0f5e5fba26, 0), scriptSig=30450221008606c394db5415)
    CTxOut(nValue=2364.70000000, scriptPubKey=OP_DUP OP_HASH160 d60e75c75e5f)
    CTxOut(nValue=100.00000000, scriptPubKey=OP_DUP OP_HASH160 275f2408e07e)
  vMerkleTree: 2d9a69b564 0464d1117f ad746ac2eb
11/05/13 17:52:07 generated 45.00
11/05/13 17:52:07 keypool keep 398
11/05/13 17:52:07 ERROR:
 ProcessBlock() : Possible Multipeer 51 percent detected, initiating anti-legit-peerban defense! halting until valid block! This is normal..

11/05/13 17:52:07 ERROR: BitcoinMiner : ProcessBlock, block not accepted
11/05/13 17:52:09 Flushing wallet.dat
11/05/13 17:52:09 Flushed wallet.dat 265ms
11/05/13 17:53:06 Flushed 13535 addresses to peers.dat  110ms

Are we able to at least link external images?

Hi Don007,

Try opening the debug console and typing...

checkwallet

then repairwallet.. should restore you coins, other than those mined during the split.. please let me know if it does

Yep same block height both clients are showing 102951 and the block explorer is also showing 102951, using version: "v0.7.1.4-gcf3abdf39d-beta"

{
"version" : 70104,
"protocolversion" : 60011,
"walletversion" : 60000,
"balance" : x,
"blocks" : 102916,
"connections" : 4,
"proxy" : "",
"difficulty" : 0.01506741,
"testnet" : false,
"keypoololdest" : 1383624534,
"keypoolsize" : 101,
"paytxfee" : 0.01000010,
"mininput" : 0.00010000,
"errors" : ""
}



Just watched a further 4 mining transactions that were approved half an hour ago and had 3 and 4 confirmations respectively revert back to 0 confirms, and become ? in the transactions list, though one block mined 10 mins before this still remain.. also this time the actual transactions didn't disappear.. well not yet.. if I exit the client they may...

[edit] yep they disappeared upon exiting and re-opening the client [/edit]



Please let me know if there is any reason as to why this would happen and why they would stop showing in the qt transaction log.

Hi Akumaburn,

1. According to the blockchain explorer I am on the most recent chain this has happened on 2 seperate clients one that is newly installed and downloaded block chain and one that I redownloaded the block chain using the nodes on the website.

2. Could be that I messed Up.. will double check that [edited]


Hi Microguy,

I solved 10 blocks over the course of the morning 4 are still in my transaction list, the other 6 have disappeared and are no longer in the transaction list, additionally my client shows a count of 11 transactions but there are only 4 in the list :/

Would be cool to understand how and why this is happening?

The new client is busted somewhat!

1. if you quit before half an hour is up since your last transaction.. you will lose all those transactions that happened in that time!
My Transactions just keep disappearing and there is no way to check or repair wallet!!

2. with connect= set and peer.dat removed the client still connects to other ips other than the ones listed in the conf

Please fix ASAP.

Thanks for getting back NZDude,

My clients are all still producing the error message: "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers." although they are all current with the block explorer, do the checkpoints need to be updated or is it just a weird bug that would be fixed by redownloading the block chain; if so though how come it has effected 3 seperate clients? Do you have any ideas?

I am happy to help with the marketing etc, and although my C++ skills leave a little to be desired I am happy to help out where I can, I am busy for the next week with work but will have some time in the following weeks to work with anyone who is interested in doing some work on the coin/promoting the coin etc.

regards

Solo mining is working fine again despite the weird checkpoint error... the problem its not on any exchanges anymore and crypto sites are beginning to list the coin as dying!!!

If the DEV was interested in working with the community here that are interested in keeping the coin alive it would definitely be a step in the right direction.

Come ON NZDUDE!

Thanks to all who bothered to try and help... Starcoin is pretty much dead as far as I can tell, removed from all exchanges and coinwarz :/

To the admin, you could have saved it... it may be too late now...

what a joke


on another shitier note, for the last few days or so I have been receiving an error...

"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."

As well as trouble mining today, has anyone else had trouble solo mining today?

It keeps connecting then detecting a new block then goes back to waiting for work from the pool message???

Mining at Minar.cc seems to still be working fine which is very weird..

[EDIT] Solo Mining working fine again, though before when it wasn't I tried it on 3 seperate clients and was having the same issue [/edit]

Hi Swiftshoot,

Properly read what I wrote...


C:\Users\infinitevs\Desktop\starcoin>starcoind /?
StarCoin version v1.5.0.0

Usage:
  StarCoind [options]
  StarCoind [options] <command> [params]  Send command to -server or StarCoind
  StarCoind [options] help                List commands
  StarCoind [options] help <command>      Get help for a command

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)
  -upnp                  Use UPnP to map the listening port (default: 0)
  -detachdb              Detach block and address databases. Increases shutdown time (default: 0)
  -paytxfee=<amt>        Fee per KB to add to transactions you send
  -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)

 

Hi Swiftshoot,


close starcoin-qt and backup and delete peers.dat in your data directory.. update the starcoin.conf with something similar to the below config


start starcoin-qt

hope it helps..

also before you mentioned that the client had no upnp support, well the starcoind does... to get it setup automatically close starcoin-qt, then in a command prompt in windows type :

starcoind -upnp

now wait it will take a while to load and not say anything.. leave that prompt open and open another.. in this prompt keep trying:

starcoind getinfo

until you get a response that isn't server not found, once you get a response

you can close both the command prompts, UPNP for that client has been set in the router!

Firstly let me just say a big THANKS to everyone that actually gave a fuck enough to try and help me troubleshoot! CHEERS!

SO I GOT ALL MY COINS BACK AND MY CLIENT PROPERLY IN SYNC

Here's how I did it:

BTW there are multiple chains happening so make sure you are 100% up to date with the blockviewer before your client starts generating pos blocks.. i'll explain below...

Okay after restoring my backup wallet, I attempted re-sync from scratch for the third time, this time remembering to unlock my wallet at the beginning of the resync...

So all the transactions happened like the 2nd time, about 4/5's of the way through my coins started appearing but this time instead of the coins disappearing after they showed up, my balance started to increase *sigh of relief*..

I kept syncing to realising that I had only lost 2 days worth of transactions now at least!

It made it all the way 199456, then slowed right down and started to generate POS blocks... after checking my other clients I realised these blocks must be stale and to allow the client to keep on regenerating them would just put it out of sync again I closed the client.

I installed a fresh client on another computer and started a resync, this went fine and completed to the correct amount as stated by the blockviewer, I closed the client and I copied the correctly completed blocks to the other computer with my original wallet overwriting the invalid block... I re-opened the client...

I then used repairwallet to restore the coins that were staked for the invalid pos blocks

SO NOW WE ARE ALL GOOD - Completely in SYNC, AWESOME..

Also I have made some changes to the conf file that will force the client to sync off of the good clients that I have found for the time being to prevent this happening again from bad clients... If anyone needs a hand just give me a yell...

Additionally if you are feeling generous feel free to send me some STR: sYYUD6zyyYpswwckX2pco8LbyxpE8FAqB5

swiftshoot: did that fix the syncing issue for you? has anyone noticed after installing a new client and syncing that the "estimated total blocks" drops from the "current number of blocks" (202517 currently) to 129471?

Dreamhouse or NZDude, can you help with our coin loss/re-sync issues!!??


Swiftshoot my client is set to listen=1 and I have set to irc=1 and dnsseed=1 also, I checked getpeerinfo and you are right none of my peers are sharing their chain either, if you want to PM me your IP i will do the same and we can start by sharing with each other.... if that will help..

but just to clarify how exactly are you coming to that conclusion?


HippieTech, could you please elaborate on that?

regards,

infin.

Hi Swiftshoot,

Yeah that was my first thought, but the check came back no errors???

Any other ideas??

loveys, just wondering did you get it fixed?? Same thing happened to me on the new blockchain coins have all disappeared dispite some transactions still showing as approved..

If I try changing over to the new blockchain I lose all my coins bar 0.8, everything I have from over a month of mining transactions as well as anything I have transferred in the past day or so to other accounts shows a question mark and those that were half way validated are never going to be validated?

Changing back to the backup of the original chain restores my balance, etc... but it won't sync ?

In changing to the new block are we expected to lose everything we have mined, if that is the case i'll be rather annoyed

btw I am stuck on 187926, my client never made it to 191569.. any help would be appreciated!!! THANKS

UPDATE: Its worth mentioning that after re-syncing the new blockchain from scratch I get the same problem with my wallet being empty bar 0.8 of a coin which is unconfirmed. Even though the other transactions in September show as valid the coins aren't there HELP! Time to abandon Starcoin?