![]() ![]() The state hash portrays, and allows to validate, the place in the referral graph state machine that each browser should be signed into to run the campaign. The code hash validates that each participant in a given campaign is running the same peer code, safeguarding the contract's integrity while it runs off-chain. The code hash tells the browser where to find and load the Javascript and typescript from decentralized storage (IPFS at this point, FileCoin when it matures), ascertaining that all the browsers in the network are running the exact same version of the code for any single campaign - as these browsers must form an effective blockchain shard for managing the state per contract/campaign. A SmartLink URL contains two hashes, a code hash, and a state hash: The contract's interim state is also echoed to a POA plasma side chain for logging purposes mainly, where the finality states of the contracts are periodically persisted to the Ethereum POW layer1. This results in a fully scalable layer2 solution (as it does not depend on any server to run), which is also fully secure (as it only relies on cryptography to manage states). The state of the referral graph - which determines the economic distribution of reputation and monetary capital within the campaign - is managed solely by the cryptography and signatures handed down from browser to browser as these links are shared. ![]() The uniqueness of the 2key protocol is that it does not require any server to run. SmartLinks contain a cryptographically proven assertion of both the code for turning a browser into a node in the 2key shard running the contract (aka the "code hash"), as well as the dynamically changing state of this contract (aka the "state hash") - allowing each browser to sign it into the correct place in the state machine of the referral graph and the underlying smart contract.Ĭreating a SmartLink deploys a smart-contract shared by all participants - SmartLink creator, viewers, converters, and referrers - and, each time they open and share links, that smart-contract updates itself in real-time through the participants' regular web browser. Unlike what happens when sharing Web 2.0 URLs, sharing a 2key SmartLink connects the browsers the SmartLink passes through, creating an ad-hoc blockchain multi-party state-network composed of multiple participants - the HTTP clients (web browsers) which touched the link. The 2key protocol effectively embeds smart contracts and economic models into HTTP links, paving the way for introducing a generalized incentive model for online sharing. ![]() ![]() Embedded in regular URLs, the 2key protocol creates cryptographically signed links shareable across the web like Web 2.0 regular links. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |