The intent of the regproducer action is to register an account as a BP candidate.
I, EOS Cleaner, hereby nominate myself for consideration as an elected block producer.
If EOS Cleaner is selected to produce blocks by the eosio contract, I will sign blocks with my producer key and I hereby attest that I will keep this key secret and secure.
If EOS Cleaner is unable to perform obligations under this contract I will resign my position by resubmitting this contract with the null producer key.
I acknowledge that a block is 'objectively valid' if it conforms to the deterministic blockchain rules in force at the time of its creation, and is 'objectively invalid' if it fails to conform to those rules.
EOS Cleaner hereby agrees to only use my producer key to sign messages under the following scenarios:
I hereby accept liability for any and all provable damages that result from my:
I hereby agree that double-signing for a timestamp or block number in concert with 2 or more other producers shall automatically be deemed malicious and subject to a fine equal to the past year of compensation received and immediate disqualification from being a producer, and other damages. An exception may be made if EOS Cleaner can demonstrate that the double-signing occurred due to a bug in the reference software; the burden of proof is on EOS Cleaner.
I hereby agree not to interfere with the producer election process. I agree to process all producer election transactions that occur in blocks I create, to sign all objectively valid blocks I create that contain election transactions, and to sign all pre-confirmations and confirmations necessary to facilitate transfer of control to the next set of producers as determined by the system contract.
I hereby acknowledge that 2/3+ other elected producers may vote to disqualify EOS Cleaner in the event EOS Cleaner is unable to produce blocks or is unable to be reached, according to criteria agreed to among producers.
If EOS Cleaner qualifies for and chooses to collect compensation due to votes received, EOS Cleaner will provide a public endpoint allowing at least 100 peers to maintain synchronization with the blockchain and/or submit transactions to be included. EOS Cleaner shall maintain at least 1 validating node with full state and signature checking and shall report any objectively invalid blocks produced by the active block producers. Reporting shall be via a method to be agreed to among producers, said method and reports to be made public.
The community agrees to allow EOS Cleaner to authenticate peers as necessary to prevent abuse and denial of service attacks; however, EOS Cleaner agrees not to discriminate against non-abusive peers.
I agree to process transactions on a FIFO best-effort basis and to honestly bill transactions for measured execution time.
I EOS Cleaner agree not to manipulate the contents of blocks in order to derive profit from: the order in which transactions are included the hash of the block that is produced
I, EOS Cleaner, hereby agree to disclose and attest under penalty of perjury all ultimate beneficial owners of my company who own more than 10% and all direct shareholders.
I, EOS Cleaner, hereby agree to cooperate with other block producers to carry out our respective and mutual obligations under this agreement, including but not limited to maintaining network stability and a valid blockchain.
I, EOS Cleaner, agree to maintain a website hosted at https://eoscleaner.com which contains up-to-date information on all disclosures required by this contract.
I, EOS Cleaner, agree to set Japan as location, such that EOS Cleaner is scheduled with minimal latency between my previous and next peer.
I, EOS Cleaner, agree to maintain time synchronization within 10 ms of global atomic clock time, using a method agreed to among producers.
I, EOS Cleaner, agree not to produce blocks before my scheduled time unless I have received all blocks produced by the prior producer.
I, EOS Cleaner, agree not to publish blocks with timestamps more than 500ms in the future unless the prior block is more than 75% full by either CPU or network bandwidth metrics.
I, EOS Cleaner, agree not to set the RAM supply to more RAM than my nodes contain and to resign if I am unable to provide the RAM approved by 2/3+ producers, as shown in the system parameters.