ink
ink copied to clipboard
use-ink
Parity's ink! to write smart contracts.
Remove outdated TODO comment and commented out code related to enc_storage_limit in the contract call implementation. This cleanup improves code readability by removing unused legacy code comments. ## Checklist before...
This pull request contains changes to improve clarity, correctness and structure.
.config/zepter.yaml `it outside` - `is outside` crates/e2e/sandbox/src/lib.rs `map_acocunt` - `map_account` crates/e2e/src/backend_calls.rs `fro dry-run` - `from dry-run`
### **Title** Error in the CHANGELOG.md --- ### **Description** This pull request fixes a typo in the `CHANGELOG.md` file. The word "explicitely" has been corrected to "explicitly" in the section...
### Description This pull request refactors the XCM-based smart contract to improve code quality, readability, and maintainability. It includes enhancements to documentation, error handling, and test structure, ensuring that the...
While performing a `transfer`, I encountered unsafe arithmetic in [ext.rs](https://github.com/use-ink/ink/blob/7338425630ca122717e360573d1b6ad09992d559/crates/engine/src/ext.rs#L117-L120), which can be triggered using the following PoC PoC: ```rust #[ink::contract] mod poc { #[ink(storage)] pub struct Poc { value:...
## Overview Following Rust semantics, ink! messages with a `&self` receiver (i.e. an immutable self reference receiver) shouldn't be able to mutate state/storage because the storage type is the Self...
Contracts written in Solidity and deployed to `pallet-revive` should be able to seamlessly call `ink!` contracts. Additionally, EVM wallets/tooling should be able to interact with `ink` contracts. This requires RLP...
## Summary Closes #2747 - [ ] n | Does it introduce breaking changes? **No** - This is a purely additive feature - [ ] n | Is it dependent...
