|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
|
|
George5
Legendary
Offline
Activity: 1205
Merit: 1003
|
 |
March 16, 2021, 09:59:58 PM |
|
WTS a bunch of XST at 300 sats. Willing to sell up to a few hundred thousand. OTC or through Bittrex orderbook. Gotta diversify my portfolio a little bit. DM if interested.
|
|
|
|
|
gustopaz
|
 |
May 17, 2021, 02:17:09 AM |
|
711 456 XST burned in 10hrs , Stealth is moving forward ,glad to see it!
|
|
|
|
gustopaz
|
 |
May 25, 2021, 06:38:18 AM |
|
We are excited to announce that the first 100 StealthNodes, each including a unique StealthDragon, have been purchased. 1,738,305 XST were burned and permanently removed from the supply. A new batch of nodes will be available soon. Stay tuned for what’s next. https://twitter.com/stealthsend/status/1396729615943618561
|
|
|
|
gustopaz
|
 |
March 23, 2022, 06:31:42 AM |
|
Update January 7 2022 Part 1/2:
Hello community, here is a quick overview of what's happening:
1. Desktop App Improvements and Fixes: - minimum amount to send changed from 0.05 XST to 0.01 XST - TX Details Sidebar: receiving address and txid can now be copied to clipboard - Disable spellchecker on address in send screen - Implemented Sentry -a tool for error reporting - improvements to speed up the Send-Process We are currently fixing a little bug, once that is resolved a new build will be released and the app can be updated.
2. Importing Private Keys of Staking wallets/addresses The Desktop HD Light wallet is not meant and designed to be able to import staking wallets, yet regular private keys of course. We had several users report issues not being able to spend their staking addresses and tried to address every single case. Moving forward anyone with a staking wallet, that means, everyone who was staking XST prior to Junaeth's mainnet launch, and even after that, and has issues spending the coins on the respective addresses, has to use the daemon, import their wallets/addresses and simply send from the daemon to either the desktop or mobile app. There will be a How-To Guide soon for anyone not knowing what to do.
3. Mobile App Android The redesign process for Android took a bit longer than expected and was more complex compared to iOS. One reason is that Android has more different screen sizes than Apple. We are very close tho. Final features have been implemented this week, during the next 1-2 weeks things the remaining items will be finalized, cosmetic adjustments will be done to have a build that refelcts iOS 1:1, or as close as possible, Android has its differences of course. Part 2/2:
4. Feeless for our Mobile Apps In progress; The current version available on the store for iOS and the upcoming redesign for Android do not feature feeless yet. Status quo is that we try to make it work on both, it looks promising and we're making good progress. Once there are news to share we will do so. It's actively being worked on. It is a unqiue approach, since the feework has to be done on the device itself and not server-side, no one has ever done it. Be sure we do everything possible to make it work.
5. Wrapped XST Not too long ago we shared a quick update on Telegram, we were looking for outside help to take on this topic since we don't have the resources currently to work on it. Both teams we hired were not able to deliver what we needed. We have a team looking into it, there is no ETA tho, ready when ready.
Update February 10 2022:
Hello @everyone
1. Desktop App: pending transactions incl an auto refresh functionality have been implemented; release v0.9.06 during the next few days
2. Mobile Apps: iOS: the first feeless transaction on mobile was successfully sent on Jan 27; its currently being implemented on the current iOS version and will be available early March Android: redesign is in its final stages, last cosmetic things are getting fixed; we're aiming for a early March release as well; it does not include feeless yet; this will be the subsequent step
3. Wrapped XST: we hired a new team to wrap the token on BSC, we'll provide an update as soon as we know more, ETA approx. 2 weeks
4. How-To Tutorial for importing private keys using the daemon; then transferring to HD-accounts is in the making
Update March 11 2022:
Hello @everyone
1. Mobile Apps – ios feeless is ready for release; we are preparing the release and announcement: this is one of our biggest accomplishments of all time and a very important release – android redesign is done; we are doing some final tests this week and prepare the release and announcement feeless implementation for android will start shortly after
2. Wrapped XST on BSC: almost finished, probably another week or so
The redesing of our mobile apps has taken way more time and resources than initially planed, it wasn't even planed in the first place but we wanted to do this; and it was worth it: we will rethink the items on our roadmap and re-prioritize, the dates and timelines are outdated and not realistic anymore
|
|
|
|
gustopaz
|
 |
March 23, 2022, 06:33:00 AM |
|
Stealth's current blocksize allows for 917 TPS - feeless (single core CPU). The throughput limit is at 9362 TPS. A 16 core CPU could verify 140430 TPS.
TPS non-feeless: BTC: 7 ETH: 15 DOT: 1000 Visa: 1700 SOL: 2825 AVAX: 5000
Stealth is setting new standards. #junaeth $XST
|
|
|
|
|
|
|
gustopaz
|
 |
April 23, 2022, 01:10:29 AM |
|
Update April 22 2022:
hello @everyone
1. Feeless Integration for Android Mobile App implementation is in progress and should be done by mid/end next week, after that we'll have about 2 weeks for testing; that's a realistic outlook
2. wrapped token on BSC everything is done; it is / would be ready to be used but we decided to implement multisig after the completion which is the reason for the extra time; we have to build an API to fully automate swap and especially the reverse swap best guess is 7-10 days Users will be able to swap XST using the desktop app since it supports sending to multisig addresses already; mobile app , both ios and android, need and update which will be next after feeless is done;
|
|
|
|
|
|
|