v0.2.8
A quick patch release that makes transaction submission error details available.
Following the recent increase in class declaration fees, many users have started facing the cryptic ValidationFailure
error, which is in fact due to their accounts not having sufficient ETH
balance to cover the transaction cost. The failure reason is rather straightforward, but Starkli wasn't correctly displaying the error details, leaving users confused (until they use --log-traffic
to inspect the raw traffic).
This release fixes that by printing error details on transaction submission. Instead of:
Error: ValidationFailure
usrs should now expect something similar to (depending on node implementation):
Error: ValidationFailure: perform_validations call failed; failure reason: TransactionFailureReason(code='native_blockifier.PyTransactionPreValidationError', error_message='TransactionFeeError(MaxFeeExceedsBalance { max_fee: Fee(100000000000000000000), balance_low: StarkFelt("0x0000000000000000000000000000000000000000000000007daaaaeb34db38c7"), balance_high: StarkFelt("0x0000000000000000000000000000000000000000000000000000000000000000") })').
Fixed
- 9b313db: tx submission error details not displayed
Full Changelog: v0.2.7...v0.2.8