The intent of the regproducer action is to register an account as a BP candidate.
I, rioblocks, hereby nominate myself for consideration as an elected block producer.
If rioblocks is selected to produce blocks by the libre contract, I will sign blocks with my producer key and I hereby attest that I will keep this key secret and secure.
If rioblocks 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.
rioblocks hereby agrees to only use my producer key to sign messages under the following scenarios: proposing an objectively valid block at the time appointed by the block scheduling algorithm pre-confirming a block produced by another producer in the schedule when I find said block objectively valid confirming a block for which rioblocks has received 2/3+ pre-confirmation messages from other producers
I hereby accept liability for any and all provable damages that result from my: signing two different block proposals with the same timestamp with my producer key signing two different block proposals with the same block number with my producer key signing any block proposal which builds off of an objectively invalid block signing a pre-confirmation for an objectively invalid block signing a confirmation for a block for which I do not possess pre-confirmation messages from 2/3+ other producers
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 imediate disqualification from being a producer, and other damages. An exception may be made if rioblocks can demonstrate that the double-signing occured due to a bug in the reference software; the burden of proof is on rioblocks.
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 rioblocks in the event rioblocks is unable to produce blocks or is unable to be reached, according to criteria agreed to among producers.
If rioblocks qualifies for and chooses to collect compensation due to votes received, rioblocks will provide a public endpoint allowing at least 100 peers to maintain synchronization with the blockchain and/or submit transactions to be included. rioblocks 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 rioblocks to authenticate peers as necessary to prevent abuse and denial of service attacks; however, rioblocks 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 rioblocks 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, rioblocks, 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, rioblocks, 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, rioblocks, agree to maintain a website hosted at rioblocks.io which contains up-to-date information on all disclosures required by this contract.
I, rioblocks, agree to set Rio de Janeiro, Brazil such that rioblocks is scheduled with minimal latency between my previous and next peer.
I, rioblocks, agree to maintain time synchronization within 10 ms of global atomic clock time, using a method agreed to among producers.
I, rioblocks, agree not to produce blocks before my scheduled time unless I have received all blocks produced by the prior producer.
I, rioblocks, 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, rioblocks, 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.