Contracts
Official addresses for Gyndore tokens, LNMS Safe infrastructure and the live Base Sepolia testnet. The Borrow, Trade and Earn protocol is awaiting mainnet launch; its remaining addresses will be published here when deployed and verified.
Verify before you interact
Use the addresses below to verify shared contracts. Each LNMS member has a separate vault address, explained below. Rows marked Published at launch are not announced mainnet deployments. Do not trust copies: pinned messages, screenshots, search results, DMs, or anyone claiming to be support. Phishing and lookalike addresses are a common way funds are lost. To check an address, copy it from the list below, open the explorer link, and compare the full string. Confirm the contract is verified, then match it against your wallet's signing prompt before you approve anything. The protocol core is designed to be immutable. LNMS vaults are owner-controlled Safe accounts, whose configuration can be changed by their owner.
Contract addresses
GYND, bGYND and the existing Safe infrastructure selected for LNMS are listed below. Publishing the Safe addresses does not open LNMS signup. The remaining protocol addresses will be published at launch.
The list covers tokens, LNMS membership vault infrastructure, the bonded-token system and DEX infrastructure. Switch between Mainnet and Testnet above. Testnet shows the current Base Sepolia deployment. LNMS membership bonds are separate from the bGYND unbonding contract listed under Bonded token system.
Each published row copies its address and links straight to the block explorer, where you can read the verified source, follow the transaction history, and see the contract exactly as it runs. The remaining contracts are being audited ahead of mainnet.
LNMS membership vaults
LNMS uses the unmodified SafeL2 1.4.1 implementation and SafeProxyFactory listed above. Signup creates and initializes a separate Safe vault in one transaction. The member's wallet is the sole owner, with a signing threshold of one. The LNMS setup adds no module, guard, fallback handler or setup delegatecall, and gives Gyndore no owner or admin authority over the vault.
GYND transfers directly to the member's vault without an ERC-20 allowance. The owner can withdraw through Safe without LNMS login or permission from Gyndore. Deposit only into your own verified vault, never the shared implementation or factory address. Keep your vault address and owner wallet available for recovery. This is a single-owner account; it does not add the protection of multiple independent signers.
On 28 October 2026, the Base deployment bytecode and proxy creation code matched Safe's official deployment records and the compiled artifacts for its 1.4.1 release. LNMS checks the vault code, implementation, owner, threshold, modules, guard and fallback handler before requesting a deposit. Its backend verifies these again when activating membership. An owner can later change their Safe configuration; LNMS treats a detected change as requiring review.
Safe audit scope
Ackee Blockchain reviewed Safe 1.4.0, including SafeL2 and SafeProxyFactory with their imports. Safe's audit notes for 1.4.1 record one subsequent ERC-4337 compatibility fix. After notifying the auditors, Safe concluded that another audit was unnecessary. Read the published audit report for its findings and limitations.
This upstream review covers the Safe contracts, not the LNMS frontend, backend, price policy or membership rules. The LNMS integration has not undergone an independent audit. Matching an audited upstream release does not guarantee that an integration is free of vulnerabilities. Vault security also depends on the owner wallet and the transactions its owner authorizes.