Source Object - GlatzkopfGuru/LivingTokenNetwork GitHub Wiki

An source object represents one well defined object. Every object can exists only once in the system and it should not be possible to create a second instance by randomness or with bad aspects. Also when there is only one source object you need one or more central points the can register the location where an object is living. Without these central services you have to implement many broadcast and get an very high overhead in network traffic. Especially when the goal is to increase the network traffic in kind of a store. More or less like lorry on the street, the street is the biggest storage we have.

Most times when you compare the discipline computer science with engineering there are arguments like: In computer science there is no production step it consists nearly all of development. This is a strong argument and relies on the fact that you can copy everything as often as you want to share it. The same strategy is used from normal softwares you copy the data from the database give it to servers and clients they CRUD-Funtions and want to persist their changes. But when there is only one object as in the real world you do not need the frequent communication to the database or merging different changes.

Now is the question how to combine the inspiration by nature, that there is only a single object with the advantages of computer science.

• First idea, if you got a painting as one object every artist has to do his work sequential. But what is if the painting consists of many tiles? Then every artists can take a tile work on it or change it with other artist. And if all artist take a break, they can build the painting to one object. This is the advantage of computer science cause you can break up most objects in scopes or tiles. When they can't be break up in nature.