@@ -92,11 +92,11 @@ grothendieck {
92
92
93
93
peer {
94
94
# Retry delay for failed attempt at connecting to a peer
95
- connect-retry-delay = 5 seconds
95
+ connect-retry-delay = 1 minute
96
96
97
97
# Maximum number of reconnect attempts after the connection has been initiated.
98
98
# After that, the connection will be dropped until its initiated again (eg. by peer discovery)
99
- connect-max-retries = 1
99
+ connect-max-retries = 2
100
100
101
101
disconnect-poison-pill-timeout = 5 seconds
102
102
@@ -111,16 +111,16 @@ grothendieck {
111
111
wait-for-tcp-ack-timeout = 5 seconds
112
112
113
113
# Maximum block headers in a single response message (as a blockchain host)
114
- max-blocks-headers-per-message = 200
114
+ max-blocks-headers-per-message = 100
115
115
116
116
# Maximum block bodies in a single response message (as a blockchain host)
117
- max-blocks-bodies-per-message = 200
117
+ max-blocks-bodies-per-message = 100
118
118
119
119
# Maximum transactions receipts in a single response message (as a blockchain host)
120
- max-receipts-per-message = 200
120
+ max-receipts-per-message = 100
121
121
122
122
# Maximum MPT components in a single response message (as a blockchain host)
123
- max-mpt-components-per-message = 400
123
+ max-mpt-components-per-message = 200
124
124
125
125
# Maximum number of peers this node can connect to
126
126
max-peers = 40
@@ -248,7 +248,7 @@ grothendieck {
248
248
peers-scan-interval = 3.seconds
249
249
250
250
# Duration for blacklisting a peer. Blacklisting reason include: invalid response from peer, response time-out, etc.
251
- blacklist-duration = 30 .seconds
251
+ blacklist-duration = 200 .seconds
252
252
253
253
# Retry interval when not having enough peers to start fast-sync
254
254
start-retry-interval = 5.seconds
@@ -257,7 +257,7 @@ grothendieck {
257
257
sync-retry-interval = 5.seconds
258
258
259
259
# Response time-out from peer during sync. If a peer fails to respond within this limit, it will be blacklisted
260
- peer-response-timeout = 10.seconds
260
+ peer-response-timeout = 3.minutes
261
261
262
262
# Interval for logging syncing status info
263
263
print-status-interval = 30.seconds
@@ -269,7 +269,7 @@ grothendieck {
269
269
max-concurrent-requests = 50
270
270
271
271
# Requested number of block headers when syncing from other peers
272
- block-headers-per-request = 2048
272
+ block-headers-per-request = 200
273
273
274
274
# Requested number of block bodies when syncing from other peers
275
275
block-bodies-per-request = 128
@@ -278,7 +278,7 @@ grothendieck {
278
278
receipts-per-request = 60
279
279
280
280
# Requested number of MPT nodes when syncing from other peers
281
- nodes-per-request = 1000
281
+ nodes-per-request = 200
282
282
283
283
# Minimum number of peers required to start fast-sync (by determining the target block)
284
284
min-peers-to-choose-target-block = 2
0 commit comments