|
|
mining as a Service
incentivized, distributed hosting for any smart-Oracle Codiu§ 2.0 Smart-Oracles and other autonomous applications have been proposed to be able to pay for their own hosting. That creates a potential market, that could be capitalized on. Future markets would be hardware and redundancy. The evolution of mining as a Service would be a direct response to the emergence of this new market. mining as a Service: When you create an Oracle, it will signal to miners that it wants to grow roots. The miners have to cryptographically certify that they use a 'mining as a Service' software that the Oracle accepts. Crawling: The Oracle 'puts itself up for display' to be crawled and indexed by miners who run 'mining as a Service'. The Oracle will not display itself in a way that is predictable, it will display itself so that it could not be tracked by a miner. The miner could only come across it by chance, which prevents miners from hosting multiple nodes that target the same Oracle. Header: The Oracle defines a set of instructions for the miners. They define:
redundacy-as-a-Service The Oracle wants to be hosted with enough redundancy so that other smart-Oracles trust it. The Bitcoin blockchain was a first example of redundancy-as-a-Service. Blockchain-type redundancy might not be what most Oracles would want to pay for. An Oracle might grow the trust it requires with much much less redundancy than what a blockchain offers. Codiu§ 1.0 has pioneered the Idea that less-than-blockchain redundancy might have higher demand. The Codiu§ technology opens up a market for new types of redundancy-design-schemes. Depending on the security model required for a particular smart contract, the contracting parties can select the host or group of hosts they trust. A larger number of hosts can be used to add more redundancy, and thus security, to the contract’s execution and to ensure that the terms are carried out exactly as specified. [1] types of hosting: The Oracle defines what type of root-tree it wants to grow. An Oracle might define a block-chain like pattern, and be chained to other Oracles from a similar domain, or it might define a cluster-like pattern, where multiple instances of the same Oracle have to co-ordinate their input/ouput. 'mining as a Service' nodes will respond to the instructions from the Oracle, and grow whatever type of tree-like structure that the Oracle pays for. Examples from the scene: In the talk below, the founder of Ethereum mentions how Ethereum 2.0 might move towards more open design in what types of hosting can be provided to smart-documents. Why Codiu§ needs to bootstrap on mining-as-a-Service:
An implicit yet fundamental requirement of Codius’ trust-enabling infrastructure is the existence of a functioning ecosystem of competing hosting-providers that offer the execution of Codius-style containers/vm images. Only if such a market with a functioning competitive landscape is available, does the trust property of Codius’ infrastructure emerge.[2] [1] https://codius.org/docs/overview/for-contracts
[2] https://medium.com/@heckerhut/the-quiet-death-of-ripple-s-codiu-project-782c11a17c02 Evolution of Codiu§ 2.0
The evolution of technology uses a phenomena known as bootstrapping. Use one technology to build the next technology. 'mining as a Service' can bootstrap on Codiu§ smart-Oracles. The infrastructure can be built on smart-Oracles, that inter-communicate and co-ordinate a peer-to-peer network of miners, who in turn grow the redundancy-patterns that are required for trust between Oracles. Bootstrapping on Codiu§ here's a miner-Oracle, an Oracle that mines other Oracles, Synopsis: an Oracle host, eg. http://codius.host, could host Oracles that mine other Oracle-hosts, and a peer-to-peer infrastructure could be built using only this one building block: apps that don't work without cryptographic signatures and continuous payment references: |
|
