Contracts Overview - Githubissues

money-infrastructure / doku

Documentation Co-op Money Infrastructure

6 stars 4 forks source link

Contracts Overview #2

Open hfhoyer opened 6 years ago

hfhoyer commented 6 years ago

Contracts - beeing a core element of the infrastructure - should be looked at from various points of view.

What is a suitable typology? How can various types be distinguished? Purchase sth., get a one time service, subscribe to a service, ...
Which are the most common and least complicated types to start with? Buy a quantity of a good with certain qualities Rent a service (mobility, accomodation, ...)
What are events, signals a contract can react to?
What are reactions, a contract should be designed for?

Contracts, events and reactions must be tested in an well defined enviroment for that purpose.

serapath commented 6 years ago

Don't mix contracts with coins. The more feature you put into one project - the less likely anyone will ever use it.

Make one project solve one issue well. Then find protocols that different systems can interact ...and competing solutions can try to find the best solution.

Do not re-invent ethereum.

hfhoyer commented 6 years ago

Thanks for the valid statements. I surely don't want to mix contracts with coins and wonder where I slipped into it. You are right with the impression, that in this stadium a wide scope is aimed at. One of the tasks for us is to let crystalize the "one issue - one solution" projects in the process of thinking about the desired infrastructure and understand the consequences. We surely are not here to re-invent ethereum nor any other wheel. We simply aren't convinced, that ethereum is what we want. We don't see smart contracts the same way. There is no DAO where we are heading to.