feature / lz gated modules

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works

[imthatcarlos]

New features

• new modules LZGatedFollowModule, LZGatedCollectModule, and LZGatedReferenceModule to do cross-chain token gating
• supporting lz contracts LZGatedProxy, LzApp, NonblockingLzApp, and SimpleLzApp
• new mocha tests
• new hardhat tasks

Example (LZGatedFollowModule)

1. lensprotocol.lens has set their gated follow data. A new follower must have 50 AAVE on Optimism.
2. carlosbeltran.lens wishes to follow - fetches the requirements and generates the signature for #followWithSig
3. anyone (ex: a relayer) can submit the follow requirements + the signature to the LZGatedProxy contract on Optimism, which relays the payload to the LZGatedFollowModule contract on Polygon via LayerZero

• TLDR; the token balance check happens on Optimism, and the follow tx on Polygon

TODO

• fix newly failing test in /lz-gated-follow-module.spec.ts
• fix cause for event MessageFailed being emitted when the tx actually succeeds
• improve fee estimates
• improve gas estimates
• ask lz team: latency between #send on source chain and #lzReceive on destination chain can be between 5-30min+ (goerli => mumbai) => testnet infra was updated, not an issue on mainnet ✅

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[donosonaumczuk]

Hey guys, good work!

There are lot of files that we are adding to the repo that are not necessarily ad-hoc for the Lens modules, but instead generic LayerZero contracts. It would be nice if you import your core repo as a dependency instead, or even create a separate repo that can be used as dependency if some of the files are not included in your core repo.

The idea is to avoid increasing the amount of files here when are not 100% related to the code of each of the Lens modules. Same reason why I am asking to remove some duplicated mocks from the PR.

[imthatcarlos]

thanks for the feedback @donosonaumczuk 🙏 I resolved all comments and pushed changes

• imported the @layerzerolabs/solidity-examples package for the lz contracts + deleted all the extra files
• opted to re-using the LzApp instead of my SimpleLzApp; all i had to do was not process messages received
• used the exiting mocks
• add LzEndpointMock in the typechain config externalArtifacts; only runs for tests, lmk if that works