Author Topic: Bounty requests: Market driven interest rate, BTC <-> BTSX  (Read 1359 times)

0 Members and 1 Guest are viewing this topic.

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BitShares: clains
Don't give up on them. Just keep pushing.  +5%

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
To fill the list up you might want to take a look here: https://bitsharestalk.org/index.php?topic=9075.0 .
I've better explained the ideas outlined in [7].

Offline oco101

  • Hero Member
  • *****
  • Posts: 586
    • View Profile
Absolutely 100% agree this should be done ASAP. Keep the good work drltc we all appreciate your contribution. Thanks.

Offline theoretical


In several different threads [1] [2] [3] there are various ideas for market-driven interest rates.

In several other different threads [4] [5] [6] [7] [8] [9] people express a desire to have some on-chain support for peer-to-peer trading of BitAssets against BTC.

In one particularly contentious thread, I got into a heated discussion with bytemaster [10] about whether writing detailed specifications and analyses such as [11] [12] [13] [14] is something that should be rewarded with I3 funds.  (The outcome of that discussion was that both bytemaster and I support the idea of rewards-after-the-fact for good ideas and careful analysis.  While I have received tips from several generous community members for my work -- for which I thank them -- I still have not received anything from bytemaster, which makes me question bytemaster's commitment to the rewards-after-the-fact paradigm.)

To address all three of these issues while conserving core developer time to focus on bugfixes and stability, I think I3 should post two new bounties:  One for a market-driven interest rate scheme, and one for an automated peer-to-peer BTSX / BitAsset-to-BTC market (with possible BTSX chain modifications to support escrow.)

There should be a pre-specified split between the phases of specification (30%), analysis / pointing out attacks, corner cases, unintended consequences of a specification (20%), blockchain / CLI implementation (30%), and GUI / web wallet implementation (20%).  In the case of the implementation phases, the bounty becomes payable when the implementation is merged into official I3 and/or dacsunlimited client.  In the case of a specification, the bounty becomes payable when an implementation based on that spec is committed or merged into the official client (regardless of whether the implementation was developed by core developers or by external developers hoping for the implementation bounty).  In case more than one person works on a phase and they can't decide how to split the bounty, bytemaster has the right to make final decision and the bounty payout is reduced (by 20%) to encourage the parties to make their own consensus.  In the case of analysis, each individual problem should be worth ~10% of the analysis budget (so ~2% of the total bounty amount for each problem).

Thoughts?

[1] https://bitsharestalk.org/index.php?topic=8422.0
[2] https://bitsharestalk.org/index.php?topic=8872.0
[3] https://bitsharestalk.org/index.php?topic=7865.0
[4] https://bitsharestalk.org/index.php?topic=9031
[5] https://bitsharestalk.org/index.php?topic=8986.0
[6] https://bitsharestalk.org/index.php?topic=8762.0
[7] https://bitsharestalk.org/index.php?topic=8818.0
[8] https://bitsharestalk.org/index.php?topic=8626.0
[9] https://bitsharestalk.org/index.php?topic=8393.0
[10] https://bitsharestalk.org/index.php?topic=8372
[11] https://github.com/drltc/bitbond-proposal/blob/master/airdrop.md
[12] https://github.com/drltc/bitbond-proposal/blob/master/bitbond.md
[13] https://github.com/drltc/bitbond-proposal/blob/master/btc-trade.md
[14] https://github.com/drltc/bitbond-proposal/blob/master/interest-0.4.13.md
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk