See the network
Watch a relationship keep paying.
Every circle is a record. Every line is a claim. Press play and move through thirty years — a client transacts, and the commission routes back up the bracket to the person who made the introduction, however long ago that was.
Selected record
Click any node in the map to see the record behind it — who it belongs to, when it was created, and the hash that fixes it in the chain.
Running total
Against what you have now
A CRM records the claim. It does not keep it.
This is not a knock on the products. Salesforce, HubSpot and the PRM tools built on them are good at what they are for. The difference is structural — a deal registration is a window the vendor grants you, and this is a record neither party can revoke.
| CRM / PRM deal registration | Commission software | This network | |
|---|---|---|---|
| How long the claim lasts | 30–180 days, by tier and deal size. On expiry the original partner loses the claim and the account opens to other partners and to the vendor's own direct team. | As long as the plan document says, and usually only while you are employed or under contract. | Permanent. It decays in value toward a floor and never lapses. Year 30 still pays. |
| Who decides the claim exists | The vendor approves or rejects each registration. | The company running the plan. | First recorded with evidence. A later claim is recorded too and ranks behind, visible to both parties. |
| Can it be edited afterwards | Yes. It is a row in a database an administrator controls. | Yes. | No. Append-only and hash-chained — a change to any field breaks every hash after it. |
| Do you have to name the client | Yes. Registering means putting your relationship in someone else's system. | Not applicable. | No. Commit sha256(client + salt) and reveal only to claim or settle a dispute. |
| Does it survive leaving | No. The record belongs to the instance. | No. | Yes. The claim is yours, not an employment term. |
| Does it check the payment is lawful | No. It routes a workflow. | It calculates. It does not opine. | Every payout runs the guard first, with the rule cited and the remedy stated when it cannot pay. |
| Can a counterparty verify it without your say-so | No. | No. | Yes — content-addressed and anchored on chain. |
Protection-period figures are the published norms for SaaS and channel programmes, not a claim about any one vendor's configuration — every programme sets its own. Sources at the foot of the page.
Why they can't just add it
A CRM's record is authoritative because the company running it says so. Make the record permanent and cross-company and you have changed what the product is — you now need a neutral registry and a settlement layer, which is a different business from selling seats.
It sits beside them, not instead
Keep your pipeline where it is. This holds one thing your CRM structurally cannot: the durable, verifiable claim over the relationship. Push attributions in from whatever you already use.
What that's worth to a firm
Originators stop leaving because their book is portable and provable. Disputes argue over dated hashes instead of memory. And the payout guard is the thing your compliance officer actually wants.
Real connection
Wire it to what you already run.
Record an attribution from anywhere
One call. From a CRM workflow, a Zap, a form, or a script. It returns the permanent record id.
Ask the guard before you promise anything
The same check the payout runs. Safe to call from a quoting screen — it records nothing.
The whole surface
| Endpoint | What it does |
|---|
Base https://rwa.unykorn.org/api/v1/network. The endpoints listed here are the ones responding right now — this table is generated by probing the live API when the page loads, so it cannot drift out of date.