Skip to content

All Core Devs - Testing (ACDT) #85, June 29, 2026 #2133

Closed

Description

@marioevz

UTC Date & Time

June 29, 2026, 14:00 UTC

Agenda

Devnet status updates

  • glamsterdam-devnet-6 status
  • glamsterdam-devnet-7 planning

Spec updates

Discussions

EL Breakout

CL Breakout

Call Series

All Core Devs - Testing

Autopilot Mode

  • Use autopilot (recommended defaults for this call series)
🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

weekly

Use Custom Meeting Link (Optional)

  • I will provide my own meeting link

Display Zoom Link in Calendar Invite (Optional)

  • Display Zoom link in invite

YouTube Livestream Link (Optional)

  • Create YouTube livestream link

Activity

  1. added
    ACDType: All Core Dev calls - execution & consensus
    on Jun 22, 2026
  2. github-actions commented on Jun 22, 2026

    @github-actions
    Contributor

    ⚡ Protocol Call Resources:

    ✅ Zoom: Join Meeting
    ✅ Calendar: View | Add to Calendar
    ✅ Discourse: Discussion Topic

  3. rakita commented on Jun 29, 2026

    @rakita

    I would like to discuss the proposal to change EIP-2780 that I wrote about in Discord.

    Current EIP-2780 have a new mechanism added in case where tx target is not existing account that needs to be created, additional gas is consumed that can cancel the value transfer but it does not invalidate the transaction.

    There is additional rule where delegation is always charged as cold so we dont need to fetch the access list or auth list for intrinsic gas calc.

    The proposal is to unify this behaviour with how it behaves inside frame and leverage mechnanism that could halt transaction (tx is still valid) even before executing.

    So if this mechanism is propagated, it would mean:

    • Intrinsic gas for authorization list covers: signature recovery and tx bytes.
      • Runtime gas should cover warm/cold load and state creation.
    • Intrinsic gas if value is zero: should cover value change (We could even do runtime check for this).
      • Runtime gas should cover: cold loading of target, loading of delegation target (be that warm or cold), and target creationg (if it happens).
      • Intrinsic Tx create, would do similar (init code analysis charge, and warm accesses), and charge gas in rutime if account is not existing etc.

    In essence, intrinsic gas represents the minimum gas required for tx to be included. Other charges are incurred at runtime, and these charges can't invalidate the tx.

  4. github-actions commented on Jun 30, 2026

    @github-actions
    Contributor

    This meeting occurred more than 24 hours ago. Closing automatically.

  5. danceratopz commented on Jul 1, 2026

    @danceratopz
    Member
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ACDType: All Core Dev calls - execution & consensusprotocol-callAutomatically applied by issue template

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions