Milestone: Kosu full system beta requirements

[hrharder]

Overview

This issue will serve as a place to record and track the necessary steps left to prepare the full Kosu system for a public beta. It will outline what that beta should look like, and refer each step to another issue.

Description

After all of the following issues are closed, we can consider the Kosu system ready for a public beta.

• Feature completion of the go-kosu MVP (Feature complete beta Kosu client #193 )
• Finalization of the bonding curve parameterization (Bonding curve parameterization and corrections #155)
• Finalization of the MVP contract system (Feature complete beta Kosu contract system #194)
• Update and complete the Kosu portal suite (Update and complete the Kosu portal suite #195)
• Plan a public, incentivized testnet (Plan a public, incentivized testnet #196)

And finally, after all of the above are complete:

• Announce Kosu: open testnet, make repo public, and new whitepaper (Formal Kosu announcement: open-source repo, announce testnet, publish WP #197)

Notes

Please use this issue as a place to discuss high-level concerns and considerations of a public beta system, but refer to the sub-issues for specific discussion on each item.