Mårten Blankfors
Mårten Blankfors
Implementing `std::error::Error` (and `Display`) would make it easier to wrap the `FromBase58Error` in applications using this library.
The `PreStxOp`, `StackStxOp` and `DelegateStxOp` burnchain operations are using less than 80 bytes of the OP_RETURN data. We would like to save the remaining bytes in these cases as a...
### Description This PR extends the signer persistence to allow for storing shares for multiple concurrent DKG rounds, identified by the aggregate public key for that round. On startup, the...
While the sBTC bridge application supports sBTC OP_RETURN deposits and withdrawals already, it needs to be adjusted to point to the right asset contract after we've deployed it in #85....
When we introduced support for persisting DKG shares in https://github.com/stacks-network/stacks-core/pull/4659 this requires two new StackerDBs to be instantiated by deploying the `signers-0-13` and `signers-1-13` contracts. However, since the signer smart...
Supersedes https://github.com/FuelLabs/fuel-vm/pull/727 ### Before requesting review - [ ] I have reviewed the code myself - [ ] I have created follow-up issues caused by this PR and linked them...
### Linked Issues Closes #2344 ### Description This PR adds support for getting batches of values from the storage through a new `StorageBatchInspect` trait in `fuel-core-storage`. This trait is implemented...
## Linked Issues/PRs Closes #2379 ## Description This PR simplifies the `kv_store::Value` type to be `Arc` instead of `Arc`. This makes the code slightly cleaner and also provides a (completely...
Observed in CI: https://github.com/FuelLabs/fuel-core/actions/runs/11580859867/job/32240358008?pr=2396 ``` Run cargo test --workspace Compiling fuel-core-types v0.40.0 (/home/runner/actions-runner/_work/fuel-core/fuel-core/crates/types) Compiling fuel-core-metrics v0.40.0 (/home/runner/actions-runner/_work/fuel-core/fuel-core/crates/metrics) ... test vm_storage::tests::read_sequential_range::read_subset_of_partially_set_range_without_running_too_far ... ok test vm_storage::tests::read_sequential_range::read_uninitialized_middle_range ... ok test vm_storage::tests::read_sequential_range::read_uninitialized_end_range ... ok...
Segfault observed on my build server today at `cf0bc5e730c394a0552cfb424ef6a24f5088a3ba` ``` SIGSEGV [ 5.469s] fuel-core-tests::integration_tests gas_price::latest_gas_price__if_node_restarts_gets_latest_value --- STDOUT: fuel-core-tests::integration_tests gas_price::latest_gas_price__if_node_restarts_gets_latest_value --- running 1 test Stopping fuel service test gas_price::latest_gas_price__if_node_restarts_gets_latest_value ... ok...