CatiPay

Liquidity orientation layer for on-chain markets

Depth before yield. Conditions, not promises

[CatiPay @CatiPayRH]

$CATI is live

CA:
0x24bc3f32289646a5bc7ccce5f71cdeed8b386e08

A payment should not begin with a signature. It should begin with a read

CatiPay inspects the recipient, token, allowance, gas and calldata before your wallet opens. No custody. No private keys. No blind signatures

[CatiPay @CatiPayRH]

Where do the numbers come from ?

Every visible value comes from wallet state, an RPC read, a contract call, a simulation or a transaction receipt

When a service is not configured, the UI says so. It never invents a value

[CatiPay @CatiPayRH]

CatiPay never asks you to trust a green checkmark

So we will not ask you to trust us on the liquidity either

$CATI LP is locked on @pinkecosystem

Proof: https://t.co/vU6i9eoAiQ

[CatiPay @CatiPayRH]

What is already permitted ?

allowance(owner, spender) is read and compared with the request

Zero, limited, high or unlimited. It is reported, not judged. You decide what that number means for you

[CatiPay @CatiPayRH]

A receipt lands on the desk :

25 USDC from vitalik.eth to protocolguild.eth on Ethereum

Nothing is signed. Nothing has moved

First, read the request. The ENS is resolved, the address is read from the chain right now. Contract or account, balance, bytecode. No guesses

[CatiPay @CatiPayRH]

Three things we never do :

/ Hold funds
/ Ask for seed phrases or private keys
/ Sign or broadcast without your wallet's explicit confirmation

CatiPay prepares the transaction object. Your wallet does the rest

[CatiPay @CatiPayRH]

The cat checks before you pay

CatiPay reads the recipient, chain, token, amount, balance, allowance, gas and calldata of a payment. Then it prepares a transaction you can inspect before signing in your own wallet

A payment should not begin with a signature. It should begin with a read