Pool reward snapshots
Record participating miners over a period and distribute rewards by block wins or share.
A lightweight token, snapshot, and settlement layer for builders, pools, communities, and real-world ecosystem rewards — built on top of the ITC chain.
Proof-of-work gives Interchained security and fair distribution. But a chain becomes more than a ledger when people use it to coordinate work, rewards, access, identity, and ownership.
A chain is a ledger of what happened. A used chain is a record of what people did together.
ITSL is a lightweight layer for issuing, tracking, and settling digital assets, participation records, reward snapshots, and ecosystem proofs — using the Interchained chain as the source of truth. No new chain. No bridge. Operations are signed, broadcast, and settled on-chain.
Create a token or asset with a name, symbol, decimals, and supply. Live today via the ITSL CLI and RPC.
Every transfer, mint, and burn is recorded. Read balances, supply, and full operation history per token.
Capture who participated over a period — block wins, contributions, or holdings — as an accountable record.
Distribute tokens to contributors and miners by rule. Transfers carry memos, so each payout has context.
Operations are signed and settle on the ITC chain itself. The same proof-of-work secures the assets.
A transfer with a memo is a receipt. Use it to evidence participation, access, or fulfilled obligations.
ITSL ships as an open-source Python SDK and CLI that talks directly to interchainedd. Issuing, transferring, and tracking tokens is real and usable now — the snapshot and settlement tooling on top is what's emerging.
# 1 · issue a pool reward token $ ./itsl.py --rpcuser=u --rpcpass=p \ createtoken "1000" "PoolRewards" "POOL" 8 → token created · symbol POOL · decimals 8 # 2 · pay a miner, attach a receipt memo $ ./itsl.py ... tokentransfer itc1q…miner POOL "0.10301990" \ --memo "week 42 · block reward share" → signed · broadcast as TOKENTX · settled on-chain # 3 · audit the full history $ ./itsl.py ... token_history POOL → [ transfer, mint, transfer, … ]
Practical patterns for pools, contributors, and applications. Status labels are deliberately conservative — what's live is marked live, everything else is roadmap.
Record participating miners over a period and distribute rewards by block wins or share.
Mint a token for contributors and transfer credits with a memo for each acknowledged piece of work.
Hold-to-access tokens that gate spaces, roles, or events. Balance checks are live; gating tooling is forming.
Issue a named asset with fixed or mintable supply, and an explicit operator who controls issuance.
Distribute to a list of addresses from a snapshot of holders, contributors, or miners.
Use signed transfers with memos as receipts that evidence work done or participation earned.
Structured allocations to builders and maintainers, settled on-chain with an auditable trail.
Meter and settle product usage in a token your application issues and accepts.
A pool wins blocks during a period. Participating miners are recorded in a snapshot. Rewards, credits, or tokens are then distributed based on participation, block wins, or predefined allocation rules. Snapshots turn activity into accountable records.
Over a defined period — say a week — the pool mines and wins some number of blocks on the SHA-256 chain.
Capture which miners participated and their share of the work, as a record anyone can check against the chain.
Allocate a reward per block won, then split it across participants by the pool's chosen rule.
Distribute the token with a memo per payout. Every miner gets a receipt; the pool keeps an auditable trail.
Example: a weekly pool snapshot can allocate a fixed reward per block won by the pool, then distribute it across participating miners according to the pool's chosen formula. Interchained has explored fixed-rate pool reward snapshots such as 0.10301990 ITC per block won by a pool.
A model for understanding the mechanism — shares are illustrative. Actual rates, formulas, and any program are set by each pool and subject to technical review.
ITSL is the coordination layer between miners, builders, pools, and applications. Here's the shape of a typical build — issuing and moving assets works today; the snapshot and display steps are emerging.
Create a token with name, symbol, decimals, and supply via createtoken.
Read token_history and chain data to capture participation over a period.
Carry context in transfer memos and read static info with token_meta.
Send to recipients with tokentransfer — each payout signed and settled on-chain.
Surface balances and receipts in dashboards, explorers, or wallets Planned
Wrap participation and settlement into your own product, pool, or community tooling.
ITSL sits between the applications people touch and the proof-of-work that secures everything. Settlement is not the end of the story — it's the base layer for what comes next.
Where people actually participate — products, pool dashboards, contributor programs, and community spaces.
The use layer. Issue and move assets, capture participation, program rewards, and turn activity into receipts.
The secured ledger. Operations are signed, broadcast as TOKENTX, and settled on-chain. Yespower remains only as an emergency fallback.
The token layer is live. Everything that makes it effortless — templates, formats, displays, and programs — is being built in stages with the community.
This page, plus a written spec for how tokens, memos, and proofs are used across the ecosystem.
In progressReusable scripts that read block wins and participation, then produce a distribution from a chosen formula.
EmergingA standard way to describe an asset — purpose, links, and image — so explorers and wallets can render it consistently.
PlannedBrowse tokens, balances, and operation history visually — for builders, pools, and auditors.
PlannedSurface token balances and receipts where users already are, and connect ITSL to other ecosystem tools.
PlannedStructured ways to fund and reward the people building the ecosystem, settled transparently on-chain.
Planned// Roadmap items are subject to technical review and community contribution.
ITSL is open-source and builder-owned. Start with the token layer that's live today, and help shape what comes next.