Skip to main content

3 posts tagged with "Gnosis Chain"

View All Tags

Core Devs Call - 2024/04/24

· 2 min read
Lion - dapplion
Hard Fork Coordinator
0xarmagan
Validator Comms Lead @ Gnosis
filoozom
Head Of Infrastructure @ Gnosis

Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.

Participants represent teams:

Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.

With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.

Missed the meeting? Catch the full recording on Gnosis Chain YouTube channel.

April 24, 2024

Client Team Updates

EL

  • Nethermind:

    • Working on Pectra, close to be ready for devnet0 (expected next week but will be announced at ACD)
    • Testing snap sync
    • Release planned for tomorrow
      • One potential bug remaining
      • Includes half-path and snap sync server for newly synced nodes by default
      • Snap sync in ~45 minutes with one peer
        • Nethermind ↔ Nethermind snap sync tested and working
        • Nethermind from Geth also worked
  • Erigon:

    • Working on Pectra
  • Geth:

    • Fully syncs on GC!
    • Serving snap sync, was able to snap sync a few nodes from it
    • 3 official Geth nodes were deployed an synced, can be used for snap syncing
      • Enodes to be sent in the Telegram group
    • Working on a rebase from a more recent Geth version
    • Block building seems to be broken
    • There’s a bug for full sync that needs to be addressed
    • Very positive in general, just some housekeeping left

Chain Infra

  • Gateway
    • Fixed the checkpointz endpoint
    • Observed OOM issues with 1.25.4
      • The node was killed and couldn’t resync after restarting
      • Will keep Nethermind posted with logs and information

Innovation

  • Shutter
    • Pushed a new update with the new curves in keypers
      • Working on integrating with that
    • Working on the libp2p stability issue (probably linked to GossipSub implementation)

Research

  • EIP-3074 + EIP-5003

Core Devs Call - 2024/04/18

· 4 min read
Lion - dapplion
Hard Fork Coordinator
0xarmagan
Validator Comms Lead @ Gnosis
filoozom
Head Of Infrastructure @ Gnosis

Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.

Participants represent teams:

Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.

With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.

Missed the meeting? Catch the full recording on Gnosis Chain YouTube channel.

April 18, 2024

Innovation

  • Account abstraction
    • https://eips.ethereum.org/EIPS/eip-3074
    • https://eips.ethereum.org/EIPS/eip-5003
    • 5003 would allow to fully transition from EOA to contract based accounts
      • If it’s not done in the next hard fork, the wait for the next one would be quite long and capabilities would not be “complete” for 3074
    • Would be interesting to hear about security considerations for 5003
    • Would be great to have 5003 in addition to 3074 to have the full account abstraction picture
    • Issues
      • Signing messages would still be possible
        • For permit transactions for example
          • Could be fixed by changing the ecrecover precompile for example, but then that would create a dependency on the state, which is a first for precompiles
      • Would break composability
        • The key would work on some chains as an EOA but wouldn’t work at all on others
      • This should be discussed in ACD calls
    • Bound historical data
      • https://eips.ethereum.org/EIPS/eip-4444
      • First step being considered by EF
      • Data
        • Portal
          • Dedicated team at the EF
          • It’s a parallel network of DHTs
          • You have to custody data based on your node ID
            • Issues
              • Can be spammed because you can mine IDs
              • Network needs sufficient replication in order not to lose data, which introduces more bandwidth and storage requirements
          • Not really proven to work yet
        • Bittorrent
          • Currently employed by Erigon (but not for EIP-4444)
            • They don’t have a state snapshot yet, meaning that you couldn’t sync without doing the whole current process
            • Will be possible with Erigon v3
              • Would only need to store historical data for RPCs or if you need to serve historical data
            • Each node creates checkpoints and seed that data
              • Hashes are added to clients to be able to find them
          • Should be sufficient, because the data can be verified anyways, and is unlikely to disappear because it’s easy to seed and back up
          • ERA1 format
        • IPFS
        • Swarm
        • Something else in the meantime?
    • Issues
      • Would create two different types of nodes, one of which would be parasitic
      • Can every CL sync deposits?
        • Lodestar not yet but every team supports this so they’ll implement it soon too
      • Syncing from a state rather than history is not possible on Erigon v2 and will require v3, which is yet to be released
        • Even in v3, historical data would be done in their proprietary format for now, and the client would require changes to support ERA1
    • Questions
    • What’s good enough for Gnosis Chain?
      • In terms of decentralization
    • Why do we care about historical data?
      • Tax reasons, archiving reasons, …
    • Requirements
      • Data doesn’t get lost
      • Newcomers are able to access that data eventually (not necessarily quickly)

Core Devs Call - 2024/04/10

· 2 min read
Lion - dapplion
Hard Fork Coordinator
0xarmagan
Validator Comms Lead @ Gnosis
filoozom
Head Of Infrastructure @ Gnosis

Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.

Participants represent teams:

Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.

With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.

Missed the meeting? Catch the full recording on Gnosis Chain YouTube channel.

April 10, 2024

Client Team Updates

EL

  • Nethermind:

    • Nothing new
      • Working on Pectra and half-path / snap sync server
  • Erigon:

    • Working on Pectra and Erigon 3
  • Geth:

    • Issue when the first blob was included in a block
    • Currently less than 2 weeks behind head
    • Then will test snap sync with a new geth node

Chain Infra

  • Gateway
    • No updates

Innovation

  • Shutter

    • The first Shutter transaction was included!
    • Transaction submitted to sequencer contract and included in a block
    • However, keypers are mocked for now, so the keys are hard coded
      • Because the keypers are still using the BN curve rather than BLS
      • Will require some changes from Shutter and then some testing
      • No ETA yet
    • The libp2p issue hasn’t been resolved yet, so the connection breaks after around half a hour
  • Verkle Tree Integration

    • Gnosis Chain has less time per block to do the transition
    • What’s the upper bound for time we can take to do the transition?
      • One issue is that snap sync is not entirely figured out for the transition yet, so syncing could be a bit more difficult (but at most nodes would have to sync 2 months worth of blocks, which on Gnosis Chain is not that huge of an issue, and it likely doesn’t change anything for Erigon at least)
    • Ethereum is targeting 2 weeks, on Gnosis Chain with identical parameters it would take 4x longer, so 2 months (mental math, to be checked)