Blazing fast
Powered by Kaspa. Bids settle in seconds, not minutes.
Rank any link with KAS. Keep bidding the same host to climb.
Leverage the speed and low-fee power of Kaspa.
Payments remain disabled until every transaction can be matched safely to one submitted host.
No bids yet. 100 KAS opens the first seat.
The first accepted 100 KAS bid creates the first seat.
Powered by Kaspa. Bids settle in seconds, not minutes.
Small bids stay small. More KAS goes to your rank.
Every accepted bid is visible and verifiable on-chain.
No card processor and no account to create.
Rank what matters to the Kaspa ecosystem.
Pay to rank
Pay-to-rank means money is the score. You do not farm upvotes or buy a CPC: you pay, you sit, and the number is public.
Kaspa.bid is pay-to-rank for websites. The score is KAS. The rail is Kaspa. One http(s) host gets one row. Bidding on that same host stacks.
Rank is the total KAS paid on a host. Not clicks, time, or a recency boost. The first accepted seat is 100 KAS. Afterwards, 100 KAS more than the leader takes #1. A smaller accepted bid still lands, wherever its total places it. Amounts use 100-KAS steps.
The receiving address is kaspa:qzfpdz4xce0mzx5nl0w089k3efjzeqwwzchmvcckf64hcpdg06kkzry4lyq7e. It is not yet accepting automatic bids.
How Kaspa.bid works, what stacks, what does not, and how a Kaspa payment gets matched to a seat.
The first accepted sit is 100 KAS. Afterwards, 100 KAS more than the leader takes #1. A smaller accepted bid still lands a seat, just not the top one. Amounts use 100-KAS steps.
You still sit once the payment is accepted and matched. Rank is the total KAS on that host, so you land wherever that total places you.
Yes. The same canonical host never creates a second row. Pay again and the KAS add to the seat you already have.
No. Clicks may be counted for context, but they do not climb. Time on the board does not climb. Only accepted KAS does.
One http or https host. Paths, www, and query strings collapse to the host. A social handle by itself is not a link.
No. The intended flow is: submit a host, receive a payment reference, and pay it from a Kaspa wallet. Nothing sits until the payment is confirmed and uniquely matched.
No. Once a valid bid is confirmed and accepted, it is final. A payment that is never confirmed or cannot be matched is not automatically placed on the board.
Any wallet that can send KAS to a Kaspa address, such as Kaspium. Wallet availability and supported features vary by provider.
Not by guessing from a public transaction. Each submitted bid will receive a unique payment reference and a one-time deposit address generated for that bid. The watcher records the confirmed output to that address, then credits the pre-registered canonical host exactly once.
No. Do not send a bid to the public address until the payment flow is live. A direct transfer to one shared address does not contain a reliable association with your intended host.