VaultFactory + VaultImplementation

​

VaultFactory

function deployVault(address user) external returns (address vault);
function vaultOf(address user) external view returns (address);

• deployVault is idempotent — calling it for a wallet that already has a vault is a no-op that returns the existing clone address.
• At creation the clone is initialised with vaultOwner = user and auto-approvals to CTFExchange, NegRiskAdapter, PredictStreetNegRiskCtfExchange, ConditionalTokens.
• deployVault consumes ~4M gas for the very first clone (storage initialisation of the auto-approvals). Send a gasLimit of 5M to avoid out of gas reverts. Subsequent re-calls are no-ops and cheap.

​

Bootstrap: vault → deposit

// 1. Make sure vault exists
await (await vaultFactory.deployVault(eoa, { gasLimit: 5_000_000 })).wait();
const vault = await vaultFactory.vaultOf(eoa);

// 2. Approve USDC and deposit into the vault
await (await usdc.connect(user).approve(vault, parseUnits('1000', 6))).wait();
await (await new Contract(
  vault,
  ['function depositERC20(address token, uint256 amount)'],
  user,
).depositERC20(usdc.target, parseUnits('1000', 6))).wait();

​

VaultImplementation entry points

​

Splitting USDC into YES + NO inside the vault

1. Backend co-signature. POST /api/vault/split-signature with { marketId, amount }. Body of response carries the dual-sig payload the vault expects:
   {
     "pendingSplitId":  "...",
     "kind":            0,
     "collateralToken": "0x9bC8...241e1",
     "conditionId":     "0x...",
     "partition":       ["1", "2"],
     "amount":          "30000000",
     "salt":            "...",
     "deadline":        1776999999,
     "vaultAddress":    "0x...",
     "backendSig":      "0x..."
   }
   
2. Owner signature. Sign the same SplitPosition typed-data with the vault EIP-712 domain (see below) using the EOA key.
3. On-chain submit. Call vault.splitPosition(kind, collateral, conditionId, partition, amount, salt, deadline, ownerSig, backendSig).

​

Merging YES + NO back into USDC

1. Backend co-signature. POST /api/vault/merge-signature with { marketId, amount }. Response shape is identical to split’s, only the field name changes (pendingMergeId instead of pendingSplitId):
   {
     "pendingMergeId":  "...",
     "kind":            0,
     "collateralToken": "0x9bC8...241e1",
     "conditionId":     "0x...",
     "partition":       ["1", "2"],
     "amount":          "30000000",
     "salt":            "...",
     "deadline":        1776999999,
     "vaultAddress":    "0x...",
     "backendSig":      "0x..."
   }
   
2. Owner signature. Sign the same MergePositions typed-data with the vault EIP-712 domain. The struct field shape is identical to SplitPosition (same 7 fields); only the EIP-712 primary type changes from SplitPosition → MergePositions. Use type table below.
3. On-chain submit. Call vault.mergePositions(kind, collateral, conditionId, partition, amount, salt, deadline, ownerSig, backendSig).

{
  "<SplitPosition or MergePositions>": [
    { "name": "kind",            "type": "uint8"     },
    { "name": "collateralToken", "type": "address"   },
    { "name": "conditionId",     "type": "bytes32"   },
    { "name": "partition",       "type": "uint256[]" },
    { "name": "amount",          "type": "uint256"   },
    { "name": "salt",            "type": "uint256"   },
    { "name": "deadline",        "type": "uint256"   }
  ]
}

​

Emergency withdraw

initiateEmergencyWithdraw(ownerSig)       // starts 7-day timelock
// ... wait 7 days ...
emergencyWithdrawERC20(token, to, amount, ownerSig)
emergencyWithdrawERC1155(token, to, id, amount, ownerSig)

cancelEmergencyWithdraw()

​

Digest invalidation

invalidateDigest(bytes32 digest) external onlyVaultOwner;
invalidateDigests(bytes32[] calldata digests) external onlyVaultOwner;

​

Why EIP-1167 minimal proxy

• Gas-cheap deployment (~45k gas vs ~2M for a full copy).
• Non-upgradeable — implementation pinned, admin can’t hot-patch.
• Bug mitigation requires new factory + user-driven emergency withdraw.

​

EIP-712 domain

name: "PredictStreetVault"
version: "1"
chainId: <chain>
verifyingContract: <your vault clone address>