Any docs for zk counter pricing?

[doutv]

I have several questions about zk counter and I can't find relevent documents.

How you determine zk counter limits?

cdk-erigon/core/vm/zk_counters_limits.go

Lines 13 to 15 in 991fecf

	preForkId10TotalSteps = 1 << 23
	forkId10TotalSteps = 1 << 24
	forkId11TotalSteps = 1 << 25

How you set price for EVM operations?

take p256Verify precompile for example

cc.Deduct some magic numbers, how you get these numbers?

I think there is some pricing mechanism, which map EVM operations to zkevm-prover cost.

cdk-erigon/core/vm/zk_counters.go

Lines 1931 to 1968 in 991fecf

	func (cc *CounterCollector) p256verify(r, s, x, y *big.Int) {
	if r.Cmp(big.NewInt(0)) == 0 {
	cc.Deduct(S, 13)
	cc.Deduct(B, 1)
	} else if SECP256R1_N_MINUS_ONE.Cmp(r) == -1 {
	cc.Deduct(S, 15)
	cc.Deduct(B, 2)
	} else if s.Cmp(big.NewInt(0)) == 0 {
	cc.Deduct(S, 17)
	cc.Deduct(B, 3)
	} else if SECP256R1_N_MINUS_ONE.Cmp(s) == -1 {
	cc.Deduct(S, 19)
	cc.Deduct(B, 4)
	} else if SECP256R1_P_MINUS_ONE.Cmp(x) == -1 {
	cc.Deduct(S, 22)
	cc.Deduct(B, 5)
	} else if SECP256R1_P_MINUS_ONE.Cmp(y) == -1 {
	cc.Deduct(S, 24)
	cc.Deduct(B, 6)
	} else if x.Cmp(big.NewInt(0)) == 0 && y.Cmp(big.NewInt(0)) == 0 {
	cc.Deduct(S, 29)
	cc.Deduct(B, 8)
	} else {
	aux_x3 := new(big.Int).Exp(x, big.NewInt(3), SECP256R1_P)
	aux_ax_b := new(big.Int).Mul(x, SECP256R1_A).Add(x, SECP256R1_B)
	aux_x3_ax_b := aux_x3.Add(aux_x3, aux_ax_b).Mod(aux_x3, SECP256R1_P)
	aux_y2 := new(big.Int).Exp(y, big.NewInt(2), SECP256R1_P)
	if aux_y2.Cmp(aux_x3_ax_b) != 0 {
	cc.Deduct(S, 104)
	cc.Deduct(B, 15)
	cc.Deduct(A, 12)
	return
	}
	cc.Deduct(S, 7718)
	cc.Deduct(B, 22)
	cc.Deduct(A, 531)
	}
	}

[obynonwane]

@doutv we have a this in the doc

[doutv]

I see. However, after read through all docs and code from repo zkevm-prover, zkevm-rom, I still confused.

Why fork11+ can have larger zkCounter?

[revitteth]

@doutv fork11+ counters changes are due to changes in the prover. It may be worth raising the issue here: https://github.com/0xPolygonHermez/zkevm-prover. For now I will close.

[doutv]

sadly no one reply my issue in zkevm-prover. Are they focusing on the new prover?
0xPolygonHermez/zkevm-prover#880