| Khaos callback sender | Address |
|---|---|
| Ethereum Mainnet | 0x1c969CD76818769205F52BC25b93e2aFE05B386E |
| Ethereum Ropsten | 0x7654a20D1502471230a6C454c908c73cF040e22C |
| Arbitrum One | 0xc9f64eC1AADdD00ddf68fcDe85397d5C29197C95 |
| Arbitrum Rinkeby | 0x913404b5d02E9F685D793f23FD8774312668CE1B |
| Polygon Mainnet | 0xBc3DeffcC9916EAd1585999697cBD2A3361165fC |
| Polygon Mumbai 　　　　 | 0x2A655dd352c98260639726E60a04Ed804A0B790A |
Keep in mind that these addresses are subject to change in the future. If you use these addresses in your smart contract, you will also need to implement a mechanism to change their values.
Khaos is an oracle service designed to bring Internet data into blockchains while keeping secret information, such as secret tokens, under wraps. Initially, we will only support Dev Protocol, but we plan to open it up in the future.
Khaos has two interfaces, Authentication, and Oraclize. The authentication interface authenticates that the user is a credential holder and returns a unique public key. The oraclize interface brings data across the Internet to the blockchain while hiding secret information through public keys.
When Khaos receives an authentication request from a user, it executes an authentication method. The authentication request contains secret information for authentication (usually a secret token) and a message (like a user ID) that expects to be authenticated by that secret information. If the authentication method is passed, Khaos returns the public signature paired with the secret information. By retrieving the message with its public signature, it guarantees the authenticity of the message while hiding the secret information. An authentication method executed by an authentication request is freely extendable by the user. To read more detail, check: Khaos Startar Kit and a guide article
Created by SequenceDiagram.org
Khaos monitors some contract events in batches. The target of the monitoring can be any address that a user deploys to. The user-deployed contract makes an oraclize request to Khaos by emitting a specified event (a user-defined name. i.g., Query) according to the interface; when Khaos receives the oraclize request, it fetches some data from the Internet according to the event messages. The data is fetched into blockchains by calling the contract's callback method according to the event messages. The data fetching method executed by the oraclize request is freely extendable by the user. An authentication method executed by an authentication request is freely extendable by the user. To read more detail, check: Khaos Startar Kit and a guide article
