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
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.

2
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?

3
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.


4
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.

5
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!



6
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!

7
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.

8
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


10
We're currently seing a large forced settle on the bitUSD market, currently standing at 22 million BTS. It's with other words a larger investor.

You can easily view that there is one large post of bitUSD margin that has no TCR value, thus the network it settling the whole position on market. You can also easily view that the account in question has enough BTS to raise the margin from ~1.5 to ~3.4.

My question here, how much responsibility should a larger investor with so much BTS have? Especially when they create a large sell wall that could easily be avoided by the same. The margin uses less than half the accounts usable BTS.

Should we force a TCR, to limit the impacts of forced margin calls?
 

11
Stakeholder Proposals / Re: [Worker] Integration of BTS with Wirex
« on: June 29, 2019, 06:57:32 pm »
Wirex seems to be a good company to use. I ordered a card to test them out around 2-3 months ago and they've served me well since then. They're expanding massively, and with their new utility token attracting some attention the last few days.

Their whitepaper states they will add their own Stable assets called *W (as in USDW, CNYW etc), and also in the long run they will add margin collateral but it still has no planned date. With this they are a competitor, or you can work together and see them as a friend. I support this Worker based on the good usage I think Wirex can help our platform with.

Their expansion horizon is massive, doubling every year, and their schedule on this is no less, adding new markets all the time. This would benefit us to.

While BTS would be a good start, I'd love to see the possibility to have one or more of our stable coins added to the list of tradeable assets on the wirex app. But that's up to the worker to negotiate the best bang for the buck. It may be to costly to convince them to do this.

 

12
Meta / Re: Forum activity is slow, how to improve?
« on: February 15, 2019, 10:53:43 pm »
I assume that Forums haven't had the best of times since the introduction of blockchains like steemit and whaleshares. However, I'm usually a frequent visitor at this place as well, hence whey I think a reply to you is a good start :)


13
Stakeholder Proposals / Re: [Worker] Bitshares UI Worker Proposal for 2019
« on: February 14, 2019, 08:35:56 am »
I would like to say thanks to the Community that has given us support for us continue our work forward for a better Bitshares experience in 2019.

Since 13th February, the new worker is active. 

14
Stakeholder Proposals / Re: [Worker] Bitshares UI Worker Proposal for 2019
« on: February 11, 2019, 03:58:22 pm »
Many of the github requests are 'can the UI add X feature' or 'it would be cool if you could do Y', will these tasks be prioritised from the perspective of 'the user should be able to experience X' or is the core design not looking to change much? User centric design is core to any UI/UX project and finding and sourcing the needs of the user is fundamental.

Thanks for the support from Bitspark.

I'm sorry if I may have missed this under ideas for the future. (I've changed the original post slightly)
Current worker will very much work with trying to incoreprate new features, where possible.
During the worker we will try to find a good way to source the community.

15
Stakeholder Proposals / [Worker] Bitshares UI Worker Proposal for 2019
« on: February 11, 2019, 02:48:31 pm »
The Bitshares UI (also known as reference UI) team wishes to present a new worker proposal to the community. Read the full proposal here

Vote for Worker 201902-bitshares-ui - id: `1.14.165`.

Problems at the end of 2018
With the sudden drop in price in 2018, the current worker suddenly received fewer funds than it had promised to pay out for work. The worker was also unfunded for about a week as it dropped out of the active workers.

Thanks to the significant support in the community, which we are much grateful for, we remain an active worker.

Structural changes
As the funds we receive from our current worker isn't covering the worker, as well as we've had some structural changes in the personnel that handles it, we've decided to create a new worker early.

The previous project manager, Bill Butler, decided to step out. The team has given responsibility over to me, and I feel honoured for this opportunity. I see a group with great ideas, potentials and a wish to produce something great for the community and ourselves.

I will manage project and UI, tightly together with our new UX manager Ihor.

Ihor will take a prominent role in UX management. We've been behind in managing and missed some great potentials with people that been onboard for UX work. With Ihor stepping in I see this finally getting started for real. Ihor and I will coordinate UX and UI work to find the best way to get forward.

Alex will take over fund management and will continue to be a great asset for the team with his skills and many ideas on how to tackle things.

Stefan will continue to be our release manager, which he took over from Sigve when he stepped out late last year.

I believe that the team today sees the same way on where we are going. It's a great set of people, and together with our previous contributors from the community we will continue to progress this product towards an even better one.

Larger responsibility on the team
One of the significant changes for the current team will be that we will go away from the purely decentralised approach, where anyone could work on whatever they wanted at any time. The team will have a more substantial responsibility to tackle issues that are required to propel the application forwards.

The community is as always welcome to work on things they can/wish to do and supply a PR for it. We're always looking for new people wanting to work with the UI.

Quick Worker Key points
We've requested a larger share of BTS this time, much due to the decrease in price, but also since we've added a Devaluation Multiplier, which will make sure we have enough funds to cover at least a drop of 20% in price. As always, the worker will refund all funds not used up at the of the worker period, so no funds are kept if not used.

We've changed payment to bitCNY, thought the proposal would state all expenses in USD. A summary in CNY are indicated at the end, together with the conversion.

We've decided to stay with Bitshares Blockchain Foundation as an escrow. They've made a great work so far and provide excellent services for us with transparent accounting for example.

Current work duration will be from 2019/02/11 to 2019/12/30 (46 weeks).
The old worker was expected to end on 2019/03/31. Once the new worker is activated it will be superseded by the new one. We do not intend to have both worker funding at the same time.

Ideas for the future

We have yet not created a complete roadmap, but as the worker states, these are some key points that we will work on forward.

- Refactoring core connectivity and reliability components.
- Establish a more methodical QA and testing phase before releasing each version.
- Create a series of automated front and backend tests to reduce resurfacing bugs.
- Finish migration to ANT components complete with a style guide.
- Refine the navigation moving away from the sub-tab model.
- Creating a more modular exchange experience and an easy way for exchanges to brand and configure their own.

Our goal is to create a more slick and unified experience for the UI. We have many ideas, and we've had several talks during the past two months about this and how to make this work. We will source the community for ideas and features that are requested, as well as working closer together with the bitshares-core team to make sure we can integrate new features as they are released by the bitshares-core team.

The team is ready to take this to the next level, give us a chance and vote for the 201902-bitshares-ui worker id `1.14.165`.

Thanks for supporting us and the future progress of Bitshares!

Also posted on


Pages: [1] 2 3 4