Forgive me if I mis-understand something,
but I think angleshares could be a natural part of 3I as an DAC,
just like the model they have proposed before.
For example, a possible model should be like this:
1. Every software project of 3I should have a new (angle)share/coin branched from the mother DAC share, and use coding as POW because the new project is directly benifited by coding itself. There is already some software available like Bithub to do this (https://github.com/WhisperSystems/BitHub)
2. This new share should accept as many currencies as possible, and donors acquire this new share in current exchange rate. In this way, this project is funded and the new share is backed by the donated money, just like fiat currencies are backed by gold.
3. To honor protoshare, protoshare holders should have 1:1 amount of this new share relative to their protoshares.
And these are also the three ways to obtain such new share
(i. e. 1. Mining by coding 2. Exchange by funding 3. obtain PTS)
The big picture: Everyone here is really keen on decentralization. But, there's a problem. Invictus is a centralized company. What to do? Well, because Invictus loves decentralized entities too, they came up with the idea of ProtoShares. ProtoShares does not benefit Invictus. They mine them just like everyone else does. If they sold the PTS, then they would have no stake in the future of DACs. Now, this is important. The future of DACs. Nothing guarantees that Invictus will be a part of that future. The projects are open source. Anyone can copy them and start their own DAC. If this happened, then it would also benefit the new company to honor the PTS social promise/contract. If they didn't, that company would have to start a whole new community fresh. They would have no network effect to propel them.
Now, Invictus needs funding. Every company needs funding. What to do? AngelShares gives any team of DAC developers a chance at funding. If the idea is good and the team is good, then funding should be easy to obtain. However, if the team starts to fail (this includes invictus) then people can stop buying the AngelShares and even trade them for another team of developer's AngelShares.
PTS is the glue that binds the DAC movement. AngelShares is the engine that move it forward. Technically, any team of Developers is free to release their AngelShares however they want. Invictus hasn't officially released their AngelShare model but it seems to be a system where you pay them to mine Invictus AngleShares for you.
Exactly. The key is every DAC/project needs funding.
As a donor, one may wanna be specific where his money goes:
1. To the DAC(3I) at kickstarting stage. This purpose is served well by PTS for 3I.
2. To a project of the DAC. This could be where angleshares go.
So PTS is like the root dorectory of '3I system' and angleshares are sub-folders.
In this way, angleshares should not be recognized as duplicate/dilution of PTS.
The problem with the whole Angelshares thing is we don't really want to trust a centralized company even if its 3I. Look at what happened to Bitfunder, or BTCT.
3I is in the United States just like those others were. If it's done following the Mastercoin model then it could work but if it's traded on an exchange then it might have legal vulnerability. I just don't know and this needs more planning.
Mining doesn't have any of these risks but I do understand the problem of raising funds and that you need some kind of Kickstarter.
To avoid trusting any centralized company, the angleshares could act much like bounty.
So funding is raised for the whole project and paid proportionally to the dev team that complete individual tasks of the project. If the original team leaves in the half way, another team can take over and earn the rest funding.
To achieve decentralization, the funding-for-bounty mechanism should be practiced by the angleshares software.
For example, the software could include the following features:
1.
Funding addresses to collect funding, and is held by the software mechanism but not anyone.
2.
the SPEC of the product. the SPEC should be recorded in individual tasks of the project.
3.
the dev team list. to be registered on this list, a dev team could propose the SPEC or accomplish at least one task of this project.
4.
a confirmation/voting mechanism to elect the dev team who gets the bounty/funding for each task.
So after the first task is done, the bounty could be the fuel for the second one.