Seal a strategy

Five numbers, encrypted in your browser and written to chain exactly once. Read the warning below before you fill anything in — it is not a formality.

There is no edit. No updateParams, no admin override, no upgrade path. If a value here is wrong, the only remedy is to register a new strategy with a new commitment and a track record starting at zero — and the mistaken one stays in your author history forever, because that is what makes the history worth reading.

Parameters

Ready

NameCosmetic. It is deliberately not part of the commitment — that has to cover exactly what the enclave computes on and nothing else.

Target WETH weight euint256How much of the book to hold in WETH when the entry signal fires. 6000 = 60%.

Entry threshold eint256The signed price move that triggers entry, in bps. 200 = +2.00%.

Exit threshold eint256The signed move that triggers exit. Negative values are normal. −150 = −1.50%.

Max trade per epoch euint256Your own risk limit, as a share of the strategy’s own book. 1000 = 10%.

Direction bias eint256+1 reads a rise as an entry; −1 reads the same rise as an exit.

Performance fee, bpsPublic and immutable, capped at 3000 (30%). Charged only above the high-water mark, per share — an allocator has to be able to read this before committing capital.

Ranges are advice, not enforcement — the values are encrypted, so no contract can check them. The arithmetic is written to behave for any input: a garbage parameter produces a bad strategy, never a broken pool.

What lands on chain

Five handles like this one, and a hash of them. Not the numbers you typed — those are encrypted in this browser tab and never sent anywhere.

0x0000007a6923…e1f3a8What a sealed parameter looks like
This is all anyone can ever see. A handle is a 32-byte pointer to a ciphertext held inside the TEE — not the value, and not an encrypted form of it you could attack offline. Reading it needs an ACL grant that nobody here has.

0x0000007a692301a4c7e2b9d1f0836e5c2a97b4d6e1f3a8