Vlad Frolov

@khorolets @telezhnaya This was an instance of duplicate transaction execution. Blocks `#22633807` and `#22635168` contain transaction `J4CZZQrZK6kYPVLkrdbTEpcqhUNZiRxktbMzHviqeGgf`. The implicit account was initially created by a [transfer call at block `#22633373`](https://explorer.near.org/transactions/ttHE4uV6P1LuAZiBk2M7X932bdoav5p5KyCUBUVZmra),...

> So my main assumption is that we might have introduced some changes to the Indexer Framework that we are no longer able to collect the Receipt 6QKTEHsLihDgVrdtWYbURA28zF29Xdw5dnfWbDVWHPv4 for block...

@telezhnaya What is the error you observe when you try parsing the metadata? Their metadata looks fine to me: ``` $ near-cli-rs contract call-function as-read-only c944e90c64b2c07662a292be6244bdf05cda44a7.factory.bridge.near ft_metadata json-args {} network-config...

@telezhnaya Your `Base64VecU8` type misses proper serialization/deserialization implementation, see `#[serde(with = "base64_bytes")]` in near-sdk-rs: https://docs.rs/near-sdk/latest/src/near_sdk/json_types/vector.rs.html#6 These contracts are fine, it is a bug in this project.

@telezhnaya Can you reference the commit here just for future reference?

Two independent nodes exhibit the same behavior (same block heights), so it is not a glitch

Well, after restarting one node I observed that it does not get stuck anymore while the one that I did not restart kept getting stuck, so I restarted the other...

I hope this issue can be prioritized. It seems that a number of projects would love to see it happen: * https://github.com/kaspar030/laze/pull/303 * https://github.com/probe-rs/probe-rs/issues/1892 * https://github.com/stchris/aleph-tui/issues/3 * I have 3+...

@connec Thanks for sharing! I tried to follow your steps, but system dependencies are blocking me (openssl and libudev): https://github.com/near/near-cli-rs/pull/319

Well, I used cross before and it worked great, so I would love to see cargo-dist support it or any other solution. I am getting more and more reports these...