Skip to content

fix: update insufficent funds for fee error #944

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

erictaylor
Copy link
Member

No description provided.

@erictaylor erictaylor self-assigned this Dec 17, 2024
@erictaylor erictaylor merged commit ef80a85 into master Dec 17, 2024
3 checks passed
@erictaylor erictaylor deleted the erictaylor/insufficient-funds-clarity branch December 17, 2024 18:32
github-actions bot pushed a commit that referenced this pull request Mar 3, 2025
# [4.2.0](v4.1.1...v4.2.0) (2025-03-03)

### Bug Fixes

* fix tests ([b7ea242](b7ea242))
* logic; fixture ([2fb8039](2fb8039))
* tests ([9a26f47](9a26f47))
* update insufficent funds for fee error ([#944](#944)) ([ef80a85](ef80a85))

### Features

* removed old pvm builder and apis ([ebbb290](ebbb290))

### BREAKING CHANGES

* The old PVM transaction builder has been removed. The new Etna builder is now the default builder in order to support dynamic fees. Static fees on P-chain are not longer applicable. Likewise, API's referring to retrieving static fees have been removed where no longer applicable, and new X-Chain specific API's have been added to cover retrieving static tx fees specific to X-Chain transactions. The `e` alias on `pvm` (ie `pvm.e.{builderMethod}`) has been marked deprecated since the builder methods are now directly available on the `pvm` export.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants