Skip to content

IPSProtocol/Web3-Security-Manifesto

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

Web3 Security Manifesto – by IPSProtocol

This manifesto outlines the values and principles driving the development of security solutions at IPSProtocol.

Our work is rooted in rethinking industry assumptions, approaches, and vision — designing systems that are redundant and resilient by default, built for adversarial conditions, and aligned with the unique aspects of decentralized environments.


1. Security must be evaluated under adversarial conditions.

Assume failure or malicious behavior at every level of the stack attempting to undermine the system. Protection must hold even when all the components are compromised.


2. Focusing on specific attack vectors is insufficient.

As foundational technologies and smart contract use cases evolve, new and unpredictable attack vectors will emerge. Systems that rely on known-pattern detection cannot scale and will always fail to protect the system.


3. Web3 security cannot be solved by AI or Web2 paradigms alone.

The decentralized, permissionless nature of public blockchains introduces unique threat models and trust assumptions that cannot be solved by existing solutions.


4. Minimize trust.

Design with the fewest possible assumptions. Where trust is required, enforce authenticity, integrity, and confidentiality through cryptographic guarantees.


5. Clarity and simplicity prevent user error.

Improving interface clarity and reducing complexity lowers the risk of unintended or unsafe actions.


6. Users are not security boundaries.

Do not assume users will act correctly. Build redundant mechanisms that detect, block, or recover from user mistakes.


7. Security must reduce user burden.

Users should not need protocol expertise to stay safe. Protection must be by design, passive as much as possible, and embedded. - Do not claim that users need a dedicated computer running a short-term memory OS just to sign transactions safely.


8. Web3 security solutions must integrate the asynchronous and decentralized nature of the system.

Security boundaries must hold across time and evolving system state, accounting for the asynchronous and decentralized nature of the environment.


9. Redundancy is not optional

Security layers must include internal fallback mechanisms or be independently verifiable through external systems.

About

Web3 Security 2025 Manifesto - Vision and principles that should be the foundation web3 security tools development

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors