Loops HouseSharded Trolls

NEAR HACKATHON
Links
Team
1 member- IMOwner
Immanuel
Overview
Problem: a NEAR contract never splits across shards, so a token is one shard's worth of capacity. Claim rushes have filled NEAR shards before (the shard holding game.hot.tg ran 42.5% full against 10.2% elsewhere before its 2024-03-21 split), and a memecoin launch is exactly that load. What we built: Sharded Trolls, a launch kit that splits one NEP-141 token's ledger into eight contracts, the trolls, one on each reachable shard, plus a root that settles each day. A holder's home troll is a hash of their account, so the crowd spreads evenly. A cross-troll transfer is debit, credit, confirm: a failed credit refunds in full and a landed credit is never refunded, so a failure can never mint. The mechanic: crossing a shard pays a 0.25% Troll Toll that the destination troll eats as food. In the daily Feeding every troll needs feeders; if all eight are fed, feeders share a reward paid from food first, then the launch pool; a starving troll burns 1% of its hoard. Anyone can settle a day for a small NEAR bounty. STRL is the first coin. How NEAR fits: shard placement checked against the live layout, one global contract code by hash for all eight trolls (the next token deploys for about 3.65 NEAR), async receipts and joined promises for transfers and settlement. Live on NEAR testnet with a public app at strl.xavio.dev; every check (fan-out, refunds, the 4 KB message bound, a full fed and starved cycle) is a testnet transaction. Synthetic local-network load with mainnet's layout: 0 congestion rejections vs 280 for one ordinary token. Not faster per transfer; the gain is room.