Risks

Using Bezel carries risk. This list is not exhaustive.

Smart contract risk#

Contracts can contain bugs. A bug could lock or lose tokens. Bezel has not published an audit. Do not assume one exists until it is published on @Bezel_rwa.

Oracle risk#

Triggers and notional rely on Chainlink feeds. A wrong but live price could let a trigger be proven. A frozen feed freezes all prongs on the asset, which protects holders but can delay protocols.

Issuer risk#

Stock Tokens are issued by a third party. The issuer can pause the token. Bezel cannot override an issuer pause. Corporate actions depend on the issuer's handling.

Protocol risk#

A prong executes against your vault when its trigger is proven. If you consent to a prong from a protocol with faulty logic, its trigger may occur when you do not expect it. Slashing compensates only up to the protocol's stake.

Verifier risk#

Each trigger is checked by a verifier chosen at placement. A flawed verifier can accept an invalid proof. Review the verifier before you consent.

Timing risk#

Execution happens only during market hours and never during a freeze. Positions can move while execution is blocked. Expiry keeps running during a freeze.

Regulatory risk#

Rules for tokenized securities differ by jurisdiction and can change. Stock Tokens are not available to US persons.

Impersonation#

$BZL is not launched. Scam tokens and fake sites may use the Bezel name. The only official channel for addresses is @Bezel_rwa.