-
Notifications
You must be signed in to change notification settings - Fork 57
chain gasLimit keeps decaying #102
Comments
This is broken in Parity as well which I use for my pool. I reported the bug here: https://github.com/paritytech/parity-ethereum/issues/10242 I tried adjusting the minGasLimit on the musicoin.json to 4712387 but now I get this error: 2019-01-24 19:59:14 UTC Syncing snapshot 34/36 #0 22/75 peers 8 KiB chain 7 KiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 0 µs 2019-01-24 19:59:24 UTC Syncing #4205000 0x9d2a…30f7 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 0 Qed #4204999 15/75 peers 299 KiB chain 1 KiB db 0 bytes queue 16 MiB sync RPC: 0 conn, 0 req/s, 0 µs Then it continues to try syncing endlessly. I lowered it several times to match the offending blocks but there continue to give errors as I go: 2019-01-24 20:15:36 UTC Stage 1 block verification failed for 0xe04d…b5aa: Error(Block(InvalidGasLimit(OutOfBounds { min: Some(4698619), max: None, found: 4695412 })), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } }) 2019-01-24 20:15:37 UTC Imported #4205036 0xb169…6081 (0 txs, 0.00 Mgas, 1 ms, 0.51 KiB) + another 3 block(s) containing 0 tx(s) Any suggestions? |
there could be compatibility between v2.8 and v2.9, because of minGasLimit, we are investigating it. but do suggest run Parity with |
to keep the compatibility, we may need to hardcode targetGasLimit instead of raising minGasLimit which may cause hardfork. |
I'd just like to add that changing the chain specification mid-blockchain will almost certainly break new nodes' ability to sync from scratch - regardless of whether they're using parity or gmc. |
we may put it into next hard fork(which is also engaging other consensus change), so the gas floor will solidly protected. Or, maybe we should hardcode the flag to make sure miners execute it arbitrarily, good? |
started from the application layer, some smart contracts (like releases first, then artists) can't be deployed and reported "internal error” then traced down to "exceed block gas limit" like this:
Soon it's getting worse because there's no bottom line for gasLimit to decay(sort of, 5000 in current setting) , so if there are more blank blocks(0 gas used), it will be very dangerous the chain can do nothing.
The text was updated successfully, but these errors were encountered: