[ANN][XST] Junaeth - World’s first private high performance blockchain protocol

[Muqocan]

Dear All,

I couldn't be here for a long time. I have some XST in my wallet into my computer.
The version of my QT is 1.3.0.0

Could you please tell me step by step what should I do for updating my wallet without lost my XST coins?

Many thanks in advance.

regards,
Muqocan

[1713937302]

1713937302

[1713937302]

1713937302

[1713937302]

1713937302

[MR1]

Dear All,

I couldn't be here for a long time. I have some XST in my wallet into my computer.
The version of my QT is 1.3.0.0

Could you please tell me step by step what should I do for updating my wallet without lost my XST coins?

Many thanks in advance.

regards,
Muqocan

1. Back up your wallet
2. Stop the old client 1.3.0.0. and delete it.
3. Download the new client from XST official website:  www.stealth-coin.com and launch its setup.
3. Go to the application data directory
4. Remove blk0001.dat, txleveldb (directory), database (directory), db.log, and debug.log
5. Download the zipped bootstrap file from https://drive.google.com/file/d/0B8rWOb ... sp=sharing
6. Unpack the bootstrap file into the application data directory (C:\Users\My Computer\AppData\Roaming\StealthCoin)
7. Start the new client
8. For the new client your computer will pause momentarily at 71% to fill the key pool (you may not notice)
9. The progress will pause at 91% for as much as one hour (up to 2 hours for old computers!) to validate the bootstrap file
10. The chain may take 5 to 10 minutes to sync

For more info, check our FAQ section:
https://stealthcointalk.com/viewtopic.php?f=16&t=46&sid=9e3b4ac2e3362a7d00321602052fe0bf

[StealthCoin1]

please let me know when i can testnet stealthsend? please don't tell me it's not exist, which it seem that way  
i think it wouldn't be this quiet if hondo or argarkig able to code something like stealthsend.
emilioman told me these guys can't code and the reason he's dumps to nothing and moving on.
i know this coin is dead but seen i want to check into my coinbase why not stop by my old coin. OMG btc, the pump again!

[gustopaz]

please let me know when i can testnet stealthsend? please don't tell me it's not exist, which it seem that way  
i think it wouldn't be this quiet if hondo or argarkig able to code something like stealthsend.
emilioman told me these guys can't code and the reason he's dumps to nothing and moving on.
i know this coin is dead but seen i want to check into my coinbase why not stop by my old coin. OMG btc, the pump again!

Why is this coin dead? How do you know that? You know Hondo personaly?

[leetcoiner]

hi

my coins from wallet didn't want to send it type   clearwallettransactions

and now my balance is 0

what can i do now in console so the balance will be back?

thanks for answer

[StealthCoin1]

please let me know when i can testnet stealthsend? please don't tell me it's not exist, which it seem that way  
i think it wouldn't be this quiet if hondo or argarkig able to code something like stealthsend.
emilioman told me these guys can't code and the reason he's dumps to nothing and moving on.
i know this coin is dead but seen i want to check into my coinbase why not stop by my old coin. OMG btc, the pump again!

Why is this coin dead? How do you know that? You know Hondo personaly?

i don't know this hondo guy. do you?

[StealthSend]

In the last couple of days, I've gotten two reports of users having difficulty syncing. It may be because two seed nodes were down for a few days. They are back up and synced without any problems.

I have also updated the bootstrap file. If you have trouble syncing, follow the bootstrap instructions in the OP.

-- Hondo

[wildduck]

Thanks a lot wallet synced

[subzer04]

Hi, I cant send XST, it says Error: Transaction creation failed. Please open Console and type 'clearwallettransactions'...

I reloaded bootstrap and resynced a couple of time but, it didn't help.

[stealth.money]

Hi, I cant send XST, it says Error: Transaction creation failed. Please open Console and type 'clearwallettransactions'...

I reloaded bootstrap and resynced a couple of time but, it didn't help.

Send in smaller amount, say if you can't send in 50000 then try to send twice in 25000. If all failed type 'clearwallettransactions' then 'scanforalltxns'. The 'scanforalltxns' would take times if you have ton of transactions, be patience.

[StealthDevs]

hi

my coins from wallet didn't want to send it type   clearwallettransactions

and now my balance is 0

what can i do now in console so the balance will be back?

thanks for answer

Follow these steps:

1) Type in the console clearwallettransactions then ENTER
2) Now type scanforalltxns and press ENTER

After doing this, your balance will show up again.

[kryptologist]

Are you guys working on anything new? Are the transactions truly anonymous? thanks

[MR1]

Are you guys working on anything new? Are the transactions truly anonymous? thanks

Yes,we are working on StealthSend which will render fund sender fully anonymous. Other projects will be released shortly after StealthSend is live.

At this stage StealthCoin has native Tor and stealth addresses which masks fund receiver.

[zeerobje]

Can we expect some news the next months....

[boltz]

Maybe stealthsend will be released , I mean it's kinda the time ....just my guess ...

[StealthSend]

In case anyone has been following, a semi-critical architecture dependent signature exploit has been found that can cause the chains of many cryptocurrencies to fork. I learned of this exploit only two or three days ago and have been researching it and determining the best fix, which seems to come from Peercoin.

I have updated github with the fix to this exploit and have been running tests.

https://github.com/StealthSend/Stealth/commit/e18175fe125b196d9bb1f25d3234f7eef3759b9f

In addition to patching this exploit, I fixed some longstanding synchronization issues, which I will be testing over the next couple of days.

https://github.com/StealthSend/Stealth/commit/540f745c4924f0c98661bf0cfeac85fbc48e8533

I will have new builds available within a day, but they may not be signed by CryptoCertify. Since release is timely, I won't wait on the code signatures. As soon as the signed builds are available, I'll replace the unsigned builds with the signed builds. This could take as long as 5 days. The issue with CryptoCertify code signing is my own mistake. I did not know I needed to manually approve the signing cert after it was re-issued. Because I missed the window of approval, I had to restart the issuance process. It may take several days before I can approve the cert and sign the builds.

When syncronization testing is done, I will issue an alert so that block explorers and exchanges update to the new sources (version 2.0.2.0). This alert will be issued within a day.

A description of the forking bug can be found here:

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki


-- Hondo

[MR1]

In case anyone has been following, a semi-critical architecture dependent signature exploit has been found that can cause the chains of many cryptocurrencies to fork. I learned of this exploit only two or three days ago and have been researching it and determining the best fix, which seems to come from Peercoin.

I have updated github with the fix to this exploit and have been running tests.

https://github.com/StealthSend/Stealth/commit/e18175fe125b196d9bb1f25d3234f7eef3759b9f

In addition to patching this exploit, I fixed some longstanding synchronization issues, which I will be testing over the next couple of days.

https://github.com/StealthSend/Stealth/commit/540f745c4924f0c98661bf0cfeac85fbc48e8533

I will have new builds available within a day, but they may not be signed by CryptoCertify. Since release is timely, I won't wait on the code signatures. As soon as the signed builds are available, I'll replace the unsigned builds with the signed builds. This could take as long as 5 days. The issue with CryptoCertify code signing is my own mistake. I did not know I needed to manually approve the signing cert after it was re-issued. Because I missed the window of approval, I had to restart the issuance process. It may take several days before I can approve the cert and sign the builds.

When syncronization testing is done, I will issue an alert so that block explorers and exchanges update to the new sources (version 2.0.2.0). This alert will be issued within a day.

A description of the forking bug can be found here:

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki


-- Hondo

Pretty cool!

I believe the lead dev`s message will reassure XST followers that StealthCoin never stops to develop. Its development goes on in Stealth mode, that`s why it is called StealthCoin  

[StealthDevs]

Version 2.0.2.0

XST has been updated to version 2.0.2.0. It has several performance improvements and bug fixes.

1. A signature malleability issue that could be used to attack the chain has been fixed. See https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
2. Syncing is now effortless and goes from genesis to fully synced without intervention in about 18 hours.
3. Staking has been improved to be more efficient. Stakers will earn closer to the maximum interest rate and the wallet should consume fewer resources.
4. A startup bug has been fixed that caused the Qt client to crash in some cases.

In all, these changes should improve client performance, usability, and network stability.

Qt client downloads are available on the OP. Github has been updated.

The current builds are not yet signed because of an administrative error in renewing the signing certificate (https://bitcointalk.org/index.php?topic=836009.msg13064430#msg13064430).  Signed builds will be available in 5-7 days when this error is corrected.

[BTCwriter]

Version 2.0.2.0

XST has been updated to version 2.0.2.0. It has several performance improvements and bug fixes.

1. A signature malleability issue that could be used to attack the chain has been fixed. See https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
2. Syncing is now effortless and goes from genesis to fully synced without intervention in about 18 hours.
3. Staking has been improved to be more efficient. Stakers will earn closer to the maximum interest rate and the wallet should consume fewer resources.
4. A startup bug has been fixed that caused the Qt client to crash in some cases.

In all, these changes should improve client performance, usability, and network stability.

Qt client downloads are available on the OP. Github has been updated.

The current builds are not yet signed because of an administrative error in renewing the signing certificate (https://bitcointalk.org/index.php?topic=836009.msg13064430#msg13064430).  Signed builds will be available in 5-7 days when this error is corrected.

Fresh new install and syncing right now. No longer need to exit then open again, installed and start syncing non-stop right now. Look to be a solid wallet. Solid 3D tile wallet.

[Bavaria]

Version 2.0.2.0

XST has been updated to version 2.0.2.0. It has several performance improvements and bug fixes.

1. A signature malleability issue that could be used to attack the chain has been fixed. See https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-July/009697.html
2. Syncing is now effortless and goes from genesis to fully synced without intervention in about 18 hours.
3. Staking has been improved to be more efficient. Stakers will earn closer to the maximum interest rate and the wallet should consume fewer resources.
4. A startup bug has been fixed that caused the Qt client to crash in some cases.

In all, these changes should improve client performance, usability, and network stability.

Qt client downloads are available on the OP. Github has been updated.

The current builds are not yet signed because of an administrative error in renewing the signing certificate (https://bitcointalk.org/index.php?topic=836009.msg13064430#msg13064430).  Signed builds will be available in 5-7 days when this error is corrected.

Always nice to hear good news from this wonderful coin!