It's all about data -- global EtherCRM

It's all about data.

While smart contracts might be interesting, it feels like a solution in search of problems. It was better to start with normal contracts. Once the encrypted reference data (existing contracts with existing counterparties) is available plenty of things will become easy and obvious.

There could be something like a global EtherCRM (or master data network) based on Ethereum. From a customer perspecitve it might rather be EtherSRM (supplier relationship management). Customers and their contract partners (friends, banks, insurance companies, government, ...) would share the same "golden record" a.k.a. single source of truth. The customers would own the majority of the data.

No need to logon to a myriad of different websites with different usage patterns and no possibility to extract your data. You just have it in your EtherCRM software on your local devices.

And later on, in a next steps there might be smarter contracts. EtherCRM might notify you about contracts that are about to auto-renew and so on. It might recognize ToS that you would never accept and warn you.

This is just to give some ideas:
- bank account X @ bank 1 - main
- bank account Y @ bank 2 - special purpose
- bank account Z @ bank 2 - special purpose
- bank account T @ bank 3 - legacy
- seccurities account @ bank 1
- safe deposit box @ bank 1
- insurance policy for me
- insurance policy for the car
- insurance policy for house
- contracts with the state (e.g. social security number)
- Bitcoin Trading Account @ xxx
- Bitcoin Trading Account @ yyy
- rental agreement
- memberships - railway
- warranty - watch
- warranty - laptop
- warranty - ...
- web-subscriptions
- twitter
- gmail
- and dozens web accounts



  • romanixromanix Member Posts: 10
    TL;DR version: use Ethereum as the platform to build something like a single global distributed Siebel or that is not owend by a single company.
  • bjtbjt Member Posts: 17
    What would be the benefit of building something like that in the blockchain over itself? Perhaps both sides using the same source-of-truth data source can prevent the sorts of conflicts that involve tedious and stressful reconciliation.

    You'd want to store the data encrypted so casual browsers of the blockchain aren't discovering private business-to-business data.

    It's hard for me to imagine data intensive applications living in Ethereum without blowing up the size of the blockchain.
  • romanixromanix Member Posts: 10
    edited January 2014
    >> It's hard for me to imagine data intensive applications living in Ethereum without blowing up the size of the blockchain.

    Totally agree.
    The majority of data should reside outside Ethereum. Ethereum should cover contract ID and a means to sign, encrypt and decrypt data that leaves outside of it in a database* that is suitable for the respective use case.

    *) e.g. Dropbox datastore API for structured data
Sign In or Register to comment.