Loops HouseNearAnyStake

NEAR HACKATHON
Links
Team
1 member- DAOwner
Danya
Overview
Problem: someone holding USDC on Base or SOL who wants to stake NEAR usually goes through a bridge app or an exchange, moves the NEAR to a NEAR wallet and only then stakes it.
Product: NearAnyStake stakes NEAR from any of 25 chains (67 tokens). The user connects a NEAR wallet (Meteor, HERE or Intear), picks what to pay with and where to stake: a validator pool, Rhea rNEAR, LiNEAR, or Instant stNEAR from Meta Pool. They pay once from an EVM, Solana, TON, Tron or Bitcoin wallet, or by hand to a one-time deposit address. NEAR Intents delivers native NEAR to their own account (Instant stNEAR: the stNEAR itself, nothing to sign), and one signature stakes at most what arrived, never what was already there, leaving a reserve so they can unstake later. Portfolio shows the validator, rNEAR and LiNEAR positions with unstake (live epoch countdown), withdraw and cash out to any chain. Without a wallet the app runs in dry-run mode: real quotes, pools and APRs, nothing payable. Non-custodial: no contract or server of ours holds funds or keys.
How NEAR fits: the browser asks the NEAR Intents 1Click API for nep141:wrap.near with recipientType DESTINATION_CHAIN, delivered as native NEAR to the user's account. The app reads that delivery on chain (the Transfers from intents.near in 1Click's delivery transaction), takes the lower of it and 1Click's reported amountOut, and stakes the lower of that and what the account can stake. Staking goes straight to NEAR validator pools (deposit_and_stake, unstake, withdraw_all) or to the rNEAR and LiNEAR contracts, through open npm modules from Any Wallet Kit (@anywalletkit/protocol-staking-native-near and protocol-staking-liquid-near), which re-check the pool and refuse if the transaction differs from what the user saw. Cash out goes back through 1Click.
Live on NEAR mainnet: https://nearanystake.xyz. The author also submits NearJar, a separate project; this one reuses some of NearJar's wallet and pay code, and both READMEs name each other.