Author Topic: [Worker Proposal] 2020 Core Development (Part 1/2)  (Read 2399 times)

0 Members and 1 Guest are viewing this topic.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 365
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
[Worker Proposal] 2020 Core Development (Part 1/2)
« on: February 21, 2020, 10:35:56 pm »
Dear BitShares,

After spending some time with assembling original core team (what's left of it), discussing roadmap individually with holders and proxies and detailed review of 2019 worker, I came up with the following draft:

https://github.com/dls-cipher/workers2020-drafts/blob/master/2020-core-part1.md


Please read carefully and ask any questions if you have.

Chinese translation will be processed soon by Linda Tian and thread will be updated.



Worker details and roadmap has been updated. For more info click here.

Chee®s
« Last Edit: March 20, 2020, 08:34:11 am by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline binggo

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #1 on: February 21, 2020, 11:28:25 pm »
Wait part two.

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 365
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #2 on: February 21, 2020, 11:34:05 pm »
Wait part two.

2020 core worker = 1 year has 12 months.

Part 1 = 6 months worker.

Read the worker PLEASE before commenting.

Chee®s
Milos (DL) Preocanin
Owner and manager of bitshares.org
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline binggo

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #3 on: February 21, 2020, 11:52:51 pm »
Wait part two.

2020 core worker = 1 year has 12 months.

Part 1 = 6 months worker.

Read the worker PLEASE before commenting.

Chee®s

OK,  Part 2=4 months worker.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4285
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #4 on: February 22, 2020, 12:10:13 am »
I think it's too early to discuss the part 2 right now. Things can change a lot in 6 months. If part 1 worked well, we may start discussing part 2.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline binggo

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #5 on: February 22, 2020, 12:17:45 am »
I think it's too early to discuss the part 2 right now. Things can change a lot in 6 months. If part 1 worked well, we may start discussing part 2.

Got it.

Development for BSIP 64: Operational HTLC preimage length, HASH160 addition, and memo field (up to 12 hours)
Development for BSIP 69: Additional Assert Predicates (up to 25 hours)
Development for BSIP 74: Margin Call Fee Ratio (up to 60 hours)
Development for BSIP 77: Require Higher CR When Creating/Adjusting Debt Positions (up to 80 hours)
Development for BSIP 86: Share market fee to the network (up to 60 hours)

If we can make a small Mainnet Release for these BSIPs asap? in the next two months?

Offline bench

Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #6 on: February 22, 2020, 12:30:49 am »
Got it.

Development for BSIP 64: Operational HTLC preimage length, HASH160 addition, and memo field (up to 12 hours)
Development for BSIP 69: Additional Assert Predicates (up to 25 hours)
Development for BSIP 74: Margin Call Fee Ratio (up to 60 hours)
Development for BSIP 77: Require Higher CR When Creating/Adjusting Debt Positions (up to 80 hours)
Development for BSIP 86: Share market fee to the network (up to 60 hours)

If we can make a small Mainnet Release for these BSIPs asap? in the next two months?

I like the idea.
Be part of the change and vote for the bitshares-vision proxy!

Offline Bangzi

  • Sr. Member
  • ****
  • Posts: 314
    • View Profile
    • Steemit: Bangzi
  • BitShares: bangzi
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #7 on: February 22, 2020, 04:20:32 am »
Bitshares Chinese Forum
https://dpos.club

China block some web sites including Github. Users from China even have difficulty to post a reply in this forum.
Bitshares DEX - Over 1000 Coins, Buy, Sell, Transfer & List Any Coins |Free Signup Today: https://wallet.bitshares.org/?r=bangzi
Please Vote for My Witness: Bangzi |Witness Update: https://bitsharestalk.org/index.php?topic=26459.0

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1824
    • View Profile
  • BitShares: ebit
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #8 on: February 22, 2020, 04:47:51 am »
Quote
BSIP 70: P2P Lending (up to 400 hours)
I like this .We need new DEFI application scenario for spreading.
telegram:ebit521
https://weibo.com/ebiter

Offline bitcrab

  • Committee member
  • Hero Member
  • *
  • Posts: 1826
    • View Profile
  • BitShares: bitcrab
  • GitHub: bitcrab
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #9 on: February 22, 2020, 07:31:12 am »
BSIP64,69,70,80,85 haven't got a higher than BSIP-Threshold voting power, I don't think it's appropriate to include them.

and in my view some of them need more discussion, maybe it's better to put them into next part after voting up.
« Last Edit: February 22, 2020, 07:37:27 am by bitcrab »
Email:bitcrab@qq.com

Offline Digital Lucifer

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 365
  • 13 years of being Slackware abUser
    • View Profile
    • BitShares 3.0
  • BitShares: dls.cipher
  • GitHub: dls-cipher
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #10 on: February 22, 2020, 08:21:32 am »
Wait part two.

2020 core worker = 1 year has 12 months.

Part 1 = 6 months worker.

Read the worker PLEASE before commenting.

Chee®s

OK,  Part 2=4 months worker.

Will it be 4 months or 6 months and end in February 2021, as long as it's starts in 2020 its part of 2020 worker. Idea is to do Part 1 before we even start discussing Part 2. :)

I think it's too early to discuss the part 2 right now. Things can change a lot in 6 months. If part 1 worked well, we may start discussing part 2.

Got it.

Development for BSIP 64: Operational HTLC preimage length, HASH160 addition, and memo field (up to 12 hours)
Development for BSIP 69: Additional Assert Predicates (up to 25 hours)
Development for BSIP 74: Margin Call Fee Ratio (up to 60 hours)
Development for BSIP 77: Require Higher CR When Creating/Adjusting Debt Positions (up to 80 hours)
Development for BSIP 86: Share market fee to the network (up to 60 hours)

If we can make a small Mainnet Release for these BSIPs asap? in the next two months?

Even I love the idea of having 64, 77 and 86 asap as tomorrow - unfortunately the answer is no.

Why ?

1) Process, development structure and corporate execution/deliveries are a must. Randomness will not be allowed
       a) If you take a close look at the worker roadmap you'll notice there is suddenly 60-80 hours for Mainnet 4.0 Release that was scheduled for November 2019. After careful review, release is not fully prepared and first 7-10 days of worker will be going to that release. 3 Core devs has total availability for that period is 130 hours and we have to give it some testing. Abit will be more utilizing hours on Audit than on coding if we want to keep some process.
       b) there is no such thing as "asap Mainnet release" and it never was unless fix takes 1-5 hours and usually it's halt of the blockchain. Each development has to be implemented on the testnet upon delivery and tested for minimum period of 25-30 days prior to mainnet release. This worker has no budget or plan to change to process for 2 release as it states clearly little bit below under the section called "New Schedule for Releases". First sentence and current schedule pretty much confirms explanation.
       c) To avoid another a) in this worker - each dev will be assigned to BSIP's if worker becomes active. Their deliveries will be reflected through available hours we defined per each team member against ETA's on BSIP's/task being assigned to.

Bitshares Chinese Forum
https://dpos.club

China block some web sites including Github. Users from China even have difficulty to post a reply in this forum.

Much appreciated for link. Yeah, I completely lost though of GitHub with China GFW. Apologies will update the links in a moment.

Quote
BSIP 70: P2P Lending (up to 400 hours)
I like this .We need new DEFI application scenario for spreading.

Idea is yes, to not just satisfy holders but also to actually bring benefits and profits to the protocol as well.

BSIP64,69,70,80,85 haven't got a higher than BSIP-Threshold voting power, I don't think it's appropriate to include them.

and in my view some of them need more discussion, maybe it's better to put them into next part after voting up.

I'll quote important part of worker then ill explain myself

Quote: "This worker's agreement is crafted as a middle path between the desires of BTS core token holders, priorities for the blockchain and technology, as well as availability of core development team."

Explanation:
- Worker is crafted as balanced offer between holder's desires and necessities for the blockchain as protocol/tech to gain more visibility, profits and power in the real world outside our private interests.
- Worker includes needed amount of hours for documentation, BSIP's and discussions as well as delivery of each at the lower rate.
- Worker defines they will be delivered and released will be only the ones voted in. This is a development offer that satisfy both sides. What will be released its up to holders. What will be developed is result of holders desire and market demand.

If holders have issue with above terms it will certainly become a problem, since the terms are more fair than ever to the both BLOCKCHAIN and HOLDERS itself.

Now I've been hearing how bitassets are irrelevant and obsolete but i still see few BSIP's related to their mechanics and terms of use, so to stop pretending - let's just make a compensation and think about blockchain as well for once.


Chee®s
« Last Edit: February 22, 2020, 08:24:37 am by Digital Lucifer »
Milos (DL) Preocanin
Owner and manager of bitshares.org
Move Institute - RN: 2098555000
Murska Sobota, Slovenia, SI.

Offline JohnR

  • Committee member
  • Full Member
  • *
  • Posts: 94
    • View Profile
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #11 on: February 23, 2020, 08:36:54 pm »
Fully support this plan for Phase I of Core Development.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12914
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #12 on: February 24, 2020, 11:30:44 am »
+5%
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4285
    • View Profile
    • Steemit Blog
  • BitShares: abit
  • GitHub: abitmore
Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #13 on: February 27, 2020, 09:39:58 am »
I think it's too early to discuss the part 2 right now. Things can change a lot in 6 months. If part 1 worked well, we may start discussing part 2.

Got it.

Development for BSIP 64: Operational HTLC preimage length, HASH160 addition, and memo field (up to 12 hours)
Development for BSIP 69: Additional Assert Predicates (up to 25 hours)
Development for BSIP 74: Margin Call Fee Ratio (up to 60 hours)
Development for BSIP 77: Require Higher CR When Creating/Adjusting Debt Positions (up to 80 hours)
Development for BSIP 86: Share market fee to the network (up to 60 hours)

If we can make a small Mainnet Release for these BSIPs asap? in the next two months?
If to add features into 4.0.0 (and postpone the release date), I'd like to have "BSIP 85 Maker Order Creation Fee Discount" in it, since it's important to increase chain income.

Also "BSIP 87: Force Settlement Fee Ratio".

In addition, if to attract gateways building businesses on top of the chain, "BSIP 81 Simple Maker-Taker Market Fees" would be helpful.

Each of these changes is relatively small. However, more BSIPs means more development work and more time is needed.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Online sschiessl

Re: [Worker Proposal] 2020 Core Development (Part 1/2)
« Reply #14 on: February 27, 2020, 09:54:27 am »
I think it's too early to discuss the part 2 right now. Things can change a lot in 6 months. If part 1 worked well, we may start discussing part 2.

Got it.

Development for BSIP 64: Operational HTLC preimage length, HASH160 addition, and memo field (up to 12 hours)
Development for BSIP 69: Additional Assert Predicates (up to 25 hours)
Development for BSIP 74: Margin Call Fee Ratio (up to 60 hours)
Development for BSIP 77: Require Higher CR When Creating/Adjusting Debt Positions (up to 80 hours)
Development for BSIP 86: Share market fee to the network (up to 60 hours)

If we can make a small Mainnet Release for these BSIPs asap? in the next two months?
If to add features into 4.0.0 (and postpone the release date), I'd like to have "BSIP 85 Maker Order Creation Fee Discount" in it, since it's important to increase chain income.

Also "BSIP 87: Force Settlement Fee Ratio".

In addition, if to attract gateways building businesses on top of the chain, "BSIP 81 Simple Maker-Taker Market Fees" would be helpful.

Each of these changes is relatively small. However, more BSIPs means more development work and more time is needed.

First step would be to get them voted in. Please keep in mind that 1.14.158 - threshold-bsip is yet to be established, and at least I don't see it as the threshold for BSIPs as approved by BTS holders. If you do see it as the active threshold for BSIPs, please explain why.