Offers
List useful goods, tools, produce, equipment, spare materials, supplies, and community resources.
Relay Market
Local trade coordination for resilient communities.
Relay Market is the future RelayHub marketplace concept for offers, requests, services, skills, local resources, community notices, and settlement-neutral exchange. It is designed to help communities coordinate economic life without turning RelayHub into a bank, wallet, payment processor, or endorsement authority.
Purpose
A marketplace should help people find each other.
Healthy communities need practical ways to exchange goods, services, labour, skills, knowledge, resources, and help. Relay Market should support that coordination while keeping trust, legality, payment, moderation, privacy, and recovery explicit.
Requests
Ask for help, transport, materials, labour, introductions, advice, repairs, or local support.
Services
Coordinate repair work, gardening, building, tutoring, technical support, food, transport, and practical services.
Skills
Share skills, mentoring, apprenticeships, workshops, learning sessions, and mutual assistance.
Community notices
Publish working bees, local needs, resource updates, lost-and-found, event needs, and practical announcements.
Local resources
Help people find shared tools, spaces, equipment, storage, vehicles, supplies, and local capability.
Core boundary
Trade coordination is not the same as payment settlement.
Relay Market should help communities coordinate trade. It should not pretend to confirm external payment, guarantee delivery, custody funds, recover wallets, certify sellers, or make every listing trustworthy. Those are separate capabilities requiring separate policy, validation, review, and implementation.
Coordination, not custody
Relay Market should help people coordinate exchange. It should not custody funds unless separately specified, audited, legally reviewed, and validated.
Settlement-neutral by default
Communities may use cash, barter, mutual credit, bank transfer, local credit, TNE, or other lawful methods without forcing one model.
Listings are not endorsement
A visible listing does not automatically mean trust, certification, recommendation, payment confirmation, or delivery guarantee.
Trust remains local
Reputation and trust should be contextual, transparent, challengeable, revocable, and subordinate to community governance.
Community rules matter
Each community should define who may list, what may be listed, moderation expectations, retention rules, and dispute handling.
Policy still governs
Local autonomy does not override safety, lawful operation, identity integrity, recovery, privacy, security, or validated hardware limits.
What could be listed
Practical exchange, not abstract ecommerce.
Relay Market should focus on what communities actually need: local help, available resources, useful skills, small trade, practical services, community notices, and coordination under real-world conditions.
Example listing categories
Goods
Services
Tools
Produce
Transport
Repairs
Training
Accommodation
Volunteer help
Community resources
Event needs
Emergency supplies
Settlement-neutral
Communities should not be forced into one economic model.
A RelayHub community may coordinate trade while using cash, barter, mutual credit, local credit, bank transfer, TNE, invoices, receipts, or other lawful settlement methods. Relay Market should support economic diversity without making any one settlement layer mandatory.
Payment intent
A future listing may express intent to pay, request payment, or reference an invoice without proving that settlement occurred.
Settlement notes
Communities may record notes, receipts, references, or status where policy allows, but external confirmation must not be claimed unless validated.
Optional integrations
Settlement integrations should remain optional, explicit, lawful, reviewable, and unable to compromise local operation or recovery.
Trust and reputation
Trust is not manufactured by a marketplace.
Relay Market should support trust, but it should not replace human judgement, community relationships, moderation, accountability, or local governance. Visibility is not verification. Participation is not endorsement.
Known participants
Communities should be able to distinguish unknown, discovered, paired, trusted, limited, quarantined, and revoked participants.
Contextual reputation
Reputation should be local, explainable, challengeable, reversible, and never treated as absolute truth.
Dispute paths
Communities should be able to define their own dispute process, moderation rules, listing rules, and escalation paths.
Local-first operation
A local marketplace should not die when the internet does.
Relay Market should remain useful inside a local community wherever practical. Wider federation, sync, remote visibility, or external settlement tools may enhance the marketplace, but they should not become hidden dependencies for basic local coordination.
Local-only
The local marketplace should remain useful inside a community even when internet or wider federation links are unavailable.
Federated
Communities may choose to share selected marketplace listings with trusted neighbouring communities or federations.
Degraded
If sync, storage, transport, or federation fails, the system should explain what still works and what no longer works.
Recovered
Marketplace records, trust state, community rules, and useful history should have realistic recovery paths where supported.
Community policy
Each community needs its own marketplace rules.
Marketplace rules should be understandable, visible, enforceable, and recoverable. The ecosystem can provide defaults, but communities should govern their own local spaces within safety, legal, trust, privacy, identity, and recovery limits.
Who may list?
Communities may decide whether listings are open to members, guests, verified members, trusted vendors, stewards, or federation partners.
What may be listed?
Communities should define permitted categories, restricted items, illegal or unsafe listings, moderation rules, and review expectations.
How long does it remain?
Listings, requests, receipts, disputes, reputation notes, and marketplace records require explicit retention and deletion rules.
Federated marketplace
Communities may share listings without surrendering autonomy.
Federation should be selective and consent-based. A community may choose to share only certain listing types, only with specific communities, only under defined moderation expectations, and only while retaining the right to revoke federation trust.
Local marketplace
Listings visible only to the local community or household network.
Shared categories
Selected categories such as tools, produce, transport, workshops, or emergency supplies may be shared wider.
Federation agreement
Shared visibility should be governed by explicit trust, moderation, data retention, and dispute expectations.
Hard boundaries
What Relay Market should not pretend to do.
Clear boundaries protect users, communities, operators, and the RelayHub ecosystem from false confidence.
Relay Market should not guarantee payment unless a validated settlement confirmation system exists.
Relay Market should not imply endorsement merely because a listing is visible.
Relay Market should not require one currency, token, payment provider, or economic model.
Relay Market should not become a hidden dependency for basic community communication.
Relay Market should not bypass community rules, safety policy, legal limits, or trust boundaries.
Relay Market should not expose private marketplace records without explicit policy and consent.
Roadmap
Build the marketplace only after the basics are trustworthy.
Relay Market should grow through validation: simple local coordination first, then policy, trust, recovery, community operation, federation, and optional settlement integrations.
Concept
Define marketplace scope, policies, listing types, trust boundaries, moderation rules, and settlement boundaries.
Local trial
Validate simple offers, requests, services, local notices, and community moderation inside one small community.
Community operation
Add roles, retention, local search, categories, support export, recovery guidance, and plain-language state visibility.
Federated sharing
Allow selected listing types to be shared with trusted communities under explicit federation policy.
Optional integrations
Explore settlement references, receipts, invoices, payment intent messages, and lawful external integrations.
Early interest
Help shape local-first trade coordination.
Relay Market should be shaped by real households, rural communities, local groups, small producers, service providers, tool-sharing groups, preparedness circles, and community operators.
Interested in Relay Market?
Register interest if you want to test marketplace concepts, community listings, offers and requests, services, skills exchange, or federated trade coordination as RelayHub develops.