Battle.in, sniper.in, catalog.in and the explorer all draw from this one file. Settle it here and nothing gets restyled twice.
One theme, on purpose. IndiaCoin is a dark product — there is no light palette to fall back to, so every surface and every colour is painted explicitly rather than inherited from whatever is behind the page.
Lowercase i, uppercase C. The C is drawn as a struck coin edge, open on the right; the i leads, and its dot is the only cyan element in the whole mark — the same cyan that means chain everywhere else in the product. Two strokes and a dot, so it survives being 16 pixels wide.
At favicon size the stroke thickens and the dot grows — the same geometry, retuned, because a mark scaled linearly to 16px turns to mush.
Every transaction's hash covers the one before it. This is the component that shows it, and it appears on the explorer home and on every transaction page. It is the honest version of "feels like a blockchain" — a reader can take the preimage we publish and recompute the hash themselves.
Blue is never used to say "good" and green is never used to say "IndiaCoin". Keeping the accent and the semantics separate is what stops a screen full of numbers turning into a screen full of noise.
Your wallet address is public. Anyone can look it up on the explorer and see every coin that has ever moved through it — that is what makes the ledger transparent. What is never shown is who the address belongs to.
Every figure uses font-variant-numeric: tabular-nums. In a ledger, digits that do not line up column to column read as sloppy long before anyone can say why.
Four figures, four different meanings. Only the one the reader came for gets the accent treatment; the rest sit quiet so the hierarchy survives.
Every address carries a colour derived from the address itself, so a wallet you see often becomes recognisable before you have finished reading it. System wallets are named instead of hashed — nobody needs to memorise the treasury's address.
The badge carries the type, the colour carries the direction, and the amount is the only thing in the row set at full weight. On a phone the badge drops to its own line rather than squeezing the amount.
| # | Wallet | Site | Earned today |
|---|---|---|---|
| 01 | iC-7f3a9b2c1e | battle.in | 485.0000 |
| 02 | iC-a91e04b7dd | catalog.in | 310.0000 |
| 03 | iC-36f8eb44c7 | battle.in | 295.0000 |
| 04 | iC-5c02de91af | sniper.in | 120.0000 |
One primary per screen. .btn-danger is outlined rather than filled — a destructive action should be findable, not inviting.
Most people's first look at a wallet is an empty one. It should read as a starting point, not a failure.
Set every amount, address, hash and timestamp in IBM Plex Mono with tabular figures. No exceptions — a balance in the body face immediately looks wrong next to one that isn't.
Reserve cyan for the chain. Height, hashes, the verification tick. When cyan appears, it means "this is provable".
Show four decimal places on any exact figure, and trim them on display figures. 1 iC is 10,000 units internally; the UI should never imply more precision than a number actually has.
Use blue for success or green for branding. The accent and the semantics do separate jobs, and mixing them makes a dense screen unreadable.
Put everything in a card. Border, fill and shadow each say "separate object". Rows in a feed share one surface; a stat tile earns its own.
Say "blockchain" in the interface. Say height, hash, transaction, wallet. The product is more convincing when it uses the vocabulary rather than the label.
Ships as public/assets/ic.css — one file, no build step, linked by every page on indiacoin.com and copied to each game site for its balance badge.