MujkicA
MujkicA
fuel-core has introduced two new transaction types which we need to implement support for. See: https://specs.fuel.network/master/tx-format/transaction.html?highlight=Upgrade#transactionupgrade https://specs.fuel.network/master/tx-format/transaction.html?highlight=Upgrade#transactionupload
https://github.com/FuelLabs/fuels-rs/issues/1289 The above issue on the Rust SDK led me to discover that we provide `eth_keystore::encrypt_key` with a mnemonic to be used as pk here: https://github.com/FuelLabs/forc-wallet/blob/4d5fa8b1214df6bcad9b31dbef571a67af70da8f/src/utils.rs#L129 which leads to variable...
This section in the code describes a caveat with estimation and output variables that we should mention in the docs somewhere: https://github.com/FuelLabs/fuels-rs/blob/80fe445b0f1f6523e6fca83e88052bf608e27324/packages/fuels-core/src/types/transaction_builders.rs#L557
As mentioned [here](https://github.com/FuelLabs/fuels-rs/pull/1423#issuecomment-2165335236), we should make out `TxPolicies` match the specs and expose/update the corresponding getters on the `Transaction` trait.
The following interface was discussed at a meeting with the client team: ```rust struct Bundle { sequence_number: u64, blocks_range: Range, // The DA block height of the last transaciton in...
Explore using a more optimised coder for the blob sidecar builder