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

Non evm support and additional ccr functions integration #422

Merged
merged 34 commits into from
Aug 14, 2024

Conversation

0xNilesh
Copy link
Member

@0xNilesh 0xNilesh commented Aug 6, 2024

No description provided.

0xNilesh and others added 26 commits July 23, 2024 16:57
Updated address params in payload to bytes32 in CCR functions
…ta-ccr

Add CCR support for updateChannelMeta
…ngs-ccr

feat: add ccr support for createChannelSettings fn
@zaryab2000 zaryab2000 self-requested a review August 6, 2024 14:44
@zaryab2000 zaryab2000 self-assigned this Aug 6, 2024
@zaryab2000 zaryab2000 added the priority-1 Indicates highest priority label Aug 6, 2024
contracts/PushComm/PushCommV3.sol Show resolved Hide resolved
contracts/PushComm/PushCommV3.sol Show resolved Hide resolved
@@ -11,7 +11,7 @@ contract PushCoreStorageV2 {
);

mapping(address => uint256) public nonces; // NOT IN USE Anymore
mapping(address => uint256) public channelUpdateCounter;
mapping(address => uint256) public oldChannelUpdateCounter;//NOT in use anymore
Copy link
Collaborator

Choose a reason for hiding this comment

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

We directly reject the use of old ChannelUpdateCounter mapping but what about the data it already stores for existing addresses ?? Has there any measures been implemented for the migration of those data?
cc: @0xNilesh

Copy link
Collaborator

Choose a reason for hiding this comment

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

two things here:

  1. It should first be checked if there are existing use of this oldChannelUpdateCounter currently?
  2. We should include functionality for the migration of this data as well from address to bytes.

Note: Ideally, every address to bytes change should be re-checked for migration again. @0xNilesh @Zartaj0

Copy link
Member

Choose a reason for hiding this comment

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

This might have slipped.

Yes, we planned to include its migration in the same migrate function we have for channelInfo.

contracts/PushCore/PushCoreV3.sol Show resolved Hide resolved
@zaryab2000 zaryab2000 assigned 0xNilesh and unassigned zaryab2000 Aug 13, 2024
@zaryab2000 zaryab2000 merged commit 4ca4fd1 into 212-crossChainReq-1st Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-1 Indicates highest priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

😈 [Feature Enhancement] - Updated the following functions to make CCR compatible
3 participants