01
Trust with a trail of evidence
Multiple nodes verify source-chain events and record their confirmation basis. Every receipt comes with traceable context.
BUILT FOR ON-CHAIN PAYMENTS
Every transfer.
A clearer signal.
Connect on-chain facts to real-world applications. A decentralized network to observe, verify, and deliver transfer notifications. So you can focus on a better payment experience.
Protocol in designIt starts with verifiable transfers.
NotifyCool
Source event observed
0x8f…3a2bIndependent nodes. Shared truth.
transfer.finalized
Transfer receiptVerified. Traceable.
receipt_0x7e…9f4aHTTPS +NETWORK CONCEPT · NOT LIVE DATA+
01/
Watch on demand
Work backed by active, funded tasks
02/
Verify together
Independent nodes. Public rules.
03/
Keep results open
Confirmed receipts anyone can read
04/
Connect your way
Webhooks or your own node
DESIGNED FOR THE NEXT WAVE OF PAYMENTS
Stablecoin paymentsWallets & treasuryBusiness financeNode operators
LESS COMPLEXITY. MORE CLARITY.
A complex on-chain world. A clear transfer signal.
From discovering an event to delivering it, bring fragmented monitoring into one verifiable, public protocol.
02
One callback. Your application.
Receive confirmed results over HTTPS, without running a network node. Or deploy your own node and own your integration.
03
Defined work. Defined budgets.
Authorize task spending, set periodic budgets and cap event fees. Costs are linked to receipts, making spending traceable.
6months
ROLLING HISTORY
A lighter network. A useful memory.
Six months of rolling history for queries and replay. Export the evidence you need to keep for longer.
FROM TRANSFER TO SIGNAL
It happens on-chain. Your app knows.
One transfer. Four explicit steps. Source-chain confirmation and NotifyCool finality, clearly distinguished.
01 / WATCH
Define your watch
Choose a chain, token and addresses. Set the rules and authorize a budget.
02 / VERIFY
Observe & verify
Nodes discover events and independently check matching rules and source finality.
03 / FINALIZE
Record the receipt
The network accepts the result and records the receipt with its authorized fee.
04 / DELIVER
Deliver to your app
Receive via webhook or node, verify signatures, and process idempotently.
Funds stay on the source chain. NotifyCool verifies transfer facts without holding payment funds.
BUILT WITH DEVELOPERS IN MIND
Familiar interfaces. Transparent results.
Connect your application without rebuilding your monitoring stack. Version one plans for both hosted webhooks and node subscriptions.
- Stable event IDs for idempotent processing
- Signed delivery and verifiable receipts
- Failure records, bounded retries and cursor replay
CONCEPT EXAMPLE · SCHEMA SUBJECT TO CHANGE
{ "schema_version": "0.2-draft", "event_id": "evt_example_001", "type": "transfer.finalized", "watch_id": "watch_example_042", "receipt_id": "receipt_example_7e9f", "transfer": { "amount": "100000000", "token_contract": "<supported_contract>" }, "network_position": "<finalized_position>"}Illustrative JSON. No live network connection.JSON
THE ROAD AHEAD
Build trust. One milestone at a time.
Progress measured in verified outcomes and working integrations.
PHASE 01In design now
Protocol prototype
Public watches, receipts, prepaid ledger and basic webhooks. One complete end-to-end flow.
PHASE 02Planned
Multi-operator testnet
Independent operators, a second adapter, reorg handling and delivery recovery.
PHASE 03Planned
Payment pilots
Real integration needs. Measurable costs, coverage and service reliability.
PHASE 04Planned
V1 mainnet readiness
Finalize supported assets, fees and participation rules. Complete security review and acceptance tests.
BEFORE YOU BUILD
Good questions. Clear answers.
The network, the integration, and the choices behind them.
Read the whitepaperIs NotifyCool live yet?
NotifyCool is in the product and protocol design phase. This site describes planned capabilities from whitepaper v0.2, not a live network. Supported chains, contracts, fees and service targets will be established through testing and acceptance.
Do I need to run a node?
No. Version one plans to offer hosted HTTPS webhooks. Create a task, authorize a budget and verify your endpoint through an API. You may also run a regular node or self-host a delivery gateway for more control.
Does NotifyCool hold payment funds?
Transfers stay on their source chains. NotifyCool does not custody payment funds or collect payment private keys. It only manages task budgets for its own services. Order matching and business accounting remain with your application.
What about duplicates or failed deliveries?
Notifications use at-least-once semantics and can arrive more than once or out of order. Deduplicate by event_id while correctly handling corrections. Bounded retries, failure records, manual redelivery and cursor recovery within retention are planned. An unavailable endpoint is not guaranteed to receive a notification.
How are history and watched addresses handled?
Historical bodies and event details have a default six-month rolling window. Current state and necessary security metadata follow their own lifecycles. V1 proposes public addresses and matching rules; callback URLs and signing keys stay out of public blocks. Export long-term audit evidence before history expires.
A CLEARER SIGNAL STARTS HERE
Your next transfer. A world of possibilities.
Explore simple, open and verifiable infrastructure for on-chain payments.
Discover NotifyCool