@ -638,7 +638,7 @@ vout.n-1: opreturn with oracletxid, prevbatontxid and data in proper format
The oraclesdata transaction is the most complex as it needs to find and spend the baton utxo, use the correct datafee and spend funds from the locked subscription funds. With the above, the oracles CC is complete and allows the creations of massively parallel data streams from multiple vendors that uses free market feedback via payments, ie. poorly performing providers wont get renewals.
I expect that at first, the data providers will just be dapp developers deploying a working system including the required data, but its structure allows open market competition. Of course, specific dapps could restrict themselves to using only publishers from a whitelist of pubkeys. The potential usecases for oracles CC is quite varied and limited only by the imagination.
I expect that at first, the data providers will just be dapp developers deploying a working system including the required data, but its structure allows open market competition. Of course, specific dapps could restrict themselves to using only publishers from a allowlist of pubkeys. The potential usecases for oracles CC is quite varied and limited only by the imagination.
Chapter 12 - limitless possibilities
As can be seen, CC contracts can do a wide range of things and since they are Turing complete, we know that this is true. However, what is more important is the added security gained from using a utxo based system. While in some ways it is more complex to have to deal with utxo, as can be seen by the above examples, it is either solved and made invisible at the rpc level, or actually used as part of the solution.
strUsage+=HelpMessageOpt("-tlskeypwd=<password>",_("Password for a private key encryption (default: not set, i.e. private key will be stored unencrypted)"));
strUsage+=HelpMessageOpt("-tlscertpath=<path>",_("Full path to a certificate"));
strUsage+=HelpMessageOpt("-tlstrustdir=<path>",_("Full path to a trusted certificates directory"));
strUsage+=HelpMessageOpt("-whitebind=<addr>",_("Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6"));
strUsage+=HelpMessageOpt("-whitelist=<netmask>",_("Whitelist peers connecting from the given netmask or IP address. Can be specified multiple times.")+
""+_("Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway"));
strUsage+=HelpMessageOpt("-allowbind=<addr>",_("Bind to given address and allowlist peers connecting to it. Use [host]:port notation for IPv6"));
strUsage+=HelpMessageOpt("-allowlist=<netmask>",_("Allowlist peers connecting from the given netmask or IP address. Can be specified multiple times.")+
""+_("Allowlisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway"));
strUsage+=HelpMessageOpt("-wallet=<file>",_("Specify wallet file absolute path or a path relative to the data directory")+""+strprintf(_("(default: %s)"),DEFAULT_WALLET_DAT));
strUsage+=HelpMessageOpt("-walletbroadcast",_("Make the wallet broadcast transactions")+""+strprintf(_("(default: %u)"),true));
strUsage+=HelpMessageOpt("-walletnotify=<cmd>",_("Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)"));
strUsage+=HelpMessageOpt("-whitelistaddress=<Raddress>",_("Enable the wallet filter for notary nodes and add one Raddress to the whitelist of the wallet filter. If -whitelistaddress= is used, then the wallet filter is automatically activated. Several Raddresses can be defined using several -whitelistaddress= (similar to -addnode). The wallet filter will filter the utxo to only ones coming from my own Raddress (derived from pubkey) and each Raddress defined using -whitelistaddress= this option is mostly for Notary Nodes)."));
strUsage+=HelpMessageOpt("-allowlistaddress=<Raddress>",_("Enable the wallet filter for notary nodes and add one Raddress to the allowlist of the wallet filter. If -allowlistaddress= is used, then the wallet filter is automatically activated. Several Raddresses can be defined using several -allowlistaddress= (similar to -addnode). The wallet filter will filter the utxo to only ones coming from my own Raddress (derived from pubkey) and each Raddress defined using -allowlistaddress= this option is mostly for Notary Nodes)."));
strUsage+=HelpMessageOpt("-zapwallettxes=<mode>",_("Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup")+
""+_("(1 = keep tx meta data e.g. account owner and payment request information, 2 = drop tx meta data)"));
// wallet filter for notary nodes. Enables by setting -whitelistaddress= as startup param or in conf file (works same as -addnode byut with R-address's)
