-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIP 007: Tiny Ethereum Network Transactions #8
Comments
1)A validator sends a transaction with the new token amounts, the new validator set deltas and the Fuse network txid that transmitted the signatures. (Fuse Network will still validate all the signatures).**
E.g. 10 nodes tx1 (11sigs / 30k tokens) is wrong Which values do you take? |
The transaction also locks some amount of ETH (it can be 1 ETH for now).** |
FIP7: Tiny Ethereum Network Transactions
Motivation
Every cycle, one validator need to “update” the Ethereum Network about two things:
Currently, it happens in two relatively expensive transactions.
The costs of these two transactions can take a toll on the validators and might be a good motivation for them not to transmit it at all.
The high gas usage that makes these transactions expensive are made for several reasons:
In this FIP we will suggest a way to reduce the gas usage of the transactions to a fraction of it.
Suggestion
First of all, we should merge the two transactions (new tokens amount, and new validator set) into one transaction.
Secondly, we will notify the network about the new validator set using deltas (newly added validators and removed validators) which can, in most cases be much less data to update.
Finally, we won’t send proof to be validated on-chain.
The last part will dramatically reduce the cost of the transaction but will create a major security breach.
To bridge that gap, we change the mechanism of Ethereum network updating from provable signatures to a delayed commit-challenge game between the validators in the following way:
This means that the validator set update is delayed and needs to be delayed in Fuse also. A new validator will start validating in the next-next cycle of the time he started staking, which can be 4 to 6 days in the current 2-days cycle time.
Cost analyses
An honest validator will send a cheap transaction that only sets the deltas and new amount of tokens along with the fuse transaction id with the signatures. No signature checks should accrue on-chain. The transaction fee should be reduced by about 80-90%.
The validator should reserve some ETH to commit to this end which will return to him in the next cycle.
If a non-honest validator will try to manipulate the new validator set, all of the other validator’s oracles will transmit another transaction that also cost much less than the original one and will be paid by the ETH committed by the rouge validator.
The text was updated successfully, but these errors were encountered: