Implemented adapter, controlled activation
The first LANDVILLE transaction adapter is deployed on Robinhood Mainnet. It supports a direct, single-pool ERC-20 to ERC-20 swap through Uniswap V3. The module must declare its transaction permissions and the operator must enable wallet transactions before requests can run.
At the time of this guide’s review, production activation and a published swap-module end-to-end test have not been confirmed. Contract deployment alone does not mean a live swap page is available. Look for a reviewed module in World and its actual availability message.
What a supported swap asks you to do
The module requests a quote, shows the trade and fee information, then asks for the required exact-amount approval and a separate swap confirmation. LANDVILLE constructs the permitted transaction; your linked wallet signs it.
Token addresses, gross input, treasury fee, amount being swapped, pool fee and slippage should be visible before you decide. A quote is not a completed trade. Check the transaction receipt in the explorer to confirm the on-chain result.
Where the 1% fee goes
The router sends 1% of the input token to its fixed fee destination and swaps the remaining 99%. The purchased token goes to the caller’s wallet. Uniswap’s pool fee and network gas are separate costs. The destination address is not displayed in LANDVILLE while the Treasury interface is under reconstruction.
For example, with 100 input tokens, the platform fee is 1 input token and 99 enter the swap. The output amount depends on the pool and slippage. Fee routing is separate from the unavailable Treasury dashboard and does not make its governance or reward controls active.
What is not supported yet
Native ETH input/output, multi-hop routing, automatic trades, arbitrary transfers, staking, minting and NFT purchases are outside the first adapter. ERC-20 trading also depends on a supported liquid pool and token behaviour; not every token or RWA is tradable.
Scrapy can design a concept for another type of transaction, but that action needs its own reviewed integration before it can execute. Generated modules never receive the treasury key, wallet private key or an unrestricted contract-call interface.
Deployment references
Network: Robinhood Mainnet, chain ID 4663. LANDVILLE fee router: 0x92a9a8308eD793D59c2653773F296F73BA9085B3.
Upstream Uniswap SwapRouter02: 0xCaf681a66D020601342297493863E78C959E5cb2. The Treasury destination is intentionally not displayed in the LANDVILLE interface while the Treasury is under reconstruction. On-chain contract data remains publicly inspectable.