Contract
1EaGq2PtdsxhZicYsrMXcVMLXMdyqpbUNQJjfZBpump
Advancing
LoadingAssay Board
Assaying is the bench step between finding ore and believing it is worth something. Enter a bitcoin amount and the board separates the projected return by who pays it, prints the rate that survives every incentive schedule, and prices the exit at the same moment as the entry.
The board reads every rate, allocation and queue parameter from the LODZ service, and that service did not answer this request. No figures are shown rather than cached or assumed ones: a rate you cannot trace to a source is exactly what this page exists to argue against.
Reload in a moment. If this persists, the seam listing and the redemption queue will be unavailable as well, since all three read the same catalogue.
Assay Office
The board above is one caller of the LODZ decomposition feed. A protocol that has to show how much of its own yield is fee revenue can read the same feed rather than assemble the collection pipeline a second time. Access to it is metered, and it settles in $LODZ.
The bench calls the endpoint from your own browser, on a key issued free and without a wallet, so the request and the answer are both things you can watch rather than take from this page.
01
A protocol quoting a rate to its own depositors and needing to say how much of it borrowers and traders actually pay, rather than an incentive schedule or a counterparty on the losing side of a trade. An allocator asking the same question about a position it already holds. Anyone who has to answer what happens to the number when the schedule ends, with a figure rather than a view.
02
The arithmetic is the cheap part. Under it sits rate collection per venue, telling an incentive-token payout apart from a fee payout, carrying the end date of every schedule that pays into a seam, keeping the observation window a rate came from attached to the rate, and holding two sources that disagree apart rather than averaging them into one plausible number. That pipeline is already running, and the board above is what it looks like from the outside.
03
A reading is paid for by sending $LODZ to the account below, proving the transfer was yours, and submitting the transaction signature. The service reads the chain, confirms the transfer landed, and credits reads against it. There is no signature from our side anywhere in that exchange: no approval to grant, no allowance to set, no contract of ours standing between a wallet and the transfer. The payment is an ordinary token transfer built and broadcast by the payer, and our half of it is a read.
04
Not one blended rate. The split by who pays it -- sustainable, emissions, counterparty -- each carrying its own figure, alongside the rate that is left once every published schedule has ended. Per seam rather than per portfolio, with the venue, the window the rate was measured over, the end date of any schedule paying into it, and the caveat the service attached to its own number where it has one.
The counter is not answering, so its terms are not on this page at this moment. What the panels above describe is the procedure, and that part does not move. The price and the readable endpoints are read off the wire when the service publishes them and are never typed into this page, which is why this panel is empty rather than holding an approximate figure.
Do not send anything to this account yet. The metering that would credit a transfer is not open, a token transfer cannot be recalled, and a payment arriving before there is anything to credit it against is simply lost. The account is printed so it can be looked up now and matched later, not so it can be paid now.
Token to send -- $LODZ mint
1EaGq2PtdsxhZicYsrMXcVMLXMdyqpbUNQJjfZBpumpAccount to pay -- owner address
4qbbSkZTTm1DKL5h6tbSiGzfkzf8X6viWSBeFUzHHTKpTransfer built as Token-2022 · 6 decimals
Send $LODZ and nothing else. A token transfer addresses the owner, so this is an owner address and a wallet resolves the Token-2022 account under it for the mint printed above. Anything else that lands there -- a different token, SOL, an item -- is not credited and is not returned. There is no recovery process and none is being offered, so check what you are sending before you sign: a mint that merely looks similar is the whole of how a substitute token gets paid instead.
Worth stating plainly: this is the same account that can replace the on-chain program. One key stands behind both, which is a smaller number of separate parties than the arrangement might suggest, and anyone routing money here should count it themselves rather than take it from this sentence.
The price is set in $LODZ, and there is no oracle converting it from a dollar figure. If the token trades higher, the feed costs more in dollar terms; if it trades lower, it costs less. That is the design and not an oversight, and it is worth being direct about the reason.
A protocol that reads this feed has to hold and spend the token to do it, so each additional reader is additional demand for it, arriving from somewhere other than speculation. Priced in dollars, that connection is cut: the token becomes a payment rail with a conversion step in front of it, and the feed could succeed completely while giving nobody a reason to hold it.
This is a statement about where demand would come from. It is not a claim about what the price will do, and nothing here should be read as one.
A price denominated in a token invites one question before any other: whether whoever is charging it can simply make more of the token. On this mint nobody can, and that is not an undertaking anyone has given. It is the state of an account, and one call to a public RPC endpoint returns it.
Removing a mint authority is one-way: no instruction puts one back. So no further $LODZ can be issued by anyone, permanently. The freeze authority is gone on the same terms, so no account holding the token can be frozen.
Supply is the one figure above that still moves, and it moves in one direction. This site carries a burn surface that lowers it and there is nothing that can raise it, which is why the number is dated rather than presented as live: read at slot 440,204,237 on 2026-08-19T05:24Z.
None of this says the token is safe, and it is not offered as though it did. It is what the account contains. Check it yourself against the mint printed beside the payee account -- the token program below is the one that owns it.
Token program
TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEbThis is a counter being opened, not a customer list. Nothing resembling a logo, a quotation or a usage count belongs on it until there is something true to put there, and nothing of the sort is on it now. No protocol has bought a reading, because there is nothing yet to buy one through: the feed answers today without a key, and what the counter adds is the metering and the settlement.