Safenet checks

Safenet checks proposed Safe transactions against the Safenet Charter. Independent Sentinels evaluate the same transaction and identify whether it violates any applicable Charter rule. The binding version of the Charter will be published at the ENS record charter.safenet-gov.eth. Safenet focuses on transaction risks that can be determined from the proposed transaction and relevant Safe state. Economic attacks are outside the current Safenet Aegis scope.

​

What Safenet checks

Safenet checks the exact proposed transaction against the Charter version in effect when the transaction is proposed. Current coverage includes:

• Recipient and target manipulation.
• Known malicious or compromised addresses or contracts.
• Prohibited Safe configuration changes.
• Delegatecalls to unauthorized or unintended targets.
• Redirected value or asset transfers.
• Permissions granted to unintended or malicious addresses.
• Excessive or unlimited approvals.

A transaction is insecure if it violates an applicable Charter rule. The result references at least one violated rule and the applicable Charter version. See Safenet results for how Sentinel evaluations become a Safenet result.

​

Recipient and target manipulation

Safenet checks whether a transaction sends value, calls a contract, or grants asset-control rights to an unintended, unauthorized, malicious, or compromised address. Examples include:

• Address poisoning or manipulated recipients.
• ENS names resolving to unintended targets.
• Manipulated contract or execution targets.
• Redirected value.
• Permissions granted to unrelated or malicious targets.

​

Configuration changes

Changes to a Safe’s configuration can materially affect who controls the account or how transactions execute. Safenet checks covered changes to:

• Owners.
• Signature threshold.
• Modules.
• Guards.
• Fallback handlers.

Covered changes that violate the Charter are treated as insecure. Safenet also checks for delegatecalls to unauthorized or unintended targets, since delegatecall executes code in the context of the Safe. Legitimate configuration changes remain possible through the defined delayed execution and exit mechanism when the Safenet Guard is enabled. See Safenet Guard for details.

​

Approval and authorization risks

Safenet checks transactions that grant another address authority over assets or execution. This includes:

• Approvals for an unintended or malicious spender.
• Excessive or unlimited token approvals.
• Permissions unrelated to the intended transaction.
• Other authorization changes that grant asset-control rights to an unintended target.

These checks focus on what the proposed transaction authorizes. They do not assess broader economic risk.

​

Unsupported scope and evolution

Transactions that Safenet cannot reliably evaluate are not treated as secure. This can include unsupported or malformed transactions and transactions outside the supported network, Safe version, or transaction scope. Each transaction is evaluated against the Charter version in effect when it is proposed. Later Charter changes are not applied retroactively. Safenet’s coverage will evolve as the Charter is extended to address additional attack scenarios and transaction risks.