Author Topic: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)  (Read 5311 times)

0 Members and 1 Guest are viewing this topic.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Dear BitSharians,

One more time, my pleasure is to introduce another, yet vital proposal to the BitShares stake-holders and Community. Earlier this year, we welcomed Trusty.fund (open-source portfolio management app) to the BitShares blockchain. As most of Community knows, we had some progress together and on 13th of June Trusty decided to make an important step and fly in to Thailand for a real meet and discussion about BitShares eco-system. How it went you can see on the images below:





Now, thing that Community doesn't understand or fully appreciate about Trusty is that

   - Trusty.fund instead of developing/fixing existing React based UI, did complete from scratch build of new library for BitShares under the Vue Framework from original https://github.com/bitshares/bitsharesjs

It was not a fork, it was a fresh new Framework and library to be used by other developers, given to the blockchain as open-source https://github.com/TrustyFund/vuex-bitshares.

This is not just a building app on existing long-lasting tools but enabling new framework to utilize bitshares and enable more developers to join the eco-system. If nothing, it should be forked to BitShares, to properly advertise Vue support we have for our technology.

WORKER DETAILS

Worker is to finally provide to the Community DEX with mixing best of UI/UX from Bitfinex and Huobi to demand of our DEX users. We aim for top-notch/bleeding edge app solution for the requirements/demands shown over the time. Wallet/DEX would be coming in 2 templates, with 2 logos of choice (BitSharesDEX or BitSharesAPP). Both wallets would be fully responsive (mobile friendly) as you can see on current demos/examples of Trusty work within proposal documents. Its a budget worker proposal, its split in 2 sprints of 3 months each, with payments every 3 weeks, improved hour tracking system/software and complete new solution for the Community.

We do believe that BitShares development community will benefit very much from adopting the two most popular JS frameworks for creating UIs: React.js for corporate demand and Vue.js for the community. Seeing development peak of both would be a brighter future for BitShares.

The price and the hours are per max budget, and on this amount of people in the team with only 4 hours available daily to devote themselves to BitShares we came up to carefully estimated max of 6 months and 300,000.00 USD. We don't expect to hit that budget, but we do appreciate more space for the bugs and actual development to ensure max quality in final delivery.

WORKER DOCUMENTATION

First 3 months ( $150,000.00 USD max. Budget ) - Part 1

http://apasia.tech/bts-workers/bitshares-communitywallet-worker-p122018.pdf

Any funds not spent/hours not claimed will be returned to Reserve Pool from the respective Escrow.

Second 3 months ( $150,000.00 USD max. Budget ) - Part 2 - Final Delivery

http://apasia.tech/bts-workers/bitshares-communitywallet-worker-p222018.pdf

Any funds not spent/hours not claimed will be returned to Reserve Pool from the respective Escrow.

NOTICE:

Worker Part 1 would be going on-chain if positive feedback is shown. Worker Part 2 is current estimate and it's expected to be changed updated after the final report of Worker Part 1. There will be no on-chain proposal regarding Part 2, until all parties are satisfied with outcome of Part 1 and Worker status is set to done/expired.

DESIGN MOCKUPS

Trusty.team has in-house designer and used its own resources to create mockup for the proposal, by in-depth analysis of popular use-cases on global scale in crypto exchange design. Mockups are as presented, theme will be available in dark/light version. Landing page is only finished for proposal and no further changes will be done on mockup, unless worker gets on-chain and voted in. Please bare in mind that how your time costs money, as per proved professionalism our time cost nothing less. We are open-minded for suggestions that will only be in the limit of UX best practices and limits through responsiveness across all mobile/tablet devices.

Respectfully, for each suggestion that stake-holders and community try to point out to us, please explain in as much as possible descriptive way in order to get proper feedback from the team.

Design preview: http://apasia.tech/bitshares-community-ui-mockup/

Design of inner pages will be ready before Part 2, and progress will start if the Part 1 gets voted in.

WORKER - OPEN POSITIONS FOR BITSHARES DEVELOPERS

In the worker documentation you will find that 3 positions are opened. We would encourage any existing/known BitShares developer fitting these positions to get paid and create a positive mix of coding arts together with us. If there is no such interest, we have our own people ready, we were just trying to make it more friendly, as we (myself, apasia.tech and trusty.team) supporters of current UI Team worker as can be confirmed from other discussions or my personal votes - i'm selected Proxy of Trusty.

1. Project Coordinator / Coordination, QA and Testing
2. HTML and CSS developer
3. Frontend JS developer

ESCROW PARTNER

We've asked initially Move Institute, but we got response that escrow is still not ready. Meanwhile, during feedback and waiting for final response from Move Institute we would like to ask that if Institute is not available BitShares Blockchain Foundation steps in. Invoices on work from Thailand will have 4% withholding VAT only for IT services.


DISCLAIMER:
In order to balance between Trusty team and any reasonable request from the stake-holders, community or potential hiring for open positions, will from now on until end of worker go directly through me. I can be PM'em here, easily found in Telegram or directly here in the thread. Armen will manage project/team, while my position is management of the worker and requests to it/final reports from it.

Feedback is welcome!

Thanks.

« Last Edit: July 26, 2018, 07:52:29 pm by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline clockwork

  • Committee member
  • Sr. Member
  • *
  • Posts: 371
    • View Profile
  • BitShares: clockwork
All these long nights finally paying off!

This worker hits right at a point I too have been considering and that is that the reference wallet , by being the reference and thus having to support every single way of interacting with the bitshares platform, has ended up too complex for the average user.

A more community orientedalternative, such as the one described in this worker will help adoption imho and will also provide the reference wallet team with some breathing space.

I am unsure about the total budget of this worker. I think it might be overestimated but as it is a budget worker and trusty team has already delivered a working product, while DLs commitment to transparency and hate for unnecessary costs is well-documented, I am sure funds will be used with dilligence.

I also hope that there will be a lot of collaboration between UI teams (especially as pertains to the bitsharesjs library) to ensure even better results for both.

Looking forward to this.

Offline binggo

  • Hero Member
  • *****
  • Posts: 1548
    • View Profile
the below information must have.


The Function of the "buy" and "sell" must seperate to prevent false operation.
and the "market depth" chart can merge into the position of "trading view" chart.



https://www.binance.com/en/trade/EOS_BTC
https://gate.io/trade/eos_usdt



For reference only :)
« Last Edit: July 27, 2018, 07:30:10 am by binggo »

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
All these long nights finally paying off!

This worker hits right at a point I too have been considering and that is that the reference wallet , by being the reference and thus having to support every single way of interacting with the bitshares platform, has ended up too complex for the average user.

A more community orientedalternative, such as the one described in this worker will help adoption imho and will also provide the reference wallet team with some breathing space.

I am unsure about the total budget of this worker. I think it might be overestimated but as it is a budget worker and trusty team has already delivered a working product, while DLs commitment to transparency and hate for unnecessary costs is well-documented, I am sure funds will be used with dilligence.

I also hope that there will be a lot of collaboration between UI teams (especially as pertains to the bitsharesjs library) to ensure even better results for both.

Looking forward to this.

Many thanks Alex. Hopefully team will get some decent feedback. 



https://www.binance.com/en/trade/EOS_BTC
https://gate.io/trade/eos_usdt

Would be this design suggestion/similar examples or ... ?

Thanks.
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline ztoth

Great proposal. I am not a techie, so I did nut run deep into technical details, but I SUPPORT SUPPORT and SUPPORT all projects that enhance the UI/UX of BitShares. This is such a powerful platform, it should have millions of users by now if proper attention is paid to measures bringing widescale adoption. Mass adoption may only come from the masses, and everyday people like clean, responsive, easy ways to interact with the blockchain.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
the below information must have.


The Function of the "buy" and "sell" must seperate to prevent false operation.
and the "market depth" chart can merge into the position of "trading view" chart.



https://www.binance.com/en/trade/EOS_BTC
https://gate.io/trade/eos_usdt



For reference only :)

Now, once the post is having missing content, my reply would be:

We certainly acknowledge that the proposed design is an example of what the UI will look like, where still has a lot to be improved (which are designer hours in actual proposal), and space for feedback/changes as long as they are in the limits of reasonable time needed for implementation. This one definitely fits that reasonable feedback expected :)

Your comments are highly appreciated,

Thanks!
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Online sschiessl

Hello Trusty,

hope to see someone from your team soon too!

Is the idea to create a full featured UI, or to create a targeted (e.g. For Trader) easy to use UI that might skip features?

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Hello Trusty,

hope to see someone from your team soon too!

Is the idea to create a full featured UI, or to create a targeted (e.g. For Trader) easy to use UI that might skip features?

Stefan,

hope we can meet all together soon... at BitFest!

A2Q: No fully featured UI. Proposal PDF has clear statement that we encourage UI team to continue build of React.js based Corporate DEX, while Vue.js based Community DEX, where React.js would be focusing on implementation of all API functionalities, while Vue.js would be focusing on everyday needs of any stake-holder/trader/community member.

Hope it was clear enough, but in case, go through pdf in details, we are not interested in adventure of full UI nor it can be done within 6 months :)

Gnite and sleep well!
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4272
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
and please add a reference currency to every asset. eg. let me know the current $ price when I trade bts with whatever asset. I hate going to external marketcap sites just to find out what bts is worth to do the math
Join us on Telegram: https://t.me/btstalk

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
and please add a reference currency to every asset. eg. let me know the current $ price when I trade bts with whatever asset. I hate going to external marketcap sites just to find out what bts is worth to do the math

Hah, i hear you well. Its in the mockup already, but so sorry that mockup is still not at high quality so its very difficult to see. I will try to get higher quality/sharper version asap!

Until then, example as per mockups presented within worker (zoomed in and pointed out):



Cheers
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4272
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Join us on Telegram: https://t.me/btstalk

Offline kimchi-king

Thank you DL for presenting yet another outstanding proposal and I'm super excited to see that this one is directly related to the UI/UX of the BitShares DEX. I know this will be specific to the general community's needs, but that's exactly what we need to reach the masses.

Thank you to everyone who has already asked some quality questions. I look forward to seeing this proposal approved by the community so DL and his team can finally provide us with the UI we deserve.

You have my full support for this proposal and let me know if there's anything I can do to help out.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
« Last Edit: July 31, 2018, 11:14:09 am by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4272
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
Join us on Telegram: https://t.me/btstalk

Online sschiessl

That's a great article for the basics!

The real war begins when you do routing, observers and more sophisticated architecture. In both cases you can do that an ugly and a less ugly way ;)

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
That's a great article for the basics!

The real war begins when you do routing, observers and more sophisticated architecture. In both cases you can do that an ugly and a less ugly way ;)

Yeah, I've came with my learning to point of reading on "Routers" of both React.js and Vue.js framework, and from perspective of a noob/beginner - Vue is winning for now. One page, structured content, from a to z, while React provides much more (including trainingcenter) but the structure of it is for someone more skilled than newbie. Again publicly, Vue is supported more by Asian community, so probably there is TrainingCenter in Cantonese/Chinese that i can't google up.

@fav

Very nice read for beginners, I wish I've started from here, would be understanding difference in basics much more easy. Should share it on Steem if you haven't done so, a lot of React/Vue potential there.
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline JohnR

  • Committee member
  • Full Member
  • *
  • Posts: 91
    • View Profile
As an otherwise well-rounded individual, I do not know a ton about programming.  But I am immediately drawn to this phrase in OP
 


   - Trusty.fund instead of developing/fixing existing React based UI, did complete from scratch build of new library for BitShares under the Vue Framework from original https://github.com/bitshares/bitsharesjs

It was not a fork, it was a fresh new Framework and library to be used by other developers, given to the blockchain as open-source https://github.com/TrustyFund/vuex-bitshares.

This is not just a building app on existing long-lasting tools but enabling new framework to utilize bitshares and enable more developers to join the eco-system. If nothing, it should be forked to BitShares, to properly advertise Vue support we have for our technology.


-   

This is an excellent example of the value proposition of free (open) software.  Permission-less creativity.  BitShares deserves constant updates on the back-end technology front.  I also believe BTS does not need a UI makeover as much as it needs more options.  The fact that most service providers / gateways on BitShares use a clone of the original UI shows the lack of creativity that can set in when we, as a community, don't voice our intents to keep things fresh.

These mock-ups look very nice I must admit - although the aesthetics are up to the individual user.  What I can say for sure is that mobile usage is critical.  For myself, I would not be that interested in entering limit orders on a mobile device.  That being said I can see mobile is many people's only interaction with the DEX.  And I use Trusty's android wallet regularly - so I can vouch for the team's product delivery.  I look forward to this proposal's success and a prosperous partnership between BTS and the Trusty team.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12896
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Given the amount of efforts already placed into developing code and putting it into github already, I fully support the efforts undertaken by the trusty team!
The VueJS code looks amazing!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline R

  • Hero Member
  • *****
  • Posts: 756
    • View Profile
I like the effort to implement the UI using an alternative to ReactJS, however could you elaborate on the final product? Will it result in a stand-alone client or a web wallet? Will there be a maintenance period after its completion, or would this require an additional worker proposal?

Do you think once this is completed that it'd be wise to investigate additional alternative frameworks than react/vue? An implementation of BTS for all the major frameworks?

---

Probably off topic, but a cool idea would be a UI toolkit for integrating the entire BTS DEX into CEX websites, rather than limiting themselves to single tokens they could offer direct access to the BTS DEX. Probably not realistic though?  :-\

---

The only thing that has me apprehensive about delivery is that the bitshares web page still has not changed despite being transfered ownership a few months ago?
« Last Edit: August 04, 2018, 11:40:21 am by Customminer »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12896
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Probably off topic, but a cool idea would be a UI toolkit for integrating the entire BTS DEX into CEX websites, rather than limiting themselves to single tokens they could offer direct access to the BTS DEX. Probably not realistic though?  :-\
This is what `bexi` is all about
https://github.com/blockchainbv/bexi
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
UPDATE

Thanks to Escrow Partner, BitShares Blockchain Foundation, I would like to announce that worker has been placed on chain and its currently available for VOTING.

Worker id: 1.14.117
Accounting by Escrow: https://workers.bitshares.foundation/201808-trusty-community-ui-p1
Worker Publication by Escrow: https://www.bitshares.foundation/workers/2018-08-trusty-community-ui-p1


Many thanks for support and respect shown, we are all very grateful for feedback received here.

On behalf of APT and Trusty,

Let the Voting BEGINS!
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline clockwork

  • Committee member
  • Sr. Member
  • *
  • Posts: 371
    • View Profile
  • BitShares: clockwork
Voted

Online sschiessl

Voted

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4272
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
voted
Join us on Telegram: https://t.me/btstalk

Offline kimchi-king

Voted!

Online abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3879
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #25 on: September 12, 2018, 12:07:58 pm »
This worker is receiving funds now. Any update please?
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #26 on: September 13, 2018, 04:43:58 am »
Update:

Thanks to everyone + special thanks to whoever was yesterday deciding vote on worker to gets voted in.

We are creating today on github repository and team will start work/logging hours no more late than this Friday. Commits will be available only to the BitShares github team until admin decide/review what is for public release.

@abit

Pinged you on telegram - re Github Repository, Fabian is away, please check when you can.

« Last Edit: September 13, 2018, 04:48:26 am by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 2274
    • View Profile
  • BitShares: jademont
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #27 on: September 13, 2018, 04:54:20 am »
Good to see that we have a professional team do professional work, expecting your output!
BTS committee member:jademont

Offline Chris4210

  • Sr. Member
  • ****
  • Posts: 431
  • Keep Building!
    • View Profile
    • www.payger.com
  • BitShares: chris4210
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #28 on: September 15, 2018, 05:57:23 pm »
I am also voting for this proposal. I am looking forward to the first results and updates for a interface update.
Vote Chris4210 for Committee Member http://bit.ly/1WKC03B! | www.Payger.com - Payments + Messenger | www.BitShareshub.io - Community based fanpage for the BitShares Blockchain

Offline R

  • Hero Member
  • *****
  • Posts: 756
    • View Profile
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #29 on: September 29, 2018, 05:24:20 pm »
Update:

Thanks to everyone + special thanks to whoever was yesterday deciding vote on worker to gets voted in.

We are creating today on github repository and team will start work/logging hours no more late than this Friday. Commits will be available only to the BitShares github team until admin decide/review what is for public release.

@abit

Pinged you on telegram - re Github Repository, Fabian is away, please check when you can.

How are things coming along? We were discussing this WP at the bitfest event last week, looking forwards to the developments.  :)

Online abit

  • Committee member
  • Hero Member
  • *
  • Posts: 3879
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #30 on: September 30, 2018, 12:04:23 pm »
Update:

Thanks to everyone + special thanks to whoever was yesterday deciding vote on worker to gets voted in.

We are creating today on github repository and team will start work/logging hours no more late than this Friday. Commits will be available only to the BitShares github team until admin decide/review what is for public release.

@abit

Pinged you on telegram - re Github Repository, Fabian is away, please check when you can.

How are things coming along? We were discussing this WP at the bitfest event last week, looking forwards to the developments.  :)
https://github.com/bitshares/bitshares-community-ui
https://github.com/bitshares/vuex-bitshares
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Re: [Worker Proposal] Community UI proposal by APT (on behalf of Trusty team)
« Reply #31 on: September 30, 2018, 03:54:10 pm »
Update:

Thanks to everyone + special thanks to whoever was yesterday deciding vote on worker to gets voted in.

We are creating today on github repository and team will start work/logging hours no more late than this Friday. Commits will be available only to the BitShares github team until admin decide/review what is for public release.

@abit

Pinged you on telegram - re Github Repository, Fabian is away, please check when you can.

How are things coming along? We were discussing this WP at the bitfest event last week, looking forwards to the developments.  :)
https://github.com/bitshares/bitshares-community-ui
https://github.com/bitshares/vuex-bitshares

Many thanks Abit! :)

Things are going very well for first 2 weeks of actual work. Getting proper traction and management of tasks/issues/hours. Actually, hese 2 weeks (hours against issues) - reports are coming up tomorrow on Github and i'll post direct links here with legend to it :D

Cheers
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 323
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
I know that nobody posted here anything for half year, but we did updates in ecosystem groups and maintained GitHub very well while worker was in/active.

Now, with my sincere apologies to entire ecosystem and its holders, a brief summary and reasoning behind the delays.

AP Asia Tech and Trusty Team has been contracted by the blockchain through worker that was escrowed with BBF in order to deliver simple (more user-friendly) trading desktop/mobile version of BitShares UI, named Community UI (as current reference Wallet/UI hosts all the functionalities of the blockchain).

To remind everyone on specific/important details of the worker/project:

- Original project was 300,000.00 USD for 6 months + Escrow to deliver written from scratch Trading Community UI web/mobile dapp in Vue.js framework, influenced by well UI/UX organized apps from CEXes (Bitfinex, Huobi, Binance). Due to amount asking for it, it was decided to be split in Part 1 and Part 2 each asking for 150,000.00 USD.
- VueX library from Trusty was forked and given as property to Official BitShares Github - more details https://github.com/bitshares/vuex-bitshares?organization=bitshares&organization=bitshares
- BitShares Community UI repository was created and work started as can be seen https://github.com/bitshares/bitshares-community-ui
- Online demo/deployment of work done over the period of 4 months (3 months + bug fixes pro bono) is available at

http://testing.community-ui.bitshares.org/ (testing repo deployment - newer Vue)
http://staging.community-ui.bitshares.org/ (staging/default repo deployment - older Vue)

AP Asia Tech did overview of project for entire 4 months, did payouts as per Team reporting and supported revival from GS of BitUSD by doing instant settlement with all payouts received.

Worker started in period of a really low price for BTS and ended up having more staked than it ever needed.


Overview of accounting for the worker, as it can be seen on BBF Workers website:

- Total asked: 155,000.00 USD
- Total paid: 135,888.40 USD ( - 10,000.00 USD Escrow )

However, worker saved through price shifting and GS = 1,647,995.28533 BTS ~ 100,000.00 USD at current price of BTS.

Issues of the past:


- Original team was practically dissolved in last 30 days of worker. One of lead JS devs got seriously ill and was unable to perform any hour, having sudden replacement and help of
Keegan Francis (thanks for hours jumped in). Noemi QA tester and internal team manager got off for private/family reasons and as any other organization, few others start taking their ways. Adding internal competition in decentralization between new devs and old devs within Trusty was already hard enough for both me or their manager Armen to keep up with.

Team was not ready/complete to dive in to the Part 2 without proper diligence and re-estimate, and we were still sitting in GS - price of a BTS was degraded to that point that it would be not reasonable asking for a worker in that period.

New Status:

I've had personal visits in Thailand in the meantime from old Trusty developer Anton, few calls with Armen, and after detailed estimate - new/old team is ready to perform and deliver final Part 2 of Community UI.

Howerever, team is asking for new basic terms for Part 2 worker:

- Instead of 155,000.00 USD, team would be asking for just 115,000.00 USD + Escrow.
- Permission of BTS Holders that escrow transfers remaining balance of BTS from Part 1 to Part 2 and worker actually asks for a difference needed from chain (prevent double spent fees for vesting, trading, transfers, burnback).
- 2 months + bug fixes to deliver promised work.

Final steps would be Trading Graph, Fix with multi-account wallets, Gateways/market selection, white template and UI/UX improvements on fonts/responsive.

There is no worker drafted for any official publication, all I'm here is asking BTS holders and proxies are they are interested to see this job done.

P.S. I'm known for many things, especially being late and lack on reporting, but never failed to deliver a single task, and this project was demanding more than just developers delivery, but management through completely decentralized team, organization, reporting, overview, internal issues, drawbacks, bugs, market/price issues, and couldn't be delivered (P2) earlier even for discussion no matter what.

« Last Edit: June 14, 2019, 01:12:20 pm by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org through Consensus
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12896
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
+5% for transparency and accountability!
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline clockwork

  • Committee member
  • Sr. Member
  • *
  • Posts: 371
    • View Profile
  • BitShares: clockwork
I know that nobody posted here anything for half year, but we did updates in ecosystem groups and maintained GitHub very well while worker was in/active.

Now, with my sincere apologies to entire ecosystem and its holders, a brief summary and reasoning behind the delays.

AP Asia Tech and Trusty Team has been contracted by the blockchain through worker that was escrowed with BBF in order to deliver simple (more user-friendly) trading desktop/mobile version of BitShares UI, named Community UI (as current reference Wallet/UI hosts all the functionalities of the blockchain).

To remind everyone on specific/important details of the worker/project:

- Original project was 300,000.00 USD for 6 months + Escrow to deliver written from scratch Trading Community UI web/mobile dapp in Vue.js framework, influenced by well UI/UX organized apps from CEXes (Bitfinex, Huobi, Binance). Due to amount asking for it, it was decided to be split in Part 1 and Part 2 each asking for 150,000.00 USD.
- VueX library from Trusty was forked and given as property to Official BitShares Github - more details https://github.com/bitshares/vuex-bitshares?organization=bitshares&organization=bitshares
- BitShares Community UI repository was created and work started as can be seen https://github.com/bitshares/bitshares-community-ui
- Online demo/deployment of work done over the period of 4 months (3 months + bug fixes pro bono) is available at

http://testing.community-ui.bitshares.org/ (testing repo deployment - newer Vue)
http://staging.community-ui.bitshares.org/ (staging/default repo deployment - older Vue)

AP Asia Tech did overview of project for entire 4 months, did payouts as per Team reporting and supported revival from GS of BitUSD by doing instant settlement with all payouts received.

Worker started in period of a really low price for BTS and ended up having more staked than it ever needed.


Overview of accounting for the worker, as it can be seen on BBF Workers website:

- Total asked: 155,000.00 USD
- Total paid: 135,888.40 USD ( - 10,000.00 USD Escrow )

However, worker saved through price shifting and GS = 1,647,995.28533 BTS ~ 100,000.00 USD at current price of BTS.

Issues of the past:


- Original team was practically dissolved in last 30 days of worker. One of lead JS devs got seriously ill and was unable to perform any hour, having sudden replacement and help of
Keegan Francis (thanks for hours jumped in). Noemi QA tester and internal team manager got off for private/family reasons and as any other organization, few others start taking their ways. Adding internal competition in decentralization between new devs and old devs within Trusty was already hard enough for both me or their manager Armen to keep up with.

Team was not ready/complete to dive in to the Part 2 without proper diligence and re-estimate, and we were still sitting in GS - price of a BTS was degraded to that point that it would be not reasonable asking for a worker in that period.

New Status:

I've had personal visits in Thailand in the meantime from old Trusty developer Anton, few calls with Armen, and after detailed estimate - new/old team is ready to perform and deliver final Part 2 of Community UI.

Howerever, team is asking for new basic terms for Part 2 worker:

- Instead of 155,000.00 USD, team would be asking for just 115,000.00 USD + Escrow.
- Permission of BTS Holders that escrow transfers remaining balance of BTS from Part 1 to Part 2 and worker actually asks for a difference needed from chain (prevent double spent fees for vesting, trading, transfers, burnback).
- 2 months + bug fixes to deliver promised work.

Final steps would be Trading Graph, Fix with multi-account wallets, Gateways/market selection, white template and UI/UX improvements on fonts/responsive.

There is no worker drafted for any official publication, all I'm here is asking BTS holders and proxies are they are interested to see this job done.

P.S. I'm known for many things, especially being late and lack on reporting, but never failed to deliver a single task, and this project was demanding more than just developers delivery, but management through completely decentralized team, organization, reporting, overview, internal issues, drawbacks, bugs, market/price issues, and couldn't be delivered (P2) earlier even for discussion no matter what.

+5%

We really need to complete this otherwise it would be a waste of part 1 funds.

The Vue-based setup would make it easier for new devs to join in/modify for other purposes as well.

Seeing as there are leftover funds from the original worker and part 2 will require much less funding, I hope all proxies lend their support to this.

Offline ztoth

Great efforts, need this kind of stuff around BitShares. More of it, even more... Go guys!