This is a “Random Thoughts” blog, which means there are many points that I’ve left hanging (not finished cleanly). The blog’s objective is to stimulate discussion, so please don’t hesitate to comment. Identity is a hot topic for me with 15+ years of previous bosts. Here are a few updates … as well as my evolving perspective.
Happy After Thanksgiving! Hope everyone was able to enjoy a wonderful time with family and friends. Today is the 3rd installment of the series, a long blog. The next big network wave is here. Call it web 2.5 or 3.0, but the integration of payments into “everything” is a major event. Payments are the “trust layer” that TRANSFORM anonymous nodes providing uncertain service into known, defined and guaranteed service providers. Effective communities require value exchange and “trust”. The payment trust function enables networks to evolve from “cost free” discovery and information sharing, into transactional resource/service exchange: from read-write to read-write-execute. Sure we could call the wave “trust” but the only ubiquitous “trust network” is payments so I prefer to keep payment wave as the naming convention.
You need to be logged in to view the rest of the content. Please Log In. Not a Member? Join Us
Trust in a transaction. In another one of my favorite books (Design Rules: modularity) there exists the concept of trust between physical components of an integrated system. This book stands in contrast to Nobel Economists’ work in defining the “Firm” and organizational boundaries in Transaction Cost Economics (TCE). But the technical theory of modularity is amazingly consistent with the concepts of “boundaries” in TCE. In modularity, there are 4 core rules for separating technical components: