Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Consensys team is suggesting a re-evaluation of defaults in the new year. We are also simultaneously suggesting adding “profiles” to Besu that when set, provide defaults that serve certain use-cases or sets of users. 

One more note. When setting a profile, any other options the user configures that fall underneath that profile will be overwritten. For example, if a user sets --profile=enterprise and --sync-mode=FULL it will override the sync mode flag from FAST  to FULL.

Defaults, no profile

When starting up Besu with no additional commands ./bin/besu , the following defaults are suggested:

  • Sync Mode: SNAP
  • Data-storage-format: BONSAI
    • Full flat DB by default Xsnapsync-synchronizer-flat-db-healing-enabled=true (DELETE THIS FLAG → Safety concerns Gary Schulte
    • Full flat DB will be default for all BONSAI users
    • bonsai-limit-trie-logs-enabled=True
    • bonsai-historical-block-limit=512
  • Network: Mainnet (should we specify a testnet for first time users without a config?)
  • Max-peers: 50 (in line with Geth and other clients)
  • -Xp2p-peer-lower-bound=25
  • Tx-pool: Layered (already default)

...

The Consensys Team is suggesting 4 profiles with their own defaults:

  • Selfish-staker
  • BenevolentConsiderate-staker (name?)
  • Private-network / Enterprise (?)
  • RPC Provider
    • Archive - Awaiting Bonsai Archive to change defaults
    • Near-head - Standard full node

...

  • Sync mode: CHECKPOINT
    • Lowest disk, quickest sync, cannot serve old block data, can serve all world state data
  • Data-storage-format: BONSAI
    • bonsai-historical-block-limit: 128Trie-log-pruning: Enabled
  • Max-peers: 2025 
    • Slight reduction in CPU overhead from peering
    • -Xp2p-peer-lower-bound=10
  • Chain-pruning: Enabled

      ...

        • Deposit logs / tree dependency (TEKU ONLY) 

      Considerate-staker

      • Sync mode: SNAP
        • Lowest More disk, quickest sync, cannot can serve old more block data, can serve all world state data
      • Data-storage-format: BONSAIMax-peers: 75Slight increase in CPU overhead from peering

      Private-network / Enterprise (?)

      • Sync-mode: FAST (move to snap —> not until snap server and Bonsai are tested in this environment, might require bonsai archive for some networks to migrate entirely over)
        • --fast-sync-min-peers = 3
      • Min-gas-price=0?
      • --remote-connections-limit-enabled=false
      • Tx-pool=Legacy / Sequential
        • --tx-pool-no-local-priority 
        • --tx-pool-limit-by-account-percentage=(something bigger than 4 transactions)

      RPC Provider (Needed?)

      • Archive - Awaiting Bonsai Archive to change defaults, then…
        • data-storage-format: Bonsai
        • New options for how many checkpoints to take (i.e. tradeoff between storage and rollback time)
      • Near-head - Standard full node
        • Uses default profile from above

      ...