Bitcoin SV and this emerging form of Bitcoin Computing will be embedded into various forms of IT systems and business process. By its unique attributes, it will be chosen for providing critical functions within the infrastructure. From there it will eat away at traditional public cloud and traditional IT while it transforms existing business and government operations. As I see it, all existing paradigms are exposed to disruption. These legacy models are subject to what I describe here as the Bitcoin SV Paradigm. The internet is not the only dysfunctional system. The centralized public cloud that runs most of the internet for the past decade is a legacy architecture, but that is a discussion for another day.
If there is a need and new opportunity, there is a gap that will be filled. Here, I review the opportunities and consider the path to where the value proposition will be uncovered and ultimately realized. Creation of the paradigm involves dependencies. It will build in a series of waves, where each forms a horizontal layer ties into place what is then built above it.
First we have a transactional layer built just above the Bitcoin SV itself. In addition to the UTXOs offering a foundation for P2P interchange, we have Data Protocols emerging at this level. An exponential number of data protocols can be supported, which can be general purpose or application specific. The root construct is shared data which can then be combined with value transfer. Within an application, information can be given value and easily transferred or split up. We can expect to see further integration as applications associate data put there by other applications. There is enormous opportunity at this level, as protocol opportunities are nearly boundless.
Above a transaction layer, we have a stateful layer. The core constructs at this level are smart contracts and objects. At this point we are running or triggering code by using Bitcoin SV as an event-driven or time-driven driven information system. The combination of these first two layers enable the unique attributes of Bitcoin SV to scale functionally in many directions simultaneously. From the solution deployment perspective, people are able to build solutions that are backendless and serverless upon these two layers.
These first two layers form a foundation for consumerization of IT infrastructure. Here we have readily accessible APIs available. These enable a company of just a few people to build new applications. It's possible because applications are able to leverage existing attributes of the technology. We've seen social apps, various special purpose apps as well as basic gaming emerge in this regard. As I pointed out, these are also tied into what is utilizing their services from above.
The next layer above this is what I refer to as a framework layer. Two example constructs are Metanet and Token systems. These frameworks can be built into many different things, and intertwined into more things. Standardization is critical at this layer. It is where tools are built to manage mass amounts of smaller constructs into something that is purpose-built. Token systems might span from ticketing solutions to asset securitization. For Metanet, this goes beyond relating structured information. We think about a new world of internet users with private encrypted information is readily-integrated into a user's external interactions with proper access controls
A management layer resides about the framework layer. Administrative infrastructure might be required to track pools of complex constructs. The key concept at this level is lifecycle. There will be a need for constructs that enable registration and discovery for wider organizations of people, devices and applications. Additional organizational key management resides here, such as integration of the Nakasendo SDK for various capabilities. This can enable access control to data and authorization for operations. Ultimately, organizations desire functional automation which saves on person and support costs. There is a lot of opportunity for solutions in this area as adoption grows.
Next layer up is a commercial layer where the key organizing concepts are business processes. These are mission-built systems. Key constructs at this level would be reforming internal systems around triple ledger accounting and processes formerly reliant on legacy EDI. Companies that adopt new internal models that capture precise valuation designation and transfer will be found to have competitive profit and market edge. This layer will end up being realized in B2B transformation and new analytics that have astounding insight. Commerce will be increasingly managed according to facts rather than statistical predictions from Markov chains. The CRM industry and existing advertising models are eventually exposed to disruption as the relationships within B2C sectors can be transformed. Customer service relationships are mostly an 'append' use case where both parties would benefit by working from the same information.
The top layer is an enterprise layer which is policy-driven. The key constructs are governance, including automation of the business process layer underneath it, as well as audit and compliance. Regulations are not only established at this level, but systems are controlled to meet them. Additional realization targets are in areas such as supply chain and fraud detection. When new accounting systems are also tied with supply chain transformation, it might lead to a total displacement of the ERP industry.
The layers combine to achieve functional goals at an IT level, management and process goals within business and government, and ultimately serve organizational objectives. The specifics listed here are highlighting the incredible scale of opportunity.
___________________________________________________________________________
Summarized stack of layers described above:
Scope -->
Concepts -->
Built for -->
Realizations of Value
Applications / Users
Enterprise
Policy
Governance
Automation Audit & Compliance
Fraud Detection Supply Chain ERP
Commercial
Business Processes
Mission-Built
EDI Triple Ledger Accounting Procurement
Analytics B2B CRM Marketing
Management
Lifecycle of services for information
Purpose-Built
Service Registration Discovery Key management services
Access rights and Private user data
Framework
Standards for structuring information
Utility-built
Metanet Token Systems
Complex pools securities Users
Stateful
Event-driven
Interface-built
Objects Smart Contracts
P2P APIs Consumerized
Transactional
Data Protocols
Microtransactions
Shared Data
Social Apps P2P Basic E-commerce

 

0.0¢
0.0¢

No one has reviewed this piece of content yet
Comments
  earned 0.0¢
I hope you can find the influences all of your favorite BitcoinSV personalities. I'm just rounding out some of the context ;-)
0.0¢
   11mo ago