Greg
Greg
I've noticed a specific version of Cadence is used in tests. Why not use the latest? ``` run: sh -ci "$(curl -fsSL https://raw.githubusercontent.com/onflow/flow-cli/master/install.sh)" -- v0.33.1-sc-m5 ``` The issue with fixing...
## Description This PR change the `access.Client` event subscription methods so they expose options for subscribing. More specifically setting heartbeat interval. Since this options are not protocol specific (grpc/http) they...
Closes: #5862 This PR adds a function to the Cadence arch that can be used to produce revertible random. The function can be called from Solidity like so: ``` cadenceArch.staticcall(abi.encodeWithSignature("revertibleRandom()"))...
Currently, we implemented access to random sources through a cadence arch contract, which uses the Flow history source of randomness contract and can be used with commit-reveal schemes to create...
Closes: #5748 WIP
We need to revert the logic for decoding previous types of blocks. During development block type was changed (new fields were added), and because blocks were persisted on previewnet we...
Closes: #5911 Change address value in the EVM events `CadenceOwnedAccountCreated` `FLOWTokensDeposited` `FLOWTokensWithdrawn` to contain hex-encoded address as string instead of byte array, this makes it more useful for developers.
EVM events `CadenceOwnedAccountCreated` `FLOWTokensDeposited` `FLOWTokensWithdrawn` contain the EVM address as byte array, this is not great for human-readability and has been suggested we could change to hex-encoded addresses. The original...
Executing EVM transactions with different combinations of modifications to the state can lead to unwanted side-effects between transactions. With the introduction of Cadence arch and batch transactions that risk increased....
Currently there's no tests around events being correctly emitted as the execution happens. We should add tests that make sure the correct events and values were emitted for transaction and...