Build with MoonShip
Compose social trading around shared identity, evidence and relationships.
Release reference · Updated 14 October 2026On this page
Choose an integration layer
Read public settled relationships for a discovery or analytics experience. Add user-selected source buys through the order flow. Use exact Relation Token holdings for community participation. Each layer retains its own permissions and evidence.
Trading frontends, wallets and communities are possible application directions, not announced partnerships. Automated copy trading needs a separately implemented execution and authorization system before it can produce qualifying settled actions.
Start with the TypeScript SDK
The SDK lives in packages/sdk/src/ in the repository. It is not advertised as a published npm package. Use the pinned repository dependencies and explicit deployment configuration. The example below is read-only; client, core, subject and wallet are your verified inputs.
import { readFanPairs } from './packages/sdk/src/index.js';
const block = await client.getBlock({ blockTag: 'finalized' });
const pairs = await readFanPairs(client, core, subject, wallet, {
blockNumber: block.number,
offset: 0,
limit: 25,
});Useful interfaces
readSubject reads controller revision and linked wallets. readFanPairs reads registered subject/asset pairs and balances. readEconomicAction observes source and destination execution. readRevenuePage checks the V0.4 pool and wallet income under an explicit scope.
An observed executed action is not itself proof of Monad Core acceptance. Reconcile the matching ActionSettled and FanMinted receipt before presenting issuance as complete.
Run an isolated demonstration
Use Node 22 and Foundry v1.8.5. The demonstration uses Monad-enabled Anvil, local test accounts and mock bridge/pools. It does not prove public bridge acceptance or independent production verification.
npm ci
npm run check
npm run demo:moonshipExecution and admission
Reusable interfaces do not grant arbitrary settlement or mint authority. New execution Cores must be reviewed and admitted; receipt witnesses and their domains must match the configured deployment. Identity proofs never authorize asset spending.

