Skip to content

Release gate: v0.19-dev → v0.19 (waits for cross-repo E2E)#91

Open
MuncleUscles wants to merge 8 commits into
v0.19from
v0.19-dev
Open

Release gate: v0.19-dev → v0.19 (waits for cross-repo E2E)#91
MuncleUscles wants to merge 8 commits into
v0.19from
v0.19-dev

Conversation

@MuncleUscles

Copy link
Copy Markdown
Member

Standing release-gate PR: v0.19-devv0.19

This is a long-lived gate PR, not a normal feature PR. Do not merge ad-hoc.

Purpose

  • v0.19-dev is the active integration branch for the v0.6 fee work. Individual PRs merge into v0.19-dev and only need to pass normal repo CI — they are not blocked on the full cross-repo release train being green.
  • This PR is the single point where v0.19-dev is promoted to v0.19. It waits for cross-repo E2E (the release train) to go green before it is merged.
  • Other projects in the release train test against v0.19-dev.

How to use

  • Keep this PR open as the running view of "what would ship to v0.19".
  • Merge only when the full release-train E2E is green.

(Mirrors genlayerlabs/genlayer-consensus#1070.)

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0bc6220a-3e6c-42a1-a915-f6167e31b0cf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch v0.19-dev

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

… parity with genlayer-js (#90)

* feat(fees)!: estimation correctness, wait-for-decided semantics, v0.6 parity with genlayer-js

Mirrors genlayer-js feat/v06-fee-estimation-rework (same designer rulings):
- effective receipt gas price = max(quoteGasPrice(), eth_gasPrice); zero price on
  an enabled policy raises instead of producing a zero cap; effective execution
  budget floor = max(on-chain view, price x 306,192 gas local recompute)
- simulation-derived budgets no longer clobbered by the 100M default (floor vs
  observed x headroom); default constant documented as provisional w/ TODO(data)
- wait_until='decided'|'finalized' replaces status (legacy param mapped with
  one-time DeprecationWarning); new is_successful(tx) helper
- enum completeness: status 14 LEADER_REVEALING (fixes a KeyError crash mid-poll),
  VoteType 3 TIMEOUT / 4 NONDET_DISAGREE, v0.6 ResultType remap
- DEPLOY_CALL_KEY = bytes32(1) deploy sentinel; fee revert selector naming in
  send errors (InsufficientFees/MaxPriceExceeded/ExecutionBudgetExceeded/
  BudgetTooLow/RollupBudgetBelowFloor/FeeValueMustBeNonZero)

py-specific parity fixes:
- asimov chain config gains FeeManager/RoundsStorage/Appeals addresses (parity
  with js testnetAsimov)
- Studio floor-fallback formula unified with js (message-reveal leg included)
- appeal_transaction/top_up_and_submit_appeal auto-resolve the minimum bond when
  value is omitted (previously defaulted to 0 = guaranteed on-chain revert);
  top_up_fees now requires value

* ci: run tests on pushes to dev branches

tests.yml had no push trigger at all — merges to v0.19-dev got zero
post-merge CI.
…y key = bytes32(0) (#93)

The wildcard sentinel previously shared bytes32(0) with GenVM's natural
empty-method-name key (deploy, emit_transfer), making deploy-specific
Mode-2 allocations impossible. Per cross-team decision, the wildcard
moves to the untagged keccak256 of empty bytes
(0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470),
which is provably outside the derived-key space. DEPLOY_CALL_KEY drops
the bytes32(1) sentinel (GenVM ask withdrawn) and now equals
CALL_KEY_UNNAMED = bytes32(0), matching what GenVM actually emits.

Must land together with the consensus CALL_KEY_WILDCARD constant and the
node Mode-2 tree decode change in v0.6.
Admin merged after required repo CI passed; optional E2E app check is queued/non-blocking for dev-branch PRs.
* feat(vesting): add vesting staking actions

* feat(vesting): validator-leg actions (join/deposit/exit/claim, operator transfer, identity, wallet reads)

Mirrors the genlayer-js validator actions for the CON-607 Vesting.sol
surface: vesting_validator_join/deposit/exit/claim, operator-transfer
initiate/complete/cancel, set_identity (extra_cid str/hex handling as
in js), and get_validator_wallets/validator_wallet_count/
validator_deposited/is_validator_wallet reads.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant