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

Multicall syntax serialize for blocksampledDatalake #12

Open
rkdud007 opened this issue Feb 1, 2024 · 0 comments
Open

Multicall syntax serialize for blocksampledDatalake #12

rkdud007 opened this issue Feb 1, 2024 · 0 comments
Labels
enhancement New feature or request I-datalake Query interface of datalake P-low Low priority, not for near future

Comments

@rkdud007
Copy link
Member

rkdud007 commented Feb 1, 2024

BlockSampledDatalake memory datalake1 = BlockSampledDatalake({
            blockRangeStart: 10399990,
            blockRangeEnd: 10400000,
            increment: 1,
            sampledProperties: BlockSampledDatalakeCodecs
                .encodeSampledPropertyForStorage(
                    address(0x7b2f05cE9aE365c3DBF30657e2DC6449989e83D6),
                    bytes32(myInt),
                    bytes32(myInt),
                    bytes32(myInt),
                )
        });

what if we can put sampledProperties multiple fields? -> compiler can be much efficient

its different from compilation pipline. It's specific to BlockSampledDatalake. more like when we decode the rlp we anyway get all the fields information, but why it just send one corresponding field, if it's in same structure ( header structure, account structure that can be retrieve from rlp at once ) .

@rkdud007 rkdud007 added P-low Low priority, not for near future I-datalake Query interface of datalake enhancement New feature or request labels Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request I-datalake Query interface of datalake P-low Low priority, not for near future
Projects
None yet
Development

No branches or pull requests

1 participant