It’s been a while since our last update, so I wanted to give a quick run down of some of the improvements we’ve been making related to our web service.
Sale of delegations will be re-enabled some time in the next 2 weeks or so
First, since we have a tendency to still get emails on this issue, I’d prefer to announce that we are going to re-enable delegation sales a while within the next a pair of more or less weeks. we are going to not give any further steerage on an explicit time once this may happen. Note that worth|the worth|the value} for delegations has enlarged dramatically since its original introduction attributable to demand and conjointly due to the rise within the price of Steem that it's tied to.
Continued specialize in reducing/mitigating user mistakes
Many of the changes we’ve created fall under the “invisible” class. once they do their job properly, the user ne'er needs to apprehend the error was caught and auto-fixed by the computer code.
Auto-fix (when possible) unhealthy memos wherever destination address was erroneously entered
One common error once individuals square measure causing Steem/SBD to U.S.A. is to place their desired destination address in as their memoranda once they send to U.S.A.. If our computer code will tell what specific coin sort they're posing for, it'll mechanically fix such transactions and send the specified coin sort to the requested address. Note that this is often solely attainable once the data formatting of the deposit address is exclusive versus alternative coins we have a tendency to support.
Auto-fix (when possible) transactions wherever Steem was sent rather than SBD (or vice-versa)
One common error is once the incorrect coin is shipped to a deposit address (Steem rather than SBD, for example). we have a tendency to can’t altogether cases fix this downside, as a result of we have a tendency to can’t invariably make certain of what's the “correct” destination to send to, however usually we are able to, and in such cases our system can auto-correct the dealing and method it currently.
Auto-refund of Steem/SBD sent with a foul memoranda
*If we’re unable to work out what the user desires to try and do once a foul memoranda is shipped, our computer code can auto-refund the Steem/SBD to the causing address, unless the causing address is AN exchange or steem service which may send a U.S.A.er’s funds to us. we have a tendency to don’t auto-refund in such cases, as a result of the exchange wouldn’t shrewdness to properly credit the funds we have a tendency to sent them to the originally causing user of their website.
If you use or attempt to operate a service that will do auto-refunds on client errors in an exceedingly similar manner, please contact U.S.A. and that we can whitelist your service against auto-refunds. this may forestall our server and your server from ping-ponging the funds back and forth attributable to continual auto-refunds (we saw one such case already before we have a tendency to whitelisted the service against auto-refunds).*
Allow re-use of deposit addresses related to Steem account creation to shop for a lot of Steem
If you get a deposit address from our system to shop for a Steem account, you'll currently re-use that address to shop for Steem for your account. Once the account is formed by our system, any more funds sent thereto deposit address are treated as a daily deposit address for getting Steem for the associated account.
Ability to repair some transactions wherever user sends wrong coin sort to “compatible” address
*If a user accidentally sends litecoin to a bitcoin deposit address, or vice-versa, our support personnel will manually “fix” such dealings if you send U.S.A. AN email with the transaction hash. antecedently this was a troublesome enterprise, therefore we’ve machine-controlled the method somewhat.
Please note but that it’s unacceptable for U.S.A. to try and do this within the case of bitcoin/bitcoin money address mistakes as a result of one uses SegWit and therefore the alternative doesn’t. therefore these mistakes can still lead to a user loss till enough exchanges implement the new Bitcoin Cash-distinct addresses (discussed in additional detail in our previous post on Bitcoin Cash). If you utilize AN exchange with Bitcoin money, you'll wish to think about recommending they create this switch to assist their users avoid such losses.
We’ve conjointly modified our default conversion from Bitcoin → Steem to ETH → Steem and requested that Steemit makes an identical modification to the default net URL they specify once linking to our website, since this may force users to form a acutely aware selection between Bitcoin and Bitcoin money once creating a sale with these 2 coins (ETH addresses square measure incompatible with Bitcoin and Bitcoin money, therefore there’s no danger of causing BTC or BCH to AN ETH address).*
Increased the suggested minimum quantity for getting Steem accounts
Our Steem account creation currently recommends causing a adequate quantity to buy a pair of Steem on the far side the bottom worth needed to make the account. This reduces the prospect for a worth fluctuation that will cause AN meagerly quantity to be sent to buy the account.
Improvements to our internal body panels for support personnel
We’ve created several enhancements to the interior data provided to our support personnel to permit them answer support requests a lot of quickly.
Added electronic computer “revision numbers”
We frequently update our electronic computer as we have a tendency to create enhancements just like the ones on top of. We’ve added a “revision number” at the lowest right corner of the positioning beside our copyright notice in order that we are able to verify what version of the positioning a client is exploitation. We’re conjointly within the method of adding code shortly to apprize users once there's AN updated version of the positioning, just in case there's AN update whereas they're on the positioning.
Performance enhancements to handle the load from giant numbers of consumers
*This last task may be a long run one, though we’ve recently created some vital enhancements during this space.
Currently our website has been ready to handle the height range of synchronous users with none downside and so our primary challenge has been to keep up our high-speed response to client support problems (hence all the work higher than to scale back the quantity of client support requests that need human intervention). however we tend to conjointly need to take care that our website itself remains strong within the face of accelerating numbers of synchronous users.
Since March of last year alone, we’ve seen the quantity of transactions processed by our website on a mean day increase by roughly an element of thirty, and there’s each indication that we are going to still see such will increase within the future, therefore we’re taking pro-active steps currently to take care we are able to handle future masses.*
Help stop accidental transfers to “phishing” accounts on Steem and BitShares blockchains
*As some folks have already discovered to their misfortune, some malicious accounts exist that commit to mimic the name of a preferred account like bittrex, poloniex, blocktrades, etc within the hopes that a user can build a literal error and accidentally transfer to their “phishing” account.
In order to assist stop this, we’ve been maintaining an inventory of such phishing accounts and warning users once they attempt to send to them. however the we tend toakness of this approach was that we had to stay up with such phishing accounts as new ones were created. to higher combat this downside, our computer code can currently auto-detect names that ar “similar” to far-famed exchanges and similar services that we tend to ar attentive to, and warn users they're getting ready to send to a suspected phishing account rather than the account that they're possible attempting to send to (to do that, we tend to re-used a number of the code that we tend to antecedently wrote to stop our Steem account creation service from making such phishing accounts).*
hmm nice updates
Congratulations! This post has been upvoted from the communal account, @minnowsupport, by utpoldebnath from the Minnow Support Project. It's a witness project run by aggroed, ausbitbank, teamsteem, theprophet0, someguy123, neoxian, followbtcnews, and netuoso. The goal is to help Steemit grow by supporting Minnows. Please find us at the Peace, Abundance, and Liberty Network (PALnet) Discord Channel. It's a completely public and open space to all members of the Steemit community who voluntarily choose to be there.
If you would like to delegate to the Minnow Support Project you can do so by clicking on the following links: 50SP, 100SP, 250SP, 500SP, 1000SP, 5000SP.
Be sure to leave at least 50SP undelegated on your account.
This post has received a 2.97 % upvote from @getboost thanks to: @utpoldebnath.