Snapshot at least on testnet is quite empty

[kalepail]

stellar snapshot create --network testnet --address GCEDG23LK46PHGXIY63E3ELQGBX6VHQ4EWLYT7FMLOOCIS3ZY2ITHDXB --out snapshot.json --output json --ledger 539455

{
  "protocol_version": 23,
  "sequence_number": 539455,
  "timestamp": 0,
  "network_id": "cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472",
  "base_reserve": 1,
  "min_persistent_entry_ttl": 0,
  "min_temp_entry_ttl": 0,
  "max_entry_ttl": 0,
  "ledger_entries": []
}

I would have expected these values to be populated with the testnet values as well as for the GCEDG23LK46PHGXIY63E3ELQGBX6VHQ4EWLYT7FMLOOCIS3ZY2ITHDXB account to have been found. It's only been created, not used for anything, but still.

% stellar --version
stellar 23.1.3 (dde778f0c26e352d8ad2eeb63382ea25ed5e0bb5)
stellar-xdr 23.0.0 (e83a6337204ecfdb0ac0d44ffb857130c1249b1b)
xdr curr (4b7a2ef7931ab2ca2499be68d849f38190b443ca)

[tupui]

For me the command is even failing with an error. I had posted on Discord but some folks posted some walls of text so I guess this got lost 😅

https://discord.com/channels/897514728459468821/966788672164855829/1414354928620535809

Anyone using snapshot for testing? I am trying to do
stellar snapshot create --address CATRNPHYKNXAPNLHEYH55REB6YSAJLGCPA4YM6L3WUKSZOPI77M2UMKI --network mainnet --output json --out network_snapshots/sorobandomains.json but I am getting :x: error: read XDR frame bucket entry: xdr value unsupported. Not sure what I am supposed to do with that

[leighmcculloch]

@tupui I've opened a separate issue for the error you are encountering:

• Add a check to the snapshot download logic to validate bucket is not corrupt #2208

[leighmcculloch]

I would have expected these values to be populated with the testnet values

+1 There's an issue open regarding this.

• Populate fields in snapshots created with stellar snapshot create #2198

I've updated that other issue to also include the timestamp field which is the other field not being set as you noted above, and will continue updates about that feature gap over there.

as well as for the GCEDG23LK46PHGXIY63E3ELQGBX6VHQ4EWLYT7FMLOOCIS3ZY2ITHDXB account to have been found.

This looks like a bug. The G address is being treated like a contract ID. cc @fnando

[janewang]

@tupui Can you check if this is fixed by #2198?

[tupui]

@janewang I will test once there is a new release, thanks a lot 😃

[tupui]

@janewang I confirm, I get this now

{
  "protocol_version": 23,
  "sequence_number": 59248127,
  "timestamp": 1759700229,
  "network_id": "7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979",
  "base_reserve": 5000000,
  "min_persistent_entry_ttl": 2073600,
  "min_temp_entry_ttl": 17280,
  "max_entry_ttl": 3110400,
  "ledger_entries": []
}