Bizantine Labs Docs

Operational Transparency

Team, custody, incident history, and operational controls for bizUSDT0.

Operational Transparency

This document covers the operational infrastructure behind bizUSDT0: key personnel, custody architecture, incident history, and business continuity procedures.


Key Personnel

NameRoleBackground
Noah BortnickPartner & Head of DeFi and On-Chain OperationsNearly a decade in crypto; founder of Carpathian Capital, a DeFi-focused digital asset manager specializing in vault curation, fund infrastructure, and audit-ready yield strategies.
Pavel SinelnikovHead of Product, Bizantine LabsFormer developer relations lead at Metis; focuses on vault risk reduction, opsec, protocol diligence, and translating on-chain opportunities into institutional-grade DeFi products.
Tony LingAdvisorCo-founder of Bitblock Capital; blockchain researcher since 2015; guest lecturer at Zhejiang University; investor in 50+ projects including ETH and Dash; author of Unlock New Cipher — From Blockchain to Cryptocurrency.
March ZhengAdvisorCrypto investor since 2016; B.A. in Economics and East Asian Studies from Washington and Lee University; provides on-the-ground perspective on Asian market sentiment and its influence on global crypto trends.

Custody Architecture

Primary Custodian: Fordefi MPC

  • Architecture: Multi-Party Computation (MPC) wallet with a 3-of-5 signing quorum.
  • Primary Manager Address: 0xf2dbC23e09f0df62613a1455aBEEc4EC536f1f36
  • Signing Quorum: 3 out of 5 authorized signers must approve any transaction.

Secondary Managers (Emergency Operators)

ManagerAddress
Noah Bortnick0xca0bFd5d7D79060c6c959062954330f5614bBaa0
Pavel Sinelnikov0xfBE0FeB78AC8E315a7a20F7d17C6e110c048d90F
March Zheng0x33fDEbBAF10D1381aeC76EA9d3362c95ABD094Da

Key Rotation Procedures

  • Key rotation is initiated by the primary manager through the Fordefi dashboard.
  • A rotation event requires 3-of-5 approval from the existing signer set.
  • All rotation events are logged on-chain and communicated to allocators within 24 hours.
  • Secondary manager keys are rotated annually or upon personnel changes, whichever comes first.

Redemption SLA

Normal Conditions

  • Expected Settlement Time: Immediate to 5 minutes for redemptions covered by the reserve bucket (up to 8% of TVL).
  • Settlement for Sleeve-Dependent Redemptions: 1-24 hours, depending on Mystic withdrawal queue depth.

Stress Conditions

  • Definition: TVL redemption requests exceeding 15% of TVL within a 24-hour window, or Mystic utilization above 95%.
  • Expected Settlement Time: 1-3 business days.
  • Communication: All depositors will receive on-chain status updates. The operations team will post a status briefing within 2 hours of identifying stress conditions.

On-Chain Audit Trail

Every vault action — deposits, redemptions, rebalances, harvest swaps, and fee payments — is recorded on the Flare blockchain and is publicly viewable.

Vault Address on FlareScan:

https://flarescan.com/address/0xb7c1c8f7191c7d76b5c6650a6fb20f6f8027bf0d

Key Event Signatures to Monitor:

EventDescription
DepositDepositor deposits USDT0 into the vault
WithdrawDepositor redeems shares for USDT0
Deposit(address,uint256,uint256)USDT0 deployed from reserve into Mystic sleeve
Withdraw(address,uint256,uint256)USDT0 withdrawn from Mystic sleeve to reserve
SwapWFLR → USDT0 conversion on SparkDEX

Allocators and auditors can independently reconstruct the vault's full transaction history from on-chain data without relying on off-chain reports.


Fordefi Due Diligence

Vendor Overview

Fordefi is an institutional-grade MPC wallet platform designed for DeFi asset management. The platform provides secure key management without single points of failure.

MPC Architecture

  • Key Generation: Distributed key generation ceremony with no single party ever holding the complete private key.
  • Signing: Threshold signature scheme requiring m-of-n participation (3-of-5 for bizUSDT0).
  • Key Shares: Distributed across independent hardware and cloud environments.

Disaster Recovery

  • Fordefi maintains encrypted key share backups with geographic redundancy.
  • Recovery procedures are documented and tested quarterly.
  • Full key recovery can be executed within 24 hours in the event of hardware failure.

Insurance & Backstop

Protocol-Level Insurance

  • Superform: Insurance fund or backstop mechanism status is pending documentation.
  • Mystic: Protocol-level insurance or first-loss capital status is pending documentation.

First-Loss Capital

  • No dedicated first-loss capital buffer has been established for bizUSDT0 at launch.
  • The vault relies on the security of the underlying protocols (Superform, Mystic) and the operational controls described in this document.

Business Continuity

Operator Unavailability

  • If the primary manager (Fordefi MPC) is unavailable, any secondary manager can execute emergency operations using their individually-controlled address.
  • Secondary managers are authorized to: execute redemptions, trigger harvests, and perform rebalances.
  • Secondary managers are not authorized to: change vault parameters, modify the fee structure, or add/remove sleeves.

Timelock Protections for Depositors

  • Depositors can always redeem their shares, subject to reserve adequacy and Mystic withdrawal queue status.
  • The vault contract does not implement a timelock on depositor redemptions.
  • If all operators become unavailable, depositors' funds remain in the Mystic sleeve and reserve bucket is accessible by any address with operator privileges on the Superform vault.
  • In a worst-case scenario where all operator access is permanently lost, depositors would need to coordinate with Superform governance to recover funds.

On this page