Joshua Hannan
Joshua Hannan
### Issue To Be Solved The rewards payment transaction currently is a very long and costly transaction and should be made more efficient. ### Suggest A Solution And ideal solution...
### Issue To Be Solved The Go tests for the core contracts are not in a good state and need to be refactored to be clearer, more organized, and easier...
### Issue To Be Solved In general, we expect that: the candidate limit exceeds the slot limit by a large margin (probably about an order of magnitude) the number of...
### Issue To Be Solved `USDCFlow.cdc` for [USDC](https://github.com/onflow/bridged-usdc/blob/main/contracts/USDCFlow.cdc) is a very commonly used contract in the Flow ecosystem and developers often will want to test with it on the emulator...
### Issue To Be Solved For stable Cadence, it isn't enough for a developer to just make their contracts compatible. They also have to know that the upgrade will work...
EDIT (07/29/2024): Updated to reflect the latest proposal which streamlines the upgrade by immediately integrating the `FiatToken` contract with the protocol bridge and removes all keys from the account. This...
Adds an option in the `Admin` resources to stage the FiatToken contract for Cadence 1.0. This functionality is accessed in the same way as any other multi-sig functionality.
### Current Behavior A contract interface defines an `access(contract)` function and gives it a default implementation. A contract that implements the contract interface does not provide an implementation for the...
### Issue To Be Solved Currently, the transactions to update weights for fees just save values directly to storage. These should be resource functions with proper input validation. ### Suggest...
### Issue To Be Solved There is a lot of code in the staking contract (`FlowIDTableStaking`) that iterates through a node's delegators and does something. This could be better. [Example](https://github.com/onflow/flow-core-contracts/blob/stable-cadence/contracts/FlowIDTableStaking.cdc#L1026-L1043)...