TRADENET – a Future Economy built on the Bitcoin Blockchain


TradeNet: programmable internet of money, Trade Federation on the Bitcoin blockchain. Keys to establishing Tradenet is use of cyclic, reliable, iterative time cycles to process computational syntax drawn from a common syntax library -- a lexicon repository of brevity codes, data class types -- a TRADENET Rosetta Stone 



Mike Hearn, a U.K.-based Bitcoin developer who used to work at Google and now gives talks imagining a future economy driven by something called the TradeNet — a kind of giant automated marketplace, a crypto-secure mashup of Yelp, Craigslist, Uber, and eBay. The key to implementing a Tradenet System is the blockchain—a distributed method of tracking and transferring assets online without need of a trusted third party (such as a bank). Today, there is only one blockchain-based system widely used  -  Bitcoin itself. Backchannel LINK Bitcoin and the blockchain function as a medium of exchange, a store of value, a unit of account. Bitcoin adds digital, cryptographic, distributed server functions to currencies. Because it functions simultaneously as a currency, an asset and a platform, Bitcoin is better described as a global cryptoCAP (currency, asset, platform) -- a synergistic form of "crypto-capital" to unleash the full economic power of the networked age. Bitcoin makes money programmable. “MONEY IS SIMPLY DATA” - a simple way to measure and keep track of exchanges in value and wealth accumulation. Bitcoin aggregates data in a distributed global ledger accessible to anyone, and software. It is the first open platform for financial services.  Color coins represent stocks, bonds, currencies, properties. Source: Wired Magazine Reid Hoffman Why the blockchain matters 


Bitcoin's identity problem -- Why?  Organizational unit (computing) LINK From Wikipedia, the free encyclopedia In computing, an organizational unit (OU) provides a way of classifying objects located in directories, or names in a digital certificate hierarchy, typically used either to differentiate between objects with the same name (John Doe in OU "marketing" versus John Doe in OU "customer service"), or to parcel out authority to create and manage objects (for example: to give rights for user-creation to local technicians instead of having to manage all accounts from a single central group). Organizational units most commonly appear in X.500 directories, X.509 certificates, Lightweight Directory Access Protocol (LDAP) directories, active directory (AD), and Lotus Notes directories and certificate trees, but they may feature in almost any modern directory or digital certificate container grouping system. In most systems, organizational units appear within a top-level organization grouping or organization certificate, called a domain. In many systems one OU can also exist within another OU. When OUs are nested, as one OU contains another OU, this creates a relationship where the contained OU is called the child and the container is called the parent. Thus, OUs are used to create a hierarchy of containers within a domain. Only OUs within the same domain can have relationships. OUs of the same name in different domains are independent.. Examples: The name "organizational unit" appears to represent a single organization with multiple units (departments) within that organization.[citation needed] However, OUs do not always follow this model. They might represent geographical regions, job-functions, associations with other (external) groups, or the technology used in relation to the objects.

Examples include:

  • Department (e.g. human resources) within a corporation
  • Division (e.g. LifeScan, Inc.) that is owned by but separate from a parent corporation (Johnson & Johnson), although this would commonly be placed in a separate domain
  • Association (e.g. contractors) that is external to the organization.
  • To identify geographically distinct regions (e.g. Kansas City) the X.521 standard recommends a "locality" entry instead.
  • Job types or functions (e.g. managers, storage servers) that runs across all divisions of a company should be represented by an "organizational role" entry.