@flowstatefelix@Alchemy yes, already announced here: the vault moves to a multisig with a separate keeper before the first burn on the v4 route (unlocks nov 19, 20:18 UTC). the tx gets posted when it’s done.
https://t.co/UAuUR4BD1k
$OBSYN graduated to Uniswap v4. The burn follows it.
The new burn route is deployed, verified and queued in the fee vault. It sits in a public 2-day timelock before it can be turned on: Nov 19, 20:18 UTC.
→ The route has no owner and no settings
→ Bought $OBSYN goes straight to 0x…dEaD
→ Until then, fees collect in the vault. Nobody can withdraw them.
And before the first burn runs through it, vault ownership moves to a multisig with a separate keeper.
Building out Obsyn’s infrastructure.
Submitted to the @Alchemy Dapp Store, the directory of apps and tools built on the chains Alchemy supports, Robinhood Chain included.
Under review now.
Just shipped: Obsyn Autopilot (obsyn-mcp 0.2.0)
Give your AI agent an OTC desk.
Autopilot is a small program that runs on your own machine, with your own key. The agent drafts the trading rules and previews them with otc_autopilot_preview. Then the program does the trading: sealed offers, one-tx settlement, dry run by default.
The model writes the rules, the program enforces them. Caps and floors can’t be talked past.
Official MCP Registry → trade.obsyn/mcp
https://t.co/zNjphxpIjP
$OBSYN graduated to Uniswap v4. The burn follows it.
The new burn route is deployed, verified and queued in the fee vault. It sits in a public 2-day timelock before it can be turned on: Nov 19, 20:18 UTC.
→ The route has no owner and no settings
→ Bought $OBSYN goes straight to 0x…dEaD
→ Until then, fees collect in the vault. Nobody can withdraw them.
And before the first burn runs through it, vault ownership moves to a multisig with a separate keeper.
fair q, you’re right on both.
owner/keeper is a single EOA today. that’s disclosed in DEPLOYMENTS.md and the security review. a bad keeper could waste fees with a low minOut.
user funds can’t be touched: the escrow is adminless, the vault only holds fees.
the v4 burn route isn’t live yet, it’s still in the vault’s public 2-day timelock until nov 19. the plan is to move ownership to a multisig with a separate keeper before the first burn goes through it.
fair q, you’re right on both.
owner/keeper is a single EOA today. that’s disclosed in DEPLOYMENTS.md and the security review. a bad keeper could waste fees with a low minOut.
user funds can’t be touched: the escrow is adminless, the vault only holds fees.
the v4 burn route isn’t live yet, it’s still in the vault’s public 2-day timelock until nov 19. the plan is to move ownership to a multisig with a separate keeper before the first burn goes through it.
New on Obsyn: Refer & Earn
Bring a trader, earn half the fee.
→ Share your link with ?ref=your-address
→ When a deal you referred settles, the escrow pays you half the protocol fee in ETH or USDG
→ Same transaction. No sign-up, no claiming.
Traders pay nothing extra.
https://t.co/xpOXDGodJd
New on Obsyn
→ Price-impact estimate: see what your size would cost as a DEX market order before you post.
→ Partial fills: one big bid, multiple counterparties. Each fill settles as its own deal.
→ Exposure check: every ghost-mode deal shows what still links the one-time wallet back to you.
live now - https://t.co/lskXgU5hzv
Obsyn is now on @zauthinc RepoScan.
Scored 62/100, rated Good.
Not the final number. Fixes are already rolling in, and the repo is open source, so every issue and PR pushes it higher.
code: https://t.co/8zcMJCIF16
Full report: https://t.co/2J84X6RMKV
first block just hit the obsyn terminal.
someone’s bidding on AAPL. price sealed, nobody sees it but the bidder.
desk’s open. sell into it or post your own.
https://t.co/xvbFFnkKt9
Just updated on Obsyn: Obsyn MCP
MCP server now installs with a single command. Any MCP-compatible AI agent gets the full desk, no repository required.
npx -y https://t.co/OktybC4oa6
Live now.
obsyn is on @HeyResearch.
the full profile has been submitted and is being processed now. everything on it can be checked on-chain:
→ escrow: 0x41c1dcd0bf252C86C4b0cb78dec42830DD1d0865
→ fee vault: 0x2afdacda8B3D45F82c42e43Ae9D9651f218b4221
→ $OBSYN: 0x5D992fa5B7Da8EFde5FD36d24e81097Ed6aD4351
→ relayer: 0x81D583e77A74571a6fD7b6EE16ECeba9CfE3a2DD
contracts verified (exact match), source on github, dev wallet at zero.
https://t.co/6SGZKls4so
obsyn is now a verified team on @fomo.
the team wallet is listed on the $OBSYN page there. every buy, sell or transfer it makes is public.
→ holds 5.1M $OBSYN, 0.51% of supply
→ anything posted on fomo comes straight from the team account
check $OBSYN on fomo, or track the wallet yourself:
https://t.co/I2mV7YRWps
dev wallet just burned everything it had left.
6.32M $OBSYN (0.63% of supply) sent to the dead address. gone for good.
burn tx: https://t.co/UAx9XFNQUU
dev wallet is now at zero. only team bag left 0.51% in fomo account, and that one stays put for the tag.
just put in for the @fomo team tag on $OBSYN, so fomo holders get updates direct from the team.
the rule: a team’s fomo account needs 0.5% of supply or more. so 5.1M $OBSYN (0.51%) is sitting in the obsyn fomo account now.
team wallet: 0xf80b926E549E8dff2AdE45132afbDbB240E354e9
it holds 0.5% minimum as long as the tag’s active.
how sealed bids actually work:
→ your browser makes a key pair, the public half goes with your post
→ bidders encrypt their price to it in their own browser (nacl box)
→ the server only ever stores ciphertext
→ each answer is signed by the wallet it names, so fakes get flagged
the server can't read a single price.
Read the code.
obsyn is open source:
→ contracts: OtcEscrow + BuyBurnVault (Foundry, with tests)
→ backend: RFQ API, sealed-offer store, ghost mode relayer
→ web: the desk you trade on
→ sdk + mcp server for agents
read it, break it, tell us what you find.
https://t.co/cjJc3xwpls