first release requirements

[rainbreak]

Let's brainstorm what we need for MVP.

• single collateral type (ETH) - can add more, but this is mvp [no reason to limit this, given feeds]
• at least one working feed for ETH
• admin toolkit?
• finalise group auth
• flesh out UI

Pitch:

• 'simplecoin 1 is a token that is stable across mid scale variations in the price of Ether (and maybe other backing assets)'.
• 'simplecoin 1 is a toolkit for deploying and operating a collateralised token'

[dbrock]

Great initiative 👍

Should we try to call the two UIs the admin UI and the issuer UI?

[nmushegian]

I'm working on the pitch of 'simplecoin 1 is a token that is stable across mid scale variations in the price of Ether (and maybe other backing assets)'.

The "pitch" is just the rules, if you plan to claim simplecoin 1 then write them there, otherwise let the backers decide their rules

[rainbreak]

Should we try to call the two UIs the admin UI and the issuer UI?

+1. The transferrer UI is just ERC20.

[nmushegian]

We don't need just any ETH feed, we need one which is the owner's manual safeguard over some other reliable feed

[nmushegian]

you need... feed combinators

[rainbreak]

We don't need just any ETH feed

I think for MVP we can have a single feed. Anyone would be mad to trust such a system not to lose all their coins (and of course they can add their own feed), but it would demonstrate that all the bits work together.

By 'manual safeguard' do you mean 'fallback feed'?

[nmushegian]

the feed this contract uses only needs to be "live" a small fraction of the time, when the owner can manually sign off on a different feed. Remember originally the owner pushed price data and an expiration interval directly to the contract