MOONSHIP / GETTING STARTED

Start with a simple relationship.

Alice buys an asset because of Bob. MoonShip connects both subjects, the exact asset and the execution evidence. Attribution is a deliberate user choice; it does not prove every psychological cause of the decision.

What do the protocol and applications do?

The protocol records facts, issues credentials, settles fees actually received and exposes public records. The Chrome extension discovers candidates, presents quotes and lets users choose an influencer and confirm an order. Community access and other specific rights are defined by applications.

What is a fan credential?

V1 uses a separate ERC-20 for each subject / asset pair. Bob/BTC names the credential associated with Bob and an exact BTC asset identifier. A qualifying buy issues it only after protocol settlement. An intent, payment or bridge message alone is not evidence that issuance is complete.

Applications may use credentials for participation thresholds and rights. A credential does not represent ownership of the original asset, the person or all their future income. It does not automatically grant dividends, redemption or a fixed return.

Current status: testnet development

Identity and payment use Monad Testnet (10143). Asset delivery uses Ethereum Sepolia (11155111). Mainnet trading is not open. The baseline configured test asset is Sepolia WETH; other quotes depend on the current asset directory and available route. The homepage’s BTC, ETH and UNI are illustrative examples.

This website provides project information. It does not connect wallets, collect authentication credentials or execute trades. Login, identity claims and cross-chain execution must be verified separately in a configured extension.

How do I use the Chrome extension?

  1. Get the source and build locally. The extension is not yet listed in the Chrome Web Store. The project is on GitHub; repository access is managed by the project maintainer. With source access and Node 22:
npm ci
npm run extension:build

The default build discovers candidates with public trading disabled. A testnet build needs deployment, authentication and backend configuration. Developers prepare these using the project documentation before running npm run extension:testnet. Backend credentials must stay out of the extension.

  1. Load the existing dist directory. Enable developer mode in Chrome’s extension manager, select “Load unpacked” and load apps/capital-extension/dist/. Rebuild and reload the same directory for updates.
  2. Follow the next step inside the extension. A configured testnet extension guides X login, test-asset funding and subject claims. Select another influencer, check the amount, fees, minimum delivery and Ethereum recipient, then approve USDC if needed and confirm payment.
  3. Read verified results. Reopen the popup to reconcile an existing order. Issuance is complete only after source-chain settlement is confirmed. Orders recovered as USDC issue no completed-trade credential. The account view shows balances, credentials and available credits.

About post discovery

A webpage’s name, handle or cashtag is candidate information. The author, stable identifiers and exact asset contract require independent verification. When post attribution is unavailable, select a registered influencer in the extension; webpage hints cannot stand in for an authenticated subject.

For builders

Subject identity, user authorization, actual execution, credential balances and fees received are separate facts. Applications can compose these records. An unverified statement cannot replace execution or revenue evidence.

Back to MoonShip