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

Add EVM integration with Base and Ethereum #406

Open
wants to merge 3 commits into
base: stable-11-17
Choose a base branch
from

Conversation

zkfarmoor
Copy link

Relates to:

Ethereum and Base integration: #303

Risks

High: involves new chain and protocol capabilities via the LI.FI SDK

Background

What does this PR do?

Adds the plugin-evm package

What kind of change is this?

Features (non-breaking change which adds functionality)

Documentation changes needed?

My changes require a change to the project documentation. (WIP)

Testing

Still in progress

Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't we keep this

}

return {
hash: process.txHash as `0x${string}`,
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we move this into a types file?

return {
hash: process.txHash as `0x${string}`,
from: fromAddress,
to: routes.routes[0].steps[0].estimate.approvalAddress as `0x${string}`,
Copy link
Contributor

Choose a reason for hiding this comment

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

^^

Comment on lines +8 to +14
const PROVIDER_CONFIG = {
PRICE_API: 'https://li.quest/v1',
NATIVE_TOKEN: {
ethereum: '0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2',
base: '0x4200000000000000000000000000000000000006'
}
} as const
Copy link
Contributor

Choose a reason for hiding this comment

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

We should add a type and move the hardcoded values into a constants file

Comment on lines +7 to +13
const PROVIDER_CONFIG = {
PRICE_API: 'https://li.quest/v1',
NATIVE_TOKEN: {
ethereum: '0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2',
base: '0x4200000000000000000000000000000000000006'
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

same here re moving to constants or config file and removing hard coded values

Copy link

Choose a reason for hiding this comment

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

constants makes sense, config doesn't just because WETH addrs are unchanging these days, so no need to inflate a config file

@zkfarmoor
Copy link
Author

working on all of these now, thank you guys for the quick reviews!

@sydneyitguy
Copy link

It would be cool to add a token creation action similar to the pump.fun action in the Solana plugin.

I've done similar stuff before using the Mint Club protocol, which is similar to pump.fun but designed for EVMs and offers more flexibility.

References:

Since adding this action is related to this EVM integration PR and will likely depend on it, I’d like to hear your thoughts on it.
What do you guys think?

@zkfarmoor
Copy link
Author

absolutely, I think a modular approach to token creation and other general evm-related actions would be appropriate to include.

this PR is intended to be a first iteration of EVM capabilities with the goal being to add more actions, chains, etc. over time. please feel free to make any changes/improvements to this!

@chandognft
Copy link

It would be cool to add a token creation action similar to the pump.fun action in the Solana plugin.

I've done similar stuff before using the Mint Club protocol, which is similar to pump.fun but designed for EVMs and offers more flexibility.

References:

Since adding this action is related to this EVM integration PR and will likely depend on it, I’d like to hear your thoughts on it. What do you guys think?

It would be cool to add a token creation action similar to the pump.fun action in the Solana plugin.

I've done similar stuff before using the Mint Club protocol, which is similar to pump.fun but designed for EVMs and offers more flexibility.

References:

Since adding this action is related to this EVM integration PR and will likely depend on it, I’d like to hear your thoughts on it. What do you guys think?

I can take a stab at this if you havent already

@sydneyitguy
Copy link

@chandognft Oh, I haven't yet. I've been learning more about Eliza's structure, which has been taking some time. It would be great if you could take a stab at this right away! 😊

@w1kke
Copy link

w1kke commented Nov 20, 2024

Looking forward to these being finished - tons of ideas that can be realised once it is merged in.

@0x-jj
Copy link

0x-jj commented Nov 22, 2024

What's required to get this merged in? Happy to help with any implementation

@chandognft
Copy link

What's required to get this merged in? Happy to help with any implementation

Theres some remaining work currently we are working on

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.

8 participants