Anup

Results 24 issues of Anup

### What problem does your feature solve? Currently, the write fees per kb is a straight line that depends on current bucketlist size. When the slope of this line is...

### What? Audit our dependent crates to see if we need to bump their versions. Also, compare stellar-core pinned versions with that of rs-soroban-env crates. ### Why? For example, we...

bug

### What? Setup Soroban baseline code coverage. After this we can work on reporting on coverage for each new PR by [hooking up with CI](https://github.com/stellar/rs-soroban-env/issues/814). Follow the documentation of [instrument-coverage](https://doc.rust-lang.org/rustc/instrument-coverage.html#test-coverage)....

### What? Back to back loadgen sessions that increase and decrease Soroban limits.

### What? Review Soroban code to make sure there are no runtime panics in the host. Check for any RefCell usages to make sure it won't panic in runtime. For...

### What? Running an experiment to see if core can be build with latest env and curr can point to that in the rust bridge. Doing this experiment only for...

### What? Restore the wasm contract used for network settings upgrade if expired. ### Why? For future network settings upgrade, since we are using the same wasm, there is a...

bug

### What? Combine the info logs for network upgrade setting change to a single message. ### Why? We have a lot of config settings so its cluttered if we log...

bug

## Why? In [Stellar-transaction.x](https://github.com/stellar/stellar-xdr/blob/curr/Stellar-transaction.x#L871) XDR, we have Transaction::fee defined as uint32 type. With introduction of Soroban, the total fees could go higher in future. The resource usage fees, rent fees...

bug
enhancement
protocol