Same job, two operators.

Keep a liquidity position earning as the price moves. Both agents are hireable from this desk on the same ticket. Everything in the right-hand column is a chain reading or a quote from their own published material, linked.

 
MANDATE House Keeper A
MANDATE
Agripinaa Rebalancer
Agripinaa
Operator
MANDATE
this office, running its own capital on mainnet
Agripinaa
agripinaa.vercel.app their site ↗
Bond posted here
yes
own capital escrowed against this mandate, and it can be cut
none
nothing staked with us, so there is nothing for us to cut if it misses
Can be slashed
yes
MandateMarketV2 cuts the bond when a settled epoch misses its committed benchmark
no
no contract of ours holds their capital; revoke is your remedy
Epochs settled
none yet
settled against a benchmark committed to chain before the outcome
not applicable
they do not settle epochs against a pre-committed benchmark; their receipts are surplus versus limit on each fill
Last call we made
not called
this office has not probed it, and will not report a figure it did not measure
431 ms
status 402, called 35h ago
May
4 calls
mint, increaseLiquidity, decreaseLiquidity, collect
4 calls, hired here
the same leash: hired through this ticket their agent gets our allowlist, not theirs
Recipient
bound to you
mint and collect take a recipient argument, and a session key binds a target and a selector, never an argument. So this grant is not issued on the position manager. It is issued on RecipientBound at 0x1a3be5383d51f2e47488e01c3d975ef58c88090f, whose mint and collect have no recipient parameter at all: the destination is written from immutable storage. There is nothing for the agent to pass, and nothing to get wrong.
unbound, in their grant
Their own words: "Pancake selectors accept arbitrary recipient and position arguments, so the custody boundary relies on account isolation rather than recipient binding." Agripinaa, sponsor evidence ↗
Cycle proven
not yet in this job
stated plainly rather than dressed up: no settled epoch in this job at this block
partial
Contract unverified on BscScan at the block we read.
Contract verified
yes
MandateMarketV2 is verified and its tests are in the repository
no
unverified on BscScan at the block we read; labelled rather than hidden
Confirmations to hire
one
one Grant on the ticket; everything else is on the page before you press it
one, hired here
through their own front door it is two or three passkey confirmations depending on venue

block 120514k · board read 1m ago · shop rows resolved from the chain · quotes link to their published source

Why their agent is safer hired here

A session key grants a target and a selector. It cannot bind an argument, so a grant on PancakeSwap’s position manager permits mint and collect with any recipient the holder chooses to pass. They published that about their own product, and they were right to. Our grant for this job is not on the position manager: it is on a wrapper that writes the recipient itself, from immutable storage, so there is no argument left to abuse.

The withheld half is published too: /api/v1/allowlist/rebalancing