* Update dependencies for Nim 2.x
* Use refc as memory management and disable styleCheck because of testutils
* Fix ambiguous import
* Change Address init because eth introduced Byte20 type for Address type
* use uint64 instead of init64
* Rename properties after a change in eth to be closer to the spec
* Use Opt type instead of Option
* Add 2.0.12 version to CI
* Increment the version
* Update the Nim version in CI
* Update to Nim 2.0.14
* Use Nim 2.x commit hash for contractabi
* Remove stable on CI because we don't want to test with Nim 2.2.x
* Update Nim minimum version to 2.0.14
* fix version deps
* remove fq typename
* Add debug flag
* Define maximumtaggedversions
* Update readme
---------
Co-authored-by: Eric <5089238+emizzle@users.noreply.github.com>
This is a braking change. Subscription callbacks wrap the arguments in the Result type.
Corrects the preceding commit marked with wrong version number (0.10.2).
* chore: export subscriptions
This has a knock-on effect of nim-serde not being imported into subscriptions when JsonRpcProvider.new is called from a consumer that does not export nim-serde.
* import/export serde
* Replace all instances of std/json with pkg/serde
* fix nonce issues by locking populate and send transaction
Concurrent asynchronous population of transactions cause issues with nonces not being in sync with the transaction count for an account on chain. This was being mitigated by tracking a "last seen" nonce and locking inside of `populateTransaction` so that the nonce could be populated in a concurrent fashion. However, if there was an async cancellation before the transaction was sent, then the nonce would become out of sync. One solution was to decrease the nonce if a cancellation occurred. The other solution, in this commit, is simply to lock the populate and sendTransaction calls together, so that there will not be concurrent nonce discrepancies. This removes the need for "lastSeenNonce" and is overall more simple.
* remove lastSeenNonce
Internal nonce tracking is no longer needed since populate/sendTransaction is now locked. Even if cancelled midway, the nonce will get a refreshed value from the number of transactions from chain.
* chronos v4 exception tracking
* Add tests
