About LemiPay

Shared money is socially fragile. When friends, housemates, or project teams pool funds informally, trust carries the whole system. One person holds the wallet or the spreadsheet; everyone else depends on that person's honesty and availability. Under pressure—disputes, exit, or simple forgetfulness—these arrangements break.

Traditional apps help with the math: they calculate who owes whom. They do not enforce coordination. Debts are tracked; execution is still manual and opaque. LemiPay exists to introduce programmable shared treasury logic: rules defined upfront, funds on-chain, execution transparent and deterministic.

In LemiPay, funds are deposited into a shared on-chain treasury. Rules are defined upfront: who can propose spending, how many approvals are required, which assets are allowed. No single party has unilateral control. There is no hidden ledger and no informal treasurer—the contract is the source of truth.

Every deposit, proposal, and approval is visible and verifiable. Outcomes are deterministic: if the rules are met, the contract executes. This shifts coordination from social guesswork to programmable infrastructure.

LemiPay sits at the intersection of bill-splitting apps, social payment apps, multi-sig wallets, and Web3 coordination tools.

Other apps calculate who owes what. Venmo and similar apps socialize payments between individuals. Gnosis Safe and other multi-sigs secure shared custody. LemiPay focuses on coordination: temporary or ongoing shared funds with clear rules, transparent proposals, and on-chain execution. We complement rather than replace these tools—we add programmable group logic for shared treasuries.

We build on Stellar for infrastructure optimized for money movement: fast finality (typically 3–5 seconds), extremely low fees, and a stablecoin-native ecosystem. Stellar is designed for real-world payments and settlements, not DeFi complexity.

Soroban smart contracts give us programmable treasury logic without sacrificing speed or cost. We chose infrastructure that fits collective spending and real-world use, not speculation-first chains.

Our early focus is Web3-native communities: hackathon teams, small DAOs, coliving groups, and project-based collectives. These users already have wallets, are comfortable with smart contracts, and frequently need temporary or recurring shared funds.

They also need coordination that scales—proposals, approvals, and execution without a single point of failure. Starting here lets us refine the product with users who understand the stack, then expand to broader audiences as onboarding and tooling improve.

Long term, we see shared treasuries as a primitive: a standard way for groups to hold and spend money together with programmable rules. That primitive can underpin everything from event budgets and travel pools to ongoing DAO operations and community funds.

We are building infrastructure for collective spending—transparent, rule-based, and chain-native. The goal is to expand from Web3-native early adopters to mainstream users as wallets and fiat ramps improve, so that programmable group coordination becomes a normal part of how people manage shared money.