feat: ERC20FeeProxy on Near testnet#1086
Conversation
|
|
||
| /** Extension interface is extended by the extensions implementation */ | ||
| export interface IExtension<T = any> { | ||
| export interface IExtension<TCreationParameters = any> { |
There was a problem hiding this comment.
Minor unrelated clarification
There was a problem hiding this comment.
TODO this yarn lock update is probably irrelevant or wrong
leoslr
left a comment
There was a problem hiding this comment.
I could not find any blocker.
Just a general, question, a saw that most of the test were using aurora / aurora-testnet. Are we sure they would pass as well using near / near-testnet ?
Or that is planned for later ?
| @@ -1,5 +1,5 @@ | |||
| overwrite: true | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near' | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near-testnet' | |||
There was a problem hiding this comment.
I have not deployed to mainnet yet, but I can actually. I noticed that for EVMs the schema is pulled from goerli.
There was a problem hiding this comment.
@leoslr I'm guessing it is to retrieve the latest schema, even before it is deployed to mainnet
Yes, we plan to make it a different change. With the recent strong typing of Thanks for your review @leoslr |
alexandre-abrioux
left a comment
There was a problem hiding this comment.
Awesome changes, I like the new chain helpers! 🙂
And thank you for the shoutout 😇
packages/advanced-logic/src/extensions/payment-network/erc20/fee-proxy-contract.ts
Show resolved
Hide resolved
| @@ -1,5 +1,5 @@ | |||
| overwrite: true | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near' | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near-testnet' | |||
There was a problem hiding this comment.
@leoslr I'm guessing it is to retrieve the latest schema, even before it is deployed to mainnet
| anyToNativeTokenExtension.supportedNetworks.includes(network), | ||
| ); | ||
| network?: CurrencyTypes.ChainName, | ||
| ): AnyToNative | undefined { |
There was a problem hiding this comment.
(Not related) Return type simplification for maintainability
| @@ -1,5 +1,5 @@ | |||
| overwrite: true | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near' | |||
| schema: 'https://api.thegraph.com/subgraphs/name/requestnetwork/request-payments-near-testnet' | |||
There was a problem hiding this comment.
I have not deployed to mainnet yet, but I can actually. I noticed that for EVMs the schema is pulled from goerli.
Description of the changes
ERC20FeeProxy extension supports Near fungible token transfers, in
advanced-logic, andpayment-detection.The
ERC20FeeProxyartifacts now refer to a version namednear, aside0.1.0etc. This choice can be debated but the assumption is that we can update contracts on Near without changing their address.getFeeProxyContractErc20ForNetworkmethod in the AdvancedLogic objectOther changes
In @requestnetwork/currency:
nearis now supported as a NearChain identifier. This is mandatory to start preparing the removal of the wrongauroraalias.aurora, even if we should get rid of it.In @requestnetwork/types and @requestnetwork/smart-contracts:
CurrencyTypes.VMChainName: Virtual machin chains, where payment proxy contracts can be deployedArtifactInfotype now supports NearChains, except for theconnectmethod that only supportsEvmChainNameIn @requestnetwork/payment-detection:
Credits
🙌 Shoutouts to @alexandre-abrioux for paving the way with #1056 and #950.