[ANN][SHA]SHACoin2 - Dead Revival - Virtual & Physical Coin - Faucet

[TimC]

TimC...does your wallet actually show v1.1.0?  I have the new wallet with the new logo, but it still shows v1.0.0

It has the new logo but say v1.0.0. Right now I'm in process going to send my coins to another wallet on my other computer but that won't help the 12k coins that are stuck in stake.

So I send 1 coin to myself from on computer to another

Sending Computer
Status: 1/unconfirmed, broadcast through 5 nodes
Date: 3/28/2014 23:37
To: SYbnJQsUFXAQjahJwGdVruSNvSjzCdsn3h
Debit: -1.00 SHA
Transaction fee: -0.001 SHA
Net amount: -1.001 SHA
Transaction ID: 325172b4c91b868ee060b7f1d9b84076b31ffcdcb6e95be911278610b6ad711a

Receiving Computer
Status: 0/unconfirmed
Date: 3/28/2014 23:37
From: unknown
To: SYbnJQsUFXAQjahJwGdVruSNvSjzCdsn3h (own address)
Credit: 1.00 SHA
Net amount: +1.00 SHA
Transaction ID: 325172b4c91b868ee060b7f1d9b84076b31ffcdcb6e95be911278610b6ad711a

Looks like the 1 coin is now in limbo.

Time for the Dev to check this out.

[powersup]

has anyone else noticed shacoind is missing from the latest release? how do you unlock wallet for minting?

[ixk1]

deleted everything but wallet.dat & shacoin.conf from folder in appdata..

stuck on block #15500

version # = v.1.0.0 but download said v.1.1.0




getinfo

{
"version" : "v1.0.0.0-SHA",
"protocolversion" : 60010,
"walletversion" : 60000,
"balance" : 2366.16446800,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 15500,
"moneysupply" : 129755203.43360600,
"connections" : 8,
"proxy" : "",
"ip" : "2001:0:9d38:6abd:3055:3d6b:b4b5:abb3",
"difficulty" : 41721.56903888,
"testnet" : false,
"keypoololdest" : 1394995953,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}

[powersup]

update: ok removed all files from old client, removed all files from appdata/roaming/shacoin except for wallet.dat, made new shacoin.conf with info in op, and now wallet seems to be syncing.

edit: in console type "walletpassphrase "yourwalletpassword" 999999999" to start minting

[chiznitz]

deleted everything but wallet.dat & shacoin.conf from folder in appdata..

stuck on block #15500

version # = v.1.0.0 but download said v.1.1.0




getinfo

{
"version" : "v1.0.0.0-SHA",
"protocolversion" : 60010,
"walletversion" : 60000,
"balance" : 2366.16446800,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 15500,
"moneysupply" : 129755203.43360600,
"connections" : 8,
"proxy" : "",
"ip" : "2001:0:9d38:6abd:3055:3d6b:b4b5:abb3",
"difficulty" : 41721.56903888,
"testnet" : false,
"keypoololdest" : 1394995953,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}

This coin is so jacked.  I did the same as above and got stuck aorund 15575, well thats before I got rid of peers.dat

Currently I'm on 18736 with extra addnodes.


I hope this can be resolved, I'm getting worried there are many forks.

[frank123m]

has anyone else noticed shacoind is missing from the latest release? how do you unlock wallet for minting?

#1189

and we need new wallet!

[Mortimer452]

My wallet is staying syncd now it seems, block # 18949, and minting POS blocks like crazy.  None are confirmed yet but are incrementing confirmations.  101,328 coins in my stake balance.

Currently, I have 3 peers, but this number varies between 3 and 29 pretty frequently: 
89.66.87.7
71.187.164.122
151.228.116.110

The transaction for the coins I purchased from CryptoAltEx appears orphaned, so I'm guessing they were (or maybe still are) definitely on the wrong chain (but who knows at this point)

I'm out for now - will leave this running overnight and see WTF is up in the morning

[powersup]

My wallet is staying syncd now it seems, block # 18949, and minting POS blocks like crazy.  None are confirmed yet but are incrementing confirmations.  101,328 coins in my stake balance.

Currently, I have 3 peers, but this number varies between 3 and 29 pretty frequently: 
89.66.87.7
71.187.164.122
151.228.116.110

The transaction for the coins I purchased from CryptoAltEx appears orphaned, so I'm guessing they were (or maybe still are) definitely on the wrong chain (but who knows at this point)

I'm out for now - will leave this running overnight and see WTF is up in the morning

{
"addr" : "198.98.120.30:25666",
"services" : "00000001",
"lastsend" : 1396066459,
"lastrecv" : 1396066459,
"conntime" : 1396066068,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 18871,
"banscore" : 0
},
{
"addr" : "109.90.106.198:25666",
"services" : "00000001",
"lastsend" : 1396066460,
"lastrecv" : 1396066459,
"conntime" : 1396066073,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 18871,
"banscore" : 0
},
{
"addr" : "175.182.76.155:25666",
"services" : "00000001",
"lastsend" : 1396066530,
"lastrecv" : 1396066459,
"conntime" : 1396066074,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 16038,
"banscore" : 0
},
{
"addr" : "94.9.147.118:25666",
"services" : "00000001",
"lastsend" : 1396066464,
"lastrecv" : 1396066464,
"conntime" : 1396066103,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 18871,
"banscore" : 0
},
{
"addr" : "24.215.120.126:25666",
"services" : "00000001",
"lastsend" : 1396066460,
"lastrecv" : 1396066459,
"conntime" : 1396066277,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 18876,
"banscore" : 0
},
{
"addr" : "67.231.63.27:25666",
"services" : "00000001",
"lastsend" : 1396066460,
"lastrecv" : 1396066529,
"conntime" : 1396066348,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 0,
"banscore" : 0
},
{
"addr" : "198.100.127.34:25666",
"services" : "00000001",
"lastsend" : 1396066514,
"lastrecv" : 1396066516,
"conntime" : 1396066512,
"version" : 60010,
"subver" : "/SHACoin:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 18964,
"banscore" : 0
}
]

[powersup]

clent now in sync, minting, and same block height as explorer 

[jdh015232]

well, my client is in sync apparently now, and the 300,000 i had in stake, is gone >.<
oh well, who knows what is going on, i dont :/

[joele]

Still has sync problem, it need to be fixed.

[sacskate]

Well my wallet is working fine. I saved my wallet and deleted everything. I used the updated wallet, it got stuck. I closed it, reopened and ran "repairwallet". Now everything is fine. I have several stakes and the first few are now confirmed.

And you using the wallet from the first page the Windows(v1.1.0)?

yes

[sacskate]

well, my client is in sync apparently now, and the 300,000 i had in stake, is gone >.<
oh well, who knows what is going on, i dont :/

Mine did that. I typed "repairwallet" in the console, waited a minute, then closed the wallet and when I reopened it my coins where back.

[jdh015232]

well, my client is in sync apparently now, and the 300,000 i had in stake, is gone >.<
oh well, who knows what is going on, i dont :/

Mine did that. I typed "repairwallet" in the console, waited a minute, then closed the wallet and when I reopened it my coins where back.

hey, this worked! haha, idk what is going on with this coin, but i kindof am liking the drama and community help
go SHAcoin

[sacskate]

well, my client is in sync apparently now, and the 300,000 i had in stake, is gone >.<
oh well, who knows what is going on, i dont :/

Mine did that. I typed "repairwallet" in the console, waited a minute, then closed the wallet and when I reopened it my coins where back.

hey, this worked! haha, idk what is going on with this coin, but i kindof am liking the drama and community help
go SHAcoin

I think the coin forked on the 26th. The coins we had staked on the 26th were on the fork. We eventually synced with the correct chain but our coins were stuck with the interest we had from the forked chain. Repairing the wallet freed those coins up because they were in the correct blockchain. I think everyone just went off on a fork on the 26th and now everyone seems to be making their way back to the correct chain. Some people are still having issues because they keep adding rouge nodes.

[sacskate]

For those having problems try this:
Delete everything in your appdata folder except the wallet.dat file.
Download the updated client from the OP.
DO NOT ADD ANY NODES AT ALL
Let it sync, if it stalls or has problems, close it and reopen it.
If you are missing coins go to the console and type repairwallet
Wait a minute or so and close the wallet.
Reopen it and all should be fine.
TO BE CLEAR DO NOT ADD ANY NODES, INCLUDING THE ONES IN THE OP.

If this helps and you feel like it, feel free to send me some SHA!
ScyQy4hDMotk6JKmWAjKe1kY3dCjMw1AE6

[powersup]

For those having problems try this:
Delete everything in your appdata folder except the wallet.dat file.
Download the updated client from the OP.
DO NOT ADD ANY NODES AT ALL
Let it sync, if it stalls or has problems, close it and reopen it.
If you are missing coins go to the console and type repairwallet
Wait a minute or so and close the wallet.
Reopen it and all should be fine.
TO BE CLEAR DO NOT ADD ANY NODES, INCLUDING THE ONES IN THE OP.

If this helps and you feel like it, feel free to send me some SHA!
ScyQy4hDMotk6JKmWAjKe1kY3dCjMw1AE6

adding nodes from the op helped fix my syncing issues. maybe try first without the nodes on the op, if still having sync issues try adding the nodes in the op.

well, my client is in sync apparently now, and the 300,000 i had in stake, is gone >.<
oh well, who knows what is going on, i dont :/

Mine did that. I typed "repairwallet" in the console, waited a minute, then closed the wallet and when I reopened it my coins where back.

hey, this worked! haha, idk what is going on with this coin, but i kindof am liking the drama and community help
go SHAcoin

I agree, its great to see community getting behind this coin, it has a lot of potential.

[L1240erion]

Wasn't the new wallet supposed to have the unlock feature?

[Biomech]

sha to the moon!

Bots go to hell.

[L1240erion]

I know someone posted the fix for unlocking. But can someone post it again? I cannot find it.