Compliance Bond
Before a hauler or feedstock supplier delivers material, they post a bond into a long-lived escrow hold. It sits as collateral against the delivery being clean, properly manifested, correctly labeled, free of the contaminants and hazmat discrepancies that create downstream liability.
Feedstock · long-lived hold
What the bond covers
The bill of lading matches what actually arrives. A mismatch is a documented violation.
The right hazmat classification on the right material, the labeling that downstream handling depends on.
No hazmat discrepancies, no off-spec contamination that turns into downstream liability.
Genuine financial consequence sits with the party whose conduct created the exposure.
Post, hold, resolve
Because the bond is modeled as a deferred hold using the same fund-locking primitive as every other escrow on the platform, it required no special accounting machinery to build.
A hauler or supplier posts collateral into a long-lived hold ahead of delivery. It sits as a neutral deferred hold, not a payment, a guarantee of conduct.
// a bond is just a deferred hold const bond = await sentinel.holds.create({ party: hauler.id, mode: "bond", // deferred amount: 15000, covers: ["manifest", "label", "clean"] }) → state: pending · collateral held
When the delivery is clean, the bond returns through the standard release path, the same path a verified delivery escrow takes. Reliable counterparties never feel it.
A documented violation triggers a slash event that redirects the bonded funds toward cleanup, penalty, or remediation costs. It gives a safety director documented, dollar-backed leverage over third-party behavior on site.
Logged by safety officer · att-7780
Conduct, priced
Have third parties post a bond against clean conduct, returned in full when they perform, redirected to remediation when they don't.