Everyield — chain-abstracted savings on Lattice diamonds (UXMAXX) - #1
Merged
Conversation
- Pin the partial-redeem amount (step 4) to the exact idle-only price (2e6 +/-1) so a future change to lattice's share math trips the test instead of a bare assertGt(got, 0). - Tighten the final-exit floor to assertGe(balance, 100e6): no principal loss allowed, not "loss capped at 1e6". - Drop the unused convertToAssets member from the local IERC4626Like interface.
…archive RPC + keystore
Add buildAdapterCuts(admin, vault, asset, provider) and an internal _deployAll(admin, asset, provider) so the recipe can target a testnet USDC/Aave-provider pair via the new runCustom entry point, while deployAll(admin)/run and the 2-arg buildAdapterCuts overload keep delegating to the mainnet constants unchanged.
…k 4a plan with cast-verified Aave addresses
…with DEPLOYER guard and RESUME flag
…tom broadcast paths
…ents/421614.json, Etherscan verify targets
… resume with Sourcify
…orge's .env auto-load
…ecyclable float, feeQuotes guard
…and assembly - Bump lib/lattice submodule v0.1.0 -> v0.2.0 (nested diamond-lib -> v0.3.0) - foundry.lock: pin lib/lattice to v0.2.0 via 'forge update dadadave80/lattice@v0.2.0' - EveryieldAaveInit: drop ReentrancyGuardLib.__ReentrancyGuard_init() + import (v0.2.0 transient ReentrancyGuard is init-free — Solady logic, mixin modifiers) - test/DeployEveryield.t.sol + test/EveryieldFork.t.sol: assemble via LatticeDiamond (@lattice/LatticeDiamond.sol) instead of @diamond/Diamond.sol, matching BaseDeploy._assemble - EveryieldCrank + DeployEveryield script recompile unchanged (import paths intact)
…ng targets, dropped from .env
…ts/42161.json (0.000572 ETH)
Add app/lib/everyield.ts (createDepositTx/createWithdrawTx via the UA SDK's createUniversalTransaction, readPosition/readApy for full-NAV on-chain reads) and app/lib/addresses.ts with the live Arbitrum mainnet deployment addresses. Also: widen the missing-keys gate in app/app/layout.tsx to require all five NEXT_PUBLIC_* env vars (Privy + Particle), not just the two Privy ones, so a partially-configured env can no longer reach the unguarded `!` reads in page.tsx's UniversalAccount init; and fix two latent tsconfig issues that this task's code newly exercises: bump target to ES2020 (BigInt literals need it) and swap the SDK's `paths` alias from a raw .d.ts (broke bun's runtime resolution) to a small re-export shim (types for tsc/next build, real module for bun test).
React 19.1.0 -> 19.2.7, lucide-react 0.x -> 1.25.0, eslint 9 -> 10.7.0, @types/node aligned to the Node 24 runtime in use. TypeScript 7.0.2 was attempted and reverted: it hangs next build's TypeScript setup step under Next 16.2.10, so typescript stays pinned to ^5.9.3. @particle-network/universal-account-sdk and @privy-io/react-auth are left untouched per prior decisions (2.x SDK drops a field page.tsx relies on; the Privy major is unverified against the 7702 hooks this app depends on).
…er-side; decode hex fee totals
…oss fee + activity
…ence returning-login wallet noise
…vault-aware labels; harden re-confirm
Max on SaveCard now reserves FEE_HEADROOM_USD ($0.50, ~3x the observed $0.14 fee) so depositing everything never leaves zero runway for the next transaction's own network fee. Preview/confirm failures across SaveCard and PositionCard are classified via classifyQuoteError — the SDK's "insufficient balance for gas fees" rejection now surfaces honest, specific copy instead of the generic "adjust the amount" text, which was misleading since the amount was never the problem.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Full build: three Lattice v0.2.0 diamonds live on Arbitrum One (vault 0x4aE34A2fA9efD143C0330c306dDF8808eE34815D), Particle UA SDK 2.0.3 in EIP-7702 mode, Next 16 app (prod: https://everyield.vercel.app, pitch at /pitch), keeper Makefile, CI green (contracts + frontend), docs (README/DEMO/SUBMISSION/SECURITY).
Live-proven with real funds on 2026-07-20: cross-chain USDC deposits Base→Arbitrum, 80/20 Aave crank, recall, partial withdrawals — every number verifiable against the vault address.
Any commits landing on the branch after this PR opens (in-flight: deposit fee-headroom + insufficient-fee messaging fix) flow into it automatically.