Date: Tuesday, January 11th 2022
a. Arbitrage Bot Transactions & Gas Price
(Status: Scheduled)
UPDATE: We are aiming to increase minimum gas fees from 1 gwei to 30 gwei at 8PM PST on Thursday, January 13th / 4AM UTC of Friday, January 14th. Proactive notifications will be distributed to as many ecosystem partners as possible as we come closer to the scheduled date and time.
b. RPC Change #2 | Rate Limiting
(Status: Fine Tuning)
We are still observing excessively high amounts of calls on doEVMcall.
UPDATE: Rate limits will be tightened on this RPC as we continue to fine tune this configuration and optimize performance of our RPC nodes.
c. RPC Change #3 | Sync Status Checks
(Status: Success/Closed)
UPDATE: We have monitored the performance of sync status checks for a number of days without observing issues. This is now considered closed but we will continue to keep an eye on the sync status check.
d. Pocket Network | Routing to an External RPC Provider
(Status: In Progress)
UPDATE: We are sending 2% of all RPC traffic to Pocket while observing performance. This will be increased to 3% tomorrow, Wednesday, January 12th. See timeline below.
Expected Timeline:
Tuesday [Jan 11]
Get the binaries updated throughout the network, ensuring all fixes we’ve applied this past week is replicated to Pocket Network RPC nodes.
Wednesday [Jan 12]
Raise redirect of traffic to 3% early in the day.
Thursday [Jan 13]
Assess and then shift towards 5% for the weekend.
Monday [Jan 17]
Assess community feedback, plan next steps.
e. Increase of RPC Node Footprint
(Status: Success/Closed)
Update: We have increased our RPC node footprint by adding 20 servers to the infrastructure over the past week. This increase in server count will help handle the increase in traffic we are observing on the network.
f. Multi-Sig Wallets:
(Status: Investigating)
Update: The team is investigating issues impacting our multi-sig wallets and hope to have the problem resolved soon. More to follow on this as progress is made.
g. Bridging Issues:
(Status: Applied Fix / Monitoring)
UPDATE: We have identified an issue impacting the bridge and have taken corrective action by dedicating two archival nodes exclusively to bridging operations.