fix(deps): CDB-2128 Address nonce errors #1004
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CDB-2128 Nonce errors in Clay AND QA CAS
Coordinator: dbrowning Investigator: dbrowning Clay CAS: QA CAS: |
dbcfd
force-pushed
the
cdb-2128-nonce-error
branch
from
52e6a23 to
15740b1
Compare
dbcfd
commented
Apr 5, 2023
| @@ -90,7 +90,7 @@ async function makeCeramicCore( | |||
| anchorServiceUrl, | |||
| // TODO CDB-2317 Remove `indexing` config when Ceramic Core allows that | |||
| indexing: { | |||
| db: "TODO", | |||
| db: 'TODO', | |||
dbcfd
commented
Apr 5, 2023
| } | ||
| } | ||
| } | ||
| return function (req: Request, _res: Response, next: NextFunction) { |
dbcfd
commented
Apr 5, 2023
| @@ -15,9 +15,11 @@ export class CeramicAnchorServer extends Server { | |||
| super(true) | |||
|
|
|||
| this.app.set('trust proxy', true) | |||
| this.app.use(bodyParser.raw({inflate: true, type: 'application/vnd.ipld.car'})) | |||
| this.app.use(bodyParser.raw({ inflate: true, type: 'application/vnd.ipld.car' })) | |||
dbcfd
commented
Apr 5, 2023
| @@ -39,7 +38,7 @@ export enum METRIC_NAMES { | |||
| // Anchor Service (histograms) | |||
|
|
|||
| // request that moves from ready -> processing | |||
| READY_PROCESSING_MS = "ready_processing_ms", | |||
| READY_PROCESSING_MS = 'ready_processing_ms', | |||
dbcfd
force-pushed
the
cdb-2128-nonce-error
branch
from
a25249b to
118fcec
Compare
stbrody
requested changes
Apr 10, 2023
src/services/blockchain/ethereum/ethereum-blockchain-service.ts
Outdated
Show resolved
Hide resolved
| const baseFee = maxFeePerGas.sub(maxPriorityFeePerGas) | ||
| txData.maxFeePerGas = baseFee.add(nextPriorityFee) | ||
| // must be greater than baseFee + maxPriorityFeePerGas | ||
| txData.maxFeePerGas = addPadding(baseFee + nextPriorityFee) |
There was a problem hiding this comment.
why are we adding padding here if we already added padding in increaseGasPricePerAttempt? Is this redundant?
There was a problem hiding this comment.
On upgrading ethers, we run into underpriced transaction errors. I'm not sure if ethers changed something in the data they report back, but this is required to not have underpriced transaction errors.
| if (attempt == 0 || previousGas == undefined) { | ||
| return increaseEstimate | ||
| ): bigint { | ||
| if (previousGas == undefined) { |
There was a problem hiding this comment.
so this is a behavior change to the gas logic. Previously we would add an increasing amount of padding per attempt on top of the gas estimate we get from ethers. So the first attempt we'd just use the gas estimate from ethers directly. The second attempt we'd add 10% on top of the estimate, and the third time we'd add 20% on top of the estimate.
In this new version we're just always adding 10% on top of the estimate every time.
I don't feel strongly about which logic is better, but could we possibly separate the changes to our estimation logic from the code changes required to keep the same logic with upgrading to the new version of the ethers package, each into their own PR?
There was a problem hiding this comment.
So there's a few things going on here
- makes this a little harder to follow, so it might make sense to pass both previous and estimate in to increase gas, rather than combining the values in set gas. If there's a previous, that always gets passed in as the estimate
- Once we have a previous (say x), we will pass that in, and multiply that by 10%.
x * 110% * 110%is always more thanx * 120%. Double check my code reading there, but I don't think we'll ever choose increaseEstimate. - As mentioned above, we run into underpriced transaction with the ethers upgrade. We would have to change the gas logic before the ethers upgrade if we want to split the PRs.
ukstv
requested changes
Apr 11, 2023
There was a problem hiding this comment.
Seems like calculation logic is okay. Minor technical improvements could be handy.
And emulation of StaticJsonRpcProvider! That could require some additional refactoring though: I am not sure if staticNetwork would work without giving explicit network to the provider.
src/services/blockchain/ethereum/ethereum-blockchain-service.ts
Outdated
Show resolved
Hide resolved
ukstv
approved these changes
Apr 11, 2023
|
@dbcfd Oh, lovely ethers: https://github.com/ceramicnetwork/ceramic-anchor-service/actions/runs/4670215624/jobs/8269672491#step:10:3555 At one point I thought maybe we could ditch ethers with viem altogether. |
viem author here! We are happy to help 😉 |
Per ethers-io/ethers.js#3812, nonce may be incorrectly incremented, which can produce off by one errors which we are currently seeing in QA and Clay
dbcfd
force-pushed
the
cdb-2128-nonce-error
branch
from
61cebb5 to
e724438
Compare
stbrody
requested changes
Apr 17, 2023
src/services/anchor-service.ts
Outdated
| @@ -404,7 +404,7 @@ export class AnchorService { | |||
| if (this.includeBlockInfoInAnchorProof) { | |||
| ipfsAnchorProof = { | |||
| blockNumber: tx.blockNumber, | |||
| blockTimestamp: tx.blockTimestamp, | |||
| blockTimestamp: tx.blockTimestamp.getUTCDate(), | |||
There was a problem hiding this comment.
this returns the date of the month. Ie for a Data object created for today it returns 17. I think you want the unix timestamp - I believe it's getTime() that you want, but do be careful of units. I'm not sure if that returns seconds or millis, and we need to make sure whatever we use matches what we are currently doing.
The fact that this change didn't cause any tests to fail is actually a bit worrying, maybe see if you can add a test that would catch this?
Please also make sure to do some manual testing to ensure that the AnchorProofs created before and after this change look the same.
There was a problem hiding this comment.
Good catch. Will fix that and check the test.
| @@ -115,20 +126,50 @@ function handleTimeoutError(transactionTimeoutSecs: number): void { | |||
| function make(config: Config): EthereumBlockchainService { | |||
| const ethereum = config.blockchain.connectors.ethereum | |||
| const { host, port, url } = ethereum.rpc | |||
| let network | |||
| try { | |||
| network = Network.from(ethereum.network) | |||
There was a problem hiding this comment.
hmm... this is likely to be a breaking change as now the network option is required in the config even when using an infura url (which implies the network and so network wasn't previously required).
That's fine since we're the only ones running a CAS, just something to look out for when we go to deploy. We should double check we have the network set so things don't break on the upgrade
There was a problem hiding this comment.
Edit: I see it's not actually required as if its not set we fall back to the non-static behavior. But that could cause our infura endpoint to be pummeled with chainid calls and blow up our bill (this happened in the past) so we'll still want to be really careful here and make sure have the network flag set on all 3 envs, and monitor our infura account as this gets deployed to various envs.
| provider = new ethers.JsonRpcProvider(hostPort) | ||
| } | ||
| } else if (network) { | ||
| logger.imp(`Connecting ethereum to etherscan provider for network ${ethereum.network}`) |
There was a problem hiding this comment.
what do you mean by "etherscan" provider here?
There was a problem hiding this comment.
The options make it so only etherscan works, since that's we use for our tests. All other providers would need host/port, and preferably name.
| alchemy: "-", | ||
| ankr: "-", | ||
| cloudflare: "-", | ||
| etherscan: ethereum.account.privateKey, |
There was a problem hiding this comment.
Removes all providers other than etherscan, and sets the private key for etherscan.
| } else if (host && port) { | ||
| logger.imp(`Connecting ethereum provider to host: ${host} and port ${port}`) | ||
| provider = new ethers.providers.StaticJsonRpcProvider(`${host}:${port}`) | ||
| const hostPort = `${host}:${port}` | ||
| if (network) { |
There was a problem hiding this comment.
maybe we can reduce code duplication by creating an empty options object and adding the staticNetwork field to it if network is set. Then we can always just pass the options object to the JSONRpcProvider constructor and not need the extra if(network) conditional in both blocks?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per ethers-io/ethers.js#3812, nonce may be incorrectly incremented, which can produce off by one errors which we are currently seeing in QA and Clay