Shuffle dev log #4 π€π
Todayβs focus: token checks, controlled rebalancing and making the basket easier to follow.
π Verified code before buying
Tokens must have publicly verified source matching their deployed contract code. For proxy tokens, checks also cover the underlying implementation.
Candidates are screened in CoinGecko market-cap order for source verification and qualifying liquidity. If verification canβt be established, the purchase doesnβt proceed.
Verified source isnβt a security auditβitβs one layer alongside pool checks, trade simulation and backing checks.
π‘οΈ Checking what backs XSHUFFLE
The system compares actual token holdings with minimum backing reconstructed from confirmed on-chain history.
Checks run before automated trading, again before signing, and through monitoring every five minutes. A detected shortfall blocks automated trading pending review.
βοΈ Daily reviews, measured execution
At 12:00 UTC, the index reviews holdings, rankings and eligibility to assess its allocations.
Rebalancing sales are capped at 0.05% of each tokenβs total supply per hour, including
$SHUFFLE. Smaller adjustments sell less; larger ones continue through hourly batches.
If a token is leaving the basket, its final sale and replacement purchase happen together, keeping the basket complete.
π― A clear finish
When follow-up selling is needed, the system works through it, then reassesses the market before putting accumulated WETH to work.
Once the rebalance is complete, automated portfolio trading waits until the next daily review. Fee receipts continue accumulating as WETH during that wait. User deposits and withdrawals remain available.
π Clearr rebalancing activity
The dashboard groups related transactions into one rebalance history, showing tokens sold and purchased, balances before and after, allocation targets, gas costs and an execution timeline.
You can follow the full adjustment across multiple batches in one place.
π Documentation that explains the process
The docs cover selection, execution limits, hourly follow-ups and when trading pauses between daily reviews.
A settings reference is generated directly from project configuration, with checks to catch documentation drifting from those settings.
A basket you can follow, with clear rules behind its decisions.
shuffle.meme