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 #2950

Open
jordy25519 opened this issue Sep 19, 2024 · 0 comments · May be fixed by #2951
Open

max rent epoch serialization #2950

jordy25519 opened this issue Sep 19, 2024 · 0 comments · May be fixed by #2951

Comments

@jordy25519
Copy link

jordy25519 commented Sep 19, 2024

Problem

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

the solana-client crate 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

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

Successfully merging a pull request may close this issue.

1 participant