Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - startail

Pages: [1] 2 3 4
1
General Discussion / Re: Getting full account history
« on: January 23, 2020, 04:17:48 pm »
@Nesh, that is indeed the way you have to do to resolve more than 10,000 OPs. This will be supplied as a patch to the UI and Bitshares-report.

2
General Discussion / Re: Getting full account history
« on: January 07, 2020, 08:45:03 pm »
You can also use https://github.com/bitshares/bitshares-report to generate the same report as the one in the UI wallet.

The code can't export more than 10,000 rows at the moment, due to a limitation in the API call. There is a fix done to this that I will submit to the repository in a week or two, together with some more changes.

The UI wallet does the same thing (and has same limitations), so there's no real difference.

3
Stakeholder Proposals / Re: [Poll] BSIP76:Set bitUSD feed threshold
« on: December 29, 2019, 07:42:52 pm »
As this proposal expired on 28th of December, will the price now shift back to normal or was it just the required time for it to gain weight? If so, will we look on a new proposal on shifting the price feeds to reflect current real conditions?

4
Speaking as one of the developers on the platform, I always kept my bit assets on the dex as I knew I could keep them safe and rely on the fact that I could always know that 1 btiCNY = 1 CNY or 1 bitUSD = 1 USD worth of BTS. That always made me feel that I could trust the platform of a well funded system.

One thing I missed was the possibility to easily trade these assets on other exchanges, thus bringing bit asset liquidity of the bitshares dex. I felt part of a platform that was growing steadily, and didn't see a reason for worry as there where big ideas and a spirit of new things coming (like Wirex integration, bitUSD on other exchanges etc).

These days I see that I was wrong. I now hold "stable" assets that aren't backed by real value and feel that nothing is done to correct this. If the community felt that paying developers in any other way is better I'm always been open for it, but these discussions have not happened. If we are once again supported to develop the Bitshares reference UI I'm willing to look at arrangements just as sschiessl.

Still hoping for a better future for Bitshares.

5
Stakeholder Proposals / Re: [Poll] BSIP76:Set bitUSD feed threshold
« on: December 07, 2019, 08:43:54 pm »
Users are settling bitCNY to exit the market with a loss since a few weeks ago, so this would be a good thing to do to make the market pair with the real price again.

6
Stakeholder Proposals / Re: [Worker] Integration of BTS with Wirex
« on: December 07, 2019, 08:42:52 pm »
Hello guys,

Do we have any update to this worker status?
I see we had some activity on invoices in oktober, but no update on the status of it.


7
I agree that we need to get back to real price feeds, the feed is now only about 60% of the real price on the markets elsewhere. As price of BTC drops this gap will only grow. We could hope for a surge back, but this would be a long wait and the DEX, and in the meantime the DEX takes the risk of all positions.

Returning to real price feeds should now be done in a controlled manner, as shorters need to be able to act on the change. It could be shifted each day over x days. However, the main difficulty now is that many shorters have abused the system and set their CR to the lowest possible as they know the price isn't moving, which introduce yet another issue with this manipulation.

To correct this, there needs to be a definite return to real price feeds. Perhaps a Global Settlement is better than anything today, as a controlled manner may just be an unnecessary hurdle, we have mechanisms to handle this, let them work their magic!

8
Stakeholder Proposals / Re: [Worker] Bitshares UI Worker Proposal for 2019
« on: September 05, 2019, 07:07:53 pm »
Thanks for the kind words from some of our users in the community. It doesn't feel good to be forced to stop our work mid release, we had a large bundle of changes to the UI addressed as well as many new features. To hold a higher standard, as wished by the communtiy, we couldn't make a release without proper testing and without funds we just can't make it.

I hope this resolves and that we at some point can start working on the UI again, but we're going to loose many good developers that just can't wait out for a solution.

9
Stakeholder Proposals / Re: [Worker] Integration of BTS with Wirex
« on: August 10, 2019, 10:13:52 am »
Do we have any update or progress reports on the Wirex integration?

10
I'd like to reach out to all of the community to support the worker for the Bitshares-UI. At the moment of writing we require about 27 million votes to become active again.

We have been out of additional worker funds for a few weeks now. There are still funds for another few weeks, but the sooner the worker is voted back in again the better.


At the moment there are funds for almost all proposed workers, the remaning daily refunded budget is 5500 bitUSD. The bitshares-ui worker requests only 2000 bitUSD per day and would still leave funds over for many other new workers.


11
Stakeholder Proposals / Re: Proxy: dls.cipher
« on: July 29, 2019, 09:10:26 pm »
Nice work and would like to say thanks for the support on the UI worker as well.

12
Please consider voting for the Bitshares-UI worker 1.14.165 to support the development

This post is a copy of this announcement on Steemit and Whaleshares

Today I'd like to present some of the great progress that the Bitshares-UI team have accomplished during the first 6 months of the current worker.

A worker is community funding open projects
Quickly described for those unaware of what a worker on the Bitshares platform is, it's where a project or team can create a worker proposal for payments directly from the blockchain funds.

To receive funds, one have to have enough support in forms of BitShares votes, and all expenses are usually published on an escrows webpage. Bitshares-UI uses BBF as an escrow.

The Bitshares-UI worker can be found here, together with full expense reports, and lasts between 2019-02-11 - 2019-12-30.

Many new Features with a faster paced process
Compared to the old worker that had a purely decentralized approach where "anything could be worked on by anyone at any time", The UI team declared in the worker that a "tighter schedule to achieve key aspects of the development".

Further down you can see a breakdown on how this approach has resulted in a faster paced process for issues, but first I'd like to talk a little more about what this has resulted in. What larger features been added and what is yet to come.

Hash Time-Locked Contracts
This is a large feature, which involved much work from both core and UI team. Once released in the core, the implementation where tested and released in the 190618 release.

Atomic Cross Chain Swaps (ACCS) or simply “Atomic Swaps” require the receiver to acknowledge a transaction prior to a deadline by generating cryptographic proof of payment. This is accomplished through the use of a hash and preimage via Hash Time-Locked Contracts (HTLC). Should the recipient fail to supply the proof, they will forfeit the ability to claim the payment and it will return to the payer. This functionality allows for completely trustless wallet-to-wallet trading between assets and enables a significant reduction in counterparty risk.

The implementation of HTLC significantly widens the permeability of the BitShares ecosystem as it allows transfers between BTS and other HTLC-enabled blockchains directly and in a completely decentralized fashion. Trading with assets outside the BitShares ecosystem is now possible and eliminates the necessity of using a gateway. For a detailed explanation, consult the user guide, or try it out directly.

Alert notifications
The past months the attempts to fool new users to hand over access of their accounts through features of the chain, in this case by sending a proposal to add them as co-owners, increased. This resulted in the team implementing two additional failsafe alerts. One being that if the proposer is not in the user’s favourites, it will not allow the proposal be possible to accept by default.

The other was recently introduced, where the team can quickly post alerts to the chain, which will show up on the wallet top, such as the below message.



Direct Debit Authorization
Creating permissions to withdraw specific assets for accounts is now possible directly within the BitShares wallet. This application opens up a variety of possible applications such as automated distribution of salary or expense account funds, reward or referral pay-outs, even a weekly allowance for your children (a great way to incentivize learning about self-sovereign finances)! Test it out online!

Market Fee Sharing
Asset owners such as Gateway operators can now define that a percent of all market fees for a given asset are funnelled through the referral rewards program. The flexibility of this new feature creates enormous incentive for web admins to onboard new users into BitShares.

At the time of writing, market fee sharing is enabled for bitUSD, bitCNY and bitEUR at a staggering 80%!

Issue and Progress Breakdown

View Issues (only open)
View Issues w/ Closed

As can be seen on the two images above, there are a steady stream of issues submitted to the repository. To the right you can see that we've had a constant stream of closed issues during the period. We started out with 267 open issues (2436 total with closed) and we are today at 321 open issues (2951 total with closed).

Since May we're also tracking the amount of assigned and unassigned (backlog) active issues. An active issue is one that has a set goal for completion and is expected to be worked on.

We've managed to close over 500 issues during the past 6 months.

Days to Complete
Many issues can require work from other teams to be possible to close, such as the core team to implement a new API for a specific feature to happen.

If we look at the time it takes for one issue to go from being submitted to closed, we've been much more effective in that department. View Image

One of the promises and goals of the new worker was to restructure the way issues are addressed. We went from a community "work on whatever you desire" approach to forming a team that should try to aim for a good feature implantation approach and how it can be applied.

With this graph we can see that we went from, in the beginning of February, a median close time of almost 200 days to a more reasonable 60 days. Since March we've also been below the period average of closing time, so the pace is good and we're able to address and handle issues quicker.

A closed issue does not, of course, mean a new feature or that something may have been added to the code at all, but a lower average still means we have addressed it, evaluated it and deemed it done either as implemented, that it can't be implemented or just a closed discussion for some reason.

We're quicker and closes issues in 2 months rather than over 5 months!

Milestone Workload
During the past 4 months we've had an average of 45 hours work per 2-week period (milestone). There were two periods of less activity, much due to the DEVCon in Shanghai. Merging of work slowed down and closed issues decreased during this period. We complete around 120 - 150 hours of work per 4 months period. View Image

When a milestone closes, the remaining work is pushed over to the next (the green bar), so we have much work estimated. We still have a significant amount of work added every week that is done in a short time span.

We do about 50 - 70 hours of work per 2-week period


Get involved - earn bitAssets!
Help develop, Do translations, Test releases


The Bitshares-UI is a community project, and even if it's a small team, everyone is free to contribute to the future progress of the application.

Help Develop - If you're a developer and know React, you can read the contribution guidelines, and check out the current active issues.

Help Test Releases - If you're not a developer, but love to test new releases, you should check out for the Release Candidates. About every 5-8 week we do a release which has to be tested first. By testing new features and the app overall you can earn testing points, which is real bitAssets!

Do Translations - We're open for translations, using Transifex, which will earn you translation points, which is real bitAssets!

Check out for Pinned Issues on the GitHub Repository for testing and translation tasks. They are posted when there are new releases.

Posting about issues are of course also much welcome!



13
I'll be reaching out CMC directly using my bitshares.org email on behalf of Move Institute. I'll cc Fabian and Ryan as well. After initial response from them we can organize better who needs to do what. Basically i'll ask for extension, explain our community/holders process (consensus) and force update of data there.

If anyone is against this action, 6 hours from this message complaints are acceptable. We have 11 days left, and I'm not into time-wasting when it comes to something this important.

"Prevent rather than cure".

Chee®s

Sounds good!

14
Why does all the links for the page for "BitShares Asset Exchange" link to Open Ledger?
Currently redirects users to https://bitshares.openledger.info/*

It also links to http://cryptofresh.com/assets, shouldn't this be https://bitshares.org?

It also seems there is a warning posted for all listings for the exchange.

Quote
Please visit the exchange's website for details regarding scheduled downtime.

15
General Discussion / Re: Price Feed Review
« on: July 15, 2019, 02:30:08 pm »
Please note that the "Global settlement happens at price" in the UI currently did not account for the MSSR values. This means that for bitUSD this value is 1.02 times higher. It's been fixed and pushed for next release.

The UI got two new enhancements to improve price feed monitoring by the community


Pages: [1] 2 3 4