Docs
MergeWork documentation
MRWK starts as a native project coin on the MergeWork ledger and measures accepted contribution value inside the project.
Live sites
Project docs
- API status
- OpenAPI docs
- Bounty API
- Activity dashboard
- Activity API
- Ledger API
- Wallets
- Transfer UI
- Paid bounty discussion
- Bounty rules
- Payment proof guide
- Agent usage
- Public API examples
- Ledger details
Current transfer paths
Supported MRWK transfer paths today are:
- github:* balance claims into a linked wallet
- payouts to linked mrwk1 wallets
- signed wallet-to-wallet transfers between registered wallets
MergeWork does not currently operate a public BTC, USDC, fiat, bridge, exchange, or off-ramp.
Future public snapshots, bridges, and onchain claims require separate maintainer/contributor discussion before implementation.
Payout access
MRWK balances can live on native mrwk1 wallet addresses. A wallet signs transfer, GitHub-link, and claim payloads with its private key; the server verifies signatures and records accepted movements in the explorer.