Launch

Docs

What Yopay reads, how it reads it, and the one rule the whole thing is built to keep.

The rule

Fees can be pointed at a handle whose owner never agreed, does not know, and may never collect. A ledger that writes all of that into one column called Received is not rounding. It is reporting the opposite of what happened. So there are four columns here and they are never added together, and the only one that counts as received can be written by one thing: a claim, carrying the signature of the transaction that took the money.

There is no received column

The database has one append-only table of events. `received` is a VIEW that sums the claims. Nothing can INSERT into a view, so the total cannot be set - only earned.

A claim needs proof

A CHECK constraint refuses any RECEIVED row without a transaction signature and a slot. Declaring money received on somebody's word is a write the database rejects.

One claim per signature

A unique index on the signature. A replayed claim is counted once.

A figure cannot be rendered bare

Every figure carries the slot it was read at. There is nowhere in this application to print a number without also printing when it was true.

Unread is not zero

A balance that could not be read is struck through and named unread. A zero is a reading; an absence is not.

What it reads

programpfeeUxB6jkeY1Hxd7CsFCAjcbHA9rWtchMGdZ6VojVZ
account size1024 bytes
mint offset11
admin offset43
shareholders offset80

Those offsets were checked against mainnet before any of this was written, and the check is still running rather than remembered: 700,324 accounts matched 1024 bytes and 0 matched 1023, so the filter distinguishes, read at slot 451,432,293, 8 min ago. The pubkey at offset 11 resolves to a real mint with a real supply. A lookup uses memcmp at that offset rather than a guessed address derivation. A guessed seed produces a pubkey that looks right and points nowhere.

Not built yet

The claim instruction. It needs authority this deployment does not hold, so the control is disabled and says why rather than failing in your wallet. Launching a token is built, and so is pointing a coin’s fees somewhere else: that sentence said neither was, and it was wrong.

The coin

Contract address

AkxLg5eTqqzxcJCBrTjF9ezRchkDvCgD6faz1DN6pump

The mint could not be read just now, so nothing about it is shown. That is an unread, not a zero. The address above is still the address, and everything else on this card waits for a reading.

Where Yopay is

these are the only accounts. Anything else using this name is not us

Read a mint