Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Contract data propagation time.
See original GitHub issueContract instance created using new Contract seems to not return up to date data directly after event. With slight delay before call returned state is correct. I am using metamask as provider.
Relaying only on events to update state is not ideal solution.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Propagation Times | HostGator Support
DNS zone record changes such as A, MX, and CNAME records can typically take 0 to 4 hours to resolve but are known...
Read more >What is 'propagation time' data based on and how to debug ...
The node latency showed on stats website is within 100 ms,but the propagation time is around 1s.The avg block time of this sidechain...
Read more >Domain propagation time - Filecamp
DNS propagation time But not all are normal conditions ... and DNS changes can take anywhere between 24 and 72 hours to start...
Read more >How Long does it Take for DNS to Update? | DNS Propagation
According to GoDaddy, updates usually take a few hours to process and propagate post modification. Maximum time: 48 hours (in case of errors)....
Read more >Research News >> Ephemeral data and the Schrödinger's paradox ...
Most smart contracts perform computations based on information coming from the ... This lowers the cost of Ephemeral data propagation time, as the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ricmoo Thank you for help. I got all I need.
@ricmoo is correct, Ethereum is inherently not a ‘sync’ framework. the event watcher is at best a ‘something happen, you may want to check’ but the serialization of any kind still needs to be built in the client and/or the contract.