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

max rent epoch serialization #35659

Closed
jordy25519 opened this issue Sep 19, 2024 · 1 comment
Closed

max rent epoch serialization #35659

jordy25519 opened this issue Sep 19, 2024 · 1 comment
Labels
community Community contribution

Comments

@jordy25519
Copy link

Problem

in the wild RPC (some) providers are returning account 'rentEpoch' as 18446744073709552000
there are multiple bugs on various clients where deserialization is broken but the client libs switched to a big int to accommodate this

the solana-client can't parse this value currently as it exceeds u64.

invalid type: floating point 1.8446744073709552e19, expected u64

example issues caused by this:
go client issue: gagliardetto/solana-go#172 (solved with BigInt)
rust client issue:: regolith-labs/ore#26 (unsolved)

Proposed Solution

Make it clear for solana protocol that maximum rent epoch should never be serialized as anything other than 18446744073709551615

otherwise accept the situation, then solana-client rpc needs special case deserialization to handle the above value

@jordy25519 jordy25519 added the community Community contribution label Sep 19, 2024
Copy link
Contributor

This repository is no longer in use. Please re-open this issue in the agave repo: https://github.com/anza-xyz/agave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Community contribution
Projects
None yet
Development

No branches or pull requests

1 participant