Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge issues into a one pager #21

Merged
merged 1 commit into from
Nov 14, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 63 additions & 0 deletions docs/known_issues/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,66 @@ sidebar_position: 5

The contract component is under heavy development. Here, we document the currently known issues
we are aware of. They can either be bugs or completely missing features. Those will be resolved.
Please consult [differences to Ethereum](../differences_to_eth) to learn about fundamental differences
within Ethereum that will likely not change in the future.

## Revive

The following compiler issues are known and we are working on it. Please do not open a new issue.

### Release

resolc `0.1.0-dev.5`

### Missing features

- [Libraries with public functions are not supported](https://github.com/paritytech/revive/issues/91)
- [Automatic import resolution is not supported](https://github.com/paritytech/revive/issues/98)
- The emulated EVM linear contract memory is limited to 64kb in size. Will be fixed with support for metered dynamic memory.
- [The contract calldata is currently limited to 1kb in size](https://github.com/paritytech/revive/issues/57)
- [EIP-4844 opcodes are not supported](https://github.com/paritytech/revive/issues/64)
- [Delegate calls are not supported](https://github.com/paritytech/revive/issues/67)
- [The `blockhash` opcode is not supported](https://github.com/paritytech/revive/issues/61)
- [Gas limits for contract calls are ignored](https://github.com/paritytech/revive/issues/60)
- [Gas related opcodes are not supported](https://github.com/paritytech/revive/issues/60)
- IPFS metadata hashes are not supported
- [Compiled contract artifacts can exceed the pallet static memory limit and fail to deploy](https://github.com/paritytech/revive/issues/96).
- [Transfers to inexistent accounts will fail if the transferred value lies below the ED.](https://github.com/paritytech/revive/issues/83) Will be fixed in the pallet to make the ED completely transparent for contracts.
- [Source level debug information and contract execution tracing](https://github.com/paritytech/revive/issues/18)
- [Compiling contracts requiring `solc` version earlier than `0.8.0` requires using the EVM legacy assembly pipeline. This is in a highly experimental state.](https://github.com/paritytech/revive/issues/89)

## REMIX

The known issues in our REMIX frontend.

### Release

REMIX `0.54-dev`

### Known issues

- Initialization Failures: Occasionally, REMIX may fail to load due to backend overload errors. If this occurs, please reload the REMIX IDE to restore functionality.

- Currency Updates: The display of currency (Wei/Ether) does not dynamically update based on the selected network.

- Loading Problems: REMIX may hang during loading, particularly on Windows 10 when using the Chrome browser. We are investigating this issue. If you encounter this, please try restarting your browser and loading REMIX again.

- Debugger Plugin: The debugger plugin is not functioning properly.

- Solidity Unit Testing: Solidity unit testing is not operational; only JavaScript-based unit testing is currently functional.

- Parallel Transactions: When sending transactions in REMIX, be patient, as REMIX may struggle to handle multiple parallel requests effectively. Please avoid initiating multiple transactions simultaneously to prevent errors.

- Deployment Issues: While the terminal may indicate a successful contract deployment, there are cases where the deployment has been reverted, and the contract does not exist on the blockchain. This discrepancy can lead to confusion, especially when the IDE shows a positive deployment status.

- UI Corruption: In some instances, users may experience UI corruption where elements do not render correctly. Reloading the REMIX IDE usually resolves these display issues.

- Missing Injected Westend - MetaMask Environment: If the required environment is not present, reloading the REMIX IDE may resolve the issue.

- Unable to Select Required Environment: Clear your browser's browsing data and disconnect REMIX from MetaMask in the ALL Permissions menu of MetaMask.

- Transaction Fails or Resolve Stuck or Pending Transactions: Go to Settings -> Advanced in MetaMask and select [Clear activity tab data](https://support.metamask.io/managing-my-wallet/resetting-deleting-and-restoring/how-to-clear-your-account-activity-reset-account/#to-reset-the-account).

### Not Tested

- Plugins Functionality: We have not yet conducted tests on the GitHub, DGIT DIFF, SOURCIFY, SWARM and IPFS plugins. Users should proceed with caution when using these features until further validation is completed.
3 changes: 0 additions & 3 deletions docs/known_issues/pallet_revive.md

This file was deleted.

35 changes: 0 additions & 35 deletions docs/known_issues/remix.md

This file was deleted.

28 changes: 0 additions & 28 deletions docs/known_issues/revive.md

This file was deleted.

4 changes: 0 additions & 4 deletions docs/known_issues/rpc.md

This file was deleted.