Luggom — a Cosmos SDK app-chain where you mine LUG by paying real taxes (public testnet)

i i had joined,

1 Like

Yes to (a), and your reason is the one that matters: changing the preimage for every rail would give each receipt that already mined a new hash that passes UsedPaymentIDs. US rails have no history yet, so they start scoped. One thing to settle per rail: the receipt number is all UsedPaymentIDs sees, so if a county later reformats it (drops dashes or leading zeros) or moves to a portal vendor that renumbers old payments, a payment that already mined comes back with a new hash. I’d normalize the id per rail and keep parcel, tax year and installment as a second key, with a rule for how partial payments count against it.

On (b), authenticated and re-issuable is better than reflective, but authenticated isn’t the same as payer-specific. On some county portals any registered user can add any parcel to their account and see whether it’s paid, so a logged-in page can still show someone else’s payment. I’d write it as “a page that lists payments made from that login”, and check each county with a second account: if it can add the parcel and see it paid, or open the first account’s receipt detail by its URL, the page doesn’t qualify.

On settled: for e-checks, cleared isn’t final either. A consumer can return an ACH debit as unauthorized up to 60 days after it settles, and the county usually reverses the payment while the LUG stays minted. With a 365 day window you can require ACH payments to be at least 60 days old before they mine. Card rails have the same question with chargebacks.

1 Like

The spec is updated with all three of your refinements — per-rail normalisation plus the
(parcel, tax year, installment) key, “a page that lists the payments made from that login” with the
second-account test, and 60-day ACH seasoning (chargeback window per processor for cards).

Implementation lands with the first US rail; the second key needs its own upgrade since it’s new
consensus state. Thanks — this closed three real gaps.

Welcome aboard! As you build the chain, if you have questions or doubts about the Stack while building the chain, please always feel free to reach out here, or directly.

On the product side, are you looking to create a verified taxpayer type of proof, or more focused on using that minted tax payment as credits that the municipalities can offer? (Lugano like!)

1 Like

Thanks — good question, and neither is exactly right, which is the interesting part.

We’re building a verified-taxpayer proof, not a municipal credit. The
municipality is only the registered recipient on-chain (tax_entity_id): it issues
nothing, backs nothing, and can’t freeze anything. The user proves they already
paid a real tax — TLSNotary attestation, no PII on-chain — and the chain mints
LUG against that payment at the basket price. So the tax payment is the minting
event, not a voucher: proof of a sacrifice that already happened. The taxpayer
keeps a share of it as LUG (30% in the current split) — a non-confiscable asset
they can hold, spend with businesses, or stake.

One precision on language: it is not a stablecoin. No peg, no issuer, no
redemption. The design target is that LUG orbits the basket — above and below,
never pegged to it: the basket is the emission cost, the vault sells at that same
price (a ceiling), and mining becomes much less attractive far below it (a soft
floor). The market still sets the price.

Where we are: the public testnet has been live since 21 October, with real mining
on a Brazilian bank (Banco do Brasil, block 144.732, code 0). US and Canada are
deliberately disabled until a rail passes our acceptance rules — so no, we don’t
have US/CA miners yet. In the coming days we’ll start onboarding ordinary users
and companies to mine and transact, to get people used to it and to exercise the
validator set.

Which leads to the invitation: would you like to run a validator? The testnet
guide (200 LUG bond, build from source) is in TESTNET/VALIDATORS.md — we’re
heading to 12 validators before mainnet, so an operator who cares about the
project is worth more than a slot.

And if you want to help on the product side, two things are open, and they’re
separate:

  1. US/CA rail pilots — a dev with a US or Canadian bank account who pays their
    own real tax (property, car, or business) and can share the receipt so we can
    build the extractor. Cosmos knowledge isn’t needed for this; it’s Rust/HTTP/regex.

  2. A Cosmos dev for the IBC side — Noble for USDC, Cosmos Hub for ATOM, relayers
    and the upgrade path.

Which of the three interests you most — validator, rail pilot, or IBC?

I can chat to the product points (I am part of the team at Cosmos Labs, so I cannot help with the validator/developer side other than recommendations :slight_smile: )

Gotcha! Seems interesting. The mention of municipality comes from what I’ve seen places like Lugano do: they incentivize people to use their payment system in exchange for an asset they can use to get rewards or discounts in their neighborhood. This could also help drive the “pay taxes” positive behavior with a similar loop. I see your point, though, regarding other uses! Very cool to hear it is being minted on a Brazilian bank already.

1 Like