Skip to content

CoreWriter venue

The CoreWriter venue (hypercore-corewriter) supplies into a HyperCore vault — the same HLP-style yield as the Core vault venue — but settles through a gasless ERC-4337 smart account on HyperEVM instead of a direct Core L1 action. One signed operation calls CoreWriter.sendRawAction(vaultTransfer) as the account, so the deposit is composable with EVM actions and sponsored by Edith's paymaster.

This is the flagship of Edith's account-abstraction path: it unifies HyperEVM and HyperCore behind a single signature.

How it differs from the Core vault venue

Core vault (hypercore-vault) CoreWriter (hypercore-corewriter)
Chain HyperCore (synthetic id) HyperEVM (998 / 999)
Signature a Core L1 action (typed data) a UserOperation hash
Gas none (Core is gasless) sponsored by the paymaster
Custody the user's Core account the user's smart account (on Core)
Composable with EVM no yes

Both earn the same vault yield; pick the CoreWriter venue when you want the gasless smart-account UX or plan to compose the deposit with EVM steps.

The flow

The deposit flow is unchanged — quote, sign, deposit — only what you sign differs.

  1. Quote. Request a quote for the venue's chain and asset. When the winning venue is a CoreWriter venue, Meadow resolves your smart account and builds a paymaster-sponsored UserOperation (via Photon's bundler), returning a txPayload of kind erc4337UserOp with a userOp and a userOpHash.
{
  "kind": "erc4337UserOp",
  "userOp": { "sender": "0x…", "callData": "0x…", "…": "…" },
  "userOpHash": "0xabc…"
}

  1. Sign. Sign userOpHash with your wallet (EIP-191 personal_sign) — the account owner is the signer.

  2. Deposit. Send the signature as executeSignature. Meadow attaches it to the operation and submits it through Photon's bundler; the order tracks to confirmed like any other.

curl -X POST https://meadow.example.com/v1/deposits \
  -H "Content-Type: application/json" \
  -d '{ "quoteId": "…", "executeSignature": "0x…" }'

Prerequisites

  • The chain must have smart accounts configured (account factory + paymaster + paymaster key) and the venue wired with hlp_corewriter_vault.
  • Your smart account must already hold Core balance for the deposit. Bridging EVM funds into Core within the same operation is a planned refinement; today the venue targets already-funded Core balances.
  • The account owner must be a registered Edith user (they are the metered payer of the sponsored gas).

Positions

Positions accrue to the smart account's Core address rather than your EOA; track them through the account address. See Track positions and earnings.