Smart Contracts

Public deployment registry for the Beav3r onchain verifier stack.

Base Sepolia

Provisioning returns the executor address for each onchain actor. Downstream contracts grant permissions to that returned executor address.

Integration Notes

Beav3r deploys and provisions the onchain execution stack. Integrators:

• inspect the published verifier stack contracts
• trust the executor address returned during provisioning
• whitelist or permission that executor address downstream

Custom Executor

For projects that need custom execution logic, Beav3r also supports an executor pattern that keeps Beav3r authorization checks while allowing project-defined routing after verification.

Source:

• Protocol repository: beav3r-ai/beav3r-protocol 
• Protocol README: README.md
• Deployment artifact index: DEPLOYMENTS.md
• Base Sepolia artifact: deployments/base-sepolia.json
• Interface: src/interfaces/IBeav3rExecutor.sol
• Base contract: src/Beav3rCustomExecutorBase.sol
• Onchain demo script: beav3r-demo/onchain-example.mjs

Use:

• IBeav3rExecutor for integrations that call executeWithAuth(...)
• Beav3rCustomExecutorBase as an abstract base for custom logic

Minimal pattern:

contract TreasuryExecutor is Beav3rCustomExecutorBase {
    function _executeAuthorized(address to, uint256 value, bytes calldata data)
        internal
        override
        returns (bytes memory)
    {
        // Final step only: all Beav3r checks already passed before this call.
        // custom flow, for example:
        // - decode data
        // - call token keeper
        // - enforce project-specific limits
        (bool ok, bytes memory ret) = to.call{value: value}(data);
        if (!ok) revert();
        return ret;
    }
}

This keeps nonce replay protection, signer verification, account binding, and executor binding identical to the standard Beav3r executor while allowing application-specific execution paths.

No mainnet deployment is published yet on this page.