Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: tombchain #1024

Merged
merged 5 commits into from
Dec 22, 2022
Merged

feat: tombchain #1024

merged 5 commits into from
Dec 22, 2022

Conversation

leoslr
Copy link
Contributor

@leoslr leoslr commented Dec 22, 2022

Description of the changes

Tombchain is a permissioned L2 evm.
Deployments: only ERC20FeeProxy and EthFeeProxy.
https://app.asana.com/0/1203350802794948/1203600402430063

Additional fix:
When making the deployment, I was blocked as the Tombchain Node RPC did not support the eth_FeeHistory method used by the eip1559.
All evm nodes may not support it yet. It does not block the deployment anymore

@coveralls
Copy link

coveralls commented Dec 22, 2022

Coverage Status

Coverage remained the same at 87.987% when pulling 53da822 on feat-tombchain into 0af020b on master.

@leoslr leoslr marked this pull request as ready for review December 22, 2022 14:05
@leoslr leoslr requested a review from olivier7delf December 22, 2022 14:06
Copy link
Member

@alexandre-abrioux alexandre-abrioux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@leoslr FYI this is how it's done for the storage to detect if it can use EIP-1559:

try {
await this.provider.send('eth_feeHistory', [1, 'latest', []]);
} catch (e) {
this.logger.warn(
'This RPC provider does not support the "eth_feeHistory" method: switching to legacy gas price',
);
this.enableEip1559 = false;
}

It could be extracted into an util function

@leoslr
Copy link
Contributor Author

leoslr commented Dec 22, 2022

@alexandre-abrioux I won't add it to this PR to keep what's related to contract deployment clean. I'll add myself a ticket to do it in the next weeks

@leoslr leoslr merged commit 7ba9b80 into master Dec 22, 2022
@leoslr leoslr deleted the feat-tombchain branch December 22, 2022 14:26
@alexandre-abrioux
Copy link
Member

@leoslr I'll also probably work on it whenever I find time since I need to finish #765. I'll keep you posted if I start first!

roadrunner21 pushed a commit to roadrunner21/requestNetwork that referenced this pull request Jan 3, 2023
roadrunner21 pushed a commit to roadrunner21/requestNetwork that referenced this pull request Jan 3, 2023
MantisClone added a commit that referenced this pull request Jan 17, 2023
* Replace default export with named exports in utils package to enable tree shaking (fixes #1015)

This change replaces the default export in the utils package with named exports, which allows for better tree shaking and smaller build sizes in user code applications. It also enforces the no-default-export ESLint rule to ensure consistent code style

* running refactored files through prehook (#1015)

* Apply changes to utils package to monorepo

This commit applies the changes made to the utils package to the rest of the monorepo. The changes include replacing the default export with named exports and enforcing the no-default-export ESLint rule.

NOTE: Not all changes could be tested (#1029, #1030, #1031)

* Apply changes to utils package to payment-processor/test/payment/any-to-near.test.ts

* feat: tombchain (#1024)

* feat: tombchain (#1024)

* running refactored files through prehook (#1015)

* Apply changes to utils package to monorepo

This commit applies the changes made to the utils package to the rest of the monorepo. The changes include replacing the default export with named exports and enforcing the no-default-export ESLint rule.

NOTE: Not all changes could be tested (#1029, #1030, #1031)

* Apply changes to utils package to payment-processor/test/payment/any-to-near.test.ts

* fix circular dependency by importing from the corresponding package rather from the same package barrel file

* Resolves #1023: Rename ambiguous functions for clarity

As discussed with @alexandre-abrioux and @benjlevesque, many of the functions in the utils module have been refactored and need to be renamed for improved code readability.

Signed-off-by: marcohefti <[email protected]>

* Fix README, identity, and signature file updates
-Removed list of utils from README to avoid staleness
-Changed 'hasError' to 'identityHasError'
-Changed 'sign' back to original name 'sign'
-Changed 'recover' to 'recoverSigner'

Addressed comments by @MantisClone

Signed-off-by: marcohefti <[email protected]>

* Refactor crypto and ec-utils modules

-Removed the named const from crypto-wrapper.ts and exported functions individually
-Removed the named const from ec-utils.ts and exported functions individually
-Renamed recover() to recoverSigner() in ec-utils.ts
-Prefixed functions with 'ec' to prevent duplicate variables
-Reverted normalizeData() to normalize()

Signed-off-by: marcohefti <[email protected]>

Signed-off-by: marcohefti <[email protected]>
Co-authored-by: MantisClone <[email protected]>
Co-authored-by: leoslr <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants