TED Developers

TED is a foundation designed to grow through its community. Business Members can create Service Plugins that add new features, improve existing systems, or even create entirely new experiences inside TED.
What is a Service Plugin?
Business Setup

Service plugins are plugins whose purpose is to provide services and additions to TED and other plugins.

Think of TED as a set of Lego blocks. TED Core provides the rules, security, payments, reputation, membership, governance, and infrastructure. Service Plugins build on top of that foundation.

Service Plugins can provide:
  • Search & Discovery systems
  • Profile Extensions
  • Page & Site Builders
  • Marketing Systems
  • Analytics Tools
  • Social Features
  • Automation Tools
  • AI-powered services
  • And anything else the community can imagine
Generate revenue through:
  • Plugin subscriptions
  • Advertising
  • Premium services
  • Business promotion
  • Lead generation
  • Professional services
  • Any model that follows TED rules

The goal is simple:

Build something useful, connect it to TED, and let members choose whether they want to use it.

Remember: on TED, reputation goes before you.

To create a Service Plugin, go to Business Setup, create a plugin, select Service Plugin as the Product Type / Plugin Registration Type, and choose the destination category.

Build with AI

You do not need to be a programmer.

Many Service Plugins can be built by describing what you want to an AI coding assistant and connecting the result to TED using the rules and systems described on this page.

Start small. Improve something useful. Let the community decide if it has value.

Then:

Verification Workflow
A reusable TED building block for features that must be checked before they can be activated.

Many TED features follow the same pattern:

Check
Approve
Activate

Instead of every application or Service Plugin creating its own approval process, TED provides a reusable verification workflow.

The workflow performs the required checks, creates a temporary approval, and allows the final action only while that approval remains valid. If the approval expires, the process simply starts again.

This gives every TED application the same reliable behavior while reducing development time and keeping the user experience consistent.

Typical uses
  • Verify a token before adding it to TED.
  • Verify a conversion provider before enabling it.
  • Verify a Service Plugin before activation.
  • Verify a future external service or integration before allowing it to operate.
Benefits
  • One consistent approval process across TED.
  • Temporary approvals with automatic expiration.
  • Protection against reusing the same approval twice.
  • Faster development of new TED applications and Service Plugins.
  • A consistent user experience throughout the ecosystem.
Developers should use this workflow whenever a feature requires verification before activation instead of creating a separate approval system for each feature.
Rules
  • Service Plugins cannot move member funds.
  • Service Plugins must use TED Core systems.
  • Service Plugins must declare their behavior.
  • Members can always return to TED's default system.
  • TED Core remains the final authority for payments, reputation, membership, governance, and security.
How Members Create One
Create the plugins on the "Business Setup" page, and to tell TED that this is a "Service Plugin", that is supposed to be added to or replace one of the systems on TED, you simply need to define it as a "Service Plugin" in the Product Type or Plugin Registration Type and select the place it is intended for from the list that opens.
New Service Plugins enter the Lobby and move into their destination category after receiving more than 10 TED Reputation ratings with a good average.
Destination Behavior
Search & DiscoveryCompetes with TED's default search. Members choose which search system to use.
Profile ExtensionsAdds new capabilities to member profiles.
Analytics ToolsExtends TED analytics pages.
Page & Site BuildersOpens as a separate tool.
Marketing SystemsOpens as a separate tool.
Social SystemsExtends TED with social features.
Members can always return to the TED default experience.
Business Automation & Integration
TED does not replace your business software. It securely connects your business software to blockchain payments.

Business Automation lets TED deliver new paid orders into the supplier's own business tools, without TED becoming a storage server.

TED proves that payment happened on the blockchain. The supplier keeps using their own systems for customers, orders, shipping, accounting, CRM, ERP, email, spreadsheets, Shopify, WooCommerce or any other business tool.

The simple supplier workflow
This is the part normal business owners need to understand.
1
Create an Escrow product or Recurring pluginThe supplier defines what is being sold, what customer details are needed, and how orders should be delivered.
2
Choose how orders are receivedUse TED Supplier Gateway for automatic delivery, Custom Integration for advanced systems, or Manual mode only as a fallback.
3
Customer buys and paysThe customer fills the required fields once, then pays through TED.
4
Blockchain proves paymentTED records/verifies the payment, amount, product/plugin ID and form payload hash.
5
Supplier Gateway receives the orderThe Gateway combines blockchain payment proof with the customer's private order details.
6
Supplier fulfills the orderThe verified order is sent to the supplier's chosen destination: email, CSV, Google Sheet, Shopify, WooCommerce, CRM, ERP or custom API.
Recommended: TED Supplier Gateway
Best choice for almost every supplier.
  • Automatically receives every paid order
  • Runs on the supplier's own computer, server, cloud account, NAS or future TED Desktop business module
  • Verifies payment directly from the blockchain before fulfillment
  • Receives the private customer details from checkout without TED storing them
  • Sends verified orders to the supplier's chosen business tool
Custom Integration
For suppliers or AI assistants that can configure their own automation.
  • Use a supplier-owned endpoint or automation system
  • Store only safe references and hashes inside TED
  • Do not put API keys, passwords or secrets on-chain
  • Supplier system must still verify blockchain payment before processing
Manual mode
Fallback only.
  • Useful for very small suppliers or testing
  • Not recommended for high order volume
  • Supplier still verifies payment from blockchain before fulfillment
  • Can be changed in future products/plugins by creating new locked setup terms
How to connect with an AI assistant
This is the prompt suppliers can copy into their own AI tool.
I am connecting my business to TED Business Automation.
Guide me step by step.
I want to use TED Supplier Gateway.
My business system is: [Shopify / WooCommerce / Google Sheets / Email / CRM / ERP / Custom API].
Explain which fields I should fill in, what should never be stored on-chain, and how to verify that paid TED orders are reaching my system.
Supplier setup checklist
  • Choose TED Supplier Gateway unless there is a reason to use Custom Integration or Manual mode
  • Choose where verified orders should go: email, CSV, Google Sheet, Shopify, WooCommerce, ERP, CRM or Custom API
  • Define the customer fields needed for fulfillment
  • Reuse TED's built-in shipping, country, region and tax fields instead of duplicating them
  • Never enter API secrets, passwords, private keys or customer databases into on-chain fields
  • Create the Escrow or Recurring plugin only after the required automation fields are complete
What TED stores, and what TED does not store
TED stores or anchors:
  • Product/plugin integration mode
  • Bridge ID or safe supplier reference
  • Endpoint/reference hash
  • Customer form schema hash and schema version
  • Payment proof, amount, token, product/plugin ID and payload hash
TED does not store:
  • API keys or passwords
  • Supplier private credentials
  • Customer private answers as permanent TED storage
  • Customer databases
  • Supplier CRM, ERP or warehouse records

Security rule: TED proves payment. The supplier-owned Gateway or supplier-owned integration receives the customer payload, checks the matching blockchain payment and payload hash, and only then creates the order in the supplier's own system.

Technical reference for AI assistants and developers
The supplier does not need to understand this section, but their AI assistant or developer can use it.
Customer form
  • Define label, type, required flag and optional choices
  • Keep schema inside TED's bounded schema size
  • Hash the schema and record the schema version
  • Hash submitted answers as form_payload_hash during checkout
Gateway / integration data
  • delivery_mode: supplier_gateway, custom_api or manual
  • bridge_id: supplier-defined connection identifier
  • endpoint_hash: hash of endpoint or delivery reference
  • event_mask: paid order, subscription created, renewal, refund, dispute or release
Verification
  • Read escrow/subscription account or emitted event from chain
  • Confirm product/plugin ID, payer, amount, token and payment status
  • Compute hash of received private payload
  • Match computed hash to on-chain form_payload_hash before fulfillment
Example verified order packet
{
  "ted_order_id": "TED-ORDER-102879",
  "escrow_id_or_subscription_id": "...",
  "tx_signature": "...",
  "buyer_wallet": "...",
  "amount": "0.1",
  "token": "UNKNOWN/Test Token",
  "payment_status": "confirmed",
  "form_payload_hash": "sha256-...",
  "schema_version": 1,
  "delivery_mode": "supplier_gateway",
  "bridge_id": "supplier-main",
  "encrypted_customer_payload": "...",
  "customer_answers": {
    "email": "customer@example.com",
    "phone": "+1...",
    "shoe_size": "42",
    "delivery_notes": "Leave near the front desk"
  }
}
18 Teddies for Marketing Systems

Marketing System Service Plugins may award up to 18 Pre-registration Teddies to future TED members before registration.

TED does not store candidate emails.

The Marketing Plugin manages:

  • Invitations
  • Emails
  • Missions
  • Progress Tracking
  • Education Flows
TED only verifies the final entitlement during registration.
Marketing Plugins pass:
  • Plugin Instance ID
  • Referrer TED Member ID
  • Claim Code
TED verifies:
  • Marketing System Service Plugin
  • First registration only
  • Claim not previously used
  • Maximum 18 Teddies
Then the entitlement is issued during registration.
Continue in TED App Example
The Marketing Plugin should send the candidate back to TED using:
ted://start?
ref=P123456
&instance=PLUGIN123-P123456
&claim=ABC123XYZ
Where:
  • ref = TED Member ID of the referrer
  • instance = Plugin Instance ID
  • claim = Unique claim code generated by the Marketing Plugin
TED uses this information to verify and issue the final Pre-registration Teddy entitlement during registration.
Hoverboard