Hey @unvault Team 🐛, Here is my case for the remaining 40% Beta spots. I’m not here to just click around; I’m here to stress-test your omnichain state machine until it breaks: 1. What can I test? • Cross-Chain State Transitions: I will aggressively test edge-case state sync between high-latency EVM chains (Ethereum L1, Abstract) and sub-second SVM/L2 environments (Solana, Base, ApeChain). • DIVIT Programmable Royalties: Verifying multi-currency royalty routing (ETH vs SOL vs APE conversions), fractional slippage, and split disbursements under volatile gas spikes. • Launchpad Concurrency: Simulating high-frequency multi-mint race conditions and front-running resistance on pending unlocks. 2. What am I good at breaking? • Dual-Wallet / Multi-Session Desync: Running concurrent sessions with MetaMask (EVM) and Phantom (Solana) hooked simultaneously, triggering network switching mid-transaction to detect state leaks. • Race Conditions on Unlock / Relist: Attempting to list an asset on Chain B while its unlock verification from Chain A is still within the mempool / confirmation window. • RPC & Network Timeout Failsafes: Testing how the UI & contracts handle dropped WebSocket subscriptions, node timeouts, and reorg rollbacks without locking assets in canonical limbo. 3. What will I notice that someone else might miss? • Metadata Inconsistencies: Dynamic attribute/IPFS updates failing to propagate across chains post-unlock. • Micro-Visual & Liquid-Glass UX Friction: Edge-case rendering bugs, decimal truncation errors on mobile viewport viewports, and signature payload ambiguities before signing. • Precise, Reproducible Bug Reports: Every bug I catch comes with exact reproduction steps, console error stacks, network request payloads, and screen recordings. You built UnVault to unlock the omnichain future. Let me help you harden it before mainnet. 🐛

Hey @unvault Team 🐛, I’m not here to just click around; I’m here to stress-test your omnichain state machine until it breaks: 1. What can I test? • Cross-Chain State Transitions: I will aggressively test edge-case state sync between high-latency EVM chains (Ethereum L1, Abstract) and sub-second SVM/L2 environments (Solana, Base, ApeChain). • DIVIT Programmable Royalties: Verifying multi-currency royalty routing (ETH vs SOL vs APE conversions), fractional slippage, and split disbursements under volatile gas spikes. • Launchpad Concurrency: Simulating high-frequency multi-mint race conditions and front-running resistance on pending unlocks. 2. What am I good at breaking? • Dual-Wallet / Multi-Session Desync: Running concurrent sessions with MetaMask (EVM) and Phantom (Solana) hooked simultaneously, triggering network switching mid-transaction to detect state leaks. • Race Conditions on Unlock / Relist: Attempting to list an asset on Chain B while its unlock verification from Chain A is still within the mempool / confirmation window. • RPC & Network Timeout Failsafes: Testing how the UI & contracts handle dropped WebSocket subscriptions, node timeouts, and reorg rollbacks without locking assets in canonical limbo. 3. What will I notice that someone else might miss? • Metadata Inconsistencies: Dynamic attribute/IPFS updates failing to propagate across chains post-unlock. • Micro-Visual & Liquid-Glass UX Friction: Edge-case rendering bugs, decimal truncation errors on mobile viewport viewports, and signature payload ambiguities before signing. • Precise, Reproducible Bug Reports: Every bug I catch comes with exact reproduction steps, console error stacks, network request payloads, and screen recordings. You built UnVault to unlock the omnichain future. Let me help you harden it before mainnet. 🐛

I'm definitely looking for an opportunity to test the market. As someone who has been an active user of NFTs for years, I would love to be among the first to test such a large market. Space link - xitter.cf/i/spaces/1RKZzBOLEyDKB @AaronHaber @ernestleedotcom @unvault