LIPs

LIPs copied to clipboard

## What does this PR introduce? - Use `uint8` instead of `uint256` in LSP7 decimals We don't need `uint256` for decimals, `uint8` is more than enough. With `uint8`, decimals can...

YamenMerhi

## What does this PR introduce? This PR updated the LIPs according to the latest updates in the smart contracts around `transferOwnership` and `renounceOwnerhsip`.

b00ste

# What does this PR introduce? Introduce a new permission `ENCRYPT` in the LSP6 standard, placed after SIGN and before the SUPER permissions.

CJ42

A LSP9Vault is based on the ERC725X standard but it should not be allowed to use DELEGATECALL. DELEGATECALL is dangerous and could override the vault storage in unexpected ways, leading...

CJ42

[LSP0 and LSP9] Add two step process for renounceOwnership

7

This creates additional safety for a very dangerous action. Options are: Call `renounceOwnership()` 2x within 50 blocks Call `renounceOwnership()` and after `confirmRenounceOwnership()/renounceOwnershipConfirm()` within 50 blocks

frozeman

To be discussed

CJ42

[LSP9] Should we add ERC1271 to verify signatures at the vault

1

Adding ERC1271 `isValidSignature()` to an LSP9 vault would allow for login with a vault. Then vault would then call the `isValidSignature()` on the owner, to see if the signature can...

frozeman

## What this issue is about? As it presently is constructed, the contract is vulnerable to the allowance double-spend exploit, as with other ERC20/LSP7 tokens. Exploit Scenario: 1. Alice allows...

YamenMerhi

[LSP6] Should we split permission for `SETDATA`, into `ADDDATA` and `EDITDATA`

1

TBD

frozeman

docs: add first draft of LSP11 specs

3

## What does this PR introduce? - Introducing **LSP11BasicSocialRecovery** standard specs

YamenMerhi