(this post is an automatic translation of this post on the english section)

來自 Bitshares UI 的過去幾年員工的團隊很高興提出 2020 年的新員工提案。

在此處閱讀完整提案

與往年相比，價格的下降使我們今年的改革了很多。

僅舉幾例（閱讀完整建議，以便更好地瞭解）

• 參加活動不支付差旅費
• 減少行政管理中注重發展的時間
• 每個開發人員商定的承諾開發時間
• 工作人員期間的三部分路線圖
• 縮短的時間段，只有 6 個月

通過這個職位，我們整個團隊尋求社區的回饋和支援。

問候馬格努斯
分配的組長

BitShares UI 的意圖是什麼？

BitShares UI 通常稱為參考 UI。它尋求完全如此：一個參考，試圖展示任何和所有功能，比特共用區塊鏈提供。易於上載、分叉和品牌。其理念是，閘道或業務有一個簡單的切入點，並能夠為他們提供關於如何與區塊鏈交互的示例代碼。這個想法不是為交易者等被描繪的目標群體提供簡單、流暢、用例的針對 UI。

任何人都應該能夠掌握功能集，同時能夠快速嘗試。當然，使用者體驗始終是 BitShares UI 開發的關鍵驅動因素之一，但它永遠不會像考慮到特定用例的定制 UI 那樣簡單或集中。

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!

The Bitshares UI (also known as reference UI) team wishes to present a new worker proposal to the community. Read the full proposal here


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


Also posted on

• https://steemit.com/bitshares/@sc-steemit/bitshares-ui-worker-proposal-for-2019-changes-ideas-and-future
• https://whaleshares.io/bitshares/@startail/bitshares-ui-worker-proposal-for-2019-changes-ideas-and-future

Signing on as a BitShares Witness

It's been about a month since I joined the group of witnesses for Steemit, and today I will take another step of signing on as a witness for BitShares.

Ever since I first started to use BitShares, which was shortly after I started to use Steemit, I have enjoyed every minute of it. This open market where you can trade openly without the risk of your assets is a groundbreaking and highly undervalued system.

The main reason I join in as a witness is because I wish to contribute to this wonderful system. Witnesses are conduits between the chain and the many users, it's our responsibility not only to make sure it runs smoothly but also to speak up when it doesn't for the users. We should listen in on the pace of the users on it.

My Steemit Witness Progress
My witness progress on Steem has been very successful so far and I keep witnessing about 10-12 block each day. My setup has been working very well with only two missed blocks so far, one being because I made a typo when I started, the second was a very temporary issue of network connection. All in all a pretty decent four weeks so far. Read My Steemit Witness Intent Post

Why me?
I'm an active member of the Gridcoin community and have been running the official blockexplorer for almost a year soon. As I said before I'm also an active witness for Steem and try to the best of my abilities to read up and keep track of changes and updates to the network and read up on the users expectations and wishes. I have my standard and wishes on how things should work, but it's also my obligation to assess the users needs and wishes. I frequently join the Beyond Bitcoin, BitShares and Gridcoin Mumble Hangouts and will do so in the future as well, which is a great place for updates and communication.

I have over 15 years of experience of running servers with various types of applications, this is nothing new to me and I'm quite diverse in ways to make sure things stay running even when I'm not around. My current setup alerts me if any of my systems services goes down or something isn't running, which I plan to keep working and refining on since it's vital that everything keeps running.

The presence of witnesses of BitShares is in my opinion too low; something that was raised in the latest BitShares Mumble session when we started to discuss things about changes that where needed on the network, only one witness was actually joining in. I'm not saying they are not very good witnesses, but we also need witnesses that are joining the crowd and listening in on the phase, something I will do.

In that same way I now wish to become part of the very best cryptocurrency exchange you can find. I will make sure to do my very best to keep it that way.

I like doing tutorials about these things; making the general public aware of the functionailty of systems and how they work.

- Why You Should Go Decentralized All In; A Quick Guide to BitShares DEX
- Quick Introduction to Steemit, or "What the Hell Is This Thing I'm On Now?
- Gridcoin Research and BOINC Explained
- Gridcoin and Distributed Work on BOINC

I am well aware that I will not witness any blocks until I reach one of the active witness positions
This doesn't stop me from doing my run for witness and I know that I will eventually, hopefully, be able to contribute to the network that I've grown to love. I will initially use the same setup system that I have for my Steem witness nodes, if it comes to the stage that they are required to run on their own servers I will be quick to react. The current servers are well equiped to handle the extra load of running another witness system.

The Income from Being a Witness
I see many great opportunities for supporting communities or projects; exploring new ways for progress. I wish to support the communities that are close to my heart, but also to expand the horizon of what can be done with cryptocurrency. I see things like Whaleshares by @officialfuzzy as a very inspiring project.

System Setup
I have two witness systems;
- One Main Witness
- One Backup Witness
In case of something happening, the backup witness is standing by. Both these systems run on a 6-core, 24GB Ram, 100% SSD VPS server.

Neither of these nodes are accessible from the outside, they can only witness the blockchain. All to make the systems secure enough.

Price Feed
I will be utilizing the BTS Tools from @wackou
Many thanks for this great tool.

How to vote for me
If you think that I will be suited for a BitShares Witness I would be very happy if you would vote for me. On BitShares my active witness is called @sc-ol

In the BitShares Wallet
1. Click "Account" on the top left
2. Click "Voting" in the left menu (4th in the menu)
3. Click "Witnesses" in the menubar on the voting page
4. Type in "sc-ol" in the textfield and press "Add"

Thank you for your support and trust!
I hope I can gain your trust in becoming one of the nodes on the witness list that You trust and rely on.

My BitShares Witness Proposal on Steemit