14 July 2026
Sa1𐤊rishnatext not yet in the index
Now I understand only Wallet O is used. One more question:
I see other attesters with much higher pending IGRA and iKAS rewards.
Are rewards based only on successful attestations and uptime, or does staking more than 400,000 IGRA increase rewards?
Tengri 𐤊 DAG🐬Фотография
Фотография
click to show
click to show
I’m curious—I just started yesterday. Here’s my dashboard. How long have you been running your attester? Are you staking more than the minimum 400k IGRA? Your rewards seem much higher than mine.
Replymessage unavailable
You can check all attestors info and copy their wallet and paste to Dashboard
Replymessage unavailable
The larger your share in the cake and the more uptime and trouble-free your server is, the greater your reward share will be.
Replymessage unavailable
If an attester PC reboots and is offline for 2–5 minutes, is there any penalty, or do you only lose rewards while offline? At what point do actual stake penalties begin?
Sa1𐤊rishnahttps://igra-labs.gitbook.io/igralabs-docs/for-attesters/attestor-setup-guide
In fact, you can find the answers to all these detailed questions here.
15 July 2026
Replymessage unavailable
I’ve decided to pause my attester. With 400k IGRA staked, the KAS fees, downtime penalties, and maintenance seem greater than the rewards I’m earning. Based on my experience so far, it isn’t financially worthwhile for a minimum-stake operator.
Mike DI’ve decided to pause my attester. With 400k IGRA staked, the KAS fees, downtime penalties, and maintenance seem greater than the rewards I’m earning. Based on my experience so far, it isn’t financially worthwhile for a minimum-stake operator.
Probably best for someone from the team to properly explain rewards. But they ramp up over time as your IAS score increases.
16 July 2026
Ссылка
click to show
click to show
From Igra-X:
"Most node platforms host your nodes and bill you monthly.
inverts the model: nodes run on your own infrastructure, which is why a single Igra RPC node can be free, permanently. Their beta is now open. Deploy an Igra RPC node in a few clicks, full node support is planned. app.novacula.io, code IGRA2026"
https://x.com/Igra_Labs/status/2077763549628129655?s=20
Replymessage unavailable
Ссылка
click to show
click to show
From Igra-X:
"Most node platforms host your nodes and bill you monthly.
inverts the model: nodes run on your own infrastructure, which is why a single Igra RPC node can be free, permanently. Their beta is now open. Deploy an Igra RPC node in a few clicks, full node support is planned. app.novacula.io, code IGRA2026"
https://x.com/Igra_Labs/status/2077763549628129655?s=20
Replymessage unavailable
Hey Mike — grouping your questions and answering each with the actual protocol values.
1) GAS REFUNDS
You asked: "What does the 'Gas refunds' value represent — are they credited or only an accounting metric?" (535 iKAS shown, wallet only ~9.45)
They're real transfers — after each successful attestation the contract sends native iKAS back to your attester address. But they reimburse the L2 gas you spent on that attestation, so they don't pile up as extra balance — they keep your attest-gas cost near zero. The 535 is the cumulative amount reimbursed across your 3,000+ attestations (roughly what you spent on that gas), not a separate claimable pot — which is why it isn't in your wallet, and why you can't "claim or stake" it. It covers L2 attest gas only, NOT the L1 KAS your kaswallet pays to post to Kaspa — those stay a separate cost. (In delegated mode, refunds land on the registered attester address, which may differ from the operator wallet you're watching.)
2) DOES STAKING MORE EARN MORE?
You asked: "Are rewards based only on successful attestations and uptime, or does staking more than 400,000 IGRA increase rewards?" (others' rewards look much higher)
Two separate things:
- How OFTEN you're selected is NOT stake-weighted — every active attester ~1/32 per block (~2,700/day), whether you stake 400k or 4M.
- How MUCH each attestation is worth IS proportional to your stake. IGRA rewards target ~15% APY and your iKAS share is proportional to stake. Timeliness counts too: blocks 1–30 pay a 120% bonus, decaying to 5% by block 512.
- Rewards also accumulate as your Attester Score (IAS) builds — a day-1 node has a tiny share vs one running for weeks.
So attesters earning much more are staking more and/or running longer with good uptime — not a hidden setting. (That's the "more cake, more rewards" / "ramps up over time" the others meant.)
3) REBOOTS / DOWNTIME
You asked: "If an attester reboots and is offline 2–5 minutes, is there any penalty, or do you only lose rewar
Replymessage unavailable
Yes — with 5 kaswallets you're running 5 workers (frontend-w5), and all 5 are meant to be funded and to share the load. Traefik round-robins requests across the workers, and each worker pays L1 KAS from its own kaswallet. Wallet 0 doing ~100% is NOT normal for a 5-worker node — it means your attestor is submitting to one worker directly (the old default http://rpc-provider-0:8535) instead of the Traefik endpoint (https://<your-domain>:8545), which bypasses the load balancer.
IMPORTANT — do this BEFORE fixing the routing:
Check W1..W4_WALLET_TO_ADDRESS in your .env. That's where each wallet's transaction CHANGE is returned, and the env template ships the same placeholder address for all five workers — if it's still a placeholder, the wallet loses its funds on its FIRST transaction. Wallet 0 surviving 3,000+ txs proves W0 is set correctly.
Then, in order:
- Check W1_KASWALLET_PASSWORD matches keys.kaswallet-1.json — "unsigned transactions" usually means the daemon can't sign (wrong password) or the wallet isn't synced; check kaswallet-1 logs and scripts/debug/wallet-status.sh.
- Update the attestor to the latest version and set its RPC_URL to https://<your-domain>:8545 (NOT rpc-provider-0:8535), then restart. Attestation txs will round-robin across all 5 wallets.
Alternatively, if you only want to attest and not run a public 5-worker RPC, just run frontend-w1 and fund only Wallet 0. Both are valid — the thing to avoid is 5 workers with the attestor pinned to one, or unpinning it while wallets 1–4 still have placeholder change addresses.
Replymessage unavailable
My dashboard now shows the attester is Active again, but I also noticed my penalty total is -277.91 IGRA while Slashes = 0.
Can you clarify exactly what contributes to the “Penalties” value?
Are these from missed attestations before or during pauses, or can other events increase this number? Does a clean Pause/Resume operation itself ever add penalties?