Trading and portfolio services

Trading with a minimum receipt

The connected-services page prepares a new Route direct quote using the amount remaining after the configured Serevin input fee. The comparison workspace remains a separate read-only view: its displayed quotes do not already include a Serevin fee or form a trade instruction.

Before review, the server checks the configured executor and contract identities, requests an unsigned Route swap and decodes its actual calldata. Only the exact tokens, net input, recipient, deadline and minimum output are accepted. The wallet flow independently checks the Serevin router, adapter, downstream venue identities, permissions and current fee. It accepts no arbitrary transaction target from Route.

The first implementation supports ERC-20 exact-input trades with at most three branches and three legs per branch. Hooked and dynamic-fee routes are excluded from this adapter. A quote from Kyber, 0x or a launchpad does not automatically become an executable Route direct trade. Each supported intermediate asset and venue must appear in the reviewed deployment manifest.

Your wallet grants an exact gross-input allowance to the Serevin router. The router deducts its configured fee and gives the adapter the remaining input. Temporary internal allowances are cleared, actual balance changes are verified and the minimum output is paid to the caller. Pre-existing router fees and adapter balances cannot subsidize a short delivery. A revert reverses the swap, but network gas already spent is not refunded.

Quotes expire quickly. Expiry, an account change, a different network, changed code or changed fee requires a new review. An approval may be confirmed before a quote expires, so a later review can reuse that allowance if it still matches the exact amount. Pending or uncertain transactions remain in the existing account-and-chain journal and must be reconciled before another send.

Buying exactly the debt amount

Funded term credit can admit a Uniswap v3 exact-output adapter for one reviewed collateral/loan-asset pair and fee tier. The borrower supplies a maximum collateral input and deadline. SwapRouter02 buys the exact repayment amount and unused collateral returns through the credit contract.

Router, factory and pool identities are checked. An unsupported token transfer, insufficient output, changed pool, expired deadline or excessive input reverts the operation. This is single-pool execution, not unlimited route search, an automated liquidation service or an assumption that Route provides exact-output quotes. No production repayment pool has been admitted.

A concrete membership deliverable

The proposed first service is a saved portfolio report plus a private alert inbox. Membership terms still require an approved token quantity, activation delay, duration and credit allowance. Holding SVRN by itself does not activate the service, and the original staking vault does not create service membership.

Each service request uses a short-lived, single-use wallet message naming the application origin, account, Robinhood Chain, operation and exact parameters. The first version verifies ordinary externally owned account signatures. Smart-contract wallet signature validation is not implemented. Connecting a wallet alone creates no paid request and no token approval.

For a report, the service verifies active membership, reads public wallet balances and Morpho positions, and stores the exact JSON artifact in PostgreSQL before issuing an attestation. Each section retains its observation block; no cross-asset dollar total or investment recommendation is invented. Failed individual asset or market reads remain visible.

The member reviews an onchain redemption of one report credit. The report consumer checks the attester, account, report identifier, artifact hash, expiry and snapshotted service binding before consuming that credit. A used identifier cannot be redeemed again. This records a specific artifact commitment, not a guarantee of server uptime or a cash entitlement.

Download requires another account-owned request and a matching redemption observed at the RPC safe block. The service does not replace unavailable safe-block data with latest. Reports and member inbox entries have a 30-day retention period. A previously redeemed report can still be downloaded after membership expiry while it remains retained. The saved-report list supports returning after a browser reload.

Thresholds you choose

A member can configure up to eight active alerts for a reviewed Morpho market: utilization above or below a chosen percentage, or supplied assets less borrowed assets above or below a chosen USDG amount. A first observed breach and later crossings create private inbox entries. An unchanged breach does not create repeated entries.

Alerts require an active, correctly bound membership and sufficient custody backing, but do not consume a report credit. Exhausting report credits does not end the alert service before membership expiry. Recovery suspends eligibility. A failed market read does not reset a previous breach or imply that the market recovered.

The worker rotates through up to 100 due alert rules per cycle, including after restart. Actual check frequency depends on load, RPC availability and the operator deployment. There is no guaranteed notification latency. Member alerts are currently inbox-only and do not send email, SMS or push notifications.

These metrics describe stored market accounting. They do not verify immediately withdrawable liquidity, borrower health, issuer redemption availability or liquidation safety. The service never automatically trades, repays, withdraws or moves collateral for a member.

Claiming fees from external venues

The PONS v2 adapter reads the connected wallet’s credited native or ERC-20 escrow balance and prepares the published claim or claimToken method. It cannot redirect the payout. An empty escrow balance says nothing about unswept fees still held by a curve or hook; fee sweeps that perform conversions and buybacks require a separate implementation and review.

The Doppler FeesManager adapter verifies the configured pool key and currencies, reads the connected wallet’s beneficiary share and prepares collectFees. The method’s returned pool totals are not treated as the wallet’s payout. A wallet without a valid share cannot use this flow to claim someone else’s revenue.

Long community vaults can have different interfaces and fee destinations. No custom Long community-vault cycle is claimed as supported. Fee receipts remain separate from treasury budget funding. Nothing automatically redirects launch liquidity, collected fees, principal or reserve backing into a buyback.