A world you can make your own.

Run Hills Craft World

Use Node.js 24.x, matching the tested production runtime. From the HillsCraft project folder:

npm install
# Copy .env.example to .env.local if customizing providers
npm run dev

Open http://localhost:3000. The public research endpoints need no API keys. For sustained use, configure a dedicated Robinhood Chain RPC provider in .env.local. Never put secrets in a NEXT_PUBLIC_ variable.

npm test
npm run typecheck
npm run build
npm start

Real reads. Clear boundaries.

The reader defaults to Robinhood Chain mainnet (chain ID 4663), with testnet (46630) and Base (8453) available explicitly. Robinhood RPC reads work from the deployed Vercel runtime. Public indexing may be unavailable or incomplete; each request shows its actual limitations. Dedicated provider overrides are available for local environments or sustained usage. Network reads never silently switch chains. Native balances and deployed bytecode come from RPC. Complete token and transaction lists require an indexer; Blockscout failures appear as partial data.

Stock perpetual markets are discovered from Hyperliquid’s live xyz universe and restricted to a documented stock-symbol list. Mark prices, oracle reference prices, funding, and open interest come from the venue. Pool discovery uses a bounded DEX Screener search on Base or Ethereum; it is not a complete chain scan.

Approve a session. Review every action.

The terminal submits reviewed stock-perpetual orders directly to Hyperliquid. Execution is on HyperCore, separate from Robinhood Chain. Connect a supported browser wallet and review the separate, short-lived trading-session permission. Approving the session places no order. Then confirm venue eligibility and review the market, side, quantity, price bounds, collateral and estimates before explicitly submitting each action. Cancellation, position reduction and leverage changes each require their own review.

Live venue data determines balances, supported markets and account limits. Orders can rest, partially fill, fail or be rejected; submission alone is never described as a fill. Stale data and unsupported account modes block actions with a specific explanation. The official venue link remains available for funding, account setup and unsupported operations. No deposit or transfer is initiated by this app.

A recipe is a set of rules.

Create a recipe in the Community Workshop, select its dataset and chain, and add typed filter rules. Save it to this browser, export validated JSON, or share a URL. Importing a link previews its rules; saving is your choice. Rules are evaluated as data, never as executable code.

Personal recipes and watchlists stay in your browser. Shared URLs contain the complete recipe, including its author and rules. Public publishing uses Neon PostgreSQL with a separate wallet sign-in, ownership checks, pagination and reporting. The server verifies a domain-bound, expiring signature and single-use nonce. For your own deployment, configure server-only DATABASE_URL and run npm run db:migrate. The workshop shows availability; saving locally never publishes automatically.

Small contributions matter.

Read README.md, CONTRIBUTING.md, and docs/ARCHITECTURE.md in the repository. Reproduce an issue, keep changes focused, add tests for behavior, and run the type check and production build. Financial and provider changes must cite primary documentation.

Security and attribution

See SECURITY.md for responsible disclosure. Remote contract source and metadata are untrusted content. Findings in the reader are observations with evidence, not a security audit or a safety rating.

Original project code is MIT licensed. The supplied HillsCraft portrait remains its owner’s asset. External contracts, provider APIs, data, and third-party dependencies keep their own licenses and terms.

Charts use TradingView Lightweight Charts™. Copyright © TradingView, Inc.